[Bug 1906479] Re: qemu:handle_cpu_signal received signal outside vCPU context

2022-05-12 Thread Thomas Dreibholz
I still had the issue on an up-to-date Ubuntu 20.04 (Focal), when building arm64 packages with pbuilder on an x86_64 system: qemu:handle_cpu_signal received signal outside vCPU context @ pc=0x60277b5c qemu:handle_cpu_signal received signal outside vCPU context @ pc=0x60001a4e These are the

[Bug 1906479] Re: qemu:handle_cpu_signal received signal outside vCPU context

2021-07-23 Thread TJ
@Cyan - is that on 21.10 (Impish) because your report has changed the status for the 20.04 (Focal) report. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906479 Title: qemu:handle_cpu_signal

[Bug 1906479] Re: qemu:handle_cpu_signal received signal outside vCPU context

2021-07-12 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: qemu (Ubuntu Focal) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906479 Title:

[Bug 1906479] Re: qemu:handle_cpu_signal received signal outside vCPU context

2021-07-12 Thread Cyan Chou
The same bug still shows when I run an i386 binary on mips64el platform using qemu-i386. $./rastertokpsl qemu:handle_cpu_signal received signal outside vCPU context @ pc=0x71db858e I'm using qemu 6.0.0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 1906479] Re: qemu:handle_cpu_signal received signal outside vCPU context

2020-12-15 Thread Christian Ehrhardt 
Ok, let us tackle bug 1908331 then and consider breaking the fixes for this bug here into what we need afterwards. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906479 Title:

[Bug 1906479] Re: qemu:handle_cpu_signal received signal outside vCPU context

2020-12-15 Thread TJ
Hi Christian, sorry I missed your updates on this one. I've only just come back to the issue yesterday and apparently I've hit another issue: bug #1908331 "Regression: qemu-user-static binaries are dynamically linked" That side-tracked me whilst trying to do the git-bisect and I've still not

[Bug 1906479] Re: qemu:handle_cpu_signal received signal outside vCPU context

2020-12-02 Thread Christian Ehrhardt 
Hi TJ, that reminds me of some bugs for arm* chroots with static that we fixed recently. Hmm no, that was bug 1890881 which isn't completely the same - but it also was not backportable to 20.04 anyway :-/ I've checked my inbox and found plenty of upstream references to this in

[Bug 1906479] Re: qemu:handle_cpu_signal received signal outside vCPU context

2020-12-01 Thread TJ
** Description changed: On 20.04 amd64 trying to run 'aptitude full-upgrade' inside a Debian buster chroot: mkdir debian-buster-aarch64 sudo debootstrap --arch=arm64 --foreign buster debian-buster-aarch64 http://deb.debian.org/debian sudo cp -a /usr/bin/qemu-aarch64-static