linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Lord <mlord@pobox.com>
To: Tejun Heo <htejun@gmail.com>
Cc: Mark Lord <liml@rtr.ca>, Jeff Garzik <jgarzik@pobox.com>,
	IDE/ATA development list <linux-ide@vger.kernel.org>,
	hare@suse.de
Subject: Re: libata total system lockup fix
Date: Tue, 09 Aug 2005 11:16:32 -0400	[thread overview]
Message-ID: <42F8C8D0.2010603@pobox.com> (raw)
In-Reply-To: <42F2E267.50402@gmail.com>

Tejun,

I'm back from holiday now, and will try your one-liner
in place of the more complex patch I had been using.

(that's what you intended, right?)

Should know within a few hours whether it solves this
problem here or not.

cheers
-- 
Mark Lord
Real-Time Remedies Inc.
mlord@pobox.com


Tejun Heo wrote:
> Mark Lord wrote:
> 
>>  >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.
>>
>> MMmm.. bummer if that's the case, but it does execute here
>> on my machine about once every two seconds, continuously,

...

>  Hello, Mark Lord.
> 
>  I think I've hit similar scsi-eh lockup problem during development of 
> new EH/NCQ helpers.  I currently don't remember where it exactly looped, 
> but I recall that scmds jumped back and forth between two lists, one of 
> which being eh_cmd_q which isn't cleared properly by SATA's strategy 
> routine.  Anyways, I'm attaching an one liner quick fix, which I'm not 
> sure if it will work or not.  Also, I'll post a combined patch of my new 
> EH/NCQ helpers in a separate mail, which, hopefully, should be free of 
> this issue.
> 
>  Please try out these two and let me know how they go.  Here's the one 
> liner against v2.6.12.
> 
> 
> diff --git a/drivers/scsi/libata-scsi.c b/drivers/scsi/libata-scsi.c
> --- a/drivers/scsi/libata-scsi.c
> +++ b/drivers/scsi/libata-scsi.c
> @@ -385,6 +385,7 @@ int ata_scsi_error(struct Scsi_Host *hos
>          * appropriate place
>          */
>         host->host_failed--;
> +       INIT_LIST_HEAD(&host->eh_cmd_q);
> 
>         DPRINTK("EXIT\n");
>         return 0;



  parent reply	other threads:[~2005-08-09 15:16 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
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 [this message]
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=42F8C8D0.2010603@pobox.com \
    --to=mlord@pobox.com \
    --cc=hare@suse.de \
    --cc=htejun@gmail.com \
    --cc=jgarzik@pobox.com \
    --cc=liml@rtr.ca \
    --cc=linux-ide@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;
as well as URLs for NNTP newsgroup(s).