Description of problem: When the system boots it finds the attached IDE DVD-ROM drive, e.g, hdc: TOSHIBA DVD-ROM SD-M1612, ATAPI CD/DVD-ROM drive it then has a long pause (~ 30 secs), after which it spits out the following message: hdc: no response (status = 0xfe) it then pauses again, after which it continues booting Version-Release number of selected component (if applicable): kernel-2.4.20-2.48 (in Phoebe 8.0.94) How reproducible: everytime. this happens when booting from the CD-ROM as well as from the hard drive after the operating system has been installed
Created attachment 90110 [details] lspci -v output of system with the problem see attached lspci -v output I'm not sure if the problem is due to a misrecognition of the Intel chipset. The motherboard is an Intel D845PTBT2, which has an Intel 845PE chipset, not the 845G/GL that is listed in lspci
Three questions 1. Does the same occur if there isa disc in the drive 2. If you tell it not to use DMA does the same happen ? 3. After the boot /pause what does hdparm -d /dev/hdc say
apologies, I appear to have been seeing things when I jotted down the initial output from the system. It isn't hdc that is having no response; rather, it appears to be the devices assigned to the Serial ATA RAID controller that is on this board. Note that I don't actually have any Serial ATA RAID drives attached. here is a snippet from dmesg that shows the problem: SiI3112 Serial ATA: IDE controller at PCI slot 02:06.0 PCI: Found IRQ 10 for device 02:06.0 PCI: Sharing IRQ 10 with 02:01.2 SiI3112 Serial ATA: chipset revision 1 SiI3112 Serial ATA: not 100% native mode: will probe irqs later ide2: MMIO-DMA at 0xe080dc00-0xe080dc07, BIOS settings: hde:pio, hdf:pio ide3: MMIO-DMA at 0xe080dc08-0xe080dc0f, BIOS settings: hdg:pio, hdh:pio hda: WDC WD1200JB-75CRA0, ATA DISK drive blk: queue c03caf40, I/O limit 4095Mb (mask 0xffffffff) hdc: TOSHIBA DVD-ROM SD-M1612, ATAPI CD/DVD-ROM drive hde: no response (status = 0xfe) hdg: no response (status = 0xfe) Is there a way to disable this timeout? It doesn't seem to affect the system, other than taking an extra minute or so to boot.
I dont see an easy way of removing it in this case.
Thanks for the bug report. However, Red Hat no longer maintains this version of the product. Please upgrade to the latest version and open a new bug if the problem persists. The Fedora Legacy project (http://fedoralegacy.org/) maintains some older releases, and if you believe this bug is interesting to them, please report the problem in the bug tracker at: http://bugzilla.fedora.us/