From: "Grzegorz Chwesewicz" <grzegorz.chwesewicz@chilan.com>
To: "Stefan Prechtel" <stefan.prechtel@googlemail.com>, tglx@linutronix.de
Cc: linux-kernel@vger.kernel.org, mingo@elte.hu,
"Len Brown" <lenb@kernel.org>, "Andi Kleen" <ak@suse.de>,
"john stultz" <johnstul@us.ibm.com>
Subject: Re: BUG lapic: Can't boot on battery (2.6.21-rc{1,2,3,4})
Date: Tue, 20 Mar 2007 17:47:02 +0100 [thread overview]
Message-ID: <20070320164604.M60273@chilan.com> (raw)
In-Reply-To: <b93822910703200123g5b3ac0e4n1ba1122a7e90a838@mail.gmail.com>
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).
#########################
2.6.20_ac:
CPU0 CPU1
0: 73190 0 local-APIC-edge-fasteio timer
LOC: 72967 72966
CPU0 CPU1
0: 83196 0 local-APIC-edge-fasteio timer
LOC: 82974 82973
#########################
2.6.20_battery:
CPU0 CPU1
0: 468590 0 local-APIC-edge-fasteio timer
LOC: 468410 468409
CPU0 CPU1
0: 478596 0 local-APIC-edge-fasteio timer
LOC: 478417 478416
#########################
2.6-git_ac:
CPU0 CPU1
0: 262 0 local-APIC-edge-fasteoi timer
LOC: 66041 66041
CPU0 CPU1
0: 262 0 local-APIC-edge-fasteoi timer
LOC: 76067 76067
#########################
2.6-git_battery:
CPU0 CPU1
0: 261 0 local-APIC-edge-fasteoi timer
LOC: 29007 29015
CPU0 CPU1
0: 261 0 local-APIC-edge-fasteoi timer
LOC: 29189 29200
#########################
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.
--
Greetings - Grzegorz Chwesewicz
next prev parent reply other threads:[~2007-03-20 17:13 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-19 17:10 BUG lapic: Can't boot on battery (2.6.21-rc{1,2,3,4}) 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 [this message]
2007-03-21 9:24 ` Thomas Gleixner
2007-03-21 9:46 ` Andi Kleen
2007-03-21 10:10 ` Thomas Gleixner
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=20070320164604.M60273@chilan.com \
--to=grzegorz.chwesewicz@chilan.com \
--cc=ak@suse.de \
--cc=johnstul@us.ibm.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=stefan.prechtel@googlemail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox