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: <51f3faa70909021724v45d2902ewdb10d5f4a188f2be@mail.gmail.com>
Date:	Wed, 2 Sep 2009 18:24:17 -0600
From:	Robert Hancock <hancockrwd@...il.com>
To:	Raphael Manfredi <Raphael_Manfredi@...ox.com>
Cc:	linux-kernel@...r.kernel.org, linux-ide@...r.kernel.org
Subject: Re: [2.6.30.5] Diagnosing an IDE lockup with SMART long tests

On Wed, Sep 2, 2009 at 8:52 AM, Raphael
Manfredi<Raphael_Manfredi@...ox.com> wrote:
> Quoting Robert Hancock:
> : 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.
>
> Sure, I'm using:
>
>        smartctl -t long /dev/sda
>
> to launch the SMART test.
>
> Here's the requested dmesg output:

Is it always this drive that's failing? I see there's a second of the
same model, does it show the same behavior?

> ata1.00: ATA-6: HDS722512VLAT80, V33OA60A, max UDMA/100
> ata1.00: 241254720 sectors, multi 16: LBA48

If only that particular drive shows this problem, then I would start
to suspect a hardware fault with that drive. The fact that it fails
with both IDE and libata (and with ata_piix, which is a really
commonly used and tested libata driver) rather points in that
direction. Errors normally shouldn't lock up the machine, except that
if the drive is doing bad things with IORDY for example, it can
basically stall the machine forever and there's nothing the kernel can
do about it..
--
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/