Bug 7242 - "hdc: ide timeout" errors sometimes occur after inserting CD
Summary: "hdc: ide timeout" errors sometimes occur after inserting CD
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: kernel
Version: 6.1
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Michael K. Johnson
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 1999-11-23 02:23 UTC by pierre
Modified: 2008-05-01 15:37 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2000-08-22 17:33:08 UTC

Attachments (Terms of Use)

Description pierre 1999-11-23 02:23:34 UTC
Occasionally (once a month maybe) after inserting an audio CD in my cdrom
drive the CDplayer "hangs". The X display enters a cycle in which
everything is frozen (no keyboard response, no mouse motion) for about 20
sec., then things look normal for 20 sec., then back to the frozen state
and so on. This makes the system unusable. Using CTL-ALT-F1 brings me to
the console, and then every few seconds I see a message (sorry, I am
quoting from memory) like "hdc: ide timeout ... ". Usually I then reboot.
Even though things other than the CD appear normal, upon booting the system
claims that the shutdown was not clean and feels the need to fix the file

I had this problem before with RedHat 6.0; again, this only showed up maybe
once a month and I can't offer a more accurate error log at this point. I
am using an AMD K6-III 450MHz with a bcm VP1541 motherboard purchased June
'99 running BIOS version 1.05 and an ACER CD ROM model 640A with a
SoundBlaster 16 card. Normally all this works just great. I do lots of
compiling, image processing etc. and nothing else seems flaky on my system,
so I'm thinking maybe this is a bug with the ide cdrom driver.

Comment 1 Cristian Gafton 2000-01-04 22:25:59 UTC
Assigned to dledford

Comment 2 Alan Cox 2000-08-22 17:33:06 UTC
It actually sounds more like the cd-rom drive firmware crashing. That would
explain the
pattern better. Does 6.2 show this ?

Comment 3 Alan Cox 2000-09-15 18:11:27 UTC
No response. Im assuming the newer kernels fixed it or its the drive. If you
read this and have the same problem re-open it

Note You need to log in before you can comment on or make changes to this bug.