Experienced after pulling the latest mainline commits after a couple weeks of vacation. Please forgive me if this is incorrectly filed, I'm guessing that it's ACPI related due to the notable presence in the BUG() call trace. Also, not sure if this is related to Bug#16542 or not, as in that case the reporter claimed it could not be reproduced after a reboot and i have managed to do so, and the stacktrace is different in the two cases. [ 0.008629] ACPI: Core revision 20100702 [ 0.013140] BUG: scheduling while atomic: swapper/0/0x10000002 [ 0.013171] Modules linked in: [ 0.013175] Pid: 0, comm: swapper Not tainted 2.6.35+ #3 [ 0.013176] Call Trace: [ 0.013182] [<ffffffff812d1470>] ? schedule+0xd0/0x5cc [ 0.013186] [<ffffffff8119ab60>] ? acpi_os_release_object+0x9/0xe [ 0.013190] [<ffffffff8103d641>] ? __cond_resched+0x13/0x1f [ 0.013193] [<ffffffff81036c7f>] ? should_resched+0x5/0x26 [ 0.013195] [<ffffffff812d1a6c>] ? _cond_resched+0x16/0x1d [ 0.013198] [<ffffffff811b8563>] ? acpi_ps_complete_op+0x257/0x26d [ 0.013201] [<ffffffff811b8ed6>] ? acpi_ps_parse_loop+0x95d/0x96b [ 0.013204] [<ffffffff812d2f9b>] ? _raw_spin_unlock_irqrestore+0x32/0x40 [ 0.013207] [<ffffffff811b7ea3>] ? acpi_ps_parse_aml+0x8e/0x29a [ 0.013210] [<ffffffff811b66ac>] ? acpi_ns_one_complete_parse+0x108/0x125 [ 0.013214] [<ffffffff81060c2e>] ? up+0xe/0x36 [ 0.013216] [<ffffffff811b66e3>] ? acpi_ns_parse_table+0x1a/0x37 [ 0.013219] [<ffffffff811b3add>] ? acpi_ns_load_table+0x3d/0x7c [ 0.013222] [<ffffffff811bac65>] ? acpi_load_tables+0x9b/0x156 [ 0.013225] [<ffffffff816abb8e>] ? acpi_early_init+0x6c/0xf7 [ 0.013229] [<ffffffff81686d43>] ? start_kernel+0x3c8/0x3dd [ 0.013232] [<ffffffff816863ba>] ? x86_64_start_kernel+0xf9/0x106 [ 0.020062] Setting APIC routing to flat [ 0.020539] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1 [ 0.063359] CPU0: AMD Phenom(tm) II X3 720 Processor stepping 02
I have the fix but it didn't get merged. I'll merge it with a 2.6.35.1 backport. *** This bug has been marked as a duplicate of bug 16210 ***