public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Anthony DiSante <theant@nodivisions.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: uninterruptible sleep lockups
Date: Mon, 21 Feb 2005 14:18:44 -0500	[thread overview]
Message-ID: <421A3414.2020508@nodivisions.com> (raw)

Processes that get permanently stuck in "uninterruptible sleep" (the D state 
as indicated by "ps aux") are such a pain.  Of course they've always 
existed, but at least on the 3 systems that I administer, they are far more 
frequent with udev than they ever were before.  I'm constantly upgrading 
udev, hal, etc on these 3 different systems, but still not a week goes by 
that one of them doesn't need a reboot because some hardware-related process 
is hung.

The most recent one was yesterday: I had run lsusb in the morning and had no 
problems, but at the end of the day I ran it again, and after outputting 3 
lines of data, it hung, stuck in D-state.  So now I have this:

[/home/user]$ ps aux|grep D
USER       PID %CPU %MEM   VSZ  RSS TTY      STAT START   TIME COMMAND
root        92  0.0  0.0     0    0 ?        D    Feb19   0:00 [khubd]
root       845  0.0  0.0     0    0 ?        D    Feb19   0:00 [knodemgrd_0]
root     29016  0.0  0.1  1512  592 ?        D    00:28   0:00 lsusb

It seems like this problem is always going to exist, because some hardware 
and some drivers will always be buggy.  So shouldn't we have some sort of 
watchdog higher up in the kernel, that watches for hung processes like this 
and kills them?

Don't get me wrong, I love rebooting every couple days... but I have a 
Windows system for that.

-Anthony DiSante
http://nodivisions.com/

             reply	other threads:[~2005-02-21 19:28 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-21 19:18 Anthony DiSante [this message]
2005-02-21 19:45 ` uninterruptible sleep lockups Valdis.Kletnieks
2005-02-21 20:24   ` Anthony DiSante
2005-02-21 20:54     ` Valdis.Kletnieks
2005-02-21 22:18       ` Anthony DiSante
2005-02-21 22:43         ` Chris Friesen
2005-02-22  0:06           ` Anthony DiSante
2005-02-22  0:36             ` Valdis.Kletnieks
2005-02-21 22:44       ` Anthony DiSante
2005-02-21 23:11         ` Nish Aravamudan
     [not found]     ` <421B12DB.70603@aitel.hist.no>
2005-02-22 11:16       ` Anthony DiSante
2005-02-22 12:26         ` Denis Vlasenko
2005-02-22 12:35           ` Anthony DiSante
2005-02-22 13:47         ` linux-os
2005-02-22 20:03           ` Anthony DiSante
2005-02-22 20:16             ` Chris Friesen
2005-02-22 20:29               ` Anthony DiSante
2005-02-22 20:24             ` Horst von Brand
2005-02-22 20:56               ` Chris Friesen
2005-02-22 21:40                 ` linux-os
2005-02-22 23:17                   ` Chris Friesen
2005-02-22 23:42                     ` linux-os
2005-02-23  0:25                       ` Chris Friesen
2005-02-23  1:05                 ` Horst von Brand
2005-02-23 10:04                   ` Bernd Petrovitsch
2005-02-22 21:31 ` Olaf Titz
2005-02-23 16:34   ` Nish Aravamudan
     [not found] <fa.duv6ag6.p5mth0@ifi.uio.no>
     [not found] ` <fa.irk349q.1c3si2o@ifi.uio.no>
2005-02-23  0:59   ` Bodo Eggert
2005-02-23 13:50     ` linux-os
2005-02-24  2:05       ` Bodo Eggert
  -- strict thread matches above, loose matches on Subject: below --
2005-02-23 16:55 Parag Warudkar

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=421A3414.2020508@nodivisions.com \
    --to=theant@nodivisions.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox