Bug 5399
Summary: | noise due to processor module - Dell Latitude D510 | ||
---|---|---|---|
Product: | ACPI | Reporter: | Jan Rasche (xcomm) |
Component: | Power-Processor | Assignee: | Len Brown (lenb) |
Status: | REJECTED DOCUMENTED | ||
Severity: | high | CC: | acpi-bugzilla |
Priority: | P2 | ||
Hardware: | i386 | ||
OS: | Linux | ||
Kernel Version: | 2.6.13.3 | Subsystem: | |
Regression: | --- | Bisected commit-id: |
Description
Jan Rasche
2005-10-08 05:24:45 UTC
>Most recent kernel where this bug did not occur: 2.6.13.3
This bug is still in 2.6.13.3 - I did overead the >>>not<<< when posting the bug.
This bug is still in 2.6.13.4 Some hardware sings when subjected to rapid changes in charge or temperature. please paste the contents of /proc/acpi/processor/*/power into this bug report. then # echo 1 >/sys/module/processor/parameters/max_cstate and report if the sound goes away. If so, try successively larger numbers until it comes back. If that doesn't do it, then please cat /sys/devices/system/cpu/cpu0/cpufreq/* into this bug report. xcomm:~# cat /proc/acpi/processor/CPU0/power active state: C3 max_cstate: C8 bus master activity: 00001000 states: C1: type[C1] promotion[C2] demotion[--] latency[001] usage[ 00000010] C2: type[C2] promotion[C3] demotion[C1] latency[001] usage[ 00544467] *C3: type[C3] promotion[C4] demotion[C2] latency[085] usage[ 00189168] C4: type[C3] promotion[--] demotion[C3] latency[185] usage[ 00525237] Hi Len, First of many thanks to you for your help with this! If I echo 1 or 2 than there is no noise, when echo 3 is send, the noice is back. xcomm:~# echo 3 > /sys/module/processor/parameters/max_cstate xcomm:~# cat /sys/devices/system/cpu/cpu0/cpufreq/* 0 800000 1600000 800000 1600000 1333000 1067000 800000 userspace performance 800000 centrino performance 800000 800000 http://www.thinkwiki.org/wiki/Problem_with_high_pitch_noises -> Solutions for CPU-triggered noise -> re-configure the kernel ( -> Processor type and features -> Timer frequency -> 250 or 100 HZ instead of 1000 HZ) I'd suggest closing this bug. |