The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Josh Poimboeuf <jpoimboe@redhat.com>
To: Alexander Tsoy <alexander@tsoy.me>
Cc: "Andy Lutomirski" <luto@amacapital.net>,
	"Linus Torvalds" <torvalds@linux-foundation.org>,
	"Toralf Förster" <toralf.foerster@gmx.de>,
	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 16:16:51 -0600	[thread overview]
Message-ID: <20171230221651.kbzn5xchjs5fexwm@treble> (raw)
In-Reply-To: <20171231010325.6de26fa5@laptop.puleglot.ru>

On Sun, Dec 31, 2017 at 01:03:25AM +0300, Alexander Tsoy wrote:
> > Turns out my previous code to print iret frames was a bit ...
> > misguided, to put it nicely.  Not sure what I was smoking.
> > 
> > Hopefully the below patch should fix it (in place of the previous
> > patch).  Would you mind testing again?
> > 
> 
> With that patch I get:
> 
> [    2.160017] NMI backtrace for cpu 0
> [    2.160017] CPU: 0 PID: 1 Comm: init Not tainted 4.15.0-rc5 #1
> [    2.160017] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1.fc27 04/01/2014
> [    2.160017] RIP: 0010:double_fault+0x0/0x30
> [    2.160017] RSP: 0000:fffffe8000007fd0 EFLAGS: 00010086
> [    2.160017] RAX: 00000000ffc00000 RBX: 0000000000000001 RCX: 00000000c0000101
> [    2.160017] RDX: 00000000ffff8edc RSI: 0000000000000000 RDI: fffffe8000007f58
> [    2.160017] RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000
> [    2.160017] R10: 0000000000000000 R11: 0000000000000000 R12: ffffffffa3c01426
> [    2.160017] R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
> [    2.160017] FS:  0000000000000000(0000) GS:ffff8edcffc00000(0000) knlGS:0000000000000000
> [    2.160017] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> [    2.160017] CR2: fffffe8000006f08 CR3: 000000007c153000 CR4: 00000000000006b0
> [    2.160017] Call Trace:
> [    2.160017]  <#DF>
> [    2.160017] RIP: 0010:do_double_fault+0xb/0x140
> [    2.160017] RSP: 0000:fffffe8000006f18 EFLAGS: 00010086
> [    2.160017]  </#DF>

Yes, that's more like it.  I'll clean up the patches and submit them
soon.  These nasty bugs are always a good testcase for the stack dump
code.

Thanks for testing!

-- 
Josh

  reply	other threads:[~2017-12-30 22:16 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-29 11:14 4.14.9 doesn't boot (regression) 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 [this message]
2017-12-30  9:30               ` Toralf Förster
2017-12-30  8:32             ` Toralf Förster
2017-12-30  9:53           ` Jiri Kosina

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=20171230221651.kbzn5xchjs5fexwm@treble \
    --to=jpoimboe@redhat.com \
    --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