[syslinux] EFI: HP + syslinux = crash
Oscar Roozen
oscar.roozen at brightcomputing.com
Mon Aug 3 07:51:15 PDT 2015
On 03-08-15 16:19, Oscar Roozen wrote:
> However(!) I did see attempts at loading ldlinux.e64 and more in the logs.
Confirmed.
Aug 03 16:42:19 demo atftpd[21115]: Advanced Trivial FTP server started
(0.7.1)
Aug 03 16:42:19 demo atftpd[21115]: Serving efi64/syslinux-e466d24.efi
to 10.141.167.251:1973
Aug 03 16:42:19 demo atftpd[21115]: Serving efi64/syslinux-e466d24.efi
to 10.141.167.251:1974
Aug 03 16:42:19 demo atftpd[21115]: Serving efi64/ldlinux.e64 to
10.141.167.251:1975
Aug 03 16:42:19 demo atftpd[21115]: Serving
efi64/pxelinux.cfg/category.default to 10.141.167.251:1976
Aug 03 16:42:19 demo atftpd[21115]: Serving
efi64/images/default-image/boot/efi64/menu.c32 to 10.141.167.251:1977
Aug 03 16:42:19 demo atftpd[21115]: Serving efi64/libcom32.c32 to
10.141.167.251:1978
Aug 03 16:42:19 demo atftpd[21115]: Serving efi64/libutil.c32 to
10.141.167.251:1979
Aug 03 16:42:19 demo atftpd[21115]: Serving
efi64/pxelinux.cfg/category.default to 10.141.167.251:1980
Aug 03 16:42:20 demo atftpd[21115]: Serving
efi64/images/default-image/boot/bootlogo.png to 10.141.167.251:1981
And then it crashes. The way it crashes appears random. Either a reboot
or a red stack trace for an exception varying from "Division by Zero"
via "Invalid Opcode" to "Page-Fault Exception". If there are any
readable label in the trace, it's this:
AslInformation+0000F1h
DxeCore+032040h
or
PeiCore+86190BDh
But most times it's just
No Image Information
Would it help if I gather more accurate statistics on these traces?
More information about the Syslinux
mailing list