From: Borislav Petkov <bp@alien8.de>
To: Paul Thompson <set.mailinglist@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: BUG: using smp_processor_id() in preemptible
Date: Thu, 25 Oct 2012 00:39:04 +0200 [thread overview]
Message-ID: <20121024223904.GA9129@liondog.tnic> (raw)
In-Reply-To: <20121024082423.GB2604@squish.home.loc>
On Wed, Oct 24, 2012 at 04:24:23AM -0400, Paul Thompson wrote:
> 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
...
http://marc.info/?l=linux-kernel&m=135111561229153
HTH.
--
Regards/Gruss,
Boris.
next prev parent reply other threads:[~2012-10-24 22:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-24 8:24 BUG: using smp_processor_id() in preemptible Paul Thompson
2012-10-24 22:39 ` Borislav Petkov [this message]
-- 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=20121024223904.GA9129@liondog.tnic \
--to=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=set.mailinglist@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).