linux-kernel - Re: 2.6.20 SATA error

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: <45E59C07.7020902@dbservice.com>
Date:	Wed, 28 Feb 2007 16:13:11 +0100
From:	Tomas Carnecky <tom@...ervice.com>
To:	Gerhard Mack <gmack@...erfire.net>
CC:	Robert Hancock <hancockr@...w.ca>, linux-kernel@...r.kernel.org
Subject: Re: 2.6.20 SATA error

Gerhard Mack wrote:
> ata1.00: configured for UDMA/100
> [...]
> ata1.00: configured for UDMA/66
> [...]
> ata1.00: configured for UDMA/44
> [...]
> ata1.00: configured for UDMA/33
> [...]
> ata1.00: configured for UDMA/25
> [...]
> ata1.00: configured for UDMA/16
> [...]
> ata1.00: configured for PIO4

I have the same problem, though it appears randomly. It seems like the 
chances for this happening are bigger if I do heavy disk I/O. The only 
way to fix that is to shut down the computer and wait a few seconds 
before rebooting (if I don't wait, the problem doesn't go away). I 
bought new harddrives, so it's most likely not caused by the drives, I 
also tried putting the drives onto a different controller (I have four 
on-board SATA controller and two harddrives), that didn't help either, 
so I suspect its the cable - SATA cables are very error-prone, I don't 
trust them as they don't hold that tightly in the socket.

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