From: bugzilla-daemon@bugzilla.kernel.org
To: cpufreq@vger.kernel.org
Subject: [Bug 62551] New: The system freezes for a moment when the CPU scaling is enabled
Date: Sat, 05 Oct 2013 07:16:41 +0000 [thread overview]
Message-ID: <bug-62551-12968@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=62551
Bug ID: 62551
Summary: The system freezes for a moment when the CPU scaling
is enabled
Product: Power Management
Version: 2.5
Kernel Version: 3.10.14
Hardware: i386
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: cpufreq
Assignee: cpufreq@vger.kernel.org
Reporter: zerobertons@yahoo.com
Regression: No
Doesn't matter which governor I use, the mouse, keyboard, video playback stops
for a moment, then it works ok for seconds or minutes, and it happens again.
This started to happen with kernel 3.10 and only when the CPU scaling is
enabled. It happens on different Linux distribution. Going back to 3.9.x solves
the problem.
The CPU is AMD Phenom II 955.
cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009
Report errors and bugs to cpufreq@vger.kernel.org, please.
analyzing CPU 0:
driver: acpi-cpufreq
CPUs which run at the same hardware frequency: 0
CPUs which need to have their frequency coordinated by software: 0
maximum transition latency: 4.0 us.
hardware limits: 800 MHz - 3.20 GHz
available frequency steps: 3.20 GHz, 2.50 GHz, 2.10 GHz, 800 MHz
available cpufreq governors: ondemand, userspace
current policy: frequency should be within 800 MHz and 3.20 GHz.
The governor "userspace" may decide which speed to use
within this range.
current CPU frequency is 3.20 GHz (asserted by call to hardware).
analyzing CPU 1:
driver: acpi-cpufreq
CPUs which run at the same hardware frequency: 1
CPUs which need to have their frequency coordinated by software: 1
maximum transition latency: 4.0 us.
hardware limits: 800 MHz - 3.20 GHz
available frequency steps: 3.20 GHz, 2.50 GHz, 2.10 GHz, 800 MHz
available cpufreq governors: ondemand, userspace
current policy: frequency should be within 800 MHz and 3.20 GHz.
The governor "userspace" may decide which speed to use
within this range.
current CPU frequency is 3.20 GHz (asserted by call to hardware).
analyzing CPU 2:
driver: acpi-cpufreq
CPUs which run at the same hardware frequency: 2
CPUs which need to have their frequency coordinated by software: 2
maximum transition latency: 4.0 us.
hardware limits: 800 MHz - 3.20 GHz
available frequency steps: 3.20 GHz, 2.50 GHz, 2.10 GHz, 800 MHz
available cpufreq governors: ondemand, userspace
current policy: frequency should be within 800 MHz and 3.20 GHz.
The governor "userspace" may decide which speed to use
within this range.
current CPU frequency is 3.20 GHz (asserted by call to hardware).
analyzing CPU 3:
driver: acpi-cpufreq
CPUs which run at the same hardware frequency: 3
CPUs which need to have their frequency coordinated by software: 3
maximum transition latency: 4.0 us.
hardware limits: 800 MHz - 3.20 GHz
available frequency steps: 3.20 GHz, 2.50 GHz, 2.10 GHz, 800 MHz
available cpufreq governors: ondemand, userspace
current policy: frequency should be within 800 MHz and 3.20 GHz.
The governor "userspace" may decide which speed to use
within this range.
current CPU frequency is 3.20 GHz (asserted by call to hardware).
root@slack:/home/zero# uname -a
Linux slack 3.10.14-smp #2 SMP Tue Oct 1 17:17:51 CDT 2013 i686 AMD Phenom(tm)
II X4 955 Processor AuthenticAMD GNU/Linux
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2013-10-05 7:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-05 7:16 bugzilla-daemon [this message]
2013-10-05 7:19 ` [Bug 62551] The system freezes for a moment when the CPU scaling is enabled bugzilla-daemon
2014-06-03 5:24 ` bugzilla-daemon
2014-07-28 1:56 ` [Bug 62551] AMD Phenom II 955.: " bugzilla-daemon
2014-08-11 7:48 ` bugzilla-daemon
2014-08-11 15:56 ` bugzilla-daemon
2014-11-03 18:38 ` 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-62551-12968@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 read-only IMAP folder(s) and NNTP newsgroup(s).