From: "Maciej W. Rozycki" <macro@linux-mips.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Yinghai Lu <yinghai@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
Andrew Morton <akpm@linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86: check_timer cleanup
Date: Mon, 9 Feb 2009 12:34:21 +0000 (GMT) [thread overview]
Message-ID: <alpine.LFD.1.10.0902091226400.12457@ftp.linux-mips.org> (raw)
In-Reply-To: <20090209114520.GE18757@elte.hu>
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
prev parent reply other threads:[~2009-02-09 12:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090206220716.GA15319@elte.hu>
[not found] ` <498D55A4.7000608@kernel.org>
[not found] ` <20090207165901.GA32116@elte.hu>
2009-02-08 5:14 ` [PATCH] x86: check_timer cleanup Yinghai Lu
2009-02-09 8:15 ` Ingo Molnar
2009-02-09 11:38 ` Maciej W. Rozycki
2009-02-09 11:45 ` Ingo Molnar
2009-02-09 12:34 ` Maciej W. Rozycki [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.LFD.1.10.0902091226400.12457@ftp.linux-mips.org \
--to=macro@linux-mips.org \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=yinghai@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox