From: Michal Hocko <mhocko@suse.cz>
To: Justin Keller <justincompsci@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: NMI watchdog
Date: Mon, 30 Mar 2015 19:09:15 +0200 [thread overview]
Message-ID: <20150330170914.GA17373@dhcp22.suse.cz> (raw)
In-Reply-To: <CALah4NdzDRo8evi1qh537jWrt5U0BdABqR-q7qzy7y5-byUhLg@mail.gmail.com>
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@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
next prev parent reply other threads:[~2015-03-30 17:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-30 12:14 Justin Keller
2015-03-30 17:09 ` Michal Hocko [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-10-12 9:18 John Sigler
2007-10-12 10:00 ` Björn Steinbrink
2007-10-12 10:58 ` John Sigler
2007-10-12 10:26 ` Steven Rostedt
2007-10-12 13:26 ` John Sigler
2007-10-12 16:12 ` Steven Rostedt
2007-10-17 12:20 ` John Sigler
2007-10-12 14:48 ` Arjan van de Ven
2007-10-15 16:05 ` John Sigler
2003-11-14 10:12 NMI Watchdog Maciej Zenczykowski
2003-11-14 10:29 ` Mikael Pettersson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150330170914.GA17373@dhcp22.suse.cz \
--to=mhocko@suse.cz \
--cc=justincompsci@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome