Skip to contentSkip to conversation

New: The system freezes for a moment when the CPU scaling is enabled

Bug 62551 [email protected] 1 participant 7 messages Oct 5, 2013 – Nov 3, 2014

lore
Share & tools
lore
#0 lore 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: [email protected]
          Reporter: [email protected]
        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 [email protected], 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
Signature · 2 lines
You are receiving this mail because:
You are the assignee for the bug.
#2 lore raw

[Bug 62551] The system freezes for a moment when the CPU scaling is enabled

In reply to [email protected]

https://bugzilla.kernel.org/show_bug.cgi?id=62551

Zhang Rui <[email protected]> changed:

What |Removed |Added
----------------------------------------------------------------------------

             Status|NEW                         |NEEDINFO
                 CC|                            |[email protected]

--- Comment #1 from Zhang Rui <[email protected]> --- please attach the output of "grep . /sys/class/thermal/*/*"

Signature · 2 lines
You are receiving this mail because:
You are the assignee for the bug.
#3 lore raw

[Bug 62551] AMD Phenom II 955.: The system freezes for a moment when the CPU scaling is enabled

In reply to [email protected]

https://bugzilla.kernel.org/show_bug.cgi?id=62551

Lan Tianyu <[email protected]> changed:

What |Removed |Added
----------------------------------------------------------------------------

                 CC|                            |[email protected]
           Hardware|i386                        |x86-64
            Summary|The system freezes for a    |AMD Phenom II 955.: The
                   |moment when the CPU scaling |system freezes for a moment
                   |is enabled                  |when the CPU scaling is
                   |                            |enabled
Signature · 2 lines
You are receiving this mail because:
You are the assignee for the bug.
#5 lore raw

[Bug 62551] AMD Phenom II 955.: The system freezes for a moment when the CPU scaling is enabled

In reply to [email protected]

https://bugzilla.kernel.org/show_bug.cgi?id=62551

[email protected] changed:

What |Removed |Added
----------------------------------------------------------------------------

             Status|NEEDINFO                    |RESOLVED
         Resolution|---                         |INVALID

--- Comment #3 from [email protected] ---
I think my problem wasn't related to the cpu scaling after all. The issue was solved by changing the timer tick handling from idle dynticks system to periodic timer ticks.
But now with newer kernels I have no issue with the idle dynticks.

Signature · 2 lines
You are receiving this mail because:
You are the assignee for the bug.
#6 lore raw

[Bug 62551] AMD Phenom II 955.: The system freezes for a moment when the CPU scaling is enabled

In reply to [email protected]

https://bugzilla.kernel.org/show_bug.cgi?id=62551

Len Brown <[email protected]> changed:

What |Removed |Added
----------------------------------------------------------------------------

             Status|RESOLVED                    |CLOSED
                 CC|                            |[email protected]
Signature · 2 lines
You are receiving this mail because:
You are the assignee for the bug.