https://bugzilla.novell.com/show_bug.cgi?id=375836 User bjorn.helgaas@hp.com added comment https://bugzilla.novell.com/show_bug.cgi?id=375836#c50 --- Comment #50 from Bjorn Helgaas <bjorn.helgaas@hp.com> 2008-06-16 14:57:04 MDT --- (In reply to comment #48 from Thomas Renninger)
I wonder what the easiest way to test this is... Parallel driver must get loaded before disk drivers, right?
Yes; this problem only occurs when parport_pc is loaded before the IDE driver.
Should compiling in parallel driver work?
Yes, I think it should work if you compile in the parport_pc driver because PNP drivers are initialized before PCI drivers. But all you need to do is rebuild the kernel with the patch and use the identical drivers. (Of course, you might have to fiddle with the kernel version string to make it match the drivers and bypass any module signature checking you do.)
While such a sanity check (provided by your patch) probably is a good idea, I still think device specific IRQ preference could not only fix this one, but also prevent running into other similar pits in the future. Bjorn, could you have a short look at the updated patch I am going to attach. It's rather the same, but has more devices added and provides a possibility to add several preferred irqs to one device (not sure whether this is overdosed). This should lower the risk of running into similar bugs in the future significantly.
I don't think your patch is sufficient to fix this problem. Your patch will make us try IRQ 7 first for a PNP0400/PNP0401 device, but if IRQ 7 happens to be busy for some reason, there's still nothing to prevent us from assigning IRQ 14 to it. That said, I am intrigued by your patch, and in some ways it makes more sense than the current xtab[] table, since I have no idea how the xtab[] order was derived. -- 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.