Comment 3 for bug 183033

Revision history for this message
enigma_0Z (enigma-0za) wrote :

--snip--
[ 4758.160000] Disabling non-boot CPUs ...
[ 4758.276000] CPU 1 is now offline
[ 4758.276000] SMP alternatives: switching to UP code
[ 4758.276000] CPU1 is down
[ 4758.276000] PM: Entering mem sleep
[ 4758.276000] Back to C!
[ 4758.276000] PM: Finishing wakeup.
[ 4758.276000] Enabling non-boot CPUs ...
[ 4758.288000] SMP alternatives: switching to SMP code
[ 4758.288000] Booting processor 1/1 eip 3000
[ 4758.296000] Initializing CPU#1
[ 4758.376000] Calibrating delay using timer specific routine.. 3989.92 BogoMIPS (lpj=7979850)
[ 4758.376000] CPU: After generic identify, caps: bfebfbff 20100000 00000000 00000000 0000e3bd 00000000 00000001
[ 4758.376000] monitor/mwait feature present.
[ 4758.376000] CPU: L1 I cache: 32K, L1 D cache: 32K
[ 4758.376000] CPU: L2 cache: 4096K
[ 4758.376000] CPU: Processor Core ID: 1
[ 4758.376000] CPU: After all inits, caps: bfebfbff 20100000 00000000 00003940 0000e3bd 00000000 00000001
[ 4758.376000] CPU1: Intel(R) Core(TM)2 Duo CPU T7300 @ 2.00GHz stepping 0a
[ 4758.376000] ACPI Error (psloop-0136): Found unknown opcode 17 at AML address f88563c3 offset 0, ignoring [20070126]
[ 4758.376000] ACPI Error (psargs-0355): [DBþÿ] Namespace lookup failure, AE_NOT_FOUND
[ 4758.376000] ACPI Error (psparse-0551): Method parse/execution failed [\_PR_.CPU1._PCT] (Node df8323c0), AE_NOT_FOUND
[ 4758.376000] ACPI Exception (processor_perflib-0170): AE_NOT_FOUND, Evaluating _PCT [20070126]
[ 4758.376000] CPU1 is up
[ 4758.380000] Switched to high resolution mode on CPU 1
--snip--

It says that it's disabling CPU1 (a non-boot CPU) so... AFAIK on Intel systems CPU1 is hot (un)plugged on suspend, so when the system resumes, I imagine that CPU0 would in fact be absent from dmesg because there's nothing necessary to do for CPU0. But I'm no ACPI expert.

What makes me wonder is the ACPI errors in the last few lines of the above snip.

Also, when the system resumes, top reports that both processors are receiving load independently, so it's not like it's not working...