Skip to contentSkip to conversation

[2.6.15] New ATA error messages on upgrade to 2.6.15

PATCH RESEND Robert Hancock 3 participants 3 messages Apr 1, 2006 5 messages not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

#5 lore raw
Quoted 2 lines · Kyle Moffett

hdg: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdg: dma_intr: error=0x84 { DriveStatusError BadCRC }

Hmm, are these new? Sure you don't have a bad IDE cable?

Signature · 3 lines
Robert Hancock      Saskatoon, SK, Canada
To email, remove "nospam" from [email protected]
Home Page: http://www.roberthancock.com/
#6 lore raw
Quoted 5 lines · Robert Hancock
Quoted 2 lines · Kyle Moffett

hdg: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdg: dma_intr: error=0x84 { DriveStatusError BadCRC }

Hmm, are these new? Sure you don't have a bad IDE cable?

Oh, those aren't the errors I'm worried about; I've had those for a while and they're harmless. Those are due to the kernel running the IDE controller at a higher-than-supported speed. It gets errors for a couple seconds and automatically drops the bus down to a lower and safer speed. The cable's aren't bad, I've tried at least 6 different 80-conductor cables that all work fine in other systems. The errors I _am_ worried about are these:

Quoted 8 lines
Mar 28 03:15:13 penelope kernel: hdi: status timeout: status=0xd0 { Busy }
Mar 28 03:15:13 penelope kernel: PDC202XX: Secondary channel reset.
Mar 28 03:15:13 penelope kernel: hdi: no DRQ after issuing MULTWRITE_EXT
Mar 28 03:15:13 penelope kernel: ide4: reset: success
Mar 28 03:30:13 penelope kernel: hdi: status timeout: status=0xd0 { Busy }
Mar 28 03:30:13 penelope kernel: PDC202XX: Secondary channel reset.
Mar 28 03:30:13 penelope kernel: hdi: no DRQ after issuing MULTWRITE_EXT
Mar 28 03:30:13 penelope kernel: ide4: reset: success

Cheers,
Kyle Moffett

#7 lore raw
Quoted 3 lines · Kyle Moffett

IDE controller at a higher-than-supported speed. It gets errors for a couple seconds and automatically drops the bus down to a lower and safer speed.

This indicates a problem somewhere. The drives and controller report their speed capabilities and if they can't meet the ones they are reporting something is very wrong somewhere and this is most definitely the first thing to debug.