From: bugzilla-daemon@bugzilla.kernel.org
To: cpufreq@vger.kernel.org
Subject: [Bug 101241] cpufreq ondemand not work in my system
Date: Wed, 18 Nov 2015 12:33:10 +0000 [thread overview]
Message-ID: <bug-101241-12968-41mftnKJOq@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-101241-12968@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=101241
Chen Yu <yu.c.chen@intel.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |yu.c.chen@intel.com
--- Comment #1 from Chen Yu <yu.c.chen@intel.com> ---
are you using acpi-cpufreq driver?
plz provide following log with latest 4.4-rc1 if possible
skywalker@sky-lake:/$ grep . /sys/devices/system/cpu/cpu0/cpufreq/*
thank you
Yu
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2015-11-18 12:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-09 3:26 [Bug 101241] New: cpufreq ondemand not work in my system bugzilla-daemon
2015-11-18 12:33 ` bugzilla-daemon [this message]
2015-11-23 10:30 ` [Bug 101241] " bugzilla-daemon
2015-12-14 23:10 ` [Bug 101241] cpufreq ondemand does not work on AMD GX-416RA SOC bugzilla-daemon
2016-08-23 9:34 ` bugzilla-daemon
2016-08-23 9:34 ` 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-101241-12968-41mftnKJOq@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).