Your message dated Fri, 12 Aug 2022 01:09:40 +0200 with message-id <[email protected]> and subject line Re: Bug#1016809: [UEFI] Installed (minimal) bookworm system hangs at boot has caused the Debian Bug report #1016809, regarding [UEFI] Installed (minimal) bookworm system hangs at boot to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 1016809: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016809 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: installation-reports Severity: normal Boot method: netinst image on QEMU Image version: debian-testing-amd64-netinst.iso from today Date: 2022-08-07 Machine: UEFI-driven qemu VM Booted with qemu-system-x86_64 -boot order=d -vga vmware -bios OVMF.fd -L . -m 1024M --enable-kvm -hda ~/qemu-img-disk-10G.img -cdrom /home/ned/installation-images/debian-daily_2022-08-07_amd64-netinst.iso Installing Debian on an UEFI-driven QEMU machine (minimal installation, only standard system task) leads to a successful installation, but the newly installed system cannot complete its boot process. It hangs forever (here on linux 5.18.0-3) with this messages [ OK ] Activated swap /dev/disk/by-uuid/f10f20e2-b6b6b-428f-8dbe-257e8d097a04 [ OK ] Reached target Swaps. [ OK ] Mounted /boot/efi. [ OK ] Reached target Local File Systems 4.720864 random: crng init done Starting Load AppArmor profiles... Starting Create Volatile Files and Directories... When installing from an older installation-image and then booting the older kernel linux 5.15.0-2, this leads to the same problem, so it's at least not somehow kernel related. I'm unable to access more logs on the qemu machine, unfortunately. Installing from today's daily image on a BIOS-driven QEMU (no UEFI) shows no problems, the installed system boots fine. So this is somehow limited to UEFI systems. Or are there specific options needed for UEFI on QEMU? Holger -- Holger Wansing <[email protected]> PGP-Fingerprint: 496A C6E8 1442 4B34 8508 3529 59F1 87CA 156E B076
--- End Message ---
--- Begin Message ---Hi, Am 12. August 2022 00:10:21 MESZ schrieb Philip Hands <[email protected]>: >Hi Holger, > >Holger Wansing <[email protected]> writes: > >... >> Anyway, let's see what happens with Philips uefi text-mode tests ... > >Have you seen this? > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016809#25 > >If you have, and were expecting something more, then please say more >about it and I'll see if I can work out a way of adding a new test. Thanks for the reminder. Now I see, that new tests have arrived in the periodic test process. That's great, thanks. Since those tests (especially the @uefi ones) have succeeded and the installed systems seem to run fine, I think I can close this bug as "an somehow unusual VM uefi configuration; not reproducible". Greets Holger -- Sent from /e/ OS on Fairphone3
--- End Message ---
