From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753395AbbC3RJW (ORCPT ); Mon, 30 Mar 2015 13:09:22 -0400 Received: from mail-wg0-f50.google.com ([74.125.82.50]:35824 "EHLO mail-wg0-f50.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753201AbbC3RJS (ORCPT ); Mon, 30 Mar 2015 13:09:18 -0400 Date: Mon, 30 Mar 2015 19:09:15 +0200 From: Michal Hocko To: Justin Keller Cc: linux-kernel@vger.kernel.org Subject: Re: NMI watchdog Message-ID: <20150330170914.GA17373@dhcp22.suse.cz> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon 30-03-15 08:14:45, Justin Keller wrote: > Hello, > Although not running a vanilla kernel on this machine, I have reported > the issue to the distribution's bug tracking system. It has been > almost a week with no response, so I am sending this email. > > Multiple times, when I return to my computer from being away for a > little while, I noticed: > Message from syslogd@redacted at Mar 23 XX:XX:XX ... > kernel:[1059322.470817] NMI watchdog: BUG: soft lockup - CPU#1 stuck > for 22s! [kswapd0:31] traces dumped as a part of the watchdog output is the most interesting information. And the kernel version is very important as well. > Dmesg | grep NMI produced: > [1151200.727734] sending NMI to all CPUs: > [1151200.727812] NMI backtrace for cpu 0 > [1151200.764129] INFO: NMI handler > (arch_trigger_all_cpu_backtrace_handler) took too long to run: 36.262 > msecs > [1151200.764198] NMI backtrace for cpu 1 > [1151216.700893] sending NMI to all CPUs: > [1151216.700984] NMI backtrace for cpu 1 > [1151216.706524] NMI backtrace for cpu 0 > [1723994.455161] [] ? dump_stack+0x41/0x51 > > I didn't have time to grep for kswapd or to investigate further. Long > story short, the machine was shutdown shortly afterwords. > > Justin > > PS this was also sent to linux-watchdog. I forgot to turn of HTML, so > I had to re-send it here > -- > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ -- Michal Hocko SUSE Labs