LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Andi Kleen <ak@suse.de>
Cc: Grzegorz Chwesewicz <grzegorz.chwesewicz@chilan.com>,
Stefan Prechtel <stefan.prechtel@googlemail.com>,
linux-kernel@vger.kernel.org, mingo@elte.hu,
Len Brown <lenb@kernel.org>, john stultz <johnstul@us.ibm.com>
Subject: Re: BUG lapic: Can't boot on battery (2.6.21-rc{1,2,3,4})
Date: Wed, 21 Mar 2007 11:10:08 +0100 [thread overview]
Message-ID: <1174471808.10840.28.camel@localhost.localdomain> (raw)
In-Reply-To: <200703211046.20724.ak@suse.de>
On Wed, 2007-03-21 at 10:46 +0100, Andi Kleen wrote:
> On Wednesday 21 March 2007 10:24, Thomas Gleixner wrote:
> > On Tue, 2007-03-20 at 17:47 +0100, Grzegorz Chwesewicz wrote:
> > > I have HP nx6325. I've tried to use WARN_ON_ONCE patch, but I don't see
> > > nothing special in dmesg. Just in case I'm posting my
> > > dmesg_2.6.20_WARN_ON_ONCE_on_battery log on
> > > http://bugzilla.kernel.org/show_bug.cgi?id=8235 .
> > >
> > > Below I post output of my /proc interrupts (10 sec. delay between reads).
> > >
> > > Other interesting thing on 2.6-git is that when I press a key on keyboard
> > > it doesn't repeat (on battery), but it repeats on 2.6-git on ac.
> >
> > Sigh. The periodic PIT interrupt pampers over the problem in <2.6.21-rc.
> > It prevents the BIOS to switch the CPU in lower power states.
>
> I think I ran into the same problem with my initial noidletick patch.
> I don't have that test machine anymore though.
>
> Normally the "use PIT when AMD && Cstate >= 2" check should
> have caught that though. Why did it here?
The BIOS/ACPI is broken and does only expose C1, which should not switch
off LAPIC. The BIOS is switching into deeper C-States behind the kernels
back somehow.
tglx
next prev parent reply other threads:[~2007-03-21 10:02 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-19 17:10 Stefan Prechtel
2007-03-19 17:36 ` Thomas Gleixner
2007-03-19 17:48 ` Thomas Gleixner
2007-03-19 18:53 ` Stefan Prechtel
2007-03-19 19:17 ` Stefan Prechtel
2007-03-19 19:27 ` Thomas Gleixner
2007-03-19 19:49 ` Stefan Prechtel
2007-03-19 20:04 ` Thomas Gleixner
2007-03-19 20:35 ` Stefan Prechtel
2007-03-19 20:56 ` Thomas Gleixner
2007-03-19 21:51 ` Stefan Prechtel
2007-03-20 1:15 ` Thomas Gleixner
2007-03-20 8:23 ` Stefan Prechtel
2007-03-20 16:47 ` Grzegorz Chwesewicz
2007-03-21 9:24 ` Thomas Gleixner
2007-03-21 9:46 ` Andi Kleen
2007-03-21 10:10 ` Thomas Gleixner [this message]
2007-03-21 10:37 ` Andi Kleen
2007-03-21 11:14 ` Thomas Gleixner
2007-03-21 12:15 ` Thomas Gleixner
2007-03-21 12:33 ` Thomas Gleixner
2007-03-21 12:42 ` Andi Kleen
2007-03-21 13:04 ` Stefan Prechtel
2007-03-21 13:15 ` Thomas Gleixner
2007-03-21 14:14 ` [PATCH] i386: disable local apic timer via command line or dmi quirk Thomas Gleixner
2007-03-21 14:09 ` Ingo Molnar
2007-03-21 15:14 ` Grzegorz Chwesewicz
2007-03-22 20:42 ` Stefan Prechtel
2007-03-28 3:28 ` Len Brown
2007-03-28 3:38 ` Len Brown
2007-03-28 9:13 ` Thomas Gleixner
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=1174471808.10840.28.camel@localhost.localdomain \
--to=tglx@linutronix.de \
--cc=ak@suse.de \
--cc=grzegorz.chwesewicz@chilan.com \
--cc=johnstul@us.ibm.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=stefan.prechtel@googlemail.com \
--subject='Re: BUG lapic: Can'\''t boot on battery (2.6.21-rc{1,2,3,4})' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).