[Linux 2.6.28-rc4] BUG: using smp_processor_id() in preemptible [00000000] code: suspend_to_disk/2934
From: Maciej Rutecki
Date: Wed Nov 12 2008 - 13:30:30 EST
-rc3 works OK
I have this bug during suspend to disk:
[ 188.592151] Enabling non-boot CPUs ...
[ 188.592151] SMP alternatives: switching to SMP code
[ 188.666058] BUG: using smp_processor_id() in preemptible [00000000]
code: suspend_to_disk/2934
[ 188.666064] caller is native_sched_clock+0x2b/0x80
[ 188.666067] Pid: 2934, comm: suspend_to_disk Not tainted 2.6.28-rc4 #1
[ 188.666069] Call Trace:
[ 188.666074] [<c02556ff>] debug_smp_processor_id+0xbf/0xd0
[ 188.666077] [<c010a2db>] native_sched_clock+0x2b/0x80
[ 188.666080] [<c03ae3a0>] init_idle+0x88/0x11a
[ 188.666083] [<c03ad206>] native_cpu_up+0x4a6/0x75a
[ 188.666086] [<c01de808>] sysfs_add_file_mode+0x58/0x90
[ 188.666089] [<c03ad4ba>] do_fork_idle+0x0/0x19
[ 188.666092] [<c014864e>] notifier_call_chain+0x3e/0x80
[ 188.666095] [<c03ae99a>] _cpu_up+0x6a/0x103
[ 188.666097] [<c03a1e75>] enable_nonboot_cpus+0x65/0xa0
[ 188.666101] [<c02cd240>] device_pm_unlock+0x0/0x10
[ 188.666105] [<c0159ba7>] hibernation_snapshot+0x137/0x200
[ 188.666107] [<c0158dff>] freeze_processes+0x4f/0xa0
[ 188.666110] [<c0159d4f>] hibernate+0xdf/0x190
[ 188.666112] [<c0158910>] state_store+0x0/0xd0
[ 188.666115] [<c01589c2>] state_store+0xb2/0xd0
[ 188.666117] [<c0158910>] state_store+0x0/0xd0
[ 188.666120] [<c024b1d4>] kobj_attr_store+0x24/0x30
[ 188.666122] [<c01de221>] sysfs_write_file+0xa1/0x110
[ 188.666124] [<c01de180>] sysfs_write_file+0x0/0x110
[ 188.666127] [<c0198e38>] vfs_write+0xa8/0x140
[ 188.666129] [<c0198fa1>] sys_write+0x41/0x80
[ 188.666131] [<c0103f49>] sysenter_do_call+0x12/0x21
[ 188.666133] [<c03b0000>] acpi_processor_start+0x690/0x69a
[ 188.666136] Booting processor 1 APIC 0x1 ip 0x6000
[ 188.590718] Initializing CPU#1
dmesg and config:
http://unixy.pl/maciek/download/kernel/2.6.28-rc4_smp/
--
Maciej Rutecki
http://www.maciek.unixy.pl
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/