add new classifier result

1 files changed, 30 insertions, 0 deletions

diff --git a/results/classifier/105/graphic/855 b/results/classifier/105/graphic/855
new file mode 100644
index 00000000..ea7ac2e3
--- /dev/null
+++ b/results/classifier/105/graphic/855
@@ -0,0 +1,30 @@
+graphic: 0.984
+boot: 0.908
+device: 0.858
+vnc: 0.856
+semantic: 0.733
+instruction: 0.716
+socket: 0.675
+network: 0.603
+other: 0.544
+mistranslation: 0.364
+KVM: 0.304
+assembly: 0.158
+
+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.
+
+![Screenshot_from_2022-02-03_17-35-59](/uploads/5bafeca625ebe8b38acd5a0d6c358392/Screenshot_from_2022-02-03_17-35-59.png)
+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