Re: Linux 2.6.24-rc7

[Michael Buesch]

On Monday 07 January 2008 17:14:15 Alejandro Riveira FernÃndez wrote:
> El Sun, 6 Jan 2008 14:19:16 -0800 (PST)
> Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx> escribiÃ:
> 
> > 
> > It's been two weeks since rc6, but let's face it, with xmas and new years 
> > (and birthdays) in between, there hasn't actually been a lot of working 
> > days, and the incremental patch from -rc6 is about half the size of the 
> > one from rc5->rc6.
> > 
> > And I'll be charitable and claim it's because it's all stabilizing, and 
> > not because we've all been in a drunken stupor over the holidays.
> > 
> > The shortlog (appended below) is short and fairly informative. It's all 
> > really just a lot of rather small changes. The diffstat shows a lot of 
> > one- and two-liners, with just a few drivers (and the Cell platform) 
> > getting a bit more attention, and the SLUB support of /proc/slabinfo 
> > showing up as a blip.
> > 
> > Both git trees and tar-balls/patches pushed out, should be mirroring out 
> > within minutes. So there are no excuses to not try it out, and see if your 
> > favorite regression has been fixed.
> > 
> > 		Linus
> > 
>   Booted with it and I see 
> 
>  [   37.043998]                                                                                                               
> [   37.043999] Call Trace:                                                                                                   
> [   37.044001]  <IRQ>  [<ffffffff80227fe3>] enqueue_task+0x13/0x30                                                           
> [   37.044040]  [<ffffffff88178cbe>] :mac80211:__ieee80211_rx+0xc7e/0xd30                                                    
> [   37.044044]  [<ffffffff80228062>] activate_task+0x32/0x50                                                                 
> [   37.044073]  [<ffffffff8816a28b>] :mac80211:ieee80211_tasklet_handler+0xbb/0x120                                          
> [   37.044086]  [<ffffffff80238d08>] tasklet_action+0x48/0xb0                                                                
> [   37.044091]  [<ffffffff80238c09>] __do_softirq+0x69/0xe0                                                                  
> [   37.044097]  [<ffffffff8020ce2c>] call_softirq+0x1c/0x30                                                                  
> [   37.044101]  [<ffffffff8020efe5>] do_softirq+0x35/0x90                                                                    
> [   37.044105]  [<ffffffff80238aa5>] irq_exit+0x95/0xa0                                                                      
> [   37.044108]  [<ffffffff8020f0c0>] do_IRQ+0x80/0x100                                                                       
> [   37.044111]  [<ffffffff8020a840>] default_idle+0x0/0x40                                                                   
> [   37.044115]  [<ffffffff8020c181>] ret_from_intr+0x0/0xa                                                                   
> [   37.044117]  <EOI>  [<ffffffff8020a869>] default_idle+0x29/0x40                                                           
> [   37.044130]  [<ffffffff8020a8f5>] cpu_idle+0x75/0xc0                                                                      
> [   37.044146]                                                                                                               

Can you post the lines above this?
This might be a WARN_ON_ONCE() triggering, for which fixes are on their way into
the wireless-2.6 tree.

-- 
Greetings Michael.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/