From: Jiri Kosina <jikos@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Toralf Förster" <toralf.foerster@gmx.de>,
"Alexander Tsoy" <alexander@tsoy.me>,
"Andy Lutomirski" <luto@amacapital.net>,
stable <stable@vger.kernel.org>,
"Linux Kernel" <linux-kernel@vger.kernel.org>,
"the arch/x86 maintainers" <x86@kernel.org>
Subject: Re: 4.14.9 doesn't boot (regression)
Date: Sat, 30 Dec 2017 10:53:33 +0100 (CET) [thread overview]
Message-ID: <alpine.LRH.2.00.1712301049580.1449@gjva.wvxbf.pm> (raw)
In-Reply-To: <CA+55aFwfHEr1mSmHyvmSeFJvxMnpN=NPgJ21zEOkDPvZ2y4wXg@mail.gmail.com>
On Fri, 29 Dec 2017, Linus Torvalds wrote:
> Ok, so what does seem to be consistent for everybody is that
> double-fault in the NMI backtrace.
>
> So the fact that the NMI always hits on a double-fault does make me
> suspect that it's a infinite stream of double-faults, and that is
> presumably also what causes the RCU timeout.
As I've been fighting with recursive double-faults lately (backporting PTI
to ancient kernels), I can tell you that this is not the symptom you'd be
seeing in such case; recursive double fault pretty quickly overflows the
interrupt stack and triple-faults.
--
Jiri Kosina
SUSE Labs
prev parent reply other threads:[~2017-12-30 10:02 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-29 11:14 Toralf Förster
2017-12-29 13:33 ` Sebastian Gottschall
2017-12-29 13:38 ` Toralf Förster
2017-12-29 15:29 ` Andy Shevchenko
2017-12-29 15:48 ` Alexander Tsoy
2017-12-29 15:52 ` Toralf Förster
2017-12-29 20:12 ` Linus Torvalds
2017-12-29 20:21 ` Ingo Molnar
2017-12-29 21:02 ` Toralf Förster
2017-12-29 21:17 ` Linus Torvalds
2017-12-29 21:39 ` Linus Torvalds
2017-12-29 22:04 ` Alexander Tsoy
2017-12-29 22:30 ` Toralf Förster
2017-12-29 22:53 ` Linus Torvalds
2017-12-29 23:14 ` Toralf Förster
2017-12-30 0:10 ` Andy Lutomirski
2017-12-30 1:00 ` Linus Torvalds
2017-12-30 1:34 ` Linus Torvalds
2017-12-30 9:14 ` Alexander Tsoy
2017-12-30 9:21 ` Toralf Förster
2017-12-30 1:13 ` Alexander Tsoy
2017-12-30 12:58 ` Toralf Förster
2017-12-30 13:14 ` Jiri Kosina
2017-12-30 3:49 ` Josh Poimboeuf
2017-12-30 8:45 ` Alexander Tsoy
2017-12-30 17:09 ` Josh Poimboeuf
2017-12-30 17:57 ` Josh Poimboeuf
2017-12-30 22:03 ` Alexander Tsoy
2017-12-30 22:16 ` Josh Poimboeuf
2017-12-30 9:30 ` Toralf Förster
2017-12-30 8:32 ` Toralf Förster
2017-12-30 9:53 ` Jiri Kosina [this message]
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=alpine.LRH.2.00.1712301049580.1449@gjva.wvxbf.pm \
--to=jikos@kernel.org \
--cc=alexander@tsoy.me \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=stable@vger.kernel.org \
--cc=toralf.foerster@gmx.de \
--cc=torvalds@linux-foundation.org \
--cc=x86@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
all inboxes | Powered by JetHome®