public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Dinakar Guniguntala <dino@in.ibm.com>
Cc: linux-kernel@vger.kernel.org,
	Thomas Gleixner <tglx@linutronix.de>,
	john stultz <johnstul@us.ibm.com>
Subject: Re: IO-APIC problem with 2.6.14-rt9
Date: Thu, 10 Nov 2005 21:02:05 +0100	[thread overview]
Message-ID: <20051110200205.GA4696@elte.hu> (raw)
In-Reply-To: <20051110200226.GA18780@in.ibm.com>


* 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

?

	Ingo


  reply	other threads:[~2005-11-10 20:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-10 20:02 IO-APIC problem with 2.6.14-rt9 Dinakar Guniguntala
2005-11-10 20:02 ` Ingo Molnar [this message]
2005-11-10 20:30   ` Dinakar Guniguntala
2005-11-10 20:29     ` john stultz
2005-11-10 20:55       ` Dinakar Guniguntala
2005-11-10 21:04       ` Ingo Molnar
2005-11-10 21:42         ` john stultz
2005-11-11  7:38           ` Ingo Molnar
2005-11-11  8:20             ` Ingo Molnar
  -- strict thread matches above, loose matches on Subject: below --
2005-11-12  2:25 Pallipadi, Venkatesh
2005-11-12  2:34 ` john stultz

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=20051110200205.GA4696@elte.hu \
    --to=mingo@elte.hu \
    --cc=dino@in.ibm.com \
    --cc=johnstul@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    /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