Bug#1003574: segfault in libc-2.33.so during i386 boot ofde QEMU VM
tag: control -1 + unreproducible
Hi,
On 2022-01-11 23:38, Christian Kastner wrote:
> Package: libc6
> Version: 2.33-2
> Severity: normal
>
> When booting an i386 VM built for autopkgtests, I see the following
> segfault during boot:
>
> > [ 1.374128] Freeing unused kernel image (initmem) memory: 940K
> > [ 1.384002] Write protecting kernel text and read-only data: 11292k
> > [ 1.384526] Run /init as init process
> > Loading, please wait...
> > Starting version 250.2-1
> > [ 1.406157] udevadm[106]: segfault at bc0000 ip b7d9f638 sp bf989cb8 error 6 in libc-2.33.so[b7c6e000
> > [ 1.407017] Code: 1c 8b 01 ca ff e3 29 d9 8d b4 26 00 00 00 00 8d 76 00 0f 18 8a c0 03 00 00 0f 18 8a
> > Segmentation fault
Unfortunately the error message is cut, so it is not possible to find
where the crashes happen. A segmentation fault in libc6 is not necessary
libc6's fault.
> Boot continues briefly after that, but then drops to an emergency shell.
>
> I've tried the other popular architectures, but I only saw this on i386.
>
>
> To reproduce, this requires qemu-system-x86 and autopkgtest >= 5.17.
>
> # Build image
> $ sudo autopkgtest-build-qemu \
> --mirror http://deb.debian.org/debian
> --arch i386 \
> unstable i386.img
>
> # Boot image. -enable-kvm assumes that this is being tested on amd64
> # Optionally use -nographic for terminal output instead of GUI
> $ qemu-system-i386 \
> -machine q35 \
> -enable-kvm \
You might also want to try without -enable-kvm
> -device virtio-serial \
> -nic user,model=virtio \
> -m 1024 -smp 1 \
> i386.img
Unfortunately I have not been able to reproduce this issue here, the
image boots perfectly. This is using an up to date sid system. The
version of QEMU might be an important factor, and maybe your CPU.
Regards,
Aurelien
--
Aurelien Jarno GPG: 4096R/1DDD8C9B
aurelien@aurel32.net http://www.aurel32.net
Reply to: