lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140403210342.GA5222@console-pimps.org>
Date:	Thu, 3 Apr 2014 22:03:42 +0100
From:	Matt Fleming <matt@...sole-pimps.org>
To:	Daniel McLellan <daniel.mclellan@...il.com>
Cc:	linux-kernel@...r.kernel.org, matt.fleming@...el.com
Subject: Re: eboot.c regression allows boot, from v3.7 on- no boot with UEFI,
 only legacy, bisect results

(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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