[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200709241457.40669.rjw@sisk.pl>
Date: Mon, 24 Sep 2007 14:57:40 +0200
From: "Rafael J. Wysocki" <rjw@...k.pl>
To: Thomas Gleixner <tglx@...utronix.de>
Cc: Andi Kleen <ak@...e.de>, Andrew Morton <akpm@...ux-foundation.org>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: 2.6.23-rc4-mm1 and -rc6-mm1: boot failure on HP nx6325, related to clockevents
On Monday, 24 September 2007 10:07, Thomas Gleixner wrote:
> On Sun, 2007-09-23 at 22:52 +0200, Rafael J. Wysocki wrote:
> > > > Second, noacpitimer added to the command line makes all of the kernels, up to
> > > > and including 2.6.23-rc6-mm1, boot (this seems to be 100% reproducible).
> > >
> > > That's valuable information. Can you please provide a boot log of one of
> > > those with an additional "apic=verbose" on the command line ?
> >
> > Attached is the dmesg output from the 2.6.23-rc6 kernel with the patchset:
> >
> > http://tglx.de/projects/hrtimers/2.6.23-rc4/patch-2.6.23-rc4-hrt1.patches.tar.bz2
> >
> > applied. I also have the 2.6.23-rc6-mm1 dmesg output ready, but there's some
> > -mm-specific noise in it. Please let me know if you want it, though.
>
> Hmm:
>
> > Command line: root=/dev/sda3 vga=792 resume=/dev/sda1 noacpitimer apic=verbose 2
> --------------------------------------------------------^^^^^^^^^^^
>
> noacpitimer is not a valid commandline option.
>
> I asked for:
> >> > > noapictimer
I'm blind, sorry.
> So I really wonder, why noacpitimer on the kernel command line makes any
> difference. I'm confused.
\metoo
Well, it was probably read as "noacpi". :-)
Fortunately, noapictimer helps as well, dmesg attached (I have the one
from 2.6.23-rc6-mm1 ready, too).
Greetings,
Rafael
View attachment "2.6.23-rc6-hrt.log" of type "text/x-log" (38968 bytes)
Powered by blists - more mailing lists