mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Meelis Roos <mroos@linux.ee>
To: Ingo Molnar <mingo@elte.hu>
Cc: Yinghai Lu <yinghai@kernel.org>,
	Linux Kernel list <linux-kernel@vger.kernel.org>,
	"Eric W. Biederman" <ebiederm@xmission.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: 2.6.35-rc* regression: ERROR: Unable to locate IOAPIC for GSI *
Date: Fri, 9 Jul 2010 13:02:10 +0300 (EEST)	[thread overview]
Message-ID: <alpine.SOC.1.00.1007091253050.5156@math.ut.ee> (raw)
In-Reply-To: <20100709072619.GE10743@elte.hu>

> > > Meelis do you have a boot trace from 2.6.34?  Meelis can you confirm
> > > that you don't come up in XT_PIC mode in 2.6.34?
> > 
> > Now that was a good question. It's XT-PIC in 2.6.34 too, just the ERROR: 
> > lines are not there.
> 
> So it's not really a regression, just a bit noisier bootup?

Yes, seems so - sorry for the overreaction over the ERROR's.
Both old and new kernels have XT-PIC-XT in /proc/interrupts and both 
work.

Notable differneces from dmesg. The TSC calibration one is interesting. 
2.6.34 tells a failure for some reason. Re-testing 2.6.34 results in 
normal "Fast TSC calibration using PIT"...

-nr_irqs_gsi: 16
+nr_irqs_gsi: 17


-Fast TSC calibration failed
-TSC: PIT calibration matches PMTIMER. 1 loops
-Detected 897.087 MHz processor.
-Calibrating delay loop (skipped), value calculated using timer frequency.. 1794.17 BogoMIPS (lpj=3588348)
+Fast TSC calibration using PIT
+Detected 896.953 MHz processor.
+Calibrating delay loop (skipped), value calculated using timer frequency.. 1793.90 BogoMIPS (lpj=3587812)


+ERROR: Unable to locate IOAPIC for GSI 8
+ERROR: Unable to locate IOAPIC for GSI 13
+ERROR: Unable to locate IOAPIC for GSI 12
+ERROR: Unable to locate IOAPIC for GSI 1
+ERROR: Unable to locate IOAPIC for GSI 6
+ERROR: Unable to locate IOAPIC for GSI 4
+ERROR: Unable to locate IOAPIC for GSI 3
+ERROR: Unable to locate IOAPIC for GSI 7


-- 
Meelis Roos (mroos@linux.ee)

      reply	other threads:[~2010-07-09 10:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-08 13:53 Meelis Roos
2010-07-08 20:27 ` Yinghai Lu
2010-07-08 20:53   ` Yinghai Lu
2010-07-08 20:59     ` Eric W. Biederman
2010-07-08 21:08       ` Yinghai Lu
2010-07-14 11:43     ` Meelis Roos
2010-07-08 22:24   ` Meelis Roos
2010-07-09  7:26     ` Ingo Molnar
2010-07-09 10:02       ` Meelis Roos [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.SOC.1.00.1007091253050.5156@math.ut.ee \
    --to=mroos@linux.ee \
    --cc=ebiederm@xmission.com \
    --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

all inboxes | Powered by JetHome®