From: Maniaxx <tripleshiftone-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: linux-acpi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: PROBLEM: Kernel panic on EFI BGRT early init code (kernel 4.11/4.12rc2) [regression]
Date: Thu, 1 Jun 2017 21:13:20 +0200 [thread overview]
Message-ID: <e6d656c0-c76b-42c3-8413-0198efb8a33a@gmail.com> (raw)
In-Reply-To: <20170601015621.GA4306-0VdLhd/A9Pl+NNSt+8eSiB/sF2h8X+2i0E9HWUfgJXw@public.gmane.org>
On 01.06.2017 at 03:57 wrote Dave Young:
> This means the efi_bgrt_init failed out originally before the early init BGRT
> patch. Checking the code the only difference is current code we have no
> below code:
>
> status = acpi_get_table("BGRT", 0,
> (struct acpi_table_header **)&bgrt_tab);
> if (ACPI_FAILURE(status))
> return;
>
> So probably acpi_get_table has some more sanity checking and it failed
> early. Can you add a printk before above return to confirm it? Just test
> the old kernel without early init BGRT patch.
Doesn't fail early. I can see the printk.
next prev parent reply other threads:[~2017-06-01 19:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <86c36f9b-f633-3354-d676-7693f35dae0d@gmail.com>
[not found] ` <86c36f9b-f633-3354-d676-7693f35dae0d-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-05-26 1:23 ` PROBLEM: Kernel panic on EFI BGRT early init code (kernel 4.11/4.12rc2) [regression] Dave Young
[not found] ` <a32eea98-9576-1ee7-c27a-b165204d825f@gmail.com>
[not found] ` <a32eea98-9576-1ee7-c27a-b165204d825f-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-05-27 5:14 ` Dave Young
[not found] ` <20170527051427.GA3492-0VdLhd/A9Pl+NNSt+8eSiB/sF2h8X+2i0E9HWUfgJXw@public.gmane.org>
2017-05-27 5:34 ` Dave Young
[not found] ` <20170527053457.GB3492-0VdLhd/A9Pl+NNSt+8eSiB/sF2h8X+2i0E9HWUfgJXw@public.gmane.org>
2017-06-01 1:17 ` Maniaxx
2017-06-01 1:57 ` Dave Young
[not found] ` <20170601015621.GA4306-0VdLhd/A9Pl+NNSt+8eSiB/sF2h8X+2i0E9HWUfgJXw@public.gmane.org>
2017-06-01 19:13 ` Maniaxx [this message]
2017-06-02 2:51 ` Dave Young
2017-06-03 18:24 ` Maniaxx
2017-06-04 0:11 ` Maniaxx
2017-06-04 2:45 ` Maniaxx
2017-06-07 8:57 ` Dave Young
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=e6d656c0-c76b-42c3-8413-0198efb8a33a@gmail.com \
--to=tripleshiftone-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=linux-acpi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.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