1 files changed, 63 insertions, 0 deletions
diff --git a/results/classifier/118/kernel/1639791 b/results/classifier/118/kernel/1639791
new file mode 100644
index 000000000..63e7008f7
--- /dev/null
+++ b/results/classifier/118/kernel/1639791
@@ -0,0 +1,63 @@
+kernel: 0.933
+x86: 0.865
+device: 0.861
+user-level: 0.856
+KVM: 0.804
+graphic: 0.775
+vnc: 0.753
+debug: 0.747
+files: 0.739
+performance: 0.666
+peripherals: 0.663
+semantic: 0.617
+architecture: 0.593
+PID: 0.592
+network: 0.586
+permissions: 0.582
+ppc: 0.557
+register: 0.555
+mistranslation: 0.544
+virtual: 0.530
+hypervisor: 0.496
+boot: 0.487
+risc-v: 0.433
+i386: 0.413
+TCG: 0.411
+VMM: 0.409
+socket: 0.398
+assembly: 0.394
+arm: 0.335
+
+early virtio console output is lost
+
+This is broken in git and reportedly in 2.5 through 2.7.
+
+Running a Linux kernel which includes a testsuite in initrd sometimes produces no output.
+
+Reportedly the console is sometimes not open when the early userspace tries to log output resulting in either the testsuite terminating early or not writing the output.
+
+Workaround patch is here:
+
+https://git.zx2c4.com/WireGuard/commit/?id=d2de8b0862a7fbb51a7f2f958d58f0efe4648259
+
+reportedly you would get -EBADF there when no output is generated.
+
+Also this reportedly happens with virtio console only, not virtio serial port.
+
+It seems that the author of said testsuite did not report the problem so I write it down so it does not get lost.
+
+test (in bash):
+
+n=0 ; while [ $n -lt 100 ] && grep -m 1 -F "WireGuard Test Suite on Linux 4.8.6" <( /opt/qemu/bin/qemu-system-x86_64         -nodefaults         -nographic         -machine q35,accel=kvm         -cpu host         -smp 2         -m 64M         -object rng-random,id=rng0,filename=/dev/urandom         -device virtio-rng-pci,rng=rng0         -device virtio-serial,max_ports=2         -chardev stdio,id=stdio         -device virtconsole,chardev=stdio         -chardev file,id=status,path=result.txt         -device virtserialport,chardev=status         -monitor none         -kernel wireguard-testing-harness-bzImage-e87cb2a7-145c-4985-907f-17e81fae329b         -append "console=hvc0 initcall_debug=1 loglevel=7" ) ; do echo $n ; n=$(expr $n + 1) ; pkill -f wireguard ; done
+
+This typically does 10-20 iterations but sometimes tens of iterations run without issue.
+
+
+
+The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting all older bugs to
+"Incomplete" now.
+If you still think this bug report here is valid, then please switch the state back to "New" within the next 60 days, otherwise this report will be marked as "Expired". Thank you and sorry for the inconvenience.
+
+
+[Expired for QEMU because there has been no activity for 60 days.]
+