linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Lord <liml@rtr.ca>
To: Tejun Heo <htejun@gmail.com>, Jeff Garzik <jgarzik@pobox.com>,
	Alan Cox <alan@redhat.com>,
	IDE/ATA development list <linux-ide@vger.kernel.org>
Subject: Hard lockup with ata_piix 2.6.21.1: strange traceback, too
Date: Wed, 20 Jun 2007 17:12:13 -0400	[thread overview]
Message-ID: <4679982D.2030000@rtr.ca> (raw)

Hi guys,

I'm debugging a system here based on ICH7/ata_piix.
When we hot-pull a drive, it locks up solid.
That's fine, but I'd like to find/fix the lockup.

So as part of poking around, I rebuilt the kernel with frame pointers,
and inserted a WARN_ON(1) into ata_busy_sleep() to see who was calling it
just before things locked up. 

Here's the result:  http://rtr.ca/libata.png

Can anyone here make sense of that traceback??
Are we *really* recursing inside the EH code?

Thanks

             reply	other threads:[~2007-06-20 21:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-20 21:12 Mark Lord [this message]
2007-06-21  4:29 ` Hard lockup with ata_piix 2.6.21.1: strange traceback, too Tejun Heo

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=4679982D.2030000@rtr.ca \
    --to=liml@rtr.ca \
    --cc=alan@redhat.com \
    --cc=htejun@gmail.com \
    --cc=jgarzik@pobox.com \
    --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).