Suspend enables only CPU0 after wake up

[Christian Schneiker]

Binary package hint: linux-source-2.6.22

My Dell XPS M1330 enables only one core after suspend. I've got an uptodate Gutsy with Kernel 2.6.22-12-generic x86_64. It's also not possible to change to scaling governor.
Here my /var/log/messages

Sep 27 02:40:06 kingslanding kernel: [ 0.458656] Enabling non-boot CPUs ...
Sep 27 02:40:06 kingslanding kernel: [ 0.459285] atkbd.c: Unknown key pressed (translated set 2, code 0x88 on isa0060/serio0).
Sep 27 02:40:06 kingslanding kernel: [ 0.459291] atkbd.c: Use 'setkeycodes e008 <keycode>' to make it known.
Sep 27 02:40:06 kingslanding kernel: [ 0.459634] atkbd.c: Unknown key pressed (translated set 2, code 0x88 on isa0060/serio0).
Sep 27 02:40:06 kingslanding kernel: [ 0.459640] atkbd.c: Use 'setkeycodes e008 <keycode>' to make it known.
Sep 27 02:40:06 kingslanding kernel: [ 0.459934] SMP alternatives: switching to SMP code
Sep 27 02:40:06 kingslanding kernel: [ 0.460182] Booting processor 1/2 APIC 0x1
Sep 27 02:40:06 kingslanding kernel: [ 0.471233] Initializing CPU#1
Sep 27 02:40:06 kingslanding kernel: [ 0.547518] Calibrating delay using timer specific routine.. 4387.96 BogoMIPS (lpj=8775936)
Sep 27 02:40:06 kingslanding kernel: [ 0.547532] CPU: L1 I cache: 32K, L1 D cache: 32K
Sep 27 02:40:06 kingslanding kernel: [ 0.547537] CPU: L2 cache: 4096K
Sep 27 02:40:06 kingslanding kernel: [ 0.547542] CPU 1/1 -> Node 0
Sep 27 02:40:06 kingslanding kernel: [ 0.547546] CPU: Physical Processor ID: 0
Sep 27 02:40:06 kingslanding kernel: [ 0.547549] CPU: Processor Core ID: 1
Sep 27 02:40:06 kingslanding kernel: [ 0.548720] Intel(R) Core(TM)2 Duo CPU T7500 @ 2.20GHz stepping 0a
Sep 27 02:40:06 kingslanding kernel: [ 0.551845] ACPI Error (psloop-0136): Found unknown opcode FE at AML address ffffc20000ab23ca offset 7, ignoring [20070126]
Sep 27 02:40:06 kingslanding kernel: [ 0.551857] ACPI Error (psloop-0136): Found unknown opcode 16 at AML address ffffc20000ab23cc offset 9, ignoring [20070126]
Sep 27 02:40:06 kingslanding kernel: [ 0.551871] ACPI Error (psloop-0136): Found unknown opcode 19 at AML address ffffc20000ab23d0 offset D, ignoring [20070126]
Sep 27 02:40:06 kingslanding kernel: [ 0.551888] ACPI Error (psargs-0355): [C\376\377^I] Namespace lookup failure, AE_NOT_FOUND
Sep 27 02:40:06 kingslanding kernel: [ 0.551899] ACPI Error (psparse-0551): Method parse/execution failed [\_PR_.CPU1._PCT] (Node ffff81007cfa3d60), AE_NOT_FOUND
Sep 27 02:40:06 kingslanding kernel: [ 0.551983] ACPI Exception (processor_perflib-0170): AE_NOT_FOUND, Evaluating _PCT [20070126]
Sep 27 02:40:06 kingslanding kernel: [ 0.551989] CPU1 is up
Sep 27 02:40:06 kingslanding kernel: [ 0.562877] PCI: Enabling device 0000:00:1a.0 (0000 -> 0001)
Sep 27 02:40:06 kingslanding kernel: [ 0.562881] ACPI: PCI Interrupt 0000:00:1a.0[A] -> GSI 20 (level, low) -> IRQ 20

After removing the modules processor, acpi_cpufreq it's sometimes working again.

[Christian Schneiker (chrisschneiker)]

Sorry, it's sometimes working after loading these modules again. :-)

[robe (r-evert)]

Hi, I also see this bug.

How do you reload processor and acpi_cpufreq? I don't get the procs that are using them.

And how is suspend to disk working for you? Reliable?

[Gabriel Ambuehl (gabriel-ambuehl)]

I see the same with my Latitude D830 on 32bit Kernel. Additionally, it seems like the CPU is locked at lowest speed but that's probably because it can't switch just one core...

[Gabriel Ambuehl (gabriel-ambuehl)]

This might be a kernel bug, I'm seeing the exact same symptom with a 2.6.23 I
compiled myself.

[Vu Ngoc San (san-vu-ngoc)]

I have the same issue on my d630.

Here is a (dirty) fix:

add the attached file in
/etc/acpi/resume.d/97-d630-resume.sh

It seems to work reliably for me.

Btw, it may be related to
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/138465
and
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/88899

[Launchpad Janitor (janitor)]

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!