Re: [RESEND][2.6.15] New ATA error messages on upgrade to 2.6.15

[Robert Hancock <hancockr@shaw.ca>]

Kyle Moffett wrote:
>>> 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.

That would be a bug, no? Sounds dangerous to rely on that.

>  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:
> 
>> 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

That sounds fishy to me. If the controller is having trouble 
communicating with the drive causing BadCRC errors, it could easily 
cause such errors as the above as well.

-- 
Robert Hancock      Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/