Hi Tony,

On Thu, 2012-02-09 at 10:36 -0800, Tony Lindgren wrote: 
> * Mark Brown <broonie@opensource.wolfsonmicro.com> [120209 05:06]:
> > On Thu, Feb 09, 2012 at 09:25:36AM +0200, Jarkko Nikula wrote:
> > > On 02/09/2012 02:47 AM, Greg KH wrote:
> > > > Show me an OMAP user that actually runs a mainline kernel :)
> > 
> > > I guess pretty much all these days? Most error reports what I recall
> > > seeing during past 2-3 years are from mainline kernel and not that much
> > > from linux-omap or some board support package kernel.
> > 
> > Most of the other guys are going in via the TI support channels rather
> > than asking on the public lists I expect (and remember that even if
> > people are basing their code on mainline the chances are they've still
> > got a bunch of out of tree changes on top for their own boards if
> > they're not directly using one of the reference boards).
> 
> Please everybody using omaps with mainline give a test for the
> merge of the various fixes planned. I've done a branch with
> v3.3-rc3 + Russell's fixes + Paul's serial port fixes + fixes
> that I've queued up.
> 
> This fixes the various build and boot issues with custom .configs
> that don't select CONFIG_MACH_OMAP_GENERIC. It should fix slow serial
> console issues. And it fixes booting with DT to minimal enviroment.
> 
> If you still see problems with compiling, booting, or slow serial
> port, please post the issues to linux-omap and LAKML lists
> immediately.
> 
> The testing branch is available at:
> 
> git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap testing-omap-fixes

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): [<c0042314>] copy_process+0x3ec/0x105c                                    
[  336.209625] softirqs last  enabled at (0): [<c0042314>] copy_process+0x3ec/0x105c                                    
[  336.217498] softirqs last disabled at (0): [<  (null)>]   (null)                                                     
[  336.217498] [<c001e1e4>] (unwind_backtrace+0x0/0x148) from [<c0502c24>] (dump_stack+0x20/0x24)                       
[  336.232879] [<c0502c24>] (dump_stack+0x20/0x24) from [<c0077998>] (__might_sleep+0x130/0x134)                        
[  336.232879] [<c0077998>] (__might_sleep+0x130/0x134) from [<c0018998>] (do_signal+0x54/0x600)                        
[  336.250793] [<c0018998>] (do_signal+0x54/0x600) from [<c0018fa4>] (do_notify_resume+0x60/0x6c)                       
[  336.250793] [<c0018fa4>] (do_notify_resume+0x60/0x6c) from [<c00154e4>] (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).

-- 
Cheers,
Luca.