https://bugzilla.novell.com/show_bug.cgi?id=229547 ------- Comment #3 from teheo@novell.com 2007-01-15 02:47 MST ------- Created an attachment (id=112943) --> (https://bugzilla.novell.com/attachment.cgi?id=112943&action=view) libata PATA ATAPI detection debug patch Can you give a shot at 2.6.20-rc5 (the kernel.org vanilla devel kernel) with the attached patch applied? This is from upstream debugging effort. I'm copying the original post to other bug reporters. If patching and testing vanilla kernel is too much work for you, you can just wait. ---------8<------------ Hello, all. Many people have been reporting libata PATA ATAPI detection problem. In many but not all cases, the ATAPI device was occupying the slave slot while a disk drive occupies the master slot. Based on that and J. Taimr's nullify freeze on via fix, I made a cocktail patch which contained four different fixes and it seemed to have fixed the problem for (at least) several people, but the reports are not all consistent. The attached patches contain the same four fixes but has a selector parameter to enable each fix separately. Both are equivalent but using 2.6.20-rc5 is recommended to rule out detection problems fixed by polling IDENTIFY. If your libata driver is compiled into the kernel, add 'libata.debug_cocktail=N' to your kernel parameter. If you compile libata.ko as module, add 'debug_cocktail=N' module parameter to the module parameter. e.g. 'modprobe libata.ko debug_cocktail=1'. Please test 0: nothing 1: common PIO mask between devices sharing a channel 2: force PIO0 (DMA mode is unaffected) 4: clear NIEN on both devices 8: make ata_bmdma_freeze() nill If none of above works, try 5, 9, then 6, 10. Please test each option and report the result. It's best if you can include dmesg's for each value but if you can't get the dmesg because boot doesn't complete, just reporting the option doesn't work suffices. Also, please don't forget to attach the result of 'lspci -nnvvv'. Thanks for your patience. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.