From: Tim Blechmann <tim@klingt.org>
To: linux-rt-users@vger.kernel.org
Subject: BUG: using smp_processor_id() in preemptible
Date: Mon, 8 Dec 2008 12:13:31 +0000 (UTC) [thread overview]
Message-ID: <ghj31b$bmr$1@ger.gmane.org> (raw)
hi all,
using the 2.6.26.6-rt11 patchset on a 2.6.26.8 kernel, i get the
following stack traces:
[ 4262.931832] BUG: using smp_processor_id() in preemptible [00000000] code: bash/361
[ 4262.931846] caller is mem_cgroup_charge_statistics+0x6d/0xa0
[ 4262.931852] Pid: 361, comm: bash Not tainted 2.6.26.8-rt11 #3
[ 4262.931855]
[ 4262.931856] Call Trace:
[ 4262.931886] [<ffffffff80396e8c>] debug_smp_processor_id+0xcc/0xd0
[ 4262.931895] [<ffffffff802daead>] mem_cgroup_charge_statistics+0x6d/0xa0
[ 4262.931905] [<ffffffff802daf19>] __mem_cgroup_add_list+0x39/0x60
[ 4262.931911] [<ffffffff802db744>] mem_cgroup_charge_common+0x314/0x330
[ 4262.931925] [<ffffffff802db78e>] mem_cgroup_charge+0xe/0x10
[ 4262.931933] [<ffffffff802b8773>] do_wp_page+0x133/0x5a0
[ 4262.931944] [<ffffffff804d7461>] ? __rt_spin_lock+0x81/0x90
[ 4262.931956] [<ffffffff802ba805>] handle_mm_fault+0x605/0x900
[ 4262.931975] [<ffffffff804dacfc>] do_page_fault+0x45c/0xd50
[ 4262.931998] [<ffffffff8021d6ee>] ? native_smp_send_reschedule+0x2e/0x50
[ 4262.932006] [<ffffffff8023a041>] ? __resched_task+0x91/0x120
[ 4262.932015] [<ffffffff8023b5f4>] ? task_new_fair+0xb4/0x100
[ 4262.932027] [<ffffffff8023e09b>] ? wake_up_new_task+0xdb/0x190
[ 4262.932038] [<ffffffff80241190>] ? do_fork+0xf0/0x330
[ 4262.932048] [<ffffffff804d748e>] ? rt_spin_lock+0x1e/0x50
[ 4262.932056] [<ffffffff802dbad2>] ? fd_install+0x52/0x60
[ 4262.932072] [<ffffffff804d81c9>] error_exit+0x0/0x60
hth, tim
--
tim@klingt.org
http://tim.klingt.org
There's no such entity as "most people". These are generalities. All
generalities are meaningless. You've got to pin it down to a specific
person doing a specific thing at a specific time and space.
William S. Burroughs
next reply other threads:[~2008-12-08 12:13 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-08 12:13 Tim Blechmann [this message]
2009-01-13 9:44 ` BUG: using smp_processor_id() in preemptible Tim Blechmann
2009-02-20 20:42 ` Paul Gortmaker
-- strict thread matches above, loose matches on Subject: below --
2018-01-11 12:31 Ricardo Nabinger Sanchez
2018-01-11 17:14 ` Eric Dumazet
2012-10-24 8:24 Paul Thompson
2012-10-24 22:39 ` Borislav Petkov
2010-05-25 5:57 Artem Bityutskiy
2010-05-25 5:57 ` Artem Bityutskiy
2009-06-24 14:15 Johannes Berg
2009-06-28 14:11 ` Avi Kivity
2009-06-29 8:32 ` Johannes Berg
2009-06-29 9:08 ` Avi Kivity
2009-06-29 9:54 ` Johannes Berg
2009-06-29 9:57 ` Johannes Berg
2009-06-29 10:00 ` Avi Kivity
2009-06-29 10:06 ` Johannes Berg
2009-06-29 10:16 ` Avi Kivity
2009-06-29 10:18 ` Johannes Berg
2009-06-29 10:25 ` Avi Kivity
2009-06-29 10:32 ` Johannes Berg
2009-06-29 10:39 ` Avi Kivity
2009-06-29 10:55 ` Johannes Berg
2009-06-29 11:38 ` Avi Kivity
2009-06-29 12:03 ` Johannes Berg
2009-06-29 9:59 ` Avi Kivity
2009-06-29 10:00 ` Johannes Berg
2009-06-29 10:04 ` Avi Kivity
2009-06-29 10:04 ` Johannes Berg
2008-08-20 5:34 Aneesh Kumar K.V
2008-08-21 4:17 ` Eric Sandeen
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='ghj31b$bmr$1@ger.gmane.org' \
--to=tim@klingt.org \
--cc=linux-rt-users@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.