Re: frequent lockups in 3.18rc4

[Dave Jones]

On Wed, Dec 03, 2014 at 02:59:58PM -0500, Chris Mason wrote:
 
 
 > > [  503.692038] Switched to clocksource hpet
 > > [  524.420897] NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! 
 > > [trinity-c178:20182]
 > 
 > Neat.  We often see switching to hpet on boxes as they are diving into 
 > softlockup pain, but it's not usually before the softlockups.
 > 
 > Are you configured for CONFIG_NOHZ_FULL?
 

No. I have recollections that I did run with that early on in this, but
I think someone asked me to try without that a few weeks back, and it's
been off since. (made no difference)

 > I'd love to blame the only commit to kernel/smp.c between 3.16 and 3.17
 > 
 > commit 478850160636c4f0b2558451df0e42f8c5a10939
 > Author: Frederic Weisbecker <fweisbec@xxxxxxxxx>
 > Date:   Thu May 8 01:37:48 2014 +0200
 > 
 >     irq_work: Implement remote queueing
 > 
 > You've also mentioned a few times where messages stopped hitting the 
 > console?
 >
 > commit 5874af2003b1aaaa053128d655710140e3187226
 > Author: Jan Kara <jack@xxxxxxx>
 > Date:   Wed Aug 6 16:09:10 2014 -0700
 > 
 >     printk: enable interrupts before calling 
 > console_trylock_for_printk()

Hmm..

	Dave
--
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/