[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <alpine.LFD.1.10.0902091226400.12457@ftp.linux-mips.org>
Date: Mon, 9 Feb 2009 12:34:21 +0000 (GMT)
From: "Maciej W. Rozycki" <macro@...ux-mips.org>
To: Ingo Molnar <mingo@...e.hu>
cc: Yinghai Lu <yinghai@...nel.org>,
Thomas Gleixner <tglx@...utronix.de>,
"H. Peter Anvin" <hpa@...or.com>,
Andrew Morton <akpm@...ux-foundation.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] x86: check_timer cleanup
On Mon, 9 Feb 2009, Ingo Molnar wrote:
> > What problems are you referring to, Ingo? Perhaps they should be looked
> > into specifically?
>
> I got a spurious boot failure on a 64-bi testbox:
>
> [ 0.280000] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
> [ 0.296000] ..MP-BIOS bug: 8254 timer not connected to IO-APIC
> [ 0.296000] ...trying to set up timer (IRQ0) through the 8259A ...
> [ 0.296000] ..... (found apic 0 pin 2) ...
> [ 0.308000] ....... failed.
> [ 0.308000] ...trying to set up timer as Virtual Wire IRQ...
> [ 0.324000] ..... failed.
> [ 0.324000] ...trying to set up timer as ExtINT IRQ...
> [ 0.340000] ..... failed :(.
> [ 0.340000] Kernel panic - not syncing: IO-APIC + timer doesn't work! Boot with apic=debug and send a report. Then try booting with the 'noapic' option.
>
> Not reproducible. Full bootlog below.
If so, it could have been anything. Even a casual hardware failure. The
timer retriggers by itself producing both edges automatically, so even if
an edge is missed because of the mask, another one follows shortly. I
don't think the change proposed by Yinghai would make any difference here.
Pity you can't use an in-circuit debugger with the x86... :(
Maciej
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists