Bug 4763
Summary: | loading of acpi processor.ko module hangs/freezes system instantly | ||
---|---|---|---|
Product: | ACPI | Reporter: | Samuel Berner (bottlecruiser) |
Component: | Config-Processors | Assignee: | Shaohua (shaohua.li) |
Status: | CLOSED CODE_FIX | ||
Severity: | normal | CC: | acpi-bugzilla |
Priority: | P2 | ||
Hardware: | i386 | ||
OS: | Linux | ||
Kernel Version: | 2.6.11.11 | Subsystem: | |
Regression: | --- | Bisected commit-id: | |
Attachments: |
dmesg -s40000
dmidecode acpidmp lscpi -vv patch to blacklist C3 tweaked patch |
Description
Samuel Berner
2005-06-19 16:35:15 UTC
Created attachment 5192 [details]
dmesg -s40000
from kernel 2.6.11.11 immedeately after a system boot
Created attachment 5193 [details]
dmidecode
created under the same conditions as the attachment before
Created attachment 5194 [details]
acpidmp
created under the same conditions as the attachment before
Created attachment 5195 [details]
lscpi -vv
created under the same conditions as the attachment before
I guess it's the bad of CST. Please try load processor module with parameter 'nocst=1'. I tried it twice. with that parameter: - the first time it freezed immediately (using "modprobe processor nocst=1" (quotes for clarity)) - the second time it freezed about 3-5 seconds after loading the module ( I used insmod here, because I wasn't entirely sure if the first attempt was correct (altough it must have been acording to the manpage)) ("insmod /lib/modules/.../acpi/processor.ko nocst=1" (again quotes for clarity)) Any other ideas? Ok, how about the parameter 'max_cstate=1'? You can try different value such as 2,3 for the parameter. max_cstate=1 worked max_cstate=2 worked also (I tested the /proc/acpi/processor interface both times) max_cstate=3 makes my system freeze (after a few seconds) The BIOS has a setting for the C3 state, which I have enabled a long time ago. But my old kernel didn't seem to use it. Do you think this is a hardware problem? Or would it probably be possible to get the C3 state working? We possibly can't make your C3 work. Did your system work in WinXP (sorry)? It's more likely a BIOS bug to me. C3 is actually sample, it just reads an IO port, and your system hangs when reading the IO port. I think we should blacklist C3 in this system. I have a W2K partition I can boot into. But I don't know how I could find out if W2K is really using the C3 state. Can you give me advice how I could do that? Do I need a special tool for that? Thanks. Created attachment 5205 [details]
patch to blacklist C3
No, there isn't any tool to do this. If win doesn't hang, we can't make any
conclusion.
I think it's not worthy digging this out. IIRC, only mobile CPU (Pentium M) has
C3 support. P4's C3 might not be a real C3. Blacklist C3 on this system should
have no impact. Could you please try the patch? Thanks!
Ok. I've applied the patch, compiled all acpi modules into the kernel image, booted from it and it works. Thank you for your help. Created attachment 5412 [details]
tweaked patch
updated patch to re-name no_c2c3() to be set_max_cstate().
applied to-linus
shipped in 2.6.13-rc5 -- closing. |