额外信息

额外信息

有时,我无法重现这种情况(但这种情况经常发生 - 至少一周几次),我的 CPU 会低于规定的最低值。这是cpufreq-info一分钟前的示例输出:

    cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009
    Report errors and bugs to [email protected], please.
    analyzing CPU 0:
      driver: intel_pstate
      CPUs which run at the same hardware frequency: 0
      CPUs which need to have their frequency coordinated by software: 0
      maximum transition latency: 0.97 ms.
      hardware limits: 800 MHz - 3.30 GHz
      available cpufreq governors: performance, powersave
      current policy: frequency should be within 800 MHz and 3.30 GHz.
                      The governor "powersave" may decide which speed to use
                      within this range.
      current CPU frequency is 610 MHz.
    analyzing CPU 1:
      driver: intel_pstate
      CPUs which run at the same hardware frequency: 1
      CPUs which need to have their frequency coordinated by software: 1
      maximum transition latency: 0.97 ms.
      hardware limits: 800 MHz - 3.30 GHz
      available cpufreq governors: performance, powersave
      current policy: frequency should be within 800 MHz and 3.30 GHz.
                      The governor "powersave" may decide which speed to use
                      within this range.
      current CPU frequency is 615 MHz.
    analyzing CPU 2:
      driver: intel_pstate
      CPUs which run at the same hardware frequency: 2
      CPUs which need to have their frequency coordinated by software: 2
      maximum transition latency: 0.97 ms.
      hardware limits: 800 MHz - 3.30 GHz
      available cpufreq governors: performance, powersave
      current policy: frequency should be within 800 MHz and 3.30 GHz.
                      The governor "powersave" may decide which speed to use
                      within this range.
      current CPU frequency is 590 MHz.
    analyzing CPU 3:
      driver: intel_pstate
      CPUs which run at the same hardware frequency: 3
      CPUs which need to have their frequency coordinated by software: 3
      maximum transition latency: 0.97 ms.
      hardware limits: 800 MHz - 3.30 GHz
      available cpufreq governors: performance, powersave
      current policy: frequency should be within 800 MHz and 3.30 GHz.
                      The governor "powersave" may decide which speed to use
                      within this range.
      current CPU frequency is 589 MHz.

问题是它确实会减慢一切。Firefox 变得更慢,vim 的启动时间从 150-250 毫秒增加到 700 毫秒以上,g++编译速度慢了三倍,等等。

重新启动即可解决所有问题。

过去几个小时来自我的系统日志的一些错误行:

    May 17 16:10:53 lati kernel: [ 1421.872755] ACPI Error: Index value 0x0000000000000083 overflows field width 0x7 (20140424/exfldio-343)
    May 17 16:10:53 lati kernel: [ 1421.872758] ACPI Error: Method parse/execution failed [\NEVT] (Node ffff88040e047258), AE_AML_REGISTER_LIMIT (20140424/psparse-536)
    May 17 16:10:53 lati kernel: [ 1421.872761] ACPI Error: Method parse/execution failed [\_SB_.PCI0.LPCB.ECDV._Q66] (Node ffff88040e044b90), AE_AML_REGISTER_LIMIT (20140424/psparse-536)
    May 17 16:10:56 lati kernel: [ 1425.907749] ACPI Error: Index value 0x0000000000000083 overflows field width 0x7 (20140424/exfldio-343)
    May 17 16:10:56 lati kernel: [ 1425.907765] ACPI Error: Method parse/execution failed [\NEVT] (Node ffff88040e047258), AE_AML_REGISTER_LIMIT (20140424/psparse-536)
    May 17 16:10:56 lati kernel: [ 1425.907794] ACPI Error: Method parse/execution failed [\_SB_.PCI0.LPCB.ECDV._Q66] (Node ffff88040e044b90), AE_AML_REGISTER_LIMIT (20140424/psparse-536)
    May 17 16:12:09 lati kernel: [    1.925333] EXT4-fs (sda5): re-mounted. Opts: errors=remount-ro
    May 17 16:12:09 lati kernel: [    2.421037] systemd-udevd[331]: Error calling EVIOCSKEYCODE: Invalid argument
    May 17 16:12:21 lati gnome-session[2251]: WARNING: Could not parse desktop file tracker-store.desktop or it references a not found TryExec binary
    May 17 16:12:21 lati gnome-session[2251]: WARNING: Could not parse desktop file tracker-miner-fs.desktop or it references a not found TryExec binary
    May 17 16:12:51 lati gnome-session[2251]: GLib-CRITICAL: g_environ_setenv: assertion 'value != NULL' failed
    May 17 17:48:19 lati kernel: [ 5769.576717] systemd-hostnamed[6983]: Warning: nss-myhostname is not installed. Changing the local hostname might make it unresolveable. Please install nss-myhostname!

我在 Dell E7440 上使用 Ubuntu 14.04.2,全新安装,64 位,BIOS 版本 A14。

lsb_release顺便说一句,当我处于这种模式时,即使执行也需要大约 400 毫秒。

额外信息

  • 我的处理器型号名称:Intel(R) Core(TM) i7-4600U CPU @ 2.10GHz
  • 我的处理器型号:69
  • 它可能仅在暂停后发生,但通常不会发生(例如,自从我问这个问题以来它只发生过一次)。

额外信息 (2)

