We updated our test instances to run on the latest hardware made
available in AWS, I have not seen this reoccur in the xenial testing.
closing bug.
** Changed in: ubuntu-kernel-tests
Status: In Progress => Invalid
** Changed in: linux-aws (Ubuntu)
Status: In Progress => Invalid
It might be fixed if AWS runs a Xen hypervisor which has the following
patch included (this is from the development tree of upstream Xen, so
will be part of Xen-4.12).
commit be07023be115c94b7fbb51d2ef6f421ddd680de8
Author: Roger Pau Monné
Date: Tue Jul 24 15:54:18 2018 +0200
x86/vhpet:
Been sorting through many of the ubuntu-kernel-tests bugs.
This is one of the few that actually is being worked.
Stefan, any update on this? Should this be/ Has it been fixed? I can
revisit once i finish cleaning up the list
** Changed in: ubuntu-kernel-tests
Status: New => In Progress
** Also affects: ubuntu-kernel-tests
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1741409
Title:
stress smoke test hang with dev test
Right now I do not think there is much choice to fix this (other than
not touch /dev/hpet on AWS). The linux kernel deliberately wants to set
a level triggered interrupt. The xen hypervisor has no support for that
(there might be some addition done but certainly not in any released
version of
** Changed in: linux-aws (Ubuntu)
Assignee: Colin Ian King (colin-king) => Stefan Bader (smb)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1741409
Title:
stress smoke test
Darn, ok I take everything back. Somehow the compiled reproducer was
mangled in such a way it did maybe no longer do what it was intended to
do. Anyhow, with freshly generated reproducers, even Xen 4.9 has the
crash. :(
--
You received this bug notification because you are a member of Kernel
I was booting the same Xenial based HVM guest on the same host (but this
time running Bionic / Xen 4.9). This combination does not crash the
domain when opening HPET. Though the check and code that would do it is
still there. I also found a bug report against xenserver which I believe
is based on
I was able to observe the crash on a Ubuntu Xenial Xen host which
produced the following text on the host console:
(XEN) domain_crash called from hpet.c:387
(XEN) Domain 2 (vcpu#1) crashed on cpu#4:
(XEN) [ Xen-4.6.5 x86_64 debug=n Not tainted ]
(XEN) CPU:4
(XEN) RIP:0010:[]
demsg of guest:
[0.00] Linux version 4.16.0-rc2+ (cking@gloin) (gcc version 7.3.0
(Ubuntu 7.3.0-3ubuntu1)) #7 SMP Tue Feb 20 14:27:20 UTC 2018
[0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-4.16.0-rc2+
root=UUID=b6adc449-5e3d-4331-ba6b-6e99a75fa48e ro console=tty1 console=ttyS0
I can reproduce this with 4.16-rc2, I've debugged this down to:
drivers/char/hpet.c, hpet_timer_set_irq():
if (irq < HPET_MAX_IRQ) {
spin_lock_irq(_lock);
v = readl(>hpet_config);
v |= irq << Tn_INT_ROUTE_CNF_SHIFT;
Tested with 4.4.0-109 lowlatency kernel, this dev test can pass now.
I will leave this bug open as discussed on the IRC.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1741409
Title:
Do you mind re-running the test to see if we get passed this stress test
now?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1741409
Title:
stress smoke test hang with dev test on
..and way back to v4.0
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1741409
Title:
stress smoke test hang with dev test on AWS Xenial kernel
Status in linux-aws package in
issue occurs with v4.15-rc7 upstream kernel too
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1741409
Title:
stress smoke test hang with dev test on AWS Xenial kernel
Status in
4.4.0-73 has the same issue, so it's not an aws specific kernel issue
per se.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1741409
Title:
stress smoke test hang with dev test on
This is locking up on opening a specific device. It is not a race
condition as I originally suspected, but a lockup on a simple read open
of a device on just AWS.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
** Changed in: linux-aws (Ubuntu)
Importance: Undecided => High
** Changed in: linux-aws (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
Manually tested with older kernel (4.4.0-1043-aws), this issue still can
be reproduced.
The node will get rebooted when bumping into this test.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
19 matches
Mail list logo
