On 06/28/2011 17:24, Sergey Babkin wrote:
(Sorry about quoting, it doesn't always work well from the web client).
Most probably the process is running in an endless loop in the kernel
mode.
Where it got after entering the STOP state. Remember, the signals are
processed
only after the process exits from the kernel mode to the user mode,
and so are the
scheduling states. While it's in the kernel mode, you can't do anything
to it other than use the kernel debugger.
How is this normally possible to make program to loop in kernel mode on
-STABLE kernel? Doesn't this mean bug in kernel?
Yuri
_______________________________________________
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
