ThinkWiki - User contributions [en]

Problem with CPU frequency scaling

2008-03-07T02:58:18Z

Fredigundis: /* Symptom */

{{stub}}

==Symptom==
If the battery pack is removed and the laptop is powered by AC only, the CPU downclocks to the lowest multiplier and remains locked in low speed. This happens irrespective of the scaling method in use (kernelspace or userspace) and of the frequency governor selected (ondemand, performance, etc.).

Output of cpufreq-info (on AC power without battery):

analyzing CPU 0:
driver: centrino
CPUs which need to switch frequency at the same time: 0 1
hardware limits: 1000 MHz - 1.83 GHz
available frequency steps: 1.83 GHz, 1.33 GHz, 1000 MHz
available cpufreq governors: ondemand, userspace, powersave, performance
'''current policy: frequency should be within 1000 MHz and 1000 MHz.'''
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency is 1000 MHz (asserted by call to hardware).

analyzing CPU 1:
driver: centrino
CPUs which need to switch frequency at the same time: 0 1
hardware limits: 1000 MHz - 1.83 GHz
available frequency steps: 1.83 GHz, 1.33 GHz, 1000 MHz
available cpufreq governors: ondemand, userspace, powersave, performance
'''current policy: frequency should be within 1000 MHz and 1000 MHz.'''
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency is 1000 MHz (asserted by call to hardware).

Output of cpufreq-info (on AC power with battery plugged in):

analyzing CPU 0:
driver: centrino
CPUs which need to switch frequency at the same time: 0 1
hardware limits: 1000 MHz - 1.83 GHz
available frequency steps: 1.83 GHz, 1.33 GHz, 1000 MHz
available cpufreq governors: ondemand, userspace, powersave, performance
'''current policy: frequency should be within 1000 MHz and 1.83 GHz.'''
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency is 1000 MHz (asserted by call to hardware).

analyzing CPU 1:
driver: centrino
CPUs which need to switch frequency at the same time: 0 1
hardware limits: 1000 MHz - 1.83 GHz
available frequency steps: 1.83 GHz, 1.33 GHz, 1000 MHz
available cpufreq governors: ondemand, userspace, powersave, performance
'''current policy: frequency should be within 1000 MHz and 1.83 GHz.'''
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency is 1000 MHz (asserted by call to hardware).

==Solution==
Other than using the laptop with the battery pack always inserted, no solution is known at this point.

Problem with CPU frequency scaling

2008-03-07T02:51:10Z

Fredigundis: /* Solution */

{{stub}}

==Symptom==
If the battery pack is removed and the laptop is powered by AC only, the CPU downclocks and remains locked in low speed. This happens irrespective of the scaling method in use (kernelspace or userspace) and of the frequency governor selected (ondemand, performance, etc.).

Output of cpufreq-info (on AC power without battery):

analyzing CPU 0:
driver: centrino
CPUs which need to switch frequency at the same time: 0 1
hardware limits: 1000 MHz - 1.83 GHz
available frequency steps: 1.83 GHz, 1.33 GHz, 1000 MHz
available cpufreq governors: ondemand, userspace, powersave, performance
'''current policy: frequency should be within 1000 MHz and 1000 MHz.'''
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency is 1000 MHz (asserted by call to hardware).

analyzing CPU 1:
driver: centrino
CPUs which need to switch frequency at the same time: 0 1
hardware limits: 1000 MHz - 1.83 GHz
available frequency steps: 1.83 GHz, 1.33 GHz, 1000 MHz
available cpufreq governors: ondemand, userspace, powersave, performance
'''current policy: frequency should be within 1000 MHz and 1000 MHz.'''
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency is 1000 MHz (asserted by call to hardware).

Output of cpufreq-info (on AC power with battery plugged in):

analyzing CPU 0:
driver: centrino
CPUs which need to switch frequency at the same time: 0 1
hardware limits: 1000 MHz - 1.83 GHz
available frequency steps: 1.83 GHz, 1.33 GHz, 1000 MHz
available cpufreq governors: ondemand, userspace, powersave, performance
'''current policy: frequency should be within 1000 MHz and 1.83 GHz.'''
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency is 1000 MHz (asserted by call to hardware).

