From mboxrd@z Thu Jan 1 00:00:00 1970 Subject: ArmVirtPkg: non-executable EFI_LOADER_DATA breaks GRUB on Ubuntu 22.04 To: devel@edk2.groups.io From: osy@turing.llc X-Originating-Location: San Jose, California, US (104.28.123.180) X-Originating-Platform: Mac Safari 16.5 User-Agent: GROUPS.IO Web Poster MIME-Version: 1.0 Date: Sat, 08 Jul 2023 14:16:51 -0700 Message-ID: Content-Type: multipart/alternative; boundary="7J7Hou12Jv7lpN7BumRD" --7J7Hou12Jv7lpN7BumRD Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable I have an existing install of Ubuntu 22.04 on a QEMU virtual machine which = I've decided to update the UEFI firmware. After doing so, GRUB no longer bo= ots ("Synchronous Exception" message seen). After a git bisect session, I f= ound the problematic 2997ae38739756ecba9b0de19e86032ebc689ef9. The comment = says GRUB should have been fixed in 2017, but for one reason or another, my= VM which was built in 2022 still had the issue. Regardless, I don't think = it's a good idea to break GRUB, even if it's fixed in 2017. In the very lea= st, a better error message would be preferable to crashing with an "Synchro= nous Exception." Googling this error message shows that other people may be= hitting this issue as well but the vague error symptom means its impossibl= e to know if it's the same issue or not. --7J7Hou12Jv7lpN7BumRD Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable I have an existing install of Ubuntu 22.04 on a QEMU virtual machine which = I've decided to update the UEFI firmware. After doing so, GRUB no longer bo= ots ("Synchronous Exception" message seen). After a git bisect session, I f= ound the problematic 2997ae38739756ecba9b0de19e86032ebc689ef9. The comment = says GRUB should have been fixed in 2017, but for one reason or another, my= VM which was built in 2022 still had the issue. Regardless, I don't think = it's a good idea to break GRUB, even if it's fixed in 2017. In the very lea= st, a better error message would be preferable to crashing with an "Synchro= nous Exception." Googling this error message shows that other people may be= hitting this issue as well but the vague error symptom means its impossibl= e to know if it's the same issue or not. --7J7Hou12Jv7lpN7BumRD--