From: luizluca@gmail.com
To: devel@edk2.groups.io
Subject: Too little and too quick UEFI HTTPv6 error messages
Date: Thu, 26 Jan 2023 19:03:46 -0300 [thread overview]
Message-ID: <CAJq09z5YnzupbS+e5idqQHXD7mU8g7dNGT2WMK9EWe1Y9=56Tg@mail.gmail.com> (raw)
Hello,
I'm not an UEFI dev but a sysadm using UEFI to netboot using PXE/HTTP IPv4/IPv6.
It took a lot of time for me to discover why the firmware was failing
to accept the URL offered by the DHCPv6 server. I only got this pretty
quick message:
"Error: Could not retrieve NBP file size from HTTP server."
I needed to record it using a camera and play it frame by frame to be
able to read it from a real HW. However, that didn't give me a clue
about what was happening. After I read the code (I'm also a dev), I
noticed that many conditions could lead to that same error message. In
my case, it was the server not setting the content-type to
application/efi.
Can't we have better error handling to inform the user what is really wrong?
Can't we have a single second of delay when an error occurs after the
boot process was attempted (i.e. after DHCP answer is good)?
Regards,
---
Luiz Angelo Daros de Luca
luizluca@gmail.com
reply other threads:[~2023-01-26 22:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-list 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='CAJq09z5YnzupbS+e5idqQHXD7mU8g7dNGT2WMK9EWe1Y9=56Tg@mail.gmail.com' \
--to=devel@edk2.groups.io \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox