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  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]
Date:	Sun, 30 May 2010 12:40:04 -0600
From:	Robert Hancock <>
To:	Thomas Fjellstrom <>
Subject: Re: via 8237 sata errors

On 05/29/2010 08:46 PM, Thomas Fjellstrom wrote:
> I'm getting a rather nasty set of messages from dmesg when trying to use
> a couple SATA II WD 2TB Green drives with an older system (via 8237 based).
> They seem to work fine on a newer p35 based system.


> [  283.308963] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
> [  283.309007] ata2.00: BMDMA stat 0x4
> [  283.309045] ata2.00: failed command: READ DMA
> [  283.309089] ata2.00: cmd c8/00:08:08:08:30/00:00:00:00:00/e0 tag 0 dma 4096 in
> [  283.309091]          res 41/04:00:08:08:30/00:00:00:00:00/e0 Emask 0x1 (device error)
> [  283.309171] ata2.00: status: { DRDY ERR }
> [  283.309207] ata2.00: error: { ABRT }
> [  283.324886] ata2.00: configured for UDMA/133
> [  283.324904] ata2: EH complete

It's not really clear why the drive is returning command aborted on a 
read, there's no other error bits to indicate an uncorrectable error or 
a CRC error. Is it only the one drive that's giving the errors?
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists