Backporting to the Xenial (Ubntu 16.04) kernel isn't feasible. 16.04
users are requested to use the hwe-z kernel as noted in the following
Wiki page :
https://wiki.ubuntu.com/HardwareSupport/Machines/Servers/Cavium/ThunderXCRB1S
** Changed in: linux (Ubuntu Xenial)
Status: Confirmed => Fix
This bug was fixed in the package linux - 4.10.0-33.37
---
linux (4.10.0-33.37) zesty; urgency=low
* linux: 4.10.0-33.37 -proposed tracker (LP: #1709303)
* CVE-2017-1000112
- Revert "udp: consistently apply ufo or fragmentation"
- udp: consistently apply ufo or fragmentat
I've been able to backport the fixes back as far as 4.7. 4.7 was when
the new vgic reimplementation was merged, and the upstream patchset
would need significant surgery to apply. To fix Ubuntu 16.04's GA kernel
(4.4-based), we'd probably need to develop a new (hopefully simpler)
solution. In the me
I've ran the vm-start-stop test on a ThunderX system for an hour on the
proposed kernel w/o any issues.
** Tags removed: patch verification-needed-zesty
** Tags added: verification-done-zesty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
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-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag 'verificati
This bug was fixed in the package linux - 4.11.0-13.19
---
linux (4.11.0-13.19) artful; urgency=low
* CVE-2017-7533
- dentry name snapshots
linux (4.11.0-12.18) artful; urgency=low
* linux: 4.11.0-12.18 -proposed tracker (LP: #1707635)
- no change rebuild to pick up the
** Changed in: linux (Ubuntu Zesty)
Status: In Progress => 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/1673564
Title:
ThunderX: soft lockup on 4.8+ kernels when running qemu-e
** Description changed:
[Impact]
VMs can cause interrupts to be disabled on the host CPU, resulting in hangs.
[Test Case]
- See Comment #1.
+ Download the attached vm-start-stop.tar.gz and unpack it. Run the start.sh
script within. This will start 30 parallel loops where a VM is defined,
** Attachment added: "vm-start-stop.tar.gz"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1673564/+attachment/4926651/+files/vm-start-stop.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
** Changed in: linux (Ubuntu)
Status: Confirmed => 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/1673564
Title:
ThunderX: soft lockup on 4.8+ kernels when running qemu-efi with
@dannf: while i used ppa:yarmouth-team/thunderx kernel, it still causes the
server hanging.
I'm using Openstack on arm64 just like what ciprian-barbu did.
R150-T60
BIOS version T12
Ubuntu 16.04.2
tested kernel: offical-4.4, thunderx-4.8
program: openstack mitaka, qemu command is same as ciprian-b
Note that, while this symptom is seemingly only reproducible with >=
4.10 (hwe-y), there is another symptom of this problem that is
reproducible with 4.4 (hwe-x). That symptom is that VMs will hang during
teardown - easily reproducible using a parallel VM start/stop test. I'll
therefore mark this a
Marc is working on a fix here:
https://git.kernel.org/pub/scm/linux/kernel/git/maz/arm-platforms.git/log/?h=kvm-arm64/gicv3-cpuif-mediated-access
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1673564
Once the build is complete, you'll be able to install it with:
sudo apt-add-repository ppa:yarmouth-team/thunderx
sudo apt update
sudo apt install
linux-image-extra-4.8.0-49-generic=4.8.0-49.52~16.04.1+lp1673564.1
The PPA web page is at:
https://launchpad.net/~yarmouth-team/+archive/ubuntu/thu
I've uploaded a test kernel w/ a potential workaround developed by Cavium to:
ppa:yarmouth-team/thunderx
The build should complete in ~4 hours. Mind giving that a test?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.la
Thanks, the patch is working well in our internal testing. I believe
this rules out edk2, so I'll drop that task from this bug.
** No longer affects: edk2 (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
The Experimental patch in comment #9, although it seems to prevent the
hang under some workloads, puts the code in the wrong function. We
really think it should be at the end of __vgic_v3_save_state()
We will have a revised patch after some further testing.
--
You received this bug notification
The attachment "Experimental workaround" seems to be a patch. If it
isn't, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are a member of the ~ubuntu-reviewers,
unsubscribe the team.
[This is an automated message performed by a Launchpad user owned by
~bria
We are testing this patch, it is not a definitive solution at this
point, but we would like to get wider testing on it to see if it helps
for this bug.
** Patch added: "Experimental workaround"
https://bugs.launchpad.net/ubuntu/+source/edk2/+bug/1673564/+attachment/4861520/+files/kvm-hang.patc
I bisected this down to the upstream commit below. Now, that's not to
say that this commit is necessarily bad - it may just make an existing
problem more reproducible.
commit 7235acdb1144460d9f520f0d931f3cbb79eb244c
Author: Jason Wang
Date: Mon Apr 25 22:14:32 2016 -0400
vhost: simplify wo
Hi, Dann,
Thanks for looking into this!
One more thing: we blacklisted the module "vhost_net", and that bypasses the
issue.
I know it's not the right direction for finding a fix, but maybe it helps with
the debug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, wh
Thanks for the steps. As you noted, I can reproduce on xenial w/ the 4.8
hwe kernel, but not with the GA 4.4. I'm marking the kernel packages as
affected because the host kernel shouldn't hang, even if the guest does
something bad (e.g. if edk2 is buggy).
--
You received this bug notification bec
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1673564
Title:
The bug shows on the CRB boards as well
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1673564
Title:
ThunderX: soft lockup on 4.8+ kernels when running qemu-efi with
vhost=on
To manage notificati
Just an additional comment, running qemu-kvm with a 3part image (kernel,
initramfs and disk) does not yield a crash on 4.8 kernel, even when
enabling vhost. Similarly, running a guest with AAVMF and no vhost
behaves ok, it's the combination of the two that didn't work no matter
what guest, FW or AA
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: edk2 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1673564
Title:
Thund
** Also affects: edk2 (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: qemu (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1673564
Title:
ThunderX: soft lockup on
Launch script showing how to start qemu with AAVMF and vhost on. It
requires an AAVMF vars file, which can be a simple zero filled 64M data
file.
** Attachment added: "launch.sh"
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1673564/+attachment/4839059/+files/launch.sh
--
You received
Serial console log, including debug messages from the Firmware and
kernel errors. Could not get dmesg output, I might try again.
** Attachment added: "console.log"
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1673564/+attachment/4839060/+files/console.log
--
You received this bug noti
29 matches
Mail list logo
