From: Matt Fleming <matt-HNK1S37rvNbeXh+fF434Mdi2O/JbrIOy@public.gmane.org>
To: Jasper Bryant-Greene <jbg-NpJDBqUeXo2lVyrhU4qvOw@public.gmane.org>
Cc: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: EFI boot problem in 3.11
Date: Sat, 26 Oct 2013 16:51:00 +0100 [thread overview]
Message-ID: <20131026155100.GC1982@console-pimps.org> (raw)
In-Reply-To: <32EA1272-FF5B-4FAA-B136-1447BF6F9876-NpJDBqUeXo2lVyrhU4qvOw@public.gmane.org>
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
WARNING: multiple messages have this Message-ID (diff)
From: Matt Fleming <matt@console-pimps.org>
To: Jasper Bryant-Greene <jbg@rf.net.nz>
Cc: linux-kernel@vger.kernel.org, linux-efi@vger.kernel.org
Subject: Re: EFI boot problem in 3.11
Date: Sat, 26 Oct 2013 16:51:00 +0100 [thread overview]
Message-ID: <20131026155100.GC1982@console-pimps.org> (raw)
In-Reply-To: <32EA1272-FF5B-4FAA-B136-1447BF6F9876@rf.net.nz>
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
next prev parent reply other threads:[~2013-10-26 15:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-23 23:14 EFI boot problem in 3.11 Jasper Bryant-Greene
[not found] ` <32EA1272-FF5B-4FAA-B136-1447BF6F9876-NpJDBqUeXo2lVyrhU4qvOw@public.gmane.org>
2013-10-26 15:51 ` Matt Fleming [this message]
2013-10-26 15:51 ` 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=20131026155100.GC1982@console-pimps.org \
--to=matt-hnk1s37rvnbexh+ff434mdi2o/jbrioy@public.gmane.org \
--cc=jbg-NpJDBqUeXo2lVyrhU4qvOw@public.gmane.org \
--cc=linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-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 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.