** Tags added: cscc
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1798110
Title:
xenial: virtio-scsi: CPU soft lockup due to loop in
virtscsi_target_destroy()
To manage notifications about this
This bug was fixed in the package linux - 4.4.0-139.165
---
linux (4.4.0-139.165) xenial; urgency=medium
* linux: 4.4.0-139.165 -proposed tracker (LP: #1799401)
* Kernel panic after the ubuntu_nbd_smoke_test on Xenial kernel (LP: #1793464)
- nbd: Remove signal usage
-
Verification successful with the kernel in xenial-proposed.
Updating verification tags.
Details
===
Guest:
---
root@mfo-sf194614:~# apt-cache madison linux-image-4.4.0-139-generic
linux-image-4.4.0-139-generic | 4.4.0-139.165 |
http://archive.ubuntu.com/ubuntu/ xenial-proposed/main amd64
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag
** Changed in: linux (Ubuntu Xenial)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1798110
Title:
xenial: virtio-scsi: CPU soft lockup due to loop in
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: Confirmed => Triaged
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Xenial)
Status: New => Triaged
** Changed
Patches posted to kernel-team mailing list [1].
[1] https://lists.ubuntu.com/archives/kernel-team/2018-October/096072.html
[SRU Xenial][PATCH 0/2] Improve our SAUCE for virtio-scsi reqs counter (fix
CPU soft lockup)
** Description changed:
[Impact]
- * Detaching virtio-scsi disk in
Organic Testcase:
It usually reproduces the problem in the 1st or 2nd iteration.
With the fix the problem did not reproduce in 35 iterations.
** Description changed:
- (I'll add the SRU template + testing steps and post to ML shortly.)
+ [Impact]
+
+ * Detaching virtio-scsi disk in Xenial
Organic Testcase
set -x
instancename=USER-trusty
firstdevice=sdb
seconddevice=sdc
diskname=USER-disk-1
gcloud compute --project "PROJECT" ssh --zone "ZONE" "$instancename" --command
'(tar -C /var/issue/first -cf - .) | (tar -C /var/issue/second -xpf -)'
gcloud compute --project
Synthetic Test Case
===
Create a Xenial KVM guest
---
mfo@rotom:~$ uvt-simplestreams-libvirt sync release=xenial arch=amd64
mfo@rotom:~$ uvt-kvm create --mem 4096 --cpu 2 --disk 16 mfo-sf194614
release=xenial arch=amd64
Modify the virsh XML to add a virtio-scsi controller +
Problem Analysis
The dmesg log 'crash/201809061748/dmesg.201809061748' shows the CPU soft lockup
occurs 25 seconds after the 'sdb' virtio-scsi drive is removed.
This seems to indicate the events are related (there's usually an extra 2s-3s
between an event and the report of the
11 matches
Mail list logo
