cpufreq Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: cpufreq@vger.kernel.org
Subject: [Bug 16072] [HP Pavilion dm1-1110ev] Cpufreq doesn't work at all ( Intel Celeron U2300 )
Date: Thu, 28 Oct 2010 15:31:13 GMT	[thread overview]
Message-ID: <201010281531.o9SFVDUt010947@demeter1.kernel.org> (raw)
In-Reply-To: <bug-16072-12968@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=16072





--- Comment #24 from Thomas Renninger <trenn@suse.de>  2010-10-28 15:30:57 ---
Robert: Please stop writing wrong assumptions you claim to know for sure. Also
only providing half information is nearly as bad as writing wrong ones.
> The power savings dropping from 2.8 GHz to 350 MHz is 144 to 109 W or nearly
> 24%.
I expect this is when the CPU is fully utilized?
The fact that you missed out some measures, smells like you do not like the
data, right?
But this bug is about something totally else, please open a new bug, add me to
CC and attach all info requested in comment #18. This is not about compiling a
kernel, it's simply measuring with a reboot in between, it doesn't take long...


For this very specific CPU this is about, I asked people who may have an idea,
but did not get an answer yet. Until now I expect freq switching is not
supported. But as deep C-states are, it's not that bad, you want to sleep as
soon as possible anyway.

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

  parent reply	other threads:[~2010-10-28 15:31 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-16072-12968@https.bugzilla.kernel.org/>
2010-08-02 18:57 ` [Bug 16072] [HP Pavilion dm1-1110ev] Cpufreq doesn't work at all ( Intel Celeron U2300 ) bugzilla-daemon
2010-10-22 15:34 ` bugzilla-daemon
2010-10-22 19:37 ` bugzilla-daemon
2010-10-22 21:09 ` bugzilla-daemon
2010-10-22 21:49 ` bugzilla-daemon
2010-10-22 22:00 ` bugzilla-daemon
2010-10-22 23:52 ` bugzilla-daemon
2010-10-23  6:03 ` bugzilla-daemon
2010-10-23 11:28 ` bugzilla-daemon
2010-10-24 10:03 ` bugzilla-daemon
2010-10-24 23:10 ` bugzilla-daemon
2010-10-25 17:34 ` bugzilla-daemon
2010-10-28 15:31 ` bugzilla-daemon [this message]
2011-07-30  4:56 ` bugzilla-daemon

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=201010281531.o9SFVDUt010947@demeter1.kernel.org \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=cpufreq@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