[Bug 1921664] Re: Coroutines are racy for risc64 emu on arm64 - crash on Assertion
No, as I described in great detail it has nothing to do with the attached devices. I just noticed that the bug was excused away as being do to the “slow” RPi 4. I’ll share that I originally hit it on Apple’s M1 but as I expect my environment might be too unusual I replicated it on RPi 4. I have since switched to building qemu from source so I don’t know if it still happens. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921664 Title: Coroutines are racy for risc64 emu on arm64 - crash on Assertion To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1921664/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921664] Re: Recent update broke qemu-system-riscv64
That would explain why I could reproduce with personal builds. Glibc looks very relevant here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921664 Title: Recent update broke qemu-system-riscv64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1921664/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921664] Re: Recent update broke qemu-system-riscv64
couldN’T, grr -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921664 Title: Recent update broke qemu-system-riscv64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1921664/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921664] Re: Recent update broke qemu-system-riscv64
Small correction: everything I've done have been everything 64-bit. I don't use armhf. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921664 Title: Recent update broke qemu-system-riscv64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1921664/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921664] Re: Recent update broke qemu-system-riscv64
FWIW: I went full inception and ran QEMU/RISC-V under QEMU/RISC-V but I couldn't reproduce the issue here (that is, everything worked, but very slowly). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921664 Title: Recent update broke qemu-system-riscv64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1921664/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921664] Re: Recent update broke qemu-system-riscv64
I'm not sure how I was _supposed_ to do this, but I checked out the official release and then switch to the hirsute-delta-as-commits- lp1921664 (6c7e3708580ac50f78261a82b2fcdc2f288d6cea) branch which kept the directories around. I configured with "--target- list=riscv64-softmmu" to save time and the resulting binary did *not* reproduce the bug. So in summary: - Debian 1:5.2+dfsg-9ubuntu1 reproduces the issue of both RPi4 and my M1 VM. - So far no version I have built have reproduced the issue. Definitely makes either _how_ I built it or the _build tools_ I used sus I'm not sure what to do next. I assume I'm supposed to set the bug back to "new"? ** Changed in: qemu (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921664 Title: Recent update broke qemu-system-riscv64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1921664/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921664] Re: Recent update broke qemu-system-riscv64
Christian, I think I need some help. Like I said I couldn't build with apt source --compile qemu. I proceeded with $ git clone -b hirsute-delta-as-commits-lp1921664 git+ssh://tommy- ubuntu...@git.launchpad.net/~paelzer/ubuntu/+source/qemu (git submodule update --init did nothing) but the configure step failed with $ ../configure warn: ignoring non-existent submodule meson warn: ignoring non-existent submodule dtc warn: ignoring non-existent submodule capstone warn: ignoring non-existent submodule slirp cross containers no NOTE: guest cross-compilers enabled: cc s390x-linux-gnu-gcc cc s390x-linux-gnu-gcc /usr/bin/python3: can't open file '/home/tommy/qemu/meson/meson.py': [Errno 2] No such file or directory /usr/bin/python3: can't open file '/home/tommy/qemu/meson/meson.py': [Errno 2] No such file or directory I had no problem building the master branch so I'm not sure what's going on with the submodules in your repo. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921664 Title: Recent update broke qemu-system-riscv64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1921664/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921664] Re: Recent update broke qemu-system-riscv64
On my 4 GB Raspberry Pi 4 QEMU emulator version 5.2.0 (Debian 1:5.2+dfsg-3ubuntu1) worked as expected as did, but QEMU emulator version 5.2.0 (Debian 1:5.2+dfsg-9ubuntu1) *did* reproduce the issue, but it took slightly longer to hit it (a few minutes): ``` ... [ OK ] Started Serial Getty on ttyS0. [ OK ] Reached target Login Prompts. Ubuntu 20.04 LTS Ubuntu-riscv64 ttyS0 Ubuntu-riscv64 login: qemu-system-riscv64: ../../util/qemu-coroutine-lock.c:57: qemu_co_queue_wait_impl: Assertion `qemu_in_coroutine()' failed. ./run_riscvVM.sh: line 31: 2304 Aborted (core dumped) qemu-system-riscv64 -machine virt -nographic -smp 4 -m 3G -bios fw_payload.bin -device virtio-blk-device,drive=hd0 -object rng-random,filename=/dev/urandom,id=rng0 -device virtio-rng-device,rng=rng0 -drive file=riscv64-UbuntuFocal-qemu.qcow2,format=qcow2,id=hd0 -device virtio-net-device,netdev=usernet -netdev user,id=usernet,$ports ``` -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921664 Title: Recent update broke qemu-system-riscv64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1921664/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921664] Re: Recent update broke qemu-system-riscv64
> Maybe it depends on what arm platform (as there are often subtle differences) > or which storage (as > the assert is about storage) you run on. > My CPU is an X-Gene and my Storage is a ZFS (that backs my container running > hirsute and Hirsute's > qemu). > What is it for you? Sorry, I thought I had already reported that, but it's not clear. My setup is special in a couple of ways: - I'm running Ubuntu/Arm64 (21.04 beta, fully up-to-date except kernel), but ... - it's a virtual machine on a macOS/Mac Mini M1 (fully up-to-date) - It's running the 5.8.0-36-generic which isn't the latest (for complicated reasons) I'll try to bring my Raspberry Pi 4 back up on Ubuntu and see if I can reproduce it there. > Is this failing 100% of the times for you, or just sometimes and maybe racy? 100% consistently reproducible with the official packages. 0% reproducible with my own build > A hint which versions to look at can be derived from > $ grep -- qemu-system-misc /var/log/dpkg.log Alas, I had critical space issues and /var/log was among the casualties > Could you rebuild what you get with "apt source qemu". That will be 5.2 plus > the Delta we have... TIL. I tried `apt source --compile qemu` but it complains dpkg-checkbuilddeps: error: Unmet build dependencies: gcc-alpha-linux- gnu gcc-powerpc64-linux-gnu but these packages are not available [anymore?]. I don't currently have the time to figure this out. > FYI my qemu is still busy It's hung. The boot take ~ 20 seconds on my host. Multi-minutes is not normal. If I can reproduce this on a Raspberry Pi 4, then I'll proceed with your suggestions above, otherwise I'll pause this until I can run Ubuntu natively on the Mac Mini. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921664 Title: Recent update broke qemu-system-riscv64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1921664/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921664] Re: Recent update broke qemu-system-riscv64
** Changed in: qemu (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921664 Title: Recent update broke qemu-system-riscv64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1921664/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921664] Re: Recent update broke qemu-system-riscv64
Self-built v5.2.0 qemu-system-riscv64 does _not_ produce the bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921664 Title: Recent update broke qemu-system-riscv64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1921664/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921664] Re: Recent update broke qemu-system-riscv64
0. Repro: $ wget https://github.com/carlosedp/riscv-bringup/releases/download/v1.0/UbuntuFocal-riscv64-QemuVM.tar.gz $ tar xzf UbuntuFocal-riscv64-QemuVM.tar.gz $ ./run_riscvVM.sh (wait ~ 20 s) [ OK ] Reached target Local File Systems (Pre). [ OK ] Reached target Local File Systems. Starting udev Kernel Device Manager... qemu-system-riscv64: ../../block/aio_task.c:64: aio_task_pool_wait_one: Assertion `qemu_coroutine_self() == pool->main_co' failed. (root password is "riscv" fwiw) 1. "Was the formerly working version 1:5.2+dfsg-6ubuntu2?" I'm afraid I don't know, but I update a few times a week. If you can tell me know to try individual versions, I'll do that 2. "full commandline you use to start your qemu test case?" Probably the repo above is more useful, but FWIW: qemu-system-riscv64 \ -machine virt \ -nographic \ -smp 4 \ -m 4G \ -bios fw_payload.bin \ -device virtio-blk-device,drive=hd0 \ -object rng-random,filename=/dev/urandom,id=rng0 \ -device virtio-rng-device,rng=rng0 \ -drive file=riscv64-UbuntuFocal-qemu.qcow2,format=qcow2,id=hd0 \ -device virtio-net-device,netdev=usernet \ -netdev user,id=usernet,$ports 3. "the same 1:5.2+dfsg-9ubuntu1 @amd64 it works fine for you? Just the emulation of riscv64 on arm64 HW is what now fails for you correct?" Yes x 2, confirmed with the above repro. $ apt-cache policy qemu qemu: Installed: 1:5.2+dfsg-9ubuntu1 Candidate: 1:5.2+dfsg-9ubuntu1 Version table: *** 1:5.2+dfsg-9ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu hirsute/universe amd64 Packages 100 /var/lib/dpkg/status 4. "It also is interesting that you built qemu from git to have it work. Did you build tag v5.2.0 or the latest commit?" latest. Rebuilding from the "vommit" tagged with v5.2.0 ... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921664 Title: Recent update broke qemu-system-riscv64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1921664/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921664] Re: Recent update broke qemu-system-riscv64
FWIW, I just now built qemu-system-riscv64 from git ToT and that works fine. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921664 Title: Recent update broke qemu-system-riscv64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1921664/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921664] [NEW] Recent update broke qemu-system-riscv64
Public bug reported: I regularly run a RISC-V (RV64GC) QEMU VM, but an update a few days ago broke it. Now when I launch it, it hits an assertion: OpenSBI v0.6 _ _ / __ \ / | _ \_ _| | | | |_ __ ___ _ __ | (___ | |_) || | | | | | '_ \ / _ \ '_ \ \___ \| _ < | | | |__| | |_) | __/ | | |) | |_) || |_ \/| .__/ \___|_| |_|_/|/_| | | |_| ... Found /boot/extlinux/extlinux.conf Retrieving file: /boot/extlinux/extlinux.conf 618 bytes read in 2 ms (301.8 KiB/s) RISC-V Qemu Boot Options 1: Linux kernel-5.5.0-dirty 2: Linux kernel-5.5.0-dirty (recovery mode) Enter choice: 1:Linux kernel-5.5.0-dirty Retrieving file: /boot/initrd.img-5.5.0-dirty qemu-system-riscv64: ../../block/aio_task.c:64: aio_task_pool_wait_one: Assertion `qemu_coroutine_self() == pool->main_co' failed. ./run.sh: line 31: 1604 Aborted (core dumped) qemu-system-riscv64 -machine virt -nographic -smp 8 -m 8G -bios fw_payload.bin -device virtio-blk-devi ce,drive=hd0 -object rng-random,filename=/dev/urandom,id=rng0 -device virtio-rng-device,rng=rng0 -drive file=riscv64-UbuntuFocal-qemu.qcow2,format=qcow2,id=hd0 -devi ce virtio-net-device,netdev=usernet -netdev user,id=usernet,$ports Interestingly this doesn't happen on the AMD64 version of Ubuntu 21.04 (fully updated). Think you have everything already, but just in case: $ lsb_release -rd Description:Ubuntu Hirsute Hippo (development branch) Release:21.04 $ uname -a Linux minimacvm 5.11.0-11-generic #12-Ubuntu SMP Mon Mar 1 19:27:36 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux (note this is a VM running on macOS/M1) $ apt-cache policy qemu qemu: Installed: 1:5.2+dfsg-9ubuntu1 Candidate: 1:5.2+dfsg-9ubuntu1 Version table: *** 1:5.2+dfsg-9ubuntu1 500 500 http://ports.ubuntu.com/ubuntu-ports hirsute/universe arm64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: qemu 1:5.2+dfsg-9ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic aarch64 ApportVersion: 2.20.11-0ubuntu61 Architecture: arm64 CasperMD5CheckResult: unknown CurrentDmesg: Error: command ['pkexec', 'dmesg'] failed with exit code 127: polkit-agent-helper-1: error response to PolicyKit daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie Error executing command as another user: Not authorized This incident has been reported. Date: Mon Mar 29 02:33:25 2021 Dependencies: KvmCmdLine: COMMAND STAT EUID RUID PIDPPID %CPU COMMAND Lspci-vt: -[:00]-+-00.0 Apple Inc. Device f020 +-01.0 Red Hat, Inc. Virtio network device +-05.0 Red Hat, Inc. Virtio console +-06.0 Red Hat, Inc. Virtio block device \-07.0 Red Hat, Inc. Virtio RNG Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: console=hvc0 root=/dev/vda SourcePackage: qemu UpgradeStatus: Upgraded to hirsute on 2020-12-30 (88 days ago) acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 127: polkit-agent-helper-1: error response to PolicyKit daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie Error
