From: Adrian Bunk <bunk@stusta.de>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Ray Lee <ray-lk@madrabbit.org>,
LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>,
john stultz <johnstul@us.ibm.com>,
Len Brown <len.brown@intel.com>, Andi Kleen <ak@suse.de>,
linux-acpi@vger.kernel.org
Subject: Re: 2.6.21-rc[123] regression with NOAPIC
Date: Thu, 22 Mar 2007 15:16:30 +0100 [thread overview]
Message-ID: <20070322141630.GA752@stusta.de> (raw)
In-Reply-To: <1174572603.10840.162.camel@localhost.localdomain>
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
next prev parent reply other threads:[~2007-03-22 14:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4601573A.8070602@madrabbit.org>
2007-03-22 13:42 ` 2.6.21-rc[123] regression with NOAPIC Adrian Bunk
2007-03-22 14:10 ` Thomas Gleixner
2007-03-22 14:16 ` Adrian Bunk [this message]
2007-03-22 15:16 ` Thomas Gleixner
2007-03-23 5:35 ` Ray Lee
2007-03-09 1:44 Ray Lee
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=20070322141630.GA752@stusta.de \
--to=bunk@stusta.de \
--cc=ak@suse.de \
--cc=johnstul@us.ibm.com \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=ray-lk@madrabbit.org \
--cc=tglx@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.