From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754140Ab3GJJzJ (ORCPT ); Wed, 10 Jul 2013 05:55:09 -0400 Received: from merlin.infradead.org ([205.233.59.134]:44698 "EHLO merlin.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753390Ab3GJJzF (ORCPT ); Wed, 10 Jul 2013 05:55:05 -0400 Date: Wed, 10 Jul 2013 11:54:59 +0200 From: Peter Zijlstra To: Sasha Levin Cc: Tejun Heo , tglx@linutronix.de, LKML , trinity@vger.kernel.org Subject: Re: timer: lockup in run_timer_softirq() Message-ID: <20130710095459.GE17211@twins.programming.kicks-ass.net> References: <51DC902F.3070403@oracle.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <51DC902F.3070403@oracle.com> User-Agent: Mutt/1.5.21 (2012-12-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Jul 09, 2013 at 06:35:27PM -0400, Sasha Levin wrote: > While going through the NMI dump, I noticed that it's very incomplete, and full of: > > [ 2536.500130] INFO: NMI handler (arch_trigger_all_cpu_backtrace_handler) > took too long to run: 697182.008 msecs Now I would actually expect arch_trigger_all_cpu_backtrace_handler() to issue this warning, that said, ~700 seconds is a bit long, I'm fairly sure it didn't actually take that long, you'd have noticed your vm being 'away' for 10+ minutes I'd think, no? There's something entirely fishy with that stuff, let me to stare at it.