From: bugzilla-daemon@bugzilla.kernel.org
To: cpufreq@vger.kernel.org
Subject: [Bug 60727] The CPU frequency does not raise when compiling packages on Gentoo
Date: Mon, 12 Aug 2013 02:56:49 +0000 [thread overview]
Message-ID: <bug-60727-12968-9erA8u0qGN@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-60727-12968@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=60727
Lan Tianyu <tianyu.lan@intel.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |NEEDINFO
CC| |tianyu.lan@intel.com
Assignee|cpufreq@vger.kernel.org |tianyu.lan@intel.com
--- Comment #1 from Lan Tianyu <tianyu.lan@intel.com> ---
Could you provide the output of running
"grep . /sys/bus/cpu/devices/cpu*/cpufreq/*" when the issue happen?
--
You are receiving this mail because:
You are the assignee for the bug.
prev parent reply other threads:[~2013-08-12 2:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-10 15:02 [Bug 60727] New: The CPU frequency does not raise when compiling packages on Gentoo bugzilla-daemon
2013-08-12 2:56 ` bugzilla-daemon [this message]
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-60727-12968-9erA8u0qGN@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).