[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070322141630.GA752@stusta.de>
Date: Thu, 22 Mar 2007 15:16:30 +0100
From: Adrian Bunk <bunk@...sta.de>
To: Thomas Gleixner <tglx@...utronix.de>
Cc: Ray Lee <ray-lk@...rabbit.org>,
LKML <linux-kernel@...r.kernel.org>, Ingo Molnar <mingo@...e.hu>,
john stultz <johnstul@...ibm.com>,
Len Brown <len.brown@...el.com>, Andi Kleen <ak@...e.de>,
linux-acpi@...r.kernel.org
Subject: Re: 2.6.21-rc[123] regression with NOAPIC
On Thu, Mar 22, 2007 at 03:10:03PM +0100, Thomas Gleixner wrote:
> On Thu, 2007-03-22 at 14:42 +0100, Adrian Bunk wrote:
> > > Starting with head as of yesterday and reverting two commits (that are
> > > duplicates of each other -- the same commit came into Linus's tree via
> > > two different paths) 'fixes' the problem for me. I'll let those with the
> > > big brains decide just why.
> > >
> > > The two commits are 5c95d3f5783ab184f64b7848f0a871352c35c3cf and
> > > 3434933b17fa64adddf83059603c61296f6e1ee2 . The net reverse diff of those
> > > two is below.
> > >...
> >
> > Thanks for tracking it down.
> >
> > It's quite possible that these commits trigger your problem.
> >
> > Does it work if you do _not_ revert the commits, and instead replace in
> > drivers/acpi/processor_idle.c the
> > #ifdef ARCH_APICTIMER_STOPS_ON_C3
> > with an
> > #if 0
> > ?
>
> Then NOAPIC probably works again, but booting w/o NOAPIC fails.
But we'll know that it's this code that has a problen with noapic
in the CONFIG_GENERIC_CLOCKEVENTS=n case.
> tglx
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
-
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