[Kernel-packages] [Bug 2075396] [NEW] Pull request: mm: fix old/young bit handling in the faulting path of set_pte_range()
Public bug reported:
Commit 3bd786f76de2 ("mm: convert do_set_pte() to set_pte_range()")
replaced do_set_pte() with set_pte_range() and that introduced a
regression in the following faulting path of non-anonymous vmas which
caused the PTE for the faulting address to be marked as old instead of
young.
handle_pte_fault()
do_pte_missing()
do_fault()
do_read_fault() || do_cow_fault() || do_shared_fault()
finish_fault()
set_pte_range()
The polarity of prefault calculation is incorrect. This leads to prefault
being incorrectly set for the faulting address. The following check will
incorrectly mark the PTE old rather than young. On some architectures
this will cause a double fault to mark it young when the access is
retried.
if (prefault && arch_wants_old_prefaulted_pte())
entry = pte_mkold(entry);
On a subsequent fault on the same address, the faulting path will see a
non NULL vmf->pte and instead of reaching the do_pte_missing() path, PTE
will then be correctly marked young in handle_pte_fault() itself.
Due to this bug, performance degradation in the fault handling path will
be observed due to unnecessary double faulting.
** Affects: linux-nvidia (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-nvidia in Ubuntu.
https://bugs.launchpad.net/bugs/2075396
Title:
Pull request: mm: fix old/young bit handling in the faulting path of
set_pte_range()
Status in linux-nvidia package in Ubuntu:
New
Bug description:
Commit 3bd786f76de2 ("mm: convert do_set_pte() to set_pte_range()")
replaced do_set_pte() with set_pte_range() and that introduced a
regression in the following faulting path of non-anonymous vmas which
caused the PTE for the faulting address to be marked as old instead of
young.
handle_pte_fault()
do_pte_missing()
do_fault()
do_read_fault() || do_cow_fault() || do_shared_fault()
finish_fault()
set_pte_range()
The polarity of prefault calculation is incorrect. This leads to prefault
being incorrectly set for the faulting address. The following check will
incorrectly mark the PTE old rather than young. On some architectures
this will cause a double fault to mark it young when the access is
retried.
if (prefault && arch_wants_old_prefaulted_pte())
entry = pte_mkold(entry);
On a subsequent fault on the same address, the faulting path will see a
non NULL vmf->pte and instead of reaching the do_pte_missing() path, PTE
will then be correctly marked young in handle_pte_fault() itself.
Due to this bug, performance degradation in the fault handling path will
be observed due to unnecessary double faulting.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-nvidia/+bug/2075396/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2064549] [NEW] pull-request: Fixes: b2b56a163230 ("gpio: tegra186: Check GPIO pin permission before access.")
Public bug reported:
The controller has several register bits describing access control
information for a given GPIO pin. When SCR_SEC_[R|W]EN is unset, it
means we have full read/write access to all the registers for given GPIO
pin. When SCR_SEC[R|W]EN is set, it means we need to further check the
accompanying SCR_SEC_G1[R|W] bit to determine read/write access to all
the registers for given GPIO pin.
This check was previously declaring that a GPIO pin was accessible
only if either of the following conditions were met:
- SCR_SEC_REN + SCR_SEC_WEN both set
or
- SCR_SEC_REN + SCR_SEC_WEN both set and
SCR_SEC_G1R + SCR_SEC_G1W both set
Update the check to properly handle cases where only one of
SCR_SEC_REN or SCR_SEC_WEN is set.
** Affects: linux-nvidia (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-nvidia in Ubuntu.
https://bugs.launchpad.net/bugs/2064549
Title:
pull-request: Fixes: b2b56a163230 ("gpio: tegra186: Check GPIO pin
permission before access.")
Status in linux-nvidia package in Ubuntu:
New
Bug description:
The controller has several register bits describing access control
information for a given GPIO pin. When SCR_SEC_[R|W]EN is unset, it
means we have full read/write access to all the registers for given GPIO
pin. When SCR_SEC[R|W]EN is set, it means we need to further check the
accompanying SCR_SEC_G1[R|W] bit to determine read/write access to all
the registers for given GPIO pin.
This check was previously declaring that a GPIO pin was accessible
only if either of the following conditions were met:
- SCR_SEC_REN + SCR_SEC_WEN both set
or
- SCR_SEC_REN + SCR_SEC_WEN both set and
SCR_SEC_G1R + SCR_SEC_G1W both set
Update the check to properly handle cases where only one of
SCR_SEC_REN or SCR_SEC_WEN is set.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-nvidia/+bug/2064549/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2063461] [NEW] Perf-stat tool does not support ipc and ipc_rate monitoring on NVIDIA Grace system
Public bug reported: PROBLEM: While trying to monitor the ipc group for using perf-stat tool, despite it being supported, I get the following errors: $ sudo perf list | grep ipc ipc ipc_rate retired_ipc spec_ipc $ sudo -S perf stat -a -M ipc -- sudo -S stress-ng --cpu 0 -t 10s Error: The sys_perf_event_open() syscall returned with 22 (Invalid argument) for event (instructions). /bin/dmesg | grep -i perf may provide additional information. $ sudo -S perf stat -a -M ipc_rate -- sudo -S stress-ng --cpu 0 -t 10s Error: The sys_perf_event_open() syscall returned with 22 (Invalid argument) for event (instructions). /bin/dmesg | grep -i perf may provide additional information. However, I can get the groups retired_ipc and spec_ipc to work: $ sudo -S perf stat -a -M retired_ipc -- sudo -S stress-ng --cpu 0 -t 10s Value 0 contains non-numeric: ' ' Performance counter stats for 'system wide': 96,818,964 INST_RETIRED # 0.58 retired_ipc 166,601,455 CPU_CYCLES 0.013516186 seconds time elapsed $ sudo -S perf stat -a -M spec_ipc -- sudo -S stress-ng --cpu 0 -t 10s Value 0 contains non-numeric: ' ' Performance counter stats for 'system wide': 91,053,297 INST_SPEC# 0.58 spec_ipc 156,558,810 CPU_CYCLES 0.009877355 seconds time elapsed SOLUTION: Please accept the pull request which cherry-picks the following two upstream commits: d43f5491210197196458c1454f2be0eb66d3e4d1 perf vendor events arm64: Update stall_slot workaround for N2 r0p3 4473949074c35072f598bd525ae51d5455f05745 perf vendor events arm64: Update N2 and V2 metrics and events using Arm telemetry repo ** Affects: linux-nvidia-6.5 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2063461 Title: Perf-stat tool does not support ipc and ipc_rate monitoring on NVIDIA Grace system Status in linux-nvidia-6.5 package in Ubuntu: New Bug description: PROBLEM: While trying to monitor the ipc group for using perf-stat tool, despite it being supported, I get the following errors: $ sudo perf list | grep ipc ipc ipc_rate retired_ipc spec_ipc $ sudo -S perf stat -a -M ipc -- sudo -S stress-ng --cpu 0 -t 10s Error: The sys_perf_event_open() syscall returned with 22 (Invalid argument) for event (instructions). /bin/dmesg | grep -i perf may provide additional information. $ sudo -S perf stat -a -M ipc_rate -- sudo -S stress-ng --cpu 0 -t 10s Error: The sys_perf_event_open() syscall returned with 22 (Invalid argument) for event (instructions). /bin/dmesg | grep -i perf may provide additional information. However, I can get the groups retired_ipc and spec_ipc to work: $ sudo -S perf stat -a -M retired_ipc -- sudo -S stress-ng --cpu 0 -t 10s Value 0 contains non-numeric: ' ' Performance counter stats for 'system wide': 96,818,964 INST_RETIRED # 0.58 retired_ipc 166,601,455 CPU_CYCLES 0.013516186 seconds time elapsed $ sudo -S perf stat -a -M spec_ipc -- sudo -S stress-ng --cpu 0 -t 10s Value 0 contains non-numeric: ' ' Performance counter stats for 'system wide': 91,053,297 INST_SPEC# 0.58 spec_ipc 156,558,810 CPU_CYCLES 0.009877355 seconds time elapsed SOLUTION: Please accept the pull request which cherry-picks the following two upstream commits: d43f5491210197196458c1454f2be0eb66d3e4d1 perf vendor events arm64: Update stall_slot workaround for N2 r0p3 4473949074c35072f598bd525ae51d5455f05745 perf vendor events arm64: Update N2 and V2 metrics and events using Arm telemetry repo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-6.5/+bug/2063461/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2060327] [NEW] Reapply the linux-nvidia kernel config options from the 5.15 and 6.5 kernels
Public bug reported: There are a number of configuration options that were set in the 5.15. and 6.5 nvidia kernels. When the 6.8 based linux-nvidia kernel was created those config options were not brought forward. This patch set brings them into the 6.8 kernel. ** Affects: linux-nvidia (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia in Ubuntu. https://bugs.launchpad.net/bugs/2060327 Title: Reapply the linux-nvidia kernel config options from the 5.15 and 6.5 kernels Status in linux-nvidia package in Ubuntu: New Bug description: There are a number of configuration options that were set in the 5.15. and 6.5 nvidia kernels. When the 6.8 based linux-nvidia kernel was created those config options were not brought forward. This patch set brings them into the 6.8 kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia/+bug/2060327/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2059814] [NEW] Enable GDS in the 6.8 based linux-nvidia kernel
Public bug reported: GDS enables a direct data path for direct memory access (DMA) transfers between GPU memory and storage, which avoids a bounce buffer through the CPU. This direct path increases system bandwidth and decreases the latency and utilization load on the CPU. This functionality has been enabled in all previous kernel versions and needs to be in this kernel so there is no loss of functionality for users. ** Affects: linux-nvidia (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia in Ubuntu. https://bugs.launchpad.net/bugs/2059814 Title: Enable GDS in the 6.8 based linux-nvidia kernel Status in linux-nvidia package in Ubuntu: New Bug description: GDS enables a direct data path for direct memory access (DMA) transfers between GPU memory and storage, which avoids a bounce buffer through the CPU. This direct path increases system bandwidth and decreases the latency and utilization load on the CPU. This functionality has been enabled in all previous kernel versions and needs to be in this kernel so there is no loss of functionality for users. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia/+bug/2059814/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2059178] Re: Pull request to fully enable nvidia-fs NVMe support
** Changed in: linux-nvidia-6.5 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2059178 Title: Pull request to fully enable nvidia-fs NVMe support Status in linux-nvidia-6.5 package in Ubuntu: Invalid Bug description: This pull request addresses a missing patch which fully enables GDS functionality using NVMe devices. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-6.5/+bug/2059178/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2059178] [NEW] Pull request to fully enable nvidia-fs NVMe support
Public bug reported: This pull request addresses a missing patch which fully enables GDS functionality using NVMe devices. ** Affects: linux-nvidia-6.5 (Ubuntu) Importance: Undecided Status: Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2059178 Title: Pull request to fully enable nvidia-fs NVMe support Status in linux-nvidia-6.5 package in Ubuntu: Invalid Bug description: This pull request addresses a missing patch which fully enables GDS functionality using NVMe devices. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-6.5/+bug/2059178/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2056498] Re: Kernel crash in amd gpu driver
The above crash was happening with large downloads of img files or git clones of large repositories (Ubuntu kernels) over wifi. I have changed to hard wired ethernet and I've not been able to reproduce it. With Wifi it's been very reproduceable. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2056498 Title: Kernel crash in amd gpu driver Status in linux-signed-hwe-6.5 package in Ubuntu: New Bug description: Mar 7 19:07:10 ripper kernel: [9.873519] UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.5-YpKOvT/linux-hwe-6.5-6.5.0/drivers/gpu/drm/amd/amdgpu/../pm/powerplay/hwmgr/smu7_hwmgr.c:3676:4 Mar 7 19:07:10 ripper kernel: [9.873531] index 7 is out of range for type 'ATOM_Polaris_SCLK_Dependency_Record [1]' Mar 7 19:07:10 ripper kernel: [9.873538] CPU: 4 PID: 849 Comm: systemd-udevd Not tainted 6.5.0-17-generic #17~22.04.1-Ubuntu Mar 7 19:07:10 ripper kernel: [9.873542] Hardware name: LENOVO 30E1S3VV00/1046, BIOS S07KT45A 01/20/2022 Mar 7 19:07:10 ripper kernel: [9.873544] Call Trace: Mar 7 19:07:10 ripper kernel: [9.873545] Mar 7 19:07:10 ripper kernel: [9.873547] dump_stack_lvl+0x48/0x70 Mar 7 19:07:10 ripper kernel: [9.873551] dump_stack+0x10/0x20 Mar 7 19:07:10 ripper kernel: [9.873554] __ubsan_handle_out_of_bounds+0xc6/0x110 Mar 7 19:07:10 ripper kernel: [9.873560] smu7_get_pp_table_entry_callback_func_v1+0x9b7/0xa00 [amdgpu] Mar 7 19:07:10 ripper kernel: [9.873897] ? srso_return_thunk+0x5/0x10 Mar 7 19:07:10 ripper kernel: [9.873900] ? vi_pcie_rreg+0x6e/0x90 [amdgpu] Mar 7 19:07:10 ripper kernel: [9.874187] ? __pfx_smu7_get_pp_table_entry_callback_func_v1+0x10/0x10 [amdgpu] Mar 7 19:07:10 ripper kernel: [9.874515] get_powerplay_table_entry_v1_0+0xf8/0x490 [amdgpu] Mar 7 19:07:10 ripper kernel: [9.874842] smu7_get_pp_table_entry_v1+0x41/0x4c0 [amdgpu] Mar 7 19:07:10 ripper kernel: [9.875169] smu7_get_pp_table_entry+0x3d/0x50 [amdgpu] Mar 7 19:07:10 ripper kernel: [9.875495] psm_init_power_state_table+0x161/0x250 [amdgpu] Mar 7 19:07:10 ripper kernel: [9.875826] hwmgr_hw_init+0xe3/0x1e0 [amdgpu] Mar 7 19:07:10 ripper kernel: [9.876150] pp_hw_init+0x16/0x50 [amdgpu] Mar 7 19:07:10 ripper kernel: [9.876484] amdgpu_device_ip_init+0x48d/0x960 [amdgpu] Mar 7 19:07:10 ripper kernel: [9.876749] amdgpu_device_init+0x9a2/0x1150 [amdgpu] Mar 7 19:07:10 ripper kernel: [9.877014] amdgpu_driver_load_kms+0x1a/0x1c0 [amdgpu] Mar 7 19:07:10 ripper kernel: [9.877278] amdgpu_pci_probe+0x182/0x450 [amdgpu] Mar 7 19:07:10 ripper kernel: [9.877541] local_pci_probe+0x47/0xb0 Mar 7 19:07:10 ripper kernel: [9.877545] pci_call_probe+0x55/0x190 Mar 7 19:07:10 ripper kernel: [9.877550] pci_device_probe+0x84/0x120 Mar 7 19:07:10 ripper kernel: [9.877553] ? srso_return_thunk+0x5/0x10 Mar 7 19:07:10 ripper kernel: [9.877557] really_probe+0x1cc/0x430 Mar 7 19:07:10 ripper kernel: [9.877560] __driver_probe_device+0x8c/0x190 Mar 7 19:07:10 ripper kernel: [9.877563] driver_probe_device+0x24/0xd0 Mar 7 19:07:10 ripper kernel: [9.877566] __driver_attach+0x10b/0x210 Mar 7 19:07:10 ripper kernel: [9.877569] ? __pfx___driver_attach+0x10/0x10 Mar 7 19:07:10 ripper kernel: [9.877572] bus_for_each_dev+0x8d/0xf0 Mar 7 19:07:10 ripper kernel: [9.877576] driver_attach+0x1e/0x30 Mar 7 19:07:10 ripper kernel: [9.877579] bus_add_driver+0x127/0x240 Mar 7 19:07:10 ripper kernel: [9.877583] driver_register+0x5e/0x130 Mar 7 19:07:10 ripper kernel: [9.877586] ? __pfx_amdgpu_init+0x10/0x10 [amdgpu] Mar 7 19:07:10 ripper kernel: [9.877849] __pci_register_driver+0x62/0x70 Mar 7 19:07:10 ripper kernel: [9.877852] amdgpu_init+0x69/0xff0 [amdgpu] Mar 7 19:07:10 ripper kernel: [9.878111] ? srso_return_thunk+0x5/0x10 Mar 7 19:07:10 ripper kernel: [9.878114] do_one_initcall+0x5e/0x340 Mar 7 19:07:10 ripper kernel: [9.878120] do_init_module+0x68/0x260 Mar 7 19:07:10 ripper kernel: [9.878123] load_module+0xb85/0xcd0 Mar 7 19:07:10 ripper kernel: [9.878128] ? srso_return_thunk+0x5/0x10 Mar 7 19:07:10 ripper kernel: [9.878131] ? security_kernel_post_read_file+0x75/0x90 Mar 7 19:07:10 ripper kernel: [9.878136] init_module_from_file+0x96/0x100 Mar 7 19:07:10 ripper kernel: [9.878139] ? srso_return_thunk+0x5/0x10 Mar 7 19:07:10 ripper kernel: [9.878142] ? init_module_from_file+0x96/0x100 Mar 7 19:07:10 ripper kernel: [9.878149] idempotent_init_module+0x11c/0x2b0 Mar 7 19:07:10 ripper kernel: [9.878155] __x64_sys_finit_module+0x64/0xd0 Mar 7 19:07:10 ripper kernel: [9.878159] do_syscall_64+0x5b/0x90 Mar 7 19:07:10
[Kernel-packages] [Bug 2056498] [NEW] Kernel crash in amd gpu driver
Public bug reported: Mar 7 19:07:10 ripper kernel: [9.873519] UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.5-YpKOvT/linux-hwe-6.5-6.5.0/drivers/gpu/drm/amd/amdgpu/../pm/powerplay/hwmgr/smu7_hwmgr.c:3676:4 Mar 7 19:07:10 ripper kernel: [9.873531] index 7 is out of range for type 'ATOM_Polaris_SCLK_Dependency_Record [1]' Mar 7 19:07:10 ripper kernel: [9.873538] CPU: 4 PID: 849 Comm: systemd-udevd Not tainted 6.5.0-17-generic #17~22.04.1-Ubuntu Mar 7 19:07:10 ripper kernel: [9.873542] Hardware name: LENOVO 30E1S3VV00/1046, BIOS S07KT45A 01/20/2022 Mar 7 19:07:10 ripper kernel: [9.873544] Call Trace: Mar 7 19:07:10 ripper kernel: [9.873545] Mar 7 19:07:10 ripper kernel: [9.873547] dump_stack_lvl+0x48/0x70 Mar 7 19:07:10 ripper kernel: [9.873551] dump_stack+0x10/0x20 Mar 7 19:07:10 ripper kernel: [9.873554] __ubsan_handle_out_of_bounds+0xc6/0x110 Mar 7 19:07:10 ripper kernel: [9.873560] smu7_get_pp_table_entry_callback_func_v1+0x9b7/0xa00 [amdgpu] Mar 7 19:07:10 ripper kernel: [9.873897] ? srso_return_thunk+0x5/0x10 Mar 7 19:07:10 ripper kernel: [9.873900] ? vi_pcie_rreg+0x6e/0x90 [amdgpu] Mar 7 19:07:10 ripper kernel: [9.874187] ? __pfx_smu7_get_pp_table_entry_callback_func_v1+0x10/0x10 [amdgpu] Mar 7 19:07:10 ripper kernel: [9.874515] get_powerplay_table_entry_v1_0+0xf8/0x490 [amdgpu] Mar 7 19:07:10 ripper kernel: [9.874842] smu7_get_pp_table_entry_v1+0x41/0x4c0 [amdgpu] Mar 7 19:07:10 ripper kernel: [9.875169] smu7_get_pp_table_entry+0x3d/0x50 [amdgpu] Mar 7 19:07:10 ripper kernel: [9.875495] psm_init_power_state_table+0x161/0x250 [amdgpu] Mar 7 19:07:10 ripper kernel: [9.875826] hwmgr_hw_init+0xe3/0x1e0 [amdgpu] Mar 7 19:07:10 ripper kernel: [9.876150] pp_hw_init+0x16/0x50 [amdgpu] Mar 7 19:07:10 ripper kernel: [9.876484] amdgpu_device_ip_init+0x48d/0x960 [amdgpu] Mar 7 19:07:10 ripper kernel: [9.876749] amdgpu_device_init+0x9a2/0x1150 [amdgpu] Mar 7 19:07:10 ripper kernel: [9.877014] amdgpu_driver_load_kms+0x1a/0x1c0 [amdgpu] Mar 7 19:07:10 ripper kernel: [9.877278] amdgpu_pci_probe+0x182/0x450 [amdgpu] Mar 7 19:07:10 ripper kernel: [9.877541] local_pci_probe+0x47/0xb0 Mar 7 19:07:10 ripper kernel: [9.877545] pci_call_probe+0x55/0x190 Mar 7 19:07:10 ripper kernel: [9.877550] pci_device_probe+0x84/0x120 Mar 7 19:07:10 ripper kernel: [9.877553] ? srso_return_thunk+0x5/0x10 Mar 7 19:07:10 ripper kernel: [9.877557] really_probe+0x1cc/0x430 Mar 7 19:07:10 ripper kernel: [9.877560] __driver_probe_device+0x8c/0x190 Mar 7 19:07:10 ripper kernel: [9.877563] driver_probe_device+0x24/0xd0 Mar 7 19:07:10 ripper kernel: [9.877566] __driver_attach+0x10b/0x210 Mar 7 19:07:10 ripper kernel: [9.877569] ? __pfx___driver_attach+0x10/0x10 Mar 7 19:07:10 ripper kernel: [9.877572] bus_for_each_dev+0x8d/0xf0 Mar 7 19:07:10 ripper kernel: [9.877576] driver_attach+0x1e/0x30 Mar 7 19:07:10 ripper kernel: [9.877579] bus_add_driver+0x127/0x240 Mar 7 19:07:10 ripper kernel: [9.877583] driver_register+0x5e/0x130 Mar 7 19:07:10 ripper kernel: [9.877586] ? __pfx_amdgpu_init+0x10/0x10 [amdgpu] Mar 7 19:07:10 ripper kernel: [9.877849] __pci_register_driver+0x62/0x70 Mar 7 19:07:10 ripper kernel: [9.877852] amdgpu_init+0x69/0xff0 [amdgpu] Mar 7 19:07:10 ripper kernel: [9.878111] ? srso_return_thunk+0x5/0x10 Mar 7 19:07:10 ripper kernel: [9.878114] do_one_initcall+0x5e/0x340 Mar 7 19:07:10 ripper kernel: [9.878120] do_init_module+0x68/0x260 Mar 7 19:07:10 ripper kernel: [9.878123] load_module+0xb85/0xcd0 Mar 7 19:07:10 ripper kernel: [9.878128] ? srso_return_thunk+0x5/0x10 Mar 7 19:07:10 ripper kernel: [9.878131] ? security_kernel_post_read_file+0x75/0x90 Mar 7 19:07:10 ripper kernel: [9.878136] init_module_from_file+0x96/0x100 Mar 7 19:07:10 ripper kernel: [9.878139] ? srso_return_thunk+0x5/0x10 Mar 7 19:07:10 ripper kernel: [9.878142] ? init_module_from_file+0x96/0x100 Mar 7 19:07:10 ripper kernel: [9.878149] idempotent_init_module+0x11c/0x2b0 Mar 7 19:07:10 ripper kernel: [9.878155] __x64_sys_finit_module+0x64/0xd0 Mar 7 19:07:10 ripper kernel: [9.878159] do_syscall_64+0x5b/0x90 Mar 7 19:07:10 ripper kernel: [9.878161] ? srso_return_thunk+0x5/0x10 Mar 7 19:07:10 ripper kernel: [9.878164] ? ksys_mmap_pgoff+0x120/0x270 Mar 7 19:07:10 ripper kernel: [9.878167] ? __secure_computing+0x89/0xf0 Mar 7 19:07:10 ripper kernel: [9.878170] ? srso_return_thunk+0x5/0x10 Mar 7 19:07:10 ripper kernel: [9.878173] ? srso_return_thunk+0x5/0x10 Mar 7 19:07:10 ripper kernel: [9.878176] ? exit_to_user_mode_prepare+0x30/0xb0 Mar 7 19:07:10 ripper kernel: [9.878179] ? srso_return_thunk+0x5/0x10 Mar 7 19:07:10 ripper kernel: [9.878181] ? syscall_exit_to_user_mode+0x37/0x60 Mar 7 19:07:1
[Kernel-packages] [Bug 2055712] [NEW] Pull-request to address bug in mm/page_alloc.c
Public bug reported: The current calculation of min_free_kbytes only uses ZONE_DMA and ZONE_NORMAL pages,but the ZONE_MOVABLE zone->_watermark[WMARK_MIN] will also divide part of min_free_kbytes.This will cause the min watermark of ZONE_NORMAL to be too small in the presence of ZONE_MOVEABLE. __GFP_HIGH and PF_MEMALLOC allocations usually don't need movable zone pages, so just like ZONE_HIGHMEM, cap pages_min to a small value in __setup_per_zone_wmarks(). On my testing machine with 16GB of memory (transparent hugepage is turned off by default, and movablecore=12G is configured) The following is a comparative test data of watermark_min no patchadd patch ZONE_DMA1 8 ZONE_DMA32 151 709 ZONE_NORMAL 233 1113 ZONE_MOVABLE1434128 min_free_kbytes 72887326 ** Affects: linux-nvidia-6.5 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2055712 Title: Pull-request to address bug in mm/page_alloc.c Status in linux-nvidia-6.5 package in Ubuntu: New Bug description: The current calculation of min_free_kbytes only uses ZONE_DMA and ZONE_NORMAL pages,but the ZONE_MOVABLE zone->_watermark[WMARK_MIN] will also divide part of min_free_kbytes.This will cause the min watermark of ZONE_NORMAL to be too small in the presence of ZONE_MOVEABLE. __GFP_HIGH and PF_MEMALLOC allocations usually don't need movable zone pages, so just like ZONE_HIGHMEM, cap pages_min to a small value in __setup_per_zone_wmarks(). On my testing machine with 16GB of memory (transparent hugepage is turned off by default, and movablecore=12G is configured) The following is a comparative test data of watermark_min no patchadd patch ZONE_DMA1 8 ZONE_DMA32 151 709 ZONE_NORMAL 233 1113 ZONE_MOVABLE1434128 min_free_kbytes 72887326 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-6.5/+bug/2055712/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2055060] [NEW] Pull-request: Apply mm/mglru patches to fix soft lockup
Public bug reported: [ 1918.995157] watchdog: BUG: soft lockup - CPU#0 stuck for 1725s! [kswapd0:42] [ 1919.002366] Modules linked in: raid10 raid456 libcrc32c async_raid6_recov async_memcpy async_pq async_xor xor xor_neon async_tx raid6_pq raid1 raid0 multipath linear scsi_dh_alua scsi_dh_emc scsi_dh_rdac nvme nvme_core nvme_common [ 1919.023319] CPU: 0 PID: 42 Comm: kswapd0 Tainted: G L 6.5.0-1011-nvidia #11-Ubuntu [ 1919.032483] Hardware name: NVIDIA Grace Hopper x4 P4496/UT2.1 DP Chassis, BIOS 01.02.00 20240120 [ 1919.042180] pstate: 8349 (Nzcv daif +PAN -UAO +TCO +DIT -SSBS BTYPE=--) [ 1919.049300] pc : __rcu_read_unlock+0x10/0x70 [ 1919.053666] lr : shrink_many+0x280/0x468 [ 1919.057675] sp : 80008149bb70 [ 1919.061060] x29: 80008149bb70 x28: 3ddfa600 x27: deee387571e0 [ 1919.068366] x26: deee383154f8 x25: 0001 x24: 301c90bf4400 [ 1919.075671] x23: x22: x21: 301c90bf4400 [ 1919.082975] x20: 02d3 x19: 80008149bd68 x18: [ 1919.090281] x17: x16: x15: [ 1919.097585] x14: x13: x12: [ 1919.104890] x11: x10: x9 : deee355c2008 [ 1919.112195] x8 : 80008149bde0 x7 : x6 : 0020 [ 1919.119500] x5 : 0001 x4 : x3 : [ 1919.126804] x2 : x1 : 0001 x0 : 301c90bf4400 [ 1919.134109] Call trace: [ 1919.136606] __rcu_read_unlock+0x10/0x70 [ 1919.140615] lru_gen_shrink_node+0x180/0x218 [ 1919.144979] shrink_node+0x400/0x470 [ 1919.148633] balance_pgdat+0x2c8/0x810 [ 1919.152464] kswapd+0x12c/0x268 [ 1919.155672] kthread+0x104/0x110 [ 1919.158970] ret_from_fork+0x10/0x20 [ 1942.995157] watchdog: BUG: soft lockup - CPU#0 stuck for 1747s! [kswapd0:42] [ 1943.002366] Modules linked in: raid10 raid456 libcrc32c async_raid6_recov async_memcpy async_pq async_xor xor xor_neon async_tx raid6_pq raid1 raid0 multipath linear scsi_dh_alua scsi_dh_emc scsi_dh_rdac nvme nvme_core nvme_common [ 1943.023319] CPU: 0 PID: 42 Comm: kswapd0 Tainted: G L 6.5.0-1011-nvidia #11-Ubuntu [ 1943.032483] Hardware name: NVIDIA Grace Hopper x4 P4496/UT2.1 DP Chassis, BIOS 01.02.00 20240120 [ 1943.042180] pstate: 6349 (nZCv daif +PAN -UAO +TCO +DIT -SSBS BTYPE=--) [ 1943.049300] pc : lru_gen_shrink_node+0x60/0x218 [ 1943.053932] lr : lru_gen_shrink_node+0x1b8/0x218 [ 1943.058651] sp : 80008149bbf0 [ 1943.062037] x29: 80008149bbf0 x28: 3ddfa600 x27: deee387571e0 [ 1943.069342] x26: deee383154f8 x25: 80008149bde0 x24: 07c0 [ 1943.076647] x23: 0001 x22: x21: 3ddfe600 [ 1943.083952] x20: 3ddfa600 x19: 80008149bd68 x18: [ 1943.091257] x17: x16: x15: [ 1943.098562] x14: x13: x12: [ 1943.105867] x11: x10: x9 : deee359e4bb8 [ 1943.113172] x8 : 80008149bde0 x7 : x6 : [ 1943.120477] x5 : x4 : x3 : [ 1943.127782] x2 : x1 : x0 : 301c90bf4400 [ 1943.135086] Call trace: [ 1943.137583] lru_gen_shrink_node+0x60/0x218 [ 1943.141858] shrink_node+0x400/0x470 [ 1943.145511] balance_pgdat+0x2c8/0x810 [ 1943.149342] kswapd+0x12c/0x268 [ 1943.152551] kthread+0x104/0x110 [ 1943.155849] ret_from_fork+0x10/0x20 ** Affects: linux-nvidia-6.5 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2055060 Title: Pull-request: Apply mm/mglru patches to fix soft lockup Status in linux-nvidia-6.5 package in Ubuntu: New Bug description: [ 1918.995157] watchdog: BUG: soft lockup - CPU#0 stuck for 1725s! [kswapd0:42] [ 1919.002366] Modules linked in: raid10 raid456 libcrc32c async_raid6_recov async_memcpy async_pq async_xor xor xor_neon async_tx raid6_pq raid1 raid0 multipath linear scsi_dh_alua scsi_dh_emc scsi_dh_rdac nvme nvme_core nvme_common [ 1919.023319] CPU: 0 PID: 42 Comm: kswapd0 Tainted: G L 6.5.0-1011-nvidia #11-Ubuntu [ 1919.032483] Hardware name: NVIDIA Grace Hopper x4 P4496/UT2.1 DP Chassis, BIOS 01.02.00 20240120 [ 1919.042180] pstate: 8349 (Nzcv daif +PAN -UAO +TCO +DIT -SSBS BTYPE=--) [ 1919.049300] pc : __rcu_read_unlock+0x10/0x70 [ 1919.053666] lr : shrink_many+0x280/0x468 [ 1919.057675] sp : 80008149bb70 [ 1919.061060] x29: 80008149bb70 x28: 3ddfa600 x27: deee387571e0 [ 1919.068366] x26: deee383154f8 x25: 000
[Kernel-packages] [Bug 2055057] [NEW] Pull-request: apply upstream patch to reject events meant for other PMUs
Public bug reported: Coresight PMU driver didn't reject events meant for other PMUs. This caused some of the Core PMU events disappearing from the output of "perf list". In addition, trying to run e.g. $ perf stat -e r2 sleep 1 made Coresight PMU driver to handle the event instead of letting Core PMU driver to deal with it. ** Affects: linux-nvidia-6.5 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2055057 Title: Pull-request: apply upstream patch to reject events meant for other PMUs Status in linux-nvidia-6.5 package in Ubuntu: New Bug description: Coresight PMU driver didn't reject events meant for other PMUs. This caused some of the Core PMU events disappearing from the output of "perf list". In addition, trying to run e.g. $ perf stat -e r2 sleep 1 made Coresight PMU driver to handle the event instead of letting Core PMU driver to deal with it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-6.5/+bug/2055057/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2054984] [NEW] Pull request: Enable support of ETE and TRBE in ACPI environment.
Public bug reported: This series enables detection of ACPI based TRBE devices via a stand alone purpose built representative platform device. But as a pre-requisite this changes coresight_platform_data structure assignment for the TRBE device. ** Affects: linux-nvidia-6.5 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2054984 Title: Pull request: Enable support of ETE and TRBE in ACPI environment. Status in linux-nvidia-6.5 package in Ubuntu: New Bug description: This series enables detection of ACPI based TRBE devices via a stand alone purpose built representative platform device. But as a pre-requisite this changes coresight_platform_data structure assignment for the TRBE device. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-6.5/+bug/2054984/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2053148] [NEW] Pull request: address GPIO initialization regression on Grace systems
Public bug reported: The tegra186_gpio_is_accessible() function incorrectly declares GPIO lines that have only one of TEGRA186_GPIO_SCR_SEC_REN _or_ TEGRA186_GPIO_SCR_SEC_WEN set as being inaccessible. ** Affects: linux-nvidia-6.5 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2053148 Title: Pull request: address GPIO initialization regression on Grace systems Status in linux-nvidia-6.5 package in Ubuntu: New Bug description: The tegra186_gpio_is_accessible() function incorrectly declares GPIO lines that have only one of TEGRA186_GPIO_SCR_SEC_REN _or_ TEGRA186_GPIO_SCR_SEC_WEN set as being inaccessible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-6.5/+bug/2053148/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049537] [NEW] Pull request for: peer-memory, ACPI thermal issues and coresight etm4x issues
Public bug reported: * Add support of "Thermal fast Sampling Period (_TFP)" for passive cooling. * Finer grained CPU throttling * The peer_memory_client scheme allows a driver to register with the ib_umem system that it has the ability to understand user virtual address ranges that are not compatible with get_user_pages(). For instance VMAs created with io_remap_pfn_range(), or other driver special VMA. ** Affects: linux-nvidia-6.5 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2049537 Title: Pull request for: peer-memory, ACPI thermal issues and coresight etm4x issues Status in linux-nvidia-6.5 package in Ubuntu: New Bug description: * Add support of "Thermal fast Sampling Period (_TFP)" for passive cooling. * Finer grained CPU throttling * The peer_memory_client scheme allows a driver to register with the ib_umem system that it has the ability to understand user virtual address ranges that are not compatible with get_user_pages(). For instance VMAs created with io_remap_pfn_range(), or other driver special VMA. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-6.5/+bug/2049537/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2048815] [NEW] Pull request to address TPM SPI devices
Public bug reported: TPM devices may insert wait state on last clock cycle of ADDR phase. For SPI controllers that support full-duplex transfers, this can be detected using software by reading the MISO line. For SPI controllers that only support half-duplex transfers, such as the Tegra QSPI, it is not possible to detect the wait signal from software. ** Affects: linux-nvidia-6.5 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2048815 Title: Pull request to address TPM SPI devices Status in linux-nvidia-6.5 package in Ubuntu: New Bug description: TPM devices may insert wait state on last clock cycle of ADDR phase. For SPI controllers that support full-duplex transfers, this can be detected using software by reading the MISO line. For SPI controllers that only support half-duplex transfers, such as the Tegra QSPI, it is not possible to detect the wait signal from software. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-6.5/+bug/2048815/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2043132] [NEW] Pull request to enable GDS optimization in the Grace enablement kernel
Public bug reported: These are the same patches that have been applied to the 5.19 and 6.2 kernels to enable GDS. NVIDIA is requesting they be applied to the 6.5 kernel which is used for Grace enablement. ** Affects: linux-nvidia-6.5 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2043132 Title: Pull request to enable GDS optimization in the Grace enablement kernel Status in linux-nvidia-6.5 package in Ubuntu: New Bug description: These are the same patches that have been applied to the 5.19 and 6.2 kernels to enable GDS. NVIDIA is requesting they be applied to the 6.5 kernel which is used for Grace enablement. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-6.5/+bug/2043132/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2043059] [NEW] Installation errors out when installing in a chroot
Public bug reported: Processing triggers for linux-image-5.15.0-1040-nvidia (5.15.0-1040.40) ... /etc/kernel/postinst.d/dkms: * dkms: running auto installation service for kernel 5.15.0-1040-nvidia ...done. /etc/kernel/postinst.d/initramfs-tools: update-initramfs: Generating /boot/initrd.img-5.15.0-1040-nvidia cryptsetup: WARNING: Couldn't determine root device W: Couldn't identify type of root file system for fsck hook cp: cannot stat '/etc/iscsi/initiatorname.iscsi': No such file or directory /etc/kernel/postinst.d/kdump-tools: kdump-tools: Generating /var/lib/kdump/initrd.img-5.15.0-1040-nvidia mkinitramfs: failed to determine device for / mkinitramfs: workaround is MODULES=most, check: grep -r MODULES /var/lib/kdump/initramfs-tools Error please report bug on initramfs-tools Include the output of 'mount' and 'cat /proc/mounts' update-initramfs: failed for /var/lib/kdump/initrd.img-5.15.0-1040-nvidia with 1. run-parts: /etc/kernel/postinst.d/kdump-tools exited with return code 1 dpkg: error processing package linux-image-5.15.0-1040-nvidia (--configure): installed linux-image-5.15.0-1040-nvidia package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: linux-image-5.15.0-1040-nvidia E: Sub-process /usr/bin/dpkg returned an error code (1) ** Affects: linux-nvidia (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia in Ubuntu. https://bugs.launchpad.net/bugs/2043059 Title: Installation errors out when installing in a chroot Status in linux-nvidia package in Ubuntu: New Bug description: Processing triggers for linux-image-5.15.0-1040-nvidia (5.15.0-1040.40) ... /etc/kernel/postinst.d/dkms: * dkms: running auto installation service for kernel 5.15.0-1040-nvidia ...done. /etc/kernel/postinst.d/initramfs-tools: update-initramfs: Generating /boot/initrd.img-5.15.0-1040-nvidia cryptsetup: WARNING: Couldn't determine root device W: Couldn't identify type of root file system for fsck hook cp: cannot stat '/etc/iscsi/initiatorname.iscsi': No such file or directory /etc/kernel/postinst.d/kdump-tools: kdump-tools: Generating /var/lib/kdump/initrd.img-5.15.0-1040-nvidia mkinitramfs: failed to determine device for / mkinitramfs: workaround is MODULES=most, check: grep -r MODULES /var/lib/kdump/initramfs-tools Error please report bug on initramfs-tools Include the output of 'mount' and 'cat /proc/mounts' update-initramfs: failed for /var/lib/kdump/initrd.img-5.15.0-1040-nvidia with 1. run-parts: /etc/kernel/postinst.d/kdump-tools exited with return code 1 dpkg: error processing package linux-image-5.15.0-1040-nvidia (--configure): installed linux-image-5.15.0-1040-nvidia package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: linux-image-5.15.0-1040-nvidia E: Sub-process /usr/bin/dpkg returned an error code (1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia/+bug/2043059/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2042697] [NEW] Pull request to address thermal core issues
Public bug reported: The Grace development team has not been testing the 6.2 Ubuntu kernel but instead a newer kernel. When they run their thermal tests on a 6.2 kernel they are running into failures. Investigations have turned up several missing kernel patches. These patches are clean cherry-picks and have been tested and confirmed to fix the thermal issues we are seeing. ** Affects: linux-nvidia-6.2 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2042697 Title: Pull request to address thermal core issues Status in linux-nvidia-6.2 package in Ubuntu: New Bug description: The Grace development team has not been testing the 6.2 Ubuntu kernel but instead a newer kernel. When they run their thermal tests on a 6.2 kernel they are running into failures. Investigations have turned up several missing kernel patches. These patches are clean cherry-picks and have been tested and confirmed to fix the thermal issues we are seeing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-6.2/+bug/2042697/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038099] [NEW] Enable building and signing of the nvidia-fs out-of-tree kernel module.
Public bug reported: [Issue] The nvidia-fs kernel module is a must have for Nvidia optimized kernels. There is now a version that is compatible with the Grace processor. Integrate the changes necessary to build and sign this out-of-tree kernel module. ** Affects: linux-nvidia-6.2 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2038099 Title: Enable building and signing of the nvidia-fs out-of-tree kernel module. Status in linux-nvidia-6.2 package in Ubuntu: New Bug description: [Issue] The nvidia-fs kernel module is a must have for Nvidia optimized kernels. There is now a version that is compatible with the Grace processor. Integrate the changes necessary to build and sign this out- of-tree kernel module. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-6.2/+bug/2038099/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037688] [NEW] Pull-request to address TPM bypass issue
Public bug reported: NVIDIA: [Config]: Ensure the TPM is available before IMA initializes Set the following configs: CONFIG_SPI_TEGRA210_QUAD=y CONFIG_TCG_TIS_SPI=y On Grace systems, the IMA driver emits the following log: ima: No TPM chip found, activating TPM-bypass! This occurs because the IMA driver initializes before we are able to detect the TPM. This will always be the case when the drivers required to communicate with the TPM, spi_tegra210_quad and tpm_tis_spi, are built as modules. Having these drivers as built-ins ensures that the TPM is available before the IMA driver initializes. ** Affects: linux-nvidia-6.2 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2037688 Title: Pull-request to address TPM bypass issue Status in linux-nvidia-6.2 package in Ubuntu: New Bug description: NVIDIA: [Config]: Ensure the TPM is available before IMA initializes Set the following configs: CONFIG_SPI_TEGRA210_QUAD=y CONFIG_TCG_TIS_SPI=y On Grace systems, the IMA driver emits the following log: ima: No TPM chip found, activating TPM-bypass! This occurs because the IMA driver initializes before we are able to detect the TPM. This will always be the case when the drivers required to communicate with the TPM, spi_tegra210_quad and tpm_tis_spi, are built as modules. Having these drivers as built-ins ensures that the TPM is available before the IMA driver initializes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-6.2/+bug/2037688/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2033685] [NEW] Pull-request to address ARM CoreSoght PMU issues
Public bug reported: [issue] This patch set addresses several CoreSight PMU issues. These are all upstream patches. Commit Summary 2940a5e perf: arm_cspmu: Fix variable dereference warning 06f6951 perf: arm_cspmu: Set irq affinitiy only if overflow interrupt is used 292771d perf/arm_cspmu: Fix event attribute type 6992931 ACPI/APMT: Don't register invalid resource 48f4b92 perf/arm_cspmu: Clean up ACPI dependency 7da1852 perf/arm_cspmu: Decouple APMT dependency d3d56a4 perf: arm_cspmu: Add missing MODULE_DEVICE_TABLE File Changes (4 files) M drivers/acpi/arm64/apmt.c (10) M drivers/perf/arm_cspmu/Kconfig (3) M drivers/perf/arm_cspmu/arm_cspmu.c (95) M drivers/perf/arm_cspmu/arm_cspmu.h (5) ** Affects: linux-nvidia-6.2 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2033685 Title: Pull-request to address ARM CoreSoght PMU issues Status in linux-nvidia-6.2 package in Ubuntu: New Bug description: [issue] This patch set addresses several CoreSight PMU issues. These are all upstream patches. Commit Summary 2940a5e perf: arm_cspmu: Fix variable dereference warning 06f6951 perf: arm_cspmu: Set irq affinitiy only if overflow interrupt is used 292771d perf/arm_cspmu: Fix event attribute type 6992931 ACPI/APMT: Don't register invalid resource 48f4b92 perf/arm_cspmu: Clean up ACPI dependency 7da1852 perf/arm_cspmu: Decouple APMT dependency d3d56a4 perf: arm_cspmu: Add missing MODULE_DEVICE_TABLE File Changes (4 files) M drivers/acpi/arm64/apmt.c (10) M drivers/perf/arm_cspmu/Kconfig (3) M drivers/perf/arm_cspmu/arm_cspmu.c (95) M drivers/perf/arm_cspmu/arm_cspmu.h (5) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-6.2/+bug/2033685/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2028576] [NEW] Pull-request for setting CPU frequency gov to performance
Public bug reported: [issue] CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE is not set so it's using ondemand. We want to be using PERFORMANCE ** Affects: linux-nvidia-6.2 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2028576 Title: Pull-request for setting CPU frequency gov to performance Status in linux-nvidia-6.2 package in Ubuntu: New Bug description: [issue] CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE is not set so it's using ondemand. We want to be using PERFORMANCE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-6.2/+bug/2028576/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1982519] Re: GDS: Add NFS patches to optimized kernel
** Also affects: linux-nvidia-5.19 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-nvidia-6.2 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/1982519 Title: GDS: Add NFS patches to optimized kernel Status in linux-nvidia package in Ubuntu: New Status in linux-nvidia-5.19 package in Ubuntu: New Status in linux-nvidia-6.2 package in Ubuntu: New Status in linux-nvidia source package in Jammy: Fix Released Status in linux-nvidia-5.19 source package in Jammy: New Status in linux-nvidia-6.2 source package in Jammy: New Bug description: [Impact] Adding these changes will enable GDS functionality NFS drivers. [Fix] This is a not a fix but a new feature being to NFS driver. [Test] Tested the NFS driver on a hpe system as I did not have a setup with BASEOS6. 1) Installed 5.15.39 kernel on the system (this is the kernel that optimized kernel is on currently). 2) Downloaded the optimized kernel. 3) Applied the patches to the optimized kernel 4) Replaced the NFS modules on the system with the one's built on optimized kernel. 5) Ran gds and compat mode tests on a NFS mount with the patched NFS driver. All tests went fine. Attaching the results Compat mode tests == ** API Tests, : 72 / 72 tests passed ** Testsuite : 211 / 211 tests passed done tests:Thu Jul 21 08:27:58 PM UTC 2022 GDS mode tests == ** NVFS IOCTL negative Tests, : 23 / 23 tests passed ** Testsuite : 249 / 249 tests passed End: nvidia-fs: GDS Version: 1.4.0.31 NVFS statistics(ver: 4.0) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia/+bug/1982519/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2026891] Re: linux-nvidia-6.2 on DGX servers: "WARNING: CPU: 0 PID: 0 at init/main.c:1065 start_kernel+0x4da/0x540"
The following changes since commit 3d28f6c10d6940b0c6a497482fe90cc4dbd5549a: UBUNTU: Ubuntu-nvidia-6.2-6.2.0-1004.4~22.04.1 (2023-07-03 10:01:31 -0700) are available in the Git repository at: https://github.com/NVIDIA-BaseOS-6/linux-nvidia-6.2/pull/new/bfigg- lp2026891 for you to fetch changes up to 8029e7fc883e8a86076e1bb4379f8d6d0236ab97: mm, slab/slub: Ensure kmem_cache_alloc_bulk() is available early (2023-07-15 19:30:31 -0700) Thomas Gleixner (1): mm, slab/slub: Ensure kmem_cache_alloc_bulk() is available early mm/slab.c | 18 ++ mm/slub.c | 9 + 2 files changed, 15 insertions(+), 12 deletions(-) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2026891 Title: linux-nvidia-6.2 on DGX servers: "WARNING: CPU: 0 PID: 0 at init/main.c:1065 start_kernel+0x4da/0x540" Status in linux-nvidia-6.2 package in Ubuntu: New Bug description: We started testing the jammy/linux-nvidia-6.2 kernels on the nvidia servers (DGX-1/DGX-2/H100) and hit the following warning during boot: [7.690486] [ cut here ] [7.690487] Interrupts were enabled early [7.690490] WARNING: CPU: 0 PID: 0 at init/main.c:1065 start_kernel+0x4da/0x540 [7.690498] Modules linked in: [7.690501] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 6.2.0-1004-nvidia #4~22.04.1-Ubuntu [7.690504] Hardware name: NVIDIA NVIDIA DGX-2/NVIDIA DGX-2, BIOS 0.29 06/07/2021 [7.690505] RIP: 0010:start_kernel+0x4da/0x540 [7.690508] Code: ff 48 c7 c7 e8 26 f0 97 e8 b3 59 a8 fd 0f 0b e9 96 fd ff ff e8 a7 1d 04 00 e9 7c fe ff ff 48 c7 c7 18 27 f0 97 e8 96 59 a8 fd <0f> 0b e9 ed fd ff ff 48 c7 c7 b0 26 f0 97 e8 83 59 a8 fd 0f 0b ff [7.690510] RSP: :98803f08 EFLAGS: 00010246 [7.690512] RAX: RBX: RCX: [7.690513] RDX: RSI: RDI: [7.690514] RBP: 98803f20 R08: R09: [7.690515] R10: R11: R12: 00e0 [7.690516] R13: 5a1ccde0 R14: 5a1c7469 R15: 5a1d7ee0 [7.690518] FS: () GS:96490060() knlGS: [7.690520] CS: 0010 DS: ES: CR0: 80050033 [7.690521] CR2: 970bf000 CR3: 00ecd7810001 CR4: 000606f0 [7.690522] DR0: DR1: DR2: [7.690523] DR3: DR6: fffe0ff0 DR7: 0400 [7.690524] Call Trace: [7.690526] [7.690529] x86_64_start_kernel+0x102/0x180 [7.690536] secondary_startup_64_no_verify+0xe5/0xeb [7.690544] [7.690544] ---[ end trace ]--- I also see pretty much the same thing on some Ampere based arm64 servers: [0.000519] [ cut here ] [0.000521] Interrupts were enabled early [0.000525] WARNING: CPU: 0 PID: 0 at init/main.c:1065 start_kernel+0x3ac/0x514 [0.000531] Modules linked in: [0.000535] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 6.2.0-1004-nvidia #4~22.04.1-Ubuntu [0.000538] pstate: 6049 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) [0.000540] pc : start_kernel+0x3ac/0x514 [0.000543] lr : start_kernel+0x3ac/0x514 [0.000545] sp : dec5ff733e60 [0.000546] x29: dec5ff733e60 x28: 0819aa09baac x27: 403ffdd124e0 [0.000549] x26: bfdf3788 x25: 9b6fc000 x24: 001dba7b [0.000552] x23: 5ec57c98 x22: 0819ab2a x21: dec5ff749140 [0.000555] x20: dec5ff73d9c0 x19: dec5ffbe4000 x18: dec5ff74a1c8 [0.000558] x17: x16: x15: [0.000560] x14: x13: 0a796c7261652064 x12: 656c62616e652065 [0.000563] x11: 656820747563205b x10: 2d2d2d2d2d2d2d2d x9 : [0.000565] x8 : x7 : x6 : [0.000568] x5 : x4 : x3 : [0.000571] x2 : x1 : x0 : [0.000573] Call trace: [0.000574] start_kernel+0x3ac/0x514 [0.000577] __primary_switched+0xc0/0xc8 [0.000580] ---[ end trace ]--- The warning does not appear on an older thunderx2 server. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-6.2/+bug/2026891/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kerne
[Kernel-packages] [Bug 2027837] Re: Pull request to address missing NVIDIA Grace SOC patches
** Description changed: [Impact] There are a number of fixes for Grace SOC enablement in the related pull request. Application of this pull-request is appreciated. These patches have been reviewed and tested, confirming they address these issues. + + Akhil R (2): + i2c: tegra: Set ACPI node as primary fwnode + i2c: tegra: Fix PEC support for SMBUS block read + + Krishna Yarlagadda (6): + spi: tegra210-quad: set half duplex flag + spi: tegra210-quad: Fix validate combined sequence + spi: tegra210-quad: Fix iterator outside loop + spi: Add TPM HW flow flag + spi: tegra210-quad: Enable TPM wait polling + tpm_tis-spi: Add hardware wait polling + + NÃcolas F. R. A. Prado (1): + arm64: defconfig: Enable missing configs for mt8183-jacuzzi-juniper + + Samuel Holland (1): + genirq: GENERIC_IRQ_EFFECTIVE_AFF_MASK depends on SMP + + Shanker Donthineni (1): + irqchip/gicv3: Workaround for NVIDIA erratum T241-FABRIC-4 + + Tushar Dave (2): + Revert "UBUNTU: SAUCE: tpm: tegra: Support SPI tpm wait state detect" + Revert "UBUNTU: SAUCE: spi: tegra210-quad: Enable TPM wait polling" -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2027837 Title: Pull request to address missing NVIDIA Grace SOC patches Status in linux-nvidia-5.19 package in Ubuntu: New Bug description: [Impact] There are a number of fixes for Grace SOC enablement in the related pull request. Application of this pull-request is appreciated. These patches have been reviewed and tested, confirming they address these issues. Akhil R (2): i2c: tegra: Set ACPI node as primary fwnode i2c: tegra: Fix PEC support for SMBUS block read Krishna Yarlagadda (6): spi: tegra210-quad: set half duplex flag spi: tegra210-quad: Fix validate combined sequence spi: tegra210-quad: Fix iterator outside loop spi: Add TPM HW flow flag spi: tegra210-quad: Enable TPM wait polling tpm_tis-spi: Add hardware wait polling NÃcolas F. R. A. Prado (1): arm64: defconfig: Enable missing configs for mt8183-jacuzzi-juniper Samuel Holland (1): genirq: GENERIC_IRQ_EFFECTIVE_AFF_MASK depends on SMP Shanker Donthineni (1): irqchip/gicv3: Workaround for NVIDIA erratum T241-FABRIC-4 Tushar Dave (2): Revert "UBUNTU: SAUCE: tpm: tegra: Support SPI tpm wait state detect" Revert "UBUNTU: SAUCE: spi: tegra210-quad: Enable TPM wait polling" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-5.19/+bug/2027837/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2027837] [NEW] Pull request to address missing NVIDIA Grace SOC patches
Public bug reported: [Impact] There are a number of fixes for Grace SOC enablement in the related pull request. Application of this pull-request is appreciated. These patches have been reviewed and tested, confirming they address these issues. ** Affects: linux-nvidia-5.19 (Ubuntu) Importance: Undecided Status: New ** Package changed: linux-nvidia-6.2 (Ubuntu) => linux-nvidia-5.19 (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2027837 Title: Pull request to address missing NVIDIA Grace SOC patches Status in linux-nvidia-5.19 package in Ubuntu: New Bug description: [Impact] There are a number of fixes for Grace SOC enablement in the related pull request. Application of this pull-request is appreciated. These patches have been reviewed and tested, confirming they address these issues. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-5.19/+bug/2027837/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2026776] Re: arm64+ast2600: No Output from BMC's VGA port
There is no need for kernel logs, we've already diagnosed the problem and are providing the solution. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2026776 Title: arm64+ast2600: No Output from BMC's VGA port Status in linux package in Ubuntu: New Status in linux-hwe-5.19 package in Ubuntu: New Status in linux-hwe-6.2 package in Ubuntu: New Bug description: [Issue] On systems that have the following combination of hardware...: 1) arm64 CPU 2) ASPEED AST2600 BMC: https://www.aspeedtech.com/server_ast2600/ .. we see no output when connecting a display to the BMC's VGA port. Upon further investigation, we see that applying the following patch fixes this issue: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/gpu/drm/ast?h=v6.4-rc6&id=4327a6137ed43a091d900b1ac833345d60f32228 [Action] Please apply the following two backports to the appropriate Ubuntu HWE kernels: https://github.com/NVIDIA-BaseOS-6/linux-nvidia-5.19/commit/055c9ec3739d7df1179db3ba054b00f3dd684560 https://github.com/NVIDIA-BaseOS-6/linux-nvidia-6.2/commit/8ab3253c6a59eee3424fe0c60b1fc6dc9f2d73b7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2026776/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2026776] Re: arm64+ast2600: No Output from BMC's VGA port
** Also affects: linux-hwe-6.2 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-hwe-5.19 (Ubuntu) Importance: Undecided Status: New ** Description changed: Hello, On systems that have the following combination of hardware...: 1) arm64 CPU 2) ASPEED AST2600 BMC: https://www.aspeedtech.com/server_ast2600/ .. we see no output when connecting a display to the BMC's VGA port. Upon further investigation, we see that applying the following patch fixes this issue: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/gpu/drm/ast?h=v6.4-rc6&id=4327a6137ed43a091d900b1ac833345d60f32228 Would it be possible to apply this patch to affected kernels? Using the aforementioned combination, the ast driver is broken without this patch. + + https://github.com/NVIDIA-BaseOS-6/linux-nvidia-5.19/commit/055c9ec3739d7df1179db3ba054b00f3dd684560 + https://github.com/NVIDIA-BaseOS-6/linux-nvidia-6.2/commit/8ab3253c6a59eee3424fe0c60b1fc6dc9f2d73b7 ** Description changed: Hello, On systems that have the following combination of hardware...: 1) arm64 CPU 2) ASPEED AST2600 BMC: https://www.aspeedtech.com/server_ast2600/ .. we see no output when connecting a display to the BMC's VGA port. Upon further investigation, we see that applying the following patch fixes this issue: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/gpu/drm/ast?h=v6.4-rc6&id=4327a6137ed43a091d900b1ac833345d60f32228 - Would it be possible to apply this patch to affected kernels? Using the - aforementioned combination, the ast driver is broken without this patch. + [Action] https://github.com/NVIDIA-BaseOS-6/linux-nvidia-5.19/commit/055c9ec3739d7df1179db3ba054b00f3dd684560 https://github.com/NVIDIA-BaseOS-6/linux-nvidia-6.2/commit/8ab3253c6a59eee3424fe0c60b1fc6dc9f2d73b7 ** Description changed: - Hello, + [Issue] On systems that have the following combination of hardware...: 1) arm64 CPU 2) ASPEED AST2600 BMC: https://www.aspeedtech.com/server_ast2600/ .. we see no output when connecting a display to the BMC's VGA port. Upon further investigation, we see that applying the following patch fixes this issue: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/gpu/drm/ast?h=v6.4-rc6&id=4327a6137ed43a091d900b1ac833345d60f32228 [Action] https://github.com/NVIDIA-BaseOS-6/linux-nvidia-5.19/commit/055c9ec3739d7df1179db3ba054b00f3dd684560 https://github.com/NVIDIA-BaseOS-6/linux-nvidia-6.2/commit/8ab3253c6a59eee3424fe0c60b1fc6dc9f2d73b7 ** Description changed: [Issue] On systems that have the following combination of hardware...: 1) arm64 CPU 2) ASPEED AST2600 BMC: https://www.aspeedtech.com/server_ast2600/ .. we see no output when connecting a display to the BMC's VGA port. Upon further investigation, we see that applying the following patch fixes this issue: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/gpu/drm/ast?h=v6.4-rc6&id=4327a6137ed43a091d900b1ac833345d60f32228 [Action] + Please apply the following two backports to the appropriate Ubuntu HWE + kernels: + https://github.com/NVIDIA-BaseOS-6/linux-nvidia-5.19/commit/055c9ec3739d7df1179db3ba054b00f3dd684560 https://github.com/NVIDIA-BaseOS-6/linux-nvidia-6.2/commit/8ab3253c6a59eee3424fe0c60b1fc6dc9f2d73b7 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2026776 Title: arm64+ast2600: No Output from BMC's VGA port Status in linux package in Ubuntu: New Status in linux-hwe-5.19 package in Ubuntu: New Status in linux-hwe-6.2 package in Ubuntu: New Bug description: [Issue] On systems that have the following combination of hardware...: 1) arm64 CPU 2) ASPEED AST2600 BMC: https://www.aspeedtech.com/server_ast2600/ .. we see no output when connecting a display to the BMC's VGA port. Upon further investigation, we see that applying the following patch fixes this issue: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/gpu/drm/ast?h=v6.4-rc6&id=4327a6137ed43a091d900b1ac833345d60f32228 [Action] Please apply the following two backports to the appropriate Ubuntu HWE kernels: https://github.com/NVIDIA-BaseOS-6/linux-nvidia-5.19/commit/055c9ec3739d7df1179db3ba054b00f3dd684560 https://github.com/NVIDIA-BaseOS-6/linux-nvidia-6.2/commit/8ab3253c6a59eee3424fe0c60b1fc6dc9f2d73b7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2026776/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2024857] [NEW] Request application of pull-request for Grace SOC enablement
Public bug reported: [Impact] We are starting work on the new 6.2 based, HWE kernel for supporting the NVIDIA Grace SOC. A setup of patches needs to be pulled in to address issues. All of these patches are found in more recent upstream kernel versions. ** Affects: linux-nvidia-6.2 (Ubuntu) Importance: Undecided Status: New ** Package changed: linux-nvidia-5.19 (Ubuntu) => linux-nvidia-6.2 (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2024857 Title: Request application of pull-request for Grace SOC enablement Status in linux-nvidia-6.2 package in Ubuntu: New Bug description: [Impact] We are starting work on the new 6.2 based, HWE kernel for supporting the NVIDIA Grace SOC. A setup of patches needs to be pulled in to address issues. All of these patches are found in more recent upstream kernel versions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-6.2/+bug/2024857/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2021535] [NEW] Request application of upstream patch to address drm/ast ARM compatibility issue
Public bug reported: [impact] This patch addresses a drm/ast compatibility issue with ARM architecture. The patch is in the upstream Linux kernel as sha1 4327a6137ed43a091d900b1ac833345d60f32228. The issue was found during development testing and application of this commit has been confirmed to resolve the issue. ** Affects: linux-nvidia-tegra (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-tegra in Ubuntu. https://bugs.launchpad.net/bugs/2021535 Title: Request application of upstream patch to address drm/ast ARM compatibility issue Status in linux-nvidia-tegra package in Ubuntu: New Bug description: [impact] This patch addresses a drm/ast compatibility issue with ARM architecture. The patch is in the upstream Linux kernel as sha1 4327a6137ed43a091d900b1ac833345d60f32228. The issue was found during development testing and application of this commit has been confirmed to resolve the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra/+bug/2021535/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2019240] [NEW] Pull-request to address a number of enablement issues for Orin platforms
Public bug reported: [impact] This patch set addresses a wide variety of bugs and missing features for NVIDIA Orin platforms. ** Affects: linux-nvidia (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia in Ubuntu. https://bugs.launchpad.net/bugs/2019240 Title: Pull-request to address a number of enablement issues for Orin platforms Status in linux-nvidia package in Ubuntu: New Bug description: [impact] This patch set addresses a wide variety of bugs and missing features for NVIDIA Orin platforms. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia/+bug/2019240/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2016177] [NEW] Pull-request to remove NOUVEAU configuration and address annotations
Public bug reported: [Impact] This patch set removes the NOUVEAU driver configuration settings. On BaseOS we normally blacklist the driver. This configuration change makes that unnecessary. Also, annotations have been effectively disabled for this kernel. This patch set makes a number of configuration changes to reflect the current state of the annotations file as well as updating the annotations file to get it closer to being able to enable enforcement again. [Patches] The following changes since commit e6d6e51ecc26e049ae80ca5ef965d3b8fae98fdd: UBUNTU: Ubuntu-nvidia-5.15.0-1020.20 (2023-04-09 21:13:44 -0700) are available in the Git repository at: https://github.com/NVIDIA-BaseOS-6/linux-nvidia/pull/new/bfigg-nouveau for you to fetch changes up to d4c2afee98a9371d18411ba1171cadeab8cff664: NVIDIA: [Config] Remove the backport-iwlwifi-dkms driver (2023-04-13 12:09:10 -0700) Brad Figg (6): NVIDIA: [Config] change CONFIG_DRM_NOUVEAU and CONFIG_DRM_NOUVEAU_BACKLIGHT to is not set NVIDIA: [Config] changed CONFIG_VIDEO_OV01A1S to is not set NVIDIA: [Config] set CONFIG_POWER_CTRL_LOGIC=m NVIDIA: [Config] set CONFIG_VIDEO_HM11B1=m and CONFIG_VIDEO_OV01A1S=m NVIDIA: [Config] Resolve a number of annotations vs config conflicts. NVIDIA: [Config] Remove the backport-iwlwifi-dkms driver debian.nvidia/abi/amd64/nvidia-lowlatency.modules | 1 - debian.nvidia/abi/amd64/nvidia.modules| 1 - debian.nvidia/config/annotations | 45 + debian.nvidia/config/config.common.ubuntu | 9 ++--- debian/dkms-versions | 1 - 5 files changed, 51 insertions(+), 6 deletions(-) ** Affects: linux-nvidia (Ubuntu) Importance: Undecided Status: New ** Description changed: [Impact] - This patch set removes the NOUVEAU driver configuration settings. On BaseOS we normally blacklist the driver. This configuration change makes that unnecessary. + This patch set removes the NOUVEAU driver configuration settings. On BaseOS we normally blacklist the driver. This configuration change makes that unnecessary. - Also, annotations have been effectively disabled for this kernel. + Also, annotations have been effectively disabled for this kernel. This patch set makes a number of configuration changes to reflect the current state of the annotations file as well as updating the annotations file to get it closer to being able to enable enforcement again. [Patches] + The following changes since commit e6d6e51ecc26e049ae80ca5ef965d3b8fae98fdd: + + UBUNTU: Ubuntu-nvidia-5.15.0-1020.20 (2023-04-09 21:13:44 -0700) + + are available in the Git repository at: + + https://github.com/NVIDIA-BaseOS-6/linux-nvidia/pull/new/bfigg-nouveau + + for you to fetch changes up to d4c2afee98a9371d18411ba1171cadeab8cff664: + + NVIDIA: [Config] Remove the backport-iwlwifi-dkms driver (2023-04-13 + 12:09:10 -0700) + + + Brad Figg (6): + NVIDIA: [Config] change CONFIG_DRM_NOUVEAU and CONFIG_DRM_NOUVEAU_BACKLIGHT to is not set + NVIDIA: [Config] changed CONFIG_VIDEO_OV01A1S to is not set + NVIDIA: [Config] set CONFIG_POWER_CTRL_LOGIC=m + NVIDIA: [Config] set CONFIG_VIDEO_HM11B1=m and CONFIG_VIDEO_OV01A1S=m + NVIDIA: [Config] Resolve a number of annotations vs config conflicts. + NVIDIA: [Config] Remove the backport-iwlwifi-dkms driver + + debian.nvidia/abi/amd64/nvidia-lowlatency.modules | 1 - + debian.nvidia/abi/amd64/nvidia.modules| 1 - + debian.nvidia/config/annotations | 45 + + debian.nvidia/config/config.common.ubuntu | 9 ++--- + debian/dkms-versions | 1 - + 5 files changed, 51 insertions(+), 6 deletions(-) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia in Ubuntu. https://bugs.launchpad.net/bugs/2016177 Title: Pull-request to remove NOUVEAU configuration and address annotations Status in linux-nvidia package in Ubuntu: New Bug description: [Impact] This patch set removes the NOUVEAU driver configuration settings. On BaseOS we normally blacklist the driver. This configuration change makes that unnecessary. Also, annotations have been effectively disabled for this kernel. This patch set makes a number of configuration changes to reflect the current state of the annotations file as well as updating the annotations file to get it closer to being able to enable enforcement again. [Patches] The following changes since commit e6d6e51ecc26e049ae80ca5ef965d3b8fae98fdd: UBUNTU: Ubuntu-nvidia-5.15.0-1020.20 (2023-04-09 21:13:44 -0700) are
[Kernel-packages] [Bug 2015755] [NEW] Pull-request to address mgbe ethernet driver on AGX Orin
Public bug reported: [Impact] This patch set is intended to address https://bugs.launchpad.net/riverside/+bug/2011636 ** Affects: linux-nvidia (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia in Ubuntu. https://bugs.launchpad.net/bugs/2015755 Title: Pull-request to address mgbe ethernet driver on AGX Orin Status in linux-nvidia package in Ubuntu: New Bug description: [Impact] This patch set is intended to address https://bugs.launchpad.net/riverside/+bug/2011636 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia/+bug/2015755/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2012939] [NEW] Pull-request to address a number of issues in the nvidia-tegra -1010.10
Public bug reported: [Impact] Adding these patches address a number of differences between the Ubuntu kernel and the internal NVIDIA kernel. [Fix] These patches do not constitute a single fix or a set of fixes for bugs but instead enable kernel functionality as well as fix kernel bugs related to Nvidia HW. ** Affects: linux-nvidia (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia in Ubuntu. https://bugs.launchpad.net/bugs/2012939 Title: Pull-request to address a number of issues in the nvidia-tegra -1010.10 Status in linux-nvidia package in Ubuntu: New Bug description: [Impact] Adding these patches address a number of differences between the Ubuntu kernel and the internal NVIDIA kernel. [Fix] These patches do not constitute a single fix or a set of fixes for bugs but instead enable kernel functionality as well as fix kernel bugs related to Nvidia HW. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia/+bug/2012939/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2010997] Re: Pull-Request to address USB and PWM cooling fan issues with Orin HW
** Description changed: - [Impact] - Adding this patch addresses a specific audio issue with the nvidia-tegra kernel. + [Impact] + Adding this patch addresses USB and PWM cooling fan issues as described in the following bugs: - https://bugs.launchpad.net/riverside/+bug/2009867 - https://bugs.launchpad.net/riverside/+bug/2002173 + https://bugs.launchpad.net/riverside/+bug/2009867 + https://bugs.launchpad.net/riverside/+bug/2002173 - [Fix] - The PR is made up of a revert of one commit and the application of 4 new patches from upstream to address the indicated issues. + Â [Fix] + The PR is made up of a revert of one commit and the application of 4 new patches from upstream to address the indicated issues. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia in Ubuntu. https://bugs.launchpad.net/bugs/2010997 Title: Pull-Request to address USB and PWM cooling fan issues with Orin HW Status in linux-nvidia package in Ubuntu: New Bug description: [Impact] Adding this patch addresses USB and PWM cooling fan issues as described in the following bugs: https://bugs.launchpad.net/riverside/+bug/2009867 https://bugs.launchpad.net/riverside/+bug/2002173 Â [Fix] The PR is made up of a revert of one commit and the application of 4 new patches from upstream to address the indicated issues. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia/+bug/2010997/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2010997] [NEW] Pull-Request to address USB and PWM cooling fan issues with Orin HW
Public bug reported: [Impact] Adding this patch addresses a specific audio issue with the nvidia-tegra kernel. https://bugs.launchpad.net/riverside/+bug/2009867 https://bugs.launchpad.net/riverside/+bug/2002173 [Fix] The PR is made up of a revert of one commit and the application of 4 new patches from upstream to address the indicated issues. ** Affects: linux-nvidia (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia in Ubuntu. https://bugs.launchpad.net/bugs/2010997 Title: Pull-Request to address USB and PWM cooling fan issues with Orin HW Status in linux-nvidia package in Ubuntu: New Bug description: [Impact] Adding this patch addresses a specific audio issue with the nvidia-tegra kernel. https://bugs.launchpad.net/riverside/+bug/2009867 https://bugs.launchpad.net/riverside/+bug/2002173 [Fix] The PR is made up of a revert of one commit and the application of 4 new patches from upstream to address the indicated issues. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia/+bug/2010997/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008921] [NEW] Please apply the indicated patch to address an audio issue with the tegra kernel
Public bug reported: [Impact] Adding this patch addresses a specific audio issue with the tegra kernel. [Fix] ASoC: simple-card-utils: Increase maximum DAI links limit to 512 The current limit of 128 is not sufficient when more components are added to the audio map on Tegra210 and later platforms. Thus it is resulting in probe failure. The requirement is of nearly ~200 DAI links. To give sufficient room for future additions the maximum limit is increased to 512 DAI links. This is a preparatory patch to add more components like resampler, mixer, multiplexers, demultiplexers and volume controllers to Tegra210 and later platforms. This is upstream commit 7a226f2eabdc2e839d8f07c5ce087136f9c0f35c ** Affects: linux-nvidia (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia in Ubuntu. https://bugs.launchpad.net/bugs/2008921 Title: Please apply the indicated patch to address an audio issue with the tegra kernel Status in linux-nvidia package in Ubuntu: New Bug description: [Impact] Adding this patch addresses a specific audio issue with the tegra kernel. [Fix] ASoC: simple-card-utils: Increase maximum DAI links limit to 512 The current limit of 128 is not sufficient when more components are added to the audio map on Tegra210 and later platforms. Thus it is resulting in probe failure. The requirement is of nearly ~200 DAI links. To give sufficient room for future additions the maximum limit is increased to 512 DAI links. This is a preparatory patch to add more components like resampler, mixer, multiplexers, demultiplexers and volume controllers to Tegra210 and later platforms. This is upstream commit 7a226f2eabdc2e839d8f07c5ce087136f9c0f35c To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia/+bug/2008921/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008795] [NEW] Please apply yet another set of Orin, platform enablement patches
Public bug reported: [Impact] Adding these patches enables additional functionality and addresses bugs related to the Ubuntu kernel on Orin reference HW. [Fix] These patches do not constitute a single fix or a set of fixes for bugs but instead enable kernel functionality as well as fix kernel bugs related to Nvidia HW. ** Affects: linux-nvidia (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia in Ubuntu. https://bugs.launchpad.net/bugs/2008795 Title: Please apply yet another set of Orin, platform enablement patches Status in linux-nvidia package in Ubuntu: New Bug description: [Impact] Adding these patches enables additional functionality and addresses bugs related to the Ubuntu kernel on Orin reference HW. [Fix] These patches do not constitute a single fix or a set of fixes for bugs but instead enable kernel functionality as well as fix kernel bugs related to Nvidia HW. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia/+bug/2008795/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008503] [NEW] Please apply another batch of Orin platform enablement patches
Public bug reported: [Impact] Adding these patches enables additional functionality and addresses bugs related to the Ubuntu kernel on Orin reference HW. [Fix] These patches do not constitute a single fix or a set of fixes for bugs but instead enable kernel functionality as well as fix kernel bugs related to Nvidia HW. ** Affects: linux-nvidia (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia in Ubuntu. https://bugs.launchpad.net/bugs/2008503 Title: Please apply another batch of Orin platform enablement patches Status in linux-nvidia package in Ubuntu: New Bug description: [Impact] Adding these patches enables additional functionality and addresses bugs related to the Ubuntu kernel on Orin reference HW. [Fix] These patches do not constitute a single fix or a set of fixes for bugs but instead enable kernel functionality as well as fix kernel bugs related to Nvidia HW. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia/+bug/2008503/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2003728] [NEW] Enable MGBE ethernet on Orin platforms
Public bug reported: [Impact] Adding these patches enables additional functionality and addresses bugs related to the Ubuntu kernel on Orin reference HW. Specifically these 3 patches (2 cherry-picks and 1 backport) add the MGBE driver. [Fix] These patches do not constitute a single fix or a set of fixes for bugs but instead enable kernel functionality as well as fix kernel bugs related to Nvidia HW. ** Affects: linux-nvidia (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia in Ubuntu. https://bugs.launchpad.net/bugs/2003728 Title: Enable MGBE ethernet on Orin platforms Status in linux-nvidia package in Ubuntu: New Bug description: [Impact] Adding these patches enables additional functionality and addresses bugs related to the Ubuntu kernel on Orin reference HW. Specifically these 3 patches (2 cherry-picks and 1 backport) add the MGBE driver. [Fix] These patches do not constitute a single fix or a set of fixes for bugs but instead enable kernel functionality as well as fix kernel bugs related to Nvidia HW. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia/+bug/2003728/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2003640] [NEW] Integrate NVIDIA Grace kernel fixes for vGIC
Public bug reported: [Impact] To save the vgic LPI pending state with GICv4.1, the VPEs must all be unmapped from the ITSs so that the sGIC caches can be flushed. The opposite is done once the state is saved. This is all done by using the activate/deactivate irqdomain callbacks directly from the vgic code. Crutially, this is done without holding the irqdesc lock for the interrupts that represent the VPE. And these callbacks are changing the state of the irqdesc. What could possibly go wrong? If a doorbell fires while we are messing with the irqdesc state, it will acquire the lock and change the interrupt state concurrently. Since we don't hole the lock, curruption occurs in on the interrupt state. Oh well. While acquiring the lock would fix this (and this was Shanker's initial approach), this is still a layering violation we could do without. A better approach is actually to free the VPE interrupt, do what we have to do, and re-request it. It is more work, but this usually happens only once in the lifetime of the VM and we don't really care about this sort of overhead. The upstream maintainer acknowledged the bug, fixed the issue. and it will be available in v6.2. [Fixes] - single patch to address the race condition on VPE activation/deactivation ** Affects: linux-nvidia-5.19 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2003640 Title: Integrate NVIDIA Grace kernel fixes for vGIC Status in linux-nvidia-5.19 package in Ubuntu: New Bug description: [Impact] To save the vgic LPI pending state with GICv4.1, the VPEs must all be unmapped from the ITSs so that the sGIC caches can be flushed. The opposite is done once the state is saved. This is all done by using the activate/deactivate irqdomain callbacks directly from the vgic code. Crutially, this is done without holding the irqdesc lock for the interrupts that represent the VPE. And these callbacks are changing the state of the irqdesc. What could possibly go wrong? If a doorbell fires while we are messing with the irqdesc state, it will acquire the lock and change the interrupt state concurrently. Since we don't hole the lock, curruption occurs in on the interrupt state. Oh well. While acquiring the lock would fix this (and this was Shanker's initial approach), this is still a layering violation we could do without. A better approach is actually to free the VPE interrupt, do what we have to do, and re-request it. It is more work, but this usually happens only once in the lifetime of the VM and we don't really care about this sort of overhead. The upstream maintainer acknowledged the bug, fixed the issue. and it will be available in v6.2. [Fixes] - single patch to address the race condition on VPE activation/deactivation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-5.19/+bug/2003640/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2002574] [NEW] Integrate Nvidia Grace kernel fixes for TPM
Public bug reported: [Impact] Adding these patches enables additional functionality and addresses bugs related to the Ubuntu kernel on Grace reference HW [Fixes] - 2 patches to address issues with the TPM module used with Grace systems ** Affects: linux-nvidia-5.19 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2002574 Title: Integrate Nvidia Grace kernel fixes for TPM Status in linux-nvidia-5.19 package in Ubuntu: New Bug description: [Impact] Adding these patches enables additional functionality and addresses bugs related to the Ubuntu kernel on Grace reference HW [Fixes] - 2 patches to address issues with the TPM module used with Grace systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-5.19/+bug/2002574/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2001557] [NEW] Integrate Nvidia Orin enablement patches
Public bug reported: [Impact] Adding these patches enables additional functionality and addresses bugs related to the Ubuntu kernel on Orin reference HW [Fix] These patches do not constitute a single fix or a set of fixes for bugs but instead enable kernel functionality as well as fix kernel bugs related to Nvidia HW. ** Affects: linux-nvidia (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia in Ubuntu. https://bugs.launchpad.net/bugs/2001557 Title: Integrate Nvidia Orin enablement patches Status in linux-nvidia package in Ubuntu: New Bug description: [Impact] Adding these patches enables additional functionality and addresses bugs related to the Ubuntu kernel on Orin reference HW [Fix] These patches do not constitute a single fix or a set of fixes for bugs but instead enable kernel functionality as well as fix kernel bugs related to Nvidia HW. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia/+bug/2001557/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998380] Re: Integrate ARM64 Performance Monitoring Unit Table patches
** Information type changed from Private to Public -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia in Ubuntu. https://bugs.launchpad.net/bugs/1998380 Title: Integrate ARM64 Performance Monitoring Unit Table patches Status in linux-nvidia package in Ubuntu: New Bug description: There are a set of patches on linux-next upstream that are required as part of NVIDIA SOC enablement. These patches need to be integrated into the Optimized linux-nvidia-5.19 kernel. ARM Performance Monitoring Unit Table describes the properties of PMU support in ARM-based system. The APMT table contains a list of nodes, each represents a PMU in the system that conforms to ARM CoreSight PMU architecture. The properties of each node include information required to access the PMU (e.g. MMIO base address, interrupt number) and also identification. For more detailed information, please refer to the specification below: * APMT: https://developer.arm.com/documentation/den0117/latest * ARM Coresight PMU: https://developer.arm.com/documentation/ihi0091/latest The initial support adds the detection of APMT table and generic infrastructure to create platform devices for ARM CoreSight PMUs. Similar to IORT the root pointer of APMT is preserved during runtime and each PMU platform device is given a pointer to the corresponding APMT node. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia/+bug/1998380/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998527] Re: Integrate ARM64 Tegra SPI & QSPI changes
** Information type changed from Private to Public -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia in Ubuntu. https://bugs.launchpad.net/bugs/1998527 Title: Integrate ARM64 Tegra SPI & QSPI changes Status in linux-nvidia package in Ubuntu: New Bug description: There are 5 commits that went upstream post 5.19 that are required for NVIDIA SOC enablement. Please integrate these patches into the linux- nvidia-5.19 kernel. The following patches are in linux-next: b76134178168b5104851b3c72d9b1092b7414ff9 spi: tegra210-quad: Multi-cs support 8777dd9dff4020bba66654ec92e4b0ab6367ad30 spi: tegra210-quad: Fix combined sequence ae4b3c1252f0fd0951d2f072a02ba46cac8d6c92 spi: tegra210-quad: Don't initialise DMA if not supported 2197aa6b0aa236b9896a09b9d08d6924d18b84f6 spi: tegra210-quad: Fix duplicate resource error 0ddf10a319f14ed626dab3a2d390e5059e20cea5 arm64: tegra: Enable Tegra SPI & QSPI in deconfig To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia/+bug/1998527/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998527] [NEW] Integrate ARM64 Tegra SPI & QSPI changes
Private bug reported: There are 4 commits that went upstream post 5.19 that are required for NVIDIA SOC enablement. Please integrate these patches into the linux- nvidia-5.19 kernel. The following patches are in linux-next: ** Affects: linux-nvidia (Ubuntu) Importance: Undecided Status: New ** Information type changed from Public to Private -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia in Ubuntu. https://bugs.launchpad.net/bugs/1998527 Title: Integrate ARM64 Tegra SPI & QSPI changes Status in linux-nvidia package in Ubuntu: New Bug description: There are 4 commits that went upstream post 5.19 that are required for NVIDIA SOC enablement. Please integrate these patches into the linux- nvidia-5.19 kernel. The following patches are in linux-next: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia/+bug/1998527/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998392] Re: Integrate IOMMU patches related to NVIDIA SOC development
** Description changed: There are 4 commits that went upstream post 5.19 that are required for NVIDIA SOC enablement. Please integrate these patches into the linux- nvidia-5.19 kernel. + + + The following patches are in linux-next: + 00208852d351ca6e4a8b9ff0c5376fa3a8ed8eaa iommu: Add return value rules to attach_dev op and APIs + bd7ebb7719356d750b1b4d671535922bae43fb3b iommu: Regulate EINVAL in ->attach_dev callback functions + f4a14773579302e5f0c4bf80b03f0db7ce67f2ce iommu: Use EINVAL for incompatible device/domain in ->attach_dev + 04cee82e04d2aff3d177ef0021ecdff228daf7b8 iommu: Propagate return value in ->attach_dev callback functions -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia in Ubuntu. https://bugs.launchpad.net/bugs/1998392 Title: Integrate IOMMU patches related to NVIDIA SOC development Status in linux-nvidia package in Ubuntu: New Bug description: There are 4 commits that went upstream post 5.19 that are required for NVIDIA SOC enablement. Please integrate these patches into the linux- nvidia-5.19 kernel. The following patches are in linux-next: 00208852d351ca6e4a8b9ff0c5376fa3a8ed8eaa iommu: Add return value rules to attach_dev op and APIs bd7ebb7719356d750b1b4d671535922bae43fb3b iommu: Regulate EINVAL in ->attach_dev callback functions f4a14773579302e5f0c4bf80b03f0db7ce67f2ce iommu: Use EINVAL for incompatible device/domain in ->attach_dev 04cee82e04d2aff3d177ef0021ecdff228daf7b8 iommu: Propagate return value in ->attach_dev callback functions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia/+bug/1998392/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998392] [NEW] Integrate IOMMU patches related to NVIDIA SOC development
Public bug reported: There are 4 commits that went upstream post 5.19 that are required for NVIDIA SOC enablement. Please integrate these patches into the linux- nvidia-5.19 kernel. ** Affects: linux-nvidia (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia in Ubuntu. https://bugs.launchpad.net/bugs/1998392 Title: Integrate IOMMU patches related to NVIDIA SOC development Status in linux-nvidia package in Ubuntu: New Bug description: There are 4 commits that went upstream post 5.19 that are required for NVIDIA SOC enablement. Please integrate these patches into the linux- nvidia-5.19 kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia/+bug/1998392/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998380] [NEW] Integrate ARM64 Performance Monitoring Unit Table patches
Private bug reported: There are a set of patches on linux-next upstream that are required as part of NVIDIA SOC enablement. These patches need to be integrated into the Optimized linux-nvidia-5.19 kernel. ** Affects: linux-nvidia (Ubuntu) Importance: Undecided Status: New ** Information type changed from Public to Private -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia in Ubuntu. https://bugs.launchpad.net/bugs/1998380 Title: Integrate ARM64 Performance Monitoring Unit Table patches Status in linux-nvidia package in Ubuntu: New Bug description: There are a set of patches on linux-next upstream that are required as part of NVIDIA SOC enablement. These patches need to be integrated into the Optimized linux-nvidia-5.19 kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia/+bug/1998380/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1895470] Re: fatal error: classmap.h: No such file or directory
** Package changed: linux-kernel-headers (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1895470 Title: fatal error: classmap.h: No such file or directory Status in linux package in Ubuntu: Fix Released Bug description: When building kernel module on ubuntu 20.04 for raspberry (arm64), I get the following error: make -C /lib/modules/5.4.0-1018-raspi/build SUBDIRS=/home/ubuntu/andor/src/driver modules make[1]: Entering directory '/usr/src/linux-headers-5.4.0-1018-raspi' HOSTCC scripts/selinux/genheaders/genheaders scripts/selinux/genheaders/genheaders.c:18:10: fatal error: classmap.h: No such file or directory 18 | #include "classmap.h" | ^~~~ compilation terminated. make[4]: *** [scripts/Makefile.host:107: scripts/selinux/genheaders/genheaders] Error 1 make[3]: *** [scripts/Makefile.build:522: scripts/selinux/genheaders] Error 2 make[2]: *** [scripts/Makefile.build:522: scripts/selinux] Error 2 make[1]: *** [Makefile:1127: scripts] Error 2 make[1]: Leaving directory '/usr/src/linux-headers-5.4.0-1018-raspi' make: *** [Makefile:12: default] Error 2 I have no clue how to resolve this To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895470/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1995023] [NEW] Integrate Nvidia Orin Audio, cpu frequency and other enablement patches
Private bug reported: [Impact] Adding these patches enables the Ubuntu kernel on Orin reference HW [Fix] These patches do not constitute a single fix or a set of fixes for bugs but instead enable kernel functionality on Nvidia HW. ** Affects: linux-nvidia (Ubuntu) Importance: Undecided Status: New ** Information type changed from Public to Private -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia in Ubuntu. https://bugs.launchpad.net/bugs/1995023 Title: Integrate Nvidia Orin Audio, cpu frequency and other enablement patches Status in linux-nvidia package in Ubuntu: New Bug description: [Impact] Adding these patches enables the Ubuntu kernel on Orin reference HW [Fix] These patches do not constitute a single fix or a set of fixes for bugs but instead enable kernel functionality on Nvidia HW. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia/+bug/1995023/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1983215] [NEW] bjf test
Public bug reported: This is just a test ** Affects: linux-nvidia (Ubuntu) Importance: Undecided Status: Invalid ** Also affects: linux-nvidia (Ubuntu Jammy) Importance: Undecided Status: New ** No longer affects: linux-nvidia (Ubuntu Jammy) ** Changed in: linux-nvidia (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia in Ubuntu. https://bugs.launchpad.net/bugs/1983215 Title: bjf test Status in linux-nvidia package in Ubuntu: Invalid Bug description: This is just a test To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia/+bug/1983215/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1983190] [NEW] bjf test
Public bug reported: bjf test ** Affects: linux-nvidia (Ubuntu) Importance: Undecided Status: Invalid ** Changed in: linux-nvidia (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia in Ubuntu. https://bugs.launchpad.net/bugs/1983190 Title: bjf test Status in linux-nvidia package in Ubuntu: Invalid Bug description: bjf test To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia/+bug/1983190/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1982519] Re: GDS: Add NFS patches to optimized kernel
** Also affects: linux-nvidia (Ubuntu Jammy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia in Ubuntu. https://bugs.launchpad.net/bugs/1982519 Title: GDS: Add NFS patches to optimized kernel Status in linux-nvidia package in Ubuntu: New Status in linux-nvidia source package in Jammy: New Bug description: [Impact] Adding these changes will enable GDS functionality NFS drivers. [Fix] This is a not a fix but a new feature being to NFS driver. [Test] Tested the NFS driver on a hpe system as I did not have a setup with BASEOS6. 1) Installed 5.15.39 kernel on the system (this is the kernel that optimized kernel is on currently). 2) Downloaded the optimized kernel. 3) Applied the patches to the optimized kernel 4) Replaced the NFS modules on the system with the one's built on optimized kernel. 5) Ran gds and compat mode tests on a NFS mount with the patched NFS driver. All tests went fine. Attaching the results Compat mode tests == ** API Tests, : 72 / 72 tests passed ** Testsuite : 211 / 211 tests passed done tests:Thu Jul 21 08:27:58 PM UTC 2022 GDS mode tests == ** NVFS IOCTL negative Tests, : 23 / 23 tests passed ** Testsuite : 249 / 249 tests passed End: nvidia-fs: GDS Version: 1.4.0.31 NVFS statistics(ver: 4.0) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia/+bug/1982519/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1982519] [NEW] GDS: Add NFS patches to optimized kernel
Public bug reported: [Impact] Adding these changes will enable GDS functionality NFS drivers. [Fix] This is a not a fix but a new feature being to NFS driver. [Test] Tested the NFS driver on a hpe system as I did not have a setup with BASEOS6. 1) Installed 5.15.39 kernel on the system (this is the kernel that optimized kernel is on currently). 2) Downloaded the optimized kernel. 3) Applied the patches to the optimized kernel 4) Replaced the NFS modules on the system with the one's built on optimized kernel. 5) Ran gds and compat mode tests on a NFS mount with the patched NFS driver. All tests went fine. Attaching the results Compat mode tests == ** API Tests, : 72 / 72 tests passed ** Testsuite : 211 / 211 tests passed done tests:Thu Jul 21 08:27:58 PM UTC 2022 GDS mode tests == ** NVFS IOCTL negative Tests, : 23 / 23 tests passed ** Testsuite : 249 / 249 tests passed End: nvidia-fs: GDS Version: 1.4.0.31 NVFS statistics(ver: 4.0) ** Affects: linux-nvidia (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia in Ubuntu. https://bugs.launchpad.net/bugs/1982519 Title: GDS: Add NFS patches to optimized kernel Status in linux-nvidia package in Ubuntu: New Bug description: [Impact] Adding these changes will enable GDS functionality NFS drivers. [Fix] This is a not a fix but a new feature being to NFS driver. [Test] Tested the NFS driver on a hpe system as I did not have a setup with BASEOS6. 1) Installed 5.15.39 kernel on the system (this is the kernel that optimized kernel is on currently). 2) Downloaded the optimized kernel. 3) Applied the patches to the optimized kernel 4) Replaced the NFS modules on the system with the one's built on optimized kernel. 5) Ran gds and compat mode tests on a NFS mount with the patched NFS driver. All tests went fine. Attaching the results Compat mode tests == ** API Tests, : 72 / 72 tests passed ** Testsuite : 211 / 211 tests passed done tests:Thu Jul 21 08:27:58 PM UTC 2022 GDS mode tests == ** NVFS IOCTL negative Tests, : 23 / 23 tests passed ** Testsuite : 249 / 249 tests passed End: nvidia-fs: GDS Version: 1.4.0.31 NVFS statistics(ver: 4.0) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia/+bug/1982519/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1982518] [NEW] NVMe/MVMEeOF: Patch NVMe/NVMeOF driver to support GDS
Public bug reported: [Impact] Adding these changes will enable GDS functionality for NVMe and NVMeOF drivers. [Fix] This is a not a fix but a new feature being added to NVMe and NVMeOF driver. [Test] Tested the NVMe driver on a hpe system as I did not have a setup with BASEOS6. 1) Installed 5.15.39 kernel on the system (this is the kernel that optimized kernel is on currently). 2) Downloaded the optimized kernel. 3) Applied the patches to the optimized kernel 4) Replaced the nvme modules on the system with the one's built on optimized kernel. 5) Ran gds tests on ext4 file system with the patched NVMe driver. All tests went fine. 6) The boot drive is on NVMe and the system is up and running which indicates no regression on the standard NVMe path as well. Attached are the results with NVMe ** NVFS IOCTL negative Tests, : 23 / 23 tests passed ** Testsuite : 249 / 249 tests passed End: nvidia-fs: GDS Version: 1.4.0.31 NVFS statistics(ver: 4.0) NVFS Driver(version: 2.13.5) Mellanox PeerDirect Supported: False IO stats: Disabled, peer IO stats: Disabled Logging level: info Compat mode Tests == ** API Tests, : 72 / 72 tests passed ** Testsuite : 211 / 211 tests passed done tests:Thu Jul 21 08:12:09 PM UTC 2022 Could not test the same with NVMeOF as a setup was not available. ** Affects: linux-nvidia (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia in Ubuntu. https://bugs.launchpad.net/bugs/1982518 Title: NVMe/MVMEeOF: Patch NVMe/NVMeOF driver to support GDS Status in linux-nvidia package in Ubuntu: New Bug description: [Impact] Adding these changes will enable GDS functionality for NVMe and NVMeOF drivers. [Fix] This is a not a fix but a new feature being added to NVMe and NVMeOF driver. [Test] Tested the NVMe driver on a hpe system as I did not have a setup with BASEOS6. 1) Installed 5.15.39 kernel on the system (this is the kernel that optimized kernel is on currently). 2) Downloaded the optimized kernel. 3) Applied the patches to the optimized kernel 4) Replaced the nvme modules on the system with the one's built on optimized kernel. 5) Ran gds tests on ext4 file system with the patched NVMe driver. All tests went fine. 6) The boot drive is on NVMe and the system is up and running which indicates no regression on the standard NVMe path as well. Attached are the results with NVMe ** NVFS IOCTL negative Tests, : 23 / 23 tests passed ** Testsuite : 249 / 249 tests passed End: nvidia-fs: GDS Version: 1.4.0.31 NVFS statistics(ver: 4.0) NVFS Driver(version: 2.13.5) Mellanox PeerDirect Supported: False IO stats: Disabled, peer IO stats: Disabled Logging level: info Compat mode Tests == ** API Tests, : 72 / 72 tests passed ** Testsuite : 211 / 211 tests passed done tests:Thu Jul 21 08:12:09 PM UTC 2022 Could not test the same with NVMeOF as a setup was not available. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia/+bug/1982518/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1929892] Re: [TGL] enable USB-dw3
We get this for free with the move to a 5.13 based focal:linux-intel kernel. ** Changed in: intel Status: New => Invalid ** Changed in: linux-intel (Ubuntu) Status: In Progress => Invalid ** Changed in: intel Assignee: (unassigned) => Brad Figg (brad-figg) ** Changed in: linux-intel (Ubuntu) Assignee: Hsuan-Yu Lin (shanelin) => Brad Figg (brad-figg) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel in Ubuntu. https://bugs.launchpad.net/bugs/1929892 Title: [TGL] enable USB-dw3 Status in intel: Invalid Status in linux package in Ubuntu: Incomplete Status in linux-intel package in Ubuntu: Invalid Bug description: Description Enable USB-dw3 for Tiger Lake Hardware: Tiger Lake Target Release: 21.04 Target Kernel: TBD External links: https://github.com/intel/linux-intel-quilt/tree/mainline-tracking-v5.11-yocto-210223T083754Z To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1929892/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1929901] Re: [EHL][TGL] EDAC support
This commit already exists in the focal:linux-intel intel-5.13-next. ** Changed in: intel Status: New => Fix Committed ** Changed in: intel Assignee: (unassigned) => Brad Figg (brad-figg) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel in Ubuntu. https://bugs.launchpad.net/bugs/1929901 Title: [EHL][TGL] EDAC support Status in intel: Fix Committed Status in linux package in Ubuntu: Incomplete Status in linux-intel package in Ubuntu: Fix Committed Bug description: Description EDAC driver support on EHL & TGL for reporting ECC error and DIMM location Hardware: Tiger Lake & Elkhart Lake Target Release: 21.04 Target Kernel: TBD External links: https://github.com/intel/linux-intel-quilt/tree/mainline-tracking-v5.11-yocto-210223T083754Z To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1929901/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1938408] Re: [ehl] board does not support soft reboot
** Summary changed: - EHL board does not support soft reboot + [ehl] board does not support soft reboot -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel in Ubuntu. https://bugs.launchpad.net/bugs/1938408 Title: [ehl] board does not support soft reboot Status in intel: Fix Committed Status in linux-intel package in Ubuntu: Fix Committed Bug description: [Summary]Telling the EHL board to reboot from within Ubuntu causes it to hang, forcing you to do a hard reboot. [Steps to reproduce] 1. Open terminal window. 2. $ reboot [Expected result] System should gracefullyl reboot. [Actual result] Screen goes blank except for a cursor. System does not reboot. You must hard reboot (pull the plug) [Failure rate]100% [Additional information] CID: 202105-29063 SKU: system-manufacturer: Intel Corporation system-product-name: Elkhart Lake Embedded Platform bios-version: EHLSFWI1.R00.2091.A00.2002250754 CPU: Genuine Intel(R) CPU @ 1.90GHz (4x) GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:4571] kernel-version: 5.11.0-1009-intel To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1938408/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1938413] Re: [ehl] Shutdown hangs on board
** Summary changed: - Shutdown hangs on EHL board + [ehl] Shutdown hangs on board -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel in Ubuntu. https://bugs.launchpad.net/bugs/1938413 Title: [ehl] Shutdown hangs on board Status in intel: Fix Committed Status in linux-intel package in Ubuntu: Fix Committed Bug description: [Summary]Go to Power -> Shutdown and the screen goes blank, but the system does not shut down. You cannot recover and have to perform a hard reboot. [Steps to reproduce] 1. Boot up Ubuntu 2. Power -> Shutdown (click ok) [Expected result] System should cleanly shut down. [Actual result] Screen blanks with a blinking cursor, the system does not shut down, the fan is still on. System is unresponsive, forcing you to do a hard reset. [Failure rate]100% [Additional information] CID: 20215-29063 SKU: system-manufacturer: Intel Corporation system-product-name: Elkhart Lake Embedded Platform bios-version: EHLSFWI1.R00.2091.A00.2002250754 CPU: Genuine Intel(R) CPU @ 1.90GHz (4x) GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:4571] kernel-version: 5.11.0-1009-intel [Stage] Device froze, issue reported and logs collected right after a reboot To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1938413/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1938413] Re: Shutdown hangs on EHL board
** Changed in: intel Status: New => Fix Committed ** Tags added: lookout-canyon -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel in Ubuntu. https://bugs.launchpad.net/bugs/1938413 Title: Shutdown hangs on EHL board Status in intel: Fix Committed Status in linux-intel package in Ubuntu: Fix Committed Bug description: [Summary]Go to Power -> Shutdown and the screen goes blank, but the system does not shut down. You cannot recover and have to perform a hard reboot. [Steps to reproduce] 1. Boot up Ubuntu 2. Power -> Shutdown (click ok) [Expected result] System should cleanly shut down. [Actual result] Screen blanks with a blinking cursor, the system does not shut down, the fan is still on. System is unresponsive, forcing you to do a hard reset. [Failure rate]100% [Additional information] CID: 20215-29063 SKU: system-manufacturer: Intel Corporation system-product-name: Elkhart Lake Embedded Platform bios-version: EHLSFWI1.R00.2091.A00.2002250754 CPU: Genuine Intel(R) CPU @ 1.90GHz (4x) GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:4571] kernel-version: 5.11.0-1009-intel [Stage] Device froze, issue reported and logs collected right after a reboot To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1938413/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1929902] Re: [EHL] enable USB-dw3
** Changed in: intel Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel in Ubuntu. https://bugs.launchpad.net/bugs/1929902 Title: [EHL] enable USB-dw3 Status in intel: Fix Committed Status in linux package in Ubuntu: New Status in linux-intel package in Ubuntu: Fix Committed Bug description: Description Enable USB-dw3 for Elkhart Lake Hardware: Elkhart Lake Target Release: 21.04 Target Kernel: TBD External links: https://github.com/intel/linux-intel-quilt/tree/mainline-tracking-v5.11-yocto-210223T083754Z To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1929902/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1938408] Re: EHL board does not support soft reboot
** Changed in: intel Status: New => Fix Committed ** Tags added: lookout-canyon -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel in Ubuntu. https://bugs.launchpad.net/bugs/1938408 Title: EHL board does not support soft reboot Status in intel: Fix Committed Status in linux-intel package in Ubuntu: Fix Committed Bug description: [Summary]Telling the EHL board to reboot from within Ubuntu causes it to hang, forcing you to do a hard reboot. [Steps to reproduce] 1. Open terminal window. 2. $ reboot [Expected result] System should gracefullyl reboot. [Actual result] Screen goes blank except for a cursor. System does not reboot. You must hard reboot (pull the plug) [Failure rate]100% [Additional information] CID: 202105-29063 SKU: system-manufacturer: Intel Corporation system-product-name: Elkhart Lake Embedded Platform bios-version: EHLSFWI1.R00.2091.A00.2002250754 CPU: Genuine Intel(R) CPU @ 1.90GHz (4x) GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:4571] kernel-version: 5.11.0-1009-intel To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1938408/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1912752] Re: linux-uc20-efi: megaraid_sas required in the initrd
** Changed in: linux (Ubuntu Focal) Importance: Undecided => Critical ** Changed in: linux (Ubuntu) Importance: Undecided => Critical -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1912752 Title: linux-uc20-efi: megaraid_sas required in the initrd Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: In Progress Bug description: == Impact == Dell R340 fails to boot with UC20 pc-kernel snap because of unable to find the storage device. == Fix == In this case, storage disks are connected through a controller enabled by kernel module megaraid_sas, hence the module must be presented in the initrd in order to make the system boot. == Risk of Regression == Low. We're only adding an existing module into the initrd. The only downside may be the small increase of the snap size. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1912752/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1885030] Re: [Intel] Add Error Disconnect Recover support
Based on this evaluation we have no plans at this time to backport these patches to the Focal 5.4 kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1885030 Title: [Intel] Add Error Disconnect Recover support Status in intel: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Focal: Incomplete Status in linux source package in Groovy: Incomplete Bug description: As per the following PCIe spec ECNs, implement EDR support in Linux kernel and upstream it. https://members.pcisig.com/wg/PCI-SIG/document/14076 https://members.pcisig.com/wg/PCI-SIG/document/12888 Patchset (Merged 5.7 mainline): 894020fdd88c PCI/AER: Rationalize error status register clearing ac1c8e35a326 PCI/DPC: Add Error Disconnect Recover (EDR) support aea47413e7ce PCI/DPC: Expose dpc_process_error(), dpc_reset_link() for use by EDR 20e15e673b05 PCI/AER: Add pci_aer_raw_clear_status() to unconditionally clear Error Status 27005618178e PCI/DPC: Cache DPC capabilities in pci_init_capabilities() e8e5ff2aeec1 PCI/ERR: Return status of pcie_do_recovery() b6cf1a42f916 PCI/ERR: Remove service dependency in pcie_do_recovery() be06c1b42eea PCI/DPC: Move DPC data into struct pci_dev 6d2c89441571 PCI/ERR: Update error status after reset_link() b5dfbeacf748 PCI/ERR: Combine pci_channel_io_frozen cases To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1885030/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1885030] Re: [Intel] Add Error Disconnect Recover support
The following evaluation was done in early May In summary, EDR is brand new in upstream kernels and to my knowledge has not been exercised in-house at Canonical, and may be difficult to test due to a lack of systems with EDR functionality in their firmware. I am unsure as to what the state of regression testing is with regards to this type of PCI functionality. Some followup patches and discussion after the original EDR submission are below. To be clear, these are not part of the request from Nvidia. These are upstream followups to the EDR patch set, and are indicative of the final state of this functionality still being in flux. https://lore.kernel.org/linux-pci/1588272369-2145-1-git-send-email-jonathan.derr...@intel.com/ The above is unapplied upstream; it is proposed to fix an issue with the negotiation between the operating system and firmware for control for DPC, and as of 1 May 2020 is pending waiting for https://lore.kernel.org/linux-pci/67af2931705bed9a588b5a39d369cb70b9942190.1587925636.git.sathyanarayanan.kuppusw...@linux.intel.com/ to be sorted out. This patch (which is applied upstream to pci git tree for merging in 5.8) relates to how the operating system and firmware negotiate control of AER and DPC via the "firmware first" bit in the ACPI HEST vs. using the _OSC ACPI method. Prior to this patch, the ACPI HEST
[Kernel-packages] [Bug 1842107] Re: [EHL][OSE] I2C implementation
These commits are in the 20.04 release kernel. ** Changed in: linux (Ubuntu) Status: Triaged => Fix Released ** Changed in: intel Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1842107 Title: [EHL][OSE] I2C implementation Status in intel: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: Description: Elkhart Lake has Offload Services Engine (OSE) that will be BIOS configurable either to have some RTOS take control of its IO blocks or hand them off to running OS. IoTG has asked to support I2C. This should be based on Synopsys v2.00a specification Target Release: 20.04 Target Kernel: TBD To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1842107/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1842142] Re: [EHL][OSE] SPI implementation
This commit is in the released 20.04 kernel ** Changed in: linux (Ubuntu) Status: Triaged => Fix Released ** Changed in: intel Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1842142 Title: [EHL][OSE] SPI implementation Status in intel: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: Description: Elkhart Lake has Offload Services Engine (OSE) that will be BIOS configurable either to have some RTOS take control of its IO blocks or hand them off to running OS. IoTG has asked to support SPI. This should be based on Synopsys v3.23a specification. To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1842142/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1842107] Re: [EHL][OSE] I2C implementation
** Changed in: linux (Ubuntu) Status: Incomplete => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1842107 Title: [EHL][OSE] I2C implementation Status in intel: Fix Committed Status in linux package in Ubuntu: Triaged Bug description: Description: Elkhart Lake has Offload Services Engine (OSE) that will be BIOS configurable either to have some RTOS take control of its IO blocks or hand them off to running OS. IoTG has asked to support I2C. This should be based on Synopsys v2.00a specification Target Release: 20.04 Target Kernel: TBD To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1842107/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1842142] Re: [EHL][OSE] SPI implementation
** Changed in: linux (Ubuntu) Status: Incomplete => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1842142 Title: [EHL][OSE] SPI implementation Status in intel: Fix Committed Status in linux package in Ubuntu: Triaged Bug description: Description: Elkhart Lake has Offload Services Engine (OSE) that will be BIOS configurable either to have some RTOS take control of its IO blocks or hand them off to running OS. IoTG has asked to support SPI. This should be based on Synopsys v3.23a specification. To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1842142/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1862028] Re: Focal uses the exfat fuse filesystem even though there is support in the kernel
I believe if got the exfat-fuse filesystem when I installed exfat-tools in order to mkexfatfs. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1862028 Title: Focal uses the exfat fuse filesystem even though there is support in the kernel Status in linux package in Ubuntu: Incomplete Status in ubuntu-mate-meta package in Ubuntu: Fix Released Status in ubuntukylin-meta package in Ubuntu: In Progress Status in udisks2 package in Ubuntu: Invalid Bug description: When a storage device formatted with exfat is automatically mounted on a system it is mounted with a fuse filesystem instead of a native, kernel filesystem. The kernel now has support for exfat. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862028/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1862028] Re: Focal uses the exfat fuse filesystem even though there is support in the kernel
exfat-utils that is -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1862028 Title: Focal uses the exfat fuse filesystem even though there is support in the kernel Status in linux package in Ubuntu: Incomplete Status in ubuntu-mate-meta package in Ubuntu: Fix Released Status in ubuntukylin-meta package in Ubuntu: In Progress Status in udisks2 package in Ubuntu: Invalid Bug description: When a storage device formatted with exfat is automatically mounted on a system it is mounted with a fuse filesystem instead of a native, kernel filesystem. The kernel now has support for exfat. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862028/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1862028] Re: Focal uses the exfat fuse filesystem even though there is support in the kernel
If I take the exfat flashdrive to a 20.04 system that does not have exfat-utils/exfat-fuse on it, it works exactly as I expect and mounts as an exfat filesystem. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1862028 Title: Focal uses the exfat fuse filesystem even though there is support in the kernel Status in linux package in Ubuntu: Incomplete Status in ubuntu-mate-meta package in Ubuntu: Fix Released Status in ubuntukylin-meta package in Ubuntu: In Progress Status in udisks2 package in Ubuntu: Invalid Bug description: When a storage device formatted with exfat is automatically mounted on a system it is mounted with a fuse filesystem instead of a native, kernel filesystem. The kernel now has support for exfat. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862028/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1862028] Re: Focal uses the exfat fuse filesystem even though there is support in the kernel
** Tags added: champagne -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1862028 Title: Focal uses the exfat fuse filesystem even though there is support in the kernel Status in linux package in Ubuntu: Incomplete Status in udisks2 package in Ubuntu: New Bug description: When a storage device formatted with exfat is automatically mounted on a system it is mounted with a fuse filesystem instead of a native, kernel filesystem. The kernel now has support for exfat. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862028/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1864303] Re: Removing the e1000e module causes a crash
** Package changed: linux-5.4 (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1864303 Title: Removing the e1000e module causes a crash Status in linux package in Ubuntu: Confirmed Bug description: I have a Lenovo x1 Carbon Gen5 and when it initially came out if you left the onboard NIC (e1000e) module loaded it would suck CPU/battery life so I have it removed in rc.local on boot. In 5.4 (also happens on 5.4.0.15.18 which I'm running from proposed right now), this is what happens when the module is unloaded: [ 608.979789] e1000e :00:1f.6 enp0s31f6: removed PHC [ 609.008352] [ cut here ] [ 609.008353] kernel BUG at drivers/pci/msi.c:375! [ 609.008358] invalid opcode: [#1] SMP PTI [ 609.008359] CPU: 0 PID: 6829 Comm: rmmod Tainted: P O 5.4.0-15-generic #18-Ubuntu [ 609.008360] Hardware name: LENOVO 20HRCTO1WW/20HRCTO1WW, BIOS N1MET59W (1.44 ) 11/25/2019 [ 609.008364] RIP: 0010:free_msi_irqs+0x17d/0x1b0 [ 609.008365] Code: 84 df fe ff ff 45 31 f6 eb 11 41 83 c6 01 44 39 73 14 0f 86 cc fe ff ff 8b 7b 10 44 01 f7 e8 ea c3 b6 ff 48 83 78 70 00 74 e0 <0f> 0b 49 8d b5 b0 00 00 00 e8 b5 7d b7 ff e9 cd fe ff ff 49 8b 78 [ 609.008366] RSP: 0018:a7d2072f7d40 EFLAGS: 00010286 [ 609.008367] RAX: 8bc9bfb49e00 RBX: 8bc9ad69c720 RCX: [ 609.008368] RDX: RSI: 0084 RDI: a9e65980 [ 609.008369] RBP: a7d2072f7d70 R08: 8bc9bb564db0 R09: 8bc9bb564df8 [ 609.008369] R10: R11: a9e65988 R12: 8bc9cb5272c0 [ 609.008370] R13: 8bc9cb527000 R14: R15: dead0100 [ 609.008371] FS: 7f188f1f9500() GS:8bc9ce20() knlGS: [ 609.008372] CS: 0010 DS: ES: CR0: 80050033 [ 609.008373] CR2: 7f6d1a6af060 CR3: 00046d9f8006 CR4: 003606f0 [ 609.008373] Call Trace: [ 609.008376] pci_disable_msi+0x100/0x130 [ 609.008385] e1000e_reset_interrupt_capability+0x52/0x60 [e1000e] [ 609.008389] e1000_remove+0xc4/0x180 [e1000e] [ 609.008391] pci_device_remove+0x3e/0xb0 [ 609.008394] device_release_driver_internal+0xf0/0x1d0 [ 609.008396] driver_detach+0x4c/0x8f [ 609.008397] bus_remove_driver+0x5c/0xd0 [ 609.008399] driver_unregister+0x31/0x50 [ 609.008400] pci_unregister_driver+0x40/0x90 [ 609.008405] e1000_exit_module+0x10/0x3c1 [e1000e] [ 609.008407] __x64_sys_delete_module+0x147/0x2b0 [ 609.008409] ? exit_to_usermode_loop+0xea/0x160 [ 609.008411] do_syscall_64+0x57/0x190 [ 609.008413] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 609.008414] RIP: 0033:0x7f188f345c9b [ 609.008416] Code: 73 01 c3 48 8b 0d f5 71 0c 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa b8 b0 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d c5 71 0c 00 f7 d8 64 89 01 48 [ 609.008416] RSP: 002b:7fffc8d32e68 EFLAGS: 0206 ORIG_RAX: 00b0 [ 609.008418] RAX: ffda RBX: 561e1a391790 RCX: 7f188f345c9b [ 609.008419] RDX: 000a RSI: 0800 RDI: 561e1a3917f8 [ 609.008420] RBP: 7fffc8d32ec8 R08: R09: [ 609.008420] R10: 7f188f3c1ac0 R11: 0206 R12: 7fffc8d33090 [ 609.008422] R13: 7fffc8d3474a R14: 561e1a3912a0 R15: 561e1a391790 [ 609.008424] Modules linked in: thunderbolt rfcomm xfrm_user xfrm_algo l2tp_ppp l2tp_netlink l2tp_core ip6_udp_tunnel udp_tunnel pppox ccm xt_comment xt_CHECKSUM xt_MASQUERADE ip6table_mangle ip6table_nat dummy iptable_mangle iptable_nat nf_tables nfnetlink bridge stp llc cmac algif_hash algif_skcipher af_alg bnep zfs(PO) zunicode(PO) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) zlua(PO) joydev intel_rapl_msr mei_hdcp nls_iso8859_1 snd_seq_midi snd_seq_midi_event snd_hda_codec_hdmi snd_hda_codec_conexant snd_hda_codec_generic intel_rapl_common x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel snd_hda_intel snd_rawmidi kvm snd_intel_nhlt snd_hda_codec intel_cstate rmi_smbus intel_rapl_perf snd_hda_core snd_hwdep iwlmvm rmi_core mac80211 uvcvideo input_leds videobuf2_vmalloc videobuf2_memops btusb btrtl snd_pcm libarc4 serio_raw snd_seq btbcm intel_wmi_thunderbolt videobuf2_v4l2 btintel videobuf2_common wmi_bmof thinkpad_acpi bluetooth videodev nvram snd_seq_device ledtrig_audio [ 609.008447] iwlwifi mc snd_timer rtsx_pci_ms ecdh_generic ecc cfg80211 memstick snd mei_me ucsi_acpi typec_ucsi intel_xhci_usb_role_switch mei roles intel_pch_thermal typec soundcore acpi_pad mac_hid nf_log_ipv6 ip6t_REJECT nf_reject_ipv6 xt_hl ip6t_rt nf_log_ipv4 nf_log_common ipt_REJECT nf_reject_ipv4 xt_LOG xt_limit xt_addrtype xt_tcpudp xt_conntrack ip6tab
[Kernel-packages] [Bug 1853044] Re: 5.3.0-23-generic causes fans to spin when idle
If we think that single patch is a solution then can we get a test kernel with that patch made available for confirmation and then get that submitted so it can go into a official 20.04 kernel? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1853044 Title: 5.3.0-23-generic causes fans to spin when idle Status in linux package in Ubuntu: Confirmed Bug description: After upgrading to 5.3.0-23-generic the fans in my machine don't stop running. They always sound like something is utilizing CPU - even with no applications running after boot. If I boot back to 5.3.0-19-generic it's fine. My microcode version is reported as 0xd4 and iucode-tool reports: iucode-tool: system has processor(s) with signature 0x000506e3 Let me know if you need anything else. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-23-generic 5.3.0-23.25 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: dean 2898 F pulseaudio /dev/snd/pcmC2D0p: dean 2898 F...m pulseaudio /dev/snd/controlC0: dean 2898 F pulseaudio /dev/snd/controlC1: dean 2898 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Nov 18 13:03:34 2019 HibernationDevice: RESUME=UUID=55a42c82-50bf-4e75-a133-dbd3aa93611b InstallationDate: Installed on 2018-07-24 (482 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180724) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-23-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-23-generic N/A linux-backports-modules-5.3.0-23-generic N/A linux-firmware1.183.2 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-07-19 (121 days ago) dmi.bios.date: 05/16/2018 dmi.bios.vendor: Intel Corp. dmi.bios.version: KYSKLi70.86A.0055.2018.0516.1629 dmi.board.name: NUC6i7KYB dmi.board.vendor: Intel Corporation dmi.board.version: H90766-406 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnIntelCorp.:bvrKYSKLi70.86A.0055.2018.0516.1629:bd05/16/2018:svn:pn:pvr:rvnIntelCorporation:rnNUC6i7KYB:rvrH90766-406:cvnIntelCorporation:ct3:cvr1.0: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853044/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1862028] [NEW] Focal uses the exfat fuse filesystem even though there is support in the kernel
Public bug reported: When a storage device formatted with exfat is automatically mounted on a system it is mounted with a fuse filesystem instead of a native, kernel filesystem. The kernel now has support for exfat. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: udisks2 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1862028 Title: Focal uses the exfat fuse filesystem even though there is support in the kernel Status in linux package in Ubuntu: New Status in udisks2 package in Ubuntu: New Bug description: When a storage device formatted with exfat is automatically mounted on a system it is mounted with a fuse filesystem instead of a native, kernel filesystem. The kernel now has support for exfat. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862028/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1858182] Re: Add support for Rizon 3900 Series Processors by updating to a newer kernel version
@ryan The kernel SRU workflow project is a special project that is only used for internal processes. Your bug should have been filed against the ubuntu/linux project which I have now fixed. Also note that we closely follow upstream stable releases and automatically pick them up. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** No longer affects: kernel-sru-workflow -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1858182 Title: Add support for Rizon 3900 Series Processors by updating to a newer kernel version Status in linux package in Ubuntu: Incomplete Bug description: According to: https://www.phoronix.com/scan.php?page=news_item&px=Linux-5.4.7 -Stable-Released "Greg Kroah-Hartman took time out of his New Year's Eve festivities to release Linux 5.4.7, 4.19.92, and 4.14.161 as the newest supported stable releases of the Linux kernel. Making these kernels noteworthy is that they contain the necessary MCE fix for booting the new AMD Ryzen Threadripper 3900 series processors. With Linux 5.5 mainline or these back-ported kernels, Linux should be booting now without issue. These stable kernel updates also add Intel Comet Lake PCH-V and Elkhart Lake SoC support to the intel_th driver. But the rest of the changes are an assortment of mostly mundane fixes, unless you happened to be affected by one of the particular bugs addressed." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1858182/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1845886] Re: Enable GVE driver on GCP/GKE kernels
*** This bug is a duplicate of bug 1855992 *** https://bugs.launchpad.net/bugs/1855992 ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** No longer affects: kernel-sru-workflow -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1845886 Title: Enable GVE driver on GCP/GKE kernels Status in linux package in Ubuntu: New Bug description: More info in: https://canonical.my.salesforce.com/5003z1zpyXH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845886/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851749] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1851749/+attachment/5303665/+files/UdevDb.txt ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1851749 Title: Frequently getting thermal warnings and cpu throttling messages in syslog Status in linux package in Ubuntu: Confirmed Bug description: Nov 6 11:34:26 fog kernel: [1129655.443564] mce: CPU0: Core temperature above threshold, cpu clock throttled (total events = 50300) Nov 6 11:34:26 fog kernel: [1129655.443565] mce: CPU2: Core temperature above threshold, cpu clock throttled (total events = 50300) Nov 6 11:34:26 fog kernel: [1129655.443567] mce: CPU1: Package temperature above threshold, cpu clock throttled (total events = 58637) Nov 6 11:34:26 fog kernel: [1129655.443568] mce: CPU3: Package temperature above threshold, cpu clock throttled (total events = 58637) Nov 6 11:34:26 fog kernel: [1129655.443569] mce: CPU2: Package temperature above threshold, cpu clock throttled (total events = 58637) Nov 6 11:34:26 fog kernel: [1129655.443570] mce: CPU0: Package temperature above threshold, cpu clock throttled (total events = 58637) Nov 6 11:34:26 fog kernel: [1129655.446528] mce: CPU2: Core temperature/speed normal Nov 6 11:34:26 fog kernel: [1129655.446529] mce: CPU0: Core temperature/speed normal Nov 6 11:34:26 fog kernel: [1129655.446530] mce: CPU1: Package temperature/speed normal Nov 6 11:34:26 fog kernel: [1129655.446531] mce: CPU3: Package temperature/speed normal Nov 6 11:34:26 fog kernel: [1129655.446531] mce: CPU0: Package temperature/speed normal Nov 6 11:34:26 fog kernel: [1129655.446532] mce: CPU2: Package temperature/speed normal Nov 6 11:40:35 fog kernel: [1130024.427390] mce: CPU0: Core temperature above threshold, cpu clock throttled (total events = 50316) Nov 6 11:40:35 fog kernel: [1130024.427391] mce: CPU2: Core temperature above threshold, cpu clock throttled (total events = 50316)
[Kernel-packages] [Bug 1851749] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1851749/+attachment/5303666/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1851749 Title: Frequently getting thermal warnings and cpu throttling messages in syslog Status in linux package in Ubuntu: Confirmed Bug description: Nov 6 11:34:26 fog kernel: [1129655.443564] mce: CPU0: Core temperature above threshold, cpu clock throttled (total events = 50300) Nov 6 11:34:26 fog kernel: [1129655.443565] mce: CPU2: Core temperature above threshold, cpu clock throttled (total events = 50300) Nov 6 11:34:26 fog kernel: [1129655.443567] mce: CPU1: Package temperature above threshold, cpu clock throttled (total events = 58637) Nov 6 11:34:26 fog kernel: [1129655.443568] mce: CPU3: Package temperature above threshold, cpu clock throttled (total events = 58637) Nov 6 11:34:26 fog kernel: [1129655.443569] mce: CPU2: Package temperature above threshold, cpu clock throttled (total events = 58637) Nov 6 11:34:26 fog kernel: [1129655.443570] mce: CPU0: Package temperature above threshold, cpu clock throttled (total events = 58637) Nov 6 11:34:26 fog kernel: [1129655.446528] mce: CPU2: Core temperature/speed normal Nov 6 11:34:26 fog kernel: [1129655.446529] mce: CPU0: Core temperature/speed normal Nov 6 11:34:26 fog kernel: [1129655.446530] mce: CPU1: Package temperature/speed normal Nov 6 11:34:26 fog kernel: [1129655.446531] mce: CPU3: Package temperature/speed normal Nov 6 11:34:26 fog kernel: [1129655.446531] mce: CPU0: Package temperature/speed normal Nov 6 11:34:26 fog kernel: [1129655.446532] mce: CPU2: Package temperature/speed normal Nov 6 11:40:35 fog kernel: [1130024.427390] mce: CPU0: Core temperature above threshold, cpu clock throttled (total events = 50316) Nov 6 11:40:35 fog kernel: [1130024.427391] mce: CPU2: Core temperature above threshold, cpu clock throttled (total events = 50316)
[Kernel-packages] [Bug 1851749] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1851749/+attachment/5303662/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1851749 Title: Frequently getting thermal warnings and cpu throttling messages in syslog Status in linux package in Ubuntu: Confirmed Bug description: Nov 6 11:34:26 fog kernel: [1129655.443564] mce: CPU0: Core temperature above threshold, cpu clock throttled (total events = 50300) Nov 6 11:34:26 fog kernel: [1129655.443565] mce: CPU2: Core temperature above threshold, cpu clock throttled (total events = 50300) Nov 6 11:34:26 fog kernel: [1129655.443567] mce: CPU1: Package temperature above threshold, cpu clock throttled (total events = 58637) Nov 6 11:34:26 fog kernel: [1129655.443568] mce: CPU3: Package temperature above threshold, cpu clock throttled (total events = 58637) Nov 6 11:34:26 fog kernel: [1129655.443569] mce: CPU2: Package temperature above threshold, cpu clock throttled (total events = 58637) Nov 6 11:34:26 fog kernel: [1129655.443570] mce: CPU0: Package temperature above threshold, cpu clock throttled (total events = 58637) Nov 6 11:34:26 fog kernel: [1129655.446528] mce: CPU2: Core temperature/speed normal Nov 6 11:34:26 fog kernel: [1129655.446529] mce: CPU0: Core temperature/speed normal Nov 6 11:34:26 fog kernel: [1129655.446530] mce: CPU1: Package temperature/speed normal Nov 6 11:34:26 fog kernel: [1129655.446531] mce: CPU3: Package temperature/speed normal Nov 6 11:34:26 fog kernel: [1129655.446531] mce: CPU0: Package temperature/speed normal Nov 6 11:34:26 fog kernel: [1129655.446532] mce: CPU2: Package temperature/speed normal Nov 6 11:40:35 fog kernel: [1130024.427390] mce: CPU0: Core temperature above threshold, cpu clock throttled (total events = 50316) Nov 6 11:40:35 fog kernel: [1130024.427391] mce: CPU2: Core temperature above threshold, cpu clock throttled (total events = 50316)
[Kernel-packages] [Bug 1851749] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1851749/+attachment/5303664/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1851749 Title: Frequently getting thermal warnings and cpu throttling messages in syslog Status in linux package in Ubuntu: Confirmed Bug description: Nov 6 11:34:26 fog kernel: [1129655.443564] mce: CPU0: Core temperature above threshold, cpu clock throttled (total events = 50300) Nov 6 11:34:26 fog kernel: [1129655.443565] mce: CPU2: Core temperature above threshold, cpu clock throttled (total events = 50300) Nov 6 11:34:26 fog kernel: [1129655.443567] mce: CPU1: Package temperature above threshold, cpu clock throttled (total events = 58637) Nov 6 11:34:26 fog kernel: [1129655.443568] mce: CPU3: Package temperature above threshold, cpu clock throttled (total events = 58637) Nov 6 11:34:26 fog kernel: [1129655.443569] mce: CPU2: Package temperature above threshold, cpu clock throttled (total events = 58637) Nov 6 11:34:26 fog kernel: [1129655.443570] mce: CPU0: Package temperature above threshold, cpu clock throttled (total events = 58637) Nov 6 11:34:26 fog kernel: [1129655.446528] mce: CPU2: Core temperature/speed normal Nov 6 11:34:26 fog kernel: [1129655.446529] mce: CPU0: Core temperature/speed normal Nov 6 11:34:26 fog kernel: [1129655.446530] mce: CPU1: Package temperature/speed normal Nov 6 11:34:26 fog kernel: [1129655.446531] mce: CPU3: Package temperature/speed normal Nov 6 11:34:26 fog kernel: [1129655.446531] mce: CPU0: Package temperature/speed normal Nov 6 11:34:26 fog kernel: [1129655.446532] mce: CPU2: Package temperature/speed normal Nov 6 11:40:35 fog kernel: [1130024.427390] mce: CPU0: Core temperature above threshold, cpu clock throttled (total events = 50316) Nov 6 11:40:35 fog kernel: [1130024.427391] mce: CPU2: Core temperature above threshold, cpu clock throttled (total events = 50316)
[Kernel-packages] [Bug 1851749] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1851749/+attachment/5303663/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1851749 Title: Frequently getting thermal warnings and cpu throttling messages in syslog Status in linux package in Ubuntu: Confirmed Bug description: Nov 6 11:34:26 fog kernel: [1129655.443564] mce: CPU0: Core temperature above threshold, cpu clock throttled (total events = 50300) Nov 6 11:34:26 fog kernel: [1129655.443565] mce: CPU2: Core temperature above threshold, cpu clock throttled (total events = 50300) Nov 6 11:34:26 fog kernel: [1129655.443567] mce: CPU1: Package temperature above threshold, cpu clock throttled (total events = 58637) Nov 6 11:34:26 fog kernel: [1129655.443568] mce: CPU3: Package temperature above threshold, cpu clock throttled (total events = 58637) Nov 6 11:34:26 fog kernel: [1129655.443569] mce: CPU2: Package temperature above threshold, cpu clock throttled (total events = 58637) Nov 6 11:34:26 fog kernel: [1129655.443570] mce: CPU0: Package temperature above threshold, cpu clock throttled (total events = 58637) Nov 6 11:34:26 fog kernel: [1129655.446528] mce: CPU2: Core temperature/speed normal Nov 6 11:34:26 fog kernel: [1129655.446529] mce: CPU0: Core temperature/speed normal Nov 6 11:34:26 fog kernel: [1129655.446530] mce: CPU1: Package temperature/speed normal Nov 6 11:34:26 fog kernel: [1129655.446531] mce: CPU3: Package temperature/speed normal Nov 6 11:34:26 fog kernel: [1129655.446531] mce: CPU0: Package temperature/speed normal Nov 6 11:34:26 fog kernel: [1129655.446532] mce: CPU2: Package temperature/speed normal Nov 6 11:40:35 fog kernel: [1130024.427390] mce: CPU0: Core temperature above threshold, cpu clock throttled (total events = 50316) Nov 6 11:40:35 fog kernel: [1130024.427391] mce: CPU2: Core temperature above threshold, cpu clock throttled (total events = 50316)
[Kernel-packages] [Bug 1851749] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1851749/+attachment/5303661/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1851749 Title: Frequently getting thermal warnings and cpu throttling messages in syslog Status in linux package in Ubuntu: Confirmed Bug description: Nov 6 11:34:26 fog kernel: [1129655.443564] mce: CPU0: Core temperature above threshold, cpu clock throttled (total events = 50300) Nov 6 11:34:26 fog kernel: [1129655.443565] mce: CPU2: Core temperature above threshold, cpu clock throttled (total events = 50300) Nov 6 11:34:26 fog kernel: [1129655.443567] mce: CPU1: Package temperature above threshold, cpu clock throttled (total events = 58637) Nov 6 11:34:26 fog kernel: [1129655.443568] mce: CPU3: Package temperature above threshold, cpu clock throttled (total events = 58637) Nov 6 11:34:26 fog kernel: [1129655.443569] mce: CPU2: Package temperature above threshold, cpu clock throttled (total events = 58637) Nov 6 11:34:26 fog kernel: [1129655.443570] mce: CPU0: Package temperature above threshold, cpu clock throttled (total events = 58637) Nov 6 11:34:26 fog kernel: [1129655.446528] mce: CPU2: Core temperature/speed normal Nov 6 11:34:26 fog kernel: [1129655.446529] mce: CPU0: Core temperature/speed normal Nov 6 11:34:26 fog kernel: [1129655.446530] mce: CPU1: Package temperature/speed normal Nov 6 11:34:26 fog kernel: [1129655.446531] mce: CPU3: Package temperature/speed normal Nov 6 11:34:26 fog kernel: [1129655.446531] mce: CPU0: Package temperature/speed normal Nov 6 11:34:26 fog kernel: [1129655.446532] mce: CPU2: Package temperature/speed normal Nov 6 11:40:35 fog kernel: [1130024.427390] mce: CPU0: Core temperature above threshold, cpu clock throttled (total events = 50316) Nov 6 11:40:35 fog kernel: [1130024.427391] mce: CPU2: Core temperature above threshold, cpu clock throttled (total events = 50316)
[Kernel-packages] [Bug 1851749] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1851749/+attachment/5303660/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1851749 Title: Frequently getting thermal warnings and cpu throttling messages in syslog Status in linux package in Ubuntu: Confirmed Bug description: Nov 6 11:34:26 fog kernel: [1129655.443564] mce: CPU0: Core temperature above threshold, cpu clock throttled (total events = 50300) Nov 6 11:34:26 fog kernel: [1129655.443565] mce: CPU2: Core temperature above threshold, cpu clock throttled (total events = 50300) Nov 6 11:34:26 fog kernel: [1129655.443567] mce: CPU1: Package temperature above threshold, cpu clock throttled (total events = 58637) Nov 6 11:34:26 fog kernel: [1129655.443568] mce: CPU3: Package temperature above threshold, cpu clock throttled (total events = 58637) Nov 6 11:34:26 fog kernel: [1129655.443569] mce: CPU2: Package temperature above threshold, cpu clock throttled (total events = 58637) Nov 6 11:34:26 fog kernel: [1129655.443570] mce: CPU0: Package temperature above threshold, cpu clock throttled (total events = 58637) Nov 6 11:34:26 fog kernel: [1129655.446528] mce: CPU2: Core temperature/speed normal Nov 6 11:34:26 fog kernel: [1129655.446529] mce: CPU0: Core temperature/speed normal Nov 6 11:34:26 fog kernel: [1129655.446530] mce: CPU1: Package temperature/speed normal Nov 6 11:34:26 fog kernel: [1129655.446531] mce: CPU3: Package temperature/speed normal Nov 6 11:34:26 fog kernel: [1129655.446531] mce: CPU0: Package temperature/speed normal Nov 6 11:34:26 fog kernel: [1129655.446532] mce: CPU2: Package temperature/speed normal Nov 6 11:40:35 fog kernel: [1130024.427390] mce: CPU0: Core temperature above threshold, cpu clock throttled (total events = 50316) Nov 6 11:40:35 fog kernel: [1130024.427391] mce: CPU2: Core temperature above threshold, cpu clock throttled (total events = 50316)
[Kernel-packages] [Bug 1851749] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1851749/+attachment/5303655/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1851749 Title: Frequently getting thermal warnings and cpu throttling messages in syslog Status in linux package in Ubuntu: Confirmed Bug description: Nov 6 11:34:26 fog kernel: [1129655.443564] mce: CPU0: Core temperature above threshold, cpu clock throttled (total events = 50300) Nov 6 11:34:26 fog kernel: [1129655.443565] mce: CPU2: Core temperature above threshold, cpu clock throttled (total events = 50300) Nov 6 11:34:26 fog kernel: [1129655.443567] mce: CPU1: Package temperature above threshold, cpu clock throttled (total events = 58637) Nov 6 11:34:26 fog kernel: [1129655.443568] mce: CPU3: Package temperature above threshold, cpu clock throttled (total events = 58637) Nov 6 11:34:26 fog kernel: [1129655.443569] mce: CPU2: Package temperature above threshold, cpu clock throttled (total events = 58637) Nov 6 11:34:26 fog kernel: [1129655.443570] mce: CPU0: Package temperature above threshold, cpu clock throttled (total events = 58637) Nov 6 11:34:26 fog kernel: [1129655.446528] mce: CPU2: Core temperature/speed normal Nov 6 11:34:26 fog kernel: [1129655.446529] mce: CPU0: Core temperature/speed normal Nov 6 11:34:26 fog kernel: [1129655.446530] mce: CPU1: Package temperature/speed normal Nov 6 11:34:26 fog kernel: [1129655.446531] mce: CPU3: Package temperature/speed normal Nov 6 11:34:26 fog kernel: [1129655.446531] mce: CPU0: Package temperature/speed normal Nov 6 11:34:26 fog kernel: [1129655.446532] mce: CPU2: Package temperature/speed normal Nov 6 11:40:35 fog kernel: [1130024.427390] mce: CPU0: Core temperature above threshold, cpu clock throttled (total events = 50316) Nov 6 11:40:35 fog kernel: [1130024.427391] mce: CPU2: Core temperature above threshold, cpu clock throttled (total events = 50316)
[Kernel-packages] [Bug 1851749] AlsaInfo.txt
apport information ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1851749/+attachment/5303654/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1851749 Title: Frequently getting thermal warnings and cpu throttling messages in syslog Status in linux package in Ubuntu: Confirmed Bug description: Nov 6 11:34:26 fog kernel: [1129655.443564] mce: CPU0: Core temperature above threshold, cpu clock throttled (total events = 50300) Nov 6 11:34:26 fog kernel: [1129655.443565] mce: CPU2: Core temperature above threshold, cpu clock throttled (total events = 50300) Nov 6 11:34:26 fog kernel: [1129655.443567] mce: CPU1: Package temperature above threshold, cpu clock throttled (total events = 58637) Nov 6 11:34:26 fog kernel: [1129655.443568] mce: CPU3: Package temperature above threshold, cpu clock throttled (total events = 58637) Nov 6 11:34:26 fog kernel: [1129655.443569] mce: CPU2: Package temperature above threshold, cpu clock throttled (total events = 58637) Nov 6 11:34:26 fog kernel: [1129655.443570] mce: CPU0: Package temperature above threshold, cpu clock throttled (total events = 58637) Nov 6 11:34:26 fog kernel: [1129655.446528] mce: CPU2: Core temperature/speed normal Nov 6 11:34:26 fog kernel: [1129655.446529] mce: CPU0: Core temperature/speed normal Nov 6 11:34:26 fog kernel: [1129655.446530] mce: CPU1: Package temperature/speed normal Nov 6 11:34:26 fog kernel: [1129655.446531] mce: CPU3: Package temperature/speed normal Nov 6 11:34:26 fog kernel: [1129655.446531] mce: CPU0: Package temperature/speed normal Nov 6 11:34:26 fog kernel: [1129655.446532] mce: CPU2: Package temperature/speed normal Nov 6 11:40:35 fog kernel: [1130024.427390] mce: CPU0: Core temperature above threshold, cpu clock throttled (total events = 50316) Nov 6 11:40:35 fog kernel: [1130024.427391] mce: CPU2: Core temperature above threshold, cpu clock throttled (total events = 50316)
[Kernel-packages] [Bug 1851749] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1851749/+attachment/5303659/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1851749 Title: Frequently getting thermal warnings and cpu throttling messages in syslog Status in linux package in Ubuntu: Confirmed Bug description: Nov 6 11:34:26 fog kernel: [1129655.443564] mce: CPU0: Core temperature above threshold, cpu clock throttled (total events = 50300) Nov 6 11:34:26 fog kernel: [1129655.443565] mce: CPU2: Core temperature above threshold, cpu clock throttled (total events = 50300) Nov 6 11:34:26 fog kernel: [1129655.443567] mce: CPU1: Package temperature above threshold, cpu clock throttled (total events = 58637) Nov 6 11:34:26 fog kernel: [1129655.443568] mce: CPU3: Package temperature above threshold, cpu clock throttled (total events = 58637) Nov 6 11:34:26 fog kernel: [1129655.443569] mce: CPU2: Package temperature above threshold, cpu clock throttled (total events = 58637) Nov 6 11:34:26 fog kernel: [1129655.443570] mce: CPU0: Package temperature above threshold, cpu clock throttled (total events = 58637) Nov 6 11:34:26 fog kernel: [1129655.446528] mce: CPU2: Core temperature/speed normal Nov 6 11:34:26 fog kernel: [1129655.446529] mce: CPU0: Core temperature/speed normal Nov 6 11:34:26 fog kernel: [1129655.446530] mce: CPU1: Package temperature/speed normal Nov 6 11:34:26 fog kernel: [1129655.446531] mce: CPU3: Package temperature/speed normal Nov 6 11:34:26 fog kernel: [1129655.446531] mce: CPU0: Package temperature/speed normal Nov 6 11:34:26 fog kernel: [1129655.446532] mce: CPU2: Package temperature/speed normal Nov 6 11:40:35 fog kernel: [1130024.427390] mce: CPU0: Core temperature above threshold, cpu clock throttled (total events = 50316) Nov 6 11:40:35 fog kernel: [1130024.427391] mce: CPU2: Core temperature above threshold, cpu clock throttled (total events = 50316)
[Kernel-packages] [Bug 1851749] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1851749/+attachment/5303657/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1851749 Title: Frequently getting thermal warnings and cpu throttling messages in syslog Status in linux package in Ubuntu: Confirmed Bug description: Nov 6 11:34:26 fog kernel: [1129655.443564] mce: CPU0: Core temperature above threshold, cpu clock throttled (total events = 50300) Nov 6 11:34:26 fog kernel: [1129655.443565] mce: CPU2: Core temperature above threshold, cpu clock throttled (total events = 50300) Nov 6 11:34:26 fog kernel: [1129655.443567] mce: CPU1: Package temperature above threshold, cpu clock throttled (total events = 58637) Nov 6 11:34:26 fog kernel: [1129655.443568] mce: CPU3: Package temperature above threshold, cpu clock throttled (total events = 58637) Nov 6 11:34:26 fog kernel: [1129655.443569] mce: CPU2: Package temperature above threshold, cpu clock throttled (total events = 58637) Nov 6 11:34:26 fog kernel: [1129655.443570] mce: CPU0: Package temperature above threshold, cpu clock throttled (total events = 58637) Nov 6 11:34:26 fog kernel: [1129655.446528] mce: CPU2: Core temperature/speed normal Nov 6 11:34:26 fog kernel: [1129655.446529] mce: CPU0: Core temperature/speed normal Nov 6 11:34:26 fog kernel: [1129655.446530] mce: CPU1: Package temperature/speed normal Nov 6 11:34:26 fog kernel: [1129655.446531] mce: CPU3: Package temperature/speed normal Nov 6 11:34:26 fog kernel: [1129655.446531] mce: CPU0: Package temperature/speed normal Nov 6 11:34:26 fog kernel: [1129655.446532] mce: CPU2: Package temperature/speed normal Nov 6 11:40:35 fog kernel: [1130024.427390] mce: CPU0: Core temperature above threshold, cpu clock throttled (total events = 50316) Nov 6 11:40:35 fog kernel: [1130024.427391] mce: CPU2: Core temperature above threshold, cpu clock throttled (total events = 50316)
[Kernel-packages] [Bug 1851749] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1851749/+attachment/5303658/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1851749 Title: Frequently getting thermal warnings and cpu throttling messages in syslog Status in linux package in Ubuntu: Confirmed Bug description: Nov 6 11:34:26 fog kernel: [1129655.443564] mce: CPU0: Core temperature above threshold, cpu clock throttled (total events = 50300) Nov 6 11:34:26 fog kernel: [1129655.443565] mce: CPU2: Core temperature above threshold, cpu clock throttled (total events = 50300) Nov 6 11:34:26 fog kernel: [1129655.443567] mce: CPU1: Package temperature above threshold, cpu clock throttled (total events = 58637) Nov 6 11:34:26 fog kernel: [1129655.443568] mce: CPU3: Package temperature above threshold, cpu clock throttled (total events = 58637) Nov 6 11:34:26 fog kernel: [1129655.443569] mce: CPU2: Package temperature above threshold, cpu clock throttled (total events = 58637) Nov 6 11:34:26 fog kernel: [1129655.443570] mce: CPU0: Package temperature above threshold, cpu clock throttled (total events = 58637) Nov 6 11:34:26 fog kernel: [1129655.446528] mce: CPU2: Core temperature/speed normal Nov 6 11:34:26 fog kernel: [1129655.446529] mce: CPU0: Core temperature/speed normal Nov 6 11:34:26 fog kernel: [1129655.446530] mce: CPU1: Package temperature/speed normal Nov 6 11:34:26 fog kernel: [1129655.446531] mce: CPU3: Package temperature/speed normal Nov 6 11:34:26 fog kernel: [1129655.446531] mce: CPU0: Package temperature/speed normal Nov 6 11:34:26 fog kernel: [1129655.446532] mce: CPU2: Package temperature/speed normal Nov 6 11:40:35 fog kernel: [1130024.427390] mce: CPU0: Core temperature above threshold, cpu clock throttled (total events = 50316) Nov 6 11:40:35 fog kernel: [1130024.427391] mce: CPU2: Core temperature above threshold, cpu clock throttled (total events = 50316)
[Kernel-packages] [Bug 1851749] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1851749/+attachment/5303656/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1851749 Title: Frequently getting thermal warnings and cpu throttling messages in syslog Status in linux package in Ubuntu: Confirmed Bug description: Nov 6 11:34:26 fog kernel: [1129655.443564] mce: CPU0: Core temperature above threshold, cpu clock throttled (total events = 50300) Nov 6 11:34:26 fog kernel: [1129655.443565] mce: CPU2: Core temperature above threshold, cpu clock throttled (total events = 50300) Nov 6 11:34:26 fog kernel: [1129655.443567] mce: CPU1: Package temperature above threshold, cpu clock throttled (total events = 58637) Nov 6 11:34:26 fog kernel: [1129655.443568] mce: CPU3: Package temperature above threshold, cpu clock throttled (total events = 58637) Nov 6 11:34:26 fog kernel: [1129655.443569] mce: CPU2: Package temperature above threshold, cpu clock throttled (total events = 58637) Nov 6 11:34:26 fog kernel: [1129655.443570] mce: CPU0: Package temperature above threshold, cpu clock throttled (total events = 58637) Nov 6 11:34:26 fog kernel: [1129655.446528] mce: CPU2: Core temperature/speed normal Nov 6 11:34:26 fog kernel: [1129655.446529] mce: CPU0: Core temperature/speed normal Nov 6 11:34:26 fog kernel: [1129655.446530] mce: CPU1: Package temperature/speed normal Nov 6 11:34:26 fog kernel: [1129655.446531] mce: CPU3: Package temperature/speed normal Nov 6 11:34:26 fog kernel: [1129655.446531] mce: CPU0: Package temperature/speed normal Nov 6 11:34:26 fog kernel: [1129655.446532] mce: CPU2: Package temperature/speed normal Nov 6 11:40:35 fog kernel: [1130024.427390] mce: CPU0: Core temperature above threshold, cpu clock throttled (total events = 50316) Nov 6 11:40:35 fog kernel: [1130024.427391] mce: CPU2: Core temperature above threshold, cpu clock throttled (total events = 50316)
[Kernel-packages] [Bug 1851749] [NEW] Frequently getting thermal warnings and cpu throttling messages in syslog
Public bug reported: Nov 6 11:34:26 fog kernel: [1129655.443564] mce: CPU0: Core temperature above threshold, cpu clock throttled (total events = 50300) Nov 6 11:34:26 fog kernel: [1129655.443565] mce: CPU2: Core temperature above threshold, cpu clock throttled (total events = 50300) Nov 6 11:34:26 fog kernel: [1129655.443567] mce: CPU1: Package temperature above threshold, cpu clock throttled (total events = 58637) Nov 6 11:34:26 fog kernel: [1129655.443568] mce: CPU3: Package temperature above threshold, cpu clock throttled (total events = 58637) Nov 6 11:34:26 fog kernel: [1129655.443569] mce: CPU2: Package temperature above threshold, cpu clock throttled (total events = 58637) Nov 6 11:34:26 fog kernel: [1129655.443570] mce: CPU0: Package temperature above threshold, cpu clock throttled (total events = 58637) Nov 6 11:34:26 fog kernel: [1129655.446528] mce: CPU2: Core temperature/speed normal Nov 6 11:34:26 fog kernel: [1129655.446529] mce: CPU0: Core temperature/speed normal Nov 6 11:34:26 fog kernel: [1129655.446530] mce: CPU1: Package temperature/speed normal Nov 6 11:34:26 fog kernel: [1129655.446531] mce: CPU3: Package temperature/speed normal Nov 6 11:34:26 fog kernel: [1129655.446531] mce: CPU0: Package temperature/speed normal Nov 6 11:34:26 fog kernel: [1129655.446532] mce: CPU2: Package temperature/speed normal Nov 6 11:40:35 fog kernel: [1130024.427390] mce: CPU0: Core temperature above threshold, cpu clock throttled (total events = 50316) Nov 6 11:40:35 fog kernel: [1130024.427391] mce: CPU2: Core temperature above threshold, cpu clock throttled (total events = 50316) Nov 6 11:40:35 fog kernel: [1130024.427392] mce: CPU2: Package temperature above threshold, cpu clock throttled (total events = 58655) Nov 6 11:40:35 fog kernel: [1130024.427394] mce: CPU0: Package temperature above threshold, cpu clock throttled (total events = 58655)
[Kernel-packages] [Bug 1851233] Re: building a snap from the eoan tree using the raspi2 defconfig results in gigantic snap package
** Changed in: linux (Ubuntu) Assignee: (unassigned) => Juerg Haefliger (juergh) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1851233 Title: building a snap from the eoan tree using the raspi2 defconfig results in gigantic snap package Status in linux package in Ubuntu: Confirmed Bug description: typically a kernel snap built from the kernel.ubuntu.com tree using the raspi2 defconfig results in a snap package that is below 150MB in size: $ ls -lh pi2-kernel_raspi2-4.4.0-1110.snap -rw--- 1 root root 129M Jun 4 15:01 pi2-kernel_raspi2-4.4.0-1110.snap trying to build a similar snap from the source tree for eoan seems to add several 100MB of unused modules to the binary, resulting in a 700MB+ snap package $ ls -lh pi4-kernel_raspi2-5.3.0-1008.9_armhf.snap -rw-r--r-- 1 ogra ogra 712M Oct 24 15:46 pi4-kernel_raspi2-5.3.0-1008.9_armhf.snap the snapcraft.yaml used for both cases is https://paste.ubuntu.com/p/J563CDsdGW/ with modified source tree and name (one pointing to xenial. the other to eoan) but no other changes between the two above packages. seems in eoan the defconfig enables a ton of additional modules (1.6G uncompressed) that have not been there before: $ sudo mount -o loop pi4-kernel_raspi2-5.3.0-1008.9_armhf.snap /mnt $ du -hcs /mnt/* 3.1M /mnt/System.map-5.3.1+ 211K /mnt/config-5.3.1+ 906K /mnt/dtbs 475M /mnt/firmware 4.5M /mnt/initrd-5.3.1+.img 7.0M /mnt/kernel.img 512 /mnt/meta 1.6G /mnt/modules 2.1G total $ that will result in unreasonable big ubuntu core images, the list of included modules should be trimmed for this flavour To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851233/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851233] Re: building a snap from the eoan tree using the raspi2 defconfig results in gigantic snap package
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1851233 Title: building a snap from the eoan tree using the raspi2 defconfig results in gigantic snap package Status in linux package in Ubuntu: Confirmed Bug description: typically a kernel snap built from the kernel.ubuntu.com tree using the raspi2 defconfig results in a snap package that is below 150MB in size: $ ls -lh pi2-kernel_raspi2-4.4.0-1110.snap -rw--- 1 root root 129M Jun 4 15:01 pi2-kernel_raspi2-4.4.0-1110.snap trying to build a similar snap from the source tree for eoan seems to add several 100MB of unused modules to the binary, resulting in a 700MB+ snap package $ ls -lh pi4-kernel_raspi2-5.3.0-1008.9_armhf.snap -rw-r--r-- 1 ogra ogra 712M Oct 24 15:46 pi4-kernel_raspi2-5.3.0-1008.9_armhf.snap the snapcraft.yaml used for both cases is https://paste.ubuntu.com/p/J563CDsdGW/ with modified source tree and name (one pointing to xenial. the other to eoan) but no other changes between the two above packages. seems in eoan the defconfig enables a ton of additional modules (1.6G uncompressed) that have not been there before: $ sudo mount -o loop pi4-kernel_raspi2-5.3.0-1008.9_armhf.snap /mnt $ du -hcs /mnt/* 3.1M /mnt/System.map-5.3.1+ 211K /mnt/config-5.3.1+ 906K /mnt/dtbs 475M /mnt/firmware 4.5M /mnt/initrd-5.3.1+.img 7.0M /mnt/kernel.img 512 /mnt/meta 1.6G /mnt/modules 2.1G total $ that will result in unreasonable big ubuntu core images, the list of included modules should be trimmed for this flavour To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851233/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1849623] Re: linux-raspi2: rebase the Eoan kernel to the latest rpi-5.3.y branch (2a085c9b42ea)
@all, The new raspi2 kernel in -proposed contains these changes. Please test. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1849623 Title: linux-raspi2: rebase the Eoan kernel to the latest rpi-5.3.y branch (2a085c9b42ea) Status in linux-raspi2 package in Ubuntu: Confirmed Status in linux-raspi2 source package in Eoan: Fix Committed Bug description: [Impact] https://bugs.launchpad.net/bugs/1848790 https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848703 Recently we had 2 bugs about the usb host on rpi4 with 4G ram, and I found the kernel in the github already had the fix for this issue, and besides this fix, it also had 106 more patches than our eoan kernel, those patches were merged during or after we prepared our eoan kernel, now let us pick those patches to our eoan too. [Fix] For the usb host issue, it adds a fix by setting the usb dma bounce buffer under 1G. [Test Case] some users and I alreaady tested the armhf and arm64 kernel on pi4 and pi3 boards, the usb host worked well and no other regressions introduced. [Regression Risk] Low, these patches are from the github which is the pi official kernel repository. And we already tested armhf and arm64 kernel on pi4/3 boards. The rpi kernel of https://github.com/raspberrypi/linux.git has been updated, for the branch of rpi-5.3.y (Eoan kernel base on this branch), there are 107 new patches merged, we also need to merge those patches to Eoan kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1849623/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848790] Re: USB not working under arm64 on Pi4
@all There is a new kernel in -proposed that should fix these USB issues as well as the KVM support. There is still a known issue with audio as is explained in comment #14 above. Please test the -proposed kernel and let us know of any issues that you find. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1848790 Title: USB not working under arm64 on Pi4 Status in linux-raspi2 package in Ubuntu: Confirmed Bug description: Ubuntu 19.10 arm64 on a Raspberry Pi 4 does not recognize a keyboard which works successfully on the same Raspberry Pi 4 with Ubuntu 19.10 armhf. Both USB hubs (2 and 3) were tested, without the OS seeing the keyboard on either. Booting the arm64 image on a Raspberry Pi 3, the keyboard worked successfully. Output of lsusb under arm64 on a Pi 3: ubuntu@ubuntu:~$ lsusb Bus 001 Device 007: ID 413c:2106 Dell Computer Corp. Dell QuietKey Keyboard Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Output of lsusb under armhf on a Pi 4 (same keyboard attached): ubuntu@ubuntu:~$ lsusb Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 413c:2106 Dell Computer Corp. Dell QuietKey Keyboard Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Output of lsusb under arm64 on the same Pi 4 (same keyboard attached): ubuntu@ubuntu:~$ lsusb Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub The fact even the VIA Labs hub doesn't show up (which is built in) suggests the kernel is (for some reason) unable to enumerate anything against the USB hubs. == Temporary Workaround == As noted by various people below, the following line can be added to the "usercfg.txt" file on the boot partition: total_mem=3072 This will limit the available RAM to 3Gb, but otherwise things should operate normally. Note that this bug does not affect Pi 4Bs with less than 4Gb of RAM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848790/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1845861] Re: package grub-efi-amd64 2.02-2ubuntu8.13 failed to install/upgrade: installed grub-efi-amd64 package post-installation script subprocess returned error exit status 1
@mahesh, Did you subscribe to the canonical-kernel-team ppa at: https://launchpad.net/~canonical-kernel- team/+archive/ubuntu/ppa/+packages ? If you did, can you tell me why? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-oem in Ubuntu. https://bugs.launchpad.net/bugs/1845861 Title: package grub-efi-amd64 2.02-2ubuntu8.13 failed to install/upgrade: installed grub-efi-amd64 package post-installation script subprocess returned error exit status 1 Status in grub2 package in Ubuntu: New Status in linux-signed-oem package in Ubuntu: New Bug description: package grub-efi-amd64 2.02-2ubuntu8.13 failed to install/upgrade: installed grub-efi-amd64 package post-installation script subprocess returned error exit status 1 ProblemType: Package DistroRelease: Ubuntu 18.04 Package: grub-efi-amd64 2.02-2ubuntu8.13 ProcVersionSignature: Ubuntu 4.15.0-1024.29-oem 4.15.18 Uname: Linux 4.15.0-1024-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 Date: Sun Sep 29 12:12:06 2019 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+loki-n3-v3-whl+X32+loki-n3+X00 ErrorMessage: installed grub-efi-amd64 package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2019-09-29 (0 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1024-oem.efi.signed root=UUID=5b8500c1-09d2-4cc8-804e-1acd636a7293 ro mem_sleep_default=deep usbcore.quirks=2386:3119:k quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.6, Python 3.6.8, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.3 apt 1.6.12 SourcePackage: grub2 Title: package grub-efi-amd64 2.02-2ubuntu8.13 failed to install/upgrade: installed grub-efi-amd64 package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1845861/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1844939] Re: nvidia dkms failure on upgrade from disco to eoan
** Attachment added: "/var/lib/dkms/nvidia/390.129/build/make.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1844939/+attachment/5290963/+files/make.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1844939 Title: nvidia dkms failure on upgrade from disco to eoan Status in linux package in Ubuntu: Confirmed Bug description: INFO:Enable nvidia DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/put_your_quirks_here DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/dell_latitude DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/lenovo_thinkpad Removing old nvidia-390.129 DKMS files... -- Deleting module version: 390.129 completely from the DKMS tree. -- Done. Loading new nvidia-390.129 DKMS files... Building for 5.0.0-29-generic 5.3.0-10-generic Building for architecture x86_64 Building initial module for 5.0.0-29-generic ERROR (dkms apport): kernel package linux-headers-5.0.0-29-generic is not supported Error! Bad return status for module build on kernel: 5.0.0-29-generic (x86_64) Consult /var/lib/dkms/nvidia/390.129/build/make.log for more information. dpkg: error processing package nvidia-dkms-390 (--configure): installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 dpkg: dependency problems prevent configuration of nvidia-driver-390: nvidia-driver-390 depends on nvidia-dkms-390 (= 390.129-0ubuntu1); however: Package nvidia-dkms-390 is not configured yet. dpkg: error processing package nvidia-driver-390 (--configure): dependency problems - leaving unconfigured No apport report written because the error message indicates its a followup error from a previous failure. Processing triggers for linux-image-5.3.0-10-generic (5.3.0-10.11) ... /etc/kernel/postinst.d/dkms: * dkms: running auto installation service for kernel 5.3.0-10-generic Kernel preparation unnecessary for this kernel. Skipping... Building module: cleaning build area... unset ARCH; env NV_VERBOSE=1 'make' -j12 NV_EXCLUDE_BUILD_MODULES='' KERNEL_UNAME=5.3.0-10-generic IGNORE_XEN_PRESENCE=1 IGNORE_CC_MISMATCH=1 SYSSRC=/lib/modules/5.3.0-10-generic/build LD=/usr/bin/ld.bfd modules cleaning build area... DKMS: build completed. nvidia.ko: Running module version sanity check. modinfo: ERROR: missing module or filename. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.3.0-10-generic/updates/dkms/ nvidia-modeset.ko: Running module version sanity check. modinfo: ERROR: missing module or filename. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.3.0-10-generic/updates/dkms/ nvidia-drm.ko: Running module version sanity check. modinfo: ERROR: missing module or filename. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.3.0-10-generic/updates/dkms/ nvidia-uvm.ko: Running module version sanity check. modinfo: ERROR: missing module or filename. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.3.0-10-generic/updates/dkms/ depmod... DKMS: install completed. ...done. /etc/kernel/postinst.d/initramfs-tools: update-initramfs: Generating /boot/initrd.img-5.3.0-10-generic /etc/kernel/postinst.d/zz-update-grub: Sourcing file `/etc/default/grub' Sourcing file `/etc/default/grub.d/init-select.cfg' Generating grub configuration file ... Found linux image: /boot/vmlinuz-5.3.0-10-generic Found initrd image: /boot/initrd.img-5.3.0-10-generic Found linux image: /boot/vmlinuz-5.0.0-29-generic Found initrd image: /boot/initrd.img-5.0.0-29-generic Found linux image: /boot/vmlinuz-5.0.0-28-generic Found initrd image: /boot/initrd.img-5.0.0-28-generic Found memtest86+ image: /boot/memtest86+.elf Found memtest86+ image: /boot/memtest86+.bin Found Ubuntu 16.04.3 LTS (16.04) on /dev/sda1 done Processing triggers for initramfs-tools (0.133ubuntu10) ... update-initramfs: Generating /boot/initrd.img-5.3.0-10-generic Processing triggers for dictionaries-common (1.28.1) ... Processing triggers for libc-bin (2.30-0ubuntu1) ... Processing triggers for rygel (0.38.1-2ubuntu2) ... Processing triggers for tex-common (6.12) ... Running updmap-sys. This may take some time... done. Running mktexlsr /var/lib/texmf ... done. Building format(s) --all. This may take some time... done. Processing triggers for libgdk-pixbuf2.0-0:amd64 (2.39.2-3) ... Processin
