From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: New l3-noc error with CPUFREQ_DT built-in with v4.0-rc1
Date: Mon, 23 Feb 2015 15:59:47 -0800 [thread overview]
Message-ID: <20150223235947.GC25954@atomide.com> (raw)
Hi Nishanth,
Olof told me about a new L3 error happening on omap5-uevm with
v4.0-rc1:
WARNING: CPU: 0 PID: 0 at drivers/bus/omap_l3_noc.c:147 l3_interrupt_handler+0x214/0x340()
4000000.ocp:L3 Custom Error: MASTER MPU TARGET L4PER2 (Idle): Data Access in Supervisor mode during Functional access
...
I tried bisecting this with no luck, but narrowed it down to
having CONFIG_CPUFREQ_DT=y causing it, while =m wont' trigger
it. This got changed by commit 40d1746d2eee ("ARM:
omap2plus_defconfig: use CONFIG_CPUFREQ_DT").
Any ideas?
Regards,
Tony
next reply other threads:[~2015-02-23 23:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-23 23:59 Tony Lindgren [this message]
2015-02-24 1:59 ` New l3-noc error with CPUFREQ_DT built-in with v4.0-rc1 Tony Lindgren
2015-02-24 2:24 ` Felipe Balbi
2015-02-24 2:35 ` Tony Lindgren
2015-02-24 3:01 ` Tony Lindgren
2015-02-24 3:15 ` Felipe Balbi
2015-02-24 3:21 ` Tony Lindgren
2015-02-24 3:24 ` Tony Lindgren
2015-02-24 14:46 ` Felipe Balbi
2015-02-24 3:12 ` Felipe Balbi
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=20150223235947.GC25954@atomide.com \
--to=tony@atomide.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).