https://bugzilla.kernel.org/show_bug.cgi?id=16382 --- Comment #5 from Rick Stockton <rickstockton@xxxxxxxxxxxxxxxxxxxxx> 2010-07-14 19:50:08 --- OK! There's a comment "check this" in the initialization code of (at line 843 within the current version of pata_hpt37x, V0.6.15), and that made me suspicious. But, per your suggestion, I rebuilt initrd with BOTH drivers included -- and I installed hpt37x first. This worked exactly as as you said it should: hpt37x was assigned to handle the interrupt, but it bailed out immediately. hpt3x2n was tried next, and was able to grab the interface. So please feel free to close this as 'invalid'. There's one TINY nitpick which I saw in pata_3x2n, but it would be a different bug (if someone wants to bother): Source code lines 536-537 (in the current version, V0.3.10)are as follows, 536 printk(KERN_INFO "pata_hpt37x: bus clock %dMHz, using 66MHz DPLL.\n", 537 pci_mhz); And you saw this in my clip from dmesg (in the bug description, above). Driver "pata_3x2n" should not print a message listing itself as "pata_hpt37x"; there's an old copy/paste mistake in there. THANKS for hand-holding the newby, you've been awesome. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug. -- 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
