From: Tejun Heo <htejun@gmail.com>
To: Mark Lord <liml@rtr.ca>
Cc: Jeff Garzik <jgarzik@pobox.com>, Alan Cox <alan@redhat.com>,
IDE/ATA development list <linux-ide@vger.kernel.org>
Subject: Re: Hard lockup with ata_piix 2.6.21.1: strange traceback, too
Date: Thu, 21 Jun 2007 13:29:12 +0900 [thread overview]
Message-ID: <4679FE98.4040602@gmail.com> (raw)
In-Reply-To: <4679982D.2030000@rtr.ca>
Mark Lord wrote:
> 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?
It looks like SCSI EH -> piix_sata_error_handler -> ata_eh_recover ->
ata_std_softreset -> ata_std_prereset -> ata_busy_sleep with lots of
bogus entries inbetween.
--
tejun
prev parent reply other threads:[~2007-06-21 4:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-20 21:12 Hard lockup with ata_piix 2.6.21.1: strange traceback, too Mark Lord
2007-06-21 4:29 ` Tejun Heo [this message]
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=4679FE98.4040602@gmail.com \
--to=htejun@gmail.com \
--cc=alan@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.