Most recent kernel where this bug did not occur: don't know Distribution: Debian/unstable Hardware Environment: Epox 8rda3+ (Nforce 2) Motherboard + Athlon XP 3200+ (Barton) + linux on a sata-hd connected to a sil 3112a port Software Environment: Linux/2.6.13/Debian Problem Description: The C2 idle state capability isn't detected anymore. It defenetly worked with some older kernel but i can't say with which it stoped to work, cause i didn't controlled it for some time. but it defenetly don't work with 2.6.12.5, 2.6.13-rc6, 2.6.13-rc6-mm1 or 2.6.13.
Created attachment 5798 [details] output from dmesg -s40000 output from dmesg -s40000
Created attachment 5799 [details] output from dmidecode
Created attachment 5800 [details] output from acpidump
Created attachment 5801 [details] output from lspci -vv
Created attachment 5802 [details] output from cat /proc/interrupts
Does patch in bug #4485 help?
i tried #4485 patch in post #9 it doesn't help ... sorry ...
It will help if you can give the kernel version where C2 states did work. Also the acpidump/disassembly from this system will help too. Thanks.
any difference if the processor module is loaded with nocst? eg modprobe processor nocst=1
hmm ... ok the c2 state definetly worked some time. i am the author of the athlon powersaving howto and i know that it worked ... BUT: all kernels i checked this morning DIDN't detect the C2 state and i checked every kernel i used back to 2.6.2 or so ... so it looks like there is another cause ... maybe a bios update ... or some sunspots ... the problem is i can't flash back to an old bios to check, cause i need the newest to use my sata drive ... any suggestions where i could look ?
I don't see either FADT or CST in acpi dump that you have attached. So, there is no way for OS to find out about the C-state capability of this system. Probably BIOS update is the issue. You will have to check with the BIOS provider.
yes ... i also think its a bios issue ... i puzzled a little bit with it last year, but came to no definite solution. chistmas brought me a new amd64 system and so from my perspective we can close this bug cause i don't have the athlon XP computer anymore.