Tejun Heo wrote: > 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'. Daniel Fraga and Sero's cases are different issue while I can't determine whether J. Taimr's case is limted on via chipset. So, I need more input to proceed. *Please* test and report the results. Thanks. -- tejun - To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
