From: Yuanhan Liu <yuanhan.liu@linux.intel.com>
To: lkp@lists.01.org
Subject: Re: [dmi] PANIC: early exception 0e rip 10:ffffffff81899e6b error 9 cr2 ffffffffff240000
Date: Fri, 07 Nov 2014 15:37:20 +0800 [thread overview]
Message-ID: <20141107073720.GB24745@yliu-dev.sh.intel.com> (raw)
In-Reply-To: <CAKv+Gu9_ipZe-BV_CxhYVdv2mPrab3EXdznJUd-Unbw3usmckw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3254 bytes --]
On Fri, Nov 07, 2014 at 08:17:36AM +0100, Ard Biesheuvel wrote:
> On 7 November 2014 06:47, LKP <lkp@01.org> wrote:
> > FYI, we noticed the below changes on
> >
> > https://git.linaro.org/people/ard.biesheuvel/linux-arm efi-for-3.19
> > commit aacdce6e880894acb57d71dcb2e3fc61b4ed4e96 ("dmi: add support for SMBIOS 3.0 64-bit entry point")
> >
> >
> > +-----------------------+------------+------------+
> > | | 2fa165a26c | aacdce6e88 |
> > +-----------------------+------------+------------+
> > | boot_successes | 20 | 10 |
> > | early-boot-hang | 1 | |
> > | boot_failures | 0 | 5 |
> > | PANIC:early_exception | 0 | 5 |
> > +-----------------------+------------+------------+
> >
> >
> > [ 0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000036fffffff] usable
> > [ 0.000000] bootconsole [earlyser0] enabled
> > [ 0.000000] NX (Execute Disable) protection: active
> > PANIC: early exception 0e rip 10:ffffffff81899e6b error 9 cr2 ffffffffff240000
> > [ 0.000000] CPU: 0 PID: 0 Comm: swapper Not tainted 3.18.0-rc2-gc5221e6 #1
> > [ 0.000000] 0000000000000000 ffffffff82203d30 ffffffff819f0a6e 00000000000003f8
> > [ 0.000000] ffffffffff240000 ffffffff82203e18 ffffffff823701b0 ffffffff82511401
> > [ 0.000000] 0000000000000000 0000000000000ba3 0000000000000000 ffffffffff240000
> > [ 0.000000] Call Trace:
> > [ 0.000000] [<ffffffff819f0a6e>] dump_stack+0x4e/0x68
> > [ 0.000000] [<ffffffff823701b0>] early_idt_handler+0x90/0xb7
> > [ 0.000000] [<ffffffff823c80da>] ? dmi_save_one_device+0x81/0x81
> > [ 0.000000] [<ffffffff81899e6b>] ? dmi_table+0x3f/0x94
> > [ 0.000000] [<ffffffff81899e42>] ? dmi_table+0x16/0x94
> > [ 0.000000] [<ffffffff823c80da>] ? dmi_save_one_device+0x81/0x81
> > [ 0.000000] [<ffffffff823c80da>] ? dmi_save_one_device+0x81/0x81
> > [ 0.000000] [<ffffffff823c7eff>] dmi_walk_early+0x44/0x69
> > [ 0.000000] [<ffffffff823c88a2>] dmi_present+0x180/0x1ff
> > [ 0.000000] [<ffffffff823c8ab3>] dmi_scan_machine+0x144/0x191
> > [ 0.000000] [<ffffffff82370702>] ? loglevel+0x31/0x31
> > [ 0.000000] [<ffffffff82377f52>] setup_arch+0x490/0xc73
> > [ 0.000000] [<ffffffff819eef73>] ? printk+0x4d/0x4f
> > [ 0.000000] [<ffffffff82370b90>] start_kernel+0x9c/0x43f
> > [ 0.000000] [<ffffffff82370120>] ? early_idt_handlers+0x120/0x120
> > [ 0.000000] [<ffffffff823704a2>] x86_64_start_reservations+0x2a/0x2c
> > [ 0.000000] [<ffffffff823705df>] x86_64_start_kernel+0x13b/0x14a
> > [ 0.000000] RIP 0x4
> >
>
> This is most puzzling. Could anyone decode the exception?
> This looks like the non-EFI path through dmi_scan_machine(), which
> calls dmi_present() /after/ calling dmi_smbios3_present(), which
> apparently has not found the _SM3_ header tag. Or could the call stack
> be inaccurate?
>
> Anyway, it would be good to know the exact type of the platform,
It's a Nehalem-EP machine, wht 16 CPU and 12G memory.
> and
> perhaps we could find out if there is an inadvertent _SM3_ tag
> somewhere in the 0xF0000 - 0xFFFFF range?
Sorry, how?
--yliu
WARNING: multiple messages have this Message-ID (diff)
From: Yuanhan Liu <yuanhan.liu@linux.intel.com>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: LKP <lkp@01.org>, Matt Fleming <matt.fleming@intel.com>,
Leif Lindholm <leif.lindholm@linaro.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [LKP] [dmi] PANIC: early exception 0e rip 10:ffffffff81899e6b error 9 cr2 ffffffffff240000
Date: Fri, 7 Nov 2014 15:37:20 +0800 [thread overview]
Message-ID: <20141107073720.GB24745@yliu-dev.sh.intel.com> (raw)
In-Reply-To: <CAKv+Gu9_ipZe-BV_CxhYVdv2mPrab3EXdznJUd-Unbw3usmckw@mail.gmail.com>
On Fri, Nov 07, 2014 at 08:17:36AM +0100, Ard Biesheuvel wrote:
> On 7 November 2014 06:47, LKP <lkp@01.org> wrote:
> > FYI, we noticed the below changes on
> >
> > https://git.linaro.org/people/ard.biesheuvel/linux-arm efi-for-3.19
> > commit aacdce6e880894acb57d71dcb2e3fc61b4ed4e96 ("dmi: add support for SMBIOS 3.0 64-bit entry point")
> >
> >
> > +-----------------------+------------+------------+
> > | | 2fa165a26c | aacdce6e88 |
> > +-----------------------+------------+------------+
> > | boot_successes | 20 | 10 |
> > | early-boot-hang | 1 | |
> > | boot_failures | 0 | 5 |
> > | PANIC:early_exception | 0 | 5 |
> > +-----------------------+------------+------------+
> >
> >
> > [ 0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000036fffffff] usable
> > [ 0.000000] bootconsole [earlyser0] enabled
> > [ 0.000000] NX (Execute Disable) protection: active
> > PANIC: early exception 0e rip 10:ffffffff81899e6b error 9 cr2 ffffffffff240000
> > [ 0.000000] CPU: 0 PID: 0 Comm: swapper Not tainted 3.18.0-rc2-gc5221e6 #1
> > [ 0.000000] 0000000000000000 ffffffff82203d30 ffffffff819f0a6e 00000000000003f8
> > [ 0.000000] ffffffffff240000 ffffffff82203e18 ffffffff823701b0 ffffffff82511401
> > [ 0.000000] 0000000000000000 0000000000000ba3 0000000000000000 ffffffffff240000
> > [ 0.000000] Call Trace:
> > [ 0.000000] [<ffffffff819f0a6e>] dump_stack+0x4e/0x68
> > [ 0.000000] [<ffffffff823701b0>] early_idt_handler+0x90/0xb7
> > [ 0.000000] [<ffffffff823c80da>] ? dmi_save_one_device+0x81/0x81
> > [ 0.000000] [<ffffffff81899e6b>] ? dmi_table+0x3f/0x94
> > [ 0.000000] [<ffffffff81899e42>] ? dmi_table+0x16/0x94
> > [ 0.000000] [<ffffffff823c80da>] ? dmi_save_one_device+0x81/0x81
> > [ 0.000000] [<ffffffff823c80da>] ? dmi_save_one_device+0x81/0x81
> > [ 0.000000] [<ffffffff823c7eff>] dmi_walk_early+0x44/0x69
> > [ 0.000000] [<ffffffff823c88a2>] dmi_present+0x180/0x1ff
> > [ 0.000000] [<ffffffff823c8ab3>] dmi_scan_machine+0x144/0x191
> > [ 0.000000] [<ffffffff82370702>] ? loglevel+0x31/0x31
> > [ 0.000000] [<ffffffff82377f52>] setup_arch+0x490/0xc73
> > [ 0.000000] [<ffffffff819eef73>] ? printk+0x4d/0x4f
> > [ 0.000000] [<ffffffff82370b90>] start_kernel+0x9c/0x43f
> > [ 0.000000] [<ffffffff82370120>] ? early_idt_handlers+0x120/0x120
> > [ 0.000000] [<ffffffff823704a2>] x86_64_start_reservations+0x2a/0x2c
> > [ 0.000000] [<ffffffff823705df>] x86_64_start_kernel+0x13b/0x14a
> > [ 0.000000] RIP 0x4
> >
>
> This is most puzzling. Could anyone decode the exception?
> This looks like the non-EFI path through dmi_scan_machine(), which
> calls dmi_present() /after/ calling dmi_smbios3_present(), which
> apparently has not found the _SM3_ header tag. Or could the call stack
> be inaccurate?
>
> Anyway, it would be good to know the exact type of the platform,
It's a Nehalem-EP machine, wht 16 CPU and 12G memory.
> and
> perhaps we could find out if there is an inadvertent _SM3_ tag
> somewhere in the 0xF0000 - 0xFFFFF range?
Sorry, how?
--yliu
next prev parent reply other threads:[~2014-11-07 7:37 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-07 5:47 [dmi] PANIC: early exception 0e rip 10:ffffffff81899e6b error 9 cr2 ffffffffff240000 LKP
2014-11-07 5:47 ` [LKP] " LKP
2014-11-07 7:17 ` Ard Biesheuvel
2014-11-07 7:17 ` [LKP] " Ard Biesheuvel
2014-11-07 7:37 ` Yuanhan Liu [this message]
2014-11-07 7:37 ` Yuanhan Liu
2014-11-07 7:44 ` Ard Biesheuvel
2014-11-07 7:44 ` [LKP] " Ard Biesheuvel
2014-11-07 8:13 ` Yuanhan Liu
2014-11-07 8:13 ` [LKP] " Yuanhan Liu
2014-11-07 8:23 ` Ard Biesheuvel
2014-11-07 8:23 ` [LKP] " Ard Biesheuvel
2014-11-07 8:46 ` Yuanhan Liu
2014-11-07 8:46 ` [LKP] " Yuanhan Liu
2014-11-07 9:03 ` Ard Biesheuvel
2014-11-07 9:03 ` [LKP] " Ard Biesheuvel
2014-11-07 9:26 ` Yuanhan Liu
2014-11-07 9:26 ` [LKP] " Yuanhan Liu
2014-11-07 9:35 ` Ard Biesheuvel
2014-11-07 9:35 ` [LKP] " Ard Biesheuvel
2014-11-07 9:36 ` Ard Biesheuvel
2014-11-07 9:36 ` [LKP] " Ard Biesheuvel
2014-11-07 10:14 ` Yuanhan Liu
2014-11-07 10:14 ` [LKP] " Yuanhan Liu
2014-11-07 10:16 ` Ard Biesheuvel
2014-11-07 10:16 ` [LKP] " Ard Biesheuvel
2014-11-07 9:36 ` Matt Fleming
2014-11-07 9:36 ` [LKP] " Matt Fleming
2014-11-07 9:40 ` Ard Biesheuvel
2014-11-07 9:40 ` [LKP] " Ard Biesheuvel
2014-11-07 9:16 ` Matt Fleming
2014-11-07 9:16 ` [LKP] " Matt Fleming
2014-11-07 9:30 ` Yuanhan Liu
2014-11-07 9:30 ` [LKP] " Yuanhan Liu
2014-11-07 11:07 ` Matt Fleming
2014-11-07 11:07 ` [LKP] " Matt Fleming
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=20141107073720.GB24745@yliu-dev.sh.intel.com \
--to=yuanhan.liu@linux.intel.com \
--cc=lkp@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.