** Description changed:
SRU Justification:
[Impact]
* The following patches removed an exported symbol that will cause
potential disruption and breakage for customers
modules: inherit TAINT_PROPRIETARY_MODULE
modules: return licensing information from find_symbol
modules:
Public bug reported:
[Impact]
These releases provide both bug fixes and new features, and we would like to
make sure all of our users have access to these improvements.
See the changelog entry below for a full list of changes and bugs.
[Test Case]
The following development and SRU process was fo
** Changed in: nvidia-graphics-drivers-510-server (Ubuntu Bionic)
Assignee: (unassigned) => Ian May (ian-may)
** Changed in: nvidia-graphics-drivers-510-server (Ubuntu Focal)
Assignee: (unassigned) => Ian May (ian-may)
** Changed in: nvidia-graphics-drivers-510-server (Ubuntu
** Description changed:
[Impact]
These releases provide both bug fixes and new features, and we would like to
make sure all of our users have access to these improvements.
See the changelog entry below for a full list of changes and bugs.
[Test Case]
The following development and
** Changed in: nvidia-graphics-drivers-510-server (Ubuntu Bionic)
Status: Confirmed => In Progress
** Changed in: nvidia-graphics-drivers-510-server (Ubuntu Focal)
Status: Confirmed => In Progress
** Changed in: nvidia-graphics-drivers-510-server (Ubuntu Impish)
Status: Confi
** Also affects: fabric-manager-510 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: libnvidia-nscq-510 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
Public bug reported:
[Impact]
These releases provide both bug fixes and new features, and we would like to
make sure all of our users have access to these improvements.
See the changelog entry below for a full list of changes and bugs.
[Test Case]
The following development and SRU process was f
** Changed in: linux-nvidia-6.5 (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055712
Title:
Pull-request to address bug in mm/page_alloc.c
To manage not
** Tags added: verification-done-jammy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055712
Title:
Pull-request to address bug in mm/page_alloc.c
To manage notifications about this bug go to:
http
Public bug reported:
Using both -generic and -nvidia 6.8 kernels I'm seeing a hang when I
load the nvidia driver.
[ 382.938326] rcu: INFO: rcu_preempt detected stalls on CPUs/tasks:
[ 382.946075] rcu: 53-...0: (4 ticks this GP)
idle=1c2c/1/0x4000 softirq=4866/4868 fqs=14124
[
** Summary changed:
- Using a 6.8 kernel modprobe nvidia hangs on Grace Hopper
+ Using a 6.8 kernel 'modprobe nvidia' hangs on Quanta Grace Hopper
** Also affects: nvidia-graphics-drivers-535-server (Ubuntu)
Importance: Undecided
Status: New
** Changed in: nvidia-graphics-drivers-535-s
This issue looks to be related to kernel configuration. Using upstream
stable 6.8.1 which is what the current noble being tested is rebased on.
Using 'make defconfig' the nvidia module loads successfully. But with
same kernel using noble config, the nvidia module experiences the same
hang as with
** Also affects: linux-nvidia (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: linux-nvidia (Ubuntu Noble)
Importance: Undecided
Status: New
--
You received this bug notification bec
** Also affects: linux-nvidia (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: linux-nvidia-6.5 (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: linux-nvidia-6.5 (Ubuntu Noble)
--
You received this bug notification because you are a member of
As I was bisecting the commits, I was attempting to take advantage of
parallelism. While my test kernel was building I would deploy a clean
AWS r5.metal instance. I started seeing test kernels boot that I
wouldn't expect to boot. So I decided as a sanity test, I would deploy
an r5.metal instance,
Public bug reported:
Encountered the following error using the docker.io package in focal-
proposed running the autotest-client-
test/ubuntu_performance_deep_learning test.
"docker: Error response from daemon: failed to create shim: OCI runtime
create failed: container_linux.go:380: starting cont
** Description changed:
Encountered the following error using the docker.io package in focal-
proposed running the autotest-client-
test/ubuntu_performance_deep_learning test.
"docker: Error response from daemon: failed to create shim: OCI runtime
create failed: container_linux.go:380
Hi,
I'm seeing a problem with docker.io 20.10.7-0ubuntu5~20.04.1 when
running autotest-client-test/ubuntu_performance_deep_learning
https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1948361
Please let me know if I can provide any further information or any
potential solutions
Thanks,
Ian
Found on: bionic/linux-aws: 4.15.0-.118
** Tags added: aws
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1940261
Title:
ubuntu_seccomp 11-basic-basic_errors failure on X/oracle
To manage notif
Found on: bionic/linux-aws: 4.15.0-.118
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1931325
Title:
cfs_bandwidth01 in sched from ubuntu_ltp_stable failed on B-4.15
To manage notifications abo
This can be resolved by applying the following patches that were added
for arm64 signed support in Disco
UBUNTU: [Packaging] remove handoff check for uefi signing
UBUNTU: [Packaging] decompress gzipped efi images in signing tarball
--
You received this bug notification because you are a member o
cannot create debian/linux-image-4.15.0-1119-SIGNED/*.postinst:
Directory nonexistent
/bin/sh: 21: cannot create debian/linux-image-4.15.0-1119-SIGNED/*.postrm:
Directory nonexistent
/bin/sh: 21: cannot create debian/linux-image-4.15.0-1119-SIGNED/*.preinst:
Directory nonexistent
/bin/sh: 21: cannot c
Patches sent to the ML
https://lists.ubuntu.com/archives/kernel-team/2022-January/127253.html
https://lists.ubuntu.com/archives/kernel-team/2022-January/127251.html
** Changed in: linux-signed-aws (Ubuntu)
Assignee: (unassigned) => Ian May (ian-may)
** Changed in: linux-signed-aws (Ubu
Patches have been applied and bionic/linux-signed-aws now builds
successfully
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958534
Title:
building of linux-signed package failing on arm64
To manag
Tested on Focal 5.4.0-97.110, confirmed inbox peer memory interface is
working.
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
Found also on 2022.01.03/impish/linux-aws: 5.13.0-1012.13
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871015
Title:
test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed
with H (Ch
Found on focal/linux-gcp-5.11: 5.11.0-1019.21~20.04.1
** Tags added: sru-20210906
** Tags added: 5.11
** Tags added: gcp
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1910312
Title:
semctl09 from
Found on impish/linux-aws: 5.13.0-1007.8
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1949532
Title:
ubuntu_ltp_controllers tests failing on Impish
To manage notifications about this bug go to:
ht
Found on impish/linux-azure: 5.13.0-1008.9
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1949532
Title:
ubuntu_ltp_controllers tests failing on Impish
To manage notifications about this bug go to:
** Tags added: aws azures sru-20211108
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1949532
Title:
ubuntu_ltp_controllers tests failing on Impish
To manage notifications about this bug go to:
http
-modules (Ubuntu)
Importance: Undecided
Assignee: Ian May (ian-may)
Status: New
** Affects: nvidia-graphics-drivers-510 (Ubuntu)
Importance: Undecided
Assignee: Ian May (ian-may)
Status: New
** Package changed: ubuntu => linux-restricted-modules (Ubuntu)
** Chan
** Also affects: linux-restricted-modules (Ubuntu Impish)
Importance: Undecided
Status: New
** Also affects: nvidia-graphics-drivers-510 (Ubuntu Impish)
Importance: Undecided
Status: New
** Also affects: linux-restricted-modules (Ubuntu Focal)
Importance: Undecided
S
** Description changed:
[Impact]
These releases provide both bug fixes and new features, and we would like to
make sure all of our users have access to these improvements.
See the changelog entry below for a full list of changes and bugs.
[Test Case]
The following development and
** Changed in: nvidia-graphics-drivers-510 (Ubuntu Bionic)
Status: Confirmed => Fix Committed
** Changed in: nvidia-graphics-drivers-510 (Ubuntu Focal)
Status: Confirmed => Fix Committed
** Changed in: nvidia-graphics-drivers-510 (Ubuntu Impish)
Status: Confirmed => Fix Commi
rg/all/1581937984-40353-2-git-send-email-
yangyic...@hisilicon.com/
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: Ian May (ian-may)
Status: New
** Affects: linux (Ubuntu Focal)
Importance: Undecided
Assignee: Ian May (ian-may)
Status: New
** Al
** Description changed:
- Our NCCL software uses the sysfs to populate the attached topo.xml file.
- Several of the entries should report "32 GT/s", but they're saying
- "Unknown speed" instead. For instance:
+ [Impact]
-
+ NVIDIA Collective Communication Library software uses sysfs to report
** Description changed:
SRU Justification
[Impact]
NVIDIA Collective Communication Library software uses sysfs to report
performance statistics. Users have reported entries showing "Unknown
speed" when they should be reporting "32 GT/s".
Example:
""
PCIe 5.0 supports 3
** Description changed:
SRU Justification
[Impact]
NVIDIA Collective Communication Library software uses sysfs to report
performance statistics. Users have reported entries showing "Unknown
speed" when they should be reporting "32 GT/s".
Example:
""
PCIe 5.0 supports 3
** Description changed:
SRU Justification
[Impact]
NVIDIA Collective Communication Library software uses sysfs to report
performance statistics. Users have reported entries showing "Unknown
speed" when they should be reporting "32 GT/s".
Example:
""
PCIe 5.0 supports 3
Fixed sent to ML and has been applied
https://lists.ubuntu.com/archives/kernel-team/2022-February/128100.html
** Changed in: linux-aws (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:
wget
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa/+files/linux-buildinfo-5.13.0-1014-azure_5.13.0-1014.16_amd64.deb
dpkg -x linux-buildinfo-5.13.0-1014-azure_5.13.0-1014.16_amd64.deb .
grep CONFIG_FB_EFI ./usr/lib/linux/5.13.0-1014-azure/config
CONFIG_FB_EFI=y
** Tags removed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1959216
Title:
linux-azure: CONFIG_FB_EFI=y
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/195
Public bug reported:
Output from BMC SOL console:
Unhandled Exception from EL2
x0 = 0x11f210305619
x1 = 0x
x2 = 0x
x3 = 0x
x4 = 0x5f972493
x5 = 0x
x6
Upgrading bios firmware resolves failure
$ sudo dmidecode -t 0
# dmidecode 3.3
Getting SMBIOS data from sysfs.
SMBIOS 3.6.0 present.
# SMBIOS implementations newer than version 3.5.0 are not
# fully supported by this version of dmidecode.
Handle 0x0001, DMI type 0, 26 bytes
BIOS Information
Public bug reported:
When creating an r5.metal instance on AWS, the default kernel is
bionic/linux-aws-5.4(5.4.0-1056-aws), when changing to bionic/linux-
aws(4.15.0-1113-aws) the machine fails to boot 4.15 kernel.
** Affects: linux-aws (Ubuntu)
Importance: Undecided
Status: New
**
** Description changed:
When creating an r5.metal instance on AWS, the default kernel is
bionic/linux-aws-5.4(5.4.0-1056-aws), when changing to bionic/linux-
aws(4.15.0-1113-aws) the machine fails to boot 4.15 kernel.
+
+ If I remove these patches the instance correctly boots the 4.15 kerne
Have been unable to capture a stack trace using 'aws get-console-
output'. Enabled kdump and was unable to replicate the failed boot,
which makes this feel like a race condition with NVME.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
** Description changed:
When creating an r5.metal instance on AWS, the default kernel is
bionic/linux-aws-5.4(5.4.0-1056-aws), when changing to bionic/linux-
aws(4.15.0-1113-aws) the machine fails to boot 4.15 kernel.
If I remove these patches the instance correctly boots the 4.15 kerne
** Description changed:
When creating an r5.metal instance on AWS, the default kernel is
bionic/linux-aws-5.4(5.4.0-1056-aws), when changing to bionic/linux-
- aws(4.15.0-1113-aws) the machine fails to boot 4.15 kernel.
+ aws(4.15.0-1113-aws) the machine fails to boot the 4.15 kernel.
If
Confirmed it does work to first upgrade bionic/linux-5.4 from
5.4.0-1056-aws to 5.4.0-1058-aws and then update to 4.15.0-1113-aws
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1946149
Title:
Bionic/
** Description changed:
When creating an r5.metal instance on AWS, the default kernel is
bionic/linux-aws-5.4(5.4.0-1056-aws), when changing to bionic/linux-
aws(4.15.0-1113-aws) the machine fails to boot the 4.15 kernel.
If I remove these patches the instance correctly boots the 4.15 k
Thanks for the in-depth update Mauricio! Is there any investigation
you'd like me to specifically target?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1946149
Title:
Bionic/linux-aws Boot failure
Just want to add an update. I haven't been able to replicate
successfully booting 4.15.0-1113-aws from 5.4.0-1058-aws, so I'm
questioning whether I made a mistake the time I thought it was
successful.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
Mauricio,
Interesting update, I agree that we need more info as to what the state
is when the instance won't boot switching to the new 4.15 kernel. I'll
check with my team in the morning and see if we can get additional info
from AWS
I was trying a few more scenarios this evening the first being
Found on bionic/linux-gcp-fips: 4.15.0-2020.22 - n1-highcpu-4
** Tags added: gcp sru-20210927
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1876687
Title:
function traceon/off triggers in ftace fro
Found on bionic/linux-oracle-5.4: 5.4.0-1056.60~18.04.1 -
BM.Standard2.52
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1830585
Title:
cpuset_memory_spread from controllers test suite in LTP failed
Hi Mauricio,
Thanks for getting this info. This is very helpful! I see a few
potential patches between 4.15.0-159.167 and 4.15.0-160.168 that could
be related to the hang. This will help greatly with the bisect.
Ian
--
You received this bug notification because you are a member of Ubuntu
Bug
57 matches
Mail list logo
