linux-kernel - Re: [2.6.30.5] Diagnosing an IDE lockup with SMART long tests

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <200909021351.33803.linux@rainbow-software.org>
Date:	Wed, 2 Sep 2009 13:51:32 +0200
From:	Ondrej Zary <linux@...nbow-software.org>
To:	Raphael Manfredi <Raphael_Manfredi@...ox.com>
Cc:	Robert Hancock <hancockrwd@...il.com>, linux-kernel@...r.kernel.org
Subject: Re: [2.6.30.5] Diagnosing an IDE lockup with SMART long tests

On Wednesday 02 September 2009, Raphael Manfredi 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?

What drive is that? Isn't that an IBM drive with buggy firmware?

-- 
Ondrej Zary
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/