From: bugzilla-daemon@bugzilla.kernel.org
To: linux-pm@vger.kernel.org
Subject: [Bug 115261] New: CPU Frequency scaling jumps and stucks at max freq
Date: Sat, 26 Mar 2016 09:05:55 +0000 [thread overview]
Message-ID: <bug-115261-137361@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=115261
Bug ID: 115261
Summary: CPU Frequency scaling jumps and stucks at max freq
Product: Power Management
Version: 2.5
Kernel Version: 4.5
Hardware: x86-64
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: cpufreq
Assignee: linux-pm@vger.kernel.org
Reporter: timo.valtoaho@gmail.com
Regression: Yes
Created attachment 210711
--> https://bugzilla.kernel.org/attachment.cgi?id=210711&action=edit
config of bisected kernel
Switching to 4.5 kernel, cpufreq ondemand governor started to act oddly.
Without any load, with freshly booted system, it pumped cpu frequency up to
maximum at some point of time and stayed there. uptime can be anything, but
usually less than 15 minutes when this happens. Driver is acpi-cpufreq.
I have git-bisected this to 0df35026c6a527e65b53bc895ad672d648a248f3. There is
a mention about certain kernel config values that are ok. My values differ and
I get this kind of behaviour.
CPU is AMD Phenom(tm) II X4 905e Processor.
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2016-03-26 9:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-26 9:05 bugzilla-daemon [this message]
2016-03-28 23:38 ` [Bug 115261] BISECTED: CPU Frequency scaling jumps and stucks at max freq - CPU is AMD Phenom(tm) II X4 905e Processor 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-115261-137361@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-pm@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).