From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kevin Hilman Subject: Re: OMAP34xx Date: Wed, 15 Feb 2012 16:13:02 -0800 Message-ID: <4F3C4A0E.1000707@deeprootsystems.com> References: <20120208231551.GA9009@kroah.com> <20120209004731.GA11343@kroah.com> <4F3374F0.3080002@bitmer.com> <20120209133739.GB2590@sirena.org.uk> <20120209183624.GJ1426@atomide.com> <1329343056.5686.6.camel@cumari> <87ehtvlkjf.fsf@ti.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from mail-pz0-f46.google.com ([209.85.210.46]:33363 "EHLO mail-pz0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752186Ab2BPANF (ORCPT ); Wed, 15 Feb 2012 19:13:05 -0500 Received: by daed14 with SMTP id d14so1392682dae.19 for ; Wed, 15 Feb 2012 16:13:04 -0800 (PST) In-Reply-To: <87ehtvlkjf.fsf@ti.com> Sender: linux-omap-owner@vger.kernel.org List-Id: linux-omap@vger.kernel.org To: Kevin Hilman Cc: Luciano Coelho , Tony Lindgren , Mark Brown , Jarkko Nikula , Greg KH , Paul Walmsley , Grazvydas Ignotas , Russell King - ARM Linux , linux-omap@vger.kernel.org, Arnd Bergmann , Olof Johansson On 02/15/2012 03:54 PM, Kevin Hilman wrote: > Luciano Coelho writes: > > [...] > >> I just tried this on my Panda and I keep getting this kind of BUGs. It >> spams my console so much that is pretty much unusable: >> >> [ 336.172302] BUG: sleeping function called from invalid context at include/linux/freezer.h:46 >> [ 336.181213] in_atomic(): 0, irqs_disabled(): 128, pid: 1618, name: ntpd >> [ 336.181213] INFO: lockdep is turned off. >> [ 336.181213] irq event stamp: 0 >> [ 336.181213] hardirqs last enabled at (0): [< (null)>] (null) >> [ 336.201660] hardirqs last disabled at (0): [] copy_process+0x3ec/0x105c >> [ 336.209625] softirqs last enabled at (0): [] copy_process+0x3ec/0x105c >> [ 336.217498] softirqs last disabled at (0): [< (null)>] (null) >> [ 336.217498] [] (unwind_backtrace+0x0/0x148) from [] (dump_stack+0x20/0x24) >> [ 336.232879] [] (dump_stack+0x20/0x24) from [] (__might_sleep+0x130/0x134) >> [ 336.232879] [] (__might_sleep+0x130/0x134) from [] (do_signal+0x54/0x600) >> [ 336.250793] [] (do_signal+0x54/0x600) from [] (do_notify_resume+0x60/0x6c) >> [ 336.250793] [] (do_notify_resume+0x60/0x6c) from [] (work_pending+0x24/0x28) >> >> I have also seen this in 3.3-rc3 (both on Panda (OMAP4460) and on Blaze >> (OMAP4430) boards) and I was hoping your tree would have the fix for it, >> but it doesn't. :( The device boots and seems to work otherwise, but >> this is annoying and looks shaky. >> >> I saw something related to this in another thread from a few months ago, >> and one patch proposal by Russell, but I didn't find any conclusion or >> any related patch queued up for upstream. >> >> Is there any solution for this? I use a tuned .config (attached) and not >> the one generated by omap2plus_defconfig (which I didn't try as >> vanilla). > > I see the same thing with your ~/.config, but I don't think this is OMAP > specific. I suspect this will happen on any ARM platform that has > CONFIG_DEBUG_ATOMIC_SLEEP=y. > > It appears to be a problem with the recently added audit support for > ARM, since reverting the commit below makes this BUG go away. False alarm. reverting the audit commit didn't make the problem go away. It was gone only because I also disabled CONFIG_DEBUG_ATOMIC_SLEEP. :/ To debug this further, you might bisect it back to v3.2 because the problem isn't there in v3.2 Kevin