Package: qemu-user-static Version: 1:5.2+dfsg-10 Severity: normal File: /usr/bin/qemu-aarch64-static X-Debbugs-Cc: pkg-raspi-maintain...@lists.alioth.debian.org
When trying to build an arm64 image for Raspberry Pi image specs (https://salsa.debian.org/raspi-team/image-specs) I and others have gotten a segfault when installing pyton3[-minimal] on a regular basis, but not always. This is essentially a 'forwarded' for an issue reported in its issue tracker: https://salsa.debian.org/raspi-team/image-specs/-/issues/42 I had to try 3 times now to trigger the issue, but now I 'succeeded'. You can reproduce it as follows: - clone the 'image-specs' repo - add 'python3' or 'python3-minimal' to the "apt: install" step - run as root or via sudo: make raspi_3_bullseye.img If it succeeds (you'll see "All went fine."), try again (and again) till it fails. Relevant part of the log file created during image built: =================================================== Setting up linux-image-5.10.0-6-arm64 (5.10.28-1) ... I: /vmlinuz.old is now a symlink to boot/vmlinuz-5.10.0-6-arm64 I: /initrd.img.old is now a symlink to boot/initrd.img-5.10.0-6-arm64 I: /vmlinuz is now a symlink to boot/vmlinuz-5.10.0-6-arm64 I: /initrd.img is now a symlink to boot/initrd.img-5.10.0-6-arm64 Setting up linux-image-arm64 (5.10.28-1) ... Setting up ssh (1:8.4p1-5) ... Processing triggers for libc-bin (2.31-11) ... Processing triggers for ca-certificates (20210119) ... Updating certificates in /etc/ssl/certs... 0 added, 0 removed; done. Running hooks in /etc/ca-certificates/update.d... done. Processing triggers for initramfs-tools (0.140) ... update-initramfs: Generating /boot/initrd.img-5.10.0-6-arm64 Processing triggers for dbus (1.12.20-2) ... 2021-05-06 23:44:24 DEBUG STDERR: E: Can not write log (Is /dev/pts mounted?) - posix_openpt (19: No such device) Moving old data out of the way Created symlink /etc/systemd/system/sysinit.target.wants/apparmor.service -> /lib/systemd/system/apparmor.service. invoke-rc.d: could not determine current runlevel ls: cannot access '/boot/initrd.img-*': No such file or directory raspi-firmware: no initrd found in /boot/initrd.img-*, cannot populate /boot/firmware Updating certificates in /etc/ssl/certs... 129 added, 0 removed; done. Segmentation fault dpkg: error processing package python3.9 (--configure): installed python3.9 package post-installation script subprocess returned error exit status 139 =================================================== And the following gets written to 'dmesg': =================================================== [38867.808238] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null) [38867.849329] show_signal_msg: 38 callbacks suppressed [38867.849331] arm64[112046]: segfault at 1e54310 ip 00000000005637c0 sp 00007ffc88256398 error 4 in qemu-aarch64-static[401000+3e3000] [38867.849339] Code: 00 e9 94 78 1c 00 0f 1f 40 00 64 83 2c 25 50 ff ff ff 01 74 05 c3 0f 1f 40 00 48 8d 3d e9 d0 7f 00 e9 e4 85 1c 00 0f 1f 40 00 <64> 8b 04 25 50 ff ff ff 85 c0 0f 9f c0 c3 66 90 48 83 ec 08 64 8b [38989.616760] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null) [39277.809928] python3.9[134304]: segfault at 24de310 ip 00000000005637c0 sp 00007ffc4cc1e6f8 error 4 in qemu-aarch64-static[401000+3e3000] [39277.809936] Code: 00 e9 94 78 1c 00 0f 1f 40 00 64 83 2c 25 50 ff ff ff 01 74 05 c3 0f 1f 40 00 48 8d 3d e9 d0 7f 00 e9 e4 85 1c 00 0f 1f 40 00 <64> 8b 04 25 50 ff ff ff 85 c0 0f 9f c0 c3 66 90 48 83 ec 08 64 8b =================================================== I noticed there's now also a segfault on 'arm64', but I don't think I've seen that before. The one that *consistently* pops up *when* it fails, is "dpkg: error processing package python3.9 (--configure)", although, thus far it was actually python3-minimal, during the '--configure' step. Normally the logical candidate to file this against is python3, but 'we' (various ppl on #debian-raspberrypi and in the previous mentioned issue) have not seen this issue on a native arm64 device or under systemd-nspawn. https://salsa.debian.org/raspi-team/image-specs/-/issues/40#note_216315 (and following) also contains several 'segfault' incidents. -- System Information: Debian Release: 11.0 APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (500, 'testing'), (101, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-6-amd64 (SMP w/16 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled qemu-user-static depends on no packages. Versions of packages qemu-user-static recommends: ii binfmt-support 2.2.1-1 Versions of packages qemu-user-static suggests: ii sudo 1.9.5p2-3 -- no debconf information
