From 9260319e7411ff8281700a532caa436f40120ec4 Mon Sep 17 00:00:00 2001 From: Christian Krinitsin Date: Fri, 30 May 2025 16:52:07 +0200 Subject: gitlab scraper: download in toml and text format --- .../target_missing/host_missing/accel_missing/2234 | 23 ++++++++++++++++++++++ 1 file changed, 23 insertions(+) create mode 100644 gitlab/issues_text/target_missing/host_missing/accel_missing/2234 (limited to 'gitlab/issues_text/target_missing/host_missing/accel_missing/2234') diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/2234 b/gitlab/issues_text/target_missing/host_missing/accel_missing/2234 new file mode 100644 index 000000000..55298a8dc --- /dev/null +++ b/gitlab/issues_text/target_missing/host_missing/accel_missing/2234 @@ -0,0 +1,23 @@ +upon pressing F2 failures in loading the edk2 bios interface app +Description of problem: +Cosmetic, low priority, but maybe easy to fix +Occasional failures to load the edk2 bios interface app +Workaround, retry until success +Steps to reproduce: +1. start qemu +2. press F2 when qemu guest display window pops up. When it works, it brings up the edk2 bios interface. + This bug concerns the case when it does not work + +For reasons not clear, sometimes, after pressing F2, and after qemu registered the key-stroke (F2) and responded by changing the window size, the bios interface loading process seems to abruptly stop at the following guest-display-screen with the following message. +```BdsDxe: Loading Boot0000 "UiApp" From Fv(7CB8BDC9-F8EB-F434-AAEA-3EE4AF6516A1)/FvFile(462CAA21-7614-4503-836E-8AB6F4662311)``` +![QEMU_3_21_2024_12_52_10_PM](/uploads/4f9f9a751eb2496c6c9947b34cf24893/QEMU_3_21_2024_12_52_10_PM.png) + +When the bios interface loading process does succeed, it goes to the expected screen: +![QEMU_3_21_2024_11_25_00_AM](/uploads/38b4ad718357debc798c3a804954a52d/QEMU_3_21_2024_11_25_00_AM.png) +Additional information: +Unsure if this sort of bug should go upstream to https://github.com/tianocore/edk2/issues +Herein notifying @kraxel + +Not a measured statistic, but on basis of feeling, I'd qualitatively say 4 out of 5 times it fails to bring up the bios interface. Its a bit frustrating because it feels like one has no control over it and a successful event is left to chance. + +This isn't a recent introduction/regression. I've noticed this since 8.0.0, so its been this way maybe longer. -- cgit 1.4.1