Re: IO-APIC problem with 2.6.14-rt9

From: Dinakar Guniguntala
Date: Thu Nov 10 2005 - 15:20:31 EST


On Thu, Nov 10, 2005 at 09:02:05PM +0100, Ingo Molnar wrote:
>
> * Dinakar Guniguntala <dino@xxxxxxxxxx> wrote:
>
> > Hi,
> >
> > I get this on boot with 2.6.14-rt9
> >
> > Intel machine check architecture supported.
> > Intel machine check reporting enabled on CPU#3.
> > CPU3: Intel P4/Xeon Extended MCE MSRs (12) available
> > CPU3: Intel(R) Xeon(TM) MP CPU 2.50GHz stepping 05
> > Total of 4 processors activated (11165.69 BogoMIPS).
> > ENABLING IO-APIC IRQs
> > ..TIMER: vector=0x31 pin1=2 pin2=-1
> > ..MP-BIOS bug: 8254 timer not connected to IO-APIC
> > ...trying to set up timer (IRQ0) through the 8259A ... failed.
> > ...trying to set up timer as Virtual Wire IRQ... failed.
> > ...trying to set up timer as ExtINT IRQ... failed :(.
> > Kernel panic - not syncing: IO-APIC + timer doesn't work! Boot with apic=debug and send a report. Then try booting with the
>
> does it help if you edit include/asm-i386/timex.h and change this line:
>
> //#define ARCH_HAS_READ_CURRENT_TIMER 1
>
> to:
>
> #define ARCH_HAS_READ_CURRENT_TIMER 1
>
> ?

It works !! Thanks Ingo for the immediate response

Just a clarification. The comment in the file include/asm-i386/timex.h
says

/*
* On an Athlon64 the cycles-based estimator is off by a
* factor of 2: udelay(100) takes 200 usecs. With the non-TSC
* based estimator the timings are precise. So turn it off.
*/
#define ARCH_HAS_READ_CURRENT_TIMER 1

Does this mean that this is not Athlon specific and needs to be
changed? I have a IBM x255 with Xeon processors

-Dinakar





-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/