linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: Mark Lord <mlord@pobox.com>
Cc: Jeff Garzik <jgarzik@pobox.com>, Mark Lord <liml@rtr.ca>,
	IDE/ATA development list <linux-ide@vger.kernel.org>,
	hare@suse.de
Subject: Re: libata total system lockup fix
Date: Fri, 19 Aug 2005 12:21:47 +0900	[thread overview]
Message-ID: <4305504B.7080201@gmail.com> (raw)
In-Reply-To: <43052C03.7060306@pobox.com>


  Hi, Mark.

Mark Lord wrote:
> After a week of further experience with this patch,
> I regretfully inform one and all that it does not
> entirely fix the lockups.
> 
> My system has experienced three of them during the
> past 24 hours.. after many days without.

  Oh.. crap.

> I'm now reverting to the original "broken" patch
> that keeps my system alive.
> 
> Cheers!

  I've been trying to reproduce your lockup here, but haven't succeeded 
yet.  I'm currently doing multiple "while true; do cat /dev/sr0; done", 
bonnie, raw random IOs (latter two are to give some randomness to test 
condition).

  I'm also digging code to discover how exactly the lockup loop occurs. 
  My lockup was between scsi_softirq and scsi_eh_scmd_add (EIP jumped 
between the two functions), and I orginally assumed adding eh_entry to 
corrupt eh_cmd_q screwed local_q iteration in scsi_softirq.  And as 
clearing eh_cmd_q solved my problem, I didn't look into it further.

  If possible, can you please hook up your notebook to a serial console 
and, when lockup occurs (with or without INIT_LIST_HEAD one liner), dump 
call trace by ctrl-alt-sysrq-p multiple times (10times across 5secs 
should do, I think) to verify that we're looking at the same problem? 
It would be best if I can find a way to reproduce it here, but the busy 
loop has been running for two hours now and nothing happened.  :-(

  Thanks.

-- 
tejun

  reply	other threads:[~2005-08-19  3:21 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
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 [this message]
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=4305504B.7080201@gmail.com \
    --to=htejun@gmail.com \
    --cc=hare@suse.de \
    --cc=jgarzik@pobox.com \
    --cc=liml@rtr.ca \
    --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).