kern/164705: inability to terminate process in D state
Eugene M. Zheganin
eugene at zhegan.in
Thu Feb 2 08:20:12 UTC 2012
>Number: 164705
>Category: kern
>Synopsis: inability to terminate process in D state
>Confidential: no
>Severity: critical
>Priority: low
>Responsible: freebsd-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Thu Feb 02 08:20:11 UTC 2012
>Closed-Date:
>Last-Modified:
>Originator: Eugene M. Zheganin
>Release: 8.2-STABLE
>Organization:
RealService LLC
>Environment:
FreeBSD bsdrookie.norma.com. 8.2-STABLE FreeBSD 8.2-STABLE #0: Mon Jul 25 14:13:03 YEKST 2011 emz@:/usr/obj/usr/src/sys/GENERIC amd64
>Description:
There's only two holy grails in FreeBSD: one, nowadays patched but sometimes still haunting FreeBSD, is the panic (livelock, hangup, name it yourself) when the mounted media is physically removed (a diskette, a flash-disk etc).
And the second - this is inability to terminate a process when it hangs in D state. Of course, kill -9 didn't work (as always. I'm guessing thi isn't a 'uncatchable uniterruptable signal' as it's man page says, It looks more like 'no big deal, safe to ignore signal, just for a process knows that something is up')
Last time I plugged the USB-mouse out of its port to hadle the mess with the cord, and when I plugged it back - hald hanged in the D state, so did all of the usbconfigs and so on.
I had to reboot the FreeBSD just to get my mouse back. Like we're back in 1996 with an non-OSR Windows 95.
It's completely ridiculous.
>How-To-Repeat:
I'm pretty sure that if you're actually using FreeBSD, then at least once in a lifetime you got the need to kill something, you realise you cannot, and then when trying to understand what the hell is going on you see the magical D letter in ps's output, which means you're doomed.
>Fix:
There's always an answer. Reboot loves you.
>Release-Note:
>Audit-Trail:
>Unformatted:
More information about the freebsd-bugs
mailing list