This change was made by a bot.
** Changed in: linux (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/1750787
Title:
enosys test in ubuntu_stress_s
This test has passed on node rumford with 4.13.0-36.
Let's see if it can pass on the next cycle.
--
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/1741437
Title:
SRU testing node rumford te
Public bug reported:
The ubuntu_stress_smoke test will fail with enosys on node "gonzo" with
Artful kernel (only on this node)
This can be reproduced in 4.13.0-32 and 4.13.0-36
enosys STARTING
enosys RETURNED 2
enosys FAILED
stress-ng: debug: [22679] 6 processors online, 6 processors configured
Public bug reported:
Uploaded the Debian packages onto the Canonical FTP Server for 8.0.5.10
foreman@cit7r02:~/sandbox/binary$ ftp archive.admin.canonical.com
Connected to archive.admin.canonical.com.
220 youngberry.canonical.com FTP server (Poppy Upload Server) ready.
Name (archive.admin.canonica
Public bug reported:
We are seeing kernel BUGs when running the stress-ng enosys stresser on
released trusty kernels.
** Affects: linux (Ubuntu)
Importance: High
Assignee: Andy Whitcroft (apw)
Status: In Progress
** Changed in: linux (Ubuntu)
Status: New => In Progress
You have been subscribed to a public bug:
Uploaded the Debian packages onto the Canonical FTP Server for 8.0.5.10
foreman@cit7r02:~/sandbox/binary$ ftp archive.admin.canonical.com
Connected to archive.admin.canonical.com.
220 youngberry.canonical.com FTP server (Poppy Upload Server) ready.
Name (a
Hello dann, or anyone else affected,
Accepted debian-installer into xenial-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/debian-
installer/20101020ubuntu451.22 in a few hours, and then in the -proposed
repository.
Please help us by testing this new
Node fozzie, onza, onibi (these three nodes are affected by this bug)
can boot with the proposed 4.13.0-36-generic #40~16.04.1-Ubuntu i386
kernel.
It looks like the 4.13.0-32 kernel is still affected by this issue, so I
can't deploy Artful image with MaaS, which uses the 4.13.0-32 kernel, we
can e
--- Comment From abdha...@in.ibm.com 2018-02-21 04:30 EDT---
On Ubuntu 1804 Bionic, with 4.15.0-10 kernel. crash analysis failed. I think
the fixes are yet to pushed to bionic
# crash /share/10.10.10.43-201802210423/dump.201802210423
/usr/lib/debug/boot/vmlinux-4.15.0-10-generic
crash 7.
I installed the linked kernel and the wifi still wasn't working (though
with antenna 1 it didn't even find the wifi in the first place and with
antenna 0 it wouldn't connect (the signal was really really bad though)
so it almost seems as if the problem is even worse than with the 4.13.
Though that
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 t
** No longer affects: bluez
** Also affects: bluez via
https://bugzilla.kernel.org/show_bug.cgi?id=198819
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launc
201 - 212 of 212 matches
Mail list logo
