From: Robert Hancock <hancockrwd@gmail.com>
To: Raphael Manfredi <Raphael_Manfredi@pobox.com>
Cc: linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: [2.6.30.5] Diagnosing an IDE lockup with SMART long tests
Date: Wed, 2 Sep 2009 08:42:20 -0600 [thread overview]
Message-ID: <51f3faa70909020742g19007084j19a0ed071aaeffdf@mail.gmail.com> (raw)
In-Reply-To: <20090902111927.GA4590@chram.org>
On Wed, Sep 2, 2009 at 5:19 AM, Raphael
Manfredi<Raphael_Manfredi@pobox.com> wrote:
> Quoting Robert Hancock:
>> It's most likely a bug in the IDE code somewhere, but realistically the
>> most effective course of action would likely be to switch from the old IDE
>> drivers and use libata instead. The IDE code doesn't receive that much
>> testing these days, and it's really hard to debug (as you've seen, the
>> debugging output is rather atrocious).
>
> I gave it a shot anyway. Converting to PATA was surprisingly straighforward.
>
> Anyway, I now get the following when running SMART long tests on /dev/sda:
>
> ata1: lost interrupt (Status 0x50)
>
> And the machine hangs... So I'm back to square one.
> How do I prevent lockups on the system when running SMART long tests?
Can you post what particular command you're running to run the SMART
test, and also the full dmesg output from bootup? Also CCing
linux-ide.
next prev parent reply other threads:[~2009-09-02 14:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-01 16:27 Raphael Manfredi
2009-09-02 4:26 ` Robert Hancock
2009-09-02 6:07 ` Raphael Manfredi
2009-09-02 11:19 ` Raphael Manfredi
2009-09-02 11:51 ` Ondrej Zary
2009-09-02 11:59 ` Raphael Manfredi
2009-09-02 14:42 ` Robert Hancock [this message]
2009-09-02 14:52 ` Raphael Manfredi
2009-09-03 0:24 ` Robert Hancock
2009-09-04 5:35 ` Raphael Manfredi
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=51f3faa70909020742g19007084j19a0ed071aaeffdf@mail.gmail.com \
--to=hancockrwd@gmail.com \
--cc=Raphael_Manfredi@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®