This is the result of pulling the lxc test sources from the git repo,
but using the lxc from the archive. Currently, the archive has version
4.0.6 and the git repo has been updated to 4.0.12 as an upload is in
progress (it's in the unapproved queue as this comment is being
written).
The result is
Public bug reported:
Hibernation testing of jammy/linux-aws 5.15.0-1003-aws is failing on all
xen instance types (c3/c4/i3/m3/m4/r3/r4/t2). The failure happens while
attempting to resume from the first attempt to hibernate. Testing on
nitro instances types (c5/m5/r5/t3) all pass.
After the
** Attachment added: "First screenshot after resume initiated"
https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1968062/+attachment/5577677/+files/post-hibernate.01.jpg
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws
** Attachment added: "Last screenshot before hibernation"
https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1968062/+attachment/5577676/+files/pre-hibernation.04.jpg
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in
This screenshot was taken a few minutes after the resume attempt. These
ssm-amazon-agent messages repeat every 120 seconds with a new set. But
this is all the progress we see from either the screenshot or the serial
console. There are no new memory consumption messages indicating that
the resume
In this screenshot, it appears the system has resumed as the login
screen is shown along with the messages from the hibernation memory
consumption utility. The first memory message was generated prior to the
hibernation (matches the message from the pre-hibernation image). The
second message could
Public bug reported:
Seeing a panic on hidon (an Nvidia H100) after booting the
5.15.0-85-generic kernel:
[ 58.935877] [ cut here ]
[ 58.935893] refcount_t: underflow; use-after-free.
[ 58.935920] WARNING: CPU: 207 PID: 2985 at lib/refcount.c:28
Here's the full log from where that snippet was pulled.
** Attachment added: "hidon.log.1"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2034447/+attachment/5697793/+files/hidon.log.1
--
You received this bug notification because you are a member of Kernel
Packages, which is
apport information
** Tags added: apport-collected jammy uec-images
** Description changed:
Seeing a panic on hidon (an Nvidia H100) after booting the
5.15.0-85-generic kernel:
[ 58.935877] [ cut here ]
[ 58.935893] refcount_t: underflow; use-after-free.
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/2034447/+attachment/5697973/+files/Lspci.txt
--
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/2034447
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/2034447/+attachment/5697978/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/2034447/+attachment/5697977/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/2034447/+attachment/5697979/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/2034447/+attachment/5697975/+files/Lsusb-v.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/2034447/+attachment/5697976/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/2034447/+attachment/5697974/+files/Lspci-vt.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/2034447/+attachment/5697982/+files/acpidump.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/2034447/+attachment/5697981/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/2034447/+attachment/5697980/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Project changed: linux => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Milestone: None => ubuntu-23.10
** Also affects: linux (Ubuntu Mantic)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Mantic)
Importance: Undecided
Status: Confirmed
--
You
The latest maas images from 20231008 are booting without issue:
ubuntu@akis:~$ lsb_release -sc
No LSB modules are available.
mantic
ubuntu@akis:~$ cat /etc/cloud/build.info
build_name: server
serial: 20231008
ubuntu@akis:~$ uname -a
Linux akis 6.5.0-7-generic #7-Ubuntu SMP PREEMPT_DYNAMIC Fri
Special maas image built with util-linux, 2.39.1-4ubuntu2, from
https://ppa.launchpadcontent.net/xnox/release-critical/ubuntu is looking
good. I have one machine deployed with this:
ubuntu@rumford:~$ uname -r
6.5.0-5-lowlatency
ubuntu@rumford:~$ apt-cache policy util-linux
util-linux:
** Changed in: linux (Ubuntu)
Status: Incomplete => 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/1973034
Title:
linux generic fails to boot on azure arm64 instance
Updated kernels are in flight. The updated kernel packages and versions
are:
linux-aws-5.13- 5.13.0-1029.32~20.04.1
linux-azure-5.13 - 5.13.0-1029.34~20.04.1
linux-gcp-5.13- 5.13.0-1031.37~20.04.1
linux-oracle-5.13 - 5.13.0-1034.40~20.04.1
The azure and gcp kernels are already in
Work on this issue continues. We have identified the following impacted
kernels and versions:
focal linux-aws-5.13 5.13.0-1028.31~20.04.1
focal linux-azure-5.13 5.13.0-1028.33~20.04.1
focal linux-gcp-5.13 5.13.0-1030.36~20.04.1
focal linux-oracle-5.13 5.13.0-1033.39~20.04.1
--
You received
All of the updated 5.13 kernels have now made it to the archive and into
both the focal-updates and focal-security pockets. That list of kernels
is:
linux-aws-5.13 - 5.13.0-1029.32~20.04.1
linux-azure-5.13 - 5.13.0-1029.34~20.04.1
linux-gcp-5.13 - 5.13.0-1031.37~20.04.1
linux-oracle-5.13 -
Hello Sebastian,
I've been unable to reproduce this issue with the 5.13.0-1029-aws kernel
and the docker-compose example available from [1]. Are you able to
provide complete steps to reproduce?
[1] - https://docs.docker.com/compose/gettingstarted/
Thanks
--
You received this bug notification
Testing of nvidia-fabricmanager-510 and libnvidia-nscq-510 has been
successfully performed again against the packages in -proposed. These
are good to release from a testing perspective.
** Tags removed: verification-needed verification-needed-bionic
verification-needed-focal
The fabric-manager-510 and libnvidia-nscq-510 were tested across all
series on an A100 system. All testing passed the standard cuda testing.
The packages tested were from https://launchpad.net/~canonical-kernel-
team/+archive/ubuntu/ppa/+packages?field.name_filter=-510_filter=published_filter=
--
Public bug reported:
Azure now has arm64 instances in a preview, for example
Standard_D2pds_v5. These work with the b/linux-azure and f/linux-azure
kernels, but fail to boot with linux-generic.
Looks like a storage device issue (from serial console):
Begin: Running /scripts/init-premount ...
Artifacts were collected from a new VM running focal/linux-azure just
prior to rebooting to linux-generic (which gets stuck at initramfs).
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1973034/+attachment/5588646/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1973034/+attachment/5588651/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1973034/+attachment/5588649/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/1973034/+attachment/5588654/+files/acpidump.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1973034/+attachment/5588653/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1973034/+attachment/5588652/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1973034/+attachment/5588650/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Tags added: apport-collected focal uec-images
** Description changed:
Azure now has arm64 instances in a preview, for example
Standard_D2pds_v5. These work with the b/linux-azure and f/linux-azure
kernels, but fail to boot with linux-generic.
Looks like a
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1973034/+attachment/5588647/+files/Lspci.txt
--
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/1973034
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1973034/+attachment/5588648/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Tags added: 5.4
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure-4.15 in Ubuntu.
https://bugs.launchpad.net/bugs/1923114
Title:
ubuntu_kernel_selftests: ./cpu-on-off-test.sh: line 94: echo: write
error: Device or
The A100 is down with some hardware issues and there is no ETA when it
will be up again. Given that the testing passed on the DGX2 and the A100
is having hardware issues which quite likely impacted the testing, I'm
going to consider the kinetic testing as verified.
** Tags removed:
Re-running through the testing on our DGX2 now passes for both DKMS and
LRM. I will need to retry the testing on A100 again and see if I missed
something like the fabricmanager not being ready yet.
--
You received this bug notification because you are a member of Kernel
Packages, which is
Verification on kinetic is incomplete. Things do work on a cloud
instance with a single gpgpu. In these cases, both the DKMS and LRM
version of the driver works with the cuda samples test.
Problems are encountered when running on either the DGX2 or A100
systems. For the A100, I have not been able
@juliank, ah, I found another detail. This appears to only break when
the package is updated in the ADT testbed. My assumption is if the
latest package version is already in the base image, there is no package
update and therefore no breakage. For example:
[1] older image, fails:
Tested bionic, focal and jammy on VMs and a DGX2. All cuda tests passed.
There is no updated kinetic driver, so unable to test there.
** Tags added: verification-done-bionic verification-done-focal
verification-done-jammy verification-failed-kinetic
--
You received this bug notification
@juliank Hello, I see that you picked up
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.4/+bug/1991676. I
just want to mention so that you are aware, that this is blocking most,
if not all, kernel ADT testing on bionic arm64.
--
You received this bug notification because you are a member
Still failing on baltar.ppc64el.9 during 2023.02.27 sru cycle. The
kuzzle and scobee (another arm64 server) passed.
** Tags added: sru-20230227
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
No regressions found for either 515-server or 525-server. Both were
tested as DKMS and as LRMs using the generic kernel in all releases
(lunar could not be installed with lrm). Jammy was also tested with the
linux-nvidia kernel and LRMs.
--
You received this bug notification because you are a
I can confirm @xnox's findings with my maas server deploying lunar.
Adding `apparmor=1` to the settings/configuration/kernel-parameters
allows for a successful deployment with the lunar 6.2.0-20.20 kernel.
--
You received this bug notification because you are a member of Kernel
Packages, which
Cuda testing passed for all drivers (470, 515, 525, 450-server,
470-server, 515-server, 525-server) on bionic, focal, jammy and kinetic
using both DKMS and LRM (when using the appropriate stream 2 ppa for the
LRM packages). DKMS testing also passed on lunar.
--
You received this bug notification
Here is the full syslog from which the portion in the bug description
was extracted from.
** Attachment added: "c5.12xlarge-3-syslog.log"
https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2006620/+attachment/5645600/+files/c5.12xlarge-3-syslog.log
--
You received this bug
Public bug reported:
Hibernation on AWS instances with jammy/5.19.0-1019-aws sometimes fails
due to the following failure to freeze:
Feb 1 01:09:05 ip-172-31-54-178 kernel: [ 443.247854] PM: hibernation:
hibernation entry
Feb 1 01:09:05 ip-172-31-54-178 kernel: [ 443.347353] TSC found
Public bug reported:
I'm seeing an issue on an isolated host, howzit, in which it fails to
remove boot entries. In my limited testing this worked with the
6.2.0-20.20 kernel, but not the 21.21 or 23.23 kernel. I have not yet
tried any of the 6.3 kernels.
I've only seen this on one host so far,
I've found a flaw in the test script in which it was installing the
wrong LRM modules for the running kernel. It was installing the generic
modules for a gcp kernel. Once I corrected this to install the gcp
modules, it now passes.
Attached are the logs with the addition of `lsmod` and `modinfo
I've reproduced this with the 6.3.0-7-generic kernel from mantic-
proposed.
--
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/2023611
Title:
Unable to remove efi variable with 6.2.0-21.21
I ran through several kernels on our DGX-2 server, only the latest
6.2.0-1004-nvidia kernel emitted the warning. Here are all the kernels I
tried:
Lunar 6.2.0-24.24 generic - PASS
Jammy 5.15.0-1028-nvidia - PASS
Jammy 5.19.0-46-generic - PASS
Jammy 5.19.0-1014-nvidia - PASS
Jammy 6.2.0-25-generic
Public bug reported:
We started testing the jammy/linux-nvidia-6.2 kernels on the nvidia
servers (DGX-1/DGX-2/H100) and hit the following warning during boot:
[7.690486] [ cut here ]
[7.690487] Interrupts were enabled early
[7.690490] WARNING: CPU: 0 PID: 0 at
I built and tested a 6.2.0-1004-nvidia based kernel with this patch
applied and did not see the warning message on boot. I'll follow up
further with Ian on Monday.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-nvidia-6.2 in
Public bug reported:
Installing "nvidia-driver-525-open" followed by "nvidia-headless-no-
dkms-525 linux-modules-nvidia-525-gcp nvidia-utils-525" led to a system
which complained about a "Driver/library version mismatch". Specifically
what was done is:
Deploy a clean google VM with:
gcloud
Automated testing of the DKMS drivers, (450-server, 470-server,
525-server, 470, 525 and 535) has completed across bionic, focal, jammy,
kinetic and lunar. This was performed with:
* Deploy host with gpgpu
* Install latest `linux-generic` kernel
* Install driver from ppa using
@navroop005,
Hello, would you mind please sharing a copy of your
`/var/log/apt/history.log`? This looks like a possible package
dependency issue.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-oracle in Ubuntu.
Thanks to everyone supplying their logs. I'm still looking through these
to try to understand what's going on here.
For most that hit this issue, the solution would be interrupt the boot
loader to boot back into the generic kernel, then remove the oracle and
lowlatency kernels.
--
You received
We are still looking into this issue. While we can reproduce the test
case and see difference in the performance, the delta is not as
significant and our results have not very consistent. I'm taking the
approach of setting up a more comprehensive test environment to run more
tests faster.
I can reproduce the failure on mantic with both the DKMS and LRM
drivers. Specifically what I'm doing to install these are:
for DKMS:
sudo DEBIAN_FRONTEND=noninteractive apt-get install -y nvidia-driver-535-server
for LRM:
sudo DEBIAN_FRONTEND=noninteractive apt-get install -y
@paride: Yes, I've seen this with other kernels, mostly with the nvidia
drivers. I think all of the runs of the following since March 20 show
this problem:
https://autopkgtest.ubuntu.com/packages/n/nvidia-graphics-drivers-510-server/focal/amd64
I have done my typical CUDA based testing with this package using the
generic, nvidia and gcp kernels using bionic, focal, jammy and mantic
(amd64 only so far).
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-470
201 - 268 of 268 matches
Mail list logo
