From: Borislav Petkov <bp@alien8.de>
To: Andy Lutomirski <luto@amacapital.net>
Cc: Josh Poimboeuf <jpoimboe@redhat.com>, 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: Tue, 13 Dec 2016 18:51:29 +0100 [thread overview]
Message-ID: <20161213175129.t6opvcuj5eukayki@pd.tnic> (raw)
In-Reply-To: <CALCETrVtjqXNCr22fGsmdg8ZyGSo=KO4uPMcfQNjdKr8ss5ykQ@mail.gmail.com>
On Tue, Dec 13, 2016 at 08:55:53AM -0800, Andy Lutomirski wrote:
> I want to file a GCC bug, though. This code sucks.
Looks like it started doing that with gcc-5. gcc-4.9 output looks fine here:
.globl x86_64_start_kernel
.type x86_64_start_kernel, @function
x86_64_start_kernel:
.LFB2013:
.loc 1 134 0
.cfi_startproc
pushq %rbp #
.cfi_def_cfa_offset 16
.cfi_offset 6, -16
movq %rsp, %rbp #,
.cfi_def_cfa_register 6
pushq %rbx #
.cfi_offset 3, -24
.loc 1 134 0
movq %rdi, %rbx # real_mode_data, real_mode_data
.LBB157:
.LBB158:
.LBB159:
.LBB160:
.LBB161:
.loc 3 69 0
#APP
# 69 "./arch/x86/include/asm/special_insns.h" 1
mov %cr4,%rax # val
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
prev parent reply other threads:[~2016-12-13 17:20 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
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 [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=20161213175129.t6opvcuj5eukayki@pd.tnic \
--to=bp@alien8.de \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--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).