openslx-ng/ipxe.git/src/interface/efi, branch master

[efi] Blacklist the Dell Ip4ConfigDxe driver

2019-02-19T19:02:11+00:00

On a Dell OptiPlex 7010, calling DisconnectController() on the LOM device handle will lock up the system. Debugging shows that execution is trapped in an infinite loop that is somehow trying to reconnect drivers (without going via ConnectController()). The problem can be reproduced in the UEFI shell with no iPXE code present, by using the "disconnect" command. Experimentation shows that the only fix is to unload (rather than just disconnect) the "Ip4ConfigDxe" driver. Add the concept of a blacklist of UEFI drivers that will be automatically unloaded when iPXE runs as an application, and add the Dell Ip4ConfigDxe driver to this blacklist. Signed-off-by: Michael Brown

[init] Show startup and shutdown function names in debug messages

2019-01-25T14:53:43+00:00

Signed-off-by: Michael Brown

[efi] Fix error handling path in efi_snp_probe

2019-01-15T14:01:17+00:00

Current (simplified): 1. InstallMultipleProtocolInterfaces if err goto err_install_protocol_interface; 2. OpenProtocol(efi_nii_protocol_guid) if err goto err_open_nii; 3. OpenProtocol(efi_nii31_protocol_guid) if err goto err_open_nii31; 4. efi_child_add if err goto err_efi_child_add; ... err_efi_child_add: CloseProtocol(efi_nii_protocol_guid) <= should be efi_nii31_protocol_guid err_open_nii: <= should be err_open_nii31 CloseProtocol(efi_nii31_protocol_guid) <= should be efi_nii_protocol_guid err_open_nii31: <= should be err_open_nii UninstallMultipleProtocolInterfaces Signed-off-by: Ignat Korchagin Signed-off-by: Michael Brown

[efi] Exclude link-layer header length from MaxPacketSize

2018-07-07T19:12:10+00:00

Modified-by: Michael Brown Signed-off-by: Michael Brown

[efi] Do not raise TPL within EFI_DRIVER_BINDING_PROTOCOL.Supported()

2018-03-26T11:10:09+00:00

When booting some versions of the UEFI shell, our driver binding protocol's Supported() entry point is called at TPL_NOTIFY for no discernible reason. Attempting to raise to TPL_CALLBACK triggers an immediate assertion failure in the firmware. Since our Supported() method can run at any TPL, fix by simply not attempting to raise the TPL within this method. Signed-off-by: Michael Brown

[efi] Release SNP devices before starting SAN boot image

2018-03-26T10:31:41+00:00

Release SNP devices to allow the SAN booted image to use our EFI_SIMPLE_NETWORK_PROTOCOL instance, and to ensure that the image is started at TPL_APPLICATION. Signed-off-by: Michael Brown

[efi] Raise TPL within EFI_DRIVER_BINDING_PROTOCOL entry points

2018-03-14T23:55:28+00:00

Debugged-by: Rob Taglang Signed-off-by: Michael Brown

[efi] Drop to TPL_APPLICATION when gathering entropy

2018-03-12T11:02:19+00:00

Commit c89a446 ("[efi] Run at TPL_CALLBACK to protect against UEFI timers") introduced a regression in the EFI entropy gathering code. When the EFI_RNG_PROTOCOL is not present, we fall back to using timer interrupts (as for the BIOS build). Since timer interrupts are disabled at TPL_CALLBACK, WaitForEvent() fails and no entropy can be gathered. Fix by dropping to TPL_APPLICATION while entropy gathering is enabled. Reported-by: Andreas Hammarskjöld Tested-by: Andreas Hammarskjöld Signed-off-by: Michael Brown

[efi] Raise TPL within EFI_USB_IO_PROTOCOL entry points

2018-02-20T11:19:39+00:00

Signed-off-by: Michael Brown

[efi] Raise TPL within EFI_SIMPLE_NETWORK_PROTOCOL entry points

2018-02-20T11:19:21+00:00

Signed-off-by: Michael Brown