lkml.org 
[lkml]   [2003]   [Dec]   [10]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: Fixes for nforce2 hard lockup, apic, io-apic, udma133 covered
    On Wed, 10 Dec 2003, Ross Dickson wrote:

    > Relevant dmesg output from Albatron KM18G Pro ( this is different MOBO (same type) but
    > this time has a barton core 2500 XP cpu).
    >
    > enabled ExtINT on CPU#0
    > ESR value before enabling vector: 00000000
    > ESR value after enabling vector: 00000000
    > 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.
    > ..TIMER: vector=0x31 pin1=2 pin2=-1
    > ..MP-BIOS bug: 8254 timer not connected to IO-APIC pin2
    > ..TIMER: Is timer irq0 connected to IOAPIC Pin0? ...
    > IOAPIC[0]: Set PCI routing entry (2-0 -> 0x31 -> IRQ 0 Mode:0 Active:0)
    > ..TIMER check 8259 ints disabled, imr1:ff, imr2:ff
    > ..TIMER: works OK on apic pin0 irq0
    > Using local APIC timer interrupts.
    > calibrating APIC timer ...
    > ..... CPU clock speed is 1829.0708 MHz.
    > ..... host bus clock speed is 332.0674 MHz.
    > cpu: 0, clocks: 332674, slice: 166337
    > CPU0<T0:332672,T1:166320,D:15,S:166337,C:332674>

    Hmm, while this is different from what is documented in the MP Spec, it
    looks like the 8254 IRQ is connected to INTIN0 indeed. We can handle such
    a setup if the BIOS reports routing correctly. Since you invoke
    io_apic_set_pci_routing() I assume you use ACPI for IRQ routing
    information. Can you please rebuild the kernel with APIC_DEBUG set to 1
    in include/asm-i386/apic.h and send me the bootstrap log? Can you please
    send me the output of a tool called `mptable' as well, so that I can
    compare the results?

    Maciej

    --
    + Maciej W. Rozycki, Technical University of Gdansk, Poland +
    +--------------------------------------------------------------+
    + e-mail: macro@ds2.pg.gda.pl, PGP key available +
    -
    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/

    \
     
     \ /
      Last update: 2005-03-22 13:59    [W:3.887 / U:0.020 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site