From: Pavel Machek <pavel-+ZI9xUNit7I@public.gmane.org>
To: ACPI mailing list
<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>,
kernel list
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: ACPI using smp_processor_id in preemptible code
Date: Sun, 9 Jan 2005 22:10:42 +0100 [thread overview]
Message-ID: <20050109211042.GA1196@elf.ucw.cz> (raw)
Hi!
I enabled CPU hotplug and preemptible debugging... now I get...
BUG: using smp_processor_id() in preemptible [00000001] code:
swapper/0
caller is acpi_processor_idle+0xb/0x235
[<c020ba28>] smp_processor_id+0xa8/0xc0
[<c02338ce>] acpi_processor_idle+0xb/0x235
[<c02338c3>] acpi_processor_idle+0x0/0x235
[<c02338ce>] acpi_processor_idle+0xb/0x235
[<c02338c3>] acpi_processor_idle+0x0/0x235
[<c02338c3>] acpi_processor_idle+0x0/0x235
[<c02338c3>] acpi_processor_idle+0x0/0x235
[<c0101115>] cpu_idle+0x75/0x110
[<c04f5988>] start_kernel+0x158/0x180
[<c04f5390>] unknown_bootoption+0x0/0x1e0
...in logs.
Pavel
--
People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
next reply other threads:[~2005-01-09 21:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-09 21:10 Pavel Machek [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-01-10 1:24 [ACPI] ACPI using smp_processor_id in preemptible code Li, Shaohua
2005-01-10 9:55 ` Pavel Machek
[not found] ` <20050110095508.GJ1353-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
2005-01-11 1:04 ` Li Shaohua
[not found] ` <1105405464.18834.4.camel-U5EdaLXB8smDugQYiPIPGdh3ngVCH38I@public.gmane.org>
2005-01-11 2:09 ` Dmitry Torokhov
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=20050109211042.GA1196@elf.ucw.cz \
--to=pavel-+zi9xunit7i@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.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