linux-kernel - Re: EFI boot problem in 3.11

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] [day] [month] [year] [list]

Message-ID: <20131026155100.GC1982@console-pimps.org>
Date:	Sat, 26 Oct 2013 16:51:00 +0100
From:	Matt Fleming <matt@...sole-pimps.org>
To:	Jasper Bryant-Greene <jbg@...net.nz>
Cc:	linux-kernel@...r.kernel.org, linux-efi@...r.kernel.org
Subject: Re: EFI boot problem in 3.11

On Thu, 24 Oct, at 12:14:26PM, Jasper Bryant-Greene wrote:
> I have a box here which is set up for EFI boot with no boot loader.
> 
> The kernel is compiled with a built-in initrd and command line.
> 
> In 3.10 this was all working well. However, after updating to 3.11.5 a
> reboot leads to the EFI firmware boot screen appearing followed by the
> middle section of it going black (just leaving two vertical stripes of
> the EFI firmware boot screen on either side of the screen) and the
> system locking up (numlock etc do not work).
> 
> However, if I hit ‘delete’ quickly when powering on, and enter the
> firmware setup screen, I can then ‘exit without saving’ and the system
> will boot successfully — ‘save and exit’ does not work as that
> performs a full reboot while ‘exit without saving’ seems to continue
> the boot where it left off.
> 
> Due to the aforementioned graphics corruption, I am wondering whether
> it is somehow related to the frame buffer? As this is a production
> system I unfortunately do not have flexibility to try a number of
> kernel versions in-between to locate where the issue was introduced.

Nothing springs to mind and nothing jumps out of the log in
drivers/video or arch/x86/platform/efi.

The best way to figure out what's causing this issue really is to bisect
the kernel versions. What hardware are you running on?

-- 
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/