From: Thomas Gleixner <tglx@linutronix.de>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Andi Kleen <ak@suse.de>,
Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>
Subject: Re: 2.6.23-rc4-mm1 and -rc6-mm1: boot failure on HP nx6325, related to clockevents
Date: Wed, 26 Sep 2007 20:51:05 +0200 [thread overview]
Message-ID: <1190832665.23376.38.camel@chaos> (raw)
In-Reply-To: <200709261725.49662.rjw@sisk.pl>
On Wed, 2007-09-26 at 17:25 +0200, Rafael J. Wysocki wrote:
> There still are some oddities.
>
> First, with the "x86-64: Disable local APIC timer use on AMD systems with C1E"
> patch and my collection of suspend patches applied, the box doesn't boot
> (the suspend patches don't even thouch the boot code, so they should be
> irrelevant here). However, it boots if patch-2.6.23-rc7-hrt1.patch (adjusted
> for 2.6.23-rc8) is applied in addition. Is this expected?
No. That's odd. It is nothing else than adding "noapictimer" to the
kernel command line.
> Next, on 2.6.23-rc8 with the patches from:
>
> http://www.sisk.pl/kernel/hibernation_and_suspend/2.6.23-rc8/patches/
>
> plus the "x86-64: Disable local APIC timer use on AMD systems with C1E" patch
> and patch-2.6.23-rc7-hrt1.patch (adjusted for 2.6.23-rc8), hibernation doesn't
> work correctly. Although the box hibernates and restores, there is a temporary
> "hang" during the "resume hardware" sequence, after which the "lock" led starts
> to blink (and remains in this state) and something like this appears in dmesg:
>
> Extended CMOS year: 2000
> Enabling non-boot CPUs ...
> SMP alternatives: switching to SMP code
> Booting processor 1/2 APIC 0x1
> Initializing CPU#1
> Calibrating delay using timer specific routine.. 3990.36 BogoMIPS (lpj=7980735)
> CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
> CPU: L2 Cache: 512K (64 bytes/line)
> Unable to handle kernel paging request at ffffffff806c64d4 RIP:
> [<ffffffff802104cb>] identify_cpu+0x2ac/0x5a1
Hmm. That's really early in the CPU bring up. The only change in this
area is the C1E patch. Can you decode the exact source line, where it is
failing ?
tglx
next prev parent reply other threads:[~2007-09-26 18:51 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-23 10:57 2.6.23-rc4-mm1 and -rc6-mm1: boot failure on HP nx6325, related to clockevents 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 [this message]
2007-09-26 19:49 ` Rafael J. Wysocki
2007-09-26 21:00 ` [REGRESSION from 2.6.23-rc8] (was: Re: 2.6.23-rc4-mm1 and -rc6-mm1: boot failure on HP nx6325, related to clockevents) Rafael J. Wysocki
2007-09-26 21:34 ` Thomas Gleixner
2007-09-26 22:22 ` Linus Torvalds
2007-09-26 22:35 ` Thomas Gleixner
2007-09-26 23:30 ` [REGRESSION from 2.6.23-rc8] Chuck Ebbert
2007-09-28 15:07 ` Chuck Ebbert
2007-09-28 15:10 ` Thomas Gleixner
2007-09-30 9:58 ` [REGRESSION from 2.6.23-rc8] (was: Re: 2.6.23-rc4-mm1 and -rc6-mm1: boot failure on HP nx6325, related to clockevents) Andi Kleen
2007-09-30 14:06 ` Thomas Gleixner
2007-09-30 15:03 ` Andi Kleen
2007-09-26 23:30 ` Rafael J. Wysocki
2007-09-26 23:21 ` Thomas Gleixner
2007-09-27 15:58 ` Rafael J. Wysocki
2007-09-30 9:52 ` Andi Kleen
[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
2007-09-25 13:15 ` 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=1190832665.23376.38.camel@chaos \
--to=tglx@linutronix.de \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rjw@sisk.pl \
/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