diff options
Diffstat (limited to 'gitlab/issues_text/target_i386/host_missing/accel_missing/855')
| -rw-r--r-- | gitlab/issues_text/target_i386/host_missing/accel_missing/855 | 17 |
1 files changed, 17 insertions, 0 deletions
diff --git a/gitlab/issues_text/target_i386/host_missing/accel_missing/855 b/gitlab/issues_text/target_i386/host_missing/accel_missing/855 new file mode 100644 index 000000000..27b5bbfd4 --- /dev/null +++ b/gitlab/issues_text/target_i386/host_missing/accel_missing/855 @@ -0,0 +1,17 @@ +Prebuilt seabios vgabios-stdvga binary causes onboot kernel panics for freebsd 10.0 +Description of problem: +FreeBSD 10.0 panics on boot since commit: `0221d73ce6a8e075adaa0a35a6ef853d2652b855`, see my attached screenshot of the panic. +I digged a bit into what specifically causes the issue, it seems to be caused by the precompiled `vgabios-stdvga.bin`. +I don't see this issue come up when I compile the binary myself via the `roms/` folder with different versions of gcc via gcc docker containers. +But once I compile the `vgabios-stdvga` from the `roms/` folder with a more modern Ubuntu version (21.10) using gcc 11.2, I also get panics on my `vgabios-stdvga`. +At first I thought it was caused by a different gcc version, but since the buster gcc docker container images create correctly functioning `vgabios-stdvga.bin` binaries, I think this is caused by a newer version of the linker coming from the `binutils` package. + +My local Ubuntu version has version 2.37 of the binutils package, the `gcc:11.2` container which compiles a correct `vgabios-stdvga.bin` has version `2.35.2` of the binutils package. + + +Steps to reproduce: +1. Compile any version after the mentioned commit using the precompiled seabios binaries +2. Try to boot freebsd 10.0-RELEASE +3. Kernel panic because of a page vault during the vesa module load. +Additional information: +https://mfsbsd.vx.sk/files/iso/10/amd64/mfsbsd-10.0-RELEASE-amd64.iso |