linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Mark Lord <mlord@pobox.com>
Cc: IDE/ATA development list <linux-ide@vger.kernel.org>
Subject: Re: libata total system lockup fix
Date: Mon, 25 Jul 2005 10:51:33 -0400	[thread overview]
Message-ID: <42E4FC75.70006@pobox.com> (raw)
In-Reply-To: <42E4ED70.1050501@pobox.com>

Mark Lord wrote:
> Jeff,
> 
> We corresponded about this bugfix ages ago,
> but I find I'm still patching it into each new
> kernel.org kernel to keep my system from locking
> up hard in the libata error handling path.
> 
> (error handling is triggered by the KDE/Gnome desktop
> polling the empty ATAPI drive every second or two,
> gets an error when no disc inserted, thereby triggering
> SCSI/libata error paths, which lock system hard once
> in a few thousand tries -- about once every two hours).
> 
> This patch originally came to me from you, and I've now
> forgotten where you got it from.  But it does fix the
> problem here.  I have also circulated this patch among
> many other users of "ata_piix" on modern laptops,
> and it seems to cure random lockups for them as well.
> 
> This configuration (2.6 kernel, ata_piix driving hard disk
> and DVD-RW drive in a Centrino laptop) is now very very
> commonplace, and the lockups are driving users crazy.
> 
> Sure would be nice to see it in 2.6.13 or 2.6.14 by default.

The problem with this patch is that is causes leaks, and doesn't 
actually ready the devices because scsi_eh_ready_devs() is never called: 
scsi_eh_abort_cmds() is guaranteed to fail out every time its called.

So it just trades one set of failures for another.  I don't dispute that 
lockups SUCK but someone (me? noone else is stepping up) needs to look 
into fixing it.

When I finish up SATA ATAPI today, I'll put this on the short list.

	Jeff




  reply	other threads:[~2005-07-25 14:51 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-25 13:47 libata total system lockup fix Mark Lord
2005-07-25 14:51 ` Jeff Garzik [this message]
2005-07-25 15:53   ` Mark Lord
2005-08-05  3:52     ` Tejun Heo
2005-08-05  4:01       ` Tejun Heo
2005-08-11 20:13         ` Jeff Garzik
2005-08-12  0:49           ` Tejun Heo
2005-08-12  2:22             ` Mark Lord
2005-08-12  2:38               ` Tejun Heo
2005-08-12  2:41                 ` Tejun Heo
2005-08-09 15:16       ` Mark Lord
2005-08-09 23:54         ` Tejun Heo
2005-08-10 14:16           ` Mark Lord
2005-08-10 21:24       ` Jeff Garzik
2005-08-19  0:46         ` Mark Lord
2005-08-19  3:21           ` Tejun Heo
2005-08-19  3:36             ` Mark Lord
2005-08-19  3:45               ` Tejun Heo
2005-08-19  4:01                 ` Mark Lord
2005-08-19  9:37               ` Erik Slagter
2005-08-19  9:35           ` Erik Slagter
2005-08-19 13:07             ` Mark Lord
2005-08-19 13:32               ` Bartlomiej Zolnierkiewicz
2005-08-19 13:37                 ` Bartlomiej Zolnierkiewicz
2005-09-03 22:58           ` Mark Lord
2005-09-03 23:06             ` Jeff Garzik

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=42E4FC75.70006@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=mlord@pobox.com \
    /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;
as well as URLs for NNTP newsgroup(s).