Re: unkillable processes

["Jason A. Pfeil" <pfeil 10east com>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

That is more than likely correct.  It is also extremely likely that the
bug is in whatever device driver is in charge of hardware which the
process is using.  I have forgotten the details of this particular
process.  What is it?

- --Jason

Stuart D. Gathman wrote:
| On Fri, 2 Jan 2004, Jason A. Pfeil wrote:
|
|
|>D is a "deadlocked" state that may or may not be permanent.  It means
|>that the process has entered an uninterruptible sleep.  If it is waiting
|>on a kernel resource that it will never get access to, then the process
|>is forever hung and any resources it holds are ne'er to return to the
|>system.  Usually, when you get processes in this state and they stay
|>there, you have a reboot in your near future to recover.  :-)
|
|
| Since this happens regularly, it's a pretty serious bug.  I have to lower
| the shades and check for spy cams before rebooting, so that none of
the Windows
| users who've heard me bragging about Linux find out.
|
| What can I do to help debug this?  Or should I take it over to kernel.org?
| I think that unkillable processes are a kernel bug regardless of what
| application bugs may trigger the problem.
|

- --
Jason A. Pfeil
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQE/+XsIF7j4r5hBUugRAkPZAJ0Z4wDQ37xcbDBSzThZkbmcqtm+hwCfYlkQ
5h7ItTWOYQGswI1lDdruvxc=
=q6Wu
-----END PGP SIGNATURE-----