diff options
Diffstat (limited to 'results/classifier/118/none/1888728')
| -rw-r--r-- | results/classifier/118/none/1888728 | 64 |
1 files changed, 64 insertions, 0 deletions
diff --git a/results/classifier/118/none/1888728 b/results/classifier/118/none/1888728 new file mode 100644 index 000000000..9ef3f7c2c --- /dev/null +++ b/results/classifier/118/none/1888728 @@ -0,0 +1,64 @@ +ppc: 0.768 +user-level: 0.755 +performance: 0.688 +device: 0.688 +files: 0.668 +vnc: 0.644 +risc-v: 0.623 +PID: 0.616 +virtual: 0.602 +debug: 0.599 +kernel: 0.576 +permissions: 0.569 +graphic: 0.566 +network: 0.558 +arm: 0.535 +architecture: 0.532 +TCG: 0.528 +boot: 0.521 +VMM: 0.520 +peripherals: 0.494 +register: 0.487 +socket: 0.486 +semantic: 0.446 +i386: 0.445 +x86: 0.419 +hypervisor: 0.392 +KVM: 0.381 +mistranslation: 0.350 +assembly: 0.282 + +Bare chroot in linux-user fails with pgb_reserved_va: Assertion `guest_base != 0' failed. + +Trying to run a bare chroot with no additional bind mounts fails on git master (8ffa52c20d5693d454f65f2024a1494edfea65d4) with: + +root@nofan:~/qemu> chroot /local_scratch/sid-m68k-sbuild/ +qemu-m68k-static: /root/qemu/linux-user/elfload.c:2315: pgb_reserved_va: Assertion `guest_base != 0' failed. +Aborted +root@nofan:~/qemu> + +The problem can be worked around by bind-mounting /proc from the host system into the target chroot: + +root@nofan:~/qemu> mount -o bind /proc/ /local_scratch/sid-m68k-sbuild/proc/ +root@nofan:~/qemu> chroot /local_scratch/sid-m68k-sbuild/ +bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8) +(sid-m68k-sbuild)root@nofan:/# + +Host system is an up-to-date Debian unstable (2020-07-23). + +I have not been able to bisect the issue yet since there is another annoying linux-user bug (virtual memory exhaustion) that was somewhere introduced and fixed between v5.0.0 and HEAD and overshadows the original Assertion failure bug. + +Could you point me to a tar.gz with your rootfs? + +Here you go: https://people.debian.org/~glaubitz/sid-m68k-sbuild.tgz + +Thanks for looking into it! + +For the record, reproducing this problem requires root, thus +trying to reproduce it outside of a chroot is non-obvious. + +https://lists.gnu.org/archive/html/qemu-devel/2020-07/msg07224.html + +Fixed here: +https://github.com/qemu/qemu/commit/c9f8066697e0d3e77b97f6df423e9d6540b693be + |