qemu-nbd on ARM64 deadlock? Stuck in rt_sigtimedwait([BUS ALRM IO], ..) and futex(0x7f749ec230, FUTEX_WAIT, ...)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Expired
|
Medium
|
Unassigned | ||
linux-meta-lts-vivid (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
qemu (Ubuntu) |
Expired
|
Medium
|
Unassigned |
Bug Description
Hi,
We're seeing this often on our HP Moonshot ARM64 nova-compute nodes where qemu-nbd processes would lock up. At the same time, there's also a bunch of kernel spew as follows:
| [605282.018238] block nbd3: Attempted send on closed socket
| [605282.018242] block nbd3: Attempted send on closed socket
| [605282.018245] block nbd3: Attempted send on closed socket
| [605282.018249] block nbd3: Attempted send on closed socket
swirlix01:
| hloeung@
| Linux swirlix01 3.19.0-30-generic #34~14.04.1-Ubuntu SMP Fri Oct 2 22:15:46 UTC 2015 aarch64 aarch64 aarch64 GNU/Linux
| hloeung@
| 27782 ? Ssl 0:00 /usr/bin/qemu-nbd -c /dev/nbd10 /var/lib/
| hloeung@
| [<ffffffc000087
| [<ffffffc000125
| [<ffffffc000126
| [<ffffffc000128
| [<ffffffc000128
| [<ffffffc000086
| [<fffffffffffff
swirlix08:
| hloeung@
| Linux swirlix08 3.19.0-31-generic #36~14.04.1-Ubuntu SMP Thu Oct 8 10:50:10 UTC 2015 aarch64 aarch64 aarch64 GNU/Linux
| hloeung@
| 31976 ? Ssl 0:00 /usr/bin/qemu-nbd -c /dev/nbd6 /var/lib/
| hloeung@
| [<ffffffc000087
| [<ffffffc000125
| [<ffffffc000126
| [<ffffffc000128
| [<ffffffc000128
| [<ffffffc000086
| [<fffffffffffff
swirlix11:
| hloeung@
| Linux swirlix11 3.19.0-31-generic #36~14.04.1-Ubuntu SMP Thu Oct 8 10:50:10 UTC 2015 aarch64 aarch64 aarch64 GNU/Linux
| hloeung@
| 18149 ? Ssl 0:00 /usr/bin/qemu-nbd -c /dev/nbd3 /var/lib/
| hloeung@
| hloeung@
| [<ffffffc000087
| [<ffffffc000125
| [<ffffffc000126
| [<ffffffc000128
| [<ffffffc000128
| [<ffffffc000086
| [<fffffffffffff
| hloeung@
| Process 18149 attached with 3 threads
| [pid 18150] rt_sigtimedwait
| [pid 18149] futex(0x7f749ec230, FUTEX_WAIT, 18152, NULL
| ... (hangs here) ...
We're using the QEMU package backported from Vivid as per LP:1457639
| hloeung@
| qemu-utils:
| Installed: 1:2.2+dfsg-
| Candidate: 1:2.2+dfsg-
| Version table:
| *** 1:2.2+dfsg-
| 500 http://
I'm also not sure if this is related to LP:1505564, which is for amd64/x86_64.
---
AlsaDevices:
total 0
crw-rw---- 1 root audio 116, 1 Oct 25 17:42 seq
crw-rw---- 1 root audio 116, 33 Oct 25 17:42 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.14.1-0ubuntu3.18
Architecture: arm64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CRDA: Error: [Errno 2] No such file or directory
DistroRelease: Ubuntu 14.04
Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99
Package: qemu (not installed)
PciMultimedia:
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_GB
SHELL=/bin/bash
ProcFB:
ProcKernelCmdLine: console=
ProcVersionSign
RfKill: Error: [Errno 2] No such file or directory
Tags: trusty uec-images trusty uec-images
Uname: Linux 3.19.0-31-generic aarch64
UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm
_MarkForUpload: True
description: | updated |
Changed in qemu (Ubuntu): | |
status: | Confirmed → Incomplete |
importance: | Undecided → Medium |
Changed in linux-meta-lts-vivid (Ubuntu): | |
status: | Confirmed → Invalid |
This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
apport-collect 1512185
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.