Distribution: Debian/sid Hardware Environment: Asus M2400N (Pentium M 1.3GHz) Software Environment: Debian kernel-image-2.6.6-1-686 & vanilla 2.6.6 Problem Description: When compiling a custom kernel v2.6.6 with cpufreq support and speedstep-centrino=y (which works like a charm with previous kernel versions), my machine panics at boot time. I was not able to transcribe the whole call trace from the screen because I couldn't scroll up. Today I installed the package kernel-image-2.6.6-1.686 (config attached) from Debian unstable which comes with cpufreq compiled as module. The machine booted up just fine, but without cpufreq support. modprobing speedstep_centrino resulted in a kernel oops and a hanging machine. I tried to shut down using the power button, but that failed, too. Luckily, this time the oops made it to syslog (attached). Steps to reproduce: Compile 2.6.6 w/ attached config (esp. CONFIG_X86_SPEEDSTEP_CENTRINO=y) and boot on Asus M2400N.
Created attachment 2949 [details] complete syslog from bootup to oops
Created attachment 2950 [details] kernel config for 2.6.6 (taken from debian kernel package 2.6.6-1-686)
I was just about entering this bug, too. Vs. 2.6.5/2.6.6 in FC2/FC2-devel and also 2.6.6-mm5 that I tried as reference. Out of curiosity: Which BIOS version are you using? 0206 has had problems in the past, especially with the local APIC, the new 0208 version seems to fix the lapic problems, it still exhibits this particular oops, however as a side effect I get problems with ALSA - the semaphore not ready messages discussed in several places but not yet fixed.
I am using the latest BIOS version (v0208, dated 2003/03/08 on Asus website) and I also receive a lot of the "failed to acquire semaphore" messages - even without any Alsa modules loaded. But I think these messages are unrelated to the current problem. I was now successful in booting 2.6.6-bk8 with SpeedStep. The cpufreq modules have not been autoloaded, but I could modprobe speedstep_centrino manually. What I changed was the kernel option CONFIG_X86_SPEEDSTEP_CENTRINO_ACPI to 'n'. At least there should be a hint in the docs that this option doesn't work with the M2N. Currently the help says "If in doubt, say Y" which is why I had it on in my first tries.
Could you attach your acpidump? thanks, -zhen
This is a known issue. Testing patch is filed at https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=121760 Thanks, Luming
Created attachment 2979 [details] acpidmp output on my ASUS M2N with the 0208 BIOS If this is not what you wanted, please let me know.
I can confirm that the referenced patch on redhat bugzilla fixes the problem for me (tested on a 2.6.6-mm5).
fix in RH bugzilla has been integrated into next ACPICA drop -- marking this as resolved.
I tried the patch with 2.6.7-rc1 and it works fine. Thanks a lot.
*** Bug 2781 has been marked as a duplicate of this bug. ***
*** Bug 2843 has been marked as a duplicate of this bug. ***
shipped in ACPICA 20040527 which was included in linux-2.6.9
Created attachment 3965 [details] 2.4 patch extracted just this fix from ACPICA 20040527 for benefit of linux-2.4.