[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1190639101.4035.185.camel@chaos>
Date: Mon, 24 Sep 2007 15:05:01 +0200
From: Thomas Gleixner <tglx@...utronix.de>
To: "Rafael J. Wysocki" <rjw@...k.pl>
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 Mon, 2007-09-24 at 14:57 +0200, Rafael J. Wysocki wrote:
> > > 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". :-)
Hmm, ACPI is in the log all over the place.
> Fortunately, noapictimer helps as well, dmesg attached (I have the one
> from 2.6.23-rc6-mm1 ready, too).
Ok, at which point is the box stopping, when you omit noa* ? Is
earlyprintk giving you any useful info ?
tglx
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists