@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
@Kevin,
Thank you for testing again. This latest output indicates something may
not be correct in your test environment. This line:
WARNING:root:_pkg_get_support nvidia-driver-525: package has invalid
Support PBheader, cannot determine support level
is indicating that the driver packages are
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
@kevinyew, @shanew, It looks like you are hitting this on focal. Can you
please confirm?
If so, can you please retest with the latest ubuntu-drivers from focal-
proposed? This should be version 1:0.9.0~0.20.04.8. This appears to fix
a bug (discussed in
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1973034
Title:
linux generic fails to boot on azure arm64 instance types
To
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1973034
Title:
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1973034
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1973034
Title:
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1973034
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1973034
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 Ubuntu
Bugs, which is subscribed to 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 Ubuntu
Bugs, which is subscribed to Ubuntu.
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1973034
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1973034
Title:
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 Ubuntu
Bugs, which is subscribed to 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
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 ...
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
** 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 Ubuntu
Bugs, which is subscribed to Ubuntu.
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
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
** 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 Ubuntu
Bugs, which is subscribed to Ubuntu.
Moving this to xmltodict as I've been able to parse multiple xml files
through just python3's xml.parsers.expat without error, but none of them
through xmltodict.
** Also affects: python-xmltodict (Ubuntu)
Importance: Undecided
Status: New
** Changed in: python-xmltodict (Ubuntu)
This may be an issue with the python3 xmltodict module. Further testing
indicates that parsing a file with just xml.parsers.expat is working
just fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Attached is an example config file and python script which demonstrates
the parsing error. This was reproduced on focal with:
$ apt-cache policy libexpat1
libexpat1:
Installed: 2.2.9-1ubuntu0.2
Candidate: 2.2.9-1ubuntu0.2
Version table:
*** 2.2.9-1ubuntu0.2 500
500
I was able to workaround the issue by downgrading to the release version
of the package:
$ sudo apt-get install libexpat1=2.2.5-3 libexpat1-dev=2.2.5-3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
I started seeing errors parsing XML files today (Feb 22, 2022) after my
system was updated to 2.2.5-3ubuntu0.4. This is on a bionic server.
The parsing is being done by python3's xmltodict module, which uses
python3 expat as the actual parser. This is the error it raises:
*** This bug is a duplicate of bug 1956613 ***
https://bugs.launchpad.net/bugs/1956613
This is a dup. After upgrading the maas server to 3.1, the issue is
resolved.
** This bug has been marked a duplicate of bug 1956613
Traceback deploying Jammy with MAAS 3.1
--
You received this bug
Public bug reported:
Using maas to install jammy to an nvidia dgx-1. Curtin fails with the
following log:
curtin: Installation started. (21.2-0ubuntu1~20.04.1)
third party drivers not installed or necessary.
start: cmd-install/stage-partitioning/builtin/cmd-block-meta: curtin command
block-meta
Public bug reported:
Several SRU tests are failing the test setup due to failure to install
the modules-extra package:
* Command:
yes "" | DEBIAN_FRONTEND=noninteractive apt-get install --yes --force-yes
automake bison build-essential byacc flex git keyutils libacl1-dev libaio-
dev
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
I've retested two released kernels that passed the lxc test last cycle:
* focal/azure 5.4.0-1068.71
* focal/azure-5-11 5.11.0-1028.31~20.04.1
Both tests now show the same testcase failures where they were passing
before. Will start digging into any other changes in the environment.
--
You
Restoring the state for python3-lxc as we're using the test from this
project.
** Changed in: python3-lxc (Ubuntu)
Status: Invalid => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1952036
This is expected due to the change in impish to cgroups2. This is really
a test issue, not an issue with lxc.
** Changed in: python3-lxc (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Tests are now passing.
** Changed in: ubuntu-kernel-tests
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/192
Title:
test_utils_testsuite from ubuntu_qrt_apparmor
Retested with the latest kernels as of Sept 7, 2021. Now able to see
that ubuntu-drivers now lists the 470-server driver as an available
option. For both Focal and Hirsute, I first had to enable -proposed. For
Bionic, it worked with the 4.15.0-156.163 kernel that was released this
week.
Tested
While the 470-server drivers installed and passed the cuda testing
across bionic/focal/hirsute, "ubuntu-drivers" does not identify this as
a option for any release. The response I see is:
$ sudo ubuntu-drivers list --gpgpu
WARNING:root:_pkg_get_support nvidia-driver-390: package has invalid
Adding verification-done as this does fix the problem in nearly all
testing. I think there is a corner case or something specific to the
testing which is causing these outliers.
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug
@sil2100
Following up on our chat conversation. I actually thing this grub2
package update could be released. It is greatly improving the situation
and I think is doing the right thing. But I think there may be other
external factors in play that may result in these corner cases.
I can give a
@juliank
This does not appear to be a complete fix for the issue seen on AWS
t2.nano. I see failures in about 5 - 10% of cases. There are two
different symptoms:
* grub-initrd-fallback.service sometimes runs right before the system
hibernates (it runs after the hibernation request was sent to
Testing has completed for this 470-server driver across bionic, focal
and hirsute. The LRM version of the driver was tested against the linux
generic kernels currently in -proposed:
4.15.0-152-generic
5.4.0-81-generic
5.11.0-25-generic
Testing consisted of running a basic set of the cuda samples
[Summary]
I believe this problem is related to a change in behavior in cloud-init version
21.2-43-g184c836a-0ubuntu1 due to comparing two different daily impish images
before and after this update.
The problem appears in a gcp account which currently has multple global
sshkeys associated with
Failed on bionic:linux generic amd64 host spitfire sru-20210621.
** Summary changed:
- function traceon/off triggers in ftace from ubuntu_kernel_selftests failed on
Focal
+ function traceon/off triggers in ftace from ubuntu_kernel_selftests failed on
B/F
** Tags added: sru-20210621
--
You
@albertomilone. I've completed the basic CUDA testing of the server
drivers. As with the prior version, the 450-server and 460-server
drivers passed across the generic kernels for bionic, focal, groovy,
hirsute and impish. This applies to both the dkms and lrm installations.
Impish was tested with
Public bug reported:
Encountered the following panic while doing hibernation/resume testing
with linux-aws 5.8 on Focal on an m3.xlarge (xen) instance type:
[ 594.291317] ACPI: Hardware changed while hibernated, success doubtful!
[ 594.411609] BUG: kernel NULL pointer dereference, address:
Public bug reported:
Ubuntu Focal (and new releases) on AWS will normally boot without an
initrd image (just the microcode.cpio). There is a fallback mechanism to
reboot with the full initrd image when the boot fails to complete. The
grub environment variable "initrdfail" is used to track when a
** Tags added: 5.4 sru-20210510
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923191
Title:
cpuhotplug from ubuntu_ltp failed for cpuhotplug02 cpuhotplug03
cpuhotplug04 cpuhotplug06
To manage
fabric-manager-460 and libnvidia-nscq-460:
These passed using the cuda samples test and 'dcgmi discovery -l' test on a
dgx-2 host using bionic and focal.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I've completed additional testing on bionic on a dgx2:
nvidia-graphics-drivers-450-server:
Both the bionic lrm and dkms versions were tested successfully with via the
cuda samples test (version 11.0).
fabric-manager-450 and libnvidia-nscq-450:
These passed using the cuda samples test and 'dcgmi
nvidia-graphics-drivers-450-server, 450.119.04 results:
The DKMS driver was tested via the cuda samples test. This passed for
bionic, focal and groovy, but failed for hirsute and impish. This
failure was expected as the nvidia_uvm module doens't currently load
with the 5.11 kernel in hirsute and
This is resolved in autotest-client-tests
5b2d46bf401e50a13be5c0641e0157d58c2a7669
** Changed in: ubuntu-kernel-tests
Status: New => Fix Released
** Changed in: linux-riscv (Ubuntu)
Status: New => Won't Fix
** Changed in: linux-riscv (Ubuntu Hirsute)
Status: New => Won't
Also tested linux-modules-nvidia-460-server-generic-hwe-18.04 on bionic
and linux-modules-nvidia-460-server-generic-hwe-20.04 on focal. They
look good now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Testing of the server drivers is also complete. All drivers were able to
install as both dkms and l-r-m with no issues. A cuda workload and
nvidia-smi was also tested for each.
Note: no upgrade testing was attempted. Drivers were fully purged before
testing the next driver.
--
You received this
This panic occurred while running the ubuntu_kernel_selftests suite. The
last bit of logs are:
13:33:20 DEBUG| [stdout] # selftests: ftrace: ftracetest
13:33:20 DEBUG| [stdout] # === Ftrace unit tests ===
13:33:28 DEBUG| [stdout] # [1] Basic trace file check [PASS]
13:37:04 DEBUG| [stdout] # [2]
This panic occurred while running the ubuntu_kernel_selftests suite. The
last bit of logs are:
13:33:20 DEBUG| [stdout] # selftests: ftrace: ftracetest
13:33:20 DEBUG| [stdout] # === Ftrace unit tests ===
13:33:28 DEBUG| [stdout] # [1] Basic trace file check [PASS]
13:37:04 DEBUG| [stdout] #
I also looked at this and compared with older kernels. This test has
never progressed past the "Kretprobe dynamic event with maxactive" test
on 5.8, but it has on 5.4:
```
18:41:31 DEBUG| [stdout] # [43] Kprobe event parser error log check [PASS]
18:41:32 DEBUG| [stdout] # [44] Kretprobe
Seen with linux-aws 5.4.0-1038.40~18.04.1.
** Tags added: sru-20210125
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1805806
Title:
test_maps in ubuntu_bpf failed with "Failed sockmap unexpected
** Tags added: sru-20210125
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1844493
Title:
ubuntu_sysdig_smoke_test failed on 5.3 / 5.4 / 5.6 /5.8 kernels
To manage notifications about this bug go
** Attachment added: "dmesg-5.8.0-17-generic"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1905728/+attachment/5464855/+files/dmesg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1905728
Still seeing this with the 5.8.0-17-generic riscv kernel on groovy. See
attached dmesg.
** Changed in: linux (Ubuntu)
Status: Expired => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Seen with linux-oracle 4.15.0-1065.73~16.04.1.
** Tags added: sru-20210125
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1748103
Title:
apic test in kvm-unit-test failed with timeout
To manage
Seen with linux-oracle 4.15.0-1065.73~16.04.1.
** Tags added: sru-20210125
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1831449
Title:
memory in ubuntu_kvm_unit_tests fails
To manage
Seen with linux-oracle 4.15.0-1065.73~16.04.1.
** Tags added: sru-20210125
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1748105
Title:
port80 test in ubuntu_kvm_unit_tests failed with timeout
Seen with linux-oracle 4.15.0-1065.73~16.04.1.
** Tags added: sru-20210125
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827979
Title:
pcid in ubuntu_kvm_unit_tests failed on B-KVM /
Seen with linux-oracle 4.15.0-1065.73.
** Tags added: oracle sru-20210125
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1829995
Title:
getaddrinfo_01 from ipv6_lib test suite in LTP failed
To
Seen with linux-oracle 4.15.0-1065.73.
** Tags added: sru-20210125
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1837035
Title:
memcg_stat_rss from controllers in ubuntu_ltp failed
To manage
Seen with linux-oracle 4.15.0-1065.73.
** Tags added: sru-20210125
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1837543
Title:
crypto_user02 in crypto from ubuntu_ltp failed
To manage
Seen with linux-oracle 4.15.0-1065.73.
** Tags added: sru-20210125
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1829849
Title:
proc01 in fs from ubuntu_ltp failed
To manage notifications about
Seen with linux-oracle 4.15.0-1065.73.
** Tags added: oracle sru-20210125
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1829978
Title:
cpuacct_100_100 from controllers test suite in LTP failed
To
Still seen with linux-oracle 4.15.0-1065.73.
** Tags added: sru-20210125
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1822309
Title:
vmx_apic_passthrough_thread in kvm_unit_tests failed with 1
Seen with linux-oracle 4.15.0-1065.73.
** Tags added: sru-2021-0125
** Tags removed: sru-2021-0125
** Tags added: sru-20210125
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1822308
Title:
Still seen with linux-oracle 4.15.0-1065.73.
** Tags added: sru-20210125
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1839912
Title:
test_map in ubuntu_bpf failed with "Allowed update sockmap
@juergh, I retested this with focal 5.4.0-1028-raspi and was unable to
reproduce.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1882213
Title:
cp file from external HDD to NFS on Pi 3B causes
Testing of the 460-server driver has passed on bionic, focal and groovy.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1913200
Title:
Introduce the new NVIDIA 460-server series and update the 460
** Tags added: sru-20200104
** Tags added: sru-20200125
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1910982
Title:
ZTE Modem USB stick not recognized with kernel 5.8
To manage notifications
*** This bug is a duplicate of bug 1906850 ***
https://bugs.launchpad.net/bugs/1906850
** This bug has been marked a duplicate of bug 1906850
aws: xen-netfront: prevent potential error on hibernate
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
The build issue is due a mismatch in package versions for those nvidia
drivers as you indicated. The driver contents are the same, the mismatch
is in the version strings.
The version strings can be brought in sync by running:
$ apt-get source linux-image-5.4.0-1035-aws
$ cd linux-aws-5.4-5.4.0
$
This is likely the same underlying root cause as
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1901633. The system
is failing to fallback to the initrd path and therefore gets stuck in a
reboot/panic loop.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
(Ubuntu Hirsute)
Assignee: (unassigned) => Francis Ginther (fginther)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1904243
Title:
21.04 Panics attempting to boot 5.10.0-3.4 in gcp EFI d
I've run through additional gpgpu testing of these drivers along with
the linux-restricted-modules for the generic kernels in bionic, focal
and groovy plus the hwe kernel in bionic.
Also added block-proposed-groovy to prevent accidental promotion on
groovy.
** Tags added: block-proposed-groovy
I ran this through our automated hibernation testing. On spot checking
the logs, I do see the resume path being set to the PARTUUID as expected
by this SRU. I consider this to cover `verification-done-focal` for our
testing.
--
You received this bug notification because you are a member of
** Tags removed: verification-needed-groovy
** Tags added: verification-done-groovy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1897751
Title:
Introduce the new NVIDIA 455 series
To manage
I tested basic installation of the linux-restricted-modules packages
along with the associated kernel and 455 driver. Also exercised the
driver with a cuda workload. This is the same testing I would execute
for the nvidia server drivers (for example:
@rbalint, we have not seen the same issue with the 4.15 linux-aws-hwe
kernels used in xenial. At this time, the backport to xenial is not
necessary.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Responding to comment #15:
The 5.8.13 upstream stable update was included in the ubuntu linux
kernel version 5.8.0-21.22 in groovy. The 5.4 kernel update including
5.4.69 has not been released yet.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
@xnox, @fheimes, we are preparing a groovy respin which will pick this
up.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1899582
Title:
ceph: fix inode number handling on arches with 32-bit ino_t
@xnox, we are preparing a groovy respin which will pick this up.
** Changed in: linux (Ubuntu Groovy)
Milestone: groovy-updates => ubuntu-20.10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Actually, I'm going to set this to 'triaged'. We can then use this as
the motivation for getting the `release hold` issue fixed.
** Changed in: linux-restricted-modules (Ubuntu)
Status: Invalid => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs,
This should be resolved now that the linux-restricted-modules which
generate `linux-modules-nvidia-450-server-generic` have been released.
It was a consequence of the nvidia driver packages being released to the
archive prematurely and the time it takes for a kernel update to advance
through the
** Tags added: groovy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1840904
Title:
ubuntu_fan_smoke_test failed with enable disable fan test on GKE 4.15
with g1-small and n1-highmem-16 /
** Tags added: groovy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1892213
Title:
psock_snd.sh in net from ubuntu_kernel_selftests ADT failure with
focal/linux
To manage notifications about
This was fixed for the groovy kernel in
https://lists.ubuntu.com/archives/kernel-team/2020-October/113973.html
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Committed
** Changed in: linux-aws (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug
I've tested the 450-server drivers for both Focal and Bionic using the
5.4.0-49-generic kernel for focal and the 4.15.0-119-generic and
5.4.0-49-generic for bionic. In all cases, the DKMS modules were used
for testing.
The test consists of running a subset of the CUDA 11.0 samples on both a
Tesla
** Description changed:
[Impact]
- * TODO
-
+ Enabling CONFIG_SUSPEND in the kernel exposes a potential deadlock on
+ Xen instance types on AWS during hibernation, so it has been disabled in
+ the linux-aws kernel as an extra safety measure to prevent this problem
+ from happening.
Patches have been committed to the 5.8 master-next branch. Expected in
the next 5.8 groovy kernel.
** Changed in: linux (Ubuntu Groovy)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Seen with Bionic linux-aws 5.4.0-1026.26~18.04.1 and
5.4.0-1025.25~18.04.1 on arm64.
** Tags added: sru-20200921
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1845870
Title:
test_verifier from
Failing with Bionic linux-aws 5.4.0-1026.26~18.04.1 and
5.4.0-1025.25~18.04.1.
** Tags added: sru-20200921
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1844493
Title:
ubuntu_sysdig_smoke_test
I've updated the find_device_for_file() function in /usr/bin/hibinit-
agent to:
def find_device_for_file(filename):
# Find the mount point for the swap file ('df -P /swap')
df_out = check_output(['df', '-P', filename]).decode('ascii')
dev_str = df_out.split("\n")[1].split()[0]
I was unable to get either the by-uuid or by-label paths to work in my
initial hacking. The kernel cmdline looked like what I would expect, for
example '... resume_offset=225280 resume=/dev/disk/by-label/cloudimg-
rootfs', but the hibernation image was not restored. Not currently
seeing anything
1 - 100 of 1603 matches
Mail list logo
