From the original report, the issue happened since 3.17, so close it on trysty because we can't reproduce it on trusty too.
I've seen this with mainline since somewhere in v3.17 and on several hardware boards stress testing KVM by running workloads in VMs.
From the original report, the issue happened since 3.17, so close it on trysty because we can't reproduce it
on trusty too.
I've seen this with mainline since somewhere in v3.17 and on several
hardware boards stress testing KVM by running workloads in VMs.