I get the following messages from the kernel after coming out of
suspend mode on my notebook, running 2.1.124:
hda: multwrite_intr: status=0x51 { DriveReady SeekComplete Error }
hda: multwrite_intr: error=0x04 { DriveStatusError }
hda: multwrite_intr: status=0x51 { DriveReady SeekComplete Error }
hda: multwrite_intr: error=0x04 { DriveStatusError }
hda: multwrite_intr: status=0x51 { DriveReady SeekComplete Error }
hda: multwrite_intr: error=0x04 { DriveStatusError }
hda: multwrite_intr: status=0x51 { DriveReady SeekComplete Error }
hda: multwrite_intr: error=0x04 { DriveStatusError }
ide0: unexpected interrupt, status=0xd0, count=1
ide0: reset: success
After this happens once, it does not happen again for subsequent
suspend/resume actions, until next reboot. Apart from slowly filling up
my syslogs, and a couple of seconds delay, it does not seem to be harmful.
I don't recall this happening with 2.1.115, and it certainly does not
happen with 2.0.35.
Anyone else getting this? If there is anything more I can do to help
track this down, let me know. Linux x86 2.1.124, compiled with egcs-1.1.
Philip Chong
pchong@eecs.berkeley.edu
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/