From: joeyli <jlee@suse.com>
To: Matt Fleming <matt@codeblueprint.co.uk>
Cc: linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org,
x86@kernel.org, Matt Fleming <matt.fleming@intel.com>,
Borislav Petkov <bp@suse.de>,
LeifLindholm@linux-rxt1.site, leif.lindholm@linaro.org,
Peter Jones <pjones@redhat.com>,
James Bottomley <JBottomley@Odin.com>,
Matthew Garrett <mjg59@srcf.ucam.org>,
"H. Peter Anvin" <hpa@zytor.com>, Dave Young <dyoung@redhat.com>,
stable@vger.kernel.org,
Ard Biesheuvel <ard.biesheuvel@linaro.org>
Subject: Re: [PATCH] x86/efi: Map EFI memmap entries in-order at runtime
Date: Wed, 9 Sep 2015 08:33:07 +0800 [thread overview]
Message-ID: <20150909003307.GJ2266@linux-rxt1.site> (raw)
In-Reply-To: <20150908204147.GC2854@codeblueprint.co.uk>
Hi Matt,
On Tue, Sep 08, 2015 at 09:41:47PM +0100, Matt Fleming wrote:
> On Mon, 07 Sep, at 12:07:52PM, joeyli wrote:
> >
> > This patch works to me on Intel S1200V3RPS to fix issue:
> > DMI: Intel Corporation (uefidk.com) Intel Server Board S1200V3RPS UEFI Development Kit/ROMLEY, BIOS 2.0
> >
> > Tested-by: Lee, Chun-Yi <jlee@suse.com>
>
> When you say "fix issue", do you mean that your machine has the
> EFI_PROPERTIES_TABLE feature enabled, and that it doesn't boot without
> this patch?
>
> --
> Matt Fleming, Intel Open Source Technology Center
Yes, the machine on my hand has EFI_PROPERTIES_TABLE enabled, and it doesn't
boot without your patch.
I captured similar kernel oops through serial port:
[ 0.037745] ACPI: All ACPI Tables successfully acquired
[ 0.044666] BUG: unable to handle kernel paging request at fffffffef0e5d450
[ 0.052451] IP: [<fffffffef0e5d450>] 0xfffffffef0e5d450
[ 0.058291] PGD 1c0d067 PUD 17fcfd063 PMD 17fd6f063 PTE 0
[ 0.064355] Oops: 0010 [#1] SMP
[ 0.067972] Modules linked in:
[ 0.071388] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.2.0-rc8-2.gc02428d-default #1
[ 0.080121] Hardware name: Intel Corporation (uefidk.com) Intel Server Board S1200V3RPS UEFI Development Kit/ROMLEY, BIOS 2.0
[ 0.092827] task: ffffffff81c114c0 ti: ffffffff81c00000 task.ti: ffffffff81c00000
[ 0.101172] RIP: 0010:[<fffffffef0e5d450>] [<fffffffef0e5d450>] 0xfffffffef0e5d450
[ 0.109724] RSP: 0000:ffffffff81c03d38 EFLAGS: 00010082
[ 0.115647] RAX: fffffffef0c5d100 RBX: fffffffef1d66040 RCX: fffffffef0c5d100
[ 0.123604] RDX: 00000000be366018 RSI: 0000000000000000 RDI: ffffffff81c38b00
[ 0.131560] RBP: 000000000000000c R08: ffffffff81c03d70 R09: ffffffff81c38b0b
[ 0.139517] R10: 0000000000000078 R11: 0000000000000002 R12: 0000000000000296
[ 0.147475] R13: ffffffff81c03eb8 R14: 0000000000000030 R15: 0000000000000007
[ 0.155432] FS: 0000000000000000(0000) GS:ffff88042e600000(0000) knlGS:0000000000000000
[ 0.164457] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 0.170864] CR2: fffffffef0e5d450 CR3: 000000000009b000 CR4: 00000000000406b0
[ 0.178819] Stack:
[ 0.181059] fffffffef10574c9 0000000000000002 0000000000000000 0000000000000000
[ 0.189351] ffffffff81c38b00 0000000000000000 fffffffef1057a4b 0000000000000058
[ 0.197645] 000000078000203c 000000000009b000 ffff8801ffd70000 000000000009b000
[ 0.205939] Call Trace:
[ 0.208669] [<ffffffff8105dd9e>] ? efi_call+0x7e/0x100
[ 0.214497] [<ffffffff81523006>] ? virt_efi_set_variable+0x66/0x90
[ 0.221487] [<ffffffff8105cd67>] ? efi_delete_dummy_variable+0x77/0x90
[ 0.228866] [<ffffffff81d41ff5>] ? efi_enter_virtual_mode+0x3ac/0x3bb
[ 0.236147] [<ffffffff81d26f24>] ? start_kernel+0x3f4/0x484
[ 0.242459] [<ffffffff81d26120>] ? early_idt_handler_array+0x120/0x120
[ 0.249835] [<ffffffff81d26315>] ? x86_64_start_reservations+0x2a/0x2c
[ 0.257212] [<ffffffff81d26452>] ? x86_64_start_kernel+0x13b/0x14a
[ 0.264200] Code: Bad RIP value.
[ 0.267916] RIP [<fffffffef0e5d450>] 0xfffffffef0e5d450
[ 0.273851] RSP <ffffffff81c03d38>
[ 0.277739] CR2: fffffffef0e5d450
[ 0.281436] ---[ end trace 19be7a419bfa9401 ]---
[ 0.286575] Kernel panic - not syncing: Attempted to kill the idle task!
[ 0.294049] Rebooting in 90 seconds..
[ 0.299184] ACPI MEMORY or I/O RESET_REG.
Thanks a lot!
Joey Lee
next prev parent reply other threads:[~2015-09-09 0:33 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-04 13:14 [PATCH] x86/efi: Map EFI memmap entries in-order at runtime Matt Fleming
2015-09-04 13:24 ` Ard Biesheuvel
2015-09-04 18:23 ` Matt Fleming
2015-09-04 18:53 ` Ard Biesheuvel
2015-09-06 14:06 ` Ard Biesheuvel
2015-09-08 13:16 ` Matt Fleming
2015-09-08 13:21 ` Ard Biesheuvel
2015-09-08 20:37 ` Matt Fleming
2015-09-09 7:37 ` Ard Biesheuvel
2015-09-09 9:58 ` Matt Fleming
2015-09-09 9:59 ` Ard Biesheuvel
2015-09-07 4:07 ` joeyli
2015-09-08 20:41 ` Matt Fleming
2015-09-09 0:33 ` joeyli [this message]
2015-09-09 11:21 ` Matt Fleming
2015-09-10 3:38 ` joeyli
2015-09-16 10:08 ` Borislav Petkov
2015-09-16 11:25 ` Ard Biesheuvel
2015-09-16 13:28 ` Borislav Petkov
2015-09-16 13:38 ` Ard Biesheuvel
2015-09-17 8:05 ` Borislav Petkov
2015-09-16 13:37 ` James Bottomley
2015-09-16 14:07 ` Ard Biesheuvel
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=20150909003307.GJ2266@linux-rxt1.site \
--to=jlee@suse.com \
--cc=JBottomley@Odin.com \
--cc=LeifLindholm@linux-rxt1.site \
--cc=ard.biesheuvel@linaro.org \
--cc=bp@suse.de \
--cc=dyoung@redhat.com \
--cc=hpa@zytor.com \
--cc=leif.lindholm@linaro.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt.fleming@intel.com \
--cc=matt@codeblueprint.co.uk \
--cc=mjg59@srcf.ucam.org \
--cc=pjones@redhat.com \
--cc=stable@vger.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).