From: bugzilla-daemon@bugzilla.kernel.org
To: cpufreq@vger.kernel.org
Subject: [Bug 91141] acpi-cpufreq cannot be loaded.
Date: Tue, 13 Jan 2015 00:45:52 +0000 [thread overview]
Message-ID: <bug-91141-12968-mzEa1cLlhN@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-91141-12968@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=91141
Zhang Rui <rui.zhang@intel.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDINFO |CLOSED
Resolution|--- |DOCUMENTED
--- Comment #8 from Zhang Rui <rui.zhang@intel.com> ---
It is better to zip them all to 1 file and upload.
I checked your acpi table, and there is no _PSS control method, on which
acpi_cpufreq driver relies.
The root cause could be that
1. there is no hardware support
or
2. you did not enable the BIOS features for cpu frequency control support.
Please check if there is any BIOS options related.
3. your current version BIOS does not support this feature, and you need to
upgrade the BIOS.
But anyway, I will close this bug report as it is not a Linux kernel issue.
Please feel free to re-open it if you still have some questions.
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2015-01-13 0:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-11 4:00 [Bug 91141] New: acpi-cpufreq cannot be loaded bugzilla-daemon
2015-01-12 4:24 ` [Bug 91141] " bugzilla-daemon
2015-01-12 4:38 ` bugzilla-daemon
2015-01-13 0:06 ` bugzilla-daemon
2015-01-13 0:08 ` bugzilla-daemon
2015-01-13 0:09 ` bugzilla-daemon
2015-01-13 0:09 ` bugzilla-daemon
2015-01-13 0:11 ` bugzilla-daemon
2015-01-13 0:45 ` bugzilla-daemon [this message]
2015-01-13 3:01 ` bugzilla-daemon
2015-01-21 1:47 ` bugzilla-daemon
2015-03-02 3:09 ` bugzilla-daemon
2015-04-16 1:54 ` 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-91141-12968-mzEa1cLlhN@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).