From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: Possible EFI memory corruption?
Date: Sun, 20 Jan 2013 22:51:34 +0100 [thread overview]
Message-ID: <50FC66E6.1060807@gmail.com> (raw)
In-Reply-To: <50916D10.9030000@ubuntu.com>
[-- Attachment #1: Type: text/plain, Size: 1125 bytes --]
On 31.10.2012 19:25, Phillip Susi wrote:
> I've been trying to help troubleshoot a problem a user has where grub
> appears to hang before booting the kernel when he does not have a USB
> device plugged in at boot time. I had him enable debug messages and
> the last one is a malloc in script.c after an append once he executes
> the boot command, so it doesn't appear to be making it to the linux
> boot function and jumping to the kernel.
>
On EFI debug messages are cut short because of video reconfig/EFI fini.
What is the device in question? Does it when when it's in? Does he have
any USB modules loaded? Normally there shouldn't be any and GRUB
shouldn't be aware of USB at all.
> I'm not sure where to proceed from here, so perhaps someone else could
> be of help? The original bug report is here:
>
> https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1069772
>
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> https://lists.gnu.org/mailman/listinfo/grub-devel
>
--
Regards
Vladimir 'φ-coder/phcoder' Serbinenko
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 294 bytes --]
prev parent reply other threads:[~2013-01-20 21:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-31 18:25 Possible EFI memory corruption? Phillip Susi
2013-01-20 21:51 ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
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=50FC66E6.1060807@gmail.com \
--to=phcoder@gmail.com \
--cc=grub-devel@gnu.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.