From: Josh Poimboeuf <jpoimboe@redhat.com>
To: Borislav Petkov <bp@alien8.de>
Cc: x86-ml <x86@kernel.org>, lkml <linux-kernel@vger.kernel.org>,
Andy Lutomirski <luto@kernel.org>
Subject: Re: WARNING: kernel stack frame pointer at ffffffff82e03f40 in swapper:0 has bad value (null)
Date: Mon, 12 Dec 2016 15:16:27 -0600 [thread overview]
Message-ID: <20161212211627.yuodrw35xwq3hmn7@treble> (raw)
In-Reply-To: <20161212181025.uz3gk3jasuskqfmf@treble>
On Mon, Dec 12, 2016 at 12:10:25PM -0600, Josh Poimboeuf wrote:
> On Mon, Dec 12, 2016 at 06:50:23PM +0100, Borislav Petkov wrote:
> > [ 0.000000] ffffffffbce03f40: 0000000000000000 ...
> > [ 0.000000] ffffffffbce03f48: ffffffffbc0001b5 (start_cpu+0x5/0x14)
> > [ 0.000000] ffffffffbce03f50: ffffffffbc0001b5 (start_cpu+0x5/0x14)
> > [ 0.000000] ffffffffbce03f58: 0000000000000000 ...
> > [ 0.000000] Linux version 4.9.0-rc8+ (root@gondor) (gcc version 6.2.0 20161109 (Debian 6.2.0-13) ) #2 SMP PREEMPT Mon Dec 12 18:36:48 CET 2016
>
> Something funky is going on in the head code. It looks like start_cpu
> is getting executed twice somehow. Need to do some more head
> scratching...
I still can't figure out what could cause this, nor can I recreate it.
Andy, any idea? I'm trying to figure out why a stack trace of the
initial task, early in start_kernel(), would show start_cpu() on the
stack *twice*. The start_cpu() entry on the stack at ffffffffbce03f50
is right where it's supposed to be. But then there's another
start_cpu() entry at 0xffffffffbce03f48 which is pointed to by the frame
pointer chain. I can't figure out where that one came from and why the
stack is offset by a word, compared to all the other idle task stacks
I've seen.
Boris, what kind of CPU is it?
--
Josh
next prev parent reply other threads:[~2016-12-12 21:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-10 16:17 WARNING: kernel stack frame pointer at ffffffff82e03f40 in swapper:0 has bad value (null) Borislav Petkov
2016-12-10 17:04 ` Josh Poimboeuf
2016-12-10 17:28 ` Borislav Petkov
2016-12-12 15:45 ` Josh Poimboeuf
2016-12-12 17:50 ` Borislav Petkov
2016-12-12 18:10 ` Josh Poimboeuf
2016-12-12 21:16 ` Josh Poimboeuf [this message]
2016-12-12 21:34 ` Borislav Petkov
2016-12-12 22:11 ` Josh Poimboeuf
2016-12-12 22:33 ` Borislav Petkov
2016-12-12 23:05 ` Josh Poimboeuf
2016-12-13 14:34 ` Josh Poimboeuf
2016-12-13 16:55 ` Andy Lutomirski
2016-12-13 17:26 ` Josh Poimboeuf
2016-12-13 17:51 ` Borislav Petkov
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=20161212211627.yuodrw35xwq3hmn7@treble \
--to=jpoimboe@redhat.com \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.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;
as well as URLs for NNTP newsgroup(s).