Description of problem: System : PE2650 BIOS : A20 H/W config : 2* 2.4 Ghz /533FSB/12GB memory /PERC3Di/PERC4DC/Intel1000MT/2*BCM570X/AIC-39160 While running the "newburn" system stress utility (from Cerberus), the following messages are flashing on console: cdrom_pc_intr: The drive appears confused (ireason = 0x01) cdrom_pc_intr, write: dev hda: flags = REQ_STARTED REQ_PC REQ_QUIET sector 0, nr/cnr 0/0 bio 00000000, biotail 00000000, buffer 00000000, data 00000000, len cdb: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 hda: cdrom_pc_intr: The drive appears confused (ireason = 0xd0) cdrom_pc_intr: The drive appears confused (ireason = 0x01) cdrom_pc_intr: The drive appears confused (ireason = 0x01) (and so on...) In spite of these messages, the CD-ROM drive is working fine. The CD drive was replaced with a new one to eliminate a chance of a hardware error. We've also seen this message on a PE2600: "hda: cdrom_pc_intr: The drive appears confused (ireason = 0x01)" which printed several times, then this- "hda: packet command error: status=0xd0 { Busy }" "ide: failed opcode was 100" It sounds like this may not happen on RHEL4 beta1. I'll attach /var/log/messages, the console while running newburn, and the contents of /proc/ide/hda/settings. Version-Release number of selected component (if applicable): How reproducible: Every time Steps to Reproduce: 1. Install and run "newburn" stress program 2. Watch screen for error messages 3. Actual results: we get error messages listed above Expected results: no error messages Additional info:
Created attachment 107555 [details] messages file from failing system
Created attachment 107556 [details] /proc/ide/hda/settings file contents
Created attachment 107557 [details] console on failing system
Does this occur with hal disabled ?
It turns out that this isn't easy to reproduce. I haven't actually been able to reproduce this myself at all--it was just reported to me after a couple of failures were seen. ...What is hal, though? And, how do I disable it?
Changing the title to reflect the Update in which a fix for this issue has been committed (from RH) or being tracked for..
You can close this issue. We have closed it from this side, as we were unable to reproduce it. Thanks, Stuart
thanks. closing.