[Bug 2064549] Re: pull-request: Fixes: b2b56a163230 ("gpio: tegra186: Check GPIO pin permission before access.")
** 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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064549
Title:
pull-request: Fixes: b2b56a163230 ("gpio: tegra186: Check GPIO pin
permission before access.")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-nvidia/+bug/2064549/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059316] Re: backport arm64 THP improvements from 6.9
** 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 because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059316 Title: backport arm64 THP improvements from 6.9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2059316/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062380] Re: Using a 6.8 kernel 'modprobe nvidia' hangs on Quanta Grace Hopper
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 noble kernel. I'm currently working through config comparison and testing changes. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062380 Title: Using a 6.8 kernel 'modprobe nvidia' hangs on Quanta Grace Hopper To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-535-server/+bug/2062380/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062380] Re: Using a 6.8 kernel 'modprobe nvidia' hangs on Quanta Grace Hopper
** 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-server (Ubuntu) Status: New => Confirmed ** Changed in: nvidia-graphics-drivers-550-server (Ubuntu) Status: New => Confirmed ** Description changed: Using both -generic and -nvidia 6.8 kernels I'm seeing a hang when I load the nvidia driver. + + $ sudo dmidecode -t 0 + # dmidecode 3.5 + 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 + Vendor: NVIDIA + Version: 01.02.01 + Release Date: 20240207 + ROM Size: 64 MB + Characteristics: + PCI is supported + PNP is supported + BIOS is upgradeable + BIOS shadowing is allowed + Boot from CD is supported + Selectable boot is supported + Serial services are supported (int 14h) + ACPI is supported + Targeted content distribution is supported + UEFI is supported + Firmware Revision: 0.0 [ 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 [ 382.955683] rcu: hardirqs softirqs csw/system [ 382.961378] rcu: number:0 00 [ 382.967071] rcu: cputime:0 00 ==> 30026(ms) [ 382.974189] rcu: (detected by 52, t=60034 jiffies, g=24469, q=1199 ncpus=72) [ 392.982095] rcu: rcu_preempt kthread starved for 9994 jiffies! g24469 f0x0 RCU_GP_DOING_FQS(6) ->state=0x0 ->cpu=31 [ 392.992769] rcu: Unless rcu_preempt kthread gets sufficient CPU time, OOM is now expected behavior - After seeing this, I Enabled kdump and set kernel.panic_on_rcu_stall = 1 KDUMP INFO WARNING: cpu 54: cannot find NT_PRSTATUS note - KERNEL: /usr/lib/debug/boot/vmlinux-6.8.0-1004-nvidia-64k [TAINTED] - DUMPFILE: /var/crash/202404172139/dump.202404172139 [PARTIAL DUMP] - CPUS: 72 - DATE: Wed Apr 17 21:39:13 UTC 2024 - UPTIME: 00:06:10 + KERNEL: /usr/lib/debug/boot/vmlinux-6.8.0-1004-nvidia-64k [TAINTED] + DUMPFILE: /var/crash/202404172139/dump.202404172139 [PARTIAL DUMP] + CPUS: 72 + DATE: Wed Apr 17 21:39:13 UTC 2024 + UPTIME: 00:06:10 LOAD AVERAGE: 0.68, 0.63, 0.28 -TASKS: 854 - NODENAME: hinyari - RELEASE: 6.8.0-1005-nvidia-64k - VERSION: #5-Ubuntu SMP PREEMPT_DYNAMIC Wed Apr 17 11:26:46 UTC 2024 - MACHINE: aarch64 (unknown Mhz) - MEMORY: 479.7 GB -PANIC: "Kernel panic - not syncing: RCU Stall" - PID: 0 - COMMAND: "swapper/21" - TASK: 82026880 (1 of 72) [THREAD_INFO: 82026880] - CPU: 21 -STATE: TASK_RUNNING (PANIC) + TASKS: 854 + NODENAME: hinyari + RELEASE: 6.8.0-1005-nvidia-64k + VERSION: #5-Ubuntu SMP PREEMPT_DYNAMIC Wed Apr 17 11:26:46 UTC 2024 + MACHINE: aarch64 (unknown Mhz) + MEMORY: 479.7 GB + PANIC: "Kernel panic - not syncing: RCU Stall" + PID: 0 + COMMAND: "swapper/21" + TASK: 82026880 (1 of 72) [THREAD_INFO: 82026880] + CPU: 21 + STATE: TASK_RUNNING (PANIC) [ 300.313144] nvidia: loading out-of-tree module taints kernel. [ 300.313153] nvidia: module verification failed: signature and/or required key missing - tainting kernel [ 300.316694] nvidia-nvlink: Nvlink Core is being initialized, major device number 506 - [ 300.316699] + [ 300.316699] [ 360.323454] rcu: INFO: rcu_preempt detected stalls on CPUs/tasks: [ 360.331206] rcu: 54-...0: (24 ticks this GP) idle=742c/1/0x4000 softirq=4931/4933 fqs=13148 [ 360.340903] rcu: hardirqs softirqs csw/system [ 360.346597] rcu: number:0 00 [ 360.352291] rcu: cputime:0 00 ==> 30031(ms) [ 360.359408] rcu: (detected by 21, t=60038 jiffies, g=25009, q=1123 ncpus=72) [ 360.366704] Sending NMI from CPU 21 to CPUs 54: [ 370.367310] rcu: rcu_preempt kthread starved for 9993 jiffies! g25009 f0x0 RCU_GP_DOING_FQS(6) ->state=0x0 ->cpu=31 [ 370.377983] rcu: Unless rcu_preempt kthread gets sufficient CPU time, OOM is now expected behavior. [ 370.387322] rcu: RCU grace-period kthread stack dump: [ 370.392482] task:rcu_preempt state:I stack:0 pid:17tgid:17 ppid:2 flags:0x0008 [ 370.392488] Call trace: [
[Bug 2062380] [NEW] Using a 6.8 kernel modprobe nvidia hangs on Grace Hopper
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 [ 382.955683] rcu: hardirqs softirqs csw/system [ 382.961378] rcu: number:0 00 [ 382.967071] rcu: cputime:0 00 ==> 30026(ms) [ 382.974189] rcu: (detected by 52, t=60034 jiffies, g=24469, q=1199 ncpus=72) [ 392.982095] rcu: rcu_preempt kthread starved for 9994 jiffies! g24469 f0x0 RCU_GP_DOING_FQS(6) ->state=0x0 ->cpu=31 [ 392.992769] rcu: Unless rcu_preempt kthread gets sufficient CPU time, OOM is now expected behavior After seeing this, I Enabled kdump and set kernel.panic_on_rcu_stall = 1 KDUMP INFO WARNING: cpu 54: cannot find NT_PRSTATUS note KERNEL: /usr/lib/debug/boot/vmlinux-6.8.0-1004-nvidia-64k [TAINTED] DUMPFILE: /var/crash/202404172139/dump.202404172139 [PARTIAL DUMP] CPUS: 72 DATE: Wed Apr 17 21:39:13 UTC 2024 UPTIME: 00:06:10 LOAD AVERAGE: 0.68, 0.63, 0.28 TASKS: 854 NODENAME: hinyari RELEASE: 6.8.0-1005-nvidia-64k VERSION: #5-Ubuntu SMP PREEMPT_DYNAMIC Wed Apr 17 11:26:46 UTC 2024 MACHINE: aarch64 (unknown Mhz) MEMORY: 479.7 GB PANIC: "Kernel panic - not syncing: RCU Stall" PID: 0 COMMAND: "swapper/21" TASK: 82026880 (1 of 72) [THREAD_INFO: 82026880] CPU: 21 STATE: TASK_RUNNING (PANIC) [ 300.313144] nvidia: loading out-of-tree module taints kernel. [ 300.313153] nvidia: module verification failed: signature and/or required key missing - tainting kernel [ 300.316694] nvidia-nvlink: Nvlink Core is being initialized, major device number 506 [ 300.316699] [ 360.323454] rcu: INFO: rcu_preempt detected stalls on CPUs/tasks: [ 360.331206] rcu: 54-...0: (24 ticks this GP) idle=742c/1/0x4000 softirq=4931/4933 fqs=13148 [ 360.340903] rcu: hardirqs softirqs csw/system [ 360.346597] rcu: number:0 00 [ 360.352291] rcu: cputime:0 00 ==> 30031(ms) [ 360.359408] rcu: (detected by 21, t=60038 jiffies, g=25009, q=1123 ncpus=72) [ 360.366704] Sending NMI from CPU 21 to CPUs 54: [ 370.367310] rcu: rcu_preempt kthread starved for 9993 jiffies! g25009 f0x0 RCU_GP_DOING_FQS(6) ->state=0x0 ->cpu=31 [ 370.377983] rcu: Unless rcu_preempt kthread gets sufficient CPU time, OOM is now expected behavior. [ 370.387322] rcu: RCU grace-period kthread stack dump: [ 370.392482] task:rcu_preempt state:I stack:0 pid:17tgid:17 ppid:2 flags:0x0008 [ 370.392488] Call trace: [ 370.392489] __switch_to+0xd0/0x118 [ 370.392499] __schedule+0x2a8/0x7b0 [ 370.392501] schedule+0x40/0x168 [ 370.392502] schedule_timeout+0xac/0x1e0 [ 370.392505] rcu_gp_fqs_loop+0x128/0x508 [ 370.392512] rcu_gp_kthread+0x150/0x188 [ 370.392514] kthread+0xf8/0x110 [ 370.392519] ret_from_fork+0x10/0x20 [ 370.392524] rcu: Stack dump where RCU GP kthread last ran: [ 370.398128] Sending NMI from CPU 21 to CPUs 31: [ 370.398131] NMI backtrace for cpu 31 [ 370.398136] CPU: 31 PID: 0 Comm: swapper/31 Kdump: loaded Tainted: G OE 6.8.0-1005-nvidia-64k #5-Ubuntu [ 370.398139] Hardware name: /P3880, BIOS 01.02.01 20240207 [ 370.398140] pstate: 6349 (nZCv daif +PAN -UAO +TCO +DIT -SSBS BTYPE=--) [ 370.398142] pc : cpuidle_enter_state+0xd8/0x790 [ 370.398150] lr : cpuidle_enter_state+0xcc/0x790 [ 370.398153] sp : 800081eefd70 [ 370.398154] x29: 800081eefd70 x28: x27: [ 370.398157] x26: x25: 00563d67e4e0 x24: [ 370.398160] x23: a0a1445699f8 x22: x21: 00563d72ece0 [ 370.398162] x20: a0a144569a10 x19: 8fa4a800 x18: 800081f00030 [ 370.398165] x17: x16: x15: ac8c73b08db0 [ 370.398168] x14: x13: x12: [ 370.398170] x11: x10: 2da0fbe3d5e8c649 x9 : a0a1424fd244 [ 370.398173] x8 : 820559b8 x7 : x6 : [ 370.398175] x5 : x4 : x3 : [ 370.398178] x2 : x1 : x0 : [ 370.398181] Call trace: [ 370.398183] cpuidle_enter_state+0xd8/0x790 [ 370.398185] cpuidle_enter+0x44/0x78 [ 370.398195] cpuidle_idle_call+0x15c/0x210 [ 370.398202] do_idle+0xb0/0x130 [ 370.398204] cpu_startup_entry+0x40/0x50 [ 370.398206] secondary_start_kernel+0xec/0x130 [ 370.398211] __secondary_switched+0xc0/0xc8 [ 370.399132] Kernel panic - not syncing: RCU Stall [ 370.403938] CPU: 21 PID: 0 Comm:
[Bug 2055712] Re: Pull-request to address bug in mm/page_alloc.c
** 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: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-6.5/+bug/2055712/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055712] Re: Pull-request to address bug in mm/page_alloc.c
** 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-6.5/+bug/2055712/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059150] Re: jammy/linux-nvidia-6.5: 6.5.0-1014.14 - Boot failure on Quanta Grace/Hopper
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 Vendor: NVIDIA Version: 01.02.01 Release Date: 20240207 ROM Size: 64 MB Characteristics: PCI is supported PNP is supported BIOS is upgradeable BIOS shadowing is allowed Boot from CD is supported Selectable boot is supported Serial services are supported (int 14h) ACPI is supported Targeted content distribution is supported UEFI is supported Firmware Revision: 0.0 ** Changed in: linux-nvidia-6.5 (Ubuntu) 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/2059150 Title: jammy/linux-nvidia-6.5: 6.5.0-1014.14 - Boot failure on Quanta Grace/Hopper To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-6.5/+bug/2059150/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059150] [NEW] jammy/linux-nvidia-6.5: 6.5.0-1014.14 - Boot failure on Quanta Grace/Hopper
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 = 0x x7 = 0x x8 = 0x x9 = 0xa0e0a03e7d6c x10= 0x x11= 0x x12= 0x x13= 0x x14= 0x x15= 0x x16= 0x x17= 0x x18= 0x x19= 0xf0f18080 x20= 0x80009e86f6a0 x21= 0x80009e86f720 x22= 0x07a5a0e0a03e7d6c x23= 0x x24= 0xa0e0a3348aa0 x25= 0xa0e0a2990008 x26= 0xa0e0a2990008 x27= 0xa0e04b4f5748 x28= 0x80009e86f710 x29= 0x80008000fe00 x30= 0xa0e0a03e7d6c scr_el3= 0x0407073d sctlr_el3 = 0x30cd183f cptr_el3 = 0x00100100 tcr_el3= 0x80853510 daif = 0x02c0 mair_el3 = 0x004404ff spsr_el3 = 0x034000c9 elr_el3= 0xa0e04b4f58b4 ttbr0_el3 = 0x0078734a5001 esr_el3= 0x622c5c1f far_el3= 0x9446dd42099e8148 spsr_el1 = 0x elr_el1= 0x spsr_abt = 0x spsr_und = 0x spsr_irq = 0x spsr_fiq = 0x sctlr_el1 = 0x30d00980 actlr_el1 = 0x cpacr_el1 = 0x0030 csselr_el1 = 0x0002 sp_el1 = 0x esr_el1= 0x ttbr0_el1 = 0x ttbr1_el1 = 0x mair_el1 = 0x amair_el1 = 0x tcr_el1= 0x tpidr_el1 = 0x tpidr_el0 = 0x8000 tpidrro_el0= 0x par_el1= 0x0800 mpidr_el1 = 0x8102 afsr0_el1 = 0x afsr1_el1 = 0x contextidr_el1 = 0x vbar_el1 = 0x cntp_ctl_el0 = 0x cntp_cval_el0 = 0x0012ec91c420 cntv_ctl_el0 = 0x cntv_cval_el0 = 0x cntkctl_el1= 0x sp_el0 = 0x0078732cf4f0 isr_el1= 0x0040 cpuectlr_el1 = 0x4000340340003000 gicd_ispendr regs (Offsets 0x200 - 0x278) Offset:value 0200: 0xUnhandled Exception in EL3. x30= 0x0078732c4384 x0 = 0x x1 = 0x0078732cb7d8 x2 = 0x0018 x3 = 0x0078732b1720 x4 = 0x x5 = 0x003c x6 = 0x0078732c9109 x7 = 0x22000204 x8 = 0x4000340340003000 x9 = 0x x10= 0x x11= 0x0012ec91c420 x12= 0x x13= 0x x14= 0x x15= 0x0078732cf4f0 x16= 0x2200 x17= 0x0018 x18= 0x0407073d x19= 0x007873386440 x20= 0x80009e86f6a0 x21= 0x80009e86f720 x22= 0x07a5a0e0a03e7d6c x23= 0x x24= 0xa0e0a3348aa0 x25= 0xa0e0a2990008 x26= 0xa0e0a2990008 x27= 0xa0e04b4f5748 x28= 0x80009e86f710 x29= 0x80008000fe00 scr_el3= 0x0407073d sctlr_el3 = 0x30cd183f cptr_el3 = 0x00100100 tcr_el3= 0x80853510 daif = 0x03c0 mair_el3 = 0x004404ff spsr_el3 = 0x834002cd elr_el3= 0x0078732b0af4 ttbr0_el3 = 0x0078734a5001 esr_el3= 0xbe11 far_el3= 0x9446dd42099e8148 spsr_el1 = 0x elr_el1= 0x spsr_abt = 0x spsr_und = 0x spsr_irq = 0x spsr_fiq = 0x sctlr_el1 = 0x30d00980 actlr_el1 = 0x cpacr_el1 = 0x0030 csselr_el1 = 0x0002 sp_el1 = 0x esr_el1= 0x ttbr0_el1 = 0x ttbr1_el1 = 0x mair_el1 =
[Bug 1976425] [NEW] Release of nvidia-graphics-drivers 515.48.07 for Bionic, Focal, Impish, Jammy, Kinetic
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 followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. Nvidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Changelog] RELEASE HIGHLIGHTS Published the source code to a variant of the NVIDIA Linux kernel modules dual-licensed as MIT/GPLv2. The source is available here: https://github.com/NVIDIA/open-gpu-kernel-modules and will be updated each driver release. Please see the "Open Linux Kernel Modules" chapter in the README for details. Added support for the VK_EXT_external_memory_dma_buf and VK_EXT_image_drm_format_modifier Vulkan extensions. To use this functionality, the nvidia-drm kernel module must be loaded with DRM KMS mode setting enabled. See the DRM KMS section of the README for guidance on enabling mode setting. Changed nvidia-suspend.service, nvidia-resume.service, and nvidia-hibernate.service to use WantedBy= rather than RequiredBy= dependencies for systemd-suspend.service and systemd-hibernate.service. This avoids a problem where suspend or hibernate fails if the NVIDIA driver is uninstalled without disabling these services first. See https://github.com/systemd/systemd/issues/21991 If these services were manually enabled, it may be necessary to update their dependencies by running sudo systemctl reenable nvidia-suspend.service nvidia-resume.service nvidia-hibernate.service Interlaced modes are now disabled when active stereo is enabled. NVIDIA X Server Settings will now display the quit confirmation dialog automatically if only there are pending changes that need to be manually saved. The corresponding configuration option to control the appearance of the quit dialog was thus also removed. Removed the warning message about mismatches between the compiler used to build the Linux kernel and the compiler used to build the NVIDIA kernel modules from nvidia-installer. Modern compilers are less likely to cause problems when this type of mismatch occurs, and it has become common in many distributions to build the Linux kernel with a different compiler than the default system compiler. Updated nvidia-installer to skip test-loading the kernel modules on systems where no supported NVIDIA GPUs are detected. Updated nvidia-installer to avoid a race condition which could cause the kernel module test load to fail due to udev automatically loading kernel modules left over from an existing NVIDIA driver installation. This failure resulted in an installation error message "Kernel module load error: File exists". Updated the RTD3 Video Memory Utilization Threshold (NVreg_DynamicPowerManagementVideoMemoryThreshold) maximum value from 200 MB to 1024 MB. Improved performance of GLX and Vulkan applications running in gamescope. Added a "kernelopen" feature tag to the supported-gpus.json file, to indicate which GPUs are compatible with open-gpu-kernel-modules. Improved Vulkan swapchain creation failure reporting. Applications can use the VK_EXT_debug_utils extension to receive additional information when an error was encountered in vkCreateSwapchainKHR(). Added a new configuration option for NVIDIA NGX to allow disabling the DSO signature check. See the "NGX" chapter of the README for more information. Fixed an issue where HDMI audio output was not working in some cases, especially with high display refresh rates (120Hz, 100Hz, etc.) using Fixed Rate Link (FRL) transmission mode. ** Affects: linux-restricted-modules (Ubuntu) Importance: Undecided Status: New ** Affects: linux-restricted-modules (Ubuntu Bionic) Importance: Undecided Status: New ** Affects: linux-restricted-modules (Ubuntu Focal) Importance: Undecided Status: New ** Affects: linux-restricted-modules (Ubuntu Impish) Importance: Undecided Status: New ** Affects: linux-restricted-modules (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: linux-restricted-modules (Ubuntu Kinetic) Importance: Undecided Status: New ** Description changed: + RELEASE HIGHLIGHTS + Published the source code to a variant of the NVIDIA Linux kernel modules dual-licensed as MIT/GPLv2. The source is available here: https://github.com/NVIDIA/open-gpu-kernel-modules and will be updated each driver release. Please
[Bug 1975509] Re: Update to the 510.73.08 ERD NVIDIA driver series in Bionic, Focal, Impish, Jammy, and Kinetic
** 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://bugs.launchpad.net/bugs/1975509 Title: Update to the 510.73.08 ERD NVIDIA driver series in Bionic, Focal, Impish, Jammy, and Kinetic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fabric-manager-510/+bug/1975509/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975509] Re: Update to the 510.73.08 ERD NVIDIA driver series in Bionic, Focal, Impish, Jammy, and Kinetic
** 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: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975509 Title: Update to the 510.73.08 ERD NVIDIA driver series in Bionic, Focal, Impish, Jammy, and Kinetic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1975509/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975509] Re: Update to the 510.73.08 ERD NVIDIA driver series in Bionic, Focal, Impish, Jammy, and Kinetic
** 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 SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] + === 510 kinetic/jammy/impish/focal/bionic === - When calculating the address of grid barrier allocated for a CUDA - stream, there was an off-by-one error. The address calculation is - corrected in this release. - - An issue that caused an AC cycle test to fail with "AssertionError: NVLink links with inappropriate status found" is resolved. - An issue that caused NX 11 to become nonresponsive during a graphics operation is resolved. - - Linking issues were observed when using libnvfm.so. Now and other depend tools use dynamic linking with libstdc++ and libgcc. - An intermittent error CUDA_ERROR_NVLINK_UNCORRECTABLE caused by some non-fatal nvlink interrupts is resolved. + * New upstream release (LP: #1975509): + - When calculating the address of grid barrier allocated for a CUDA + stream, there was an off-by-one error. The address calculation is + corrected in thisrelease. + - An issue that caused an AC cycle test to fail with "AssertionError: + NVLink links with inappropriate status found" is resolved. + - An issue that caused NX 11 to become nonresponsive during a graphics + operation is resolved. + - Linking issues were observed when using libnvfm.so. Now and other + depend tools use dynamic linking with libstdc++ and libgcc. + - An intermittent error CUDA_ERROR_NVLINK_UNCORRECTABLE caused by some + non-fatal nvlink interrupts is resolved. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975509 Title: Update to the 510.73.08 ERD NVIDIA driver series in Bionic, Focal, Impish, Jammy, and Kinetic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1975509/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975509] Re: Update to the 510.73.08 ERD NVIDIA driver series in Bionic, Focal, Impish, Jammy, and Kinetic
** 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 Impish) Assignee: (unassigned) => Ian May (ian-may) ** Changed in: nvidia-graphics-drivers-510-server (Ubuntu Jammy) Assignee: (unassigned) => Ian May (ian-may) ** Changed in: nvidia-graphics-drivers-510-server (Ubuntu Kinetic) Assignee: (unassigned) => Ian May (ian-may) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975509 Title: Update to the 510.73.08 ERD NVIDIA driver series in Bionic, Focal, Impish, Jammy, and Kinetic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1975509/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975509] [NEW] Update to the 510.73.08 ERD NVIDIA driver series in Bionic, Focal, Impish, Jammy, and Kinetic
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 followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] When calculating the address of grid barrier allocated for a CUDA stream, there was an off-by-one error. The address calculation is corrected in this release. An issue that caused an AC cycle test to fail with "AssertionError: NVLink links with inappropriate status found" is resolved. An issue that caused NX 11 to become nonresponsive during a graphics operation is resolved. Linking issues were observed when using libnvfm.so. Now and other depend tools use dynamic linking with libstdc++ and libgcc. An intermittent error CUDA_ERROR_NVLINK_UNCORRECTABLE caused by some non-fatal nvlink interrupts is resolved. ** Affects: linux-restricted-modules (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: nvidia-graphics-drivers-510-server (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux-restricted-modules (Ubuntu Bionic) Importance: Undecided Status: Confirmed ** Affects: nvidia-graphics-drivers-510-server (Ubuntu Bionic) Importance: Undecided Status: Confirmed ** Affects: linux-restricted-modules (Ubuntu Focal) Importance: Undecided Status: Confirmed ** Affects: nvidia-graphics-drivers-510-server (Ubuntu Focal) Importance: Undecided Status: Confirmed ** Affects: linux-restricted-modules (Ubuntu Impish) Importance: Undecided Status: Confirmed ** Affects: nvidia-graphics-drivers-510-server (Ubuntu Impish) Importance: Undecided Status: Confirmed ** Affects: linux-restricted-modules (Ubuntu Jammy) Importance: Undecided Status: Confirmed ** Affects: nvidia-graphics-drivers-510-server (Ubuntu Jammy) Importance: Undecided Status: Confirmed ** Affects: linux-restricted-modules (Ubuntu Kinetic) Importance: Undecided Status: Confirmed ** Affects: nvidia-graphics-drivers-510-server (Ubuntu Kinetic) Importance: Undecided Status: Confirmed ** Also affects: nvidia-graphics-drivers-510-server (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-510-server (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-510-server (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-510-server (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-510-server (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux-restricted-modules (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-restricted-modules (Ubuntu Bionic) Status: New => Confirmed ** Changed in: linux-restricted-modules (Ubuntu Focal) Status: New => Confirmed ** Changed in: linux-restricted-modules (Ubuntu Impish) Status: New => Confirmed ** Changed in: linux-restricted-modules (Ubuntu Jammy) Status: New => Confirmed ** Changed in: linux-restricted-modules (Ubuntu Kinetic) Status: New => Confirmed ** Changed in: nvidia-graphics-drivers-510-server (Ubuntu Bionic) Status: New => Confirmed ** Changed in: nvidia-graphics-drivers-510-server (Ubuntu Focal) Status: New => Confirmed ** Changed in: nvidia-graphics-drivers-510-server (Ubuntu Impish) Status: New => Confirmed ** Changed in: nvidia-graphics-drivers-510-server (Ubuntu Jammy) Status: New => Confirmed ** Changed in: nvidia-graphics-drivers-510-server (Ubuntu Kinetic) Status: New => Confirmed ** No longer affects: linux-restricted-modules (Ubuntu Kinetic) ** No longer affects: nvidia-graphics-drivers-510-server (Ubuntu Kinetic) ** Also affects: linux-restricted-modules (Ubuntu Kinetic) Importance: Undecided Status: Confirmed ** Also affects: nvidia-graphics-drivers-510-server (Ubuntu Kinetic) Importance: Undecided Status: Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975509 Title: Update to the 510.73.08 ERD
[Bug 1970798] Re: 32 GT/s PCI link speeds reporting "Unknown speed" in sysfs
** 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 32 GT/s and is available in the 5.4 kernel, but the patches for properly reporting speeds in sysfs are missing. The - following upstream patches add the reporting capability. + following upstream v5.7 patches add the reporting capability. - https://lore.kernel.org/linux- - pci/20200229030706.17835-1-helg...@kernel.org/ + PCI ML submission + https://lore.kernel.org/linux-pci/20200229030706.17835-1-helg...@kernel.org/ + + Upstream Patches + https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=9cb3985af63555810bb07de50acdf4170771451d + + https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=e56faff57f0b39661093c00e0262d4ab9088830e + + https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=6348a34dcb98d8e285685a205f2a601817fa2d38 + + https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=757bfaa2c3515803dde9a6728bbf8c8a3c5f098a + [Test Plan] Testing these speeds requires special hardware. A Test kernel with these patches applied was provided to the customer and they confirmed the proper numbers are reported. [Where problems could occur] Changes are for reporting info so chance of problems should be low. If a problem did occur it would be with sysfs or pcie driver misreporting speeds. [Other] SF-00333784 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970798 Title: 32 GT/s PCI link speeds reporting "Unknown speed" in sysfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970798/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970798] Re: 32 GT/s PCI link speeds reporting "Unknown speed" in sysfs
** 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 32 GT/s and is available in the 5.4 kernel, but the patches for properly reporting speeds in sysfs are missing. The following upstream patches add the reporting capability. https://lore.kernel.org/linux- pci/20200229030706.17835-1-helg...@kernel.org/ [Test Plan] Testing these speeds requires special hardware. A Test kernel with these patches applied was provided to the customer and they confirmed the proper numbers are reported. [Where problems could occur] Changes are for reporting info so chance of problems should be low. If - a problem did occur it would be with sysfs or pcie driver. + a problem did occur it would be with sysfs or pcie driver misreporting + speeds. [Other] SF-00333784 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970798 Title: 32 GT/s PCI link speeds reporting "Unknown speed" in sysfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970798/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970798] Re: 32 GT/s PCI link speeds reporting "Unknown speed" in sysfs
** 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 32 GT/s and is available in the 5.4 kernel, but the patches for properly reporting speeds in sysfs are missing. The following upstream patches add the reporting capability. https://lore.kernel.org/linux- pci/20200229030706.17835-1-helg...@kernel.org/ [Test Plan] Testing these speeds requires special hardware. A Test kernel with these patches applied was provided to the customer and they confirmed the proper numbers are reported. [Where problems could occur] Changes are for reporting info so chance of problems should be low. If a problem did occur it would be with sysfs or pcie driver. + + [Other] + SF00333784 ** 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 32 GT/s and is available in the 5.4 kernel, but the patches for properly reporting speeds in sysfs are missing. The following upstream patches add the reporting capability. https://lore.kernel.org/linux- pci/20200229030706.17835-1-helg...@kernel.org/ [Test Plan] Testing these speeds requires special hardware. A Test kernel with these patches applied was provided to the customer and they confirmed the proper numbers are reported. [Where problems could occur] Changes are for reporting info so chance of problems should be low. If a problem did occur it would be with sysfs or pcie driver. [Other] + SF00333784 ** 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 32 GT/s and is available in the 5.4 kernel, but the patches for properly reporting speeds in sysfs are missing. The following upstream patches add the reporting capability. https://lore.kernel.org/linux- pci/20200229030706.17835-1-helg...@kernel.org/ [Test Plan] Testing these speeds requires special hardware. A Test kernel with these patches applied was provided to the customer and they confirmed the proper numbers are reported. [Where problems could occur] Changes are for reporting info so chance of problems should be low. If a problem did occur it would be with sysfs or pcie driver. [Other] - SF00333784 + SF-00333784 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970798 Title: 32 GT/s PCI link speeds reporting "Unknown speed" in sysfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970798/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970798] Re: 32 GT/s PCI link speeds reporting "Unknown speed" in sysfs
** 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 + performance statistics. Users have reported entries showing "Unknown + speed" when they should be reporting "32 GT/s". - The 5.4 kernel is missing the following commit: - https://lore.kernel.org/all/1581937984-40353-2-git-send-email- - yangyic...@hisilicon.com/ + Example: + "" + + PCIe 5.0 which supports 32 GT/s is available in the 5.4 kernel, but the + patches for properly reporting speeds in sysfs are missing. The + following upstream patches add the reporting capability. + + https://lore.kernel.org/linux- + pci/20200229030706.17835-1-helg...@kernel.org/ + + + [Test Plan] + + Testing these speeds requires special hardware. A Test kernel with these + patches applied was provided to the customer and they confirmed the + proper numbers are reported. + + + [Where problems could occur] + + Changes are for reporting info so chance of problems should be low. If + a problem did occur it would be with sysfs or pcie driver. ** Changed in: linux (Ubuntu Focal) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: linux (Ubuntu Focal) Importance: Undecided => High ** 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 which supports 32 GT/s is available in the 5.4 kernel, but the patches for properly reporting speeds in sysfs are missing. The following upstream patches add the reporting capability. https://lore.kernel.org/linux- pci/20200229030706.17835-1-helg...@kernel.org/ - [Test Plan] Testing these speeds requires special hardware. A Test kernel with these patches applied was provided to the customer and they confirmed the proper numbers are reported. - [Where problems could occur] Changes are for reporting info so chance of problems should be low. If a problem did occur it would be with sysfs or pcie driver. ** 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 which supports 32 GT/s is available in the 5.4 kernel, but the + PCIe 5.0 supports 32 GT/s and is available in the 5.4 kernel, but the patches for properly reporting speeds in sysfs are missing. The following upstream patches add the reporting capability. https://lore.kernel.org/linux- pci/20200229030706.17835-1-helg...@kernel.org/ [Test Plan] Testing these speeds requires special hardware. A Test kernel with these patches applied was provided to the customer and they confirmed the proper numbers are reported. [Where problems could occur] Changes are for reporting info so chance of problems should be low. If a problem did occur it would be with sysfs or pcie driver. ** Changed in: linux (Ubuntu) Importance: High => Medium ** Changed in: linux (Ubuntu Focal) Importance: High => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970798 Title: 32 GT/s PCI link speeds reporting "Unknown speed" in sysfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970798/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970798] [NEW] 32 GT/s PCI link speeds reporting "Unknown speed" in sysfs
Public bug reported:
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:
The 5.4 kernel is missing the following commit:
https://lore.kernel.org/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
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Ian May (ian-may)
** Changed in: linux (Ubuntu Focal)
Assignee: (unassigned) => Ian May (ian-may)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1970798
Title:
32 GT/s PCI link speeds reporting "Unknown speed" in sysfs
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970798/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970451] Re: Update to the 510.68.02 UDA NVIDIA driver series in Bionic, Focal, Impish, and Jammy
** 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 Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970451 Title: Update to the 510.68.02 UDA NVIDIA driver series in Bionic, Focal, Impish, and Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1970451/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970451] Re: Update to the 510.68.02 UDA NVIDIA driver series in Bionic, Focal, Impish, and Jammy
** 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 SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] + + [Changelog] + + === 510 jammy/impish/focal/bionic === + + * New upstream release (LP: #1970451): + - Fixed an issue where NvFBC was requesting Vulkan 1.0 while using + Vulkan 1.1 core features. This caused NvFBC to fail to initialize + with Vulkan loader versions 1.3.204 or newer. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970451 Title: Update to the 510.68.02 UDA NVIDIA driver series in Bionic, Focal, Impish, and Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1970451/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970451] Re: Update to the 510.68.02 UDA NVIDIA driver series in Bionic, Focal, Impish, and Jammy
** 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 Status: New ** Also affects: nvidia-graphics-drivers-510 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-restricted-modules (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-510 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-restricted-modules (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-510 (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970451 Title: Update to the 510.68.02 UDA NVIDIA driver series in Bionic, Focal, Impish, and Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1970451/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970451] [NEW] Update to the 510.68.02 UDA NVIDIA driver series in Bionic, Focal, Impish, and Jammy
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 followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] ** Affects: linux-restricted-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) ** Changed in: linux-restricted-modules (Ubuntu) Assignee: (unassigned) => Ian May (ian-may) ** Also affects: nvidia-graphics-drivers-510 (Ubuntu) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-510 (Ubuntu) Assignee: (unassigned) => Ian May (ian-may) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970451 Title: Update to the 510.68.02 UDA NVIDIA driver series in Bionic, Focal, Impish, and Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1970451/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959216] Re: linux-azure: CONFIG_FB_EFI=y
-- 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/1959216/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959216] Re: linux-azure: CONFIG_FB_EFI=y
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: verification-needed-impish ** Tags added: verification-done-impish -- 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/1959216/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960871] Re: linux-modules-extra-* fails to install due to dependency on unsigned package
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://bugs.launchpad.net/bugs/1960871 Title: linux-modules-extra-* fails to install due to dependency on unsigned package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1960871/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871015] Re: test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed with H (Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL])
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 (Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL]) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1871015/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923104] Re: Include Infiniband Peer Memory interface
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.net/bugs/1923104 Title: Include Infiniband Peer Memory interface To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1923104/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958534] Re: building of linux-signed package failing on arm64
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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-aws/+bug/1958534/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958534] Re: building of linux-signed package failing on arm64
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 (Ubuntu Bionic) Assignee: (unassigned) => Ian May (ian-may) ** Changed in: linux-signed-aws (Ubuntu) Status: New => Fix Committed ** Changed in: linux-signed-aws (Ubuntu Bionic) Status: New => Fix Committed -- 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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-aws/+bug/1958534/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958534] [NEW] building of linux-signed package failing on arm64
ot;; \ \ package="kernel-signed-image-$verflav-di"; \ echo "$package: adding $signed";\ echo "$signed boot" >>"debian/$package.install";\ \ package="linux-image-$verflav"; \ echo "$package: adding $signed";\ echo "$signed boot" >>"debian/$package.install";\ \ ./generate-depends linux-image-unsigned-$verflav 4.15.0-1119.126 \ linux-image-$verflav\ >>"debian/linux-image-$verflav.substvars"; \ \ for which in postinst postrm preinst prerm; do \ template="debian/templates/image.$which.in";\ script="debian/$package.$which";\ sed -e "s/@abiname@/4.15.0-1119/g" \ -e "s/@localversion@/-$flavour/g" \ -e "s/@image-stem@/$instfile/g" \ <"$template" >"$script";\ done; \ echo "interest linux-update-4.15.0-1119-$flavour" \ >"debian/$package.triggers";\ done kernel-signed-image-4.15.0-1119-SIGNED/*-di: adding SIGNED/* /bin/sh: 8: cannot create debian/kernel-signed-image-4.15.0-1119-SIGNED/*-di.install: Directory nonexistent linux-image-4.15.0-1119-SIGNED/*: adding SIGNED/* /bin/sh: 12: cannot create debian/linux-image-4.15.0-1119-SIGNED/*.install: Directory nonexistent /bin/sh: 14: cannot create debian/linux-image-4.15.0-1119-SIGNED/*.substvars: Directory nonexistent /bin/sh: 21: 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 create debian/linux-image-4.15.0-1119-SIGNED/*.prerm: Directory nonexistent /bin/sh: 26: cannot create debian/linux-image-4.15.0-1119-SIGNED/*.triggers: Directory nonexistent debian/rules:81: recipe for target 'override_dh_auto_install' failed make[1]: *** [override_dh_auto_install] Error 2 make[1]: Leaving directory '/<>' debian/rules:45: recipe for target 'binary-arch' failed make: *** [binary-arch] Error 2 dpkg-buildpackage: error: fakeroot debian/rules binary-arch subprocess returned exit status 2 ** Affects: linux-signed-aws (Ubuntu) Importance: Undecided Assignee: Ian May (ian-may) Status: Fix Committed ** Affects: linux-signed-aws (Ubuntu Bionic) Importance: Undecided Assignee: Ian May (ian-may) Status: Fix Committed ** Also affects: linux-signed-aws (Ubuntu Bionic) Importance: Undecided Status: New -- 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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-aws/+bug/1958534/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958534] Re: building of linux-signed package failing on arm64
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 of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958534 Title: building of linux-signed package failing on arm64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-aws/+bug/1958534/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949532] Re: ubuntu_ltp_controllers tests failing on Impish
** 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: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1949532/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949532] Re: ubuntu_ltp_controllers tests failing on Impish
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: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1949532/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949532] Re: ubuntu_ltp_controllers tests failing on Impish
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: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1949532/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938908] Re: Backport the container stack in Impish
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 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938908 Title: Backport the container stack in Impish To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/containerd/+bug/1938908/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1948361] Re: docker.io - error adding seccomp filter rule for syscall clone3
** 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: starting container process caused: error adding seccomp filter rule for syscall clone3: permission denied: unknown." This test essentially pulls down a nvidia tensorflow docker container, runs the container and triggers the preloaded tests while capturing the output as results. The failure is seen with the following version of docker.io Version: 20.10.7-0ubuntu5~20.04.1 APT-Sources: http://archive.ubuntu.com/ubuntu focal-proposed/universe amd64 Packages Using the focal-updates docker.io the failure cannot be reproduced Version: 20.10.7-0ubuntu1~20.04.2 APT-Sources: http://archive.ubuntu.com/ubuntu focal-updates/universe amd64 Packages + To reproduce: - To reproduce: - + enable focal-proposed + git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest - + ln -sf ~/autotest-client-tests autotest/client/tests - - AUTOTEST_PATH=/home/ubuntu/autotest sudo -E autotest/client/autotest-local --verbose autotest/client/tests/ubuntu_performance_deep_learning/control + + AUTOTEST_PATH=/home/ubuntu/autotest sudo -E autotest/client/autotest- + local --verbose + autotest/client/tests/ubuntu_performance_deep_learning/control -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1948361 Title: docker.io - error adding seccomp filter rule for syscall clone3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1948361/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1948361] [NEW] docker.io - error adding seccomp filter rule for syscall clone3
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 container process caused: error adding seccomp filter rule for syscall clone3: permission denied: unknown." This test essentially pulls down a nvidia tensorflow docker container, runs the container and triggers the preloaded tests while capturing the output as results. The failure is seen with the following version of docker.io Version: 20.10.7-0ubuntu5~20.04.1 APT-Sources: http://archive.ubuntu.com/ubuntu focal-proposed/universe amd64 Packages Using the focal-updates docker.io the failure cannot be reproduced Version: 20.10.7-0ubuntu1~20.04.2 APT-Sources: http://archive.ubuntu.com/ubuntu focal-updates/universe amd64 Packages To reproduce: git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest ln -sf ~/autotest-client-tests autotest/client/tests AUTOTEST_PATH=/home/ubuntu/autotest sudo -E autotest/client/autotest-local --verbose autotest/client/tests/ubuntu_performance_deep_learning/control ** Affects: docker.io (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1948361 Title: docker.io - error adding seccomp filter rule for syscall clone3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1948361/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946149] Re: Bionic/linux-aws Boot failure downgrading from Bionic/linux-aws-5.4 on r5.metal
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, let it sit idle for 20 minutes and then install the known problematic 4.15.0-1113-aws kernel. Sure enough it booted fine. Tried the same thing again with letting it sit idle 20 mins and it worked again. So this does appear to be a race condition. I think this also explains some of the erratic test results I've seen while looking at this bug. Fortunately the console output gave us some definitive proof as to where the problem was occurring. With that being said, it appears I have found the offending commits. PCI/MSI: Enforce that MSI-X table entry is masked for update PCI/MSI: Enforce MSI[X] entry updates to be visible https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux- aws/+git/bionic/commit/?id=27571f5ea1dd074924b41a455c50dc2278e8c2b7 https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux- aws/+git/bionic/commit/?id=2478f358c2b35fea04e005447ce99ad8dc53fd5d More specifically the hang is introduced by 'PCI/MSI: Enforce that MSI-X table entry is masked for update', but it isn't a clean revert without reverting the other commit. So for a quick test confirmation I reverted both. I have not had a chance to determine why these commits are causing the problem, but with these reverted in a test build on top of 4.15.0-1113-aws, I can migrate from 5.4 to 4.15 as soon as the instance is available. I've done at least 6 attempts now and all have passed and doing the same steps without the reverts all have hung(unless I wait 20 mins). -- 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 downgrading from Bionic/linux-aws-5.4 on r5.metal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1946149/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946149] Re: Bionic/linux-aws Boot failure downgrading from Bionic/linux-aws-5.4 on r5.metal
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946149 Title: Bionic/linux-aws Boot failure downgrading from Bionic/linux-aws-5.4 on r5.metal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1946149/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1830585] Re: cpuset_memory_spread from controllers test suite in LTP failed (hog the memory on the unexpected node)
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 (hog the memory on the unexpected node) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1830585/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876687] Re: function traceon/off triggers in ftace from ubuntu_kernel_selftests failed on B/F
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 from ubuntu_kernel_selftests failed on B/F To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1876687/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946149] Re: Bionic/linux-aws Boot failure downgrading from Bionic/linux-aws-5.4 on r5.metal
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 the most interesting. Scenario 1 start with 5.4.0-1056-aws install 5.4.0-1058-aws reboot confirm 5.4.0-1058-aws booted reboot AGAIN install 4.15.0-1113-aws reboot machine booted 4.15.0-1113-aws successfully Scenario 2 start with 5.4.0-1056-aws install 4.15.0-1112-aws reboot install 4.15.0-1113-aws reboot confirmed 4.15.0-1113-aws booted then booted back into 5.4.0-1056-aws removed 4.15.0-1112-aws and 4.15.0-1113-aws rebooted again for good measure confirmed still running 5.4.0-1056-aws installed 4.15.0-1113-aws rebooted 4.15.0-1113-aws successfully loaded -- 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 downgrading from Bionic/linux-aws-5.4 on r5.metal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1946149/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946149] Re: Bionic/linux-aws Boot failure downgrading from Bionic/linux-aws-5.4 on r5.metal
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 subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946149 Title: Bionic/linux-aws Boot failure downgrading from Bionic/linux-aws-5.4 on r5.metal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1946149/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946149] Re: Bionic/linux-aws Boot failure downgrading from Bionic/linux-aws-5.4 on r5.metal
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 downgrading from Bionic/linux-aws-5.4 on r5.metal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1946149/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946149] Re: Bionic/linux-aws Boot failure downgrading from Bionic/linux-aws-5.4 on r5.metal
** 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 kernel https://lists.ubuntu.com/archives/kernel-team/2021-September/123963.html With that being said, after successfully updating to the 4.15 without those patches applied, I can then upgrade to a 4.15 kernel with the above patches included, and the instance will boot properly. This problem only appears on metal instances, which uses NVME instead of XVDA devices. AWS instances also use the 'discard' mount option with ext4, thought maybe there could be a race condition between ext4 discard and journal - flush. Removed 'discard' mount and rebooted 5.4 kernel prior to 4.15 - kernel installation, but still wouldn't boot after installing the 4.15 - kernel. + flush. Removed 'discard' from mount options and rebooted 5.4 kernel + prior to 4.15 kernel installation, but still wouldn't boot after + installing the 4.15 kernel. I have been unable to capture a stack trace using 'aws get-console- output'. After enabling kdump I was unable to replicate the failure. So there must be some sort of race with either ext4 and/or nvme. -- 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 downgrading from Bionic/linux-aws-5.4 on r5.metal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1946149/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946149] Re: Bionic/linux-aws Boot failure downgrading from Bionic/linux-aws-5.4 on r5.metal
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/linux-aws Boot failure downgrading from Bionic/linux-aws-5.4 on r5.metal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1946149/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946149] Re: Bionic/linux-aws Boot failure downgrading from Bionic/linux-aws-5.4 on r5.metal
** 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 I remove these patches the instance correctly boots the 4.15 kernel https://lists.ubuntu.com/archives/kernel-team/2021-September/123963.html - But after successfully updating to the 4.15 without those patches - applied, I can then upgrade to a 4.15 kernel with the above patches - included, and the instance will boot properly. + With that being said, after successfully updating to the 4.15 without + those patches applied, I can then upgrade to a 4.15 kernel with the + above patches included, and the instance will boot properly. This problem only appears on metal instances, which uses NVME instead of XVDA devices. AWS instances also use the 'discard' mount option with ext4, thought maybe there could be a race condition between ext4 discard and journal flush. Removed 'discard' mount and rebooted 5.4 kernel prior to 4.15 kernel installation, but still wouldn't boot after installing the 4.15 kernel. I have been unable to capture a stack trace using 'aws get-console- output'. After enabling kdump I was unable to replicate the failure. So there must be some sort of race with either ext4 and/or nvme. -- 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 downgrading from Bionic/linux-aws-5.4 on r5.metal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1946149/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946149] Re: Bionic/linux-aws Boot failure downgrading from Bionic/linux-aws-5.4 on r5.metal
** 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 kernel https://lists.ubuntu.com/archives/kernel-team/2021-September/123963.html But after successfully updating to the 4.15 without those patches applied, I can then upgrade to a test kernel with the above patches included, and the instance will boot properly. This problem only appears on metal instances, which uses NVME instead of XVDA devices. AWS instances also use the 'discard' mount option with ext4, thought maybe there could be a race condition between ext4 discard and journal flush. Removed 'discard' mount and rebooted 5.4 kernel prior to 4.15 kernel installation, but still wouldn't boot. + + I have been unable to capture a stack trace using 'aws get-console- + output'. I enabled kdump and was unable to replicate the failure. So + there must be some sort of race with either ext4 and/or nvme. ** 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 kernel https://lists.ubuntu.com/archives/kernel-team/2021-September/123963.html But after successfully updating to the 4.15 without those patches - applied, I can then upgrade to a test kernel with the above patches + applied, I can then upgrade to a 4.15 kernel with the above patches included, and the instance will boot properly. This problem only appears on metal instances, which uses NVME instead of XVDA devices. AWS instances also use the 'discard' mount option with ext4, thought maybe there could be a race condition between ext4 discard and journal flush. Removed 'discard' mount and rebooted 5.4 kernel prior to 4.15 kernel installation, but still wouldn't boot. I have been unable to capture a stack trace using 'aws get-console- output'. I enabled kdump and was unable to replicate the failure. So there must be some sort of race with either ext4 and/or nvme. ** 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 kernel https://lists.ubuntu.com/archives/kernel-team/2021-September/123963.html But after successfully updating to the 4.15 without those patches applied, I can then upgrade to a 4.15 kernel with the above patches included, and the instance will boot properly. This problem only appears on metal instances, which uses NVME instead of XVDA devices. AWS instances also use the 'discard' mount option with ext4, thought maybe there could be a race condition between ext4 discard and journal flush. Removed 'discard' mount and rebooted 5.4 kernel prior to 4.15 - kernel installation, but still wouldn't boot. + kernel installation, but still wouldn't boot after installing the 4.15 + kernel. I have been unable to capture a stack trace using 'aws get-console- - output'. I enabled kdump and was unable to replicate the failure. So + output'. After enabling kdump I was unable to replicate the failure. So there must be some sort of race with either ext4 and/or nvme. -- 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 downgrading from Bionic/linux-aws-5.4 on r5.metal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1946149/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946149] Re: Bionic/linux-aws Boot failure downgrading from Bionic/linux-aws-5.4 on r5.metal
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. https://bugs.launchpad.net/bugs/1946149 Title: Bionic/linux-aws Boot failure downgrading from Bionic/linux-aws-5.4 on r5.metal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1946149/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946149] Re: Bionic/linux-aws Boot failure downgrading from Bionic/linux-aws-5.4 on r5.metal
** 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 kernel + + https://lists.ubuntu.com/archives/kernel-team/2021-September/123963.html + + But after successfully updating to the 4.15 without those patches + applied, I can then upgrade to a test kernel with the above patches + included, and the instance will boot properly. + + This problem only appears on metal instances, which uses NVME instead of + XVDA devices. + + AWS instances also use the 'discard' mount option with ext4, thought + maybe there could be a race condition between ext4 discard and journal + flush. Removed 'discard' mount and rebooted 5.4 kernel prior to 4.15 + kernel installation, but still wouldn't boot. -- 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 downgrading from Bionic/linux-aws-5.4 on r5.metal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1946149/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946149] [NEW] Bionic/linux-aws Boot failure downgrading from Bionic/linux-aws-5.4 on r5.metal
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 ** Package changed: ubuntu => linux-aws (Ubuntu) -- 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 downgrading from Bionic/linux-aws-5.4 on r5.metal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1946149/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1910312] Re: semctl09 from ubuntu_ltp_syscalls failed on X / F-oem-5.6 / F-oracle-5.4
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 ubuntu_ltp_syscalls failed on X / F-oem-5.6 / F-oracle-5.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1910312/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931325] Re: cfs_bandwidth01 in sched from ubuntu_ltp_stable failed on B-4.15
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 about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1931325/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940261] Re: ubuntu_seccomp 11-basic-basic_errors failure on X/oracle
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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1940261/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1932065] Re: Upstream v5.9 introduced 'module' patches that removed exported symbols
** 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: rename the licence field in struct symsearch to license modules: unexport __module_address modules: unexport __module_text_address modules: mark each_symbol_section static modules: mark find_symbol static modules: mark ref_module static [Fix] * Temporarily revert as SAUCE patches to allow customers time to make necessary changes to support eventual patch changes. [Test Plan] - * none + * Check symbols on running kernel + sudo grep -e ' ref_module' -e ' find_symbol' -e ' each_symbol_section$' -e ' __module_address' -e ' __module_text_address' /proc/kallsyms + + * Check symbols on all installed kernels + sudo grep -e ' ref_module' -e ' find_symbol' -e ' each_symbol_section$' -e ' __module_address' -e ' __module_text_address' /boot/System.map-* [Where problems could occur] * The new functionality provided by patches will be removed, since we aren't removing existing functionality the risk should be low. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1932065 Title: Upstream v5.9 introduced 'module' patches that removed exported symbols To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1932065/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
