From mboxrd@z Thu Jan 1 00:00:00 1970 From: pavel@ucw.cz (Pavel Machek) Date: Tue, 24 Jan 2017 00:22:49 +0100 Subject: 4.10-rc1 on Nokia N900: regression, WARN_ON() omap_l3_smx.c In-Reply-To: <20170102181058.GF9325@atomide.com> References: <20161229231411.GA6865@amd> <20170102181058.GF9325@atomide.com> Message-ID: <20170123232249.GA11641@amd> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org Hi! > * Pavel Machek [161229 15:14]: > > Hi! > > > > I forgot I had v4.10-rc1 running, and now I got warning on all the > > consoles (hand-copied). > > > > > > Unhandled fault: external abort on non-linefetch (0x1028) at > > 0xfa0ab060 > > ... > > Comm: kworker/0:0 Not tainted. > > Workqueue: events musb_irq_work > > ... > > PC is at musb_default_readb(). > > ... > > This means the clocks are not enabled at that point. > > > WARNING: CPU: 0 ... at drivers/bus/omap_l3_smx.c:166 > > omap3_l3_app_irq+0xcc/... > > Tainted: GDW. > > If you comment out postcore_initcall_sync(omap3_l3_init); > in drivers/bus/omap_l3_smx.c you'll see the proper stack > trace instead of the l3 interrupt trace. The system will > hang at that point most likely. > > > I do have patches to allow nfsroot over usb. But they worked ok in > > v4.9... Does anyone see it, too? > > Hmm not much has changed since v4.9. Are you sure you > had v4.9 or some earlier v4.9-rc version? It happened again in -rc5. I have full dmesg this time. I started new thread with " Subject: v4.9 to v4.10 regression: oops when USB cable is plugged in. ". It does no longer look completely scary. Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: Digital signature URL: