From: Alistair John Strachan <s0348365@sms.ed.ac.uk>
To: Arjan van de Ven <arjan@linux.intel.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-acpi@vger.kernel.org
Subject: Re: [announce] Intel announces the PowerTOP utility for Linux
Date: Sat, 12 May 2007 22:12:43 +0100 [thread overview]
Message-ID: <200705122212.43653.s0348365@sms.ed.ac.uk> (raw)
In-Reply-To: <4644F726.1050806@linux.intel.com>
On Saturday 12 May 2007 00:07:18 Arjan van de Ven wrote:
> What's eating the battery life of my laptop? Why isn't it many more
> hours? Which software component causes the most power to be burned?
> These are important questions without a good answer... until now.
This is a really great tool and presents a very intuitive alternative to the
timer stats file..
On a Core 2 Duo Macbook, Linux always gets around 3.2h battery, OS X about
4.2h. This tool has identified that uhci_hcd is where 75% of the ticks are
going when X is not loaded. Unloading uhci_hcd drops the battery life back to
around 4.2h, but I lose the keyboard.
Is there any way to find out what USB driver is causing usb_uhci to be this
busy?
(BTW, the link to Keith's patch for dhcdbd seems to be broken on your
homepage.)
--
Cheers,
Alistair.
Final year Computer Science undergraduate.
1F2 55 South Clerk Street, Edinburgh, UK.
next prev parent reply other threads:[~2007-05-12 21:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-11 23:07 Arjan van de Ven
2007-05-12 0:17 ` Matt Mackall
2007-05-12 1:40 ` Jose Celestino
2007-05-12 2:39 ` Matt Mackall
2007-05-12 4:09 ` Jose Celestino
2007-05-12 11:00 ` Jan Engelhardt
2007-05-12 17:44 ` Arjan van de Ven
2007-05-12 21:12 ` Alistair John Strachan [this message]
2007-05-14 20:22 ` Jan Engelhardt
2007-05-14 20:42 ` Alistair John Strachan
[not found] <fa.FTEkheuP0nHOUv0cCp0k8pBuoMU@ifi.uio.no>
2007-05-15 0:13 ` Robert Hancock
2007-05-15 16:30 ` Ondrej Zary
2007-05-16 7:52 ` Schmidt Michal
2007-05-16 14:20 ` Pavel Machek
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=200705122212.43653.s0348365@sms.ed.ac.uk \
--to=s0348365@sms.ed.ac.uk \
--cc=arjan@linux.intel.com \
--cc=linux-acpi@vger.kernel.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
all inboxes | Powered by JetHome®