From: Andi Kleen <ak@suse.de>
To: Patrick McHardy <kaber@trash.net>
Cc: Andi Kleen <ak@suse.de>, Ed Tomlinson <tomlins@cam.org>,
Alexander Nyberg <alexn@dsv.su.se>,
Parag Warudkar <kernel-stuff@comcast.net>,
linux-kernel@vger.kernel.org
Subject: Re: X86_64: 2.6.12-rc3 spontaneous reboot
Date: Tue, 26 Apr 2005 16:22:52 +0200 [thread overview]
Message-ID: <20050426142252.GJ5098@wotan.suse.de> (raw)
In-Reply-To: <426E4DD2.8060808@trash.net>
On Tue, Apr 26, 2005 at 04:18:58PM +0200, Patrick McHardy wrote:
> Patrick McHardy wrote:
> >Andi Kleen wrote:
> >
> >>Hmm, thats hard to believe. And are you sure the NMI watchdog
> >>did not trigger? (e.g. did you run it with serial or netconsole)?
> >
> >I ran it with netconsole, but nothing was received. I'm going to retry
> >with and without the patch once more to make sure.
>
> I tried starting uml with and without the patch, five times each.
> Without the patch it worked fine every time, with the patch it
> instantly rebooted every time. Nothing was logged on netconsole.
> Perhaps also interesting is that if I revert all patches after
> this change up to HEAD, it doesn't always instantly reboot, but
> sometimes just hangs. When using HEAD, it rebooted each time so far.
Ok thanks for the information. I will stare a bit at the patch.
It is very mysterious though. Even if the patch was somehow wrong
the worst thing that could happen is that you end up with interrupts
off when you shouldnt, and the NMI watchdog is very good
at catching that.
Hmm actually - on some systems I broke the NMI watchdog. Can you
check your dmesg to see if check_nmi_watchdog doesnt report it
as stuck? If yes please put a return on top of check_nmi_watchdog
that should fix it. You can verify it works by looking at the
per CPU NMI counters in /proc/interrupts. An nmi watchdog
backtrace would be nice to see.
-Andi
next prev parent reply other threads:[~2005-04-26 14:23 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-24 4:08 Parag Warudkar
2005-04-24 8:41 ` Alexander Nyberg
2005-04-24 13:03 ` Ed Tomlinson
2005-04-24 13:35 ` ismail dönmez
2005-04-25 8:44 ` Patrick McHardy
2005-04-25 15:35 ` Andi Kleen
2005-04-25 18:14 ` Alexander Nyberg
2005-04-26 0:04 ` Patrick McHardy
2005-04-26 8:26 ` Alexander Nyberg
2005-04-26 13:04 ` Patrick McHardy
2005-04-26 13:53 ` Andi Kleen
2005-04-26 13:57 ` Patrick McHardy
2005-04-26 14:18 ` Patrick McHardy
2005-04-26 14:22 ` Andi Kleen [this message]
2005-04-26 14:51 ` Patrick McHardy
2005-04-26 14:53 ` Andi Kleen
2005-04-26 15:04 ` Patrick McHardy
2005-04-27 12:59 ` Andi Kleen
2005-04-27 22:05 ` Patrick McHardy
2005-04-26 20:28 ` Patrick McHardy
2005-04-24 21:58 Parag Warudkar
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=20050426142252.GJ5098@wotan.suse.de \
--to=ak@suse.de \
--cc=alexn@dsv.su.se \
--cc=kaber@trash.net \
--cc=kernel-stuff@comcast.net \
--cc=linux-kernel@vger.kernel.org \
--cc=tomlins@cam.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