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 08:19:12 -0800 Message-ID: <20150102161911.GA3298@atomide.com> References: <54A58E23.5080103@gmx.net> <20150101182053.GG582@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-02-ewr.mailhop.org ([204.13.248.72]:51991 "EHLO mho-02-ewr.mailhop.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752160AbbABQWr (ORCPT ); Fri, 2 Jan 2015 11:22:47 -0500 Content-Disposition: inline In-Reply-To: <20150101182053.GG582@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 * Aaro Koskinen [150101 10:23]: > Hi, >=20 > On Thu, Jan 01, 2015 at 07:12:51PM +0100, Peter K=C3=BCmmel 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? >=20 > > [ 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() >=20 > 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? 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