linux-kernel - Re: Timeouts on ICH7 PATA drive with ata_piix; ide

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: <45C5AD27.5080008@gmail.com>
Date:	Sun, 04 Feb 2007 18:53:43 +0900
From:	Tejun Heo <htejun@...il.com>
To:	Keenan Pepper <keenanpepper@...il.com>
CC:	linux-kernel@...r.kernel.org
Subject: Re: Timeouts on ICH7 PATA drive with ata_piix; ide_generic works
 perfectly

Keenan Pepper wrote:
> I just upgraded the kernel on my System76 Gazelle laptop (basically an
> ASUS Z62FP without the Microsoft tax) and the hard drive began
> freezing every few minutes. I blacklisted ata_piix and the problem
> went away, so that really narrows down where the bug has to be. Here's
> the relevant part of the dmesg:
> 
> [  924.000000] ata1.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2
> frozen
> [  924.000000] ata1.01: cmd a0/01:00:00:00:00/00:00:00:00:00/b0 tag 0
> cdb 0x25 data 8 in
> [  924.000000]          res 40/00:03:00:00:00/00:00:00:00:00/b0 Emask
> 0x4 (timeout)
> [  931.004000] ata1: port is slow to respond, please be patient (Status
> 0xd0)
> [  954.028000] ata1: port failed to respond (30 secs, Status 0xd0)

It seems that something is issuing READ_CAPACITY to your drive or trying
to open the device triggering media revalidation periodically and your
drive doesn't like it.  Your harddisk is sharing the channel with the
ODD so it can't be accessed till the command times out and the ODD gets
recovered.

* Does putting in a readable CD or DVD make any difference?

* Does the problem occur in single mode where no HAL or whatever is running?

PS: It *really* helps if you include full dmesg including the detection
messages and whole error messages when reporting bugs.  If you need
snippet of it to explain, copy that part but keep the whole dmesg at the
end.  Kernel developers are usually pretty good at filtering useful info
from tons of kernel messages.

-- 
tejun
-
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/