http://bugzilla.kernel.org/show_bug.cgi?id=6654
------- Comment #12 from [EMAIL PROTECTED] 2008-01-02 13:33 ------- I like your theory that this is caused by a broken BIOS. However, I would like to try to work around the problem in the kernel rather than just rejecting the bug report. I'm not sure we can tell yet whether a) the LNKC device reports "3 4 6 7 10 11 12" as possible IRQs but is in fact hardwired to IRQ 5, or b) 0000:00:10.4[C] is connected directly to IRQ 5 rather than to LNKC. The kernel thinks Paul's gameport device (0000:00:0c.0[A]) is also connected to LNKC. If /proc/interrupts shows gameport interrupts on IRQ 11, then I think it's more likely that (b) is the problem. Either way, I think it's possible to work around this. Paul, can you boot with no options and try out the gameport to see where its interrupts are going? Please also attach the dmidecode output, so if we write a workaround, we can make it specific to this motherboard. -- Configure bugmail: http://bugzilla.kernel.org/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. ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ acpi-bugzilla mailing list acpi-bugzilla@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla
