[Kernel-packages] [Bug 1512185] Re: qemu-nbd on ARM64 deadlock? Stuck in rt_sigtimedwait([BUS ALRM IO], ..) and futex(0x7f749ec230, FUTEX_WAIT, ...)

[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1512185] Re: qemu-nbd on ARM64 deadlock? Stuck in rt_sigtimedwait([BUS ALRM IO], ..) and futex(0x7f749ec230, FUTEX_WAIT, ...)

[Expired for qemu (Ubuntu) because there has been no activity for 60 days.] ** Changed in: qemu (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1512185] Re: qemu-nbd on ARM64 deadlock? Stuck in rt_sigtimedwait([BUS ALRM IO], ..) and futex(0x7f749ec230, FUTEX_WAIT, ...)

** Changed in: qemu (Ubuntu) Status: Confirmed => Incomplete ** Changed in: qemu (Ubuntu) Importance: Undecided => Medium ** Changed in: linux-meta-lts-vivid (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel

[Kernel-packages] [Bug 1512185] Re: qemu-nbd on ARM64 deadlock? Stuck in rt_sigtimedwait([BUS ALRM IO], ..) and futex(0x7f749ec230, FUTEX_WAIT, ...)

Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-meta-lts-vivid (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1512185] Re: qemu-nbd on ARM64 deadlock? Stuck in rt_sigtimedwait([BUS ALRM IO], ..) and futex(0x7f749ec230, FUTEX_WAIT, ...)

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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1512185

[Kernel-packages] [Bug 1512185] Re: qemu-nbd on ARM64 deadlock? Stuck in rt_sigtimedwait([BUS ALRM IO], ..) and futex(0x7f749ec230, FUTEX_WAIT, ...)

Hi Joseph, Happy to test upstream kernels, but this setup requires a 64-bit native arm64/aarch64 kernel, which I can't see at the link provided - only 32-bit armhf kernels. Currently we're running the kernel from the linux-generic-lts-wily package: Linux swirlix18 4.2.0-16-generic

[Kernel-packages] [Bug 1512185] Re: qemu-nbd on ARM64 deadlock? Stuck in rt_sigtimedwait([BUS ALRM IO], ..) and futex(0x7f749ec230, FUTEX_WAIT, ...)

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.3

[Kernel-packages] [Bug 1512185] Re: qemu-nbd on ARM64 deadlock? Stuck in rt_sigtimedwait([BUS ALRM IO], ..) and futex(0x7f749ec230, FUTEX_WAIT, ...)

Kernel OOPS on one of the mcdivitts: | [544599.231964] block nbd0: Attempted send on closed socket | [544599.231968] block nbd0: Attempted send on closed socket | [544599.231972] block nbd0: Attempted send on closed socket | [544599.231975] block nbd0: Attempted send on closed socket |

[Kernel-packages] [Bug 1512185] Re: qemu-nbd on ARM64 deadlock? Stuck in rt_sigtimedwait([BUS ALRM IO], ..) and futex(0x7f749ec230, FUTEX_WAIT, ...)

apport information ** Also affects: linux-meta-lts-vivid (Ubuntu) Importance: Undecided Status: New ** Tags added: apport-collected trusty uec-images ** Description changed: Hi, We're seeing this often on our HP Moonshot ARM64 nova-compute nodes where qemu-nbd processes