http://bugzilla.kernel.org/show_bug.cgi?id=7699

[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |acpi-
                   |                            |[EMAIL PROTECTED]
                   |                            |et
              Owner|acpi_config-                |[EMAIL PROTECTED]
                   |[EMAIL PROTECTED]          |
                   |bugs.osdl.org               |
             Status|NEW                         |ASSIGNED
            Summary|irq9: nobody cared (try     |irq9: nobody cared - VIA
                   |booting with the "irqpoll"  |KT400 - PIC-mode
                   |option)                     |



------- Additional Comments From [EMAIL PROTECTED]  2006-12-17 18:46 -------
Please attach the full dmesg -s64000 (or serial console log
with "debug" enabled)and /proc/interrupts of the latest working kernel,
and the first failing kernel (failing kernel will need irqpoll to boot)

Confused about the comment regarding reverting patch in bug #7601 --
as that patch is already reverted in 2.6.19.1 -- it appeared only
in 2.6.19.

acpidump shows that this machine has an IOAPIC:

ACPI: APIC (v001 ASUS   A7V600-X 0x42302e31 MSFT 0x31313031) @ 0x(nil)
ACPI: IOAPIC (id[0x02] address[0xfec00000] global_irq_base[0x0])
ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl edge)
ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 low level)
ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Length 90 OK
Checksum OK

however, the 2.6.16 /proc/interrupts shows PIC mode
is being used, and the config for 2.6.19.1
suggests that it isn't being used there either.

While this appears to be a PIC-mode regression, and worthy of
being debugged, it would also be interesting to try IOAPIC
mode on the old and new kernel as well -- simple to enble
this with CONFIG_SMP.  As IOAPIC mode is preferable if it works.
The MADT shows that the APIC-mode entries are all hard-coded
so from an ACPI point of view, it should be very simple
and reliable -- and the only obstacle might be the dreaded VIA quirk.


------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
You are on the CC list for the bug, or are watching someone who is.

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
acpi-bugzilla mailing list
acpi-bugzilla@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla

Reply via email to