Created attachment 23463 [details] System information for 2.6.30 and 2.6.31 Since updating to 2.6.31 my CD drive is no longer detected. The drive is still detected in version 2.6.30. The offending part of dmesg appears to be: Probing IDE interface ide1... ide1: no devices on the port Compared with 2.6.30's: Probing IDE interface ide1... hdc: PLEXTOR CD-R PX-W8432T, ATAPI CD/DVD-ROM drive hdc: host max PIO5 wanted PIO255(auto-tune) selected PIO4 hdc: MWDMA2 mode selected I have checked to make sure that the CD drive is set to master (it is), and have also tried kernel 2.6.32-rc5 with identical results. I cannot find any obvious differences in the kernel configurations that may be causing the problem. I have attached various logs / proc / config files that i think are appropriate. However, i cannot find much information that distinguishes them.
Created attachment 23464 [details] System info as above, but for 2.6.30, 2.6.31 and 2.6.32 Resubmitted with information for 2.6.32-rc4
Please don't create bugs in bugzilla when you're drunk.
(In reply to comment #2) > Please don't create bugs in bugzilla when you're drunk. He clearly isn't drunk, and you clearly are not as funny or clever as you think you are. This kind of arrogance and unprovoked rudeness should not be tolerated by any open source project, you drag the project your working for down as much as you do people's opinions of yourself.
Hi, does libata also fail to detect your drive? I.e., turn off CONFIG_IDE and enable CONFIG_PATA_VIA.
libata seems to find the drive fine -- abcde and mplayer are happy with it, vlc won't play it, but i suspect that's vlc's problem. I play around a bit tonight to see if the change is fine -- my drives all have different names now... Thanks.
(In reply to comment #5) > I play around a bit tonight to see if the change is fine -- my drives all > have > different names now... You can always have stable device names with udev: http://reactivated.net/writing_udev_rules.html
I had a problem which sounds very similar last week. I started a forum thread here (before I discovered this DB): http://www.linuxquestions.org/questions/linux-virtualization-90/2.6.31-kernel-guest-os-on-vmware-esx-3.5.0-780042/ The solution (for us) was to regress out this kernel change: http://kerneltrap.org/mailarchive/git-commits-head/2009/6/12/5948973 A more resilient fix might be to leave ide_probe_port() as-is but to fix ide_wait_not_busy() to return the last successful rc code (only returning -ENODEV if strictly no device is detected on the IDE port). I do not know what other repercussions such a fix might have however.
Same issue here on vmware server 1.08: The IDE cdrom is not detected anymore on kernel 2.6.32.9. I've reapplied the patch to 2.6.32.9 and will attach it here for easier access.
Created attachment 25337 [details] Fix for vmware IDE cdrom detection
See Documentation/SubmittingPatches for how to get patches accepted. The person handling IDE now is Dave Miller.
Thanks for the tip, Alan. The patch was meant as a hint or PoC, there must be a reason why the IDE controller is returning "no devices attached". Just added it for the IDE maintainer to get an idea what might be wrong. I also can't sign the patch as I didn't write it in the first place, can I? Reverting the commit mentioned above should do the same trick: http://kerneltrap.org/mailarchive/git-commits-head/2009/6/12/5948973 btw: I guess it's a good idea to add the original author as CC:.
Please always bring your upstream kernel problem with current upstream maintainer (I'm really sorry but I have absolutely no time to spend on investigating current IDE problems).
The 2.6.33 code looked fixed to me and I just verified it works again with 2.6.33.2 and VMware server 1.0.8. This issue is resolved in 2.6.33, please close it.