[Bug 1920784] Re: qemu-system-ppc64le fails with kvm acceleration
** No longer affects: qemu (Ubuntu Hirsute) ** No longer affects: qemu (Ubuntu) ** No longer affects: glibc (Ubuntu Hirsute) ** No longer affects: glibc (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920784 Title: qemu-system-ppc64le fails with kvm acceleration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1920784/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920784] Re: qemu-system-ppc64le fails with kvm acceleration
** Changed in: ubuntu-power-systems Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920784 Title: qemu-system-ppc64le fails with kvm acceleration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1920784/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920784] Re: qemu-system-ppc64le fails with kvm acceleration
This bug was fixed in the package linux - 5.11.0-14.15 --- linux (5.11.0-14.15) hirsute; urgency=medium * hirsute/linux: 5.11.0-14.15 -proposed tracker (LP: #1923103) * Packaging resync (LP: #1786013) - update dkms package versions * Include Infiniband Peer Memory interface (LP: #1923104) - SAUCE: RDMA/core: Introduce peer memory interface * Hirsute update: v5.11.12 upstream stable release (LP: #1923069) - arm64: mm: correct the inside linear map range during hotplug check - virtiofs: Fail dax mount if device does not support it - ext4: shrink race window in ext4_should_retry_alloc() - ext4: fix bh ref count on error paths - fs: nfsd: fix kconfig dependency warning for NFSD_V4 - rpc: fix NULL dereference on kmalloc failure - iomap: Fix negative assignment to unsigned sis->pages in iomap_swapfile_activate - ASoC: rt1015: fix i2c communication error - ASoC: rt5640: Fix dac- and adc- vol-tlv values being off by a factor of 10 - ASoC: rt5651: Fix dac- and adc- vol-tlv values being off by a factor of 10 - ASoC: sgtl5000: set DAP_AVC_CTRL register to correct default value on probe - ASoC: es8316: Simplify adc_pga_gain_tlv table - ASoC: soc-core: Prevent warning if no DMI table is present - ASoC: cs42l42: Fix Bitclock polarity inversion - ASoC: cs42l42: Fix channel width support - ASoC: cs42l42: Fix mixer volume control - ASoC: cs42l42: Always wait at least 3ms after reset - NFSD: fix error handling in NFSv4.0 callbacks - ASoC: mediatek: mt8192: fix tdm out data is valid on rising edge - kernel: freezer should treat PF_IO_WORKER like PF_KTHREAD for freezing - vhost: Fix vhost_vq_reset() - io_uring: fix ->flags races by linked timeouts - io_uring: halt SQO submission on ctx exit - scsi: st: Fix a use after free in st_open() - scsi: qla2xxx: Fix broken #endif placement - staging: comedi: cb_pcidas: fix request_irq() warn - staging: comedi: cb_pcidas64: fix request_irq() warn - ASoC: rt5659: Update MCLK rate in set_sysclk() - ASoC: rt711: add snd_soc_component remove callback - thermal/core: Add NULL pointer check before using cooling device stats - locking/ww_mutex: Simplify use_ww_ctx & ww_ctx handling - locking/ww_mutex: Fix acquire/release imbalance in ww_acquire_init()/ww_acquire_fini() - nvmet-tcp: fix kmap leak when data digest in use - io_uring: imply MSG_NOSIGNAL for send[msg]()/recv[msg]() calls - Revert "PM: ACPI: reboot: Use S5 for reboot" - nouveau: Skip unvailable ttm page entries - static_call: Align static_call_is_init() patching condition - ext4: do not iput inode under running transaction in ext4_rename() - io_uring: call req_set_fail_links() on short send[msg]()/recv[msg]() with MSG_WAITALL - net: mvpp2: fix interrupt mask/unmask skip condition - mptcp: deliver ssk errors to msk - mptcp: fix poll after shutdown - mptcp: init mptcp request socket earlier - mptcp: add a missing retransmission timer scheduling - flow_dissector: fix TTL and TOS dissection on IPv4 fragments - mptcp: fix DATA_FIN processing for orphaned sockets - mptcp: provide subflow aware release function - can: dev: move driver related infrastructure into separate subdir - net: introduce CAN specific pointer in the struct net_device - mptcp: fix race in release_cb - net: bonding: fix error return code of bond_neigh_init() - mptcp: fix bit MPTCP_PUSH_PENDING tests - can: tcan4x5x: fix max register value - brcmfmac: clear EAP/association status bits on linkdown events - ath11k: add ieee80211_unregister_hw to avoid kernel crash caused by NULL pointer - netdevsim: dev: Initialize FIB module after debugfs - iwlwifi: pcie: don't disable interrupts for reg_lock - ath10k: hold RCU lock when calling ieee80211_find_sta_by_ifaddr() - net: ethernet: aquantia: Handle error cleanup of start on open - appletalk: Fix skb allocation size in loopback case - net: ipa: remove two unused register definitions - net: ipa: use a separate pointer for adjusted GSI memory - net: ipa: fix register write command validation - net: wan/lmc: unregister device when no matching device is found - net: 9p: advance iov on empty read - bpf: Remove MTU check in __bpf_skb_max_len - ACPI: tables: x86: Reserve memory occupied by ACPI tables - ACPI: processor: Fix CPU0 wakeup in acpi_idle_play_dead() - ACPI: scan: Fix _STA getting called on devices with unmet dependencies - ALSA: usb-audio: Apply sample rate quirk to Logitech Connect - ALSA: hda: Re-add dropped snd_poewr_change_state() calls - ALSA: hda: Add missing sanity checks in PM prepare/complete callbacks - ALSA: hda/realtek: call alc_update_headset_mode() in hp_automute_hook - xtensa: fix uaccess-related livelock in do_page_fault - xtensa: move coprocessor_flush to
[Bug 1920784] Re: qemu-system-ppc64le fails with kvm acceleration
** Changed in: ubuntu-power-systems Assignee: (unassigned) => Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920784 Title: qemu-system-ppc64le fails with kvm acceleration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1920784/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920784] Re: qemu-system-ppc64le fails with kvm acceleration
** No longer affects: qemu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920784 Title: qemu-system-ppc64le fails with kvm acceleration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1920784/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920784] Re: qemu-system-ppc64le fails with kvm acceleration
** Also affects: glibc (Ubuntu Hirsute) Importance: Undecided Status: Invalid ** Also affects: qemu (Ubuntu Hirsute) Importance: Undecided Status: Invalid ** Also affects: linux (Ubuntu Hirsute) Importance: Undecided Assignee: Frank Heimes (fheimes) Status: In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920784 Title: qemu-system-ppc64le fails with kvm acceleration To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1920784/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920784] Re: qemu-system-ppc64le fails with kvm acceleration
The fix was sent to the kernel teams mailing list: https://lists.ubuntu.com/archives/kernel-team/2021-March/thread.html#118449 ** Changed in: linux (Ubuntu) Status: Confirmed => In Progress ** Changed in: ubuntu-power-systems Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920784 Title: qemu-system-ppc64le fails with kvm acceleration To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1920784/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920784] Re: qemu-system-ppc64le fails with kvm acceleration
And gladly this was only added in >=5.9 and we have Groovy (5.8) and Hirsute (5.11) so only the Hirsute kernel is needed to adapt, but further backports are not needed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920784 Title: qemu-system-ppc64le fails with kvm acceleration To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1920784/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920784] Re: qemu-system-ppc64le fails with kvm acceleration
@Sadoon - yes, that is the same fix that Laurent pointed to a few hours before. @Frank - the kernel I had before was 5.11.0-11-generic (failing). I've tested "5.11.0-13-generic #14~lp1920784" from your PPA and can confirm that this fixes the issue. Thanks Laurent for identifying the fix and thanks Frank for the kernel. I'll mark bug tasks accordingly and @Frank you'll let me know if there is anything else you need to drive this to completion. ** Changed in: qemu Status: New => Invalid ** Changed in: glibc (Ubuntu) Status: New => Invalid ** Changed in: qemu (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920784 Title: qemu-system-ppc64le fails with kvm acceleration To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1920784/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920784] Re: qemu-system-ppc64le fails with kvm acceleration
The guys on the Fedora side seem to have found the patch to fix this: https://bugzilla.redhat.com/show_bug.cgi?id=1941652#c6 Apparently it will go upstream in Linux 5.11, but earlier versions also need the fix, specifically 5.9 and 5.10 Thank you! ** Bug watch added: Red Hat Bugzilla #1941652 https://bugzilla.redhat.com/show_bug.cgi?id=1941652 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920784 Title: qemu-system-ppc64le fails with kvm acceleration To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1920784/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920784] Re: qemu-system-ppc64le fails with kvm acceleration
Thx Laurent, I took the hirsute master-next source and cherry-picked the patch and it applied cleanly. Now I kicked off a kernel build of this patched kernel in the following PPA: https://launchpad.net/~fheimes/+archive/ubuntu/lp1920784 (however, the builds will take some time to complete) If it can be proofed that this patched kernel fixes the problem, I can go ahead and work on a patch submission for hirsute/21.04. (kernel freeze is April 8th) ** Changed in: ubuntu-power-systems Status: New => Confirmed ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Frank Heimes (fheimes) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920784 Title: qemu-system-ppc64le fails with kvm acceleration To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1920784/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920784] Re: qemu-system-ppc64le fails with kvm acceleration
** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920784 Title: qemu-system-ppc64le fails with kvm acceleration To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1920784/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920784] Re: qemu-system-ppc64le fails with kvm acceleration
You need a kernel with a the following fix for POWER9: commit 25edcc50d76c834479d11fcc7de46f3da4d95121 Author: Fabiano Rosas Date: Thu Feb 4 17:05:17 2021 -0300 KVM: PPC: Book3S HV: Save and restore FSCR in the P9 path The Facility Status and Control Register is a privileged SPR that defines the availability of some features in problem state. Since it can be written by the guest, we must restore it to the previous host value after guest exit. This restoration is currently done by taking the value from current->thread.fscr, which in the P9 path is not enough anymore because the guest could context switch the QEMU thread, causing the guest-current value to be saved into the thread struct. The above situation manifested when running a QEMU linked against a libc with System Call Vectored support, which causes scv instructions to be run by QEMU early during the guest boot (during SLOF), at which point the FSCR is 0 due to guest entry. After a few scv calls (1 to a couple hundred), the context switching happens and the QEMU thread runs with the guest value, resulting in a Facility Unavailable interrupt. This patch saves and restores the host value of FSCR in the inner guest entry loop in a way independent of current->thread.fscr. The old way of doing it is still kept in place because it works for the old entry path. Signed-off-by: Fabiano Rosas Signed-off-by: Paul Mackerras -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920784 Title: qemu-system-ppc64le fails with kvm acceleration To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1920784/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920784] Re: qemu-system-ppc64le fails with kvm acceleration
I might be spoiled by the s390x-POP style to define instructions, but in the following doc about the PowerISA unfortunately there is no list of reasons-for-SIGILL. Therefore I'm out of options on this waiting for someone - most likely IBM - to chime in. https://wiki.raptorcs.com/w/images/f/f5/PowerISA_public.v3.1.pdf -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920784 Title: qemu-system-ppc64le fails with kvm acceleration To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1920784/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920784] Re: qemu-system-ppc64le fails with kvm acceleration
As my other repro-code didn't trigger the issue I looked at qemu again and found that before the failing ioctl->scv call there are plenty other even some very similar (same?) calls that work just fine. I wonder if on guest setup qemu (or e.g. the rom we load) might set some arch-bits or such which then breaks the next "scv 0" call. I attached the full ioctl log here. ** Attachment added: "ioctl log of qemu until the crash happens" https://bugs.launchpad.net/qemu/+bug/1920784/+attachment/5480011/+files/qemu-ioctls-util-crash.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920784 Title: qemu-system-ppc64le fails with kvm acceleration To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1920784/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920784] Re: qemu-system-ppc64le fails with kvm acceleration
** Also affects: ubuntu-power-systems Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920784 Title: qemu-system-ppc64le fails with kvm acceleration To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1920784/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920784] Re: qemu-system-ppc64le fails with kvm acceleration
[10] outlined to use PPC_FEATURE2_SCV but [4] does just that.
In addition [6] added power9 machine settings as only on this ISA it
is available - like:
+ .machine "push"
+ .machine "power9"
scv 0
+ .machine "pop"
Maybe there is some generated "scv 0" left that needs the same [6]
treatment?
OTOH In a normal test program I can run "scv 0" just fine.
But not other scv levels (expected).
# cat test.c
#include
int main() {
printf("Hello scv 0\n");
__asm__(
"scv 0\n\t"
);
printf("survived\n");
__asm__(
"scv 1\n\t"
);
printf("survived level 1\n");
return 0;
}
# gcc -Wall -o test test.c
./test
Hello scv 0
survived
Illegal instruction (core dumped)
IIRC .machine is only a psedo-op for the assembler.
So it is correct that I can't see it in the live disassembly of gdb.
The failing "svc 0" from glibcs __GI___ioctl is
0x766c49a0 <+320>: 01 00 00 44 scv 0
And in my test program it is
0x00010848 <+44>:01 00 00 44 scv 0
Hmm, this is the same opcode but fails in just one of the cases.
This might need someone being more an ppc64/glibc expert than me :-/
@Frank - could you modify this bug to become mirrored to IBM for their
arch-expertise please?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1920784
Title:
qemu-system-ppc64le fails with kvm acceleration
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1920784/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920784] Re: qemu-system-ppc64le fails with kvm acceleration
qemu calls this ioctl on ppc64 as:
sysdeps/unix/sysv/linux/powerpc/ioctl.c
result = INLINE_SYSCALL (ioctl, 3, fd, request, arg);
The mapping of macros in sysdeps/unix/sysv/linux/powerpc/sysdep.h seems to be:
INTERNAL_SYSCALL -> INTERNAL_SYSCALL_NCS -> TRY_SYSCALL_SCV -> SYSCALL_SCV
76 #define SYSCALL_SCV(nr) \
77 ({\
78 __asm__ __volatile__\
79 (".machine \"push\"\n\t" \
80".machine \"power9\"\n\t"\
81"scv 0\n\t" \
82".machine \"pop\"\n\t" \
83"0:" \
84: "=&r" (r0),\
85 "=&r" (r3), "=&r" (r4), "=&r" (r5),\
86 "=&r" (r6), "=&r" (r7), "=&r" (r8) \
87: ASM_INPUT_##nr \
88: "r9", "r10", "r11", "r12", \
89 "lr", "ctr", "memory");\
90 r3; \
91 })
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1920784
Title:
qemu-system-ppc64le fails with kvm acceleration
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1920784/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920784] Re: qemu-system-ppc64le fails with kvm acceleration
Hi Sadoon, thanks for the report! There isn't much to find about this issue yet. One automatic syscaller crash report [1]. On the emulation side there is [2][3]. On the glibc side we have [4][5] adding the use of it with [6] being a fix. All those seem to be in glibc 2.33 - so I'd expect with [6] it should only be issued on power9 which in turn should HW-support the instruction. I was trying to recreate this on power8 and power9 machines. As expected on power8 just nothing happens (the instruction isn't used due to [6]). TBH I first wondered if these Sforza chips [7][8][9] you mentioned are fully identical to a classic IBM p9 box - but I was indeed able to reproduce the issue just fine on an IBM-sold P9 dmesg: [ 1516.438442] Facility 'SCV' unavailable (12), exception at 0x76c9f84c49a0, MSR=9280f033 [ 1516.438472] qemu-system-ppc[42884]: illegal instruction (4) at 76c9f84c49a0 nip 76c9f84c49a0 lr 1f12839d9f0 code 1 in libc-2.33.so[76c9f838+22] [ 1516.438489] qemu-system-ppc[42884]: code: e8010010 7c0803a6 4e800020 6042 7ca42b78 4bffed65 6000 38210020 [ 1516.438493] qemu-system-ppc[42884]: code: e8010010 7c0803a6 4e800020 6042 <4401> 4bb8 6000 6042 The chip I used for this test is: Model: 2.2 (pvr 004e 1202) Model name: POWER9, altivec supported The syscall this crashes in belongs to the ioctl (gdb) bt #0 __GI___ioctl (fd=, request=536915584) at ../sysdeps/unix/sysv/linux/powerpc/ioctl.c:56 #1 0x0cb63ef7d9f0 in kvm_vcpu_ioctl (cpu=cpu@entry=0x7d0f48010010, type=type@entry=536915584) at ../../accel/kvm/kvm-all.c:2654 #2 0x0cb63ef7dbdc in kvm_cpu_exec (cpu=0x7d0f48010010) at ../../accel/kvm/kvm-all.c:2491 #3 0x0cb63ee78344 in kvm_vcpu_thread_fn (arg=0x7d0f48010010) at ../../accel/kvm/kvm-cpus.c:49 #4 0x0cb63f1d14bc in qemu_thread_start (args=) at ../../util/qemu-thread-posix.c:521 #5 0x7d0f4ac69114 in start_thread (arg=0x7d0f23dfe720) at pthread_create.c:473 #6 0x7d0f4ab755c0 in clone () at ../sysdeps/unix/sysv/linux/powerpc/powerpc64/clone.S:103 And jumping into the code of the __GI___ioctl we can clearly see the scv instruction is indeed there in the executed code path: 0x766c4984 <__GI___ioctl+292> bl 0x766c36e8 <__GI___tcgetattr+8> 0x766c4988 <__GI___ioctl+296> nop 0x766c498c <__GI___ioctl+300> addir1,r1,32 0x766c4990 <__GI___ioctl+304> ld r0,16(r1) 0x766c4994 <__GI___ioctl+308> mtlrr0 0x766c4998 <__GI___ioctl+312> blr 0x766c499c <__GI___ioctl+316> ori r2,r2,0 >0x766c49a0 <__GI___ioctl+320> scv 0 [1]: https://webcache.googleusercontent.com/search?q=cache:uS0jhPekyqMJ:https://syzkaller-ppc64.appspot.com/text%3Ftag%3DCrashReport%26x%3D17d9988300+&cd=2&hl=de&ct=clnk&gl=uk [2]: https://git.qemu.org/?p=qemu.git;a=commit;h=3c89b8d6ac5b8728cd7620f9885bd953edd18a11 [3]: https://lists.gnu.org/archive/html/qemu-devel/2021-03/msg05425.html [4]: https://sourceware.org/git/?p=glibc.git;a=commit;h=68ab82f56690ada86ac1e0c46bad06ba189a10ef [5]: https://sourceware.org/git/?p=glibc.git;a=commit;h=41f013cef24884604c303435dd1915be2ea5c0e0 [6]: https://sourceware.org/git/?p=glibc.git;a=commit;h=527c89cd32f8522859f58343be3d3dc8f754b783 [7]: https://wiki.raptorcs.com/wiki/Sforza [8]: https://wiki.raptorcs.com/wiki/Talos_II [9]: https://wiki.raptorcs.com/wiki/POWER9 [10]: https://lwn.net/Articles/822867/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920784 Title: qemu-system-ppc64le fails with kvm acceleration To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1920784/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920784] Re: qemu-system-ppc64le fails with kvm acceleration
Since this seems to be broken on all Distributions as soon as the triggering combination of kernel/glibc is present I think we'd want to open that up to upstream qemu for a wider discussion and to also hit the ppc64 architecture experts. Furthermore I'm not entirely sure if this needs to be fixed in qemu, it might instead be the case that instead a fix is needed in glibc. Therefore I'm adding a qemu (upstream) bug task for now to have the bug reported there as well (might be worth for awareness anyway) - but chances are that after some debugging it will turn out to become a glibc issue instead. If only I could break this test out of kvm ioctl into something simpler, then we could then properly file against glibc ** Also affects: glibc (Ubuntu) Importance: Undecided Status: New ** Also affects: qemu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920784 Title: qemu-system-ppc64le fails with kvm acceleration To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1920784/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920784] Re: qemu-system-ppc64le fails with kvm acceleration
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: qemu (Ubuntu) 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/1920784 Title: qemu-system-ppc64le fails with kvm acceleration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1920784/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