输出grep -r . */sys/class/thermal

    cooling_device0/type:Processor
    cooling_device0/power/control:auto
    cooling_device0/power/async:disabled
    cooling_device0/power/runtime_enabled:disabled
    cooling_device0/power/runtime_active_kids:0
    cooling_device0/power/runtime_active_time:0
    cooling_device0/power/runtime_status:unsupported
    cooling_device0/power/runtime_usage:0
    cooling_device0/power/runtime_suspended_time:0
    cooling_device0/cur_state:0
    cooling_device0/max_state:3
    cooling_device1/type:Processor
    cooling_device1/power/control:auto
    cooling_device1/power/async:disabled
    cooling_device1/power/runtime_enabled:disabled
    cooling_device1/power/runtime_active_kids:0
    cooling_device1/power/runtime_active_time:0
    cooling_device1/power/runtime_status:unsupported
    cooling_device1/power/runtime_usage:0
    cooling_device1/power/runtime_suspended_time:0
    cooling_device1/cur_state:0
    cooling_device1/max_state:3
    cooling_device2/type:Processor
    cooling_device2/power/control:auto
    cooling_device2/power/async:disabled
    cooling_device2/power/runtime_enabled:disabled
    cooling_device2/power/runtime_active_kids:0
    cooling_device2/power/runtime_active_time:0
    cooling_device2/power/runtime_status:unsupported
    cooling_device2/power/runtime_usage:0
    cooling_device2/power/runtime_suspended_time:0
    cooling_device2/cur_state:0
    cooling_device2/max_state:3
    cooling_device3/type:Processor
    cooling_device3/power/control:auto
    cooling_device3/power/async:disabled
    cooling_device3/power/runtime_enabled:disabled
    cooling_device3/power/runtime_active_kids:0
    cooling_device3/power/runtime_active_time:0
    cooling_device3/power/runtime_status:unsupported
    cooling_device3/power/runtime_usage:0
    cooling_device3/power/runtime_suspended_time:0
    cooling_device3/cur_state:0
    cooling_device3/max_state:3
    cooling_device4/type:intel_powerclamp
    cooling_device4/power/control:auto
    cooling_device4/power/async:disabled
    cooling_device4/power/runtime_enabled:disabled
    cooling_device4/power/runtime_active_kids:0
    cooling_device4/power/runtime_active_time:0
    cooling_device4/power/runtime_status:unsupported
    cooling_device4/power/runtime_usage:0
    cooling_device4/power/runtime_suspended_time:0
    cooling_device4/cur_state:-1
    cooling_device4/max_state:50
    thermal_zone0/mode:enabled
    thermal_zone0/temp:25000
    thermal_zone0/type:acpitz
    thermal_zone0/power/control:auto
    thermal_zone0/power/async:disabled
    thermal_zone0/power/runtime_enabled:disabled
    thermal_zone0/power/runtime_active_kids:0
    thermal_zone0/power/runtime_active_time:0
    thermal_zone0/power/runtime_status:unsupported
    thermal_zone0/power/runtime_usage:0
    thermal_zone0/power/runtime_suspended_time:0
    thermal_zone0/trip_point_0_temp:107000
    thermal_zone0/trip_point_0_type:critical
    thermal_zone0/policy:step_wise
    thermal_zone0/passive:0
    thermal_zone1/temp:47000
    thermal_zone1/type:x86_pkg_temp
    thermal_zone1/power/control:auto
    thermal_zone1/power/async:disabled
    thermal_zone1/power/runtime_enabled:disabled
    thermal_zone1/power/runtime_active_kids:0
    thermal_zone1/power/runtime_active_time:0
    thermal_zone1/power/runtime_status:unsupported
    thermal_zone1/power/runtime_usage:0
    thermal_zone1/power/runtime_suspended_time:0
    thermal_zone1/trip_point_0_temp:0
    thermal_zone1/trip_point_0_type:passive
    thermal_zone1/trip_point_1_temp:0
    thermal_zone1/trip_point_1_type:passive
    thermal_zone1/policy:step_wise

答案1

问题还会发生吗?
我迫切希望得到对我认为正在发生的事情的确认或否定。

理论上,在挂起时钟调制后,不知何故(怀疑是 BIOS 问题)已启用。当前版本的 intel_pstate 驱动程序与任何时钟调制的使用都不兼容,总是导致将目标 pstate 驱动到最小值,而不管负载如何。结果是明显的 CPU 频率停留在最小值 * 调制百分比。acpi-cpufreq 驱动程序与时钟调制配合良好,可产生所需的频率 * 调制百分比。(即,acpi-cpufreq 驱动程序的问题不太明显。)

请执行以下测试:
1.)(每次启动需要一次)

sudo modprobe msr

2.) 在任何暂停之前:

sudo rdmsr -a 0x19a

3.) 暂停后导致 CPU 频率降低:

sudo rdmsr -a 0x19a

4.)如果步骤3的结果不为0,则:

sudo wrmsr -a 0x19a 0x0

并检查:

sudo rdmsr -a 0x19a

5.) CPU 频率现在正常吗?

将所有输出结果发回此处。

注意:rdmsr 和 wrmsr 包含在 msr-tools 包中,我不记得它是否默认安装。

编辑:

如果可以的话,英特尔热相互作用和 pstates 方面的主题专家还希望获得以下输出:

cd /sys/class/thermal
grep -r . *

相关内容