VIA VT6421 SATA card still seems to crash many systems
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
I am using a VIA VT6421 SATA card on a 64bit Ubuntu/Natty
Upon accessing a DVD drive connected to the card, the whole server crashes almost immediately. Here the messages I get from the kernel upon the crash:
Aug 11 20:47:13 hostname kernel: [ 728.573496] ata3.00: exception Emask 0x12 SAct 0x0 SErr 0x1380500 action 0x6
Aug 11 20:47:13 hostname kernel: [ 728.573501] ata3.00: BMDMA stat 0x5
Aug 11 20:47:13 hostname kernel: [ 728.573505] ata3: SError: { UnrecovData Proto 10B8B Dispar BadCRC TrStaTrns }
Aug 11 20:47:13 hostname kernel: [ 728.573511] sr 2:0:0:0: [sr1] CDB: Read(10): 28 00 00 00 00 00 00 00 02 00
Aug 11 20:47:13 hostname kernel: [ 728.573528] ata3.00: cmd a0/01:00:
Aug 11 20:47:13 hostname kernel: [ 728.573530] res 51/40:03:
Aug 11 20:47:13 hostname kernel: [ 728.573534] ata3.00: status: { DRDY ERR }
Aug 11 20:47:13 hostname kernel: [ 728.573544] ata3: hard resetting link
Aug 11 20:47:14 hostname kernel: [ 728.920055] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Aug 11 20:47:14 hostname kernel: [ 728.980238] ata3.00: configured for UDMA/100
Aug 11 20:47:14 hostname kernel: [ 728.981398] ata3: EH complete
Aug 11 20:47:14 hostname kernel: [ 729.274406] ata3.00: exception Emask 0x12 SAct 0x0 SErr 0x1380500 action 0x6
Aug 11 20:47:14 hostname kernel: [ 729.274411] ata3.00: BMDMA stat 0x5
Aug 11 20:47:14 hostname kernel: [ 729.274416] ata3: SError: { UnrecovData Proto 10B8B Dispar BadCRC TrStaTrns }
Aug 11 20:47:14 hostname kernel: [ 729.274422] sr 2:0:0:0: [sr1] CDB: Read(10): 28 00 00 00 00 22 00 00 06 00
Aug 11 20:47:14 hostname kernel: [ 729.274439] ata3.00: cmd a0/01:00:
Aug 11 20:47:14 hostname kernel: [ 729.274441] res 51/40:03:
Aug 11 20:47:14 hostname kernel: [ 729.274445] ata3.00: status: { DRDY ERR }
Aug 11 20:47:14 hostname kernel: [ 729.274455] ata3: hard resetting link
Aug 11 20:47:14 hostname kernel: [ 729.620064] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Aug 11 20:47:14 hostname kernel: [ 729.680248] ata3.00: configured for UDMA/100
Aug 11 20:47:14 hostname kernel: [ 729.681247] ata3: EH complete
Aug 11 20:47:14 hostname kernel: [ 729.768369] ata3.00: exception Emask 0x12 SAct 0x0 SErr 0x1380500 action 0x6
Aug 11 20:47:14 hostname kernel: [ 729.768374] ata3.00: BMDMA stat 0x5
Aug 11 20:47:14 hostname kernel: [ 729.768379] ata3: SError: { UnrecovData Proto 10B8B Dispar BadCRC TrStaTrns }
Aug 11 20:47:14 hostname kernel: [ 729.768385] sr 2:0:0:0: [sr1] CDB: Read(10): 28 00 00 00 01 00 00 00 02 00
Aug 11 20:47:14 hostname kernel: [ 729.768402] ata3.00: cmd a0/01:00:
Aug 11 20:47:14 hostname kernel: [ 729.768403] res 51/40:03:
Aug 11 20:47:14 hostname kernel: [ 729.768414] ata3.00: status: { DRDY ERR }
Aug 11 20:47:14 hostname kernel: [ 729.768431] ata3: hard resetting link
Aug 11 20:47:15 hostname kernel: [ 730.110058] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Aug 11 20:47:15 hostname kernel: [ 730.170231] ata3.00: configured for UDMA/100
Aug 11 20:47:15 hostname kernel: [ 730.170847] ata3: EH complete
Aug 11 20:47:15 hostname kernel: [ 730.298920] ata3.00: limiting speed to UDMA/66:PIO4
Aug 11 20:47:15 hostname kernel: [ 730.298928] ata3.00: exception Emask 0x12 SAct 0x0 SErr 0x1380500 action 0x6
Aug 11 20:47:15 hostname kernel: [ 730.298931] ata3.00: BMDMA stat 0x4
Aug 11 20:47:15 hostname kernel: [ 730.298935] ata3: SError: { UnrecovData Pr
The log stops there. There seem to be others with this problem:
https:/
http://
http://
http://
Changed in linux-lts-backport-natty (Ubuntu): | |
status: | New → Confirmed |
affects: | linux-lts-backport-natty (Ubuntu) → linux (Ubuntu) |
#724421 seems to be a duplicate of this bug (or the other way round...)
Please note that in my case the issue is not linked to Western Digital hard drives - but I also seem to be the only one attaching a DVD drive to this card. Additionally, the crash is always reproducible. It seems to have nothing to do with high transfer speeds as reported by other people.