sata_sil bug
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Quoted 4 lines · Justin Cormack
ata1: DMA timeout, stat
0x0
ATA: abnormal status0xD8on port0xF8807087
scsi0: ERROR on channel 0, id 0, lun 0, CDB:0x2a00 17 9b d9 80 00 00 20 00
Quoted 9 lines
Current sda: sense = 70 3
ASC= c ASCQ= 2
Raw sense data:0x700x000x030x000x000x000x000x060x000x000x000x000x0cend_request: I/O error, dev sda, sector 396089728
ATA: abnormal status0xD8on port0xF8807087
ATA: abnormal status0xD8on port0xF8807087
ATA: abnormal status0xD8on port0xF8807087
I was able to produce this error on my system too. It occured for me, when I compiled the ide interface of sil_3112 as a modul in to my kernel, although I was using the libata driver for my harddisks. I lost more then five times my sdb drive. After removing the ide modul, the system was rock stable again.
Tom
- --
- -------------------------------------------
protect your privacy - encrypt your mails
my key is: 0x2AA933B6
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFAoIZ+yat6ziqpM7YRAolbAJkBKrk8TYGzBUU2zemTuoFqWvdwOgCgyuQk kSy0Sgn7TPGWQ1XLn00rut0=
=VWPw
-----END PGP SIGNATURE-----
Quoted 16 lines · Thomas Maguin
Quoted 4 lines · Justin Cormack
ata1: DMA timeout, stat
0x0
ATA: abnormal status0xD8on port0xF8807087
scsi0: ERROR on channel 0, id 0, lun 0, CDB:0x2a00 17 9b d9 80 00 00 20 00Quoted 9 lines
Current sda: sense = 70 3
ASC= c ASCQ= 2
Raw sense data:0x700x000x030x000x000x000x000x060x000x000x000x000x0cend_request: I/O error, dev sda, sector 396089728
ATA: abnormal status0xD8on port0xF8807087
ATA: abnormal status0xD8on port0xF8807087
ATA: abnormal status0xD8on port0xF8807087
Quoted 4 lines
I was able to produce this error on my system too. It occured for me, when I compiled the ide interface of
sil_3112as a modul in to my kernel, although I was using the libata driver for my harddisks. I lost more then five times my sdb drive. After removing the ide modul, the system was rock stable again.
I definitely didnt have sii3112 as a module. I get this happening very very rarely. Still wonder if it might be the SiI3112 bug for which there is a watchdog workaround - any idea if this is the case Jeff? It is quite hard to repeat as it happened on a faulty disk and they tend to remap sectors eventually...
Justin