[Kernel-packages] [Bug 2049248] Re: Kernel 6.5 breaks display brightness controls and sets it to 100% all the time
Further information: I am using "xrandr --brightness …" in a background script that repeats every third of a second, to keep the brightness where I need it whenever the system resets it to 100%. I've noticed that the system resets the brightness *exactly* every 60 seconds, with five resets over five seconds (the screen flashes each time before my script resets it). The resets aren't equally timed, but they always follow the same consistent pattern. However, the system sometimes leaves the brightness alone for a longer period before reverting to resetting each minute. I would love to be able to help by diagnosing what is causing that weird behaviour. The problem is that I have no clue whatsoever where to start. -- 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/2049248 Title: Kernel 6.5 breaks display brightness controls and sets it to 100% all the time Status in linux-signed-hwe-6.5 package in Ubuntu: Confirmed Bug description: Since kernel 6.5, monitor brightness is set to 100%, and cannot be changed: The brightness controls have disappeared from Settings, and brightness doesn't respond to the keypad controls. See the attached screenshot, showing the difference between the settings in kernels 6.2 and 6.5. This applies to Ubuntu 22.04 and 23.10, whether using Wayland or X.Org. It's possible (when using X.Org) to adjust the brightness with… $ xrandr --output [monitor] --brightness [brightness] e.g. on my machine… $ xrandr --output eDP-1 --brightness 0.5 … but, unfortunately, it doesn't last long — anywhere between a less than a second later and about a minute later, the screen reverts to 100% brightness. As a workaround, I am running the following command in the background… $ while true; do xrandr --output eDP-1 --brightness 0.5; sleep 1s; done … which results in the screen at the correct brightness, but frequently flashing! Tested on: • Ubuntu 22.04 — Kernel 6.2.0-39 and prior works correctly — Kernel 6.5.0-14 has the problem • Ubuntu 23.10 — Kernel 6.5.0-9 has the problem $ sudo lshw -numeric -C display *-display description: VGA compatible controller product: CometLake-S GT2 [UHD Graphics 630] [8086:9BC5] vendor: Intel Corporation [8086] physical id: 2 bus info: pci@:00:02.0 logical name: /dev/fb0 version: 05 width: 64 bits clock: 33MHz capabilities: pciexpress msi pm vga_controller bus_master cap_list rom fb configuration: depth=32 driver=i915 latency=0 resolution=1920,1080 resources: irq:145 memory:c100-c1ff memory:d000-dfff ioport:3000(size=64) memory:c-d ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-14-generic 6.5.0-14.14~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Jan 13 07:19:58 2024 InstallationDate: Installed on 2022-08-28 (502 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: linux-signed-hwe-6.5 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2049248/+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 2048735] Re: Disable keyboard wakeup for Framework 13
and yes, I agree 6.1 should be skipped at this point ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: New => Won't Fix -- 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/2048735 Title: Disable keyboard wakeup for Framework 13 Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Won't Fix Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux source package in Noble: Fix Released Status in linux-oem-6.1 source package in Noble: Invalid Status in linux-oem-6.5 source package in Noble: Invalid Bug description: Framework 13" AMD version has an unexpected behavior that EC triggers a keyboard wakeup event every time the system exits s0i3. This EC keyboard wakeup event is to workaround a different bug. Because of this, the following series is sent to mailing list to disable wakeup from keyboard when on latest BIOS for Framework 13 AMD. https://lore.kernel.org/platform-driver-x86/20231212045006.97581-1-mario.limoncie...@amd.com/T/#mca26ce4d4358b188fc61e8b32c27d62410780c5a 85980669a863 platform/x86/amd/pmc: Move platform defines to header 2d53c0ab61e6 platform/x86/amd/pmc: Only run IRQ1 firmware version check on Cezanne b614a4bd73ef platform/x86/amd/pmc: Move keyboard wakeup disablement detection to pmc-quirks a55bdad5dfd1 platform/x86/amd/pmc: Disable keyboard wakeup on AMD Framework 13 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2048735/+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 2048735] Re: Disable keyboard wakeup for Framework 13
they applied cleanly when cherry-picking to 6.5 ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Status: New => Fix Committed -- 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/2048735 Title: Disable keyboard wakeup for Framework 13 Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Won't Fix Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux source package in Noble: Fix Released Status in linux-oem-6.1 source package in Noble: Invalid Status in linux-oem-6.5 source package in Noble: Invalid Bug description: Framework 13" AMD version has an unexpected behavior that EC triggers a keyboard wakeup event every time the system exits s0i3. This EC keyboard wakeup event is to workaround a different bug. Because of this, the following series is sent to mailing list to disable wakeup from keyboard when on latest BIOS for Framework 13 AMD. https://lore.kernel.org/platform-driver-x86/20231212045006.97581-1-mario.limoncie...@amd.com/T/#mca26ce4d4358b188fc61e8b32c27d62410780c5a 85980669a863 platform/x86/amd/pmc: Move platform defines to header 2d53c0ab61e6 platform/x86/amd/pmc: Only run IRQ1 firmware version check on Cezanne b614a4bd73ef platform/x86/amd/pmc: Move keyboard wakeup disablement detection to pmc-quirks a55bdad5dfd1 platform/x86/amd/pmc: Disable keyboard wakeup on AMD Framework 13 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2048735/+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 2046504] Re: Fix AMDGPU display on lower resolution modes
** Tags added: originate-from-2047489 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2046504 Title: Fix AMDGPU display on lower resolution modes Status in HWE Next: In Progress Status in linux package in Ubuntu: Confirmed Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: Fix Committed Bug description: [Impact] AMD GPU display is blank when set lower resolution than native mode on eDP. [Fix] On eDP the invalid modes are set, call mode set for valid modes instead. [Test] Tested on hardware, all the modes shown in gnome menu can be set OK. [Where problems could occur] It may break AMD display. This issue is not reproduced on v6.2- kernel versions, so SRU for oem-6.5 only. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2046504/+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 2049579] [NEW] package linux-lowlatency-tools-6.6.0-14 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/libcpupower.so.6.6.0-14', which is also in packag
Public bug reported: aptitude -> update -> upgrade all upgradable packages -> dpkg fails because of conflict with linux-tools-generic ProblemType: Package DistroRelease: Ubuntu 24.04 Package: linux-lowlatency-tools-6.6.0-14 (not installed) ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu6 AptOrdering: linux-lowlatency-tools-6.6.0-14:amd64: Install linux-tools-6.6.0-14-lowlatency:amd64: Install linux-tools-lowlatency:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config Date: Wed Jan 17 00:18:22 2024 DpkgTerminalLog: Preparing to unpack .../linux-lowlatency-tools-6.6.0-14_6.6.0-14.14.1_amd64.deb ... Unpacking linux-lowlatency-tools-6.6.0-14 (6.6.0-14.14.1) ... dpkg: error processing archive /var/cache/apt/archives/linux-lowlatency-tools-6.6.0-14_6.6.0-14.14.1_amd64.deb (--unpack): trying to overwrite '/usr/lib/libcpupower.so.6.6.0-14', which is also in package linux-tools-6.6.0-14 6.6.0-14.14 DuplicateSignature: package:linux-lowlatency-tools-6.6.0-14:(not installed) Unpacking linux-lowlatency-tools-6.6.0-14 (6.6.0-14.14.1) ... dpkg: error processing archive /var/cache/apt/archives/linux-lowlatency-tools-6.6.0-14_6.6.0-14.14.1_amd64.deb (--unpack): trying to overwrite '/usr/lib/libcpupower.so.6.6.0-14', which is also in package linux-tools-6.6.0-14 6.6.0-14.14 ErrorMessage: trying to overwrite '/usr/lib/libcpupower.so.6.6.0-14', which is also in package linux-tools-6.6.0-14 6.6.0-14.14 InstallationDate: Installed on 2023-11-18 (60 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) Python3Details: /usr/bin/python3.11, Python 3.11.7, python3-minimal, 3.11.4-5 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.22.2ubuntu2 apt 2.7.6 SourcePackage: linux-lowlatency Title: package linux-lowlatency-tools-6.6.0-14 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/libcpupower.so.6.6.0-14', which is also in package linux-tools-6.6.0-14 6.6.0-14.14 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-lowlatency (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check noble package-conflict -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lowlatency in Ubuntu. https://bugs.launchpad.net/bugs/2049579 Title: package linux-lowlatency-tools-6.6.0-14 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/libcpupower.so.6.6.0-14', which is also in package linux- tools-6.6.0-14 6.6.0-14.14 Status in linux-lowlatency package in Ubuntu: New Bug description: aptitude -> update -> upgrade all upgradable packages -> dpkg fails because of conflict with linux-tools-generic ProblemType: Package DistroRelease: Ubuntu 24.04 Package: linux-lowlatency-tools-6.6.0-14 (not installed) ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu6 AptOrdering: linux-lowlatency-tools-6.6.0-14:amd64: Install linux-tools-6.6.0-14-lowlatency:amd64: Install linux-tools-lowlatency:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config Date: Wed Jan 17 00:18:22 2024 DpkgTerminalLog: Preparing to unpack .../linux-lowlatency-tools-6.6.0-14_6.6.0-14.14.1_amd64.deb ... Unpacking linux-lowlatency-tools-6.6.0-14 (6.6.0-14.14.1) ... dpkg: error processing archive /var/cache/apt/archives/linux-lowlatency-tools-6.6.0-14_6.6.0-14.14.1_amd64.deb (--unpack): trying to overwrite '/usr/lib/libcpupower.so.6.6.0-14', which is also in package linux-tools-6.6.0-14 6.6.0-14.14 DuplicateSignature: package:linux-lowlatency-tools-6.6.0-14:(not installed) Unpacking linux-lowlatency-tools-6.6.0-14 (6.6.0-14.14.1) ... dpkg: error processing archive /var/cache/apt/archives/linux-lowlatency-tools-6.6.0-14_6.6.0-14.14.1_amd64.deb (--unpack): trying to overwrite '/usr/lib/libcpupower.so.6.6.0-14', which is also in package linux-tools-6.6.0-14 6.6.0-14.14 ErrorMessage: trying to overwrite '/usr/lib/libcpupower.so.6.6.0-14', which is also in package linux-tools-6.6.0-14 6.6.0-14.14 InstallationDate: Installed on 2023-11-18 (60 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) Python3Details: /usr/bin/python3.11, Python 3.11.7, python3-minimal, 3.11.4-5 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks.
[Kernel-packages] [Bug 2039991] Re: UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.2-n2KLlt (drivers/gpu/drm/amd/amdgpu/../display/dc/irq/dce110/irq_service_dce110.c)
Ubuntu MATE 22.04.3 LTS Linux hp 6.5.0-14-generic #14~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Mon Nov 20 18:15:30 UTC 2 x86_64 x86_64 x86_64 GNU/Linux I'm getting several of these messages at boot time. Here's one of them: UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.5-q7NZ0T/linux-hwe-6.5-6.5.0/drivers/gpu/drm/radeon/kv_dpm.c:2509:32 index 48 is out of range for type 'UCHAR [1]' -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2039991 Title: UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.2-n2KLlt (drivers/gpu/drm/amd/amdgpu/../display/dc/irq/dce110/irq_service_dce110.c) Status in linux package in Ubuntu: Incomplete Status in linux-hwe-6.2 package in Ubuntu: Confirmed Bug description: Everything works fine, this error shows up in the boot log. Description: Ubuntu 22.04.3 LTS Release: 22.04 Ubuntu 6.2.0-35.35~22.04.1-generic 6.2.16 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde PRO [Radeon HD 7750/8740 / R7 250E] driverInfo = Mesa 23.2.1 - kisak-mesa PPA (LLVM 15.0.7) oct 20 18:12:33 H-Linux kernel: oct 20 18:12:33 H-Linux kernel: UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.2-n2KLlt/linux-hwe-6.2-6.2.0/drivers/gpu/drm/amd/amdgpu/../display/dc/irq/dce110/irq_service_dce110.c:215:39 oct 20 18:12:33 H-Linux kernel: index 178 is out of range for type 'pipe_ctx [6]' oct 20 18:12:33 H-Linux kernel: CPU: 1 PID: 865 Comm: canonical-livep Not tainted 6.2.0-35-generic #35~22.04.1-Ubuntu oct 20 18:12:33 H-Linux kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./960GC-GS FX, BIOS P1.60 10/20/2014 oct 20 18:12:33 H-Linux kernel: Call Trace: oct 20 18:12:33 H-Linux kernel: oct 20 18:12:33 H-Linux kernel: dump_stack_lvl+0x48/0x70 oct 20 18:12:33 H-Linux kernel: dump_stack+0x10/0x20 oct 20 18:12:33 H-Linux kernel: __ubsan_handle_out_of_bounds+0xa2/0x100 oct 20 18:12:33 H-Linux kernel: dce110_vblank_set+0xc9/0xd0 [amdgpu] oct 20 18:12:33 H-Linux kernel: dal_irq_service_set+0x67/0x100 [amdgpu] oct 20 18:12:33 H-Linux kernel: dc_interrupt_set+0x24/0x40 [amdgpu] oct 20 18:12:33 H-Linux kernel: dm_set_vupdate_irq+0x38/0x90 [amdgpu] oct 20 18:12:33 H-Linux kernel: dm_set_vblank+0x173/0x1d0 [amdgpu] oct 20 18:12:33 H-Linux kernel: dm_disable_vblank+0x10/0x20 [amdgpu] oct 20 18:12:33 H-Linux kernel: drm_vblank_disable_and_save+0xfd/0x150 [drm] oct 20 18:12:33 H-Linux kernel: vblank_disable_fn+0x74/0xa0 [drm] oct 20 18:12:33 H-Linux kernel: ? __pfx_vblank_disable_fn+0x10/0x10 [drm] oct 20 18:12:33 H-Linux kernel: call_timer_fn+0x2c/0x160 oct 20 18:12:33 H-Linux kernel: ? __pfx_vblank_disable_fn+0x10/0x10 [drm] oct 20 18:12:33 H-Linux kernel: __run_timers.part.0+0x1fb/0x2b0 oct 20 18:12:33 H-Linux kernel: ? __pfx_tick_sched_timer+0x10/0x10 oct 20 18:12:33 H-Linux kernel: ? __pfx_native_apic_mem_write+0x10/0x10 oct 20 18:12:33 H-Linux kernel: ? lapic_next_event+0x20/0x30 oct 20 18:12:33 H-Linux kernel: ? clockevents_program_event+0xb5/0x140 oct 20 18:12:33 H-Linux kernel: run_timer_softirq+0x2a/0x60 oct 20 18:12:33 H-Linux kernel: __do_softirq+0xdd/0x330 oct 20 18:12:33 H-Linux kernel: ? hrtimer_interrupt+0x12b/0x250 oct 20 18:12:33 H-Linux kernel: __irq_exit_rcu+0xa2/0xd0 oct 20 18:12:33 H-Linux kernel: irq_exit_rcu+0xe/0x20 oct 20 18:12:33 H-Linux kernel: sysvec_apic_timer_interrupt+0x96/0xb0 oct 20 18:12:33 H-Linux kernel: oct 20 18:12:33 H-Linux kernel: oct 20 18:12:33 H-Linux kernel: asm_sysvec_apic_timer_interrupt+0x1b/0x20 oct 20 18:12:33 H-Linux kernel: RIP: 0010:lzma_literal+0x100/0x2a0 oct 20 18:12:33 H-Linux kernel: Code: ff 00 77 22 48 8b 73 18 4c 8b 53 10 c1 e1 08 c1 e2 08 89 0b 4c 8d 5e 01 4c 89 5b 18 41 0f b6 34 32 01 f2 89 53 04 45 0f b7 10 <89> ce 01 c0 c1 ee 0b 41 0f af f2 39 d6 77 9b> oct 20 18:12:33 H-Linux kernel: RSP: 0018:b21d4167f748 EFLAGS: 0216 oct 20 18:12:33 H-Linux kernel: RAX: 0001 RBX: 8e7f86cf8000 RCX: 09d930a8 oct 20 18:12:33 H-Linux kernel: RDX: 04455f07 RSI: 04455f07 RDI: 8e7f86cf8f0c oct 20 18:12:33 H-Linux kernel: RBP: b21d4167f770 R08: 8e7f86cf8f0e R09: 0800 oct 20 18:12:33 H-Linux kernel: R10: 071a R11: R12: oct 20 18:12:33 H-Linux kernel: R13: 0003 R14: 0001 R15: 0003 oct 20 18:12:33 H-Linux kernel: lzma_main+0x85/0x2b0 oct 20 18:12:33 H-Linux kernel: lzma2_lzma+0x1c0/0x3f0 oct 20 18:12:33 H-Linux kernel: xz_dec_lzma2_run+0x83/0x4e0 oct 20 18:12:33 H-Linux kernel: dec_block+0x184/0x1a0 oct 20 18:12:33 H-Linux kernel: dec_main+0x2dc/0x4e0 oct 20 18:12:33 H-Linux kernel:
[Kernel-packages] [Bug 2046504] Re: Fix AMDGPU display on lower resolution modes
** Tags added: originate-from-2047680 ** No longer affects: oem-priority -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2046504 Title: Fix AMDGPU display on lower resolution modes Status in HWE Next: In Progress Status in linux package in Ubuntu: Confirmed Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: Fix Committed Bug description: [Impact] AMD GPU display is blank when set lower resolution than native mode on eDP. [Fix] On eDP the invalid modes are set, call mode set for valid modes instead. [Test] Tested on hardware, all the modes shown in gnome menu can be set OK. [Where problems could occur] It may break AMD display. This issue is not reproduced on v6.2- kernel versions, so SRU for oem-6.5 only. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2046504/+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 2049571] Re: module fails to compile nvidia-470.223.02 for kernel 6.5.0-14-generic (x86_64)
The problems solved on installing gcc-12 from launchpad ppa and reinstalling kernel package -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/2049571 Title: module fails to compile nvidia-470.223.02 for kernel 6.5.0-14-generic (x86_64) Status in nvidia-graphics-drivers-470 package in Ubuntu: New Bug description: During installation of 6.5.0-14 the nvidia modules compilation exists with error dkms compile log attached ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nvidia-driver-470 470.223.02-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jan 17 10:11:04 2024 InstallationDate: Installed on 2022-05-03 (623 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: nvidia-graphics-drivers-470 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/2049571/+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 2049570] [NEW] 10de:28B9 was not supported in nvidia-driver-535
Public bug reported: On OEM project, we found the 28B9 is not supported in nvidia-driver-535, the version 535.154.05-0ubuntu0.22.04.1 in the proposed channel also doesn't include this id. ** Affects: oem-priority Importance: Undecided Status: New ** Affects: nvidia-graphics-drivers-535 (Ubuntu) Importance: Undecided Status: New ** Tags: oem-priority originate-from-2049497 sutton ** Tags added: oem-priority originate-from-2049497 sutton -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-535 in Ubuntu. https://bugs.launchpad.net/bugs/2049570 Title: 10de:28B9 was not supported in nvidia-driver-535 Status in OEM Priority Project: New Status in nvidia-graphics-drivers-535 package in Ubuntu: New Bug description: On OEM project, we found the 28B9 is not supported in nvidia- driver-535, the version 535.154.05-0ubuntu0.22.04.1 in the proposed channel also doesn't include this id. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2049570/+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 2049571] [NEW] module fails to compile nvidia-470.223.02 for kernel 6.5.0-14-generic (x86_64)
Public bug reported: During installation of 6.5.0-14 the nvidia modules compilation exists with error dkms compile log attached ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nvidia-driver-470 470.223.02-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jan 17 10:11:04 2024 InstallationDate: Installed on 2022-05-03 (623 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: nvidia-graphics-drivers-470 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-470 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy third-party-packages ** Attachment added: "make.log" https://bugs.launchpad.net/bugs/2049571/+attachment/5740077/+files/make.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/2049571 Title: module fails to compile nvidia-470.223.02 for kernel 6.5.0-14-generic (x86_64) Status in nvidia-graphics-drivers-470 package in Ubuntu: New Bug description: During installation of 6.5.0-14 the nvidia modules compilation exists with error dkms compile log attached ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nvidia-driver-470 470.223.02-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jan 17 10:11:04 2024 InstallationDate: Installed on 2022-05-03 (623 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: nvidia-graphics-drivers-470 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/2049571/+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 2049569] Re: Enable the mic-mute led on Dell MTL laptops
** Tags added: oem-priority originate-from-2047635 somerville -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2049569 Title: Enable the mic-mute led on Dell MTL laptops Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux-oem-6.5 package in Ubuntu: New Status in linux source package in Jammy: New Status in linux-oem-6.5 source package in Jammy: New Status in linux source package in Noble: New Status in linux-oem-6.5 source package in Noble: New Bug description: [Impact] On Dell's Precision 3550, Intel MTL platform, the MIC-Mute function is working but the LED(on F4) state is not changed accordingly. [Fix] There's no problem on the same series on RPL platform. It needs MTL specific SoF driver and controls to support the registered mixer switch. [Test Case] 1. press mic-mute hot-key and check if mic-mute is enabled or not by the OSD icon. 2. The mic-mute led should be ON when mic-mute enabled, OFF when disabled. [Where problems could occur] It's only required for new sof-audio-pci-intel-mtl driver. The impact should be restricting. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2049569/+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 2049569] [NEW] Enable the mic-mute led on Dell MTL laptops
Public bug reported: [Impact] On Dell's Precision 3550, Intel MTL platform, the MIC-Mute function is working but the LED(on F4) state is not changed accordingly. [Fix] There's no problem on the same series on RPL platform. It needs MTL specific SoF driver and controls to support the registered mixer switch. [Test Case] 1. press mic-mute hot-key and check if mic-mute is enabled or not by the OSD icon. 2. The mic-mute led should be ON when mic-mute enabled, OFF when disabled. [Where problems could occur] It's only required for new sof-audio-pci-intel-mtl driver. The impact should be restricting. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux-oem-6.5 (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: linux-oem-6.5 (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Affects: linux-oem-6.5 (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu) Importance: Undecided Status: New ** Description changed: [Impact] On Dell's Precision 3550, Intel MTL platform, the MIC-Mute function is working but the LED(on F4) state is not changed accordingly. [Fix] - There's no problem on the same series on RPL platform. It needs MTL specific SoF driver to support the registered mixer switch. + There's no problem on the same series on RPL platform. It needs MTL specific SoF driver and controls to support the registered mixer switch. [Test Case] 1. press mic-mute hot-key and check if mic-mute is enabled or not by the OSD icon. 2. The mic-mute led should be ON when mic-mute enabled, OFF when disabled. [Where problems could occur] - It's only required for new sof-audio-pci-intel-mtl driver. The impact should be low. + It's only required for new sof-audio-pci-intel-mtl driver. The impact should be restricting. -- 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/2049569 Title: Enable the mic-mute led on Dell MTL laptops Status in linux package in Ubuntu: New Status in linux-oem-6.5 package in Ubuntu: New Status in linux source package in Jammy: New Status in linux-oem-6.5 source package in Jammy: New Status in linux source package in Noble: New Status in linux-oem-6.5 source package in Noble: New Bug description: [Impact] On Dell's Precision 3550, Intel MTL platform, the MIC-Mute function is working but the LED(on F4) state is not changed accordingly. [Fix] There's no problem on the same series on RPL platform. It needs MTL specific SoF driver and controls to support the registered mixer switch. [Test Case] 1. press mic-mute hot-key and check if mic-mute is enabled or not by the OSD icon. 2. The mic-mute led should be ON when mic-mute enabled, OFF when disabled. [Where problems could occur] It's only required for new sof-audio-pci-intel-mtl driver. The impact should be restricting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049569/+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 2043665] Re: Hundreds of errors per second: kernel: pcieport 0000:00:1c.3: PCIe Bus Error
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
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/2043665
Title:
Hundreds of errors per second: kernel: pcieport :00:1c.3: PCIe Bus
Error
Status in linux package in Ubuntu:
Expired
Bug description:
After a fresh 23.10 install I have noticed that booting up my PC in
the morning was taking a long time. Checking journalctl there are
hundreds of warnings generated every second, and not only at boot
time (see below). Searching for this problem I found a stopgap
solution by adding this instruction in GRUB:
pcie_aspm=off
However, as a plain Ubuntu user I should be having this problem of
long boot times and edit GRUB to "fix" it, when the problem captured
in the log isn't even fixed, I just avoided it with instruction. This
is why I'm reporting it in case it helps find the original cause.
Previously I was running 23.04 on the same PC and booting times were
short, just normal. I believe this is a new problem even when the
hardware is the same and I haven't done any changes apart from
upgrading.
The errors are all the same:
Nov 16 09:26:37 quiet kernel: pcieport :00:1c.3: AER: Corrected error
received: :00:1c.3
Nov 16 09:26:37 quiet kernel: pcieport :00:1c.3: PCIe Bus Error:
severity=Corrected, type=Physical Layer, (Receiv>
Nov 16 09:26:37 quiet kernel: pcieport :00:1c.3: device [8086:7abb]
error status/mask=0001/2000
Nov 16 09:26:37 quiet kernel: pcieport :00:1c.3:[ 0] RxErr
(First)
Nov 16 09:26:37 quiet kernel: pcieport :00:1c.3: AER: Corrected error
received: :00:1c.3
Nov 16 09:26:37 quiet kernel: pcieport :00:1c.3: PCIe Bus Error:
severity=Corrected, type=Physical Layer, (Receiv>
Nov 16 09:26:37 quiet kernel: pcieport :00:1c.3: device [8086:7abb]
error status/mask=0001/2000
Nov 16 09:26:37 quiet kernel: pcieport :00:1c.3:[ 0] RxErr
(First)
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-10-generic 6.5.0-10.10
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CRDA: N/A
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Thu Nov 16 09:38:28 2023
InstallationDate: Installed on 2023-11-13 (2 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64
(20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-10-generic
root=UUID=fa113624-262e-4625-ba8b-eabf66ab696c ro pcie_aspm=off
RelatedPackageVersions:
linux-restricted-modules-6.5.0-10-generic N/A
linux-backports-modules-6.5.0-10-generic N/A
linux-firmware20230919.git3672ccab-0ubuntu2.2
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/03/2021
dmi.bios.release: 5.24
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: A.10
dmi.board.asset.tag: Default string
dmi.board.name: MPG Z690 FORCE WIFI (MS-7D30)
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: 2.0
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: 2.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrA.10:bd12/03/2021:br5.24:svnMicro-StarInternationalCo.,Ltd.:pnMS-7D30:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnMPGZ690FORCEWIFI(MS-7D30):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0:skuDefaultstring:
dmi.product.family: Default string
dmi.product.name: MS-7D30
dmi.product.sku: Default string
dmi.product.version: 2.0
dmi.sys.vendor: Micro-Star International Co., Ltd.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2043665/+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 2043561] Re: rtl8761bu bluetooth dongle bails out or looses device connection
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/2043561 Title: rtl8761bu bluetooth dongle bails out or looses device connection Status in linux package in Ubuntu: Expired Bug description: Environment: Bluetooth dongle connected to integrated Hub -> bluetooth mouse After a fresh boot into (K)ubuntu, the dongle/mouse works. Then, after some minutes, the mouse stops working. Errors: A) Some times, the bluetooth dongle is gone and I have to re-plug it to make it work again. B) Some times, it is enough, to deactivate and activate bluetooth in the settings. What is strange is, that I can't find any crash or similar entries in the logs for A). Following the "dmesg|grep -i bluetooth" and the "journalctl" of that moment: ─$ sudo dmesg|grep -i bluetooth [2.017029] usb 1-8.1: Product: Bluetooth Radio [ 16.482420] Bluetooth: Core ver 2.22 [ 16.482513] NET: Registered PF_BLUETOOTH protocol family [ 16.482515] Bluetooth: HCI device and connection manager initialized [ 16.482548] Bluetooth: HCI socket layer initialized [ 16.482549] Bluetooth: L2CAP socket layer initialized [ 16.482553] Bluetooth: SCO socket layer initialized [ 16.639986] Bluetooth: hci0: RTL: examining hci_ver=0a hci_rev=000b lmp_ver=0a lmp_subver=8761 [ 16.640993] Bluetooth: hci0: RTL: rom_version status=0 version=1 [ 16.640996] Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_fw.bin [ 16.643667] Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_config.bin [ 16.643720] Bluetooth: hci0: RTL: cfg_sz 6, total sz 30210 [ 16.796044] Bluetooth: hci0: RTL: fw version 0xdfc6d922 [ 17.340032] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 17.340034] Bluetooth: BNEP filters: protocol multicast [ 17.340036] Bluetooth: BNEP socket layer initialized [ 17.340857] Bluetooth: MGMT ver 1.22 [ 25.315698] Bluetooth: RFCOMM TTY layer initialized [ 25.315714] Bluetooth: RFCOMM socket layer initialized [ 25.315721] Bluetooth: RFCOMM ver 1.11 [ 173.107927] hid-generic 0005:046D:B031.0003: input,hidraw2: BLUETOOTH HID v0.10 Mouse [LIFT] on a0:9f:10:be:79:e4 [ 1698.769225] usb 1-8.4: Product: Bluetooth Radio [ 1698.782108] Bluetooth: hci0: RTL: examining hci_ver=0a hci_rev=000b lmp_ver=0a lmp_subver=8761 [ 1698.783105] Bluetooth: hci0: RTL: rom_version status=0 version=1 [ 1698.783119] Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_fw.bin [ 1698.784771] Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_config.bin [ 1698.784945] Bluetooth: hci0: RTL: cfg_sz 6, total sz 30210 [ 1698.943074] Bluetooth: hci0: RTL: fw version 0xdfc6d922 [ 1699.011186] Bluetooth: MGMT ver 1.22 [ 1711.453643] hid-generic 0005:046D:B031.0004: input,hidraw2: BLUETOOTH HID v0.10 Mouse [LIFT] on a0:9f:10:be:79:e4 [ 1926.008318] Bluetooth: hci0: ACL packet for unknown connection handle 16 [ 1926.008337] Bluetooth: hci0: ACL packet for unknown connection handle 16 [ 1926.008345] Bluetooth: hci0: ACL packet for unknown connection handle 16 [ 1926.008352] Bluetooth: hci0: ACL packet for unknown connection handle 16 [ 1926.008358] Bluetooth: hci0: ACL packet for unknown connection handle 16 [ 1926.008364] Bluetooth: hci0: ACL packet for unknown connection handle 16 [ 1926.008370] Bluetooth: hci0: ACL packet for unknown connection handle 16 [ 1930.221737] hid-generic 0005:046D:B031.0005: input,hidraw2: BLUETOOTH HID v0.10 Mouse [LIFT] on a0:9f:10:be:79:e4 Nov 15 10:12:39 media-pc-lx dbus-daemon[1094]: [system] Rejected send message, 0 matched rules; type="error", sender=":1.57" (uid=1000 pid=4460 comm="/usr/bin/wireplumber" label="unconfined") interface="(unset)" member="(unset)" error name="org.bluez.MediaEndpoint1.Error.NotImplemented" requested_reply="0" destination=":1.3" (uid=0 pid=1093 comm="/usr/lib/bluetooth/bluetoothd" label="unconfined") Nov 15 10:12:39 media-pc-lx dbus-daemon[1094]: [system] Rejected send message, 0 matched rules; type="error", sender=":1.57" (uid=1000 pid=4460 comm="/usr/bin/wireplumber" label="unconfined") interface="(unset)" member="(unset)" error name="org.bluez.MediaEndpoint1.Error.NotImplemented" requested_reply="0" destination=":1.3" (uid=0 pid=1093 comm="/usr/lib/bluetooth/bluetoothd" label="unconfined") Nov 15 10:12:39 media-pc-lx dbus-daemon[1094]: [system] Rejected send message, 0 matched rules; type="error", sender=":1.57" (uid=1000 pid=4460 comm="/usr/bin/wireplumber" label="unconfined") interface="(unset)" member="(unset)" error name="org.bluez.MediaEndpoint1.Error.NotImplemented" requested_reply="0" destination=":1.3" (uid=0 pid=1093
[Kernel-packages] [Bug 2036281] Re: activate bpf LSM by default
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/2036281 Title: activate bpf LSM by default Status in linux package in Ubuntu: Expired Bug description: in Fedora/RHEL if I want to see if the bpf LSM is active/available in the kernel I can go here: [root@virtualrocky]# cat /sys/kernel/security/lsm lockdown,capability,yama,selinux,bpf[root@virtualrocky]# but if I do the same thing in Ubuntu 22.0.4 bpf is NOT there: root@virtual-ubuntu2204:/# cat /sys/kernel/security/lsm lockdown,capability,landlock,yama,apparmorroot@virtual-ubuntu2204:/# Please add bpf LSM to the CONFIG_LSM See discourse for background info https://discourse.ubuntu.com/t/ask-us-anything-about-ubuntu- kernels/27664/127?u=why2jjj root@virtual-ubuntu2204:/opt/# cat /proc/version_signature Ubuntu 5.15.0-82.91-generic 5.15.111 THANK YOU! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jfreyensee 2526 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-08-29 (17 days ago) InstallationMedia: Ubuntu-Server 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230810) MachineType: Parallels Software International Inc. Parallels Virtual Platform NonfreeKernelModules: prl_fs_freeze prl_fs prl_eth prl_tg Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-82-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro ProcVersionSignature: Ubuntu 5.15.0-82.91-generic 5.15.111 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-5.15.0-82-generic N/A linux-backports-modules-5.15.0-82-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.18 RfKill: Tags: jammy uec-images Uname: Linux 5.15.0-82-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 07/03/2023 dmi.bios.release: 18.3 dmi.bios.vendor: Parallels Software International Inc. dmi.bios.version: 18.3.2 (53621) dmi.board.name: Parallels Virtual Platform dmi.board.vendor: Parallels Software International Inc. dmi.board.version: None dmi.chassis.type: 2 dmi.chassis.vendor: Parallels Software International Inc. dmi.ec.firmware.release: 18.3 dmi.modalias: dmi:bvnParallelsSoftwareInternationalInc.:bvr18.3.2(53621):bd07/03/2023:br18.3:efr18.3:svnParallelsSoftwareInternationalInc.:pnParallelsVirtualPlatform:pvrNone:rvnParallelsSoftwareInternationalInc.:rnParallelsVirtualPlatform:rvrNone:cvnParallelsSoftwareInternationalInc.:ct2:cvr:skuUndefined: dmi.product.family: Parallels VM dmi.product.name: Parallels Virtual Platform dmi.product.sku: Undefined dmi.product.version: None dmi.sys.vendor: Parallels Software International Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036281/+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 2043686] Re: package linux-image-5.15.0-88-generic (not installed) failed to install/upgrade: installed linux-image-5.15.0-88-generic package pre-removal script subprocess retur
[Expired for linux-signed-hwe-5.15 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux-signed-hwe-5.15 (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2043686 Title: package linux-image-5.15.0-88-generic (not installed) failed to install/upgrade: installed linux-image-5.15.0-88-generic package pre- removal script subprocess returned error exit status 1 Status in linux-signed-hwe-5.15 package in Ubuntu: Expired Bug description: crashed on me ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.15.0-88-generic (not installed) ProcVersionSignature: Ubuntu 5.4.0-1.0~upboard5-generic 5.4.65 Uname: Linux 5.4.0-1-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Nov 15 23:21:42 2023 ErrorMessage: installed linux-image-5.15.0-88-generic package pre-removal script subprocess returned error exit status 1 InstallationDate: Installed on 2023-11-16 (0 days ago) InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.10 SourcePackage: linux-signed-hwe-5.15 Title: package linux-image-5.15.0-88-generic (not installed) failed to install/upgrade: installed linux-image-5.15.0-88-generic package pre-removal script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2023-11-16 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.15/+bug/2043686/+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 2043542] Re: Support Mediatek MT7925 WiFi/BT
verified linux-firmware/jammy-proposed version
20220329.git681281e4-0ubuntu3.25
** Tags added: verification-done-jammy
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2043542
Title:
Support Mediatek MT7925 WiFi/BT
Status in HWE Next:
New
Status in linux package in Ubuntu:
Fix Released
Status in linux-firmware package in Ubuntu:
In Progress
Status in linux-oem-6.5 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Invalid
Status in linux-firmware source package in Jammy:
Fix Committed
Status in linux-oem-6.5 source package in Jammy:
In Progress
Status in linux source package in Noble:
Fix Released
Status in linux-firmware source package in Noble:
In Progress
Status in linux-oem-6.5 source package in Noble:
Invalid
Bug description:
[kernel SRU Justification]
[Impact]
Mediatek MT7925 WiFi/Bluetooth not supported yet.
[Fix]
For WiFi, there are tons of patches to be backported from upstream
kernel v6.7 due to a massive refactoring was done to integrate
multiple mt79xx drivers into one before landing support for mt7925.
While these changes, mostly clean cherry-picks, are tied to each
other, and separating them may cause more efforts in the future, a
huge patchset of total number 144 is proposed.
For Bluetooth, upstream commit 4c92ae75ea7d ("Bluetooth: btusb: Add
support Mediatek MT7925") is required.
[Test Case]
Initial hardware support. One should be able to find WiFi/BT
interfaces up available along with proposed kernels.
[Where problems could occur]
Features for MT7925 are not all available at this moment, and expect
more fixes for every corner case.
[Other Info]
MT7925 is supported since v6.7, and we need it for oem-6.5 as well.
Nominate for Jammy and Noble.
[linux-firmware SRU Justification]
[Impact]
Missing firmware for Mediatek MT7925 WiFi/BT.
[Fix]
Upstream firmware commits:
- WiFi: 4de2d71b322b ("linux-firmware: add firmware for MT7925")
- Bluetooth: b83108216200 ("linux-firmware: add firmware for mediatek
bluetooth
chip (MT7925)")
[Test Case]
Initial hardware support. One should be able to find WiFi/BT interfaces up
available along with proposed kernels.
[Where problems could occur]
Features for MT7925 are not all available at this moment, and expect more
fixes
for every corner case.
[Other Info]
MT7925 is supported since v6.7, and we need it for oem-6.5 as well. Nominate
for Jammy and Noble.
== original bug report ==
* WiFi
- kernel:
https://lore.kernel.org/all/cover.1690863143.git.deren...@mediatek.com/
* ebe81e6b8659 wifi: mt76: connac: add more unified event IDs
* 3c1199134874 wifi: mt76: connac: add more unified command IDs
* 473f26fb167e wifi: mt76: connac: add data field in struct tlv
* 975cd4d6d547 wifi: mt76: connac: add eht support for tx power
* e9eac4eb1bbd wifi: mt76: connac: add eht support for phy mode config
* d3d7f57e5c1c wifi: mt76: connac: export functions for mt7925
* 69f94b9fab06 wifi: mt76: mt792x: support mt7925 chip init
* 525209262f9c wifi: mt76: connac: introduce helper for mt7925 chipset
- firmware:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=4de2d71b322b9289a9851b9e1ef8c29ebf01071a
* Bluetooth
- kernel:
https://github.com/torvalds/linux/commit/4c92ae75ea7d41b6bafe10ee6f4c12ec12624786
- firmware:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=b83108216200dfece891ddc52bcde2e2860f5dc2
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2043542/+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 2048991] Re: upstream Intel VSC firmware paths moved to intel/vsc/
verified linux-firmware/jammy-proposed version
20220329.git681281e4-0ubuntu3.25.
** Tags added: verification-done-jammy
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2048991
Title:
upstream Intel VSC firmware paths moved to intel/vsc/
Status in linux-firmware package in Ubuntu:
Confirmed
Status in linux-firmware source package in Jammy:
Fix Committed
Status in linux-firmware source package in Noble:
Confirmed
Bug description:
[SRU Justification]
[Impact]
In upstream commit 5370a431 ("mei: vsc: Rework firmware image names") for
char-misc-next targeting v6.8, the VSC firmware paths have been changed to
intel/vsc instead of the original vsc/soc_a1_prod that has been used for all
existing Intel IPU6 camera platforms.
[Fix]
Upstream linux-firmware commit cfc997c6 ("intel: vsc: Add firmware for Visual
Sensing Controller").
In order to keep backward compatibility for Jammy oem/hwe kernels, an
additional
patch adds symlinks for each moved binary.
[Test Case]
The binaries are bit-to-bit identical, except for the destination path
installed. With extra symlinks created, all the IPU6 platforms should keep
working as usual.
[Where problems could occur]
No problem is expected.
[Other Info]
We're switching to upstreamed binaries in Jammy and Noble, because they're
likely to receive furhter updates for both linux-firmware and vsc drivers.
== original bug report ==
In upstream commit
https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-
misc.git/commit/?h=char-misc-
next=5370a431ef915b52697d25a5a32cbaf9a4cbef95 for char-misc-next
targeting v6.8, the VSC firmware paths have been changed to intel/vsc
instead of the original vsc/soc_a1_prod that has been used for all
existing Intel IPU6 camera platforms.
The corresponding linux-firmware commit is in
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
firmware.git/commit/?id=cfc997c664f076c6800b749ed7ef315b1e8e76fd.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2048991/+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 2048747] Re: Dell dock station WD22TB4 loses ether dev after reboot/power off
verified linux-firmware/jammy-proposed version
20220329.git681281e4-0ubuntu3.25, and linux-firmware/lunar-proposed
version 20230323.gitbcdcfbcf-0ubuntu1.10.
** Tags added: verification-done-jammy verification-done-lunar
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2048747
Title:
Dell dock station WD22TB4 loses ether dev after reboot/power off
Status in HWE Next:
New
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-firmware source package in Jammy:
Fix Committed
Status in linux-firmware source package in Lunar:
Fix Committed
Status in linux-firmware source package in Mantic:
Fix Released
Status in linux-firmware source package in Noble:
Fix Released
Bug description:
[SRU Justification]
[Impact]
Dell dock station WD22TB4 loses ether dev after reboot/power off.
[Fix]
Upstream firmware update commit e88bdbe4b5a9 ("rtl_nic: update firmware of USB
devices").
[Test Case]
1. Connect WD22TB4 with ethernet cable
2. Boot into OS
3. power off (or just reboot)
4. power on and check if ethernet connection is still available.
[Where problems could occur]
Opaque firmware update. No known issue found yet after the update.
[Other Info]
The proposed fix has been included in Mantic and Noble, so nominate only for
Lunar and Jammy (for oem-6.5).
== original bug report ==
[Steps to reproduce]
1. Connect WD22TB4 with ethernet
2. Boot into OS
3. poweroff (or just reboot)
4. poweron
[Fix]
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=e88bdbe4b5a98370e30f8b6cbbfebf09cd604b4d
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2048747/+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 2048901] Re: Update the NVIDIA ERD 535 series to 535.154.05
This bug was fixed in the package fabric-manager-535 - 535.154.05-0ubuntu1 --- fabric-manager-535 (535.154.05-0ubuntu1) noble; urgency=medium * New upstream release (LP: #2048901) * Make orig tarballs reproducible -- Dimitri John Ledkov Wed, 10 Jan 2024 16:39:27 + ** Changed in: fabric-manager-535 (Ubuntu Noble) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-535 in Ubuntu. https://bugs.launchpad.net/bugs/2048901 Title: Update the NVIDIA ERD 535 series to 535.154.05 Status in fabric-manager-535 package in Ubuntu: Fix Released Status in libnvidia-nscq-535 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-535 package in Ubuntu: New Status in nvidia-graphics-drivers-535-server package in Ubuntu: New Status in fabric-manager-535 source package in Bionic: New Status in libnvidia-nscq-535 source package in Bionic: New Status in nvidia-graphics-drivers-535 source package in Bionic: New Status in nvidia-graphics-drivers-535-server source package in Bionic: New Status in fabric-manager-535 source package in Focal: New Status in libnvidia-nscq-535 source package in Focal: New Status in nvidia-graphics-drivers-535 source package in Focal: New Status in nvidia-graphics-drivers-535-server source package in Focal: New Status in fabric-manager-535 source package in Jammy: New Status in libnvidia-nscq-535 source package in Jammy: New Status in nvidia-graphics-drivers-535 source package in Jammy: New Status in nvidia-graphics-drivers-535-server source package in Jammy: New Status in fabric-manager-535 source package in Mantic: New Status in libnvidia-nscq-535 source package in Mantic: New Status in nvidia-graphics-drivers-535 source package in Mantic: New Status in nvidia-graphics-drivers-535-server source package in Mantic: New Status in fabric-manager-535 source package in Noble: Fix Released Status in libnvidia-nscq-535 source package in Noble: Fix Released Status in nvidia-graphics-drivers-535 source package in Noble: New Status in nvidia-graphics-drivers-535-server source package in Noble: New Bug description: [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fabric-manager-535/+bug/2048901/+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 2048901] Re: Update the NVIDIA ERD 535 series to 535.154.05
This bug was fixed in the package libnvidia-nscq-535 - 535.154.05-0ubuntu1 --- libnvidia-nscq-535 (535.154.05-0ubuntu1) noble; urgency=medium * New upstream release (LP: #2048901) * Make orig tarballs reproducible -- Dimitri John Ledkov Thu, 11 Jan 2024 12:22:41 + ** Changed in: libnvidia-nscq-535 (Ubuntu Noble) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-535 in Ubuntu. https://bugs.launchpad.net/bugs/2048901 Title: Update the NVIDIA ERD 535 series to 535.154.05 Status in fabric-manager-535 package in Ubuntu: New Status in libnvidia-nscq-535 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-535 package in Ubuntu: New Status in nvidia-graphics-drivers-535-server package in Ubuntu: New Status in fabric-manager-535 source package in Bionic: New Status in libnvidia-nscq-535 source package in Bionic: New Status in nvidia-graphics-drivers-535 source package in Bionic: New Status in nvidia-graphics-drivers-535-server source package in Bionic: New Status in fabric-manager-535 source package in Focal: New Status in libnvidia-nscq-535 source package in Focal: New Status in nvidia-graphics-drivers-535 source package in Focal: New Status in nvidia-graphics-drivers-535-server source package in Focal: New Status in fabric-manager-535 source package in Jammy: New Status in libnvidia-nscq-535 source package in Jammy: New Status in nvidia-graphics-drivers-535 source package in Jammy: New Status in nvidia-graphics-drivers-535-server source package in Jammy: New Status in fabric-manager-535 source package in Mantic: New Status in libnvidia-nscq-535 source package in Mantic: New Status in nvidia-graphics-drivers-535 source package in Mantic: New Status in nvidia-graphics-drivers-535-server source package in Mantic: New Status in fabric-manager-535 source package in Noble: New Status in libnvidia-nscq-535 source package in Noble: Fix Released Status in nvidia-graphics-drivers-535 source package in Noble: New Status in nvidia-graphics-drivers-535-server source package in Noble: New Bug description: [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fabric-manager-535/+bug/2048901/+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 2049548] [NEW] package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: подпроцесс из пакета nvidia-dkms-390 установлен сценарий post-installation возвратил к
Public bug reported: package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: подпроцесс из пакета nvidia-dkms-390 установлен сценарий post-installation возвратил код ошибки 10 ProblemType: Package DistroRelease: Ubuntu 22.04 Package: nvidia-dkms-390 390.157-0ubuntu0.22.04.2 ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Jan 17 01:43:33 2024 ErrorMessage: подпроцесс из пакета nvidia-dkms-390 установлен сценарий post-installation возвратил код ошибки 10 InstallationDate: Installed on 2024-01-16 (0 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.11 SourcePackage: nvidia-graphics-drivers-390 Title: package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: подпроцесс из пакета nvidia-dkms-390 установлен сценарий post-installation возвратил код ошибки 10 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/2049548 Title: package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: подпроцесс из пакета nvidia-dkms-390 установлен сценарий post-installation возвратил код ошибки 10 Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: подпроцесс из пакета nvidia-dkms-390 установлен сценарий post-installation возвратил код ошибки 10 ProblemType: Package DistroRelease: Ubuntu 22.04 Package: nvidia-dkms-390 390.157-0ubuntu0.22.04.2 ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Jan 17 01:43:33 2024 ErrorMessage: подпроцесс из пакета nvidia-dkms-390 установлен сценарий post-installation возвратил код ошибки 10 InstallationDate: Installed on 2024-01-16 (0 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.11 SourcePackage: nvidia-graphics-drivers-390 Title: package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: подпроцесс из пакета nvidia-dkms-390 установлен сценарий post-installation возвратил код ошибки 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2049548/+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 2000947] Re: UVC Quanta 0408:4035 camera PROBLEM
@Bevz
I tested again the script with the new code from github and it works
For what I can see from your consolle output:
- there is a "file not found" error (Error 127), so that no driver is compiled
nor installed
- make is NOT running in your home directory but in the root (/) directory,
("make: Leaving directory '/usr/src/linux-headers-6.5.0-14-generic'") and
this also explain previous error
please check better where and how you are running the script
BR
Giuliano
--
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/2000947
Title:
UVC Quanta 0408:4035 camera PROBLEM
Status in linux package in Ubuntu:
Confirmed
Bug description:
I bought a Acer Nitro 5 AN517-55 with Quanta ACER HD User Facing',
USB 0408:4035.
The camera is reported to have problems by many users:
https://linux-hardware.org/?id=usb:0408-4035
The uvc camera Quanta 0408:4035 does not work with ubuntu 22,04. the camera
is “recongized” but fails installation.
My console commands report similar info to other users:
https://unix.stackexchange.com/questions/723504/integrated-camera-not-detected-working-on-acer-nitro-5-an515-58
PROPOSED SOLUTION
I got in contact with laurent.pinch...@ideasonboard.com and with
riba...@chromium.org , and subscribed to https://www.linuxtv.org/lists. And
me...@vger.kernel.org mailinglist.
Laurent proposed me a fix and I modified the 5,15 uvc_driver.c
version, and loaded it on github
https://github.com/Giuliano69/uvc_driver-for-Quanta-HD-User-
Facing-0x0408-0x4035-/blob/main/uvc_driver.c
I offered to test the fix, so I tried to compile the module with the
new source.
COMPILING PROBLEMS
I’m running **Ubuntu 22.04.1 LTS, with kernel
giuliano@Astra2A:/usr/src$ cat /proc/version_signature
Ubuntu 5.15.0-56.62-generic 5.15.64
BUT the linux-source that I found installed seems to be different
tgiuliano@Astra2A:/usr/src$ ls -al linux-so*
lrwxrwxrwx 1 root root 47 nov 22 16:08 linux-source-5.15.0.tar.bz2 ->
linux-source-5.15.0/linux-source-5.15.0.tar.bz2
I expanded the tar file, configured the IDE and compiled without error any
errors…
I manually copied the uvcvideo.ko in
/lib/modules/5.15.0-56-
sudo cp…...
then tryed to intall the new uvcvideo.ko module
sudo rmmod uvcvideo && sudo modprobe uvcvideo
BUT… IT FAILS
giuliano@Astra2A:~$ sudo rmmod uvcvideo && sudo modprobe uvcvideo
modprobe: ERROR: could not insert 'uvcvideo': Exec format error
and dmesg shows
[25961.151982] usbcore: registered new interface driver uvcvideo
[26323.125534] usbcore: deregistering interface driver uvcvideo
[26323.189294] uvcvideo: disagrees about version of symbol module_layout
These are the TWO modinfo from the old and new uvcvideo modules
https://pastebin.com/tSj8Exm6
Basically
OLD module: vermagic: 5.15.0-56-generic SMP mod_unload modversions
NEW module: vermagic: 5.15.64 SMP mod_unload modversions
-kindly ASK
HOW can FORCE the uvcdriver.c to match mi kernel version ?
Have I got OTHER ways to make the kernel module I’m compiling, match my
running system ?
I would like to test the module so to confirm the patch and let it
enter the kernel main stream...
BR
Giuliano
PS
btw…. to allow Eclipse to compile the kernel, I had to pass this commands
scripts/config --disable CONFIG_SYSTEM_REVOCATION_KEYS
scripts/config --disable SYSTEM_REVOCATION_KEYS
scripts/config --disable SYSTEM_TRUSTED_KEYS
hope that this does not affect the module layout & checking
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: giuliano 2142 F pulseaudio
/dev/snd/pcmC1D0p: giuliano 2142 F...m pulseaudio
/dev/snd/controlC0: giuliano 2142 F pulseaudio
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2022-11-03 (66 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64
(20220809.1)
MachineType: Acer Nitro AN517-55
NonfreeKernelModules: nvidia_modeset nvidia
Package: linux (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=it_IT.UTF-8
SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-57-generic
root=UUID=f07e25f9-07e7-4a29-a15e-f481aa0ee0f2 ro rootflags=subvol=@ quiet
splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.15.0-57.63-generic 5.15.74
RelatedPackageVersions:
linux-restricted-modules-5.15.0-57-generic N/A
linux-backports-modules-5.15.0-57-generic N/A
linux-firmware 20220329.git681281e4-0ubuntu3.9
Tags: jammy
Uname: Linux 5.15.0-57-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
[Kernel-packages] [Bug 2047658] Re: package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: podproces zainstalowany pakiet nvidia-dkms-390 skrypt post-installation zwrócił kod błęd
It looks that it is the problem with nvidia-390 driver is no longer compatible with linux 6+ kernel. At the moment when i start computer with linux 6.2.0-39 kernel nvidia-390 works fine, but with 6.5.0-14 nvidia-dmks-390 do not configure and so nvidia driver doesnt work. The initial module do not compile. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/2047658 Title: package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: podproces zainstalowany pakiet nvidia-dkms-390 skrypt post-installation zwrócił kod błędu 10 Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Bug description: I want to check if my nvidia is going well, so i use nvidia-smi and got error, then I processed to reinstall my nvidia drivers and got this error ProblemType: Package DistroRelease: Ubuntu 22.04 Package: nvidia-dkms-390 390.157-0ubuntu0.22.04.2 ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Dec 28 21:10:15 2023 ErrorMessage: podproces zainstalowany pakiet nvidia-dkms-390 skrypt post-installation zwrócił kod błędu 10 InstallationDate: Installed on 2022-09-13 (470 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Python3Details: /usr/local/bin/python3.10, Python 3.10.7, unpackaged PythonDetails: /usr/bin/python3.10, Python 3.10.12, python-is-python3, 3.9.2-2 RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.11 SourcePackage: nvidia-graphics-drivers-390 Title: package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: podproces zainstalowany pakiet nvidia-dkms-390 skrypt post-installation zwrócił kod błędu 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2047658/+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 2048935] Re: Right speaker broken on Dell XPS 13 Plus 9320
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-meta-hwe-6.5 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2048935 Title: Right speaker broken on Dell XPS 13 Plus 9320 Status in linux-meta-hwe-6.5 package in Ubuntu: Confirmed Bug description: After upgrading from the previous HWE kernel 6.2.0-39-generic to the new HWE kernel 6.5.0-14-generic, the right speaker no longer works. When booting back into the old HWE kernel, the right speaker functions again. The left speaker works in both cases. Hardware info: Dell XPS 13 Plus 9320 with Intel i7 1260P Software info: Description: Ubuntu 22.04.3 LTS Release: 22.04 Package info: apt-cache policy linux-generic-hwe-22.04 linux-generic-hwe-22.04: Installed: 6.5.0.14.14~22.04.7 Candidate: 6.5.0.14.14~22.04.7 Version table: *** 6.5.0.14.14~22.04.7 500 500 http://nl.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 100 /var/lib/dpkg/status 5.15.0.25.27 500 500 http://nl.archive.ubuntu.com/ubuntu jammy/main amd64 Packages lspci output on kernel 6.5.0-14-generic: ``` 00:1f.3 Multimedia audio controller: Intel Corporation Alder Lake PCH-P High Definition Audio Controller (rev 01) Subsystem: Dell Device 0af3 Flags: bus master, fast devsel, latency 64, IRQ 201, IOMMU group 15 Memory at 603e1d (64-bit, non-prefetchable) [size=16K] Memory at 603e00 (64-bit, non-prefetchable) [size=1M] Capabilities: [50] Power Management version 3 Capabilities: [80] Vendor Specific Information: Len=14 Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+ Kernel driver in use: sof-audio-pci-intel-tgl Kernel modules: snd_hda_intel, snd_sof_pci_intel_tgl 00:1f.4 SMBus: Intel Corporation Alder Lake PCH-P SMBus Host Controller (rev 01) Subsystem: Dell Device 0af3 Flags: medium devsel, IRQ 16, IOMMU group 15 Memory at 603e1dc000 (64-bit, non-prefetchable) [size=256] I/O ports at efa0 [size=32] ``` aplay -l output on kernel 6.5.0-14-generic: ``` List of PLAYBACK Hardware Devices card 0: sofsoundwire [sof-soundwire], device 2: Speaker (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: sofsoundwire [sof-soundwire], device 5: HDMI 1 (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: sofsoundwire [sof-soundwire], device 6: HDMI 2 (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: sofsoundwire [sof-soundwire], device 7: HDMI 3 (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 ``` ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-generic-hwe-22.04 6.5.0.14.14~22.04.7 ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Jan 10 21:40:02 2024 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85 InstallationDate: Installed on 2022-06-25 (563 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 SourcePackage: linux-meta-hwe-6.5 UpgradeStatus: Upgraded to jammy on 2022-08-15 (513 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-6.5/+bug/2048935/+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 1954924] Re: Kernel 5.4 - general protection fault SMP NOPTI
we're seeing this exact issue on our Dell R6525 servers running the latest patch level of focal, kernel is 5.4.0-169-generic. -- 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/1954924 Title: Kernel 5.4 - general protection fault SMP NOPTI Status in linux package in Ubuntu: Confirmed Bug description: Setup is comprised of multiple compute nodes in an OpenStack setup, all nodes being connected to a SAN storage through FC. Env specs: Ubuntu-Server 20.04.3 LTS Kernel: 5.4.0-89-generic CPU: AMD EPYC 7H12 At random times we observe the nodes getting locked up, system load is increasing and no actions can be taken, leading to having to reboot the server to recover. There is no pattern in this and stress testing the servers does not reproduce this. Log snippet: [1673239.174269] general protection fault: [#1] SMP NOPTI [1673239.183446] CPU: 97 PID: 1224718 Comm: cadvisor Not tainted 5.4.0-89-generic #100-Ubuntu [1673239.192622] Hardware name: Dell Inc. PowerEdge R7525/0590KW, BIOS 2.3.6 07/06/2021 [1673239.203336] RIP: 0010:string_nocheck+0x38/0x60 [1673239.212811] Code: 66 85 c0 74 3e 83 e8 01 4c 8d 5c 07 01 31 c0 eb 19 49 39 fa 76 03 44 88 07 48 83 c7 01 41 8d 71 01 48 83 c0 01 4c 39 df 74 0f <44> 0f b6 04 02 41 89 c1 89 c6 45 84 c0 75 d8 4c 89 d2 e8 11 ff ff [1673239.232904] RSP: 0018:a25f3199fba0 EFLAGS: 00010046 [1673239.244331] RAX: RBX: a25f3199fc58 RCX: 0a00ff04 [1673239.256551] RDX: d969688991a5a25c RSI: 8de32b56 RDI: 8de32b5400c6 [1673239.269226] RBP: a25f3199fba0 R08: 9c445a00 R09: 000a [1673239.279111] R10: 8de32b56 R11: 8de42b5400c5 R12: 8de32b56 [1673239.289855] R13: d969688991a5a25c R14: 0a00ff04 R15: 8de32b5400c6 [1673239.299447] FS: 7f925a7fc700() GS:8df87f44() knlGS: [1673239.308670] CS: 0010 DS: ES: CR0: 80050033 [1673239.317988] CR2: 7f9012efcfb8 CR3: 007fa1abe000 CR4: 00340ee0 [1673239.327377] Call Trace: [1673239.337796] string+0x4a/0x60 [1673239.347948] vsnprintf+0x26f/0x4e0 [1673239.356909] seq_vprintf+0x35/0x50 [1673239.365819] seq_printf+0x53/0x70 [1673239.374919] __blkg_prfill_rwstat+0x5d/0xb0 [1673239.383362] blkg_prfill_rwstat_field+0x97/0xc0 [1673239.391580] blkcg_print_blkgs+0xba/0xf0 [1673239.399891] ? blkg_prfill_rwstat+0xc0/0xc0 [1673239.408266] blkg_print_stat_bytes+0x45/0x50 [1673239.416378] cgroup_seqfile_show+0x56/0xc0 [1673239.424336] kernfs_seq_show+0x27/0x30 [1673239.432208] seq_read+0xdc/0x490 [1673239.440065] kernfs_fop_read+0x35/0x1b0 [1673239.448107] __vfs_read+0x1b/0x40 [1673239.456329] vfs_read+0xab/0x160 [1673239.465529] ksys_read+0x67/0xe0 [1673239.473872] __x64_sys_read+0x1a/0x20 [1673239.481269] do_syscall_64+0x57/0x190 [1673239.488798] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [1673239.497445] RIP: 0033:0x4cc910 [1673239.504694] Code: 8b 7c 24 10 48 8b 74 24 18 48 8b 54 24 20 49 c7 c2 00 00 00 00 49 c7 c0 00 00 00 00 49 c7 c1 00 00 00 00 48 8b 44 24 08 0f 05 <48> 3d 01 f0 ff ff 76 20 48 c7 44 24 28 ff ff ff ff 48 c7 44 24 30 [1673239.519380] RSP: 002b:00c01dd1e7a0 EFLAGS: 0202 ORIG_RAX: [1673239.526527] RAX: ffda RBX: 00c46f00 RCX: 004cc910 [1673239.534890] RDX: 1000 RSI: 00c00c2cd000 RDI: 000e [1673239.542958] RBP: 00c01dd1e7f0 R08: R09: [1673239.549915] R10: R11: 0202 R12: [1673239.558350] R13: 0002 R14: 0001 R15: 0002 [1673239.565178] Modules linked in: veth vhost_net nf_conntrack_netlink vhost tap dm_queue_length cls_u32 sch_cbq xsk_diag udp_diag raw_diag unix_diag af_packet_diag tcp_diag inet_diag netlink_diag ebtable_filter ebtables sch_ingress geneve ip6_udp_tunnel udp_tunnel nfnetlink_cttimeout nfnetlink aufs overlay rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache bonding ip6t_REJECT nf_reject_ipv6 ip6table_filter ip6_tables ipt_REJECT nf_reject_ipv4 xt_tcpudp xt_comment xt_state xt_conntrack iptable_filter bpfilter nls_iso8859_1 scsi_dh_rdac scsi_dh_emc scsi_dh_alua ipmi_ssif amd64_edac_mod edac_mce_amd dell_smbios kvm_amd dcdbas kvm wmi_bmof dell_wmi_descriptor ccp k10temp ipmi_si ipmi_devintf ipmi_msghandler acpi_power_meter mac_hid sch_fq_codel tcp_bbr openvswitch nsh nf_conncount nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 msr dm_multipath br_netfilter bridge stp llc sunrpc ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy asyn c_pq [1673239.565265] async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear mlx5_ib lpfc drm_vram_helper
[Kernel-packages] [Bug 2049536] Re: apply nvidia-tegra patches 2024 Jan 1-15
** Also 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/2049536 Title: apply nvidia-tegra patches 2024 Jan 1-15 Status in linux-nvidia-tegra package in Ubuntu: New Status in linux-nvidia-tegra-igx package in Ubuntu: New Bug description: Apply patches to linux-nvidia-tegra (for use in both linux-nvidia- tegra and linux-nvida-tegra-igx). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra/+bug/2049536/+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 2048735] Re: Disable keyboard wakeup for Framework 13
It's a pretty complicated backport to 6.1. there is a directory rename, missing quirks that this builds on. Considering 6.1 OEM will transition to 6.5 OEM eventually it might be better to only target to 6.5 OEM. They patches were nominated to 6.6.y already, but 6.5.y is EOL upstream so it's up to kernel team to manually do backport instead of cherry pick from stable tree. -- 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/2048735 Title: Disable keyboard wakeup for Framework 13 Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: New Status in linux-oem-6.5 source package in Jammy: New Status in linux source package in Noble: Fix Released Status in linux-oem-6.1 source package in Noble: Invalid Status in linux-oem-6.5 source package in Noble: Invalid Bug description: Framework 13" AMD version has an unexpected behavior that EC triggers a keyboard wakeup event every time the system exits s0i3. This EC keyboard wakeup event is to workaround a different bug. Because of this, the following series is sent to mailing list to disable wakeup from keyboard when on latest BIOS for Framework 13 AMD. https://lore.kernel.org/platform-driver-x86/20231212045006.97581-1-mario.limoncie...@amd.com/T/#mca26ce4d4358b188fc61e8b32c27d62410780c5a 85980669a863 platform/x86/amd/pmc: Move platform defines to header 2d53c0ab61e6 platform/x86/amd/pmc: Only run IRQ1 firmware version check on Cezanne b614a4bd73ef platform/x86/amd/pmc: Move keyboard wakeup disablement detection to pmc-quirks a55bdad5dfd1 platform/x86/amd/pmc: Disable keyboard wakeup on AMD Framework 13 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2048735/+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 2047658] Re: package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: podproces zainstalowany pakiet nvidia-dkms-390 skrypt post-installation zwrócił kod błęd
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/2047658 Title: package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: podproces zainstalowany pakiet nvidia-dkms-390 skrypt post-installation zwrócił kod błędu 10 Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Bug description: I want to check if my nvidia is going well, so i use nvidia-smi and got error, then I processed to reinstall my nvidia drivers and got this error ProblemType: Package DistroRelease: Ubuntu 22.04 Package: nvidia-dkms-390 390.157-0ubuntu0.22.04.2 ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Dec 28 21:10:15 2023 ErrorMessage: podproces zainstalowany pakiet nvidia-dkms-390 skrypt post-installation zwrócił kod błędu 10 InstallationDate: Installed on 2022-09-13 (470 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Python3Details: /usr/local/bin/python3.10, Python 3.10.7, unpackaged PythonDetails: /usr/bin/python3.10, Python 3.10.12, python-is-python3, 3.9.2-2 RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.11 SourcePackage: nvidia-graphics-drivers-390 Title: package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: podproces zainstalowany pakiet nvidia-dkms-390 skrypt post-installation zwrócił kod błędu 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2047658/+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 2049220] Re: Update firmware for MT7921 in order to fix Framework 13 AMD 7040
For the Framework 13 (using MT7921 WiFi), we'd like to see this to be with linux-oem-6.1 (Ubuntu) and/or linux-oem-6.5 (Ubuntu) as this is our official path for 22.04.3 LTS. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2049220 Title: Update firmware for MT7921 in order to fix Framework 13 AMD 7040 Status in linux-firmware package in Ubuntu: In Progress Status in linux-firmware source package in Jammy: In Progress Status in linux-firmware source package in Mantic: In Progress Status in linux-firmware source package in Noble: In Progress Bug description: The current firmware for MT7921 WiFi is giving me problems like dropping multicast packets (mDNS). I manually updated the firmware files and that fixed the issue. To be more specific, please include this commit: https://gitlab.com/kernel-firmware/linux-firmware/-/commit/0a18a7292a66532633d9586521f0b954c68a9fbc And possibly also this: https://gitlab.com/kernel-firmware/linux-firmware/-/commit/1366b827c21351b37665303397e161dd4158316e Thanks! We also need: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Ubuntu 22.04.3 LTS 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center ii linux-firmware 20220329.git681281e4-0ubuntu3.24 all Firmware for Linux kernel drivers 3) What you expected to happen WiFi working 4) What happened instead Multicast packets dropped, mDNS not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2049220/+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 2049536] [NEW] apply nvidia-tegra patches 2024 Jan 1-15
Public bug reported: Apply patches to linux-nvidia-tegra (for use in both linux-nvidia-tegra and linux-nvida-tegra-igx). ** Affects: linux-nvidia-tegra-igx (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-igx in Ubuntu. https://bugs.launchpad.net/bugs/2049536 Title: apply nvidia-tegra patches 2024 Jan 1-15 Status in linux-nvidia-tegra-igx package in Ubuntu: New Bug description: Apply patches to linux-nvidia-tegra (for use in both linux-nvidia- tegra and linux-nvida-tegra-igx). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra-igx/+bug/2049536/+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 1983153] Re: cpu timer UAF
** Information type changed from Private Security to Public Security -- 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/1983153 Title: cpu timer UAF Status in linux package in Ubuntu: New Bug description: [Impact] When exec'ing from a non-leader thread, armed CPU timers will not be removed from the armed list, leading to potential use-after-free. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1983153/+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 1983154] Re: nft allows references to objects on different tables
** Information type changed from Private Security to Public Security -- 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/1983154 Title: nft allows references to objects on different tables Status in linux package in Ubuntu: New Bug description: [Impact] When adding objects/sets/elements on the same nftables netlink batch, there can be cross-table references. When a table is deleted, references to freed objects may be left, leading to use-after-free vulnerabilities. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1983154/+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 1851592] Re: SMT warning not printed to kernel logs
It needs to be reproduced on more recent kernels. ** Information type changed from Private Security to Public Security ** Changed in: linux (Ubuntu) Assignee: Tyler Hicks (tyhicks) => (unassigned) -- 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/1851592 Title: SMT warning not printed to kernel logs Status in linux package in Ubuntu: Triaged Bug description: The TAA SMT warning log message is not emitted, as intended, when SMT is enabled on Cascade Lake and newer CPUs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851592/+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 2049352] Re: Package BlueZ 5.72 for Noble
** Changed in: bluez (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2049352 Title: Package BlueZ 5.72 for Noble Status in bluez package in Ubuntu: Fix Committed Bug description: ver 5.72: Fix issue with BAP and handling stream IO linking. Fix issue with BAP and setup of multiple streams per endpoint. Fix issue with AVDTP and potential incorrect transaction label. Fix issue with A2DP and handling crash on suspend. Fix issue with GATT database and an invalid pointer. Add support for AICS service. https://mirrors.edge.kernel.org/pub/linux/bluetooth/bluez-5.72.tar.xz https://git.kernel.org/pub/scm/bluetooth/bluez.git/tag/?h=5.72 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2049352/+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 2049530] [NEW] apply nvidia-tegra patches for Jan 16
Public bug reported: Additional patches for nvidia-tegra kernel. ** Affects: linux-nvidia-tegra (Ubuntu) Importance: Undecided Status: New ** Package changed: linux-nvidia-tegra-igx (Ubuntu) => linux-nvidia- tegra (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-tegra-igx in Ubuntu. https://bugs.launchpad.net/bugs/2049530 Title: apply nvidia-tegra patches for Jan 16 Status in linux-nvidia-tegra package in Ubuntu: New Bug description: Additional patches for nvidia-tegra kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra/+bug/2049530/+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 2039167] Re: I get this message "array-index-out-of-bounds" every time I turn on my laptop since I upgraded from 23.04. to 23.10. (drivers/gpu/drm/amd/amdgpu/../pm/powerplay/hwm
Happens to me on the latest LTS:
6.5.0-14-generic #14~22.04.1-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/2039167
Title:
I get this message "array-index-out-of-bounds" every time I turn on
my laptop since I upgraded from 23.04. to 23.10.
(drivers/gpu/drm/amd/amdgpu/../pm/powerplay/hwmgr/processpptables.c)
Status in linux package in Ubuntu:
Confirmed
Bug description:
UBSAN: array-index-out-of-bounds in
/build/linux-D15vQj/linux-6.5.0/drivers/gpu/drm/amd/amdgpu/../pm/powerplay/hwmgr/processpptables.c:929:40
index 1 is out of range for type 'UCHAR [1]'
My firmware version is X515DAP.311.
OS type 64-bit.
GNOME version 45.0.
Kernel version Linux 6.5.0-9-generic.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-9-generic 6.5.0-9.9
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: zoran 2329 F wireplumber
/dev/snd/controlC0: zoran 2329 F wireplumber
/dev/snd/seq:zoran 2316 F pipewire
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 12 13:42:16 2023
InstallationDate: Installed on 2023-09-21 (21 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64
(20230807.2)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9-generic
root=UUID=9b0c8205-22d2-4c7e-8e53-959a91e2174d ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-6.5.0-9-generic N/A
linux-backports-modules-6.5.0-9-generic N/A
linux-firmware 20230919.git3672ccab-0ubuntu2.1
SourcePackage: linux
UpgradeStatus: Upgraded to mantic on 2023-10-12 (0 days ago)
dmi.bios.date: 01/06/2023
dmi.bios.release: 5.14
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X515DAP.311
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X515DAP
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrX515DAP.311:bd01/06/2023:br5.14:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX515DAP_M515DA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX515DAP:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
dmi.product.family: ASUSLaptop
dmi.product.name: VivoBook_ASUSLaptop X515DAP_M515DA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039167/+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 2049352] Re: Package BlueZ 5.72 for Noble
This was missing a build dependency on python3-pygments (which is in Main), I added it. Testing well with my Beats Flex, YouTube Music with the Firefox Nightly snap. I can adjust the latency offset with no issue, and blueman DTRT with connecting and disconnecting. Popped open journalctl and syslog, no errors presented on either front. As usual, here are the Lintian flags raised (that I don't plan on blocking on, but you should at least be aware of.) Regardless, great work, thank you! W: bluez source: illegal-runtime-test-name bluez_response [debian/tests/control:1] W: bluez: maintainer-script-should-not-use-dpkg-maintscript-helper "dpkg-maintscript-helper" [postinst:11] W: bluez: maintainer-script-should-not-use-dpkg-maintscript-helper "dpkg-maintscript-helper" [postinst:14] W: bluez: maintainer-script-should-not-use-dpkg-maintscript-helper "dpkg-maintscript-helper" [postinst:21] W: bluez: maintainer-script-should-not-use-dpkg-maintscript-helper "dpkg-maintscript-helper" [postinst:25] W: bluez: maintainer-script-should-not-use-dpkg-maintscript-helper "dpkg-maintscript-helper" [postinst:28] W: bluez: maintainer-script-should-not-use-dpkg-maintscript-helper "dpkg-maintscript-helper" [postinst:31] W: bluez: maintainer-script-should-not-use-dpkg-maintscript-helper "dpkg-maintscript-helper" [postinst:5] W: bluez: maintainer-script-should-not-use-dpkg-maintscript-helper "dpkg-maintscript-helper" [preinst:16] W: bluez: maintainer-script-should-not-use-dpkg-maintscript-helper "dpkg-maintscript-helper" [preinst:22] W: bluez: maintainer-script-should-not-use-dpkg-maintscript-helper "dpkg-maintscript-helper" [preinst:25] W: bluez: maintainer-script-should-not-use-dpkg-maintscript-helper "dpkg-maintscript-helper" [preinst:32] W: bluez: maintainer-script-should-not-use-dpkg-maintscript-helper "dpkg-maintscript-helper" [preinst:39] W: bluez: maintainer-script-should-not-use-dpkg-maintscript-helper "dpkg-maintscript-helper" [preinst:43] W: bluez: maintainer-script-should-not-use-dpkg-maintscript-helper "dpkg-maintscript-helper" [preinst:46] W: bluez: maintainer-script-should-not-use-dpkg-maintscript-helper "dpkg-maintscript-helper" [preinst:49] W: bluez-test-tools: no-manual-page [usr/bin/hfp] W: bluez-test-tools: no-manual-page [usr/bin/ioctl-tester] W: bluez-test-tools: no-manual-page [usr/bin/iso-tester] W: bluez-test-tools: no-manual-page [usr/bin/mesh-tester] W: bluez source: superfluous-file-pattern obexd/plugins/messages-tracker.c [debian/copyright:632] W: bluez source: superfluous-file-pattern obexd/plugins/syncevolution.c [debian/copyright:511] W: bluez: systemd-service-file-refers-to-unusual-wantedby-target bluetooth.target [usr/lib/systemd/system/bluetooth.service] W: bluez-meshd: systemd-service-file-refers-to-unusual-wantedby-target bluetooth.target [usr/lib/systemd/system/bluetooth-mesh.service] W: bluez: unusual-interpreter /usr/bin/python [usr/share/apport/package-hooks/source_bluez.py] I: bluez source: adopted-extended-field (in section for source) XSBC-Original-Maintainer [debian/control:3]
[Kernel-packages] [Bug 2048977] Please test proposed package
Hello You-Sheng, or anyone else affected,
Accepted linux-firmware into jammy-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/20220329.git681281e4-0ubuntu3.25 in a few hours, and then in
the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
jammy to verification-done-jammy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-jammy. In either case, without details of your testing we will
not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2048977
Title:
WCN6856 Wi-FI Unavailable and no function during suspend stress
Status in HWE Next:
New
Status in linux-firmware package in Ubuntu:
In Progress
Status in linux-firmware source package in Jammy:
Fix Committed
Status in linux-firmware source package in Lunar:
Fix Committed
Status in linux-firmware source package in Mantic:
Fix Committed
Status in linux-firmware source package in Noble:
In Progress
Bug description:
[SRU Justification]
[Impact]
Due to a known silicon limitation, the following sequence is needed while
initialing the PCIE device on a certain devices with ASMedia chipset involved:
1. 'hot reset' assert
2. 2nd PCIe reset' assert
3. Asmedia 'hot reset' deassert
4. PT21 GPIO13 2nd PCIe reset' deassert.
In certain caes, the WIFI link training failed while system resumes from
suspend.
[Fix]
Upstream commits:
* 17509e53b97b ("ath11k: WCN6855 hw2.0: update to
WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.36")
* 324cc56975d7 ("ath11k: WCN6855 hw2.0: update board-2.bin")
And Jammy takes an additional commit d1dc30480fef ("ath11k: WCN6855 hw2.0:
update board-2.bin") to forfill git history dependency.
And while we pulled a firmware fix from github.com/kvalo/ath11k-firmware in
bug 2042534, it fails to clean cherry-pick of commit 17509e53b97b. Since Noble
has not yet accept the PR for bug 2042534, it has no such problem at this
moment.
[Test Case]
This can be reproduced with suspend/resume stress test.
$ checkbox-cli run com.canonical.certification::stress-
suspend-30-cycles-with-reboots-automated
[Where problems could occur]
Opaque firmware update. No known issue found yet after the update.
[Other Info]
This affects all series with WCN6855/WCN6856 support, Noble/Mantic/Lunar and
Jammy for oem-6.5 included.
== original bug report ==
Due to a known silicon limitation, the following sequence is needed
while initialing the PCIE device on a certain devices with ASMedia
chipset involved:
1. 'hot reset' assert
2. 2nd PCIe reset' assert
3. Asmedia 'hot reset' deassert
4. PT21 GPIO13 2nd PCIe reset' deassert.
In certain caes, the WIFI link training failed while system resumes
from suspend.
This can be reproduced with suspend/resume stress test.
$ checkbox-cli run com.canonical.certification::stress-
suspend-30-cycles-with-reboots-automated
The proposed fixes are:
*
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=17509e53b97baaefeb287b98d3358da8a6e1c199
- This FW include this LP ticket issue fix
*
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=324cc56975d7b5a375259a49667c24f2f5a4c8fe
- The FW is to support new China regulatory support.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2048977/+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 2048977] Re: WCN6856 Wi-FI Unavailable and no function during suspend stress
Hello You-Sheng, or anyone else affected,
Accepted linux-firmware into lunar-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/20230323.gitbcdcfbcf-0ubuntu1.10 in a few hours, and then in
the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
lunar to verification-done-lunar. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-lunar. In either case, without details of your testing we will
not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
** Changed in: linux-firmware (Ubuntu Lunar)
Status: In Progress => Fix Committed
** Changed in: linux-firmware (Ubuntu Jammy)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2048977
Title:
WCN6856 Wi-FI Unavailable and no function during suspend stress
Status in HWE Next:
New
Status in linux-firmware package in Ubuntu:
In Progress
Status in linux-firmware source package in Jammy:
Fix Committed
Status in linux-firmware source package in Lunar:
Fix Committed
Status in linux-firmware source package in Mantic:
Fix Committed
Status in linux-firmware source package in Noble:
In Progress
Bug description:
[SRU Justification]
[Impact]
Due to a known silicon limitation, the following sequence is needed while
initialing the PCIE device on a certain devices with ASMedia chipset involved:
1. 'hot reset' assert
2. 2nd PCIe reset' assert
3. Asmedia 'hot reset' deassert
4. PT21 GPIO13 2nd PCIe reset' deassert.
In certain caes, the WIFI link training failed while system resumes from
suspend.
[Fix]
Upstream commits:
* 17509e53b97b ("ath11k: WCN6855 hw2.0: update to
WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.36")
* 324cc56975d7 ("ath11k: WCN6855 hw2.0: update board-2.bin")
And Jammy takes an additional commit d1dc30480fef ("ath11k: WCN6855 hw2.0:
update board-2.bin") to forfill git history dependency.
And while we pulled a firmware fix from github.com/kvalo/ath11k-firmware in
bug 2042534, it fails to clean cherry-pick of commit 17509e53b97b. Since Noble
has not yet accept the PR for bug 2042534, it has no such problem at this
moment.
[Test Case]
This can be reproduced with suspend/resume stress test.
$ checkbox-cli run com.canonical.certification::stress-
suspend-30-cycles-with-reboots-automated
[Where problems could occur]
Opaque firmware update. No known issue found yet after the update.
[Other Info]
This affects all series with WCN6855/WCN6856 support, Noble/Mantic/Lunar and
Jammy for oem-6.5 included.
== original bug report ==
Due to a known silicon limitation, the following sequence is needed
while initialing the PCIE device on a certain devices with ASMedia
chipset involved:
1. 'hot reset' assert
2. 2nd PCIe reset' assert
3. Asmedia 'hot reset' deassert
4. PT21 GPIO13 2nd PCIe reset' deassert.
In certain caes, the WIFI link training failed while system resumes
from suspend.
This can be reproduced with suspend/resume stress test.
$ checkbox-cli run com.canonical.certification::stress-
suspend-30-cycles-with-reboots-automated
The proposed fixes are:
*
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=17509e53b97baaefeb287b98d3358da8a6e1c199
- This FW include this LP ticket issue fix
*
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=324cc56975d7b5a375259a49667c24f2f5a4c8fe
- The FW is to support new China regulatory support.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2048977/+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 2048853] Please test proposed package
Hello You-Sheng, or anyone else affected,
Accepted linux-firmware into jammy-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/20220329.git681281e4-0ubuntu3.25 in a few hours, and then in
the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
jammy to verification-done-jammy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-jammy. In either case, without details of your testing we will
not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2048853
Title:
occasional wifi firmware loading failures: wiwlwifi: BE200: Failed to
start RT ucode: -110
Status in HWE Next:
New
Status in linux-firmware package in Ubuntu:
Triaged
Status in linux-firmware source package in Jammy:
Fix Committed
Status in linux-firmware source package in Mantic:
Fix Committed
Status in linux-firmware source package in Noble:
Triaged
Bug description:
[SRU Justification]
[Impact]
Within stress reboot tests, iwlwifi may fail to load firmware, triggers
retries,
and finally makes wifi operative.
iwlwifi :05:00.0: Loaded firmware version: 83.d24e06ed.0
gl-c0-fm-c0-83.ucode
iwlwifi :05:00.0: 0x0071 | NMI_INTERRUPT_UMAC_FATAL
iwlwifi :05:00.0: 0x02F0 | trm_hw_status0
iwlwifi :05:00.0: 0x | trm_hw_status1
iwlwifi :05:00.0: 0x002C27F2 | branchlink2
iwlwifi :05:00.0: 0x002B79AE | interruptlink1
..
iwlwifi :05:00.0: UMAC CURRENT PC: 0x8026934e
iwlwifi :05:00.0: LMAC1 CURRENT PC: 0xd0
iwlwifi :05:00.0: LMAC2 CURRENT PC: 0xd0
iwlwifi :05:00.0: UMAC CURRENT PC 1: 0x8026934c
iwlwifi :05:00.0: TCM1 CURRENT PC: 0xd0
iwlwifi :05:00.0: RCM1 CURRENT PC: 0xd0
iwlwifi :05:00.0: RCM2 CURRENT PC: 0xd0
iwlwifi :05:00.0: Function Scratch status:
iwlwifi :05:00.0: 0x01010101 | Func Scratch
iwlwifi :05:00.0: Failed to start RT ucode: -110
iwlwifi :05:00.0: WRT: Collecting data: ini trigger 13 fired
(delay=0ms).
[Fix]
Resolved in upstream commit 318c64abfb33 ("iwlwifi: update gl FW for
core80-165
release").
While the iwlwifi firmware updates come with a sequential manner, it pulls a
few
more:
* 765492b8b ("iwlwifi: add new FWs from core81-65 release"), already in Mantic
* a07fd0b96 ("iwlwifi: add new FWs from core83-55 release")
* f27dec616 ("iwlwifi: fix for the new FWs from core83-55 release")
These contain firmware blob for ucore 84/86, and are not used by
kernels < v6.7.
[Test Case]
Use checkbox reboot stress test case to observe iwlwifi dmesg logs:
$ checkbox-cli run com.canonical.certification::stress/reboot
[Where problems could occur]
Opaque firmware update. No known issue found yet after the update.
[Other Info]
This affects series with kernels that load iwlwifi ucode 83 firmware, namely
Noble, Mantic, and for oem-6.5, Jammy.
== original bug report ==
Within stress reboot tests, iwlwifi may fail to load firmware and
triggers retry, and finally makes wifi operative.
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: Loaded firmware version:
83.d24e06ed.0 gl-c0-fm-c0-83.ucode
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: 0x0071 |
NMI_INTERRUPT_UMAC_FATAL
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: 0x02F0 |
trm_hw_status0
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: 0x |
trm_hw_status1
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: 0x002C27F2 | branchlink2
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: 0x002B79AE |
interruptlink1
..
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: UMAC CURRENT PC:
0x8026934e
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: LMAC1 CURRENT PC: 0xd0
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: LMAC2 CURRENT PC: 0xd0
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: UMAC CURRENT PC 1:
0x8026934c
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: TCM1 CURRENT PC: 0xd0
Oct 12
[Kernel-packages] [Bug 2048991] Please test proposed package
Hello You-Sheng, or anyone else affected,
Accepted linux-firmware into jammy-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/20220329.git681281e4-0ubuntu3.25 in a few hours, and then in
the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
jammy to verification-done-jammy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-jammy. In either case, without details of your testing we will
not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2048991
Title:
upstream Intel VSC firmware paths moved to intel/vsc/
Status in linux-firmware package in Ubuntu:
Confirmed
Status in linux-firmware source package in Jammy:
Fix Committed
Status in linux-firmware source package in Noble:
Confirmed
Bug description:
[SRU Justification]
[Impact]
In upstream commit 5370a431 ("mei: vsc: Rework firmware image names") for
char-misc-next targeting v6.8, the VSC firmware paths have been changed to
intel/vsc instead of the original vsc/soc_a1_prod that has been used for all
existing Intel IPU6 camera platforms.
[Fix]
Upstream linux-firmware commit cfc997c6 ("intel: vsc: Add firmware for Visual
Sensing Controller").
In order to keep backward compatibility for Jammy oem/hwe kernels, an
additional
patch adds symlinks for each moved binary.
[Test Case]
The binaries are bit-to-bit identical, except for the destination path
installed. With extra symlinks created, all the IPU6 platforms should keep
working as usual.
[Where problems could occur]
No problem is expected.
[Other Info]
We're switching to upstreamed binaries in Jammy and Noble, because they're
likely to receive furhter updates for both linux-firmware and vsc drivers.
== original bug report ==
In upstream commit
https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-
misc.git/commit/?h=char-misc-
next=5370a431ef915b52697d25a5a32cbaf9a4cbef95 for char-misc-next
targeting v6.8, the VSC firmware paths have been changed to intel/vsc
instead of the original vsc/soc_a1_prod that has been used for all
existing Intel IPU6 camera platforms.
The corresponding linux-firmware commit is in
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
firmware.git/commit/?id=cfc997c664f076c6800b749ed7ef315b1e8e76fd.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2048991/+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 2000947] Re: UVC Quanta 0408:4035 camera PROBLEM
Hi @Giuliano Will be good If you could help me. I have Acer with Quanta 4033 camera Previously I used your script and camera worked. But yesterday I got update from 6.2 kernel to 6.5 and now it is not working. I saw that you create new commit today but still not working. Error the same as in #123 Here is error linux-hwe-6.5-6.5.0/ubuntu/include/README linux-hwe-6.5-6.5.0/ubuntu/ubuntu-host/Kconfig linux-hwe-6.5-6.5.0/ubuntu/ubuntu-host/Makefile linux-hwe-6.5-6.5.0/ubuntu/ubuntu-host/ubuntu-host.c linux-hwe-6.5-6.5.0/update-dkms-versions linux-hwe-6.5-6.5.0/virt/kvm/vfio.c --2024-01-16 18:34:02-- https://raw.githubusercontent.com/Giuliano69/uvc_driver-for-Quanta-HD-User-Facing-0x0408-0x4035-/main/uvc_driver.c Resolving raw.githubusercontent.com (raw.githubusercontent.com)... 185.199.109.133, 185.199.108.133, 185.199.111.133, ... Connecting to raw.githubusercontent.com (raw.githubusercontent.com)|185.199.109.133|:443... connected. HTTP request sent, awaiting response... 200 OK Length: 89121 (87K) [text/plain] Saving to: ‘uvc_driver.c’ uvc_driver.c 100%[>] 87,03K 538KB/sin 0,2s 2024-01-16 18:34:02 (538 KB/s) - ‘uvc_driver.c’ saved [89121/89121] make: Entering directory '/usr/src/linux-headers-6.5.0-14-generic' warning: the compiler differs from the one used to build the kernel The kernel was built by: x86_64-linux-gnu-gcc-12 (Ubuntu 12.3.0-1ubuntu1~22.04) 12.3.0 You are using: CC [M] /home/vasyl/linux-hwe-6.5-6.5.0/drivers/media/usb/uvc/uvc_driver.o /bin/sh: 1: gcc-12: not found make[2]: *** [scripts/Makefile.build:251: /home/vasyl/linux-hwe-6.5-6.5.0/drivers/media/usb/uvc/uvc_driver.o] Error 127 make[2]: *** Waiting for unfinished jobs make[1]: *** [/usr/src/linux-headers-6.5.0-14-generic/Makefile:2037: /home/vasyl/linux-hwe-6.5-6.5.0/drivers/media/usb/uvc] Error 2 make: *** [Makefile:234: __sub-make] Error 2 make: Leaving directory '/usr/src/linux-headers-6.5.0-14-generic' cp: cannot stat 'uvcvideo.ko': No such file or directory rmmod: ERROR: Module uvcvideo is not currently loaded 1. I removed all directories in home, which starts from "linux" 2. I removed add documents and archives in home, which starts from "linux" 3. I put your script into home and launch it. (Tested with sudo and without) Could you help me or tell what to check? -- 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/2000947 Title: UVC Quanta 0408:4035 camera PROBLEM Status in linux package in Ubuntu: Confirmed Bug description: I bought a Acer Nitro 5 AN517-55 with Quanta ACER HD User Facing', USB 0408:4035. The camera is reported to have problems by many users: https://linux-hardware.org/?id=usb:0408-4035 The uvc camera Quanta 0408:4035 does not work with ubuntu 22,04. the camera is “recongized” but fails installation. My console commands report similar info to other users: https://unix.stackexchange.com/questions/723504/integrated-camera-not-detected-working-on-acer-nitro-5-an515-58 PROPOSED SOLUTION I got in contact with laurent.pinch...@ideasonboard.com and with riba...@chromium.org , and subscribed to https://www.linuxtv.org/lists. And me...@vger.kernel.org mailinglist. Laurent proposed me a fix and I modified the 5,15 uvc_driver.c version, and loaded it on github https://github.com/Giuliano69/uvc_driver-for-Quanta-HD-User- Facing-0x0408-0x4035-/blob/main/uvc_driver.c I offered to test the fix, so I tried to compile the module with the new source. COMPILING PROBLEMS I’m running **Ubuntu 22.04.1 LTS, with kernel giuliano@Astra2A:/usr/src$ cat /proc/version_signature Ubuntu 5.15.0-56.62-generic 5.15.64 BUT the linux-source that I found installed seems to be different tgiuliano@Astra2A:/usr/src$ ls -al linux-so* lrwxrwxrwx 1 root root 47 nov 22 16:08 linux-source-5.15.0.tar.bz2 -> linux-source-5.15.0/linux-source-5.15.0.tar.bz2 I expanded the tar file, configured the IDE and compiled without error any errors… I manually copied the uvcvideo.ko in /lib/modules/5.15.0-56- sudo cp…... then tryed to intall the new uvcvideo.ko module sudo rmmod uvcvideo && sudo modprobe uvcvideo BUT… IT FAILS giuliano@Astra2A:~$ sudo rmmod uvcvideo && sudo modprobe uvcvideo modprobe: ERROR: could not insert 'uvcvideo': Exec format error and dmesg shows [25961.151982] usbcore: registered new interface driver uvcvideo [26323.125534] usbcore: deregistering interface driver uvcvideo [26323.189294] uvcvideo: disagrees about version of symbol module_layout These are the TWO modinfo from the
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-gcp/5.4.0.1122.124)
All autopkgtests for the newly accepted linux-meta-gcp (5.4.0.1122.124) for focal have finished running. The following regressions have been reported in tests triggered by the package: r8168/8.048.00-1ubuntu0.20.04.2 (amd64) systemd/245.4-4ubuntu3.22 (arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-meta-gcp [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packaging resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+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 2043542] Please test proposed package
Hello You-Sheng, or anyone else affected,
Accepted linux-firmware into jammy-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/20220329.git681281e4-0ubuntu3.25 in a few hours, and then in
the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
jammy to verification-done-jammy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-jammy. In either case, without details of your testing we will
not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2043542
Title:
Support Mediatek MT7925 WiFi/BT
Status in HWE Next:
New
Status in linux package in Ubuntu:
Fix Released
Status in linux-firmware package in Ubuntu:
In Progress
Status in linux-oem-6.5 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Invalid
Status in linux-firmware source package in Jammy:
Fix Committed
Status in linux-oem-6.5 source package in Jammy:
In Progress
Status in linux source package in Noble:
Fix Released
Status in linux-firmware source package in Noble:
In Progress
Status in linux-oem-6.5 source package in Noble:
Invalid
Bug description:
[kernel SRU Justification]
[Impact]
Mediatek MT7925 WiFi/Bluetooth not supported yet.
[Fix]
For WiFi, there are tons of patches to be backported from upstream
kernel v6.7 due to a massive refactoring was done to integrate
multiple mt79xx drivers into one before landing support for mt7925.
While these changes, mostly clean cherry-picks, are tied to each
other, and separating them may cause more efforts in the future, a
huge patchset of total number 144 is proposed.
For Bluetooth, upstream commit 4c92ae75ea7d ("Bluetooth: btusb: Add
support Mediatek MT7925") is required.
[Test Case]
Initial hardware support. One should be able to find WiFi/BT
interfaces up available along with proposed kernels.
[Where problems could occur]
Features for MT7925 are not all available at this moment, and expect
more fixes for every corner case.
[Other Info]
MT7925 is supported since v6.7, and we need it for oem-6.5 as well.
Nominate for Jammy and Noble.
[linux-firmware SRU Justification]
[Impact]
Missing firmware for Mediatek MT7925 WiFi/BT.
[Fix]
Upstream firmware commits:
- WiFi: 4de2d71b322b ("linux-firmware: add firmware for MT7925")
- Bluetooth: b83108216200 ("linux-firmware: add firmware for mediatek
bluetooth
chip (MT7925)")
[Test Case]
Initial hardware support. One should be able to find WiFi/BT interfaces up
available along with proposed kernels.
[Where problems could occur]
Features for MT7925 are not all available at this moment, and expect more
fixes
for every corner case.
[Other Info]
MT7925 is supported since v6.7, and we need it for oem-6.5 as well. Nominate
for Jammy and Noble.
== original bug report ==
* WiFi
- kernel:
https://lore.kernel.org/all/cover.1690863143.git.deren...@mediatek.com/
* ebe81e6b8659 wifi: mt76: connac: add more unified event IDs
* 3c1199134874 wifi: mt76: connac: add more unified command IDs
* 473f26fb167e wifi: mt76: connac: add data field in struct tlv
* 975cd4d6d547 wifi: mt76: connac: add eht support for tx power
* e9eac4eb1bbd wifi: mt76: connac: add eht support for phy mode config
* d3d7f57e5c1c wifi: mt76: connac: export functions for mt7925
* 69f94b9fab06 wifi: mt76: mt792x: support mt7925 chip init
* 525209262f9c wifi: mt76: connac: introduce helper for mt7925 chipset
- firmware:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=4de2d71b322b9289a9851b9e1ef8c29ebf01071a
* Bluetooth
- kernel:
https://github.com/torvalds/linux/commit/4c92ae75ea7d41b6bafe10ee6f4c12ec12624786
- firmware:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=b83108216200dfece891ddc52bcde2e2860f5dc2
To manage notifications about this
[Kernel-packages] [Bug 2048747] Please test proposed package
Hello You-Sheng, or anyone else affected,
Accepted linux-firmware into jammy-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/20220329.git681281e4-0ubuntu3.25 in a few hours, and then in
the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
jammy to verification-done-jammy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-jammy. In either case, without details of your testing we will
not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2048747
Title:
Dell dock station WD22TB4 loses ether dev after reboot/power off
Status in HWE Next:
New
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-firmware source package in Jammy:
Fix Committed
Status in linux-firmware source package in Lunar:
Fix Committed
Status in linux-firmware source package in Mantic:
Fix Released
Status in linux-firmware source package in Noble:
Fix Released
Bug description:
[SRU Justification]
[Impact]
Dell dock station WD22TB4 loses ether dev after reboot/power off.
[Fix]
Upstream firmware update commit e88bdbe4b5a9 ("rtl_nic: update firmware of USB
devices").
[Test Case]
1. Connect WD22TB4 with ethernet cable
2. Boot into OS
3. power off (or just reboot)
4. power on and check if ethernet connection is still available.
[Where problems could occur]
Opaque firmware update. No known issue found yet after the update.
[Other Info]
The proposed fix has been included in Mantic and Noble, so nominate only for
Lunar and Jammy (for oem-6.5).
== original bug report ==
[Steps to reproduce]
1. Connect WD22TB4 with ethernet
2. Boot into OS
3. poweroff (or just reboot)
4. poweron
[Fix]
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=e88bdbe4b5a98370e30f8b6cbbfebf09cd604b4d
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2048747/+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 2048747] Please test proposed package
Hello You-Sheng, or anyone else affected,
Accepted linux-firmware into lunar-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/20230323.gitbcdcfbcf-0ubuntu1.10 in a few hours, and then in
the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
lunar to verification-done-lunar. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-lunar. In either case, without details of your testing we will
not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2048747
Title:
Dell dock station WD22TB4 loses ether dev after reboot/power off
Status in HWE Next:
New
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-firmware source package in Jammy:
Fix Committed
Status in linux-firmware source package in Lunar:
Fix Committed
Status in linux-firmware source package in Mantic:
Fix Released
Status in linux-firmware source package in Noble:
Fix Released
Bug description:
[SRU Justification]
[Impact]
Dell dock station WD22TB4 loses ether dev after reboot/power off.
[Fix]
Upstream firmware update commit e88bdbe4b5a9 ("rtl_nic: update firmware of USB
devices").
[Test Case]
1. Connect WD22TB4 with ethernet cable
2. Boot into OS
3. power off (or just reboot)
4. power on and check if ethernet connection is still available.
[Where problems could occur]
Opaque firmware update. No known issue found yet after the update.
[Other Info]
The proposed fix has been included in Mantic and Noble, so nominate only for
Lunar and Jammy (for oem-6.5).
== original bug report ==
[Steps to reproduce]
1. Connect WD22TB4 with ethernet
2. Boot into OS
3. poweroff (or just reboot)
4. poweron
[Fix]
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=e88bdbe4b5a98370e30f8b6cbbfebf09cd604b4d
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2048747/+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 2048977] Re: WCN6856 Wi-FI Unavailable and no function during suspend stress
Hello You-Sheng, or anyone else affected,
Accepted linux-firmware into mantic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/20230919.git3672ccab-0ubuntu2.6 in a few hours, and then in the
-proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
mantic to verification-done-mantic. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-mantic. In either case, without details of your testing we will
not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
** Changed in: linux-firmware (Ubuntu Mantic)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2048977
Title:
WCN6856 Wi-FI Unavailable and no function during suspend stress
Status in HWE Next:
New
Status in linux-firmware package in Ubuntu:
In Progress
Status in linux-firmware source package in Jammy:
In Progress
Status in linux-firmware source package in Lunar:
In Progress
Status in linux-firmware source package in Mantic:
Fix Committed
Status in linux-firmware source package in Noble:
In Progress
Bug description:
[SRU Justification]
[Impact]
Due to a known silicon limitation, the following sequence is needed while
initialing the PCIE device on a certain devices with ASMedia chipset involved:
1. 'hot reset' assert
2. 2nd PCIe reset' assert
3. Asmedia 'hot reset' deassert
4. PT21 GPIO13 2nd PCIe reset' deassert.
In certain caes, the WIFI link training failed while system resumes from
suspend.
[Fix]
Upstream commits:
* 17509e53b97b ("ath11k: WCN6855 hw2.0: update to
WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.36")
* 324cc56975d7 ("ath11k: WCN6855 hw2.0: update board-2.bin")
And Jammy takes an additional commit d1dc30480fef ("ath11k: WCN6855 hw2.0:
update board-2.bin") to forfill git history dependency.
And while we pulled a firmware fix from github.com/kvalo/ath11k-firmware in
bug 2042534, it fails to clean cherry-pick of commit 17509e53b97b. Since Noble
has not yet accept the PR for bug 2042534, it has no such problem at this
moment.
[Test Case]
This can be reproduced with suspend/resume stress test.
$ checkbox-cli run com.canonical.certification::stress-
suspend-30-cycles-with-reboots-automated
[Where problems could occur]
Opaque firmware update. No known issue found yet after the update.
[Other Info]
This affects all series with WCN6855/WCN6856 support, Noble/Mantic/Lunar and
Jammy for oem-6.5 included.
== original bug report ==
Due to a known silicon limitation, the following sequence is needed
while initialing the PCIE device on a certain devices with ASMedia
chipset involved:
1. 'hot reset' assert
2. 2nd PCIe reset' assert
3. Asmedia 'hot reset' deassert
4. PT21 GPIO13 2nd PCIe reset' deassert.
In certain caes, the WIFI link training failed while system resumes
from suspend.
This can be reproduced with suspend/resume stress test.
$ checkbox-cli run com.canonical.certification::stress-
suspend-30-cycles-with-reboots-automated
The proposed fixes are:
*
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=17509e53b97baaefeb287b98d3358da8a6e1c199
- This FW include this LP ticket issue fix
*
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=324cc56975d7b5a375259a49667c24f2f5a4c8fe
- The FW is to support new China regulatory support.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2048977/+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 2048853] Please test proposed package
Hello You-Sheng, or anyone else affected,
Accepted linux-firmware into mantic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/20230919.git3672ccab-0ubuntu2.6 in a few hours, and then in the
-proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
mantic to verification-done-mantic. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-mantic. In either case, without details of your testing we will
not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2048853
Title:
occasional wifi firmware loading failures: wiwlwifi: BE200: Failed to
start RT ucode: -110
Status in HWE Next:
New
Status in linux-firmware package in Ubuntu:
Triaged
Status in linux-firmware source package in Jammy:
Fix Committed
Status in linux-firmware source package in Mantic:
Fix Committed
Status in linux-firmware source package in Noble:
Triaged
Bug description:
[SRU Justification]
[Impact]
Within stress reboot tests, iwlwifi may fail to load firmware, triggers
retries,
and finally makes wifi operative.
iwlwifi :05:00.0: Loaded firmware version: 83.d24e06ed.0
gl-c0-fm-c0-83.ucode
iwlwifi :05:00.0: 0x0071 | NMI_INTERRUPT_UMAC_FATAL
iwlwifi :05:00.0: 0x02F0 | trm_hw_status0
iwlwifi :05:00.0: 0x | trm_hw_status1
iwlwifi :05:00.0: 0x002C27F2 | branchlink2
iwlwifi :05:00.0: 0x002B79AE | interruptlink1
..
iwlwifi :05:00.0: UMAC CURRENT PC: 0x8026934e
iwlwifi :05:00.0: LMAC1 CURRENT PC: 0xd0
iwlwifi :05:00.0: LMAC2 CURRENT PC: 0xd0
iwlwifi :05:00.0: UMAC CURRENT PC 1: 0x8026934c
iwlwifi :05:00.0: TCM1 CURRENT PC: 0xd0
iwlwifi :05:00.0: RCM1 CURRENT PC: 0xd0
iwlwifi :05:00.0: RCM2 CURRENT PC: 0xd0
iwlwifi :05:00.0: Function Scratch status:
iwlwifi :05:00.0: 0x01010101 | Func Scratch
iwlwifi :05:00.0: Failed to start RT ucode: -110
iwlwifi :05:00.0: WRT: Collecting data: ini trigger 13 fired
(delay=0ms).
[Fix]
Resolved in upstream commit 318c64abfb33 ("iwlwifi: update gl FW for
core80-165
release").
While the iwlwifi firmware updates come with a sequential manner, it pulls a
few
more:
* 765492b8b ("iwlwifi: add new FWs from core81-65 release"), already in Mantic
* a07fd0b96 ("iwlwifi: add new FWs from core83-55 release")
* f27dec616 ("iwlwifi: fix for the new FWs from core83-55 release")
These contain firmware blob for ucore 84/86, and are not used by
kernels < v6.7.
[Test Case]
Use checkbox reboot stress test case to observe iwlwifi dmesg logs:
$ checkbox-cli run com.canonical.certification::stress/reboot
[Where problems could occur]
Opaque firmware update. No known issue found yet after the update.
[Other Info]
This affects series with kernels that load iwlwifi ucode 83 firmware, namely
Noble, Mantic, and for oem-6.5, Jammy.
== original bug report ==
Within stress reboot tests, iwlwifi may fail to load firmware and
triggers retry, and finally makes wifi operative.
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: Loaded firmware version:
83.d24e06ed.0 gl-c0-fm-c0-83.ucode
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: 0x0071 |
NMI_INTERRUPT_UMAC_FATAL
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: 0x02F0 |
trm_hw_status0
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: 0x |
trm_hw_status1
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: 0x002C27F2 | branchlink2
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: 0x002B79AE |
interruptlink1
..
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: UMAC CURRENT PC:
0x8026934e
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: LMAC1 CURRENT PC: 0xd0
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: LMAC2 CURRENT PC: 0xd0
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: UMAC CURRENT PC 1:
0x8026934c
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: TCM1 CURRENT PC: 0xd0
Oct 12
[Kernel-packages] [Bug 2049519] [NEW] crashes on boot leading to blank screen
Public bug reported: driver bug while update ProblemType: Package DistroRelease: Ubuntu 22.04 Package: nvidia-dkms-390 390.157-0ubuntu0.22.04.2 ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 AptOrdering: nvidia-kernel-source-390:amd64: Install nvidia-kernel-common-390:amd64: Install nvidia-dkms-390:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Jan 10 21:00:05 2024 ErrorMessage: »installiertes nvidia-dkms-390-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 10 zurück InstallationDate: Installed on 2023-04-21 (263 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.11 SourcePackage: nvidia-graphics-drivers-390 Title: package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: »installiertes nvidia-dkms-390-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 10 zurück UpgradeStatus: No upgrade log present (probably fresh install) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nvidia-dkms-390 (not installed) ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Jan 16 16:01:38 2024 InstallationDate: Installed on 2021-12-03 (773 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: nvidia-graphics-drivers-390 UpgradeStatus: Upgraded to jammy on 2024-01-11 (5 days ago) ** Affects: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/2049519 Title: crashes on boot leading to blank screen Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: driver bug while update ProblemType: Package DistroRelease: Ubuntu 22.04 Package: nvidia-dkms-390 390.157-0ubuntu0.22.04.2 ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 AptOrdering: nvidia-kernel-source-390:amd64: Install nvidia-kernel-common-390:amd64: Install nvidia-dkms-390:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Jan 10 21:00:05 2024 ErrorMessage: »installiertes nvidia-dkms-390-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 10 zurück InstallationDate: Installed on 2023-04-21 (263 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.11 SourcePackage: nvidia-graphics-drivers-390 Title: package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: »installiertes nvidia-dkms-390-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 10 zurück UpgradeStatus: No upgrade log present (probably fresh install) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nvidia-dkms-390 (not installed) ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Jan 16 16:01:38 2024 InstallationDate: Installed on 2021-12-03 (773 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: nvidia-graphics-drivers-390 UpgradeStatus: Upgraded to jammy on 2024-01-11 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2049519/+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 2043542] Re: Support Mediatek MT7925 WiFi/BT
** Changed in: linux-firmware (Ubuntu Jammy)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2043542
Title:
Support Mediatek MT7925 WiFi/BT
Status in HWE Next:
New
Status in linux package in Ubuntu:
Fix Released
Status in linux-firmware package in Ubuntu:
In Progress
Status in linux-oem-6.5 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Invalid
Status in linux-firmware source package in Jammy:
Fix Committed
Status in linux-oem-6.5 source package in Jammy:
In Progress
Status in linux source package in Noble:
Fix Released
Status in linux-firmware source package in Noble:
In Progress
Status in linux-oem-6.5 source package in Noble:
Invalid
Bug description:
[kernel SRU Justification]
[Impact]
Mediatek MT7925 WiFi/Bluetooth not supported yet.
[Fix]
For WiFi, there are tons of patches to be backported from upstream
kernel v6.7 due to a massive refactoring was done to integrate
multiple mt79xx drivers into one before landing support for mt7925.
While these changes, mostly clean cherry-picks, are tied to each
other, and separating them may cause more efforts in the future, a
huge patchset of total number 144 is proposed.
For Bluetooth, upstream commit 4c92ae75ea7d ("Bluetooth: btusb: Add
support Mediatek MT7925") is required.
[Test Case]
Initial hardware support. One should be able to find WiFi/BT
interfaces up available along with proposed kernels.
[Where problems could occur]
Features for MT7925 are not all available at this moment, and expect
more fixes for every corner case.
[Other Info]
MT7925 is supported since v6.7, and we need it for oem-6.5 as well.
Nominate for Jammy and Noble.
[linux-firmware SRU Justification]
[Impact]
Missing firmware for Mediatek MT7925 WiFi/BT.
[Fix]
Upstream firmware commits:
- WiFi: 4de2d71b322b ("linux-firmware: add firmware for MT7925")
- Bluetooth: b83108216200 ("linux-firmware: add firmware for mediatek
bluetooth
chip (MT7925)")
[Test Case]
Initial hardware support. One should be able to find WiFi/BT interfaces up
available along with proposed kernels.
[Where problems could occur]
Features for MT7925 are not all available at this moment, and expect more
fixes
for every corner case.
[Other Info]
MT7925 is supported since v6.7, and we need it for oem-6.5 as well. Nominate
for Jammy and Noble.
== original bug report ==
* WiFi
- kernel:
https://lore.kernel.org/all/cover.1690863143.git.deren...@mediatek.com/
* ebe81e6b8659 wifi: mt76: connac: add more unified event IDs
* 3c1199134874 wifi: mt76: connac: add more unified command IDs
* 473f26fb167e wifi: mt76: connac: add data field in struct tlv
* 975cd4d6d547 wifi: mt76: connac: add eht support for tx power
* e9eac4eb1bbd wifi: mt76: connac: add eht support for phy mode config
* d3d7f57e5c1c wifi: mt76: connac: export functions for mt7925
* 69f94b9fab06 wifi: mt76: mt792x: support mt7925 chip init
* 525209262f9c wifi: mt76: connac: introduce helper for mt7925 chipset
- firmware:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=4de2d71b322b9289a9851b9e1ef8c29ebf01071a
* Bluetooth
- kernel:
https://github.com/torvalds/linux/commit/4c92ae75ea7d41b6bafe10ee6f4c12ec12624786
- firmware:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=b83108216200dfece891ddc52bcde2e2860f5dc2
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2043542/+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 2049514] [NEW] sleeping laptop and moving between external monitors triggers screen flickering
Public bug reported: Note: this has been happening for many of the past kernel releases. Wasn't seeing this under Ubuntu-22.04 until around 6 months ago - but it's been triggering ever since (although not all the time) Basically I'll be docked at work on my Dell Latitude laptop, pull out the USB-C connector (which power/ethernet/HDMI runs through) and go home. Then plug into a similar dock at home. End result is the same whether it's work->home or home->work, the laptop un-sleeps, monitor comes back to life - but the screen is flickering, wayland seems to think the monitor is waay bigger than it is (eg fonts are big) and it's unusable. Once in this state, plugging/unplugging cables doesn't help - only a reboot fixes the problem. Then it all works again for several home<->work journey's - until it happens again. No real rhythm to it from what I can see - maybe once every couple of weeks? But definitely related to coming back from sleep-mode Googling around shows the same symptoms related to the kernel error i915 :00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun: transcoder Suggested fixes seems to mention it's related to cstate and a suggested fix is to edit /etc/default/grub with GRUB_CMDLINE_LINUX="i915.enable_psr=0 intel_idle.max_cstate=4" I'm going to give that a go to see if it helps ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-39-generic 6.2.0-39.40~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jan 17 04:03:13 2024 InstallationDate: Installed on 2022-03-13 (673 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-6.2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2049514 Title: sleeping laptop and moving between external monitors triggers screen flickering Status in linux-signed-hwe-6.2 package in Ubuntu: New Bug description: Note: this has been happening for many of the past kernel releases. Wasn't seeing this under Ubuntu-22.04 until around 6 months ago - but it's been triggering ever since (although not all the time) Basically I'll be docked at work on my Dell Latitude laptop, pull out the USB-C connector (which power/ethernet/HDMI runs through) and go home. Then plug into a similar dock at home. End result is the same whether it's work->home or home->work, the laptop un-sleeps, monitor comes back to life - but the screen is flickering, wayland seems to think the monitor is waay bigger than it is (eg fonts are big) and it's unusable. Once in this state, plugging/unplugging cables doesn't help - only a reboot fixes the problem. Then it all works again for several home<->work journey's - until it happens again. No real rhythm to it from what I can see - maybe once every couple of weeks? But definitely related to coming back from sleep-mode Googling around shows the same symptoms related to the kernel error i915 :00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun: transcoder Suggested fixes seems to mention it's related to cstate and a suggested fix is to edit /etc/default/grub with GRUB_CMDLINE_LINUX="i915.enable_psr=0 intel_idle.max_cstate=4" I'm going to give that a go to see if it helps ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-39-generic 6.2.0-39.40~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jan 17 04:03:13 2024 InstallationDate: Installed on 2022-03-13 (673 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2049514/+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 2048747] Re: Dell dock station WD22TB4 loses ether dev after reboot/power off
** Changed in: linux-firmware (Ubuntu Jammy)
Status: In Progress => Fix Committed
** Changed in: linux-firmware (Ubuntu Lunar)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2048747
Title:
Dell dock station WD22TB4 loses ether dev after reboot/power off
Status in HWE Next:
New
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-firmware source package in Jammy:
Fix Committed
Status in linux-firmware source package in Lunar:
Fix Committed
Status in linux-firmware source package in Mantic:
Fix Released
Status in linux-firmware source package in Noble:
Fix Released
Bug description:
[SRU Justification]
[Impact]
Dell dock station WD22TB4 loses ether dev after reboot/power off.
[Fix]
Upstream firmware update commit e88bdbe4b5a9 ("rtl_nic: update firmware of USB
devices").
[Test Case]
1. Connect WD22TB4 with ethernet cable
2. Boot into OS
3. power off (or just reboot)
4. power on and check if ethernet connection is still available.
[Where problems could occur]
Opaque firmware update. No known issue found yet after the update.
[Other Info]
The proposed fix has been included in Mantic and Noble, so nominate only for
Lunar and Jammy (for oem-6.5).
== original bug report ==
[Steps to reproduce]
1. Connect WD22TB4 with ethernet
2. Boot into OS
3. poweroff (or just reboot)
4. poweron
[Fix]
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=e88bdbe4b5a98370e30f8b6cbbfebf09cd604b4d
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2048747/+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 2048991] Re: upstream Intel VSC firmware paths moved to intel/vsc/
** Changed in: linux-firmware (Ubuntu Jammy)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2048991
Title:
upstream Intel VSC firmware paths moved to intel/vsc/
Status in linux-firmware package in Ubuntu:
Confirmed
Status in linux-firmware source package in Jammy:
Fix Committed
Status in linux-firmware source package in Noble:
Confirmed
Bug description:
[SRU Justification]
[Impact]
In upstream commit 5370a431 ("mei: vsc: Rework firmware image names") for
char-misc-next targeting v6.8, the VSC firmware paths have been changed to
intel/vsc instead of the original vsc/soc_a1_prod that has been used for all
existing Intel IPU6 camera platforms.
[Fix]
Upstream linux-firmware commit cfc997c6 ("intel: vsc: Add firmware for Visual
Sensing Controller").
In order to keep backward compatibility for Jammy oem/hwe kernels, an
additional
patch adds symlinks for each moved binary.
[Test Case]
The binaries are bit-to-bit identical, except for the destination path
installed. With extra symlinks created, all the IPU6 platforms should keep
working as usual.
[Where problems could occur]
No problem is expected.
[Other Info]
We're switching to upstreamed binaries in Jammy and Noble, because they're
likely to receive furhter updates for both linux-firmware and vsc drivers.
== original bug report ==
In upstream commit
https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-
misc.git/commit/?h=char-misc-
next=5370a431ef915b52697d25a5a32cbaf9a4cbef95 for char-misc-next
targeting v6.8, the VSC firmware paths have been changed to intel/vsc
instead of the original vsc/soc_a1_prod that has been used for all
existing Intel IPU6 camera platforms.
The corresponding linux-firmware commit is in
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
firmware.git/commit/?id=cfc997c664f076c6800b749ed7ef315b1e8e76fd.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2048991/+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 2048853] Re: occasional wifi firmware loading failures: wiwlwifi: BE200: Failed to start RT ucode: -110
** Changed in: linux-firmware (Ubuntu Jammy)
Status: In Progress => Fix Committed
** Changed in: linux-firmware (Ubuntu Mantic)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2048853
Title:
occasional wifi firmware loading failures: wiwlwifi: BE200: Failed to
start RT ucode: -110
Status in HWE Next:
New
Status in linux-firmware package in Ubuntu:
Triaged
Status in linux-firmware source package in Jammy:
Fix Committed
Status in linux-firmware source package in Mantic:
Fix Committed
Status in linux-firmware source package in Noble:
Triaged
Bug description:
[SRU Justification]
[Impact]
Within stress reboot tests, iwlwifi may fail to load firmware, triggers
retries,
and finally makes wifi operative.
iwlwifi :05:00.0: Loaded firmware version: 83.d24e06ed.0
gl-c0-fm-c0-83.ucode
iwlwifi :05:00.0: 0x0071 | NMI_INTERRUPT_UMAC_FATAL
iwlwifi :05:00.0: 0x02F0 | trm_hw_status0
iwlwifi :05:00.0: 0x | trm_hw_status1
iwlwifi :05:00.0: 0x002C27F2 | branchlink2
iwlwifi :05:00.0: 0x002B79AE | interruptlink1
..
iwlwifi :05:00.0: UMAC CURRENT PC: 0x8026934e
iwlwifi :05:00.0: LMAC1 CURRENT PC: 0xd0
iwlwifi :05:00.0: LMAC2 CURRENT PC: 0xd0
iwlwifi :05:00.0: UMAC CURRENT PC 1: 0x8026934c
iwlwifi :05:00.0: TCM1 CURRENT PC: 0xd0
iwlwifi :05:00.0: RCM1 CURRENT PC: 0xd0
iwlwifi :05:00.0: RCM2 CURRENT PC: 0xd0
iwlwifi :05:00.0: Function Scratch status:
iwlwifi :05:00.0: 0x01010101 | Func Scratch
iwlwifi :05:00.0: Failed to start RT ucode: -110
iwlwifi :05:00.0: WRT: Collecting data: ini trigger 13 fired
(delay=0ms).
[Fix]
Resolved in upstream commit 318c64abfb33 ("iwlwifi: update gl FW for
core80-165
release").
While the iwlwifi firmware updates come with a sequential manner, it pulls a
few
more:
* 765492b8b ("iwlwifi: add new FWs from core81-65 release"), already in Mantic
* a07fd0b96 ("iwlwifi: add new FWs from core83-55 release")
* f27dec616 ("iwlwifi: fix for the new FWs from core83-55 release")
These contain firmware blob for ucore 84/86, and are not used by
kernels < v6.7.
[Test Case]
Use checkbox reboot stress test case to observe iwlwifi dmesg logs:
$ checkbox-cli run com.canonical.certification::stress/reboot
[Where problems could occur]
Opaque firmware update. No known issue found yet after the update.
[Other Info]
This affects series with kernels that load iwlwifi ucode 83 firmware, namely
Noble, Mantic, and for oem-6.5, Jammy.
== original bug report ==
Within stress reboot tests, iwlwifi may fail to load firmware and
triggers retry, and finally makes wifi operative.
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: Loaded firmware version:
83.d24e06ed.0 gl-c0-fm-c0-83.ucode
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: 0x0071 |
NMI_INTERRUPT_UMAC_FATAL
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: 0x02F0 |
trm_hw_status0
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: 0x |
trm_hw_status1
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: 0x002C27F2 | branchlink2
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: 0x002B79AE |
interruptlink1
..
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: UMAC CURRENT PC:
0x8026934e
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: LMAC1 CURRENT PC: 0xd0
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: LMAC2 CURRENT PC: 0xd0
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: UMAC CURRENT PC 1:
0x8026934c
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: TCM1 CURRENT PC: 0xd0
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: RCM1 CURRENT PC: 0xd0
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: RCM2 CURRENT PC: 0xd0
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: Function Scratch status:
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: 0x01010101 | Func Scratch
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: Failed to start RT ucode:
-110
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: WRT: Collecting data: ini
trigger 13 fired (delay=0ms).
Test steps:
$ checkbox-cli run com.canonical.certification::stress/reboot
Proposed fix:
* https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/linux-
firmware.git/commit/?id=318c64abfb33c4211b002f5e5b4ff25cd19f712b
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2048853/+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 2045428] Re: AWS: Set ENA_INTR_INITIAL_TX_INTERVAL_USECS to 64
This bug is awaiting verification that the linux-aws/6.5.0-1013.13
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-mantic-linux-aws' to 'verification-done-mantic-
linux-aws'. If the problem still exists, change the tag 'verification-
needed-mantic-linux-aws' to 'verification-failed-mantic-linux-aws'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: kernel-spammed-mantic-linux-aws-v2
verification-needed-mantic-linux-aws
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/2045428
Title:
AWS: Set ENA_INTR_INITIAL_TX_INTERVAL_USECS to 64
Status in linux-aws package in Ubuntu:
Fix Committed
Status in linux-aws source package in Lunar:
Fix Committed
Status in linux-aws source package in Mantic:
Fix Committed
Status in linux-aws source package in Noble:
Fix Committed
Bug description:
SRU Justification
[Impact]
An update from LP: #1853180 was carried forward to the Lunar 6.2 and
Mantic 6.5 kernels. As it did not cause a conflict it likely escaped
notice when the Jammy AWS kernel was forward ported. Commit
05785adf6e570a068adf0502b61fe2b521d7f0ca ('net: ena: fix default tx
interrupt moderation interval') from v5.5 set
ENA_INTR_INITIAL_TX_INTERVAL_USECS to 64, but was then overwritten
during the forward port rebase by patch ('UBUNTU: SAUCE: net: ena: fix
too long default tx interrupt moderation interval'). Reverting this
patch will restore the AWS ENA driver to upstream default of 64.
[Test Plan]
AWS tested.
[Regression potential]
Network connections could exhibit adverse jitter times.
[Other info]
SF: #00372168
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2045428/+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 2039991] Re: UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.2-n2KLlt (drivers/gpu/drm/amd/amdgpu/../display/dc/irq/dce110/irq_service_dce110.c)
Ubuntu 22.04. 3 LTS I get the same error Jan 16 14:41:04 claus-VPCEC2S1E kernel: x86/cpu: VMX (outside TXT) disabled by BIOS Jan 16 14:41:32 claus-VPCEC2S1E kernel: Jan 16 14:41:32 claus-VPCEC2S1E kernel: UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.5-q7NZ0T/linux-hwe-6.5-6.5.0/drivers/ gpu/drm/radeon/radeon_atombios.c:2620:43 Jan 16 14:41:32 claus-VPCEC2S1E kernel: index 1 is out of range for type 'UCHAR [1]' -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2039991 Title: UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.2-n2KLlt (drivers/gpu/drm/amd/amdgpu/../display/dc/irq/dce110/irq_service_dce110.c) Status in linux package in Ubuntu: Incomplete Status in linux-hwe-6.2 package in Ubuntu: Confirmed Bug description: Everything works fine, this error shows up in the boot log. Description: Ubuntu 22.04.3 LTS Release: 22.04 Ubuntu 6.2.0-35.35~22.04.1-generic 6.2.16 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde PRO [Radeon HD 7750/8740 / R7 250E] driverInfo = Mesa 23.2.1 - kisak-mesa PPA (LLVM 15.0.7) oct 20 18:12:33 H-Linux kernel: oct 20 18:12:33 H-Linux kernel: UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.2-n2KLlt/linux-hwe-6.2-6.2.0/drivers/gpu/drm/amd/amdgpu/../display/dc/irq/dce110/irq_service_dce110.c:215:39 oct 20 18:12:33 H-Linux kernel: index 178 is out of range for type 'pipe_ctx [6]' oct 20 18:12:33 H-Linux kernel: CPU: 1 PID: 865 Comm: canonical-livep Not tainted 6.2.0-35-generic #35~22.04.1-Ubuntu oct 20 18:12:33 H-Linux kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./960GC-GS FX, BIOS P1.60 10/20/2014 oct 20 18:12:33 H-Linux kernel: Call Trace: oct 20 18:12:33 H-Linux kernel: oct 20 18:12:33 H-Linux kernel: dump_stack_lvl+0x48/0x70 oct 20 18:12:33 H-Linux kernel: dump_stack+0x10/0x20 oct 20 18:12:33 H-Linux kernel: __ubsan_handle_out_of_bounds+0xa2/0x100 oct 20 18:12:33 H-Linux kernel: dce110_vblank_set+0xc9/0xd0 [amdgpu] oct 20 18:12:33 H-Linux kernel: dal_irq_service_set+0x67/0x100 [amdgpu] oct 20 18:12:33 H-Linux kernel: dc_interrupt_set+0x24/0x40 [amdgpu] oct 20 18:12:33 H-Linux kernel: dm_set_vupdate_irq+0x38/0x90 [amdgpu] oct 20 18:12:33 H-Linux kernel: dm_set_vblank+0x173/0x1d0 [amdgpu] oct 20 18:12:33 H-Linux kernel: dm_disable_vblank+0x10/0x20 [amdgpu] oct 20 18:12:33 H-Linux kernel: drm_vblank_disable_and_save+0xfd/0x150 [drm] oct 20 18:12:33 H-Linux kernel: vblank_disable_fn+0x74/0xa0 [drm] oct 20 18:12:33 H-Linux kernel: ? __pfx_vblank_disable_fn+0x10/0x10 [drm] oct 20 18:12:33 H-Linux kernel: call_timer_fn+0x2c/0x160 oct 20 18:12:33 H-Linux kernel: ? __pfx_vblank_disable_fn+0x10/0x10 [drm] oct 20 18:12:33 H-Linux kernel: __run_timers.part.0+0x1fb/0x2b0 oct 20 18:12:33 H-Linux kernel: ? __pfx_tick_sched_timer+0x10/0x10 oct 20 18:12:33 H-Linux kernel: ? __pfx_native_apic_mem_write+0x10/0x10 oct 20 18:12:33 H-Linux kernel: ? lapic_next_event+0x20/0x30 oct 20 18:12:33 H-Linux kernel: ? clockevents_program_event+0xb5/0x140 oct 20 18:12:33 H-Linux kernel: run_timer_softirq+0x2a/0x60 oct 20 18:12:33 H-Linux kernel: __do_softirq+0xdd/0x330 oct 20 18:12:33 H-Linux kernel: ? hrtimer_interrupt+0x12b/0x250 oct 20 18:12:33 H-Linux kernel: __irq_exit_rcu+0xa2/0xd0 oct 20 18:12:33 H-Linux kernel: irq_exit_rcu+0xe/0x20 oct 20 18:12:33 H-Linux kernel: sysvec_apic_timer_interrupt+0x96/0xb0 oct 20 18:12:33 H-Linux kernel: oct 20 18:12:33 H-Linux kernel: oct 20 18:12:33 H-Linux kernel: asm_sysvec_apic_timer_interrupt+0x1b/0x20 oct 20 18:12:33 H-Linux kernel: RIP: 0010:lzma_literal+0x100/0x2a0 oct 20 18:12:33 H-Linux kernel: Code: ff 00 77 22 48 8b 73 18 4c 8b 53 10 c1 e1 08 c1 e2 08 89 0b 4c 8d 5e 01 4c 89 5b 18 41 0f b6 34 32 01 f2 89 53 04 45 0f b7 10 <89> ce 01 c0 c1 ee 0b 41 0f af f2 39 d6 77 9b> oct 20 18:12:33 H-Linux kernel: RSP: 0018:b21d4167f748 EFLAGS: 0216 oct 20 18:12:33 H-Linux kernel: RAX: 0001 RBX: 8e7f86cf8000 RCX: 09d930a8 oct 20 18:12:33 H-Linux kernel: RDX: 04455f07 RSI: 04455f07 RDI: 8e7f86cf8f0c oct 20 18:12:33 H-Linux kernel: RBP: b21d4167f770 R08: 8e7f86cf8f0e R09: 0800 oct 20 18:12:33 H-Linux kernel: R10: 071a R11: R12: oct 20 18:12:33 H-Linux kernel: R13: 0003 R14: 0001 R15: 0003 oct 20 18:12:33 H-Linux kernel: lzma_main+0x85/0x2b0 oct 20 18:12:33 H-Linux kernel: lzma2_lzma+0x1c0/0x3f0 oct 20 18:12:33 H-Linux kernel: xz_dec_lzma2_run+0x83/0x4e0 oct 20 18:12:33 H-Linux kernel:
[Kernel-packages] [Bug 2008157] Re: [SRU][Ubuntu 22.04.1]: Observed "Array Index out of bounds" Call Trace multiple times on Ubuntu 22.04.1 OS during boot
The bug is still present. I have checked on 22.04.3 (kernel 5.15.0-91) DELL PowerEdge R350 PERC H755 During boot, there are "array-index-out-of-bounds", "index -1 is out of range", and stack trace present. There is a part of dmesg output - https://pastebin.com/raw/Zfe19x12 Is it safe to use the server and store data with this issue present or is it better to wait for a fix? Thanks. -- 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/2008157 Title: [SRU][Ubuntu 22.04.1]: Observed "Array Index out of bounds" Call Trace multiple times on Ubuntu 22.04.1 OS during boot Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Committed Bug description: SRU Justification: [Impact] When booted into Ubuntu 22.04.1 OS after installation, observed "Array Index out of bounds" Call Trace multiple times in dmesg. Call Trace is as follow: [ 6.125704] UBSAN: array-index-out-of-bounds in /build/linux-JjvoxS/linux-5.15.0/drivers/scsi/megaraid/megaraid_sas_fp.c:103:32 [ 6.125705] index 1 is out of range for type 'MR_LD_SPAN_MAP [1]' [ 6.125707] CPU: 0 PID: 18 Comm: kworker/0:1 Not tainted 5.15.0-53-generic #59-Ubuntu [ 6.125709] Hardware name: Dell Inc. , BIOS 11/08/2022 [ 6.125710] Workqueue: events work_for_cpu_fn [ 6.125716] Call Trace: [ 6.125718] [ 6.125720] show_stack+0x52/0x5c [ 6.125725] dump_stack_lvl+0x4a/0x63 [ 6.125731] dump_stack+0x10/0x16 [ 6.125732] ubsan_epilogue+0x9/0x49 [ 6.125734] __ubsan_handle_out_of_bounds.cold+0x44/0x49 [ 6.125736] ? MR_PopulateDrvRaidMap+0x194/0x580 [megaraid_sas] [ 6.125747] mr_update_load_balance_params+0xb9/0xc0 [megaraid_sas] [ 6.125753] MR_ValidateMapInfo+0x8d/0x290 [megaraid_sas] [ 6.125757] megasas_init_adapter_fusion+0x3ce/0x420 [megaraid_sas] [ 6.125762] ? megasas_setup_reply_map+0x49/0xac [megaraid_sas] [ 6.125768] megasas_init_fw.cold+0x87c/0x10c8 [megaraid_sas] [ 6.125774] megasas_probe_one+0x15c/0x4e0 [megaraid_sas] [ 6.125779] local_pci_probe+0x48/0x90 [ 6.125783] work_for_cpu_fn+0x17/0x30 [ 6.125785] process_one_work+0x228/0x3d0 [ 6.125786] worker_thread+0x223/0x420 [ 6.125787] ? process_one_work+0x3d0/0x3d0 [ 6.125788] kthread+0x127/0x150 [ 6.125790] ? set_kthread_struct+0x50/0x50 [ 6.125791] ret_from_fork+0x1f/0x30 [ 6.125796] [ 6.125796] Steps to reproduce: 1. Connect PERC H355 controller to the system 2. Create RAID1 using drives connected to PERC Controller 3. Install Ubuntu 22.04.1 on VD 4. Boot into OS after installation 5. Multiple Call Traces of "array-index-out-of-bounds" are seen Expected Behavior: OS should boot without this Call Trace [Fix] [PATCH v3 0/6] Replace one-element arrays with flexible-array members https://lore.kernel.org/linux-hardening/cover.1660592640.git.gustavo...@kernel.org/ 48658213 scsi: megaraid_sas: Use struct_size() in code related to struct MR_PD_CFG_SEQ_NUM_SYNC 41e83026 scsi: megaraid_sas: Use struct_size() in code related to struct MR_FW_RAID_MAP ee92366a scsi: megaraid_sas: Replace one-element array with flexible- array member in MR_PD_CFG_SEQ_NUM_SYNC eeb3bab7 scsi: megaraid_sas: Replace one-element array with flexible- array member in MR_DRV_RAID_MAP 204a29a1 scsi: megaraid_sas: Replace one-element array with flexible- array member in MR_FW_RAID_MAP_DYNAMIC ac23b92b scsi: megaraid_sas: Replace one-element array with flexible- array member in MR_FW_RAID_MAP [Test Plan] 1. Connect PERC H355 controller to the system 2. Create RAID1 using drives connected to PERC Controller 3. Install Ubuntu 22.04.1 on VD 4. Boot into OS after installation OS should boot without the Call Trace listed in the Impact field [Where problems could occur] [Other Info] https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/array_bounds_lp_2008157 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008157/+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 2045561] Re: linux: please move dmi-sysfs.ko (CONFIG_DMI_SYSFS for SMBIOS support) from linux-modules-extra to linux-modules
Gentle ping. Would love to see this fix in time for Noble's release. Thanks! ** Description changed: SRU Justification [Impact] The dmi-sysfs.ko module (CONFIG_DMI_SYSFS) is currently shipped in linux-modules-extra. This makes it hard to pull in via the linux-virtual package, it can only come from the linux-generic one that also pulls in the firmware and everything else needed for baremetal, and that serves no purpose in a qemu VM. This stops VMs using these kernels from being configurable using qemu or cloud-hypervisor's SMBIOS type 11 strings. This feature is supported and used widely by systemd: https://www.freedesktop.org/software/systemd/man/latest/smbios-type-11.html https://systemd.io/CREDENTIALS/ A user launching a VM using the linux-kvm kernel image is not able to specify SMBIOS strings to automatically configured userspace services and programs due to the lack of this kconfig. We make extensive use of these in systemd's upstream CI, which is running on Github Actions, which uses Jammy, so it would be great to have this backported. For example: qemu-system-x86_64 \ -machine type=q35,accel=kvm,smm=on \ -smp 2 \ -m 1G \ -cpu host \ -nographic \ -nodefaults \ -serial mon:stdio \ -drive if=none,id=hd,file=ubuntu_jammy.raw,format=raw \ -device virtio-scsi-pci,id=scsi \ -device scsi-hd,drive=hd,bootindex=1 \ -smbios type=11,value=io.systemd.credential:mycred=supersecret [Fix] Please consider moving this module to linux-modules. These are already enabled in the 'main' kernel config, and in other distros. In Debian/Archlinux/Fedora it is a built-in, and on SUSE it is a module installed by default. To verify this works, it is sufficient to check that the /sys/firmware/dmi/entries/ directory in sysfs is present: $ ls /sys/firmware/dmi/entries/ 0-0126-1 126-4 126-8 130-0 133-0 136-0 140-2 15-0 18-0 21-1 221-1 24-0 7-1 8-2 8-6 1-0126-10 126-5 126-9 131-0 134-0 14-0 140-3 16-0 19-0 219-0 221-2 3-0 7-2 8-3 9-0 12-0 126-2 126-6 127-0 131-1 135-0 140-0 140-4 17-0 2-0 22-0 221-3 4-0 8-0 8-4 9-1 126-0 126-3 126-7 13-0 132-0 135-1 140-1 14-1 17-1 21-0 221-0 222-0 7-0 8-1 8-5 Without this module installed and loaded, the directory won't be there. Once enabled, it will be there. [Regression Potential] Moving a module from a less-common to a more-common package should not - have any negative side effects. + have any negative side effects. The main effect will be a little more + disk space used by the more common package, whether the module is in use + or not. There will also be more functionality available in the default + installation, which means a slightly increased surface and possibility + of new bugs in case it gets used. -- 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/2045561 Title: linux: please move dmi-sysfs.ko (CONFIG_DMI_SYSFS for SMBIOS support) from linux-modules-extra to linux-modules Status in linux package in Ubuntu: New Status in linux source package in Jammy: New Status in linux source package in Lunar: New Status in linux source package in Mantic: New Status in linux source package in Noble: New Bug description: SRU Justification [Impact] The dmi-sysfs.ko module (CONFIG_DMI_SYSFS) is currently shipped in linux-modules-extra. This makes it hard to pull in via the linux- virtual package, it can only come from the linux-generic one that also pulls in the firmware and everything else needed for baremetal, and that serves no purpose in a qemu VM. This stops VMs using these kernels from being configurable using qemu or cloud-hypervisor's SMBIOS type 11 strings. This feature is supported and used widely by systemd: https://www.freedesktop.org/software/systemd/man/latest/smbios-type-11.html https://systemd.io/CREDENTIALS/ A user launching a VM using the linux-kvm kernel image is not able to specify SMBIOS strings to automatically configured userspace services and programs due to the lack of this kconfig. We make extensive use of these in systemd's upstream CI, which is running on Github Actions, which uses Jammy, so it would be great to have this backported. For example: qemu-system-x86_64 \ -machine type=q35,accel=kvm,smm=on \ -smp 2 \ -m 1G \ -cpu host \ -nographic \ -nodefaults \ -serial mon:stdio \ -drive if=none,id=hd,file=ubuntu_jammy.raw,format=raw \ -device virtio-scsi-pci,id=scsi \ -device scsi-hd,drive=hd,bootindex=1 \ -smbios type=11,value=io.systemd.credential:mycred=supersecret [Fix] Please consider moving this
[Kernel-packages] [Bug 2047184] Re: Audio device is not available, instead it shows dummy output in the settings
** Tags added: originate-from-2047794 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2047184 Title: Audio device is not available, instead it shows dummy output in the settings Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux source package in Noble: In Progress Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] Audio device is not available, instead it shows dummy output in the settings [Fix] SOF driver looks for a config which both sample width and valid bits are both 32 bits. However, the config in NHLT table is 32-bit sample width and 24-bit valid bits. Should ignore the valid bits in NHLT when the sample width is 32 bits. Confirmed the below commit in v6.7-rc4 fix the issue 7b4c93a50a2e ALSA: hda: intel-nhlt: Ignore vbps when looking for DMIC 32 bps format [Test case] 1. check audio input/output on the system 2. System can play and record audio normally [Where problems could occur] When the samples assumed to be vbps=32 then the 'noise' introduced by the lower two bits (channel number) have no real life implication on audio quality. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2047184/+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 2040192] Re: AppArmor spams kernel log with assert when auditing
Verification passed for mantic-linux-laptop. I ran the AppArmor QA Regression Tests [1] and the specific prompting tests [2] which were able to reproduce the issue before. The QA Regression Tests that failed were due to a timeout because I'm emulating in my machine, but they pass when the timeout is increased. georgia@sec-mantic-arm64:~$ uname -a Linux sec-mantic-arm64 6.5.0-1007-laptop #10-Ubuntu SMP PREEMPT_DYNAMIC Wed Nov 22 20:27:28 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux georgia@sec-mantic-arm64:~/apparmor/tests/regression/apparmor$ sudo ./prompt.sh xpass: PROMPT (allow (rule link file l)) - root xpass: PROMPT (allow (flag link file l)) - root xpass: PROMPT (allow (rule mmap_exec file rwm)) - root xpass: PROMPT (allow (flag mmap_exec file rwm)) - root xpass: PROMPT (allow (rule lock file rwk)) - root xpass: PROMPT (allow (flag lock file rwk)) - root xpass: PROMPT (allow (rule exec file rix)) - root xpass: PROMPT (allow (flag exec file rix)) - root xpass: PROMPT (allow (rule exec file ux)) - root xpass: PROMPT (allow (flag exec file ux)) - root georgia@sec-mantic-arm64:~/qrt-test-apparmor$ sudo ./test-apparmor.py ERROR: test_dbus (__main__.ApparmorTest.test_dbus) Test dbus apparmor activation from dbus-tests -- Traceback (most recent call last): File "/home/georgia/qrt-test-apparmor/./test-apparmor.py", line 719, in test_dbus rc, report = testlib.cmd(['/usr/lib/dbus-1.0/installed-tests/dbus/test-apparmor-activation.sh'], ^^^ File "/home/georgia/qrt-test-apparmor/testlib.py", line 471, in cmd out, outerr = sp.communicate(input, timeout=timeout) ^^ File "/usr/lib/python3.11/subprocess.py", line 1209, in communicate stdout, stderr = self._communicate(input, endtime, timeout) ^^ File "/usr/lib/python3.11/subprocess.py", line 2109, in _communicate self._check_timeout(endtime, orig_timeout, stdout, stderr) File "/usr/lib/python3.11/subprocess.py", line 1253, in _check_timeout raise TimeoutExpired( subprocess.TimeoutExpired: Command '['/usr/lib/dbus-1.0/installed-tests/dbus/test-apparmor-activation.sh']' timed out after 5 seconds - running attach_disconnected Fatal Error (unix_fd_server): Unable to run test sub-executable PASSED: aa_exec access at_secure introspect capabilities changeprofile onexec changehat changehat_fork changehat_misc chdir clone coredump deleted e2e environ exec exec_qual fchdir fd_inheritance fork i18n link link_subset mkdir mmap mount mult_mount named_pipe namespaces net_raw open openat pipe pivot_root posix_ipc ptrace pwrite query_label regex rename readdir rw socketpair swap sd_flags setattr symlink syscall sysv_ipc tcp unix_fd_server unix_socket_pathname unix_socket_abstract unix_socket_unnamed unix_socket_autobind unlink userns xattrs xattrs_profile longpath nfs dbus_eavesdrop dbus_message dbus_service dbus_unrequested_reply io_uring aa_policy_cache exec_stack nnp stackonexec stackprofile FAILED: attach_disconnected make: *** [Makefile:402: alltests] Error 1 - ERROR: test_0 (__main__.TestLogprof.test_0) test 'ping' -- Traceback (most recent call last): File "/tmp/testlib2jc8hiih/source/mantic/apparmor-4.0.0~alpha2/utils/test/common_test.py", line 90, in stub_test self._run_test(test_data, expected) File "/tmp/testlib2jc8hiih/source/mantic/apparmor-4.0.0~alpha2/utils/test/test-logprof.py", line 99, in _run_test self.process.wait(timeout=0.2) File "/usr/lib/python3.11/subprocess.py", line 1264, in wait return self._wait(timeout=timeout) ^^^ File "/usr/lib/python3.11/subprocess.py", line 2038, in _wait raise TimeoutExpired(self.args, timeout) subprocess.TimeoutExpired: Command '['/usr/bin/python3', '../aa-logprof', '--json', '--configdir', './', '-f', './logprof/ping.auditlog', '-d', '/tmp/aa-test-tkkg1ex3/profiles', '--no-check-mountpoint']' timed out after 0.2 seconds -- Ran 62 tests in 43542.817s FAILED (failures=3, errors=1, skipped=3) Rerunning failing tests increasing the timeout georgia@sec-mantic-arm64:~/qrt-test-apparmor$ sudo ./test-apparmor.py ApparmorTest.test_dbus Skipping private tests . -- Ran 1 test in 19.786s OK georgia@sec-mantic-arm64:~/apparmor-4.0.0~alpha2/tests/regression/apparmor$ sudo bash ./attach_disconnected.sh georgia@sec-mantic-arm64:~/apparmor-4.0.0~alpha2/tests/regression/apparmor$ echo $? 0
[Kernel-packages] [Bug 2040245] Re: apparmor oops when racing to retrieve a notification
Verification passed for mantic-linux-laptop. I ran the AppArmor QA Regression Tests [1] and specific prompting tests [2]. The QA Regression Tests that failed were due to a timeout because I'm emulating in my machine, but they pass when the timeout is increased. georgia@sec-mantic-arm64:~$ uname -a Linux sec-mantic-arm64 6.5.0-1007-laptop #10-Ubuntu SMP PREEMPT_DYNAMIC Wed Nov 22 20:27:28 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux georgia@sec-mantic-arm64:~/apparmor/tests/regression/apparmor$ sudo ./prompt.sh xpass: PROMPT (allow (rule link file l)) - root xpass: PROMPT (allow (flag link file l)) - root xpass: PROMPT (allow (rule mmap_exec file rwm)) - root xpass: PROMPT (allow (flag mmap_exec file rwm)) - root xpass: PROMPT (allow (rule lock file rwk)) - root xpass: PROMPT (allow (flag lock file rwk)) - root xpass: PROMPT (allow (rule exec file rix)) - root xpass: PROMPT (allow (flag exec file rix)) - root xpass: PROMPT (allow (rule exec file ux)) - root xpass: PROMPT (allow (flag exec file ux)) - root georgia@sec-mantic-arm64:~/qrt-test-apparmor$ sudo ./test-apparmor.py ERROR: test_dbus (__main__.ApparmorTest.test_dbus) Test dbus apparmor activation from dbus-tests -- Traceback (most recent call last): File "/home/georgia/qrt-test-apparmor/./test-apparmor.py", line 719, in test_dbus rc, report = testlib.cmd(['/usr/lib/dbus-1.0/installed-tests/dbus/test-apparmor-activation.sh'], ^^^ File "/home/georgia/qrt-test-apparmor/testlib.py", line 471, in cmd out, outerr = sp.communicate(input, timeout=timeout) ^^ File "/usr/lib/python3.11/subprocess.py", line 1209, in communicate stdout, stderr = self._communicate(input, endtime, timeout) ^^ File "/usr/lib/python3.11/subprocess.py", line 2109, in _communicate self._check_timeout(endtime, orig_timeout, stdout, stderr) File "/usr/lib/python3.11/subprocess.py", line 1253, in _check_timeout raise TimeoutExpired( subprocess.TimeoutExpired: Command '['/usr/lib/dbus-1.0/installed-tests/dbus/test-apparmor-activation.sh']' timed out after 5 seconds - running attach_disconnected Fatal Error (unix_fd_server): Unable to run test sub-executable PASSED: aa_exec access at_secure introspect capabilities changeprofile onexec changehat changehat_fork changehat_misc chdir clone coredump deleted e2e environ exec exec_qual fchdir fd_inheritance fork i18n link link_subset mkdir mmap mount mult_mount named_pipe namespaces net_raw open openat pipe pivot_root posix_ipc ptrace pwrite query_label regex rename readdir rw socketpair swap sd_flags setattr symlink syscall sysv_ipc tcp unix_fd_server unix_socket_pathname unix_socket_abstract unix_socket_unnamed unix_socket_autobind unlink userns xattrs xattrs_profile longpath nfs dbus_eavesdrop dbus_message dbus_service dbus_unrequested_reply io_uring aa_policy_cache exec_stack nnp stackonexec stackprofile FAILED: attach_disconnected make: *** [Makefile:402: alltests] Error 1 - ERROR: test_0 (__main__.TestLogprof.test_0) test 'ping' -- Traceback (most recent call last): File "/tmp/testlib2jc8hiih/source/mantic/apparmor-4.0.0~alpha2/utils/test/common_test.py", line 90, in stub_test self._run_test(test_data, expected) File "/tmp/testlib2jc8hiih/source/mantic/apparmor-4.0.0~alpha2/utils/test/test-logprof.py", line 99, in _run_test self.process.wait(timeout=0.2) File "/usr/lib/python3.11/subprocess.py", line 1264, in wait return self._wait(timeout=timeout) ^^^ File "/usr/lib/python3.11/subprocess.py", line 2038, in _wait raise TimeoutExpired(self.args, timeout) subprocess.TimeoutExpired: Command '['/usr/bin/python3', '../aa-logprof', '--json', '--configdir', './', '-f', './logprof/ping.auditlog', '-d', '/tmp/aa-test-tkkg1ex3/profiles', '--no-check-mountpoint']' timed out after 0.2 seconds -- Ran 62 tests in 43542.817s FAILED (failures=3, errors=1, skipped=3) Rerunning failing tests increasing the timeout georgia@sec-mantic-arm64:~/qrt-test-apparmor$ sudo ./test-apparmor.py ApparmorTest.test_dbus Skipping private tests . -- Ran 1 test in 19.786s OK georgia@sec-mantic-arm64:~/apparmor-4.0.0~alpha2/tests/regression/apparmor$ sudo bash ./attach_disconnected.sh georgia@sec-mantic-arm64:~/apparmor-4.0.0~alpha2/tests/regression/apparmor$ echo $? 0 georgia@sec-mantic-arm64:~/apparmor-4.0.0~alpha2/utils/test$ python3
[Kernel-packages] [Bug 2040250] Re: apparmor notification files verification
Verification passed for mantic-linux-laptop. I ran the AppArmor QA Regression Tests [1] and specific prompting tests [2]. The QA Regression Tests that failed were due to a timeout because I'm emulating in my machine, but they pass when the timeout is increased. georgia@sec-mantic-arm64:~$ uname -a Linux sec-mantic-arm64 6.5.0-1007-laptop #10-Ubuntu SMP PREEMPT_DYNAMIC Wed Nov 22 20:27:28 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux georgia@sec-mantic-arm64:~/apparmor/tests/regression/apparmor$ sudo ./prompt.sh xpass: PROMPT (allow (rule link file l)) - root xpass: PROMPT (allow (flag link file l)) - root xpass: PROMPT (allow (rule mmap_exec file rwm)) - root xpass: PROMPT (allow (flag mmap_exec file rwm)) - root xpass: PROMPT (allow (rule lock file rwk)) - root xpass: PROMPT (allow (flag lock file rwk)) - root xpass: PROMPT (allow (rule exec file rix)) - root xpass: PROMPT (allow (flag exec file rix)) - root xpass: PROMPT (allow (rule exec file ux)) - root xpass: PROMPT (allow (flag exec file ux)) - root georgia@sec-mantic-arm64:~/qrt-test-apparmor$ sudo ./test-apparmor.py ERROR: test_dbus (__main__.ApparmorTest.test_dbus) Test dbus apparmor activation from dbus-tests -- Traceback (most recent call last): File "/home/georgia/qrt-test-apparmor/./test-apparmor.py", line 719, in test_dbus rc, report = testlib.cmd(['/usr/lib/dbus-1.0/installed-tests/dbus/test-apparmor-activation.sh'], ^^^ File "/home/georgia/qrt-test-apparmor/testlib.py", line 471, in cmd out, outerr = sp.communicate(input, timeout=timeout) ^^ File "/usr/lib/python3.11/subprocess.py", line 1209, in communicate stdout, stderr = self._communicate(input, endtime, timeout) ^^ File "/usr/lib/python3.11/subprocess.py", line 2109, in _communicate self._check_timeout(endtime, orig_timeout, stdout, stderr) File "/usr/lib/python3.11/subprocess.py", line 1253, in _check_timeout raise TimeoutExpired( subprocess.TimeoutExpired: Command '['/usr/lib/dbus-1.0/installed-tests/dbus/test-apparmor-activation.sh']' timed out after 5 seconds - running attach_disconnected Fatal Error (unix_fd_server): Unable to run test sub-executable PASSED: aa_exec access at_secure introspect capabilities changeprofile onexec changehat changehat_fork changehat_misc chdir clone coredump deleted e2e environ exec exec_qual fchdir fd_inheritance fork i18n link link_subset mkdir mmap mount mult_mount named_pipe namespaces net_raw open openat pipe pivot_root posix_ipc ptrace pwrite query_label regex rename readdir rw socketpair swap sd_flags setattr symlink syscall sysv_ipc tcp unix_fd_server unix_socket_pathname unix_socket_abstract unix_socket_unnamed unix_socket_autobind unlink userns xattrs xattrs_profile longpath nfs dbus_eavesdrop dbus_message dbus_service dbus_unrequested_reply io_uring aa_policy_cache exec_stack nnp stackonexec stackprofile FAILED: attach_disconnected make: *** [Makefile:402: alltests] Error 1 - ERROR: test_0 (__main__.TestLogprof.test_0) test 'ping' -- Traceback (most recent call last): File "/tmp/testlib2jc8hiih/source/mantic/apparmor-4.0.0~alpha2/utils/test/common_test.py", line 90, in stub_test self._run_test(test_data, expected) File "/tmp/testlib2jc8hiih/source/mantic/apparmor-4.0.0~alpha2/utils/test/test-logprof.py", line 99, in _run_test self.process.wait(timeout=0.2) File "/usr/lib/python3.11/subprocess.py", line 1264, in wait return self._wait(timeout=timeout) ^^^ File "/usr/lib/python3.11/subprocess.py", line 2038, in _wait raise TimeoutExpired(self.args, timeout) subprocess.TimeoutExpired: Command '['/usr/bin/python3', '../aa-logprof', '--json', '--configdir', './', '-f', './logprof/ping.auditlog', '-d', '/tmp/aa-test-tkkg1ex3/profiles', '--no-check-mountpoint']' timed out after 0.2 seconds -- Ran 62 tests in 43542.817s FAILED (failures=3, errors=1, skipped=3) Rerunning failing tests increasing the timeout georgia@sec-mantic-arm64:~/qrt-test-apparmor$ sudo ./test-apparmor.py ApparmorTest.test_dbus Skipping private tests . -- Ran 1 test in 19.786s OK georgia@sec-mantic-arm64:~/apparmor-4.0.0~alpha2/tests/regression/apparmor$ sudo bash ./attach_disconnected.sh georgia@sec-mantic-arm64:~/apparmor-4.0.0~alpha2/tests/regression/apparmor$ echo $? 0 georgia@sec-mantic-arm64:~/apparmor-4.0.0~alpha2/utils/test$ python3
[Kernel-packages] [Bug 2040194] Re: apparmor restricts read access of user namespace mediation sysctls to root
Verification passed for mantic-linux-laptop. I ran the AppArmor QA Regression Tests [1] checked file permissions for /proc/sys/kernel/*unprivileged*. The QA Regression Tests that failed were due to a timeout because I'm emulating in my machine, but they pass when the timeout is increased. georgia@sec-mantic-arm64:~$ uname -a Linux sec-mantic-arm64 6.5.0-1007-laptop #10-Ubuntu SMP PREEMPT_DYNAMIC Wed Nov 22 20:27:28 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux georgia@sec-mantic-arm64:~$ ll /proc/sys/kernel/*unprivileged* -rw--- 1 root root 0 Jan 12 18:38 /proc/sys/kernel/apparmor_restrict_unprivileged_io_uring -rw-r--r-- 1 root root 0 Jan 12 18:38 /proc/sys/kernel/apparmor_restrict_unprivileged_unconfined -rw-r--r-- 1 root root 0 Jan 12 18:36 /proc/sys/kernel/apparmor_restrict_unprivileged_userns -rw--- 1 root root 0 Jan 12 18:38 /proc/sys/kernel/apparmor_restrict_unprivileged_userns_complain -rw--- 1 root root 0 Jan 12 18:38 /proc/sys/kernel/apparmor_restrict_unprivileged_userns_force -rw-r--r-- 1 root root 0 Jan 12 18:38 /proc/sys/kernel/unprivileged_bpf_disabled -rw--- 1 root root 0 Jan 12 18:38 /proc/sys/kernel/unprivileged_userns_apparmor_policy -rw-r--r-- 1 root root 0 Jan 12 18:38 /proc/sys/kernel/unprivileged_userns_clone georgia@sec-mantic-arm64:~/qrt-test-apparmor$ sudo ./test-apparmor.py ERROR: test_dbus (__main__.ApparmorTest.test_dbus) Test dbus apparmor activation from dbus-tests -- Traceback (most recent call last): File "/home/georgia/qrt-test-apparmor/./test-apparmor.py", line 719, in test_dbus rc, report = testlib.cmd(['/usr/lib/dbus-1.0/installed-tests/dbus/test-apparmor-activation.sh'], ^^^ File "/home/georgia/qrt-test-apparmor/testlib.py", line 471, in cmd out, outerr = sp.communicate(input, timeout=timeout) ^^ File "/usr/lib/python3.11/subprocess.py", line 1209, in communicate stdout, stderr = self._communicate(input, endtime, timeout) ^^ File "/usr/lib/python3.11/subprocess.py", line 2109, in _communicate self._check_timeout(endtime, orig_timeout, stdout, stderr) File "/usr/lib/python3.11/subprocess.py", line 1253, in _check_timeout raise TimeoutExpired( subprocess.TimeoutExpired: Command '['/usr/lib/dbus-1.0/installed-tests/dbus/test-apparmor-activation.sh']' timed out after 5 seconds - running attach_disconnected Fatal Error (unix_fd_server): Unable to run test sub-executable PASSED: aa_exec access at_secure introspect capabilities changeprofile onexec changehat changehat_fork changehat_misc chdir clone coredump deleted e2e environ exec exec_qual fchdir fd_inheritance fork i18n link link_subset mkdir mmap mount mult_mount named_pipe namespaces net_raw open openat pipe pivot_root posix_ipc ptrace pwrite query_label regex rename readdir rw socketpair swap sd_flags setattr symlink syscall sysv_ipc tcp unix_fd_server unix_socket_pathname unix_socket_abstract unix_socket_unnamed unix_socket_autobind unlink userns xattrs xattrs_profile longpath nfs dbus_eavesdrop dbus_message dbus_service dbus_unrequested_reply io_uring aa_policy_cache exec_stack nnp stackonexec stackprofile FAILED: attach_disconnected make: *** [Makefile:402: alltests] Error 1 - ERROR: test_0 (__main__.TestLogprof.test_0) test 'ping' -- Traceback (most recent call last): File "/tmp/testlib2jc8hiih/source/mantic/apparmor-4.0.0~alpha2/utils/test/common_test.py", line 90, in stub_test self._run_test(test_data, expected) File "/tmp/testlib2jc8hiih/source/mantic/apparmor-4.0.0~alpha2/utils/test/test-logprof.py", line 99, in _run_test self.process.wait(timeout=0.2) File "/usr/lib/python3.11/subprocess.py", line 1264, in wait return self._wait(timeout=timeout) ^^^ File "/usr/lib/python3.11/subprocess.py", line 2038, in _wait raise TimeoutExpired(self.args, timeout) subprocess.TimeoutExpired: Command '['/usr/bin/python3', '../aa-logprof', '--json', '--configdir', './', '-f', './logprof/ping.auditlog', '-d', '/tmp/aa-test-tkkg1ex3/profiles', '--no-check-mountpoint']' timed out after 0.2 seconds -- Ran 62 tests in 43542.817s FAILED (failures=3, errors=1, skipped=3) Rerunning failing tests increasing the timeout georgia@sec-mantic-arm64:~/qrt-test-apparmor$ sudo ./test-apparmor.py ApparmorTest.test_dbus Skipping private tests . -- Ran 1 test in 19.786s OK
[Kernel-packages] [Bug 2047461] Re: drm: Update file owner during use
6.7 in noble has this ** Changed in: linux (Ubuntu Noble) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2047461 Title: drm: Update file owner during use Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux source package in Mantic: Fix Committed Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: Fix Released Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] Our testing tools need to check the app runs on which GPU, and now it only shows the processes as Xorg or XWayland $ cat /sys/kernel/debug/dri/0/clients command pid dev master a uid magic Xorg 2344 0 yy 0 0 Xorg 2344 0 ny 0 2 Xorg 2344 0 ny 0 3 Xorg 2344 0 ny 0 4 [Fix] The commit from v6.7-rc1 fixes the issue $ cat /sys/kernel/debug/dri/0/clients command tgid dev master a uid magic Xorg 830 0 yy 0 0 xfce4-session 880 0 ny 0 1 xfwm4 943 0 ny 0 2 neverball 1095 0 ny 0 3 [Test case] 1. check processes by 'cat /sys/kernel/debug/dri/0/clients' 2. runs glxgears(specify the GPU if needed) 3. check the precesses again and there should be a 'glxgears' process [Where problems could occur] This commit added some protections on read/write and only changes the process' pid, the worst case is that the process got the wrong pid as its owner. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2047461/+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 2049317] Re: UBSAN array-index-out-of-bounds error in dmesg - amd gpu drivers
I changed the source package to linux-meta-hwe-6.5 because this is the kernel version, but I'm not sure that this is the correct package. ** Package changed: ubuntu => linux-meta-hwe-6.5 (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2049317 Title: UBSAN array-index-out-of-bounds error in dmesg - amd gpu drivers Status in linux-meta-hwe-6.5 package in Ubuntu: Confirmed Bug description: lsb_release -a System info Distributor ID: Ubuntu Description:Ubuntu 22.04.3 LTS Release:22.04 Codename: jammy uname -a Linux dario-Aspire-E5-553G 6.5.0-14-generic #14~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Mon Nov 20 18:15:30 UTC 2 x86_64 x86_64 x86_64 GNU/Linux At boot and in dmesg (and /var/log/syslog) this error appears, repeated multiple times, I don't remember seeing it in the past, If necessary I can provide the ful /var/log/syslog file: Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.503732] Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.504707] UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.5-q7NZ0T/linux-hwe-6.5-6.5.0/drivers/gpu/drm/amd/amdgpu/../pm/powerplay/hwmgr/processpptables.c:1502:42 Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.506717] index 1 is out of range for type 'ATOM_PPLIB_CAC_Leakage_Record [1]' Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.507673] CPU: 1 PID: 136 Comm: systemd-udevd Not tainted 6.5.0-14-generic #14~22.04.1-Ubuntu Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.507677] Hardware name: Acer Aspire E5-553G/Wasp_BR, BIOS V1.31 03/28/2018 Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.507679] Call Trace: Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.507681] Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.507684] dump_stack_lvl+0x48/0x70 Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.507694] dump_stack+0x10/0x20 Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.507696] __ubsan_handle_out_of_bounds+0xc6/0x110 Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.507701] init_dpm2_parameters+0x2d6/0x360 [amdgpu] Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.509001] pp_tables_initialize+0x12c/0x440 [amdgpu] Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.510250] ? amdgpu_ring_test_helper+0x83/0x90 [amdgpu] Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.511425] hwmgr_hw_init+0x7b/0x1e0 [amdgpu] Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.512733] pp_hw_init+0x16/0x50 [amdgpu] Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.513987] amdgpu_device_ip_init+0x48d/0x960 [amdgpu] Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.515143] amdgpu_device_init+0x9c8/0x1160 [amdgpu] Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.516313] amdgpu_driver_load_kms+0x1a/0x1c0 [amdgpu] Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.517507] amdgpu_pci_probe+0x182/0x450 [amdgpu] Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.518678] local_pci_probe+0x47/0xb0 Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.518684] pci_call_probe+0x55/0x190 Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.518688] pci_device_probe+0x84/0x120 Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.518692] really_probe+0x1cc/0x430 Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.518696] __driver_probe_device+0x8c/0x190 Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.518709] driver_probe_device+0x24/0xd0 Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.518712] __driver_attach+0x10b/0x210 Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.518715] ? __pfx___driver_attach+0x10/0x10 Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.518718] bus_for_each_dev+0x8d/0xf0 Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.518723] driver_attach+0x1e/0x30 Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.518727] bus_add_driver+0x127/0x240 Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.518731] driver_register+0x5e/0x130 Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.518735] ? __pfx_amdgpu_init+0x10/0x10 [amdgpu] Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.519866] __pci_register_driver+0x62/0x70 Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.519871] amdgpu_init+0x69/0xff0 [amdgpu] Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.521048] do_one_initcall+0x5e/0x340 Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.521056] do_init_module+0x68/0x260 Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.521062] load_module+0xb85/0xcd0 Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.521066] ? security_kernel_post_read_file+0x75/0x90 Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.521070] ?
[Kernel-packages] [Bug 2049317] [NEW] UBSAN array-index-out-of-bounds error in dmesg - amd gpu drivers
You have been subscribed to a public bug: lsb_release -a System info Distributor ID: Ubuntu Description:Ubuntu 22.04.3 LTS Release:22.04 Codename: jammy uname -a Linux dario-Aspire-E5-553G 6.5.0-14-generic #14~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Mon Nov 20 18:15:30 UTC 2 x86_64 x86_64 x86_64 GNU/Linux At boot and in dmesg (and /var/log/syslog) this error appears, repeated multiple times, I don't remember seeing it in the past, If necessary I can provide the ful /var/log/syslog file: Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.503732] Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.504707] UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.5-q7NZ0T/linux-hwe-6.5-6.5.0/drivers/gpu/drm/amd/amdgpu/../pm/powerplay/hwmgr/processpptables.c:1502:42 Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.506717] index 1 is out of range for type 'ATOM_PPLIB_CAC_Leakage_Record [1]' Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.507673] CPU: 1 PID: 136 Comm: systemd-udevd Not tainted 6.5.0-14-generic #14~22.04.1-Ubuntu Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.507677] Hardware name: Acer Aspire E5-553G/Wasp_BR, BIOS V1.31 03/28/2018 Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.507679] Call Trace: Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.507681] Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.507684] dump_stack_lvl+0x48/0x70 Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.507694] dump_stack+0x10/0x20 Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.507696] __ubsan_handle_out_of_bounds+0xc6/0x110 Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.507701] init_dpm2_parameters+0x2d6/0x360 [amdgpu] Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.509001] pp_tables_initialize+0x12c/0x440 [amdgpu] Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.510250] ? amdgpu_ring_test_helper+0x83/0x90 [amdgpu] Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.511425] hwmgr_hw_init+0x7b/0x1e0 [amdgpu] Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.512733] pp_hw_init+0x16/0x50 [amdgpu] Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.513987] amdgpu_device_ip_init+0x48d/0x960 [amdgpu] Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.515143] amdgpu_device_init+0x9c8/0x1160 [amdgpu] Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.516313] amdgpu_driver_load_kms+0x1a/0x1c0 [amdgpu] Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.517507] amdgpu_pci_probe+0x182/0x450 [amdgpu] Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.518678] local_pci_probe+0x47/0xb0 Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.518684] pci_call_probe+0x55/0x190 Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.518688] pci_device_probe+0x84/0x120 Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.518692] really_probe+0x1cc/0x430 Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.518696] __driver_probe_device+0x8c/0x190 Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.518709] driver_probe_device+0x24/0xd0 Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.518712] __driver_attach+0x10b/0x210 Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.518715] ? __pfx___driver_attach+0x10/0x10 Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.518718] bus_for_each_dev+0x8d/0xf0 Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.518723] driver_attach+0x1e/0x30 Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.518727] bus_add_driver+0x127/0x240 Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.518731] driver_register+0x5e/0x130 Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.518735] ? __pfx_amdgpu_init+0x10/0x10 [amdgpu] Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.519866] __pci_register_driver+0x62/0x70 Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.519871] amdgpu_init+0x69/0xff0 [amdgpu] Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.521048] do_one_initcall+0x5e/0x340 Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.521056] do_init_module+0x68/0x260 Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.521062] load_module+0xb85/0xcd0 Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.521066] ? security_kernel_post_read_file+0x75/0x90 Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.521070] ? security_kernel_post_read_file+0x75/0x90 Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.521074] init_module_from_file+0x96/0x100 Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.521077] ? init_module_from_file+0x96/0x100 Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.521082] idempotent_init_module+0x11c/0x2b0 Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.521087] __x64_sys_finit_module+0x64/0xd0 Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.521090] do_syscall_64+0x5b/0x90 Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [ 12.521095] ?
[Kernel-packages] [Bug 2049327] Re: `alsactl init` unable to initialze audio device on G700
This bug was fixed in the package alsa-ucm-conf - 1.2.10-1ubuntu2 --- alsa-ucm-conf (1.2.10-1ubuntu2) noble; urgency=medium * d/p/0001-Add-initial-support-for-MediaTek-Genio-boards.patch - fix typo to make the patch work on mtk8390-evk (lp: #2049327) -- Zhaoxuan Zhai Tue, 16 Jan 2024 11:23:07 +0100 ** Changed in: alsa-ucm-conf (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/2049327 Title: `alsactl init` unable to initialze audio device on G700 Status in alsa-ucm-conf package in Ubuntu: Fix Released Bug description: [Impact] This bug cause "alsactl init" command unable to initialize mt8390-evk correctly and print these error message: ``` ceqa@ubuntu:/home/ceqa$ alsactl init alsa-lib main.c:761:(execute_sequence) unable to execute cset 'name='DP_OUT_MUX' Disconnect' alsa-lib main.c:2373:(set_boot_user) Unable to execute boot sequence Found hardware: "mt8390-evk" "" "" "" "" Hardware is initialized using a generic method ``` Thus, the audio devices on MediaTek G700 do not work. This patch fix this bug by correcting 'DP_OUT_MUX' to 'DPTX_OUT_MUX'. [ Test Plan ] Reproduce: 1. Install Ubuntu 22.04 (jammy) on a MediaTek G700 device 2. Run `alsactl init` on MediaTek G700 device 3. alsactl print error message "unable to execute cset 'name='DP_OUT_MUX' Disconnect'" and audio devices do not work. Verify: By applying this patch, alsactl does not print this error message and audio devices work. [Where problems could occur] This patch fix the typo in ucm files, and it affects the device init process on Mediatek Genio boards. [ Other Info ] There is a typo in 'd/p/0001-Add-initial-support-for-MediaTek-Genio-boards.patch'. The name of the flag that controls the audio output of the DP port is not 'DP_OUT_MUX'. It is 'DPTX_OUT_MUX'. MediaTek fix this issue in the PR in upstream: https://github.com/alsa-project/alsa-ucm-conf/compare/243f2d60740e41a0cfb7779388c17e4a00e1bfe9..a55f840ab2b13f32cb55cd1730933ef0f5a96079 mt8390-evk (G700) Pull Request: (Still under review) https://github.com/alsa-project/alsa-ucm-conf/pull/321 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/2049327/+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 2049234] Re: non-Ethernet tunnel interface creation fails on jammy 5.15.0-81 or later
I’m unsure this is the right way but adding linux package as this was also caused by kernel upgrade. ** Also affects: linux (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/2049234 Title: non-Ethernet tunnel interface creation fails on jammy 5.15.0-81 or later Status in linux package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: jammy kernel 5.15.0-81.90 includes the following backport: https://github.com/torvalds/linux/commit/b0ad3c179059089d809b477a1d445c1183a7b8fe https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy/commit/?h=Ubuntu-5.15.0-91.101=1dcafa2582f335f0d929f3e9e736775a95271c43 https://bugs.launchpad.net/bugs/2029401 This causes creation of ip6tnl tunnel interface to fail through systemd-networkd. The following systemd commit also has to be applied to jammy: https://github.com/systemd/systemd/commit/3be64aa462642de9fbe9f95536f8d167c19994bb (Other commits might be required along with above) Since the systemd commit is missing on jammy, Kind=ip6tnl netdev configuration fails as follows: > eno1: Could not create stacked netdev: Invalid argument I believe this is a regression; We encountered this linux- image-5.15.0-91-generic installed via unattended-upgrade -- Also EINVAL during creating tunnel interfaces let AcceptIPv6RA function not to start, so we lose connection to our server due to missing IP address. ``` # eno1.network [Match] Name=eno1 [Network] Tunnel=test_tun ``` ``` # test_tun.netdev [NetDev] Name=test_tun Kind=ip6tnl [Tunnel] Local=2001:db8::a Remote=2001:db8::b Mode=any ``` ``` # test_tun.network [Match] Name=test_tun [Network] Address=10.0.0.1/24 ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049234/+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 1786013] Autopkgtest regression report (linux-meta-nvidia-6.5/6.5.0.1010.11)
All autopkgtests for the newly accepted linux-meta-nvidia-6.5 (6.5.0.1010.11) for jammy have finished running. The following regressions have been reported in tests triggered by the package: linux-nvidia-6.5/6.5.0-1010.10 (arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#linux-meta-nvidia-6.5 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packaging resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+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 2042426] Re: Introduce the new NVIDIA 545 driver series
** Package changed: nvidia-graphics-drivers-535 (Ubuntu) => nvidia- graphics-drivers-545 (Ubuntu) ** Changed in: nvidia-graphics-drivers-545 (Ubuntu) Status: In Progress => Fix Released ** Changed in: nvidia-graphics-drivers-545 (Ubuntu Lunar) Status: In Progress => Won't Fix ** Changed in: nvidia-graphics-drivers-545 (Ubuntu Mantic) Status: In Progress => Fix Committed ** Changed in: nvidia-graphics-drivers-545 (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-535 in Ubuntu. https://bugs.launchpad.net/bugs/2042426 Title: Introduce the new NVIDIA 545 driver series Status in nvidia-graphics-drivers-545 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-545 source package in Jammy: Fix Committed Status in nvidia-graphics-drivers-545 source package in Lunar: Won't Fix Status in nvidia-graphics-drivers-545 source package in Mantic: Fix Committed Bug description: Introduce the new NVIDIA 545 driver series. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-545/+bug/2042426/+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 2049444] Re: mintupdate newest kernel in /boot/vmlinuz-6.5.0-14-generic wont' boot
** Package changed: ubuntu => linux-hwe-6.5 (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2049444 Title: mintupdate newest kernel in /boot/vmlinuz-6.5.0-14-generic wont' boot Status in linux-hwe-6.5 package in Ubuntu: New Bug description: I booted a new kernel from /@/boot/vmlinuz-6.5.0-14-generic in grub.cfg: see below for what took 30 secs to cycle from: [1] ata1.00: configured for UDMA/133 snip [31] ata1.00: configured for UDMA/100 snip [61] ata1.00: configured for UDMA/66 snip [91] ata1.00: configured for PIO4 DOWN to PIO0. THEN I POWERED OFF Then in grub I chose 6.2.0-37-generic recovery (2nd choice): this is a successful boot by using a older kernel. My dmesg reads info about a boot that measures sda3 speed: [1.754905] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [1.758397] ata1.00: ACPI cmd f5/00:00:00:00:00:00(SECURITY FREEZE LOCK) filtered out [1.758491] ata1.00: ACPI cmd b1/c1:00:00:00:00:00(DEVICE CONFIGURATION OVERLAY) filtered out [1.758816] ata1.00: ACPI cmd 00/00:00:00:00:00:a0(NOP) rejected by device (Stat=0x51 Err=0x04) [1.761007] ata1.00: ATA-8: WDC WD3200BEKT-75PVMT0, 01.01A01, max UDMA/133 [1.762103] ata1.00: 625142448 sectors, multi 16: LBA48 NCQ (depth 32), AA [1.765817] ata1.00: ACPI cmd f5/00:00:00:00:00:00(SECURITY FREEZE LOCK) filtered out [1.765908] ata1.00: ACPI cmd b1/c1:00:00:00:00:00(DEVICE CONFIGURATION OVERLAY) filtered out [1.766265] ata1.00: ACPI cmd 00/00:00:00:00:00:a0(NOP) rejected by device (Stat=0x51 Err=0x04) [1.768698] ata1.00: configured for UDMA/133 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.5/+bug/2049444/+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 2049444] [NEW] mintupdate newest kernel in /boot/vmlinuz-6.5.0-14-generic wont' boot
You have been subscribed to a public bug: I booted a new kernel from /@/boot/vmlinuz-6.5.0-14-generic in grub.cfg: see below for what took 30 secs to cycle from: [1] ata1.00: configured for UDMA/133 snip [31] ata1.00: configured for UDMA/100 snip [61] ata1.00: configured for UDMA/66 snip [91] ata1.00: configured for PIO4 DOWN to PIO0. THEN I POWERED OFF Then in grub I chose 6.2.0-37-generic recovery (2nd choice): this is a successful boot by using a older kernel. My dmesg reads info about a boot that measures sda3 speed: [1.754905] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [1.758397] ata1.00: ACPI cmd f5/00:00:00:00:00:00(SECURITY FREEZE LOCK) filtered out [1.758491] ata1.00: ACPI cmd b1/c1:00:00:00:00:00(DEVICE CONFIGURATION OVERLAY) filtered out [1.758816] ata1.00: ACPI cmd 00/00:00:00:00:00:a0(NOP) rejected by device (Stat=0x51 Err=0x04) [1.761007] ata1.00: ATA-8: WDC WD3200BEKT-75PVMT0, 01.01A01, max UDMA/133 [1.762103] ata1.00: 625142448 sectors, multi 16: LBA48 NCQ (depth 32), AA [1.765817] ata1.00: ACPI cmd f5/00:00:00:00:00:00(SECURITY FREEZE LOCK) filtered out [1.765908] ata1.00: ACPI cmd b1/c1:00:00:00:00:00(DEVICE CONFIGURATION OVERLAY) filtered out [1.766265] ata1.00: ACPI cmd 00/00:00:00:00:00:a0(NOP) rejected by device (Stat=0x51 Err=0x04) [1.768698] ata1.00: configured for UDMA/133 ** Affects: linux-hwe-6.5 (Ubuntu) Importance: Undecided Status: New ** Tags: 6.5.0-14-generic kernel mint21.3 -- mintupdate newest kernel in /boot/vmlinuz-6.5.0-14-generic wont' boot https://bugs.launchpad.net/bugs/2049444 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.5 in Ubuntu. -- 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 2049327] Re: `alsactl init` unable to initialze audio device on G700
Thanks, I've uploaded to N/M/J now after adding the bug reference to the changelog (please try to think about doing that next time), I don't think it makes sense to SRU to Lunar at this point unless you had an explicit need for it? I've also changed the J version to be .10 instead of .9 but let me know if there was a reason you did skip one revision -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/2049327 Title: `alsactl init` unable to initialze audio device on G700 Status in alsa-ucm-conf package in Ubuntu: Fix Committed Bug description: [Impact] This bug cause "alsactl init" command unable to initialize mt8390-evk correctly and print these error message: ``` ceqa@ubuntu:/home/ceqa$ alsactl init alsa-lib main.c:761:(execute_sequence) unable to execute cset 'name='DP_OUT_MUX' Disconnect' alsa-lib main.c:2373:(set_boot_user) Unable to execute boot sequence Found hardware: "mt8390-evk" "" "" "" "" Hardware is initialized using a generic method ``` Thus, the audio devices on MediaTek G700 do not work. This patch fix this bug by correcting 'DP_OUT_MUX' to 'DPTX_OUT_MUX'. [ Test Plan ] Reproduce: 1. Install Ubuntu 22.04 (jammy) on a MediaTek G700 device 2. Run `alsactl init` on MediaTek G700 device 3. alsactl print error message "unable to execute cset 'name='DP_OUT_MUX' Disconnect'" and audio devices do not work. Verify: By applying this patch, alsactl does not print this error message and audio devices work. [Where problems could occur] This patch fix the typo in ucm files, and it affects the device init process on Mediatek Genio boards. [ Other Info ] There is a typo in 'd/p/0001-Add-initial-support-for-MediaTek-Genio-boards.patch'. The name of the flag that controls the audio output of the DP port is not 'DP_OUT_MUX'. It is 'DPTX_OUT_MUX'. MediaTek fix this issue in the PR in upstream: https://github.com/alsa-project/alsa-ucm-conf/compare/243f2d60740e41a0cfb7779388c17e4a00e1bfe9..a55f840ab2b13f32cb55cd1730933ef0f5a96079 mt8390-evk (G700) Pull Request: (Still under review) https://github.com/alsa-project/alsa-ucm-conf/pull/321 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/2049327/+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 2048919] Comment bridged from LTC Bugzilla
--- Comment From boris.m...@de.ibm.com 2024-01-16 05:23 EDT--- @Canonical: Thanks a lot, especially to Frank and the kernel team for your extra effort providing a fixed version instantly. Highly appreciated! -- 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/2048919 Title: [UBUNTU 23.04] Regression: Ubuntu 23.04/23.10 do not include uvdevice anymore Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in linux source package in Lunar: Won't Fix Status in linux source package in Mantic: Fix Committed Status in linux source package in Noble: Fix Committed Bug description: ---Problem Description--- Regression: uvdevice at /dev/uv not compiled into kernel Machine Type = IBM z15, IBM z16 Contact Information = steffen.ei...@ibm.com ---uname output--- Linux 6.5.0-14-generic #14-Ubuntu SMP Tue Nov 14 14:16:58 UTC 2023 s390x s390x s390x GNU/Linux ---Debugger--- A debugger is not configured ---Additional Hardware Info--- Secure Execution feature code enabled (optional) ---Steps to Reproduce--- # working/ old behavior on a fresh ubuntu 22.10 (and 22.04) LPAR/guest1 (with Secure execution available) > cat /dev/uv /dev/uv > cat /boot/config-$(uname -r) | grep UV_UAPI CONFIG_S390_UV_UAPI=y that's the expected state for Ubuntu. # current/ non expected behavior since Ubuntu 23.04 the following happens: stock kernel non-modified, latest available > cat /dev/uv cat: /dev/uv: No such file or directory COMMENT: this still can happen if the machine has no Secure Execution feature available However, the following should not be the case under any circumstances: > cat /boot/config-$(uname -r) | grep UV_UAPI # CONFIG_S390_UV_UAPI is not set Somehow that configuration got lost between 22.X and 23.X. Maybe, because IIRC that features got back-ported to 22.X # Proposed Solution: change the kernel config to CONFIG_S390_UV_UAPI=y(same as 22.X backport) or CONFIG_S390_UV_UAPI=m(same as upstream) and provide a new kernel binary Stack trace output: n/a System Dump Info: The system is not configured to capture a system dump. Oops output: n/a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2048919/+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 2049327] Re: `alsactl init` unable to initialze audio device on G700
** Changed in: alsa-ucm-conf (Ubuntu) Status: New => Fix Committed ** Changed in: alsa-ucm-conf (Ubuntu) Importance: Undecided => High ** Changed in: alsa-ucm-conf (Ubuntu) Assignee: (unassigned) => Zhaoxuan Zhai (kxuan) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/2049327 Title: `alsactl init` unable to initialze audio device on G700 Status in alsa-ucm-conf package in Ubuntu: Fix Committed Bug description: [Impact] This bug cause "alsactl init" command unable to initialize mt8390-evk correctly and print these error message: ``` ceqa@ubuntu:/home/ceqa$ alsactl init alsa-lib main.c:761:(execute_sequence) unable to execute cset 'name='DP_OUT_MUX' Disconnect' alsa-lib main.c:2373:(set_boot_user) Unable to execute boot sequence Found hardware: "mt8390-evk" "" "" "" "" Hardware is initialized using a generic method ``` Thus, the audio devices on MediaTek G700 do not work. This patch fix this bug by correcting 'DP_OUT_MUX' to 'DPTX_OUT_MUX'. [ Test Plan ] Reproduce: 1. Install Ubuntu 22.04 (jammy) on a MediaTek G700 device 2. Run `alsactl init` on MediaTek G700 device 3. alsactl print error message "unable to execute cset 'name='DP_OUT_MUX' Disconnect'" and audio devices do not work. Verify: By applying this patch, alsactl does not print this error message and audio devices work. [Where problems could occur] This patch fix the typo in ucm files, and it affects the device init process on Mediatek Genio boards. [ Other Info ] There is a typo in 'd/p/0001-Add-initial-support-for-MediaTek-Genio-boards.patch'. The name of the flag that controls the audio output of the DP port is not 'DP_OUT_MUX'. It is 'DPTX_OUT_MUX'. MediaTek fix this issue in the PR in upstream: https://github.com/alsa-project/alsa-ucm-conf/compare/243f2d60740e41a0cfb7779388c17e4a00e1bfe9..a55f840ab2b13f32cb55cd1730933ef0f5a96079 mt8390-evk (G700) Pull Request: (Still under review) https://github.com/alsa-project/alsa-ucm-conf/pull/321 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/2049327/+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 2048919] Re: [UBUNTU 23.04] Regression: Ubuntu 23.04/23.10 do not include uvdevice anymore
** Tags removed: targetmilestone-inin--- ** Tags added: targetmilestone-inin2310 -- 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/2048919 Title: [UBUNTU 23.04] Regression: Ubuntu 23.04/23.10 do not include uvdevice anymore Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in linux source package in Lunar: Won't Fix Status in linux source package in Mantic: Fix Committed Status in linux source package in Noble: Fix Committed Bug description: ---Problem Description--- Regression: uvdevice at /dev/uv not compiled into kernel Machine Type = IBM z15, IBM z16 Contact Information = steffen.ei...@ibm.com ---uname output--- Linux 6.5.0-14-generic #14-Ubuntu SMP Tue Nov 14 14:16:58 UTC 2023 s390x s390x s390x GNU/Linux ---Debugger--- A debugger is not configured ---Additional Hardware Info--- Secure Execution feature code enabled (optional) ---Steps to Reproduce--- # working/ old behavior on a fresh ubuntu 22.10 (and 22.04) LPAR/guest1 (with Secure execution available) > cat /dev/uv /dev/uv > cat /boot/config-$(uname -r) | grep UV_UAPI CONFIG_S390_UV_UAPI=y that's the expected state for Ubuntu. # current/ non expected behavior since Ubuntu 23.04 the following happens: stock kernel non-modified, latest available > cat /dev/uv cat: /dev/uv: No such file or directory COMMENT: this still can happen if the machine has no Secure Execution feature available However, the following should not be the case under any circumstances: > cat /boot/config-$(uname -r) | grep UV_UAPI # CONFIG_S390_UV_UAPI is not set Somehow that configuration got lost between 22.X and 23.X. Maybe, because IIRC that features got back-ported to 22.X # Proposed Solution: change the kernel config to CONFIG_S390_UV_UAPI=y(same as 22.X backport) or CONFIG_S390_UV_UAPI=m(same as upstream) and provide a new kernel binary Stack trace output: n/a System Dump Info: The system is not configured to capture a system dump. Oops output: n/a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2048919/+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 2049220] Re: Update firmware for MT7921 in order to fix Framework 13 AMD 7040
As per https://bugs.launchpad.net/bugs/2049303 - another workaround for Ubuntu 22.04.3 LTS is switching to the 6.2 HWE Kernel. For me, I noticed the issue after my system got updated from the 6.2 HWE kernel to the 6.5 HWE Kernel. Rebooting the system back to the previous 6.2 HWE Kernel resolved the problem. Note that both kernel images leverage the same firmware version as that's provided via the linux-firmware package: mt7921e :05:00.0: WM Firmware Version: 01, Build Time: 20220209150915 So something specific with the 6.5 HWE Kernel module mt7921e in combination with this specific firmware version breaks multicast. Seen that updating the firmware image resolves the issue, it points to a bug in the firmware and not the kernel module. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2049220 Title: Update firmware for MT7921 in order to fix Framework 13 AMD 7040 Status in linux-firmware package in Ubuntu: In Progress Status in linux-firmware source package in Jammy: In Progress Status in linux-firmware source package in Mantic: In Progress Status in linux-firmware source package in Noble: In Progress Bug description: The current firmware for MT7921 WiFi is giving me problems like dropping multicast packets (mDNS). I manually updated the firmware files and that fixed the issue. To be more specific, please include this commit: https://gitlab.com/kernel-firmware/linux-firmware/-/commit/0a18a7292a66532633d9586521f0b954c68a9fbc And possibly also this: https://gitlab.com/kernel-firmware/linux-firmware/-/commit/1366b827c21351b37665303397e161dd4158316e Thanks! We also need: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Ubuntu 22.04.3 LTS 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center ii linux-firmware 20220329.git681281e4-0ubuntu3.24 all Firmware for Linux kernel drivers 3) What you expected to happen WiFi working 4) What happened instead Multicast packets dropped, mDNS not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2049220/+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 2049303] Re: MT7921 - IPv6 no longer working (Not receiving Multicast)
*** This bug is a duplicate of bug 2049220 *** https://bugs.launchpad.net/bugs/2049220 ** This bug has been marked a duplicate of bug 2049220 Update firmware for MT7921 in order to fix Framework 13 AMD 7040 -- 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/2049303 Title: MT7921 - IPv6 no longer working (Not receiving Multicast) Status in linux-signed-hwe-6.5 package in Ubuntu: New Bug description: After updating to kernel linux-image-6.5.0-14-generic, IPv6 stopped working with the MT7921 wifi card. No errors are logged, but when using tcpdump / wireshark to capture traffic, I can see the MT7921 card no longer appears to receive IPv6 Multicast (thus it never receives the Router Advertisements, etc.). Booting back to the previous kernel image (linux- image-6.2.0-39-generic) resolves the issue and IPv6 Multicast works fine and IPv6 connectivity works fine again. The system is configured to use the 22.04 HWE kernel to better support the AMD Advantage Platform hardware (ASUS ROG Strix G513QY). Steps to reproduce: 1. Have Ubuntu 22.04 LTS installed on a laptop with MT7921 Wifi adapter and connect it to a Dual-stack network leveraging Router Advertisements for IPv6. 2. Run it with HWE Kernel image linux-image-6.2.0-39-generic and observe the following: - IPv6 stateless autoconfiguration works and a public/global address is assigned. - Inbound IPv6 Multicast packets are seen when using tcpdump/wireshark. 3. Update the HWE Kernel to linux-image-6.5.0-14-generic and observe the following: - IPv6 only configures link-local address (fe80::) and no public/global address. - No inbound IPv6 multicast packets are seen when using tcpdump/wireshark. fludizz@pauwel:~$ lsb_release -rd Description: Ubuntu 22.04.3 LTS Release: 22.04 Network card in question: 05:00.0 Network controller: MEDIATEK Corp. MT7921 802.11ax PCI Express Wireless Network Adapter Subsystem: AzureWave Device 4680 Flags: bus master, fast devsel, latency 0, IRQ 83, IOMMU group 14 Memory at fc3030 (64-bit, prefetchable) [size=1M] Memory at fc3040 (64-bit, prefetchable) [size=16K] Memory at fc30404000 (64-bit, prefetchable) [size=4K] Capabilities: [80] Express Endpoint, MSI 00 Capabilities: [e0] MSI: Enable+ Count=1/32 Maskable+ 64bit+ Capabilities: [f8] Power Management version 3 Capabilities: [100] Vendor Specific Information: ID=1556 Rev=1 Len=008 Capabilities: [108] Latency Tolerance Reporting Capabilities: [110] L1 PM Substates Capabilities: [200] Advanced Error Reporting Kernel driver in use: mt7921e Kernel modules: mt7921e fludizz@pauwel:~$ apt-cache policy linux-image-6.5.0-14-generic linux-image-6.5.0-14-generic: Installed: 6.5.0-14.14~22.04.1 Candidate: 6.5.0-14.14~22.04.1 Version table: *** 6.5.0-14.14~22.04.1 500 500 http://nl.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 100 /var/lib/dpkg/status Note: The WiFi device is using the same firmware version on both kernels. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2049303/+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 2049220] Re: Update firmware for MT7921 in order to fix Framework 13 AMD 7040
** Tags added: kern-8926 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2049220 Title: Update firmware for MT7921 in order to fix Framework 13 AMD 7040 Status in linux-firmware package in Ubuntu: In Progress Status in linux-firmware source package in Jammy: In Progress Status in linux-firmware source package in Mantic: In Progress Status in linux-firmware source package in Noble: In Progress Bug description: The current firmware for MT7921 WiFi is giving me problems like dropping multicast packets (mDNS). I manually updated the firmware files and that fixed the issue. To be more specific, please include this commit: https://gitlab.com/kernel-firmware/linux-firmware/-/commit/0a18a7292a66532633d9586521f0b954c68a9fbc And possibly also this: https://gitlab.com/kernel-firmware/linux-firmware/-/commit/1366b827c21351b37665303397e161dd4158316e Thanks! We also need: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Ubuntu 22.04.3 LTS 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center ii linux-firmware 20220329.git681281e4-0ubuntu3.24 all Firmware for Linux kernel drivers 3) What you expected to happen WiFi working 4) What happened instead Multicast packets dropped, mDNS not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2049220/+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 2049195] Re: Wifi missing after upgrade to 6.5 kernel
** Tags added: kern-8925 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2049195 Title: Wifi missing after upgrade to 6.5 kernel Status in linux-meta-hwe-6.5 package in Ubuntu: New Bug description: After upgrading the HWE kernel from 6.2 to 6.5 the wifi interface is missing. Hardware: Framework Laptop $ lspci | grep Network aa:00.0 Network controller: Intel Corporation Wi-Fi 6 AX210/AX211/AX411 160MHz (rev 1a) With 6.2: $ sudo ethtool -i wlp170s0 driver: iwlwifi version: 6.2.0-39-generic firmware-version: 72.a764baac.0 ty-a0-gf-a0-72.uc Messages from journalctl that seem relevant: Jan 12 12:21:25 fw1 kernel: iwlwifi :aa:00.0: Detected Intel(R) Wi-Fi 6 AX210 160MHz, REV=0x420 Jan 12 12:21:25 fw1 kernel: iwlwifi :aa:00.0: WRT: Invalid buffer destination and then some backtraces, result of journalctl -b-1 | grep "kernel: " > kernel-log.txt attached. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-generic-hwe-22.04 6.5.0.14.14~22.04.7 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jan 12 12:32:19 2024 InstallationDate: Installed on 2022-06-29 (561 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-meta-hwe-6.5 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-6.5/+bug/2049195/+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 2048919] Re: [UBUNTU 23.04] Regression: Ubuntu 23.04/23.10 do not include uvdevice anymore
Thx for the prompt verification! -- 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/2048919 Title: [UBUNTU 23.04] Regression: Ubuntu 23.04/23.10 do not include uvdevice anymore Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in linux source package in Lunar: Won't Fix Status in linux source package in Mantic: Fix Committed Status in linux source package in Noble: Fix Committed Bug description: ---Problem Description--- Regression: uvdevice at /dev/uv not compiled into kernel Machine Type = IBM z15, IBM z16 Contact Information = steffen.ei...@ibm.com ---uname output--- Linux 6.5.0-14-generic #14-Ubuntu SMP Tue Nov 14 14:16:58 UTC 2023 s390x s390x s390x GNU/Linux ---Debugger--- A debugger is not configured ---Additional Hardware Info--- Secure Execution feature code enabled (optional) ---Steps to Reproduce--- # working/ old behavior on a fresh ubuntu 22.10 (and 22.04) LPAR/guest1 (with Secure execution available) > cat /dev/uv /dev/uv > cat /boot/config-$(uname -r) | grep UV_UAPI CONFIG_S390_UV_UAPI=y that's the expected state for Ubuntu. # current/ non expected behavior since Ubuntu 23.04 the following happens: stock kernel non-modified, latest available > cat /dev/uv cat: /dev/uv: No such file or directory COMMENT: this still can happen if the machine has no Secure Execution feature available However, the following should not be the case under any circumstances: > cat /boot/config-$(uname -r) | grep UV_UAPI # CONFIG_S390_UV_UAPI is not set Somehow that configuration got lost between 22.X and 23.X. Maybe, because IIRC that features got back-ported to 22.X # Proposed Solution: change the kernel config to CONFIG_S390_UV_UAPI=y(same as 22.X backport) or CONFIG_S390_UV_UAPI=m(same as upstream) and provide a new kernel binary Stack trace output: n/a System Dump Info: The system is not configured to capture a system dump. Oops output: n/a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2048919/+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 1786013] Autopkgtest regression report (linux-meta-bluefield/5.4.0.1078.73)
All autopkgtests for the newly accepted linux-meta-bluefield (5.4.0.1078.73) for focal have finished running. The following regressions have been reported in tests triggered by the package: acpi-call/unknown (arm64) adv-17v35x/unknown (arm64) bbswitch/unknown (arm64) ddcci-driver-linux/unknown (arm64) dm-writeboost/unknown (arm64) dpdk/unknown (arm64) fwts/unknown (arm64) glibc/unknown (arm64) gost-crypto/unknown (arm64) iptables-netflow/unknown (arm64) jool/unknown (arm64) langford/unknown (arm64) lime-forensics/unknown (arm64) linux-bluefield/unknown (arm64) lttng-modules/unknown (arm64) lxc/unknown (arm64) mali-midgard/unknown (arm64) nat-rtsp/unknown (arm64) openafs/unknown (arm64) openrazer/unknown (arm64) r8168/unknown (arm64) snapd/unknown (arm64) west-chamber/unknown (arm64) wireguard-linux-compat/unknown (arm64) xtables-addons/unknown (arm64) zfs-linux/unknown (arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-meta-bluefield [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packaging resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+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 2049496] Re: Jammy update: v6.1.73 upstream stable release
** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: New => Fix Committed ** Changed in: linux-oem-6.1 (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2049496 Title: Jammy update: v6.1.73 upstream stable release Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.1.73 upstream stable release from git://git.kernel.org/ Linux 6.1.73 cifs: fix flushing folio regression for 6.1 backport ipv6: remove max_size check inline with ipv4 Revert "nfsd: separate nfsd_last_thread() from nfsd_put()" Revert "nfsd: call nfsd_last_thread() before final nfsd_put()" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.1/+bug/2049496/+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 2049496] [NEW] Jammy update: v6.1.73 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.1.73 upstream stable release from git://git.kernel.org/ Linux 6.1.73 cifs: fix flushing folio regression for 6.1 backport ipv6: remove max_size check inline with ipv4 Revert "nfsd: separate nfsd_last_thread() from nfsd_put()" Revert "nfsd: call nfsd_last_thread() before final nfsd_put()" ** Affects: linux-oem-6.1 (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux-oem-6.1 (Ubuntu Jammy) Importance: Undecided Status: New ** Tags: kernel-stable-tracking-bug ** Changed in: linux-oem-6.1 (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux-oem-6.1 (Ubuntu Jammy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2049496 Title: Jammy update: v6.1.73 upstream stable release Status in linux-oem-6.1 package in Ubuntu: Confirmed Status in linux-oem-6.1 source package in Jammy: New Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.1.73 upstream stable release from git://git.kernel.org/ Linux 6.1.73 cifs: fix flushing folio regression for 6.1 backport ipv6: remove max_size check inline with ipv4 Revert "nfsd: separate nfsd_last_thread() from nfsd_put()" Revert "nfsd: call nfsd_last_thread() before final nfsd_put()" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.1/+bug/2049496/+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 2048919] Comment bridged from LTC Bugzilla
--- Comment From fran...@de.ibm.com 2024-01-16 03:12 EDT--- uvdevice is in linux-image-6.5.0-17-generic # dpkg --list | grep linux-image ii linux-image-6.5.0-17-generic 6.5.0-17.17 s390xSigned kernel image generic # uname -r 6.5.0-17-generic cat /boot/config-$(uname -r) | grep UV_UAPI CONFIG_S390_UV_UAPI=y # ls /dev/uv /dev/uv -- 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/2048919 Title: [UBUNTU 23.04] Regression: Ubuntu 23.04/23.10 do not include uvdevice anymore Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in linux source package in Lunar: Won't Fix Status in linux source package in Mantic: Fix Committed Status in linux source package in Noble: Fix Committed Bug description: ---Problem Description--- Regression: uvdevice at /dev/uv not compiled into kernel Machine Type = IBM z15, IBM z16 Contact Information = steffen.ei...@ibm.com ---uname output--- Linux 6.5.0-14-generic #14-Ubuntu SMP Tue Nov 14 14:16:58 UTC 2023 s390x s390x s390x GNU/Linux ---Debugger--- A debugger is not configured ---Additional Hardware Info--- Secure Execution feature code enabled (optional) ---Steps to Reproduce--- # working/ old behavior on a fresh ubuntu 22.10 (and 22.04) LPAR/guest1 (with Secure execution available) > cat /dev/uv /dev/uv > cat /boot/config-$(uname -r) | grep UV_UAPI CONFIG_S390_UV_UAPI=y that's the expected state for Ubuntu. # current/ non expected behavior since Ubuntu 23.04 the following happens: stock kernel non-modified, latest available > cat /dev/uv cat: /dev/uv: No such file or directory COMMENT: this still can happen if the machine has no Secure Execution feature available However, the following should not be the case under any circumstances: > cat /boot/config-$(uname -r) | grep UV_UAPI # CONFIG_S390_UV_UAPI is not set Somehow that configuration got lost between 22.X and 23.X. Maybe, because IIRC that features got back-ported to 22.X # Proposed Solution: change the kernel config to CONFIG_S390_UV_UAPI=y(same as 22.X backport) or CONFIG_S390_UV_UAPI=m(same as upstream) and provide a new kernel binary Stack trace output: n/a System Dump Info: The system is not configured to capture a system dump. Oops output: n/a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2048919/+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 2049492] [NEW] package linux-image-6.5.0-14-generic 6.5.0-14.14~22.04.1 failed to install/upgrade: linux-image-6.5.0-14-generic paketi pre-removal betiği kuruldu alt süreci 1 ha
Public bug reported: nvidia-driver-390 dkms cerate err ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-14-generic 6.5.0-14.14~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Mon Jan 15 11:31:10 2024 ErrorMessage: linux-image-6.5.0-14-generic paketi pre-removal betiği kuruldu alt süreci 1 hatalı çıkış kodu ile sona erdi InstallationDate: Installed on 2023-12-14 (33 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.11 SourcePackage: linux-signed-hwe-6.5 Title: package linux-image-6.5.0-14-generic 6.5.0-14.14~22.04.1 failed to install/upgrade: linux-image-6.5.0-14-generic paketi pre-removal betiği kuruldu alt süreci 1 hatalı çıkış kodu ile sona erdi UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-6.5 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- 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/2049492 Title: package linux-image-6.5.0-14-generic 6.5.0-14.14~22.04.1 failed to install/upgrade: linux-image-6.5.0-14-generic paketi pre-removal betiği kuruldu alt süreci 1 hatalı çıkış kodu ile sona erdi Status in linux-signed-hwe-6.5 package in Ubuntu: New Bug description: nvidia-driver-390 dkms cerate err ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-14-generic 6.5.0-14.14~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Mon Jan 15 11:31:10 2024 ErrorMessage: linux-image-6.5.0-14-generic paketi pre-removal betiği kuruldu alt süreci 1 hatalı çıkış kodu ile sona erdi InstallationDate: Installed on 2023-12-14 (33 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.11 SourcePackage: linux-signed-hwe-6.5 Title: package linux-image-6.5.0-14-generic 6.5.0-14.14~22.04.1 failed to install/upgrade: linux-image-6.5.0-14-generic paketi pre-removal betiği kuruldu alt süreci 1 hatalı çıkış kodu ile sona erdi UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2049492/+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 2048919] Re: [UBUNTU 23.04] Regression: Ubuntu 23.04/23.10 do not include uvdevice anymore
** Tags removed: verification-needed-mantic-linux -- 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/2048919 Title: [UBUNTU 23.04] Regression: Ubuntu 23.04/23.10 do not include uvdevice anymore Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in linux source package in Lunar: Won't Fix Status in linux source package in Mantic: Fix Committed Status in linux source package in Noble: Fix Committed Bug description: ---Problem Description--- Regression: uvdevice at /dev/uv not compiled into kernel Machine Type = IBM z15, IBM z16 Contact Information = steffen.ei...@ibm.com ---uname output--- Linux 6.5.0-14-generic #14-Ubuntu SMP Tue Nov 14 14:16:58 UTC 2023 s390x s390x s390x GNU/Linux ---Debugger--- A debugger is not configured ---Additional Hardware Info--- Secure Execution feature code enabled (optional) ---Steps to Reproduce--- # working/ old behavior on a fresh ubuntu 22.10 (and 22.04) LPAR/guest1 (with Secure execution available) > cat /dev/uv /dev/uv > cat /boot/config-$(uname -r) | grep UV_UAPI CONFIG_S390_UV_UAPI=y that's the expected state for Ubuntu. # current/ non expected behavior since Ubuntu 23.04 the following happens: stock kernel non-modified, latest available > cat /dev/uv cat: /dev/uv: No such file or directory COMMENT: this still can happen if the machine has no Secure Execution feature available However, the following should not be the case under any circumstances: > cat /boot/config-$(uname -r) | grep UV_UAPI # CONFIG_S390_UV_UAPI is not set Somehow that configuration got lost between 22.X and 23.X. Maybe, because IIRC that features got back-ported to 22.X # Proposed Solution: change the kernel config to CONFIG_S390_UV_UAPI=y(same as 22.X backport) or CONFIG_S390_UV_UAPI=m(same as upstream) and provide a new kernel binary Stack trace output: n/a System Dump Info: The system is not configured to capture a system dump. Oops output: n/a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2048919/+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 2049352] Re: Package BlueZ 5.72 for Noble
** Attachment added: "bluez_5.72-0ubuntu1.debian.tar.xz" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2049352/+attachment/5739878/+files/bluez_5.72-0ubuntu1.debian.tar.xz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2049352 Title: Package BlueZ 5.72 for Noble Status in bluez package in Ubuntu: In Progress Bug description: ver 5.72: Fix issue with BAP and handling stream IO linking. Fix issue with BAP and setup of multiple streams per endpoint. Fix issue with AVDTP and potential incorrect transaction label. Fix issue with A2DP and handling crash on suspend. Fix issue with GATT database and an invalid pointer. Add support for AICS service. https://mirrors.edge.kernel.org/pub/linux/bluetooth/bluez-5.72.tar.xz https://git.kernel.org/pub/scm/bluetooth/bluez.git/tag/?h=5.72 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2049352/+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 2049352] Re: Package BlueZ 5.72 for Noble
** Patch added: "bluez_5.72-0ubuntu1.debdiff" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2049352/+attachment/5739879/+files/bluez_5.72-0ubuntu1.debdiff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2049352 Title: Package BlueZ 5.72 for Noble Status in bluez package in Ubuntu: In Progress Bug description: ver 5.72: Fix issue with BAP and handling stream IO linking. Fix issue with BAP and setup of multiple streams per endpoint. Fix issue with AVDTP and potential incorrect transaction label. Fix issue with A2DP and handling crash on suspend. Fix issue with GATT database and an invalid pointer. Add support for AICS service. https://mirrors.edge.kernel.org/pub/linux/bluetooth/bluez-5.72.tar.xz https://git.kernel.org/pub/scm/bluetooth/bluez.git/tag/?h=5.72 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2049352/+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 2049352] Re: Package BlueZ 5.72 for Noble
** Attachment added: "bluez_5.72.orig.tar.xz" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2049352/+attachment/5739877/+files/bluez_5.72.orig.tar.xz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2049352 Title: Package BlueZ 5.72 for Noble Status in bluez package in Ubuntu: In Progress Bug description: ver 5.72: Fix issue with BAP and handling stream IO linking. Fix issue with BAP and setup of multiple streams per endpoint. Fix issue with AVDTP and potential incorrect transaction label. Fix issue with A2DP and handling crash on suspend. Fix issue with GATT database and an invalid pointer. Add support for AICS service. https://mirrors.edge.kernel.org/pub/linux/bluetooth/bluez-5.72.tar.xz https://git.kernel.org/pub/scm/bluetooth/bluez.git/tag/?h=5.72 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2049352/+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 2049327] Re: `alsactl init` unable to initialze audio device on G700
Here is a debdiff for noble. Thank you! @seb128 @ethan.hsieh ** Patch added: "debdiff_alsa-ucm-conf_noble_from_1.2.10-1ubuntu1_to_1.2.10-1ubuntu2.debdiff" https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/2049327/+attachment/5739852/+files/debdiff_alsa-ucm-conf_noble_from_1.2.10-1ubuntu1_to_1.2.10-1ubuntu2.debdiff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/2049327 Title: `alsactl init` unable to initialze audio device on G700 Status in alsa-ucm-conf package in Ubuntu: New Bug description: [Impact] This bug cause "alsactl init" command unable to initialize mt8390-evk correctly and print these error message: ``` ceqa@ubuntu:/home/ceqa$ alsactl init alsa-lib main.c:761:(execute_sequence) unable to execute cset 'name='DP_OUT_MUX' Disconnect' alsa-lib main.c:2373:(set_boot_user) Unable to execute boot sequence Found hardware: "mt8390-evk" "" "" "" "" Hardware is initialized using a generic method ``` Thus, the audio devices on MediaTek G700 do not work. This patch fix this bug by correcting 'DP_OUT_MUX' to 'DPTX_OUT_MUX'. [ Test Plan ] Reproduce: 1. Install Ubuntu 22.04 (jammy) on a MediaTek G700 device 2. Run `alsactl init` on MediaTek G700 device 3. alsactl print error message "unable to execute cset 'name='DP_OUT_MUX' Disconnect'" and audio devices do not work. Verify: By applying this patch, alsactl does not print this error message and audio devices work. [Where problems could occur] This patch fix the typo in ucm files, and it affects the device init process on Mediatek Genio boards. [ Other Info ] There is a typo in 'd/p/0001-Add-initial-support-for-MediaTek-Genio-boards.patch'. The name of the flag that controls the audio output of the DP port is not 'DP_OUT_MUX'. It is 'DPTX_OUT_MUX'. MediaTek fix this issue in the PR in upstream: https://github.com/alsa-project/alsa-ucm-conf/compare/243f2d60740e41a0cfb7779388c17e4a00e1bfe9..a55f840ab2b13f32cb55cd1730933ef0f5a96079 mt8390-evk (G700) Pull Request: (Still under review) https://github.com/alsa-project/alsa-ucm-conf/pull/321 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/2049327/+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
