From: Matt Fleming <matt@console-pimps.org>
To: Daniel McLellan <daniel.mclellan@gmail.com>
Cc: linux-kernel@vger.kernel.org, matt.fleming@intel.com
Subject: Re: eboot.c regression allows boot, from v3.7 on- no boot with UEFI, only legacy, bisect results
Date: Thu, 3 Apr 2014 22:03:42 +0100 [thread overview]
Message-ID: <20140403210342.GA5222@console-pimps.org> (raw)
In-Reply-To: <CAEigmK-pY+9XF4V-KRZrbiO8GY5Fs6scE+Ehm1zc5T8V2RiB9g@mail.gmail.com>
(Adding linux-efi and correct Matthew's address)
On Fri, 28 Mar, at 04:08:36PM, Daniel McLellan wrote:
> System: Hewlett-Packard product: HP EliteBook 2570p
> CPU~Dual core Intel Core i7-3520M CPU (-HT-MCP-)
> Kernel: 3.12.4-2-hplove x86_64 (64 bit) Desktop: Enlightenment 0.18.99.18202
> Distro: Arch Linux
>
>
> I believe this issue is common to only a few iterations of ivy bridge
>
> https://bbs.archlinux.org/viewtopic.php?id=156670
> https://bugs.archlinux.org/task/33745?project=1
>
> I had been patching eboot.c to v3.7 with the attached
> efi_hp_boot.patch, but due to the recent changes in eboot.c (in v3.13)
> I decided to bisect, and identified the following:
>
> # first bad commit: [dd5fc854de5fd37adfcef8a366cd21a55aa01d3d] EFI:
> Stash ROMs if they're not in the PCI BAR
>
> My next step is diffing the eboot.c from v3.13.
>
> or would a better path be to check for ivy bridge?
Daniel, could you try booting a recent kernel, without your patch
applied and with the earlyprintk=efi,keep kernel parameter.
Meanwhile I'm going to try and reproduce this error.
--
Matt Fleming, Intel Open Source Technology Center
next prev parent reply other threads:[~2014-04-03 21:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-28 20:08 eboot.c regression allows boot, from v3.7 on- no boot with UEFI, only legacy, bisect results Daniel McLellan
2014-04-03 21:03 ` Matt Fleming [this message]
[not found] ` <20140403210342.GA5222-HNK1S37rvNbeXh+fF434Mdi2O/JbrIOy@public.gmane.org>
2014-04-03 21:04 ` Matt Fleming
2014-04-03 21:04 ` 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=20140403210342.GA5222@console-pimps.org \
--to=matt@console-pimps.org \
--cc=daniel.mclellan@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matt.fleming@intel.com \
/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.