From: Sascha Heid <saschaheid@gmail.com>
To: linux-acpi@vger.kernel.org
Subject: CoreDuo Bus-Master-Activity on Core1 ffffffff when idle, no C3
Date: Fri, 09 Feb 2007 03:47:06 +0100 [thread overview]
Message-ID: <1170989226.4546.17.camel@localhost> (raw)
Hi List!
i recently got a Lenovo X60T, installed Gentoo Linux, and since then i
am trying to figure out why i miss 2h of battery-life compared to
Windows-Users. After a while i noticed that the Bus-Master-Activity on
CPU1 is ffffffff when its idle and only drops if i give it some work to
do (like a kernel compile with make -j3)
When i put some load on both cores the Bus Master Activity of CPU1 is
normalizing itself and varies according to the load.
When i leave the Laptop idle for a while it gets actually hotter (60C)
then when i use it (44C).
The CPU is not able to stay in C3, it tries but comes back to C2 within
the second, i assume that is because of the high Bus Master Activity of
CPU1?
I have already looked for help about this on various forums and mailing
lists and i talked to other people with CoreDuo's and they do not have
this issue with the Bus Master Activity.
I tried alot of different kernels (2.6.19 and 2.6.20) and setups or used
preconfigured Kernels or even Live-Distros.
I also booted a *very* minimal Gentoo-Linux setup, no WLAN, no USB, no X
etc., and played with the BIOS-Settings (disabling as much as possible),
and now i am at a point where i really dont know what to do anymore and
i fear that im not getting any answers anywhere.
If anyone has any advice, information or would like to see some logs or
configs, i would be very gratefull.
Greetings from Germany,
Sascha
next reply other threads:[~2007-02-09 1:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-09 2:47 Sascha Heid [this message]
2007-02-09 6:54 ` CoreDuo Bus-Master-Activity on Core1 ffffffff when idle, no C3 Len Brown
2007-02-09 14:29 ` Henrique de Moraes Holschuh
2007-02-09 18:35 ` Sascha Heid
2007-02-09 19:17 ` Henrique de Moraes Holschuh
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=1170989226.4546.17.camel@localhost \
--to=saschaheid@gmail.com \
--cc=linux-acpi@vger.kernel.org \
/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