From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Mikhail Kshevetskiy <mikhail.kshevetskiy@gmail.com>,
linux-kernel@vger.kernel.org, Dave Jones <davej@redhat.com>,
Chuck Ebbert <cebbert@redhat.com>
Subject: Re: 2.6.23-rc4-mm1 and -rc6-mm1: boot failure on HP nx6325, related to clockevents
Date: Tue, 25 Sep 2007 14:52:00 +0200 [thread overview]
Message-ID: <200709251452.01415.rjw@sisk.pl> (raw)
In-Reply-To: <1190723305.4035.327.camel@chaos>
On Tuesday, 25 September 2007 14:28, Thomas Gleixner wrote:
> On Tue, 2007-09-25 at 14:20 +0200, Rafael J. Wysocki wrote:
> > > > > As i can see from the log, you are booting on computer with dualcore AMD
> > > > > processor. Do you have C1E feature enabled?
> >
> > That's possible, how to check?
> >
> > > > > i386 kernel disable lapic on dualcore AMD with C1E support (see
> > > > > http://lkml.org/lkml/2007/3/29/199). x86_64 kernel do not have this
> > > > > patch still (it's required for tickless kernel only).
> > > >
> > > > Well it is required for non tickless mode as well.
> > > >
> > > > > As result, if
> > > > > you run x86_64 kernel with hrt patch on such computer, the system
> > > > > will stall during boot on lapic timer calibration.
> > > >
> > > > Thanks for the reminder. I have a look into this.
> > >
> > > Can you please boot mainline and provide the output of:
> > >
> > > # cat /proc/interrupts; sleep 10; cat /proc/interrupts
> >
> > albercik:~ # cat /proc/interrupts; sleep 10; cat /proc/interrupts
> > CPU0 CPU1
> > 0: 1159492 0 local-APIC-edge timer
> > LOC: 0 1158220 Local interrupts
> >
> > 0: 1161996 0 local-APIC-edge timer
> > LOC: 0 1160723 Local interrupts
>
> Hmm. That's strange. It looks like the local apic timer is not used, but
> x86_64 definitely lacks the above check.
Ouch, sorry. This is from the kernel booted with "noapictimer".
I'll get the correct output in a little while.
Greetings,
Rafael
next prev parent reply other threads:[~2007-09-25 12:38 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070925101418.68d30a72@localhost>
2007-09-25 8:07 ` 2.6.23-rc4-mm1 and -rc6-mm1: boot failure on HP nx6325, related to clockevents Thomas Gleixner
2007-09-25 9:30 ` Thomas Gleixner
2007-09-25 12:20 ` Rafael J. Wysocki
2007-09-25 12:28 ` Thomas Gleixner
2007-09-25 12:52 ` Rafael J. Wysocki [this message]
2007-09-25 13:15 ` Rafael J. Wysocki
2007-09-23 10:57 Rafael J. Wysocki
2007-09-23 19:10 ` Thomas Gleixner
2007-09-23 20:08 ` Rafael J. Wysocki
2007-09-23 19:59 ` Thomas Gleixner
2007-09-23 20:52 ` Rafael J. Wysocki
2007-09-24 8:07 ` Thomas Gleixner
2007-09-24 12:57 ` Rafael J. Wysocki
2007-09-24 13:05 ` Thomas Gleixner
2007-09-24 13:52 ` Rafael J. Wysocki
2007-09-24 14:23 ` Thomas Gleixner
2007-09-24 15:18 ` Rafael J. Wysocki
2007-09-24 16:46 ` Thomas Gleixner
2007-09-24 19:11 ` Rafael J. Wysocki
2007-09-24 19:13 ` Thomas Gleixner
2007-09-25 13:16 ` Rafael J. Wysocki
2007-09-25 13:17 ` Thomas Gleixner
2007-09-25 20:07 ` Rafael J. Wysocki
2007-09-25 20:46 ` Thomas Gleixner
2007-09-25 21:28 ` Rafael J. Wysocki
2007-09-25 21:24 ` Thomas Gleixner
2007-09-26 15:25 ` Rafael J. Wysocki
2007-09-26 18:51 ` Thomas Gleixner
2007-09-26 19:49 ` Rafael J. Wysocki
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=200709251452.01415.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=cebbert@redhat.com \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mikhail.kshevetskiy@gmail.com \
--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