Fixer Issue 019f9eb7-d046-7732-ad3b-eaab1885c0e4

Runaway CPU investigation for qemu-s390x: unknown userspace loop at unresolved offset in qemu-s390x

qemu-s390x is stuck in a likely unclassified userspace loop: 3.25% of sampled CPU passed through unresolved offset, with repeated thread backtraces show 1 thread(s) around 0x00007fd4b10cf98d in ?? () and 1 thread(s) around 0x00007fd4b13582c9 in ?? ().

highpackage: qemu-usersource: qemuscore: 106reports: 1

Technical snapshot

This is the clearest retained userspace thread cluster Fixer captured while the process was spinning.

Representative thread backtrace

Command: /usr/bin/qemu-s390x /bin/sh /bin/sh -c echo $CI_SCRIPT | base64 -d | /bin/sh -e
Why Fixer classified it this way: The process is demonstrably CPU-hot, but the current syscall and symbol sample does not point to a single dominant loop family yet.
Thread summary: thread backtraces show 1 thread(s) around 0x00007fd4b10cf98d in ?? () and 1 thread(s) around 0x00007fd4b13582c9 in ?? ()
Contention signals: gdb-stderr: gdb: warning: Couldn't determine a path for the index cache directory. warning: "target:<path>": could not open as an executable file: Input<path> error. warning: `target:<path>': can't open to read symbols: Input<path> error. warning: Could not load vsyscall page because no executable was specified warning: Target and debugger are in different PID namespaces; thread lists and other data are likely unreliable. Connect to gdbserver inside the container.
Repeated loop: futex -> wait4
Top syscalls: futex x1, wait4 x1
Package: qemu-user 1:11.1.2+ds-3
Kernel: 7.1.8+deb14.1-amd64
Distribution: debian

0x00007fd4b10cf98d in ?? ()
0x00007ffc42b0f3c0 in ?? ()
0x00007fd4b1138065 in ?? ()
0x00007fd4b1b55390 in ?? ()
0x0000000000000001 in ?? ()
0x00007fd4b1b54f30 in ?? ()
0x0000555500000040 in ?? ()

Possible duplicates

These are suggestions based on sanitized trigram similarity plus structured fields like package, subsystem, classification, and wait site. They are not auto-merged.

Runaway CPU investigation for qemu-arm: unknown userspace loop at unresolved offset in qemu-arm

possible duplicate

qemu-arm is stuck in a likely unclassified userspace loop: 2.78% of sampled CPU passed through unresolved offset, with repeated thread backtraces show 1 thread(s) around 0x00007f5ee08d430d in ?? () and 1 thread(s) around 0x00007f5ee0be73c9 in ?? ().

highpackage: qemu-usersource: qemuscore: 106reports: 1similarity: 99%

Why this looks related: same classification, same package, same source package, same subsystem, same wait site

Last seen: 2026-10-21 04:19 UTC. Public page: /issues/019f9e15-6812-7222-920d-b38631b98fd2. Public JSON: /v1/issues/019f9e15-6812-7222-920d-b38631b98fd2

Runaway CPU investigation for ollama: unknown userspace loop at unresolved offset in ollama

possible duplicate

ollama is stuck in a likely unclassified userspace loop: 12.27% of sampled CPU passed through unresolved offset, with repeated thread backtraces show 1 thread(s) around 0x000055c5c39ed143 in ?? () and 1 thread(s) around 0x000055c5c39ed143 in ?? ().

highscore: 106reports: 3successful triagesimilarity: 88%

Why this looks related: same classification, same subsystem