From: Luis Henriques <henrix@sapo.pt>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org
Subject: [BUG] using smp_processor_id() in preemptible
Date: Sat, 15 Nov 2008 23:30:51 +0000 [thread overview]
Message-ID: <20081115233050.GA13439@hades> (raw)
Hi Ingo,
while running latencytop, got the following:
...
[ 775.663239] BUG: using smp_processor_id() in preemptible [00000000] code: latencytop/6585
[ 775.663303] caller is native_sched_clock+0x3a/0x80
[ 775.663314] Pid: 6585, comm: latencytop Tainted: G W 2.6.28-rc4-00355-g9c7c354 #1
[ 775.663322] Call Trace:
[ 775.663343] [<ffffffff803a94e4>] debug_smp_processor_id+0xe4/0xf0
[ 775.663356] [<ffffffff80213f7a>] native_sched_clock+0x3a/0x80
[ 775.663368] [<ffffffff80213e19>] sched_clock+0x9/0x10
[ 775.663381] [<ffffffff8024550d>] proc_sched_show_task+0x8bd/0x10e0
[ 775.663395] [<ffffffff8034466e>] sched_show+0x3e/0x80
[ 775.663408] [<ffffffff8031039b>] seq_read+0xdb/0x350
[ 775.663421] [<ffffffff80368776>] ? security_file_permission+0x16/0x20
[ 775.663435] [<ffffffff802f4198>] vfs_read+0xc8/0x170
[ 775.663447] [<ffffffff802f4335>] sys_read+0x55/0x90
[ 775.663460] [<ffffffff8020c67a>] system_call_fastpath+0x16/0x1b
...
I am running 2.6.28-rc4-00355-g9c7c354 and, after taking a look at the code, it
looks like the problem is in commit 7cbaef9c83e58bbd4bdd534b09052b6c5ec457d5,
where native_sched_clock is modified to use __cycles_2_ns instead of
cycles_2_ns.
--
Luis Henriques
next reply other threads:[~2008-11-15 23:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-15 23:30 Luis Henriques [this message]
2008-11-16 7:10 ` [BUG] using smp_processor_id() in preemptible Ingo Molnar
2008-11-18 11:05 ` Michal Hocko
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=20081115233050.GA13439@hades \
--to=henrix@sapo.pt \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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.