analyzing CPU 1:
driver: centrino
CPUs which need to switch frequency at the same time: 0 1
hardware limits: 1000 MHz - 1.83 GHz
available frequency steps: 1.83 GHz, 1.33 GHz, 1000 MHz
available cpufreq governors: ondemand, userspace, powersave, performance
'''current policy: frequency should be within 1000 MHz and 1.83 GHz.'''
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency is 1000 MHz (asserted by call to hardware).

==Solution==
Other than using the laptop with the battery pack always inserted, no solution is known at this point.

Problem with CPU frequency scaling

2008-03-07T02:48:50Z

Fredigundis: /* Symptom */

{{stub}}

==Symptom==
If the battery pack is removed and the laptop is powered by AC only, the CPU downclocks and remains locked in low speed. This happens irrespective of the scaling method in use (kernelspace or userspace) and of the frequency governor selected (ondemand, performance, etc.).

Output of cpufreq-info (on AC power without battery):

analyzing CPU 0:
driver: centrino
CPUs which need to switch frequency at the same time: 0 1
hardware limits: 1000 MHz - 1.83 GHz
available frequency steps: 1.83 GHz, 1.33 GHz, 1000 MHz
available cpufreq governors: ondemand, userspace, powersave, performance
'''current policy: frequency should be within 1000 MHz and 1000 MHz.'''
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency is 1000 MHz (asserted by call to hardware).

analyzing CPU 1:
driver: centrino
CPUs which need to switch frequency at the same time: 0 1
hardware limits: 1000 MHz - 1.83 GHz
available frequency steps: 1.83 GHz, 1.33 GHz, 1000 MHz
available cpufreq governors: ondemand, userspace, powersave, performance
'''current policy: frequency should be within 1000 MHz and 1000 MHz.'''
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency is 1000 MHz (asserted by call to hardware).

Output of cpufreq-info (on AC power with battery plugged in):

analyzing CPU 0:
driver: centrino
CPUs which need to switch frequency at the same time: 0 1
hardware limits: 1000 MHz - 1.83 GHz
available frequency steps: 1.83 GHz, 1.33 GHz, 1000 MHz
available cpufreq governors: ondemand, userspace, powersave, performance
'''current policy: frequency should be within 1000 MHz and 1.83 GHz.'''
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency is 1000 MHz (asserted by call to hardware).

analyzing CPU 1:
driver: centrino
CPUs which need to switch frequency at the same time: 0 1
hardware limits: 1000 MHz - 1.83 GHz
available frequency steps: 1.83 GHz, 1.33 GHz, 1000 MHz
available cpufreq governors: ondemand, userspace, powersave, performance
'''current policy: frequency should be within 1000 MHz and 1.83 GHz.'''
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency is 1000 MHz (asserted by call to hardware).

==Solution==
With the battery pack inserted, the CPU frequency scales up/down as expected.

Problem with CPU frequency scaling

2008-03-05T03:53:44Z

Fredigundis: â†Created page with '{{stub}} ==Symptom== If the battery pack is removed and the laptop is powered by AC only, the CPU frequency remains locked in low speed. This happens irrespective of the ...'

{{stub}}

==Symptom==
If the battery pack is removed and the laptop is powered by AC only, the CPU frequency remains locked in low speed. This happens irrespective of the scaling method in use (kernelspace or userspace) and of the frequency governor selected (ondemand, performance, etc.).

Output of cpufreq-info (on AC power without battery):

analyzing CPU 0:
driver: centrino
CPUs which need to switch frequency at the same time: 0 1
hardware limits: 1000 MHz - 1.83 GHz
available frequency steps: 1.83 GHz, 1.33 GHz, 1000 MHz
available cpufreq governors: ondemand, userspace, powersave, performance
'''current policy: frequency should be within 1000 MHz and 1000 MHz.'''
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency is 1000 MHz (asserted by call to hardware).

analyzing CPU 1:
driver: centrino
CPUs which need to switch frequency at the same time: 0 1
hardware limits: 1000 MHz - 1.83 GHz
available frequency steps: 1.83 GHz, 1.33 GHz, 1000 MHz
available cpufreq governors: ondemand, userspace, powersave, performance
'''current policy: frequency should be within 1000 MHz and 1000 MHz.'''
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency is 1000 MHz (asserted by call to hardware).

