public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Michael (Micksa) Slade" <micksa@knobbits.org>
To: linux-kernel@vger.kernel.org
Subject: Inspiron 6000 and CPU power saving
Date: Mon, 16 Oct 2006 12:18:10 +1000	[thread overview]
Message-ID: <4532EBE2.6090709@knobbits.org> (raw)

I recently discovered that my Inspiron 6000 uses about 50% more power 
idling in linux than in windows XP.  This means its battery life is 
about 2/3 of what it could/should be.

I guessed it might be the CPU, and did some tests.  The results strongly 
suggest as much.  These are the results I got for power consumption in 
various situations.

linux idle at 800MHz: 27W        
linux idle at 1600MHz: 36W        
linux raytracing at 800: 30W
linux raytracing at 1600: 42W 

windows idle (presumably 800MHz): 16W
windows raytracing (presumably 1600MHz): 36W

I've tried ubuntu dapper and ubuntu edgy, and RIP 10 (rescue disk) and 
BBC 2.1 (rescue disk), and they all appear to have the same issue.  The 
machine's BIOS has no APM so I can't try it for comparison.

I've tried noapic and "echo n > 
/sys/module/processor/parameters/max_cstate", where n is 1 thru 4.  
Neither appear to have any affect.

I need help digging deeper.  I guess /proc/acpi/processor/CPU0/power 
could give some insight but I'm not sure how to read the numbers.  That 
and "learn about ACPI" is all I can figure out so far.

So where to from here?  I am prepared to spend a significant amount of 
time researching and resolving the issue, so feel free to suggest 
reading the ACPI spec or whatever if that's what it's going to take.

Mick.


             reply	other threads:[~2006-10-16  2:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-16  2:18 Michael (Micksa) Slade [this message]
2006-10-17  8:07 ` Inspiron 6000 and CPU power saving Oleg Verych
2006-10-25  9:47 ` Pavel Machek
  -- strict thread matches above, loose matches on Subject: below --
2006-10-19 17:26 Pallipadi, Venkatesh
2006-10-21 11:45 ` Michael (Micksa) Slade

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=4532EBE2.6090709@knobbits.org \
    --to=micksa@knobbits.org \
    --cc=linux-kernel@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