From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tony Lindgren Subject: Re: 3.18.1->3.19-rc2: In-band Error seen by MPU Date: Fri, 2 Jan 2015 16:02:21 -0800 Message-ID: <20150103000220.GE3279@atomide.com> References: <54A58E23.5080103@gmx.net> <20150101182053.GG582@fuloong-minipc.musicnaut.iki.fi> <20150102161911.GA3298@atomide.com> <54A6E408.1090908@gmx.net> <20150102201908.GK582@fuloong-minipc.musicnaut.iki.fi> <20150102204018.GF3298@atomide.com> <20150102223451.GL582@fuloong-minipc.musicnaut.iki.fi> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: Received: from mho-03-ewr.mailhop.org ([204.13.248.66]:31306 "EHLO mho-01-ewr.mailhop.org" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1752207AbbACAF5 (ORCPT ); Fri, 2 Jan 2015 19:05:57 -0500 Content-Disposition: inline In-Reply-To: <20150102223451.GL582@fuloong-minipc.musicnaut.iki.fi> Sender: linux-omap-owner@vger.kernel.org List-Id: linux-omap@vger.kernel.org To: Aaro Koskinen Cc: Peter =?utf-8?Q?K=C3=BCmmel?= , linux-omap@vger.kernel.org, Pavel Machek , Russell King , Santosh Shilimkar * Aaro Koskinen [150102 14:37]: > Hi, >=20 > On Fri, Jan 02, 2015 at 12:40:19PM -0800, Tony Lindgren wrote: > > * Aaro Koskinen [150102 12:21]: > > > On Fri, Jan 02, 2015 at 07:31:36PM +0100, Peter K=C3=BCmmel wrote= : > > > > Am 02.01.2015 um 17:19 schrieb Tony Lindgren: > > > > >* Aaro Koskinen [150101 10:23]: > > > > >>On Thu, Jan 01, 2015 at 07:12:51PM +0100, Peter K=C3=BCmmel w= rote: > > > > >>>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= =2E1. > > > > >>>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? > > > >=20 > > > > Indeed, when I disable CONFIG_PREEMPT the warning is gone. > > >=20 > > > Yeah, disabling CONFIG_PREEMPT helps here too. Is there some e-ma= il > > > thread / patch set for this already; or should we try to bisect t= his? > >=20 > > 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. > >=20 > > 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. >=20 > I tried to bisect this on N950, and it resulted in: >=20 > aa25729cfd9709156661bea0f9293deb7729f57a is the first bad commit > commit aa25729cfd9709156661bea0f9293deb7729f57a > Author: Tony Lindgren > Date: Wed Nov 5 09:21:23 2014 -0800 >=20 > ARM: OMAP3: Fix errors for omap_l3_smx when booted with device tr= ee >=20 > 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? Regards, Tony -- To unsubscribe from this list: send the line "unsubscribe linux-omap" i= n the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html