Output of cpufreq-info (on AC power with battery plugged in):

analyzing CPU 0:
driver: centrino
CPUs which need to switch frequency at the same time: 0 1
hardware limits: 1000 MHz - 1.83 GHz
available frequency steps: 1.83 GHz, 1.33 GHz, 1000 MHz
available cpufreq governors: ondemand, userspace, powersave, performance
'''current policy: frequency should be within 1000 MHz and 1.83 GHz.'''
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency is 1000 MHz (asserted by call to hardware).

analyzing CPU 1:
driver: centrino
CPUs which need to switch frequency at the same time: 0 1
hardware limits: 1000 MHz - 1.83 GHz
available frequency steps: 1.83 GHz, 1.33 GHz, 1000 MHz
available cpufreq governors: ondemand, userspace, powersave, performance
'''current policy: frequency should be within 1000 MHz and 1.83 GHz.'''
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency is 1000 MHz (asserted by call to hardware).

==Solution==
With the battery pack inserted, the CPU frequency scales up/down as expected.

Known Problems

2008-03-05T03:16:47Z

Fredigundis: /* Power Management, AC-adapter or Battery Problems */

{| width="100%"
|style="vertical-align:top;padding-right:20px;width:10px;white-space:nowrap;" | __TOC__
|style="vertical-align:top" |
Information on known problems with certain ThinkPad models.
|}
==Display Problems==
*[[Problem with unusable console | Console unusable]] <tt>(models with savage video chipset: T2x, A22e)</tt>
*[[Problem with Pixel Error | Dead pixels on TFT displays]] <tt>(all models)</tt>
*[[Problem with DVI throughput | DVI throughput on port replicators and docks]] <tt>(models from 2000-2004)</tt>
*[[Problems with fglrx | fglrx problems]] <tt>(ATI Radeon models)</tt>
*[[Problem with garbled screen | Garbled Screen]] <tt>(T40, T41, T42, R32, R40, R50p, R51, A30, A31, A31p)</tt>
*[[Problem with broken inverter | Inverter broken]] <tt>(all models)</tt>
*[[Problem with key and trackpoint markings on the display | Key and Trackpoint markings on display]]
*[https://bugs.freedesktop.org/show_bug.cgi?id=2187 Radeon 7500 "DynamicClocks" randomly hangs] <tt>(TP T4x, Xorg-X11 bug report)</tt>
*[[Problem with red display shadow | Red shadow on display]] <tt>(TP T41p)</tt>
*[[Problem with red tinted display | Red tinted display]] <tt>(TP 23)</tt>
*[[Problem with black X | Unmovable square black X in X]] <tt>(TP T2x)</tt>
*[[Problem with video related system lockup | System Lockups related to video adapter]] <tt>(TP T2x)</tt>
*[[Problem with video related system lockup II | System Lockups related to video adapter T42]] <tt>(TP T42, T42p)</tt>
*[[Problem with ati driver in xorg 6.9.x | System lockup soon after starting xorg 6.9.x ]] <tt>(TP T4x)</tt>
*[[Problem with video output switching | Video output switching]]
*[[Problem with LCD brightness buttons | Video brightness up keys don't work or cause crashes]]

==Harddisk Drive related Problems==
*[[Problem with APS harddisk parking|APS harddisk parking]] <tt>(models featuring APS)</tt>
*[[Problem with too large harddrive|BIOS hangs with harddrive sized over 8G]] <tt>(560)</tt>
*[[Problem with hard drive clicking | Clicking Hard Drive]] <tt>(models with Hitachi's 5k80 hard drive)</tt>
*[[Problem with non-ThinkPad hard disks|Non-ThinkPad hard disks]] <tt>(T43, X41, R52)</tt>
*[[Problems with SATA and Linux|SATA and Linux]] <tt>(T43, X41, R52, Z60)</tt>

==Network Problems==
*[[Problem with 3Com 10/100 Ethernet card not being recognized|3Com 10/100 Ethernet card not recognized]] <tt>(models with that card)</tt>
*[[Problem with unauthorized MiniPCI network card|"Unauthorized" MiniPCI Wireless Network card error (Error 1802)]] <tt>(Recent TPs)</tt>
*[[Cisco Aironet Wireless 802.11b]] fails to work with certain firmware versions
*[[Problem with error 01C9 - More than one Ethernet devices | Error 01C9: More than one Ethernet Devices are found (Atheros WLAN MiniPCI)]] <tt>(T23, T30, A31p, R40 and others)</tt>
*[[Problem with e1000: EEPROM Checksum Is Not Valid]] <tt>(T60, X60, may be others)</tt>
*[[Problem with e1000: 99.9% packet loss on 7.x drivers]] <tt>(Recent TPs)</tt>
*[[Problem with 3945ABG: Internal wifi cannot associate with AP]] <tt>(T60, probably others)</tt>
*[[Need to disable V90/V92/56K modem speed]] ([[IBM_Integrated_Bluetooth_III_with_56K_Modem_(BMDC-2)|BMDC-2]] on X40)

==Power Management, AC-adapter or Battery Problems==
*[[Problem with ThinkPad 600 batteries | 600 series Battery dying prematurely]] <tt>(TP 600/E/X)</tt>
*[[Damage in 56W AC-Adapter, plastic housing melted |AC-Adapter damaged, plastic housing melted]] <tt>(240, 390, i and s models)</tt>
*[[Problems with ACPI suspend-to-ram|ACPI suspend-to-ram]] <tt>(ACPI sleep troubles)</tt>
**[[Problem with display remaining black after resume|Blank display after resume]] <tt>(various models)</tt>
**[[Problem with high power drain in ACPI sleep | High power drain in ACPI sleep]] <tt>(various models)</tt>
**[[Problem with LCD backlight remaining on during ACPI sleep | LCD backlight remaining on during ACPI sleep]] <tt>(various models)</tt>
*[[Problem with fan noise | Fan noise]] <tt>(TP T4x/p, TP R5x/p)</tt>
*[[Problem with checking battery status | Checking battery status causes mouse to jerk around]] <tt>(R31)</tt>
*[[Battery drains despite seemingly being charged]] <tt>(A/C adapter issues)</tt>
*[[Problem with high pitch noises | High pitch noises]] <tt>(several models)</tt>
*[[Problem with CPU frequency scaling | CPU frequency scaling locks up when on AC power only]] <tt>(several models)</tt>

==Sound Problems==
*[[Problem with broken sound on ThinkPad 600 | Broken sound on ThinkPad 600/E]] <tt>(TP 600/E/X, 770Z)</tt>
*[[Problem with audio jacks | Audio jacks not working properly]] <tt>(TP T43)</tt>
*[[Problem with ALSA audio output | No audio heard with kernel 2.6.11+/ALSA]] <tt>(TP T43, T40)</tt>
*[[Problem with audio clipping|Audio clipping]] <tt>(TP T43)</tt>
*[[Problem with no sound on ThinkPad R60e | No Sound on ThinkPad R60e and T60]] <tt>(R60e, T60)</tt>

==Misc Problems==
*[[System randomly freezes and requires hard reset]] <tt>(X61s and all newer systems including X,T,R,Z series)</tt>
*[[Problem with Bending / Twisting|Casing malformed by bending/twising]] <tt>(X41)</tt>
*[[Problem with failing memory slot]] <tt>(T30, and some T2x models)</tt>
*[[Problem with Dock USB Ports | Dock USB Ports]] <tt>(T30/X21)</tt>
*[[High-pitch noise from AC-Adapter]] <tt>(T60/p)</tt>
*[[Problem with lm-sensors | lm_sensors kills ThinkPads]] <tt>(TP 570E, 770X/Z, 600E/X, 240, X20)</tt>
*[[Problem with USB 2.0 | USB 2.0 problems]] <tt>(T40/T41)</tt>
*[[Embedded Controller Firmware#Firmware_issues|Firmware issues]]
*[[Problem with hot surfaces|Problem with hot surfaces]] <tt>(T43)</tt>
*[[Problem with disabled VT]] <tt>(Z61t, X60, X60s)</tt>
*[[Unable to create recovery cds when another python is installed on the system]] <tt>(T43p)</tt>