From: bugzilla-daemon@bugzilla.kernel.org
To: cpufreq@vger.kernel.org
Subject: [Bug 65301] Cores stuck at max frequency after resume from suspend (Haswell)
Date: Sun, 24 Nov 2013 07:16:23 +0000 [thread overview]
Message-ID: <bug-65301-12968-FWwvS53kad@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-65301-12968@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=65301
tomasi <tomas.ivanek@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tomas.ivanek@gmail.com
--- Comment #1 from tomasi <tomas.ivanek@gmail.com> ---
I can confirm on Lenovo T440s with Intel(R) Core(TM) i5-4200U CPU @ 1.60GHz
after resume cpu is set on max
bio@dell-xps:/sys/devices/system/cpu/cpu0/cpufreq$ sudo cat cpuinfo_cur_freq
2543476
Linux dell-xps 3.12.0-031200-generic #201311031935 SMP Mon Nov 4 00:36:54 UTC
2013 x86_64 x86_64 x86_64 GNU/Linux
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2013-11-24 7:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-21 9:34 [Bug 65301] New: Cores stuck at max frequency after resume from suspend (Haswell) bugzilla-daemon
2013-11-24 7:16 ` bugzilla-daemon [this message]
2013-11-25 2:08 ` [Bug 65301] " bugzilla-daemon
2013-11-25 3:09 ` bugzilla-daemon
2013-11-25 3:28 ` bugzilla-daemon
2013-11-25 9:08 ` bugzilla-daemon
2013-11-25 20:22 ` bugzilla-daemon
2013-11-25 22:15 ` bugzilla-daemon
2013-11-26 1:20 ` bugzilla-daemon
2013-11-28 8:15 ` bugzilla-daemon
2013-12-09 3:26 ` bugzilla-daemon
2013-12-09 5:49 ` bugzilla-daemon
2013-12-09 5:52 ` 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=bug-65301-12968-FWwvS53kad@https.bugzilla.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.