From: Paul Thompson <set.mailinglist@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: BUG: using smp_processor_id() in preemptible
Date: Wed, 24 Oct 2012 04:24:23 -0400 [thread overview]
Message-ID: <20121024082423.GB2604@squish.home.loc> (raw)
Hi;
Just saw this after invoking cpufreq-set -g performance in
an attempt to enhance a stuttering mpeg transcode for ps3mediaserver.
This repeats in the logs about 10 times. If anyone cares, I
will be responsive.
Paul
2012 Oct 24 01:39:14: BUG: using smp_processor_id() in preemptible [00000000] code: cpufreq-set/22941
2012 Oct 24 01:39:14: caller is powernowk8_target+0x19/0x50
2012 Oct 24 01:39:14: Pid: 22941, comm: cpufreq-set Not tainted 3.6.2-low-lat #13
2012 Oct 24 01:39:14: Call Trace:
2012 Oct 24 01:39:14: [<ffffffff811b0476>] ? debug_smp_processor_id+0xd6/0xf0
2012 Oct 24 01:39:14: [<ffffffff812eb6e9>] ? powernowk8_target+0x19/0x50
2012 Oct 24 01:39:14: [<ffffffff812e9a95>] ? cpufreq_governor_performance+0x25/0x30
2012 Oct 24 01:39:14: [<ffffffff812e7f87>] ? __cpufreq_governor+0x47/0xc0
2012 Oct 24 01:39:14: [<ffffffff812e8164>] ? __cpufreq_set_policy+0x164/0x1a0
2012 Oct 24 01:39:14: [<ffffffff812e8849>] ? store_scaling_governor+0xc9/0x1b0
2012 Oct 24 01:39:15: [<ffffffff812e8c40>] ? cpufreq_update_policy+0xf0/0xf0
2012 Oct 24 01:39:15: [<ffffffff812e9005>] ? store+0x65/0xb0
2012 Oct 24 01:39:15: [<ffffffff8112574d>] ? sysfs_write_file+0xcd/0x150
2012 Oct 24 01:39:15: [<ffffffff810ca9a7>] ? vfs_write+0xa7/0x180
2012 Oct 24 01:39:15: [<ffffffff810cacd7>] ? sys_write+0x47/0x90
2012 Oct 24 01:39:15: [<ffffffff813d8526>] ? system_call_fastpath+0x1a/0x1f
next reply other threads:[~2012-10-24 8:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-24 8:24 Paul Thompson [this message]
2012-10-24 22:39 ` Borislav Petkov
-- strict thread matches above, loose matches on Subject: below --
2010-05-25 5:57 Artem Bityutskiy
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=20121024082423.GB2604@squish.home.loc \
--to=set.mailinglist@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®