Re: NMI watchdog

From: Michal Hocko
Date: Mon Mar 30 2015 - 13:09:25 EST


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] <NMI> [<ffffffff81554a5e>] ? 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@xxxxxxxxxxxxxxx
> 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
--
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/