2.4.27-rc1 reintroduced x86-64 2x timer bug

From: Mikael Pettersson (mikpe_at_csd.uu.se)
Date: 06/20/04

  • Next message: Andi Kleen: "Re: Opteron bug" 
    Date:	Sun, 20 Jun 2004 13:44:34 +0200 (MEST)
To: ak@suse.de

    2.4.27-rc1 reintroduced the "2x timer" ACPI bug on
    x86-64 which was fixed previously in 2.4.27-pre3.

    dmesg diff below between pre6 (ok) and rc1 (buggy).

    /Mikael

    --- dmesg-amd64-2.4.27-pre6 2004-06-20 13:12:48.000000000 +0200
    +++ dmesg-amd64-2.4.27-rc1 2004-06-20 13:28:53.000000000 +0200
    @@ -38,9 +38,6 @@
     IOAPIC[0]: apic_id 2, version 3, address 0xfec00000, IRQ 0-23
     ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
     ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 low level)
    -ACPI: IRQ0 used by override.
    -ACPI: IRQ2 used by override.
    -ACPI: IRQ9 used by override.
     Using ACPI (MADT) for SMP configuration information
     Kernel command line: BOOT_IMAGE=linux auto
     Initializing CPU#0
    @@ -61,7 +58,7 @@
     testing NMI watchdog ... OK.
     ENABLING IO-APIC IRQs
     init IO_APIC IRQs
    - IO-APIC (apicid-pin) 2-0, 2-16, 2-17, 2-18, 2-19, 2-20, 2-21, 2-22, 2-23 not connected.
    + IO-APIC (apicid-pin) 2-16, 2-17, 2-18, 2-19, 2-20, 2-21, 2-22, 2-23 not connected.
     ..TIMER: vector=0x31 pin1=2 pin2=-1
     Using local APIC timer interrupts.
     Detected 12.500 MHz APIC timer.
    @@ -98,7 +95,7 @@
     00:00:05[D] -> 2-19 -> vector 0xd1 -> IRQ 19 level low
     00:00:10[A] -> 2-21 -> vector 0xd9 -> IRQ 21 level low
     00:00:12[A] -> 2-23 -> vector 0xe1 -> IRQ 23 level low
    -number of MP IRQ sources: 15.
    +number of MP IRQ sources: 18.
     number of IO-APIC #2 registers: 24.
     testing the IO APIC.......................
     
    @@ -111,7 +108,7 @@
     ....... : IO APIC version: 0003
     .... IRQ redirection table:
      NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect:
    - 00 000 00 1 0 0 0 0 0 0 00
    + 00 001 01 0 0 0 0 0 1 1 31
      01 001 01 0 0 0 0 0 1 1 39
      02 001 01 0 0 0 0 0 1 1 31
      03 001 01 0 0 0 0 0 1 1 41
    @@ -136,7 +133,7 @@
      16 001 01 1 1 0 1 0 1 1 C1
      17 001 01 1 1 0 1 0 1 1 E1
     IRQ to pin mappings:
    -IRQ0 -> 0:2
    +IRQ0 -> 0:0-> 0:2
     IRQ1 -> 0:1
     IRQ3 -> 0:3
     IRQ4 -> 0:4
    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  • Next message: Andi Kleen: "Re: Opteron bug"

    Relevant Pages

    • Re: Fixes for nforce2 hard lockup, apic, io-apic, udma133 covered
      ... Thanks Maciej for your response. ... What if we had a really fast cpu or is it restricted solely to the timer irq?? ... Fortunately only the timer IRQ ...
      (Linux-Kernel)
    • Intermittent panic at boot on x86-64
      ... I noticed that during the single processor boot it also has timer problems: ... usbcore: registered new driver usbfs ... PCI->APIC IRQ transform: -> 19 ... USB Serial support registered for Generic ...
      (Linux-Kernel)
    • Re: + stupid-hack-to-make-mainline-build.patch added to -mm tree
      ... Our prayer wheel would be easier appeased if you actually told us which parts of the VMI timer you objected to. ... We should not add our own assembly code to call out to a local timer handler ... Using either of those for the local timer interrupt on SMP does not work because they assume traditional IRQ semantics - an IRQ raised from the bus should be serviced by one processor. ...
      (Linux-Kernel)
    • Re: hardwired VMI crap
      ... Clock events and clocksources take care of most of the timer issues, but there is still ugliness from SMP timer events depending on having part of the APIC infrastructure for wiring the interrupt gates. ... When we're about two weeks away from a product release and you are threatening to unmerge or block our code because we didn't create an abstract interrupt controller, we re-used the APIC and IO-APIC, this is uber rocket science. ... Use the irq APIs to allocate IRQ-0 as a percpu IRQ, then change the IO-APIC code so it can know not to convert this PIC IRQ into a IO-APIC edge IRQ. ...
      (Linux-Kernel)
    • Re: Problem with ata layer in 2.6.24
      ... Nvidia board detected. ... Ignoring ACPI timer override. ... include an incorrect ACPI interrupt override for the timer interrupt, ...
      (Linux-Kernel)