public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Anthony DiSante <theant@nodivisions.com>
To: unlisted-recipients:; (no To-header on input)
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: uninterruptible sleep lockups
Date: Mon, 21 Feb 2005 19:06:23 -0500	[thread overview]
Message-ID: <421A777F.1010802@nodivisions.com> (raw)
In-Reply-To: <421A6426.6020802@nortel.com>

Chris Friesen wrote:
>> It's indisputable that there will always be driver bugs and faulty 
>> hardware.  Of course these should be fixed, but if it's possible for 
>> the kernel to gracefully deal with the bugs until they get fixed, then 
>> why shouldn't it do so?
> 
> Think of the overhead required to track every single resource ever 
> aquired by the process/thread/entity in question.  Then if/when it 
> hangs, you'd have to properly clean up every last one of them.

Yes, that would be difficult and expensive.  But if permanently-D-stated 
processes happened monthly on 50% of systems, then wouldn't it be worth it? 
  How about weekly on 10% of systems?  The point is that at some point this 
becomes worth considering, and with more people adding more new hardware to 
their systems every day, this problem is becoming more and more frequent.

> Much safer/simpler to leave it hung, and force an eventual reboot.

"Eventual" makes it sound far away, but the reality is that if part of your 
USB subsystem is D-stated, then "eventually" means next time you want to use 
your USB stick, or your printer, or your digital camera, or your MP3 device, 
  or... In other words, "eventually" means "right now, interrupting all your 
current work."

> If you have been given code that causes D states, bitch to the supplier 
> until they fix it.

The driver code for my devices has "been given" to me as part of the kernel. 
  Any of a handful of USB devices has caused permanent D states, as has a 
CDROM and a NIC.  I guess I'll need to start debugging all of these drivers. 
  When something goes into permanent D sleep, what should I do to start 
tracking down the problem?  Aside from obvious stuff like dmesg and checking 
/var/log/messages, neither of which ever seems to say anything useful when 
this happens.

> Kernel bugs are not acceptable.

That's a nice-sounding ideal, but the truth is that kernel bugs exist and 
are not uncommon.

-Anthony DiSante
http://nodivisions.com/

  reply	other threads:[~2005-02-22  0:08 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-21 19:18 uninterruptible sleep lockups Anthony DiSante
2005-02-21 19:45 ` 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 [this message]
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=421A777F.1010802@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