From: jolsa@redhat.com (Jiri Olsa)
To: linux-arm-kernel@lists.infradead.org
Subject: [BUG] sleeping function called from invalid context in perf_pmu_register()
Date: Wed, 10 Jan 2018 11:52:47 +0100 [thread overview]
Message-ID: <20180110105247.GA25103@krava> (raw)
In-Reply-To: <20171229085904.GC18393@Red>
On Fri, Dec 29, 2017 at 09:59:04AM +0100, Corentin Labbe wrote:
SNIP
> [ 1.494884] Exception stack(0xee845fb0 to 0xee845ff8)
> [ 1.499933] 5fa0: 00000000 00000000 00000000 00000000
> [ 1.508100] 5fc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
> [ 1.516267] 5fe0: 00000000 00000000 00000000 00000000 00000013 00000000
> [ 1.522871] r5:c06c2528 r4:00000000
>
> This is due to get_cpu() in cci_pmu_probe() in drivers/bus/arm-cci.c which disable preemption.
> But now I do not know how to fix it.
> My .config is below.
yep, looks like cci_pmu_probe needs to be fixed.. can't
call perf_pmu_register with preemption disabled
jirka
parent reply other threads:[~2018-01-10 10:52 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20171229085904.GC18393@Red>]
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=20180110105247.GA25103@krava \
--to=jolsa@redhat.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).