Your message dated Mon, 11 Aug 2025 10:42:56 +0300
with message-id <[email protected]>
and subject line Re: Bug#990659: qemu-system-misc: qemu-riscv64-static
sometimes crashes while running gcc in chroot
has caused the Debian Bug report #990659,
regarding qemu-system-misc: qemu-riscv64-static sometimes crashes while running
gcc in chroot
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
990659: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990659
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: qemu-system-misc
Version: 1:5.2+dfsg-9~bpo10+1
Severity: normal
I was assembling a Debian riscv64 (and therefore, currently, sid) root FS to
test something, ultimately in a VM, and building OpenZFS git master chrooted
into that root to that end.
I did the ./autogen.sh && ./configure --with-linux=.../source
--with-linux-obj=.../build && make dance, left it alone for a bit, and came to
curiously
find it errored out with no error output printed that I saw.
Ran make again, it did not immediately error.
I then noticed in dmesg:
[1726926.715475] cc1[66416]: segfault at 2ad48a0 ip 00000000004857e0 sp
00007ffc9ef97948 error 4 in qemu-riscv64-static[401000+2cc000]
[1726926.715488] Code: 00 e9 24 fc 18 00 0f 1f 40 00 64 83 2c 25 60 ff ff ff 01
74 05 c3 0f 1f 40 00 48 8d 3d c9 6f 77 00 e9 74 0a 19 00 0f 1f 40 00 <64> 8b 04
25 60 ff ff ff 85 c0 0f 9f c0 c3 66 90 48 83 ec 08 64 8b
[1726967.092517] cc1[71234]: segfault at 2ad58a0 ip 00000000004857e0 sp
00007ffc23573a18 error 4 in qemu-riscv64-static[401000+2cc000]
[1726967.092530] Code: 00 e9 24 fc 18 00 0f 1f 40 00 64 83 2c 25 60 ff ff ff 01
74 05 c3 0f 1f 40 00 48 8d 3d c9 6f 77 00 e9 74 0a 19 00 0f 1f 40 00 <64> 8b 04
25 60 ff ff ff 85 c0 0f 9f c0 c3 66 90 48 83 ec 08 64 8b
(There's a couple more.)
(Much later on, gcc ICEd, on something it hadn't tried building before, but
that didn't reproduce on running it again...)
I have a core, from doing this dance a second time, from yet another source
file that built fine on successive runs, but I'm not sure how readily useful it
is. I'll upload it if it would be helpful.
- Rich
-- System Information:
Debian Release: 10.10
APT prefers stable-updates
APT policy: (1000, 'stable-updates'), (1000, 'stable'), (900,
'testing-debug'), (900, 'testing'), (800, 'unstable-debug'), (800, 'unstable'),
(500, 'stable-debug'), (500, 'proposed-updates-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.19.0-16-amd64 (SMP w/16 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages qemu-system-misc depends on:
ii libaio1 0.3.112-3
ii libasound2 1.1.8-1
ii libbrlapi0.6 5.6-10+deb10u1
ii libc6 2.28-10
ii libcacard0 1:2.6.1-1
ii libcapstone4 4.0.2-3
ii libepoxy0 1.5.3-0.1
ii libfdt1 1.6.0-1~bpo10+1
ii libgbm1 18.3.6-2+deb10u1
ii libgcc-s1 [libgcc1] 10.2.1-6
ii libgcc1 1:8.3.0-6
ii libglib2.0-0 2.58.3-2+deb10u3
ii libgnutls30 3.6.7-4+deb10u7
ii libibverbs1 22.1-1
ii libjpeg62-turbo 1:1.5.2-2+deb10u1
ii libncursesw6 6.1+20181013-2+deb10u2
ii libnettle6 3.4.1-1+deb10u1
ii libnuma1 2.0.12-1
ii libpixman-1-0 0.36.0-1
ii libpmem1 1.5.1-1
ii libpng16-16 1.6.36-6
ii librdmacm1 22.1-1
ii libsasl2-2 2.1.27+dfsg-1+deb10u1
ii libseccomp2 2.3.3-4
ii libslirp0 4.4.0-1
ii libspice-server1 0.14.0-1.3+deb10u1
ii libtinfo6 6.1+20181013-2+deb10u2
ii libudev1 241-7~deb10u7
ii liburing1 0.7-3
ii libusb-1.0-0 2:1.0.22-2
ii libusbredirparser1 0.8.0-1
ii libvdeplug2 2.3.2+r586-2.2
ii libvirglrenderer0 0.7.0-2
ii qemu-system-common 1:5.2+dfsg-9~bpo10+1
ii qemu-system-data 1:5.2+dfsg-9~bpo10+1
ii zlib1g 1:1.2.11.dfsg-1
Versions of packages qemu-system-misc recommends:
ii ipxe-qemu 1.0.0+git-20190125.36a4c85-1
ii qemu-system-gui 1:5.2+dfsg-9~bpo10+1
ii qemu-utils 1:5.2+dfsg-9~bpo10+1
ii seabios 1.12.0-1
Versions of packages qemu-system-misc suggests:
pn qemu-block-extra <none>
ii samba 2:4.9.5+dfsg-5+deb10u1
ii vde2 2.3.2+r586-2.2
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 1:7.2+dfsg-1
On Mon, 21 Aug 2023 18:23:32 +0300 Michael Tokarev <[email protected]> wrote:
Control: tag -1 + moreinfo
Hi!
Do you have any information about how the situation with current qemu is?
There's 8.0 in testing now (but 8.0 had its own share of linux-user bugs),
and 8.1~rc4 in experimental, - can you try 8.1 one please?
Ok. This bug report has been in "moreinfo" state for quite some time,
and it looks like the reported issue doesn't exist in bookworm already.
Let's close this bug report with bookworm version of qemu.
If you think this is incorrect, please feel free to reopen it.
Thanks,
/mjt
--- End Message ---
