Am 03.01.2015 um 01:02 schrieb Tony Lindgren:
* Aaro Koskinen <aaro.koskinen@xxxxxx> [150102 14:37]:
Hi,
On Fri, Jan 02, 2015 at 12:40:19PM -0800, Tony Lindgren wrote:
* Aaro Koskinen <aaro.koskinen@xxxxxx> [150102 12:21]:
On Fri, Jan 02, 2015 at 07:31:36PM +0100, Peter Kümmel wrote:
Am 02.01.2015 um 17:19 schrieb Tony Lindgren:
* Aaro Koskinen <aaro.koskinen@xxxxxx> [150101 10:23]:
On Thu, Jan 01, 2015 at 07:12:51PM +0100, Peter Kümmel wrote:
When updating (custom DM3730 board) from 3.18.1 ro 3.19-rc2
I see a "In-band ERROR" warning which wasn't present in 3.18.1.
Could it be that I missed some DT updates?
[ 0.366882] In-band Error seen by MPU at address 0
[ 0.366912] ------------[ cut here ]------------
[ 0.366943] WARNING: CPU: 0 PID: 1 at drivers/bus/omap_l3_smx.c:166 omap3_l3_app_irq+0x100/0x134()
This appears also on N900/N950/N9...
Do you have CONFIG_PREEMPT enabled? It seems there's some
regression related to CONFIG_PREEMPT that started happening
with the merge window?
Indeed, when I disable CONFIG_PREEMPT the warning is gone.
Yeah, disabling CONFIG_PREEMPT helps here too. Is there some e-mail
thread / patch set for this already; or should we try to bisect this?
AFAIK I'm not aware of other threads, I noticied it with the
"OMAP 4430 SDP: rather sick with recent kernels" thread, but
never got anywhere with it.
Yeah it seems it's somewhere between v3.18 and v3.19-rc1, but
that too should be verified. Sounds like running git bisect on
this one is needed.
I tried to bisect this on N950, and it resulted in:
aa25729cfd9709156661bea0f9293deb7729f57a is the first bad commit
commit aa25729cfd9709156661bea0f9293deb7729f57a
Author: Tony Lindgren <tony@xxxxxxxxxxx>
Date: Wed Nov 5 09:21:23 2014 -0800
ARM: OMAP3: Fix errors for omap_l3_smx when booted with device tree
But when I tried to revert this from 3.19-rc2, my board won't boot at
all...
Hmm OK that commit just fixed the omap_l3_smx so we now see
warnings about the unclocked register access.
It seems that probably the CONFIG_PREEMPT issue has been lurking
around for longer but we have not seen any errors because
omap_l3_smx just recently started exposing them.
Does v3.18 + commit aa25729cfd9 manually applied also produce
the CONFIG_PREEMPT errors?
Yes, same error. I applied it on top of v3.18.1.
Peter
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
