From: "Zdenek Kabelac" <zdenek.kabelac@gmail.com>
To: "Kernel development list" <linux-kernel@vger.kernel.org>
Subject: BUG: using smp_processor_id() during suspend with 2.6.25-rc8
Date: Mon, 7 Apr 2008 15:25:47 +0200 [thread overview]
Message-ID: <c4e36d110804070625n17eb44e1nbb5558f500f13438@mail.gmail.com> (raw)
Hello
This has appeared in my kernel log:
Zdenek
----
hwsleep-0322 [00] enter_sleep_state : Entering sleep state [S3]
BUG: using smp_processor_id() in preemptible [00000000] code: pm-suspend/18791
caller is do_machine_check+0xa9/0x500
Pid: 18791, comm: pm-suspend Not tainted 2.6.25-rc8 #32
Call Trace:
[debug_smp_processor_id+196/208] debug_smp_processor_id+0xc4/0xd0
[do_machine_check+169/1280] do_machine_check+0xa9/0x500
[init_8259A+27/256] ? init_8259A+0x1b/0x100
[mce_init+86/240] mce_init+0x56/0xf0
[mce_resume+11/16] mce_resume+0xb/0x10
[__sysdev_resume+32/96] __sysdev_resume+0x20/0x60
[sysdev_resume+88/144] sysdev_resume+0x58/0x90
[device_power_up+9/16] device_power_up+0x9/0x10
[suspend_devices_and_enter+327/416] suspend_devices_and_enter+0x147/0x1a0
[enter_state+326/464] enter_state+0x146/0x1d0
[state_store+186/256] state_store+0xba/0x100
[kobj_attr_store+23/32] kobj_attr_store+0x17/0x20
[sysfs_write_file+202/320] sysfs_write_file+0xca/0x140
[vfs_write+203/368] vfs_write+0xcb/0x170
[sys_write+80/144] sys_write+0x50/0x90
[system_call_after_swapgs+123/128] system_call_after_swapgs+0x7b/0x80
Extended CMOS year: 2000
BUG: using smp_processor_id() in preemptible [00000000] code: pm-suspend/18791
caller is retrigger_next_event+0x1c/0xf0
Pid: 18791, comm: pm-suspend Not tainted 2.6.25-rc8 #32
Call Trace:
[debug_smp_processor_id+196/208] debug_smp_processor_id+0xc4/0xd0
[retrigger_next_event+28/240] retrigger_next_event+0x1c/0xf0
[_spin_unlock+48/96] ? _spin_unlock+0x30/0x60
[hres_timers_resume+30/80] hres_timers_resume+0x1e/0x50
[timekeeping_resume+293/352] timekeeping_resume+0x125/0x160
[__sysdev_resume+32/96] __sysdev_resume+0x20/0x60
[sysdev_resume+88/144] sysdev_resume+0x58/0x90
[device_power_up+9/16] device_power_up+0x9/0x10
[suspend_devices_and_enter+327/416] suspend_devices_and_enter+0x147/0x1a0
[enter_state+326/464] enter_state+0x146/0x1d0
[state_store+186/256] state_store+0xba/0x100
[kobj_attr_store+23/32] kobj_attr_store+0x17/0x20
[sysfs_write_file+202/320] sysfs_write_file+0xca/0x140
[vfs_write+203/368] vfs_write+0xcb/0x170
[sys_write+80/144] sys_write+0x50/0x90
[system_call_after_swapgs+123/128] system_call_after_swapgs+0x7b/0x80
BUG: using smp_processor_id() in preemptible [00000000] code: pm-suspend/18791
caller is retrigger_next_event+0x84/0xf0
Pid: 18791, comm: pm-suspend Not tainted 2.6.25-rc8 #32
Call Trace:
[debug_smp_processor_id+196/208] debug_smp_processor_id+0xc4/0xd0
[retrigger_next_event+132/240] retrigger_next_event+0x84/0xf0
[hres_timers_resume+30/80] hres_timers_resume+0x1e/0x50
[timekeeping_resume+293/352] timekeeping_resume+0x125/0x160
[__sysdev_resume+32/96] __sysdev_resume+0x20/0x60
[sysdev_resume+88/144] sysdev_resume+0x58/0x90
[device_power_up+9/16] device_power_up+0x9/0x10
[suspend_devices_and_enter+327/416] suspend_devices_and_enter+0x147/0x1a0
[enter_state+326/464] enter_state+0x146/0x1d0
[state_store+186/256] state_store+0xba/0x100
[kobj_attr_store+23/32] kobj_attr_store+0x17/0x20
[sysfs_write_file+202/320] sysfs_write_file+0xca/0x140
[vfs_write+203/368] vfs_write+0xcb/0x170
[sys_write+80/144] sys_write+0x50/0x90
[system_call_after_swapgs+123/128] system_call_after_swapgs+0x7b/0x80
Enabling non-boot CPUs ...
lockdep: fixing up alternatives.
SMP alternatives: switching to SMP code
Booting processor 1/2 APIC 0x1
next reply other threads:[~2008-04-07 13:25 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-07 13:25 Zdenek Kabelac [this message]
2008-04-07 21:54 ` Jiri Kosina
2008-04-07 22:02 ` Andi Kleen
2008-04-07 22:04 ` Jiri Kosina
2008-04-07 22:12 ` Andi Kleen
2008-04-07 22:11 ` Jiri Kosina
2008-04-07 22:14 ` Jiri Kosina
2008-04-07 22:23 ` Andi Kleen
2008-04-07 22:29 ` Rafael J. Wysocki
2008-04-07 22:33 ` Jiri Kosina
2008-04-07 22:53 ` Zdenek Kabelac
2008-04-07 23:10 ` Rafael J. Wysocki
2008-04-08 8:09 ` Jiri Kosina
2008-04-10 11:16 ` Zdenek Kabelac
2008-04-07 22:56 ` Rafael J. Wysocki
2008-04-10 9:45 ` Pavel Machek
2008-04-10 23:25 ` Jiri Kosina
2008-04-11 10:49 ` Pavel Machek
2008-04-11 10:51 ` Ingo Molnar
2008-04-11 10:54 ` Pavel Machek
2008-04-11 11:09 ` Ingo Molnar
2008-04-12 9:51 ` Pavel Machek
2008-04-11 15:29 ` Rafael J. Wysocki
2008-04-11 11:37 ` Andi Kleen
2008-04-11 15:27 ` Rafael J. Wysocki
2008-04-07 22:35 ` Andi Kleen
2008-04-07 22:54 ` Rafael J. Wysocki
2008-04-11 10:25 ` Ingo Molnar
2008-04-11 10:34 ` Jiri Kosina
2008-04-11 10:40 ` Ingo Molnar
2008-04-11 10:39 ` Andi Kleen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c4e36d110804070625n17eb44e1nbb5558f500f13438@mail.gmail.com \
--to=zdenek.kabelac@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®