[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200709232208.18797.rjw@sisk.pl>
Date: Sun, 23 Sep 2007 22:08:18 +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 Sunday, 23 September 2007 21:10, Thomas Gleixner wrote:
> On Sun, 2007-09-23 at 12:57 +0200, Rafael J. Wysocki wrote:
> > Hi Thomas,
> >
> > Unfortunately, my observation that the patch series:
> >
> > http://tglx.de/projects/hrtimers/2.6.23-rc4/patch-2.6.23-rc4-hrt1.patches.tar.bz2
> >
> > worked with 2.6.23-rc4 was wrong. It _sometimes_ works, but usually doesn't
> > boot, just like 2.6.23-rc4-mm1, 2.6.23-rc6-mm1 and everything in between with
> > the above patch series applied. I've also tried:
> >
> > http://tglx.de/projects/hrtimers/2.6.23-rc5/patch-2.6.23-rc5-hrt1.patches.tar.bz2
> > http://tglx.de/projects/hrtimers/2.6.23-rc6/patch-2.6.23-rc6-hrt2.patch
> >
> > with the same result.
> >
> > The problematic patch is x86_64-convert-to-clockevents.patch .
> >
> > Since the boot fails very early, before any messages reach the (VGA) console,
> > I have no idea what to do next, except for digging in the code.
>
> Ok, lets track it down. Is there any difference when you add:
>
> nohz=off
> highres=off
> noapictimer
>
> or any combinations of the above to the kernel command line ?
First, for now, I build all kernels with NO_HZ and HIGH_RES_TIMERS unset
(.config for 2.6.23-rc6-mm1 is attached).
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).
Greetings,
Rafael
View attachment "2.6.23-rc6-mm1-config" of type "text/plain" (55974 bytes)
Powered by blists - more mailing lists