Re: unkillable process ?
Re: unkillable process ?
- Subject: Re: unkillable process ?
- From: Pejvan BEIGUI <email@hidden>
- Date: Fri, 04 Apr 2003 21:44:44 +0200
- Organization: Project:Omega
email@hidden wrote:
On Thursday, April 3, 2003, at 12:12PM, Pejvan BEIGUI wrote:
I've got a real and weird problem, which seems to come from the
kernel, and hence I haven't been able to find the answer anywhere
else, i'm asking it here:
How can anyone explain this:
> [2:10:22pm] _pejvan_ ~ >> kill -9 1026
> [2:21:32pm] _pejvan_ ~ >> kill -9 1026
> [2:21:33pm] _pejvan_ ~ >> kill -9 1026
> [2:21:33pm] _pejvan_ ~ >> kill -9 1026
> [2:21:34pm] _pejvan_ ~ >> sudo kill -9 1026
> Password:
> [2:21:42pm] _pejvan_ ~ >> sudo kill -9 1026
> [2:21:44pm] _pejvan_ ~ >> sudo kill -9 1026
> [2:21:45pm] _pejvan_ ~ >> ps -U pejvan | grep 1026
> 1026 ?? Us 0:00.02 /Users/pejvan/devel/[...]
That "U" means that the process (or more appropriately, one of the
threads in the process) is blocked in the kernel in an "uninterruptible"
state. It is unacceptable for the kernel/drivers to so mark a thread
and then non make forward progress on it. Do you have any non-standard
kernel extensions? What system call was thread making when it got into
this state? You can find the latter by running the sample tool on the
process (or attaching with gdb).
In fact, this error doesn't come from my sources, it comes sometimes
when I use cdrdao. I only have one non-standard kernel extension: the
MSMouse kext.
I'll try to run the sample tool on it next time i get this crash, and
I'll report it to you. "Hopefully" this week-end.
I really need to be able to kill this process, since it totally blocks
the launching of any graphical app when it crashes, and there's no way
for me to restart the computer in clean way:
$ sudo shutdown now
will fail and after two or three minutes, I get in the text mode
output, with a message telling me that there have been some IPC
failure, which leads me to the question:
does the process crash and blocks some stuff? (which is totally wrong
on a preemptive OS)
does the IPC mechanism fail somewhere and make this process crash?
(which is weirder)
What you asked for [with that shutdown command] was not to reboot the
machine, but instead to bring it back down to single-user-mode. Two
things of note about that:
1. the un-interruptible process will still be blocked, more than likely,
unless the shutdown killed off the facility that it was blocked waiting
on (not likely).
2. Mac OS X/Darwin does not like being brought down to single-user mode
after it was already running in multi-user-mode. Many of the key system
services are implemented in user space. Bringing the system down to
single-user-mode killed those off. The IPC messages you see are because
you killed off the mach_init process that manages the namespace of
public mach ports. But you also killed off the dynamic pager, which
manages your swap files, and it doesn't like to get restarted either.
You probably wanted "shutdown -r now" where the "-r" is to force a reboot.
well, after being unsuccessfull with "sudo shutdown -r now" "sudo
reboot" "kill -9 -1" and Apple Menu > Log Out, I tried the "sudo shutdown".
Thanks for the info though, it's very intresting.
I'll keep you updated anyway.
Cheers,
Pejvan
_______________________________________________
darwin-kernel mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/darwin-kernel
Do not post admin requests to the list. They will be ignored.