Messages in this thread | | | Subject | Re: IO-APIC problem with 2.6.14-rt9 | From | john stultz <> | Date | Thu, 10 Nov 2005 12:29:34 -0800 |
| |
On Fri, 2005-11-11 at 02:00 +0530, Dinakar Guniguntala wrote: > On Thu, Nov 10, 2005 at 09:02:05PM +0100, Ingo Molnar wrote: > > > > * Dinakar Guniguntala <dino@in.ibm.com> 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
Hrm. Could you post the value for BogoMIPS that you're getting now?
My patches touch the __delay() code, since using the TSC based delay has just as many, if not more, problems as the loop based delay. So I want to be careful that my changes are not further causing problems.
Ingo, did you commented out ARCH_HAS_READ_CURRENT_TIMER because of problems with the new calibration code?
thanks -john
- 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/
| |