http://bugzilla.kernel.org/show_bug.cgi?id=8956
------- Comment #54 from [EMAIL PROTECTED] 2007-10-15 23:41 ------- Hi, Arjan Thanks for your info. Now there is another problem about your system. When booted with acpi=off, the system reports that nobody cares IRQ 11. >From the comment of #50, #19 and #20, it is doubted that the problem is caused by the BIOS bug( Ethernet PCI interrupt routing). 1. When acpi is enabled, ethernet PCI interrupt is routed to Pin 23 of I/O APIC through LINK device(LSA0) and IRQ number is 16. It seems that it can work well. 2. When booted with acpi=off noapic, ethernet PCI interrupt is routed to Pin 11 of I8259(defined directly by PCI device). It seems that eth0 can work well. 3. When booted with acpi=off, ethernet PCI interrupt is routed to Pin 15 of I/O APIC accordint to the definition in MPS table(defined by BIOS) and IRQ 15 is enabled. But the route is uncorrect and ethernet is still connected with Pin 11 of I/O APIC . After ethernet device is enabled, IRQ 15 can't receive the interrupt and IRQ 11 can't process the interrupts triggered by ethernet device. So the system will report that IRQ 11 is cared by nobody. Based on the above analysis the problem is caused by the Bug of BIOS. So we won't fix this problem. The patch about the timer override will be soon available. Thanks. -- 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: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ acpi-bugzilla mailing list acpi-bugzilla@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla
