Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1540683
| From | Borislav Petkov <bp@alien8.de> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: WARNING: kernel stack frame pointer at ffffffff82e03f40 in swapper:0 has bad value (null) |
| Date | 2016-12-12 22:40 +0100 |
| Message-ID | <sNGue-113-15@gated-at.bofh.it> (permalink) |
| References | (2 earlier) <sMTDb-54T-3@gated-at.bofh.it> <sNB1v-67R-11@gated-at.bofh.it> <sND3k-7j0-27@gated-at.bofh.it> <sNDmF-7Fp-17@gated-at.bofh.it> <sNGaS-Uq-41@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Mon, Dec 12, 2016 at 03:16:27PM -0600, Josh Poimboeuf wrote:
> I still can't figure out what could cause this, nor can I recreate it.
Want my .config?
> 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.
Btw, why do you have:
call 1f # put return address on stack for unwinder
there in start_cpu() instead of
push $start_cpu
or so? That CALL looks strange there. If you want to put the return
address, just push start_cpu's address and that's it.
Or am I missing something?
> Boris, what kind of CPU is it?
[ 0.169371] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-1620 0 @ 3.60GHz (family: 0x6, model: 0x2d, stepping: 0x7)
Sandybridge. The model 0x2d corresponds to that INTEL_FAM6_SANDYBRIDGE_X
define in intel-family.h.
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Re: WARNING: kernel stack frame pointer at ffffffff82e03f40 in swapper:0 has bad value (null) Josh Poimboeuf <jpoimboe@redhat.com> - 2016-12-12 16:50 +0100
Re: WARNING: kernel stack frame pointer at ffffffff82e03f40 in swapper:0 has bad value (null) Borislav Petkov <bp@alien8.de> - 2016-12-12 19:00 +0100
Re: WARNING: kernel stack frame pointer at ffffffff82e03f40 in swapper:0 has bad value (null) Josh Poimboeuf <jpoimboe@redhat.com> - 2016-12-12 19:20 +0100
Re: WARNING: kernel stack frame pointer at ffffffff82e03f40 in swapper:0 has bad value (null) Josh Poimboeuf <jpoimboe@redhat.com> - 2016-12-12 22:20 +0100
Re: WARNING: kernel stack frame pointer at ffffffff82e03f40 in swapper:0 has bad value (null) Borislav Petkov <bp@alien8.de> - 2016-12-12 22:40 +0100
Re: WARNING: kernel stack frame pointer at ffffffff82e03f40 in swapper:0 has bad value (null) Josh Poimboeuf <jpoimboe@redhat.com> - 2016-12-12 23:20 +0100
Re: WARNING: kernel stack frame pointer at ffffffff82e03f40 in swapper:0 has bad value (null) Borislav Petkov <bp@alien8.de> - 2016-12-12 23:40 +0100
Re: WARNING: kernel stack frame pointer at ffffffff82e03f40 in swapper:0 has bad value (null) Josh Poimboeuf <jpoimboe@redhat.com> - 2016-12-13 00:10 +0100
Re: WARNING: kernel stack frame pointer at ffffffff82e03f40 in swapper:0 has bad value (null) Josh Poimboeuf <jpoimboe@redhat.com> - 2016-12-13 15:40 +0100
Re: WARNING: kernel stack frame pointer at ffffffff82e03f40 in swapper:0 has bad value (null) Andy Lutomirski <luto@amacapital.net> - 2016-12-13 18:00 +0100
Re: WARNING: kernel stack frame pointer at ffffffff82e03f40 in swapper:0 has bad value (null) Borislav Petkov <bp@alien8.de> - 2016-12-13 18:30 +0100
Re: WARNING: kernel stack frame pointer at ffffffff82e03f40 in swapper:0 has bad value (null) Josh Poimboeuf <jpoimboe@redhat.com> - 2016-12-13 18:30 +0100
csiph-web