[Kernel-packages] [Bug 2061940] Re: Some DUTs can't boot up after installing the proposed kernel on Mantic
6.6.x has this in addition commit 3a3bbc6911f57e1c3b4eabf1d098cde7bf7baeb0 Author: Rafael J. Wysocki Date: Tue Sep 19 20:59:53 2023 +0200 thermal: trip: Drop redundant trips check from for_each_thermal_trip() [ Upstream commit a15ffa783ea4210877886c59566a0d20f6b2bc09 ] It is invalid to call for_each_thermal_trip() on an unregistered thermal zone anyway, and as per thermal_zone_device_register_with_trips(), the trips[] table must be present if num_trips is greater than zero for the given thermal zone. Hence, the trips check in for_each_thermal_trip() is redundant and so it can be dropped. Signed-off-by: Rafael J. Wysocki Acked-by: Daniel Lezcano Stable-dep-of: e95fa7404716 ("thermal: gov_power_allocator: avoid inability to reset a cdev") Signed-off-by: Sasha Levin FYI, 6.1 didn't backport any of these, even though e95fa7404716 says "5.13+" -- 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/2061940 Title: Some DUTs can't boot up after installing the proposed kernel on Mantic Status in linux package in Ubuntu: In Progress Bug description: During the SRU testing for 6.5.0.33 kernel, I found some machines freeze at very early stage of booting process. The last messages displayed on the screen are: EFI stub: Loaded initrd from LINUX_EFI_INITRD_MEDIA_GUID device path EFI stub: Measured initrd data into PCR 9 There are no journal logs existed when it boot with the 6.5.0-33 kernel. Here is the list of the impacted machines that I found so far https://certification.canonical.com/hardware/202106-29206/ https://certification.canonical.com/hardware/202106-29207/ https://certification.canonical.com/hardware/201912-27623/ https://certification.canonical.com/hardware/202007-28059/ https://certification.canonical.com/hardware/202103-28762/ https://certification.canonical.com/hardware/202012-28510/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2061940/+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 1980805] Re: Backport packages for 20.04.5 HWE stack
** Changed in: mesa-amber (Ubuntu Focal) Status: Fix Committed => Won't Fix ** Changed in: llvm-toolchain-13 (Ubuntu Focal) Status: Fix Committed => Won't Fix ** Changed in: libdrm (Ubuntu Focal) Status: Fix Committed => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to llvm-toolchain-13 in Ubuntu. https://bugs.launchpad.net/bugs/1980805 Title: Backport packages for 20.04.5 HWE stack Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-13 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in mesa-amber package in Ubuntu: Invalid Status in libdrm source package in Focal: Won't Fix Status in llvm-toolchain-13 source package in Focal: Won't Fix Status in mesa source package in Focal: Won't Fix Status in mesa-amber source package in Focal: Won't Fix Bug description: [Impact] These are needed for 20.04.5 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. [What could go wrong] libdrm: pci-id updates, some minor api updates mesa: a new major release, but we'll pull the final stable release of 22.0.x series, so there shouldn't be any regressions left at that point mesa-amber: forked from mesa 21.3.x, this LTS branch keeps old DRI drivers that were removed from main mesa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1980805/+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 2058179] Re: Kernel 6.8 + zfs-2.2.2: copy_file_range Operation Not Supported
oh, it needs the kernel module to be rebuilt for the fix.. don't think we have time for that anymore before the release. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/2058179 Title: Kernel 6.8 + zfs-2.2.2: copy_file_range Operation Not Supported Status in Native ZFS for Linux: Fix Released Status in systemd package in Ubuntu: Triaged Status in zfs-linux package in Ubuntu: Confirmed Status in systemd source package in Noble: Triaged Status in zfs-linux source package in Noble: Confirmed Bug description: As per https://github.com/openzfs/zfs/issues/15930 ZFS and kernel 6.8 seem to throw EOPNOTSUPP on calling copy_file_range, breaking a multitude of applications. Upcoming noble (24.04) appears to currently include kernel 6.8 and ZFS 2.2.2. One notable issue is when running Root on ZFS: systemd-sysusers will always fail to create users/groups with the error "Failed to backup /etc/{group,passwd}: Operation not supported" due to the call to copy_file_range. To manage notifications about this bug go to: https://bugs.launchpad.net/zfs/+bug/2058179/+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 2058179] Re: Kernel 6.8 + zfs-2.2.2: copy_file_range Operation Not Supported
and a build is available at https://launchpad.net/~john-cabaj/+archive/ubuntu/zfs-splice- fix/+packages feel free to test before it is available in noble -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/2058179 Title: Kernel 6.8 + zfs-2.2.2: copy_file_range Operation Not Supported Status in Native ZFS for Linux: Fix Released Status in systemd package in Ubuntu: Triaged Status in zfs-linux package in Ubuntu: Confirmed Status in systemd source package in Noble: Triaged Status in zfs-linux source package in Noble: Confirmed Bug description: As per https://github.com/openzfs/zfs/issues/15930 ZFS and kernel 6.8 seem to throw EOPNOTSUPP on calling copy_file_range, breaking a multitude of applications. Upcoming noble (24.04) appears to currently include kernel 6.8 and ZFS 2.2.2. One notable issue is when running Root on ZFS: systemd-sysusers will always fail to create users/groups with the error "Failed to backup /etc/{group,passwd}: Operation not supported" due to the call to copy_file_range. To manage notifications about this bug go to: https://bugs.launchpad.net/zfs/+bug/2058179/+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 2058830] Re: vp9 hw decode broken on modern AMD apus, needs amdgpu update
update pending review -- 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/2058830 Title: vp9 hw decode broken on modern AMD apus, needs amdgpu update Status in Linux Firmware: Fix Released Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: Confirmed Status in linux-firmware source package in Mantic: Confirmed Status in linux-firmware source package in Noble: Fix Released Bug description: Current version of amdgpu binaries in linux-firmware shipped with ubuntu 22.04 (jammy) and ubuntu 23.10 (mantic) create various problems when decoding VP9 content with the iGPU on modern AMD mobile processor (rembrant and phoenix, i.e. 6xxxU/H, 7x40U/H and 7x35U/H processor). The issue has been reported and solved upstream: https://gitlab.freedesktop.org/mesa/mesa/-/issues/8044 [EDIT: fixed link] Solution dates to the end of February: https://gitlab.com/kernel- firmware/linux- firmware/-/commit/977332782302476e1c863b09b840f463d0378807 Ubuntu 24.04 already ships the updated binaries and should not be affected. Steps to reproduce: * on an affected system play a VP9 video with hardware decoding Additional links: * https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=977332782302476e1c863b09b840f463d0378807 * https://bugzilla.redhat.com/show_bug.cgi?id=2267714 * https://www.phoronix.com/news/AMDGPU-Firmware-Fixes-VP9 Workaround: * download the amdgpu folder from upstream linux-firmware repos * compress each file with zstd * copy into /lib/firmware/amdgpu * regenerate the initrd I'm currently running ubuntu 23.10 (mantic) with binaries from upstream and the issue is solved. To manage notifications about this bug go to: https://bugs.launchpad.net/linux-firmware/+bug/2058830/+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 2055384] Re: New NVIDIA release 550.54.14
** Changed in: fabric-manager-535 (Ubuntu Bionic) Status: Fix Committed => Fix Released ** Changed in: fabric-manager-535 (Ubuntu Focal) Status: Fix Committed => Fix Released ** Changed in: fabric-manager-535 (Ubuntu Mantic) Status: Fix Committed => Fix Released ** Changed in: fabric-manager-535 (Ubuntu Noble) Status: Fix Committed => Fix Released ** Changed in: libnvidia-nscq-535 (Ubuntu Bionic) Status: Fix Committed => Fix Released ** Changed in: libnvidia-nscq-535 (Ubuntu Focal) Status: Fix Committed => Fix Released ** Changed in: libnvidia-nscq-535 (Ubuntu Jammy) Status: Fix Committed => Fix Released ** Changed in: libnvidia-nscq-535 (Ubuntu Mantic) Status: Fix Committed => Fix Released ** Changed in: libnvidia-nscq-535 (Ubuntu Noble) Status: Fix Committed => Fix Released ** Changed in: nvidia-graphics-drivers-535 (Ubuntu Bionic) Status: Fix Committed => Fix Released ** Changed in: nvidia-graphics-drivers-535 (Ubuntu Focal) Status: Fix Committed => Fix Released ** Changed in: nvidia-graphics-drivers-535 (Ubuntu Jammy) Status: Fix Committed => Fix Released ** Changed in: nvidia-graphics-drivers-535 (Ubuntu Mantic) Status: Fix Committed => Fix Released ** Changed in: nvidia-graphics-drivers-535 (Ubuntu Noble) Status: Fix Committed => Fix Released ** Changed in: nvidia-graphics-drivers-535-server (Ubuntu Bionic) Status: Fix Committed => Fix Released ** Changed in: nvidia-graphics-drivers-535-server (Ubuntu Focal) Status: Fix Committed => Fix Released ** Changed in: nvidia-graphics-drivers-535-server (Ubuntu Jammy) Status: Fix Committed => Fix Released ** Changed in: nvidia-graphics-drivers-535-server (Ubuntu Mantic) Status: Fix Committed => Fix Released ** Changed in: nvidia-graphics-drivers-550-server (Ubuntu Jammy) Status: Fix Committed => Fix Released ** Changed in: nvidia-graphics-drivers-550-server (Ubuntu Mantic) Status: Fix Committed => Fix Released ** Changed in: nvidia-graphics-drivers-535-server (Ubuntu Noble) Status: Fix Committed => 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/2055384 Title: New NVIDIA release 550.54.14 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: Fix Released Status in nvidia-graphics-drivers-535-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-550 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-550-server package in Ubuntu: Fix Released Status in fabric-manager-535 source package in Bionic: Fix Released Status in libnvidia-nscq-535 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-535 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-535-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-550 source package in Bionic: Invalid Status in nvidia-graphics-drivers-550-server source package in Bionic: Invalid Status in fabric-manager-535 source package in Focal: Fix Released Status in libnvidia-nscq-535 source package in Focal: Fix Released Status in nvidia-graphics-drivers-535 source package in Focal: Fix Released Status in nvidia-graphics-drivers-535-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-550 source package in Focal: Invalid Status in nvidia-graphics-drivers-550-server source package in Focal: Invalid Status in fabric-manager-535 source package in Jammy: Fix Released Status in libnvidia-nscq-535 source package in Jammy: Fix Released Status in nvidia-graphics-drivers-535 source package in Jammy: Fix Released Status in nvidia-graphics-drivers-535-server source package in Jammy: Fix Released Status in nvidia-graphics-drivers-550 source package in Jammy: Fix Released Status in nvidia-graphics-drivers-550-server source package in Jammy: Fix Released Status in fabric-manager-535 source package in Mantic: Fix Released Status in libnvidia-nscq-535 source package in Mantic: Fix Released Status in nvidia-graphics-drivers-535 source package in Mantic: Fix Released Status in nvidia-graphics-drivers-535-server source package in Mantic: Fix Released Status in nvidia-graphics-drivers-550 source package in Mantic: Fix Released Status in nvidia-graphics-drivers-550-server source package in Mantic: Fix Released 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: Fix Released Status in nvidia-graphics-drivers-535-server source package in Noble: Fix Released Status in
[Kernel-packages] [Bug 2059115] Re: New upstream release 535.161.08 ERD2
** Summary changed: - New upstream release 550.54.15 ERD2 + New upstream release 535.161.08 ERD2 ** Changed in: fabric-manager-535 (Ubuntu Bionic) Status: Fix Committed => Fix Released ** Changed in: fabric-manager-535 (Ubuntu Focal) Status: Fix Committed => Fix Released ** Changed in: fabric-manager-535 (Ubuntu Jammy) Status: Fix Committed => Fix Released ** Changed in: fabric-manager-535 (Ubuntu Mantic) Status: Fix Committed => Fix Released ** Changed in: fabric-manager-535 (Ubuntu Noble) Status: Fix Committed => Fix Released ** Changed in: libnvidia-nscq-535 (Ubuntu Bionic) Status: Fix Committed => Fix Released ** Changed in: libnvidia-nscq-535 (Ubuntu Focal) Status: Fix Committed => Fix Released ** Changed in: libnvidia-nscq-535 (Ubuntu Jammy) Status: Fix Committed => Fix Released ** Changed in: libnvidia-nscq-535 (Ubuntu Mantic) Status: Fix Committed => Fix Released ** Changed in: libnvidia-nscq-535 (Ubuntu Noble) Status: Fix Committed => Fix Released ** Changed in: nvidia-graphics-drivers-535-server (Ubuntu Bionic) Status: Fix Committed => Fix Released ** Changed in: nvidia-graphics-drivers-535-server (Ubuntu Focal) Status: Fix Committed => Fix Released ** Changed in: nvidia-graphics-drivers-535-server (Ubuntu Jammy) Status: Fix Committed => Fix Released ** Changed in: nvidia-graphics-drivers-535-server (Ubuntu Mantic) Status: Fix Committed => Fix Released ** Changed in: nvidia-graphics-drivers-535-server (Ubuntu Noble) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-535-server in Ubuntu. https://bugs.launchpad.net/bugs/2059115 Title: New upstream release 535.161.08 ERD2 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-server package in Ubuntu: Fix Released Status in fabric-manager-535 source package in Bionic: Fix Released Status in libnvidia-nscq-535 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-535-server source package in Bionic: Fix Released Status in fabric-manager-535 source package in Focal: Fix Released Status in libnvidia-nscq-535 source package in Focal: Fix Released Status in nvidia-graphics-drivers-535-server source package in Focal: Fix Released Status in fabric-manager-535 source package in Jammy: Fix Released Status in libnvidia-nscq-535 source package in Jammy: Fix Released Status in nvidia-graphics-drivers-535-server source package in Jammy: Fix Released Status in fabric-manager-535 source package in Mantic: Fix Released Status in libnvidia-nscq-535 source package in Mantic: Fix Released Status in nvidia-graphics-drivers-535-server source package in Mantic: Fix Released 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-server source package in Noble: Fix Released 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/2059115/+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 2055384] Re: New NVIDIA release 550.54.14
** Changed in: fabric-manager-535 (Ubuntu Jammy) Status: Fix Committed => 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/2055384 Title: New NVIDIA release 550.54.14 Status in fabric-manager-535 package in Ubuntu: Fix Committed Status in libnvidia-nscq-535 package in Ubuntu: Fix Committed Status in nvidia-graphics-drivers-535 package in Ubuntu: Fix Committed Status in nvidia-graphics-drivers-535-server package in Ubuntu: Fix Committed Status in nvidia-graphics-drivers-550 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-550-server package in Ubuntu: Fix Released Status in fabric-manager-535 source package in Bionic: Fix Committed Status in libnvidia-nscq-535 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-535 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-535-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-550 source package in Bionic: Invalid Status in nvidia-graphics-drivers-550-server source package in Bionic: Invalid Status in fabric-manager-535 source package in Focal: Fix Committed Status in libnvidia-nscq-535 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-535 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-535-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-550 source package in Focal: Invalid Status in nvidia-graphics-drivers-550-server source package in Focal: Invalid Status in fabric-manager-535 source package in Jammy: Fix Released Status in libnvidia-nscq-535 source package in Jammy: Fix Committed Status in nvidia-graphics-drivers-535 source package in Jammy: Fix Committed Status in nvidia-graphics-drivers-535-server source package in Jammy: Fix Committed Status in nvidia-graphics-drivers-550 source package in Jammy: Fix Released Status in nvidia-graphics-drivers-550-server source package in Jammy: Fix Committed Status in fabric-manager-535 source package in Mantic: Fix Committed Status in libnvidia-nscq-535 source package in Mantic: Fix Committed Status in nvidia-graphics-drivers-535 source package in Mantic: Fix Committed Status in nvidia-graphics-drivers-535-server source package in Mantic: Fix Committed Status in nvidia-graphics-drivers-550 source package in Mantic: Fix Released Status in nvidia-graphics-drivers-550-server source package in Mantic: Fix Committed Status in fabric-manager-535 source package in Noble: Fix Committed Status in libnvidia-nscq-535 source package in Noble: Fix Committed Status in nvidia-graphics-drivers-535 source package in Noble: Fix Committed Status in nvidia-graphics-drivers-535-server source package in Noble: Fix Committed Status in nvidia-graphics-drivers-550 source package in Noble: Fix Released Status in nvidia-graphics-drivers-550-server source package in Noble: Fix Released 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/2055384/+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 2046315] Re: panel flickering after the i915.psr2 is enabled
** Changed in: linux-oem-6.8 (Ubuntu Noble) Status: New => 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/2046315 Title: panel flickering after the i915.psr2 is enabled Status in HWE Next: New Status in linux package in Ubuntu: Triaged Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux-oem-6.8 package in Ubuntu: Fix Committed Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux-oem-6.8 source package in Jammy: Invalid Status in linux source package in Noble: Triaged Status in linux-oem-6.5 source package in Noble: Invalid Status in linux-oem-6.8 source package in Noble: Fix Committed Bug description: SRU verificaton for Noble and oem-6.8-noble: [Impact] In Dell oem project, we found the graphic is flickering on some machines, finally we narrowed down the issue on (some specific panels + i915.psr2 enabled), and the issue was reported to Intel, Intel fixed the issue in the most recent mainline kernel. Here backporting the patches to Noble kernel. It is hard to backport the patches to mantic and oem-6.5, so we wrote a workaround patch to disable the psr2 for those pannels in the oem-6.5. https://gitlab.freedesktop.org/drm/intel/-/issues/9739 [Fix] cherry-pick 8 patches from mainline kernel [Test] I applied the patches to Noble kernel and built a testing kernel, and Dell validated the testing kernel on those machines, the graphic didn't flicker anymore. I installed the testing kernel on some machines with Intel 13th, 12th 11th and 10th gen cpu, the grahic worked well too. [Where problems could occur] This patchset changes the fast wake settings for some gpu, it is possible to make the graphic flicker, but this possibility is very low, since the patchset comes from mainline kernel and we validated the patchset on different gens of Intel cpus. === BugLink: https://bugs.launchpad.net/bugs/2046315 [Impact] On serveral Dell laptops, the screen often displays garbage or the screen is flicking This PR is just a workaround, the upstream bug is here: https://gitlab.freedesktop.org/drm/intel/-/issues/9739#note_2187863 After the upstream fix this bug with a real fix, I will revert the workaround and backport the real fix to Noble and Jammy oem-kernel. [Fix] There is no real fix so far, ODM recommends to use a workaround to disable PSR2, this is a temp solution, after we get the real fix, we could revert the temp workaround. [Test case] booting with the patched kernel, If the pannel's edid is in the qurik list, the PSR2 will be disabled (checking /sys/kernel/debug/dri/0/i915_edp_psr_status; if the pannel's edid is not in the quirk list, the graphic driver will work as before. [Where problems could occur] It is possible that the temp solution couldn't work, then the screen will still show garbage and the screen is flicking, another possible regression is the screen has no problem before, but after running patched kernel, the PSR2 is disabled and the system cost more power, but this possibility is very low, I tested the patched on some dell machines, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2046315/+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 2061953] Re: intel_rapl_common: Add support for ARL and LNL
** Changed in: linux-oem-6.8 (Ubuntu Noble) 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/2061953 Title: intel_rapl_common: Add support for ARL and LNL Status in linux package in Ubuntu: New Status in linux-oem-6.8 package in Ubuntu: Fix Committed Status in linux source package in Noble: New Status in linux-oem-6.8 source package in Noble: Fix Committed Bug description: [Impact] The installer doesn't work without blacklisting intel_rapl_common (snap mounts fail), unless these commits are added. Needs a oneliner fix for both platforms: 4add6e841a3e079 powercap: intel_rapl: Add support for Arrow Lake 876ed77fbed4450 powercap: intel_rapl: Add support for Lunar Lake-M paltform [Test case] Check that snaps work. [Regression potential] Can't regress other platforms, and if these would then fail in other ways, it's still likely better than before. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2061953/+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 2061747] Re: obsolete out-of-tree ivsc dkms in favor of in-tree one
https://kernel.ubuntu.com/gitea/kernel/kernel-versions/pulls/290 ** Changed in: linux-oem-6.8 (Ubuntu Noble) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2061747 Title: obsolete out-of-tree ivsc dkms in favor of in-tree one Status in ipu6-drivers package in Ubuntu: New Status in ivsc-driver package in Ubuntu: New Status in linux package in Ubuntu: New Status in linux-oem-6.8 package in Ubuntu: Fix Released Status in ipu6-drivers source package in Noble: New Status in ivsc-driver source package in Noble: New Status in linux source package in Noble: New Status in linux-oem-6.8 source package in Noble: Fix Released Bug description: Starting from kernel v6.8 (yet from the code diff it's v6.6), Intel demands the use of in-tree IVSC drivers instead of out-of-tree dkms from https://github.com/intel/ivsc-driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ipu6-drivers/+bug/2061747/+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 2059263] Re: Fix acpi_power_meter accessing IPMI region before it's ready
** Changed in: linux-oem-6.5 (Ubuntu Jammy) Status: Confirmed => 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/2059263 Title: Fix acpi_power_meter accessing IPMI region before it's ready Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux 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 Mantic: Confirmed Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: Confirmed Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] ACPI error can be found in kernel message: [3.717920] ACPI Error: No handler for Region [SYSI] (ab9e62c5) [IPMI] (20230628/evregion-130) [Fix] On Dell systems that have IPI0001 device, ensure IPMI region is ready before acpi_power_meter invokes any ACPI method. [Test] With the patch applied, no such error can be found in kernel message. acpi_power_meter sysfs also works correctly. [Where problems could occur] If asynchronous probe is disabled, the device drivers that probe after acpi_power_meter needs to wait until the completion is done, hence the boot time might be slower. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2059263/+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 2060727] Re: The keyboard does not work after latest kernel update
** Changed in: linux-oem-6.5 (Ubuntu Jammy) Status: In Progress => Fix Committed ** Changed in: linux-oem-6.5 (Ubuntu) Status: In Progress => Invalid -- 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/2060727 Title: The keyboard does not work after latest kernel update 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 Mantic: In Progress Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: The computer is a ThinkPad L15 Gen 4, its integrated keyboard does not work after the latest kernel update and its subsequent reboot of the laptop. Nothing else is connected to the laptop. -- In /var/log/apt/history.log , the latest we can see is: Start-Date: 2024-04-09 12:37:28 Commandline: apt full-upgrade Install: linux-modules-extra-6.5.0-27-generic:amd64 (6.5.0-27.28, automatic), linux-headers-6.5.0-27:amd64 (6.5.0-27.28, automatic), linux-modules-6.5.0-27-generic:amd64 (6.5.0-27.28, automatic), linux-image-6.5.0-27-generic:amd64 (6.5.0-27.28, automatic), linux-headers-6.5.0-27-generic:amd64 (6.5.0-27.28, automatic) Upgrade: linux-headers-generic:amd64 (6.5.0.26.26, 6.5.0.27.27), linux-generic:amd64 (6.5.0.26.26, 6.5.0.27.27), linux-image-generic:amd64 (6.5.0.26.26, 6.5.0.27.27), linux-libc-dev:amd64 (6.5.0-26.26, 6.5.0-27.28) End-Date: 2024-04-09 12:37:51 -- $ lsb_release -rd No LSB modules are available. Description:Ubuntu 23.10 Release:23.10 $ # Note: It's Kubuntu 23.10 -- $ uname -a Linux tp 6.5.0-27-generic #28-Ubuntu SMP PREEMPT_DYNAMIC Thu Mar 7 18:21:00 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux SRU Justification: == [Impact] Keyboard is lost after updated to 6.5.0-27 and oem-6.5-1019 kernel versions. [Fix] Regression commit is found commit: 936e4d49ecbc ("Input: atkbd - skip ATKBD_CMD_GETID in translated mode") Fixes: 9cf6e24c9fbf1 Input: atkbd - do not skip atkbd_deactivate() when skipping ATKBD_CMD_GETID 683cd8259a9b8 Input: atkbd - skip ATKBD_CMD_SETLEDS when skipping ATKBD_CMD_GETID [Test] Tested on hardware, keyboard works fine after bootup. The regression commit is only in 6.5 stable, so SRU for 6.5 only. [Where problems could occur] It may break keyboard. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060727/+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 2061953] [NEW] intel_rapl_common: Add support for ARL and LNL
Public bug reported: [Impact] The installer doesn't work without blacklisting intel_rapl_common (snap mounts fail), unless these commits are added. Needs a oneliner fix for both platforms: 4add6e841a3e079 powercap: intel_rapl: Add support for Arrow Lake 876ed77fbed4450 powercap: intel_rapl: Add support for Lunar Lake-M paltform [Test case] Check that snaps work. [Regression potential] Can't regress other platforms, and if these would then fail in other ways, it's still likely better than before. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux-oem-6.8 (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Affects: linux-oem-6.8 (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux-oem-6.8 (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/2061953 Title: intel_rapl_common: Add support for ARL and LNL Status in linux package in Ubuntu: New Status in linux-oem-6.8 package in Ubuntu: New Status in linux source package in Noble: New Status in linux-oem-6.8 source package in Noble: New Bug description: [Impact] The installer doesn't work without blacklisting intel_rapl_common (snap mounts fail), unless these commits are added. Needs a oneliner fix for both platforms: 4add6e841a3e079 powercap: intel_rapl: Add support for Arrow Lake 876ed77fbed4450 powercap: intel_rapl: Add support for Lunar Lake-M paltform [Test case] Check that snaps work. [Regression potential] Can't regress other platforms, and if these would then fail in other ways, it's still likely better than before. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2061953/+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 2061830] Re: Limit supported pci-id's to the new ones added by 550
** Also affects: nvidia-graphics-drivers-550 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-550-server (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-550 (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-550-server (Ubuntu Mantic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-550 in Ubuntu. https://bugs.launchpad.net/bugs/2061830 Title: Limit supported pci-id's to the new ones added by 550 Status in nvidia-graphics-drivers-550 package in Ubuntu: New Status in nvidia-graphics-drivers-550-server package in Ubuntu: New Status in nvidia-graphics-drivers-550 source package in Jammy: New Status in nvidia-graphics-drivers-550-server source package in Jammy: New Status in nvidia-graphics-drivers-550 source package in Mantic: New Status in nvidia-graphics-drivers-550-server source package in Mantic: New Status in nvidia-graphics-drivers-550 source package in Noble: New Status in nvidia-graphics-drivers-550-server source package in Noble: New Bug description: Since 550 wasn't included in the beta we should limit the potential impact on 24.04 stability by limiting the driver to be loaded only on the new hw supported by this driver. This will be temporary until we are ready to migrate 535 to 550. The id list for 'Pmaliases' is not modified, as that only tells gpu- manager to enable runtime power management for matching GPUs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-550/+bug/2061830/+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 2061830] [NEW] Limit supported pci-id's to the new ones added by 550
Public bug reported: Since 550 wasn't included in the beta we should limit the potential impact on 24.04 stability by limiting the driver to be loaded only on the new hw supported by this driver. This will be temporary until we are ready to migrate 535 to 550. ** Affects: nvidia-graphics-drivers-550 (Ubuntu) Importance: Undecided Assignee: Timo Aaltonen (tjaalton) Status: New ** Affects: nvidia-graphics-drivers-550-server (Ubuntu) Importance: Undecided Status: New ** Affects: nvidia-graphics-drivers-550 (Ubuntu Noble) Importance: Undecided Assignee: Timo Aaltonen (tjaalton) Status: New ** Affects: nvidia-graphics-drivers-550-server (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-550 (Ubuntu) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-550 (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-550-server (Ubuntu Noble) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-550 (Ubuntu Noble) Assignee: (unassigned) => Timo Aaltonen (tjaalton) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-550-server in Ubuntu. https://bugs.launchpad.net/bugs/2061830 Title: Limit supported pci-id's to the new ones added by 550 Status in nvidia-graphics-drivers-550 package in Ubuntu: New Status in nvidia-graphics-drivers-550-server package in Ubuntu: New Status in nvidia-graphics-drivers-550 source package in Noble: New Status in nvidia-graphics-drivers-550-server source package in Noble: New Bug description: Since 550 wasn't included in the beta we should limit the potential impact on 24.04 stability by limiting the driver to be loaded only on the new hw supported by this driver. This will be temporary until we are ready to migrate 535 to 550. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-550/+bug/2061830/+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 2061049] Re: Fix random HuC/GuC initialization failure of Intel i915 driver
and noble:linux of course -- 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/2061049 Title: Fix random HuC/GuC initialization failure of Intel i915 driver Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux-oem-6.8 package in Ubuntu: New Status in linux source package in Jammy: New Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux-oem-6.8 source package in Jammy: Invalid Status in linux source package in Noble: New Status in linux-oem-6.5 source package in Noble: Invalid Status in linux-oem-6.8 source package in Noble: New Bug description: [Impact] i915 error can sometimes be found in kernel message when booting the machine w/ power unplugged kernel: i915 :00:02.0: [drm] *ERROR* GT1: GuC initialization failed -EIO kernel: i915 :00:02.0: [drm] *ERROR* GT1: Enabling uc failed (-5) kernel: i915 :00:02.0: [drm] *ERROR* GT1: Failed to initialize GPU, declaring it wedged! The GPU won't work with this failure [Fix] Backport the upatream fix for allowing slow HuC loading. [Test] 1. Unplug the power of the laptop and make sure it's charged by battery 2. Cold boot or Warm boot the machine and check the GuC init fail message. 3. Go to settings - > about --> graphics to make sure the GPU information is correct every boot. [Where problems could occur] Simply increase the loading time of HuC still get a working system. Should be low risk of regression. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2061049/+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 2061049] Re: Fix random HuC/GuC initialization failure of Intel i915 driver
please send for oem-6.8 too if it's an issue there -- 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/2061049 Title: Fix random HuC/GuC initialization failure of Intel i915 driver Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux-oem-6.8 package in Ubuntu: New Status in linux source package in Jammy: New Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux-oem-6.8 source package in Jammy: Invalid Status in linux source package in Noble: New Status in linux-oem-6.5 source package in Noble: Invalid Status in linux-oem-6.8 source package in Noble: New Bug description: [Impact] i915 error can sometimes be found in kernel message when booting the machine w/ power unplugged kernel: i915 :00:02.0: [drm] *ERROR* GT1: GuC initialization failed -EIO kernel: i915 :00:02.0: [drm] *ERROR* GT1: Enabling uc failed (-5) kernel: i915 :00:02.0: [drm] *ERROR* GT1: Failed to initialize GPU, declaring it wedged! The GPU won't work with this failure [Fix] Backport the upatream fix for allowing slow HuC loading. [Test] 1. Unplug the power of the laptop and make sure it's charged by battery 2. Cold boot or Warm boot the machine and check the GuC init fail message. 3. Go to settings - > about --> graphics to make sure the GPU information is correct every boot. [Where problems could occur] Simply increase the loading time of HuC still get a working system. Should be low risk of regression. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2061049/+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 2060984] Re: FFe: New firmware release
nope, that's fine -- 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/2060984 Title: FFe: New firmware release Status in linux-firmware package in Ubuntu: New Bug description: A new upstream release of linux-firmware was tagged on 2024.04.10, this would sync us with that. Changes: - imx: sdma: update firmware to v3.6/v4.6 - linux-firmware: mediatek: Update MT8173 VPU firmware to v1.1.8 - amdgpu: DMCUB updates for various AMDGPU ASICs - Intel Bluetooth: Update firmware file for Intel Bluetooth 9260 - Intel Bluetooth: Update firmware file for Intel Bluetooth 9560 - Intel Bluetooth: Update firmware file for Intel Bluetooth AX201 - Intel Bluetooth: Update firmware file for Intel Bluetooth AX200 - Intel Bluetooth: Update firmware file for Solar Intel Bluetooth AX210 - Intel Bluetooth: Update firmware file for Solar Intel Bluetooth AX211 - Intel Bluetooth: Update firmware file for SolarF Intel Bluetooth AX211 - Intel Bluetooth: Update firmware file for Solar Intel Bluetooth AX203 - Intel Bluetooth: Update firmware file for SolarF Intel Bluetooth AX203 - Intel Bluetooth: Update firmware file for Solar Intel Bluetooth AX101 - Intel Bluetooth: Update firmware file for SolarF Intel Bluetooth AX101 - Intel Bluetooth: Update firmware file for Magnetor Intel Bluetooth AX211 - Intel Bluetooth: Update firmware file for Magnetor Intel Bluetooth AX203 - Intel Bluetooth: Update firmware file for Magnetor Intel Bluetooth AX101 - Intel Bluetooth: Update firmware file for Intel Bluetooth BE200 - WHENCE: Link the Raspberry Pi CM4 and 5B to the 4B - Montage: update firmware for Mont-TSSE - linux-firmware: Add firmware for Cirrus CS35L56 for Dell laptops - rtw88: Add RTL8703B firmware v11.0.0 - rtw89: 8922a: add firmware v0.35.18.0 - rtw89: 8852c: update fw to v0.27.56.14 - mekdiatek: Update mt8186 SOF firmware to v2.0.1 - linux-firmware: update firmware for en8811h 2.5G ethernet phy - amdgpu: DMCUB updates for various AMDGPU ASICs - i915: Add DG2 HuC 7.10.15 - ath10k: WCN3990: hw1.0: move firmware back from qcom/ location - ath10k: WCN3990: hw1.0: add qcm2290 firmware API file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2060984/+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 1949314] Re: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed.
** Also affects: intel-gpu-tools (Ubuntu Noble) Importance: Undecided Assignee: Hector CAO (hectorcao) Status: In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to intel-gpu-tools in Ubuntu. https://bugs.launchpad.net/bugs/1949314 Title: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. Status in intel-gpu-tools package in Ubuntu: In Progress Status in intel-gpu-tools source package in Jammy: In Progress Status in intel-gpu-tools source package in Mantic: New Status in intel-gpu-tools source package in Noble: In Progress Bug description: [ Impact ] When resizing the terminal window, intel_gpu_top may crash if the window becomes small enough. The output when it crashes is: intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. The fix has been reported and fixed upstream recently : https://gitlab.freedesktop.org/drm/igt-gpu-tools/-/issues/143 The fix has been part of a serie of fixes that improve intel_gpu_top UI behavior for some corner cases : https://patchwork.freedesktop.org/series/124890/ The proposed fix consists of backporting these fixes to affected Ubuntu releases (Jammy, Mantic and Noble) Tvrtko Ursulin (4): tools/intel_gpu_top: Fix clients header width when no clients tools/intel_gpu_top: Fix client layout on first sample period tools/intel_gpu_top: Optimise interactive display a bit tools/intel_gpu_top: Handle narrow terminals more gracefully [ Test Plan ] Run intel_gpu_top inside a console Resize the console with the mouse to it smallest size [ Where problems could occur ] The problem occurs when intel_gpu_top try to draw information on the console [ Other Info ] This fix should not cause regression on any other feature. When resizing the terminal window, intel_gpu_top may crash if the window become small enough. The output when it crashes is: intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. Abortado I was able to reproduce this crash with tilix and xterm. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: intel-gpu-tools 1.26-2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu72 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Sun Oct 31 21:06:01 2021 InstallationDate: Installed on 2017-06-13 (1601 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: intel-gpu-tools UpgradeStatus: Upgraded to jammy on 2019-12-22 (679 days ago) modified.conffile..etc.cron.daily.apport: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+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 1949314] Re: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed.
** Also affects: intel-gpu-tools (Ubuntu Mantic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to intel-gpu-tools in Ubuntu. https://bugs.launchpad.net/bugs/1949314 Title: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. Status in intel-gpu-tools package in Ubuntu: In Progress Status in intel-gpu-tools source package in Jammy: In Progress Status in intel-gpu-tools source package in Mantic: New Bug description: [ Impact ] When resizing the terminal window, intel_gpu_top may crash if the window becomes small enough. The output when it crashes is: intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. The proposed fix consists of removing the assert() function and only skip drawing. [ Test Plan ] Run intel_gpu_top inside a console Resize the console with the mouse to it smallest size [ Where problems could occur ] The problem occurs when intel_gpu_top try to draw information on the console [ Other Info ] This fix should not cause regression on any other feature. When resizing the terminal window, intel_gpu_top may crash if the window become small enough. The output when it crashes is: intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. Abortado I was able to reproduce this crash with tilix and xterm. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: intel-gpu-tools 1.26-2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu72 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Sun Oct 31 21:06:01 2021 InstallationDate: Installed on 2017-06-13 (1601 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: intel-gpu-tools UpgradeStatus: Upgraded to jammy on 2019-12-22 (679 days ago) modified.conffile..etc.cron.daily.apport: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+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 1949314] Re: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed.
** Also affects: intel-gpu-tools (Ubuntu Jammy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to intel-gpu-tools in Ubuntu. https://bugs.launchpad.net/bugs/1949314 Title: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. Status in intel-gpu-tools package in Ubuntu: In Progress Status in intel-gpu-tools source package in Jammy: New Bug description: When resizing the terminal window, intel_gpu_top may crash if the window become small enough. The output when it crashes is: intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. Abortado I was able to reproduce this crash with tilix and xterm. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: intel-gpu-tools 1.26-2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu72 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Sun Oct 31 21:06:01 2021 InstallationDate: Installed on 2017-06-13 (1601 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: intel-gpu-tools UpgradeStatus: Upgraded to jammy on 2019-12-22 (679 days ago) modified.conffile..etc.cron.daily.apport: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+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 2061324] Re: Error when re-building package from source
** Also affects: intel-gpu-tools (Ubuntu Jammy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to intel-gpu-tools in Ubuntu. https://bugs.launchpad.net/bugs/2061324 Title: Error when re-building package from source Status in intel-gpu-tools package in Ubuntu: In Progress Status in intel-gpu-tools source package in Jammy: New Bug description: [ Impact ] Impossible to build the package from source on Ubuntu 22.04, users will get this error: ``` int main(void) { void *a = (void*) _create; long long b = (long long) a; return (int) b; } Compiler stdout: Compiler stderr: Checking for function "memfd_create" : YES Configuring config.h using configuration ../lib/meson.build:155:4: ERROR: Function does not take positional arguments. dh_auto_configure: error: cd build && LC_ALL=C.UTF-8 meson .. --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc --localstatedir=/var --libdir=lib/x86_64-linux-gnu -Dtests=disabled returned exit code 1 make[1]: *** [debian/rules:19: override_dh_auto_configure] Error 255 make[1]: Leaving directory '/home/ubuntu/hector/intel-gpu-tools-1.26' make: *** [debian/rules:39: build] Error 2 dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2 ``` The problem comes from the bad call to meson function underscorify in lib/meson.build This problem has been fixed upstream: 963917a3565466832a3b2fc22e9285d34a0bf944 lib/meson.build: Fix underscorify call f.underscorify() is correct, f.underscorify(f) is an error that later meson versions don't like at all. The proposed fix for Ubuntu consists of backporting this patch. [ Test Plan ] Build the package from source on Ubuntu 22.04 The build command is : dpkg-buildpackage -us -uc -b Ubuntu release : Jammy 22.04 Meson version : 0.61.2 [ Where problems could occur ] The problem occurs only at build process [ Other Info ] This issue only happens at build and has been fixed upstream. It is safe to have it in SRU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/2061324/+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 1853665] Re: Realtek RTL8821CE [10ec:c821] Subsystem [103c:831a] Bluetooth not probed
** Changed in: linux-oem (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1853665 Title: Realtek RTL8821CE [10ec:c821] Subsystem [103c:831a] Bluetooth not probed Status in linux package in Ubuntu: Confirmed Status in linux-oem package in Ubuntu: Invalid Status in rtl8821ce package in Ubuntu: Confirmed Bug description: The driver installed just fine and wifi is working but bluetooth does not. I will gladly provide further debugging information. Ubuntu 19.10 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: steven 2090 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-11-17 (75 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0408:5321 Quanta Computer, Inc. HP Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP 250 G7 Notebook PC Package: rtl8821ce ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-29-generic root=UUID=a0cdf605-0b72-4674-a76e-ad1dbae26043 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-29-generic N/A linux-backports-modules-5.3.0-29-generic N/A linux-firmware1.183.3 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: eoan Uname: Linux 5.3.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/05/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.16 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8532 dmi.board.vendor: HP dmi.board.version: 70.22 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.16:bd12/05/2018:svnHP:pnHP250G7NotebookPC:pvrType1ProductConfigId:rvnHP:rn8532:rvr70.22:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5336AN HP 200 dmi.product.name: HP 250 G7 Notebook PC dmi.product.sku: 6MQ54EA#ABD dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: steven 1931 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-11-17 (231 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0408:5321 Quanta Computer, Inc. HP Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 1M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 5: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M |__ Port 5: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M MachineType: HP HP 250 G7 Notebook PC Package: rtl8821ce ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=a0cdf605-0b72-4674-a76e-ad1dbae26043 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no StagingDrivers: ashmem_linux Tags: focal staging staging Uname: Linux 5.4.0-40-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-18 (47 days ago) UserGroups: adm audio cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/05/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.16 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8532 dmi.board.vendor: HP dmi.board.version: 70.22 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias:
[Kernel-packages] [Bug 1825813] Re: Need to add AMD Stony Ridge APU support to Bionic
** Changed in: linux-oem (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1825813 Title: Need to add AMD Stony Ridge APU support to Bionic Status in linux-oem package in Ubuntu: Invalid Bug description: AMD suggested to back port the following fixes in 4.18 kernel needed to support AMD Stony Ridge APU to Bionic: drm/amdgpu/vcn: Update vcn.cur_state during suspend drm/amd/display: Fix BUG_ON during CRTC atomic check update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem/+bug/1825813/+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 1848318] Re: [DELL][BIONICS] Observed firmware assert during backgroung scan.
** Changed in: linux-oem (Ubuntu Bionic) Status: Fix Committed => Invalid ** Changed in: linux-oem (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1848318 Title: [DELL][BIONICS] Observed firmware assert during backgroung scan. Status in linux package in Ubuntu: Incomplete Status in linux-oem package in Ubuntu: Invalid Status in linux source package in Bionic: New Status in linux-oem source package in Bionic: Invalid Bug description: SRU Justification: -- Impact: --- Observed firmware assert(non responsive state) just 2 min after connection. Test case: -- 1) Power up the device, Redpine modules are loaded by default, Nmcli initiates the connection and device starts background scan after connection. After 2-3 min issue will be replicated. Result: --- Observed firmware assert while performing background scan. Root cause analysis: There is a redundant null check for ssid info while preparing probe request in background scan case, which blocks the probe request pkt length update, leads to assert no-71(if probe-req-length is 0 or greater the max probe length 120) in firmware. Fix: Removed the redundant null check. Regression Potential: - This is observed just 2 min after connection, fixed and checked the driver stability. Every thing ran smooth. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848318/+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 1847198] Re: amdgpu kernel module should be used instead of radeon on amd graphic
** Changed in: linux-oem (Ubuntu) Status: Confirmed => Won't Fix ** Changed in: linux-oem (Ubuntu Bionic) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1847198 Title: amdgpu kernel module should be used instead of radeon on amd graphic Status in OEM Priority Project: Won't Fix Status in OEM Priority Project bionic series: Won't Fix Status in linux-oem package in Ubuntu: Won't Fix Status in linux-oem source package in Bionic: Won't Fix Bug description: there're some graphic be supported both on amdgpu and radeon. But somehow kernel might pick radeon instead of amdgpu. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-oem 4.15.0.1057.61 ProcVersionSignature: Ubuntu 4.15.0-1057.66-oem 4.15.18 Uname: Linux 4.15.0-1057-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Oct 8 03:33:43 2019 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-lancel+X97 InstallationDate: Installed on 2019-10-04 (3 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 SourcePackage: linux-meta-oem UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1847198/+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 1905013] Re: focal linux-oem-{5.6, 5.10} should express their flavour
** Changed in: linux-oem (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1905013 Title: focal linux-oem-{5.6,5.10} should express their flavour Status in linux-oem package in Ubuntu: Fix Released Bug description: It seems we have ended up with the oem flavour not being expressed in either of the meta or lrm packages, the -oem component is smooshed into the variant. This is inconsistent with all other packages. Consider what would happen if we needed a second flavour in the package, there would be literally no way to express it in the current form. We should pull -oem off of the variant and express it formally in all of these packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem/+bug/1905013/+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 1901976] Re: Introduce support for Systems Management Driver over WMI for Dell Systems
** Changed in: linux-oem (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1901976 Title: Introduce support for Systems Management Driver over WMI for Dell Systems Status in linux-oem package in Ubuntu: Invalid Bug description: The Dell WMI Systems Management Driver provides a sysfs interface for systems management to enable BIOS configuration capability on certain Dell Systems. This driver allows user to configure Dell systems with a uniform common interface. To facilitate this, the patch introduces a generic way for driver to be able to create configurable BIOS Attributes available in Setup (F2) screen. [Impact] This provides a huge benefit to Dell machines users to be able to manipulate BIOS settings from within Ubuntu. [Fix] By the patches: https://www.spinics.net/lists/platform-driver-x86/msg23302.html Maintainer has merged the code to his branch: https://www.spinics.net/lists/platform-driver-x86/msg23313.html [Test Case] [Regression Risk] This is a new driver and self-contained. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem/+bug/1901976/+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 1904091] Re: Linux, Ubuntu, 20.04, X40CI, S_P: Monitor connect Salomon Dock has no display(FR:100%)
** Changed in: linux-oem (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1904091 Title: Linux,Ubuntu,20.04,X40CI,S_P: Monitor connect Salomon Dock has no display(FR:100%) Status in linux-oem package in Ubuntu: Invalid Bug description: [Result] Expected Result Boot to SUT to Ubutnu OS, plugging in the external Display/Monitor video cable to the Salomon dock, SUT& monitor has not problem(s) or issue(s). Actual Result Boot to SUT to Ubutnu OS, plugging in the external Display/Monitor video cable to the Salomon dock, SUT can recognize monitor, but monitor no display. [Additional Information] 1. Test Vault ID: 61923.008 2. SKU: Precision All SKU 3. BIOS Version: 1.4.0 4. ImageManifest: Ubuntu 20.04.1 LTS (fossa-bronn X40) 5. Product Name: Precision 5750 6. Kernel Version:5.6.0-2029-oem 7. CPU: Intel(R) Core(TM) i7-10850H @ 2.70GHz12 8. GPU: Mesa Intel(R) UHD Graphics (CML GT2) 9.VP DC/SC/TBT FWA03 & FWA04 Dock 10.VP all types of Monitors & Monitors ports 11.VNP Ubuntu 18.04 Failure rate Precision-SKU5-6 10/10 times Precision-SKUP2-3 10/10times [Reproduce Steps] 1. Flash Latest BIOS, Install Ubuntu OS 20.04.1. 2. Do Ubuntu update. 3. Plugging in the external Display/Monitor video cable to the Salomon dock, SUT can recognize monitor, but monitor no display.>problem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem/+bug/1904091/+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 1962799] Re: Bad items from Powertop on oem kernel
** Changed in: linux-oem (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1962799 Title: Bad items from Powertop on oem kernel Status in OEM Priority Project: Triaged Status in linux-oem package in Ubuntu: Invalid Bug description: On Jaguar2, we found some items are bad from powertop, could we set them 'Good' by default from oem kernel, so that we could save more power consumption. System info "ThinkPad X1 Yoga Gen 7", "BIOS": "N3AET52W (1.17 ) 02/21/2022", CPU": "12th Gen Intel(R) Core(TM) i5-1235U", VGA: [8086:46a8], Kernel: 5.14.0-1024-oem Power Consumption === The idle-screen-on-residency-check/cpu-low-power-idle/system-low-power-idle passed. Default value and the value after set all ‘Good’ in powertop ShortIdle: 5.5W, 5W LongIdle: 1.8W, 2W S2Idle: 0.6W, 0.6W Bad items === * VM writeback timeout (echo ‘1500’ > /proc/sys/vm/dirty_writeback_centisecs) * Should we turn off the NMI watchdog for the OEM kernel? It prompt“NMI watchdog should be turned off” (/proc/sys/kernel/nmi_watchdog) * Runtime PM for I2C Adapter i2c-[2-10] (i915 gmbus tc[1-6]/dp[a-c])? By default these values are ‘on’, should we set it to ‘auto’? (/sys/bus/i2c/devices/i2c-2/device/power/control) * Runtime PM for PCI Device Intel Corporation Device [4601,46a8,461d,464f,51a4,51f0,5182,51ed,51ef,51fc]? Host bridge,VGA controller,Signal processing controller,System peripheral,Serial bus controller,Network Controller,ISA bridge,USB controller,RAM memory,Serial controller. (/sys/bus/pci/devices/:00:00.0/power/control) * Runtime PM for PCI Device MEDIATEK Corp. Device 4d75 * Runtime PM for PCI Device Samsung Electronics Co Ltd Device a80a * Autosuspend for USB device USB Bridge [MCHP]? (/sys/bus/usb/devices/3-8/power/control) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1962799/+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 1822714] Re: Need a meta package to add kernel 5.0 support to Bionic
** Changed in: linux-oem (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1822714 Title: Need a meta package to add kernel 5.0 support to Bionic Status in linux-oem package in Ubuntu: Invalid Bug description: - In preparation of the 18.04osp1 base image, we need to have meta package ready that adds kernel 5.0 support to Bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem/+bug/1822714/+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 1818028] Re: linux-oem 4.15.0-1034.39 ADT test failure with linux-oem 4.15.0-1034.39
** Changed in: linux-oem (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1818028 Title: linux-oem 4.15.0-1034.39 ADT test failure with linux-oem 4.15.0-1034.39 Status in linux-oem package in Ubuntu: Invalid Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/l/linux-oem/20190227_173811_bb609@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem/+bug/1818028/+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 2061049] Re: Fix random HuC/GuC initialization failure of Intel i915 driver
** Changed in: linux-oem-6.5 (Ubuntu Jammy) Status: In Progress => Fix Committed ** Changed in: linux-oem-6.5 (Ubuntu Noble) Status: New => Invalid ** Also affects: linux-oem-6.8 (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux-oem (Ubuntu) ** No longer affects: linux-oem (Ubuntu Jammy) ** No longer affects: linux-oem (Ubuntu Noble) ** Changed in: linux-oem-6.8 (Ubuntu Jammy) Status: New => Invalid -- 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/2061049 Title: Fix random HuC/GuC initialization failure of Intel i915 driver Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux-oem-6.8 package in Ubuntu: New Status in linux source package in Jammy: New Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux-oem-6.8 source package in Jammy: Invalid Status in linux source package in Noble: New Status in linux-oem-6.5 source package in Noble: Invalid Status in linux-oem-6.8 source package in Noble: New Bug description: [Impact] i915 error can sometimes be found in kernel message when booting the machine w/ power unplugged kernel: i915 :00:02.0: [drm] *ERROR* GT1: GuC initialization failed -EIO kernel: i915 :00:02.0: [drm] *ERROR* GT1: Enabling uc failed (-5) kernel: i915 :00:02.0: [drm] *ERROR* GT1: Failed to initialize GPU, declaring it wedged! The GPU won't work with this failure [Fix] Backport the upatream fix for allowing slow HuC loading. [Test] 1. Unplug the power of the laptop and make sure it's charged by battery 2. Cold boot or Warm boot the machine and check the GuC init fail message. 3. Go to settings - > about --> graphics to make sure the GPU information is correct every boot. [Where problems could occur] Simply increase the loading time of HuC still get a working system. Should be low risk of regression. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2061049/+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 2058452] Re: Support USB serial port for Dell DW5826e WWAN
** Tags removed: verification-needed-jammy-linux-oem-6.5 ** Tags added: verification-done-jammy-linux-oem-6.5 -- 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/2058452 Title: Support USB serial port for Dell DW5826e WWAN Status in HWE Next: New Status in OEM Priority Project: New Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [SRU Justification] [Impact] Missing usb serial interface for Dell DW5826e. [Fix] * commit 129690fb229a ("USB: serial: qcserial: add new usb-id for Dell Wireless DW5826e "): in v6.8 [Test Case] 1. check system with USB\VID_413C_8217 or USB\VID_413C_8218 creates corresponding tty port [Where problems could occur] The commit adds new device ID only, it won't impact devices which are supported originally. [Other Info] Upstream commit: https://github.com/torvalds/linux/commit/129690fb229a20b6e563a77a2c85266acecf20bc Dell new platform with the device will be enabled by linux-oem-6.5. The tty port will be utilized by the userspace fcc unlock program. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2058452/+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 2060984] Re: FFe: New firmware release
build available at https://launchpad.net/~tjaalton/+archive/ubuntu/firmware -- 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/2060984 Title: FFe: New firmware release Status in linux-firmware package in Ubuntu: New Bug description: A new upstream release of linux-firmware was tagged on 2024.04.10, this would sync us with that. Changes: - imx: sdma: update firmware to v3.6/v4.6 - linux-firmware: mediatek: Update MT8173 VPU firmware to v1.1.8 - amdgpu: DMCUB updates for various AMDGPU ASICs - Intel Bluetooth: Update firmware file for Intel Bluetooth 9260 - Intel Bluetooth: Update firmware file for Intel Bluetooth 9560 - Intel Bluetooth: Update firmware file for Intel Bluetooth AX201 - Intel Bluetooth: Update firmware file for Intel Bluetooth AX200 - Intel Bluetooth: Update firmware file for Solar Intel Bluetooth AX210 - Intel Bluetooth: Update firmware file for Solar Intel Bluetooth AX211 - Intel Bluetooth: Update firmware file for SolarF Intel Bluetooth AX211 - Intel Bluetooth: Update firmware file for Solar Intel Bluetooth AX203 - Intel Bluetooth: Update firmware file for SolarF Intel Bluetooth AX203 - Intel Bluetooth: Update firmware file for Solar Intel Bluetooth AX101 - Intel Bluetooth: Update firmware file for SolarF Intel Bluetooth AX101 - Intel Bluetooth: Update firmware file for Magnetor Intel Bluetooth AX211 - Intel Bluetooth: Update firmware file for Magnetor Intel Bluetooth AX203 - Intel Bluetooth: Update firmware file for Magnetor Intel Bluetooth AX101 - Intel Bluetooth: Update firmware file for Intel Bluetooth BE200 - WHENCE: Link the Raspberry Pi CM4 and 5B to the 4B - Montage: update firmware for Mont-TSSE - linux-firmware: Add firmware for Cirrus CS35L56 for Dell laptops - rtw88: Add RTL8703B firmware v11.0.0 - rtw89: 8922a: add firmware v0.35.18.0 - rtw89: 8852c: update fw to v0.27.56.14 - mekdiatek: Update mt8186 SOF firmware to v2.0.1 - linux-firmware: update firmware for en8811h 2.5G ethernet phy - amdgpu: DMCUB updates for various AMDGPU ASICs - i915: Add DG2 HuC 7.10.15 - ath10k: WCN3990: hw1.0: move firmware back from qcom/ location - ath10k: WCN3990: hw1.0: add qcm2290 firmware API file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2060984/+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 2060984] Re: FFe: New firmware release
would also fix https://bugs.launchpad.net/ubuntu/+source/linux- firmware/+bug/2060904 -- 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/2060984 Title: FFe: New firmware release Status in linux-firmware package in Ubuntu: New Bug description: A new upstream release of linux-firmware was tagged on 2024.04.10, this would sync us with that. Changes: - imx: sdma: update firmware to v3.6/v4.6 - linux-firmware: mediatek: Update MT8173 VPU firmware to v1.1.8 - amdgpu: DMCUB updates for various AMDGPU ASICs - Intel Bluetooth: Update firmware file for Intel Bluetooth 9260 - Intel Bluetooth: Update firmware file for Intel Bluetooth 9560 - Intel Bluetooth: Update firmware file for Intel Bluetooth AX201 - Intel Bluetooth: Update firmware file for Intel Bluetooth AX200 - Intel Bluetooth: Update firmware file for Solar Intel Bluetooth AX210 - Intel Bluetooth: Update firmware file for Solar Intel Bluetooth AX211 - Intel Bluetooth: Update firmware file for SolarF Intel Bluetooth AX211 - Intel Bluetooth: Update firmware file for Solar Intel Bluetooth AX203 - Intel Bluetooth: Update firmware file for SolarF Intel Bluetooth AX203 - Intel Bluetooth: Update firmware file for Solar Intel Bluetooth AX101 - Intel Bluetooth: Update firmware file for SolarF Intel Bluetooth AX101 - Intel Bluetooth: Update firmware file for Magnetor Intel Bluetooth AX211 - Intel Bluetooth: Update firmware file for Magnetor Intel Bluetooth AX203 - Intel Bluetooth: Update firmware file for Magnetor Intel Bluetooth AX101 - Intel Bluetooth: Update firmware file for Intel Bluetooth BE200 - WHENCE: Link the Raspberry Pi CM4 and 5B to the 4B - Montage: update firmware for Mont-TSSE - linux-firmware: Add firmware for Cirrus CS35L56 for Dell laptops - rtw88: Add RTL8703B firmware v11.0.0 - rtw89: 8922a: add firmware v0.35.18.0 - rtw89: 8852c: update fw to v0.27.56.14 - mekdiatek: Update mt8186 SOF firmware to v2.0.1 - linux-firmware: update firmware for en8811h 2.5G ethernet phy - amdgpu: DMCUB updates for various AMDGPU ASICs - i915: Add DG2 HuC 7.10.15 - ath10k: WCN3990: hw1.0: move firmware back from qcom/ location - ath10k: WCN3990: hw1.0: add qcm2290 firmware API file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2060984/+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 2060984] [NEW] FFe: New firmware release
Public bug reported: A new upstream release of linux-firmware was tagged on 2024.04.10, this would sync us with that. Changes: - imx: sdma: update firmware to v3.6/v4.6 - linux-firmware: mediatek: Update MT8173 VPU firmware to v1.1.8 - amdgpu: DMCUB updates for various AMDGPU ASICs - Intel Bluetooth: Update firmware file for Intel Bluetooth 9260 - Intel Bluetooth: Update firmware file for Intel Bluetooth 9560 - Intel Bluetooth: Update firmware file for Intel Bluetooth AX201 - Intel Bluetooth: Update firmware file for Intel Bluetooth AX200 - Intel Bluetooth: Update firmware file for Solar Intel Bluetooth AX210 - Intel Bluetooth: Update firmware file for Solar Intel Bluetooth AX211 - Intel Bluetooth: Update firmware file for SolarF Intel Bluetooth AX211 - Intel Bluetooth: Update firmware file for Solar Intel Bluetooth AX203 - Intel Bluetooth: Update firmware file for SolarF Intel Bluetooth AX203 - Intel Bluetooth: Update firmware file for Solar Intel Bluetooth AX101 - Intel Bluetooth: Update firmware file for SolarF Intel Bluetooth AX101 - Intel Bluetooth: Update firmware file for Magnetor Intel Bluetooth AX211 - Intel Bluetooth: Update firmware file for Magnetor Intel Bluetooth AX203 - Intel Bluetooth: Update firmware file for Magnetor Intel Bluetooth AX101 - Intel Bluetooth: Update firmware file for Intel Bluetooth BE200 - WHENCE: Link the Raspberry Pi CM4 and 5B to the 4B - Montage: update firmware for Mont-TSSE - linux-firmware: Add firmware for Cirrus CS35L56 for Dell laptops - rtw88: Add RTL8703B firmware v11.0.0 - rtw89: 8922a: add firmware v0.35.18.0 - rtw89: 8852c: update fw to v0.27.56.14 - mekdiatek: Update mt8186 SOF firmware to v2.0.1 - linux-firmware: update firmware for en8811h 2.5G ethernet phy - amdgpu: DMCUB updates for various AMDGPU ASICs - i915: Add DG2 HuC 7.10.15 - ath10k: WCN3990: hw1.0: move firmware back from qcom/ location - ath10k: WCN3990: hw1.0: add qcm2290 firmware API file ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Summary changed: - New firmware release + FFe: New firmware release -- 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/2060984 Title: FFe: New firmware release Status in linux-firmware package in Ubuntu: New Bug description: A new upstream release of linux-firmware was tagged on 2024.04.10, this would sync us with that. Changes: - imx: sdma: update firmware to v3.6/v4.6 - linux-firmware: mediatek: Update MT8173 VPU firmware to v1.1.8 - amdgpu: DMCUB updates for various AMDGPU ASICs - Intel Bluetooth: Update firmware file for Intel Bluetooth 9260 - Intel Bluetooth: Update firmware file for Intel Bluetooth 9560 - Intel Bluetooth: Update firmware file for Intel Bluetooth AX201 - Intel Bluetooth: Update firmware file for Intel Bluetooth AX200 - Intel Bluetooth: Update firmware file for Solar Intel Bluetooth AX210 - Intel Bluetooth: Update firmware file for Solar Intel Bluetooth AX211 - Intel Bluetooth: Update firmware file for SolarF Intel Bluetooth AX211 - Intel Bluetooth: Update firmware file for Solar Intel Bluetooth AX203 - Intel Bluetooth: Update firmware file for SolarF Intel Bluetooth AX203 - Intel Bluetooth: Update firmware file for Solar Intel Bluetooth AX101 - Intel Bluetooth: Update firmware file for SolarF Intel Bluetooth AX101 - Intel Bluetooth: Update firmware file for Magnetor Intel Bluetooth AX211 - Intel Bluetooth: Update firmware file for Magnetor Intel Bluetooth AX203 - Intel Bluetooth: Update firmware file for Magnetor Intel Bluetooth AX101 - Intel Bluetooth: Update firmware file for Intel Bluetooth BE200 - WHENCE: Link the Raspberry Pi CM4 and 5B to the 4B - Montage: update firmware for Mont-TSSE - linux-firmware: Add firmware for Cirrus CS35L56 for Dell laptops - rtw88: Add RTL8703B firmware v11.0.0 - rtw89: 8922a: add firmware v0.35.18.0 - rtw89: 8852c: update fw to v0.27.56.14 - mekdiatek: Update mt8186 SOF firmware to v2.0.1 - linux-firmware: update firmware for en8811h 2.5G ethernet phy - amdgpu: DMCUB updates for various AMDGPU ASICs - i915: Add DG2 HuC 7.10.15 - ath10k: WCN3990: hw1.0: move firmware back from qcom/ location - ath10k: WCN3990: hw1.0: add qcm2290 firmware API file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2060984/+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 2057424] Re: No variable refresh rate (VRR) on the Framework 16
** Also affects: linux-oem-6.8 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.8 in Ubuntu. https://bugs.launchpad.net/bugs/2057424 Title: No variable refresh rate (VRR) on the Framework 16 Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.8 package in Ubuntu: New Status in linux source package in Noble: In Progress Status in linux-oem-6.8 source package in Noble: New Bug description: Quoted from AMD proposed fix in https://lore.kernel.org/amd- gfx/46657fa4-630e-47a5-a339-242ecd5ba...@amd.com/T/#m94e3b7d292e359f3d656babe3ccdbf7fc6daab6f > The monitor shipped with the Framework 16 supports VRR [1], but it's not > being advertised. > > This is because the detailed timing block doesn't contain > `EDID_DETAIL_MONITOR_RANGE` which amdgpu looks for to find min and max > frequencies. This check however is superfluous for this case because > update_display_info() calls drm_get_monitor_range() to get these ranges > already. > > So if the `DRM_EDID_FEATURE_CONTINUOUS_FREQ` EDID feature is found then > turn on freesync without extra checks. See: https://www.reddit.com/r/framework/comments/1b4y2i5/no_variable_refresh_rate_on_the_framework_16_on/ See: https://www.reddit.com/r/framework/comments/1b6vzcy/framework_16_variable_refresh_rate/ See: https://community.frame.work/t/resolved-no-vrr-freesync-with-amd-version/42338 Link: https://gist.github.com/superm1/e8fbacfa4d0f53150231d3a3e0a13faf To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2057424/+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 2055384] Re: New NVIDIA release 550.54.14
** Changed in: nvidia-graphics-drivers-550 (Ubuntu Noble) Status: Fix Committed => Fix Released ** Also affects: nvidia-graphics-drivers-550-server (Ubuntu) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-550-server (Ubuntu Noble) Status: New => Fix Released ** Changed in: nvidia-graphics-drivers-550-server (Ubuntu Bionic) Status: New => Invalid ** Changed in: nvidia-graphics-drivers-550-server (Ubuntu Focal) Status: New => Invalid -- 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/2055384 Title: New NVIDIA release 550.54.14 Status in fabric-manager-535 package in Ubuntu: Fix Committed Status in libnvidia-nscq-535 package in Ubuntu: Fix Committed Status in nvidia-graphics-drivers-535 package in Ubuntu: Fix Committed Status in nvidia-graphics-drivers-535-server package in Ubuntu: Fix Committed Status in nvidia-graphics-drivers-550 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-550-server package in Ubuntu: Fix Released Status in fabric-manager-535 source package in Bionic: Fix Committed Status in libnvidia-nscq-535 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-535 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-535-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-550 source package in Bionic: Invalid Status in nvidia-graphics-drivers-550-server source package in Bionic: Invalid Status in fabric-manager-535 source package in Focal: Fix Committed Status in libnvidia-nscq-535 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-535 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-535-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-550 source package in Focal: Invalid Status in nvidia-graphics-drivers-550-server source package in Focal: Invalid Status in fabric-manager-535 source package in Jammy: Fix Committed Status in libnvidia-nscq-535 source package in Jammy: Fix Committed Status in nvidia-graphics-drivers-535 source package in Jammy: Fix Committed Status in nvidia-graphics-drivers-535-server source package in Jammy: Fix Committed Status in nvidia-graphics-drivers-550 source package in Jammy: Fix Released Status in nvidia-graphics-drivers-550-server source package in Jammy: New Status in fabric-manager-535 source package in Mantic: Fix Committed Status in libnvidia-nscq-535 source package in Mantic: Fix Committed Status in nvidia-graphics-drivers-535 source package in Mantic: Fix Committed Status in nvidia-graphics-drivers-535-server source package in Mantic: Fix Committed Status in nvidia-graphics-drivers-550 source package in Mantic: Fix Released Status in nvidia-graphics-drivers-550-server source package in Mantic: New Status in fabric-manager-535 source package in Noble: Fix Committed Status in libnvidia-nscq-535 source package in Noble: Fix Committed Status in nvidia-graphics-drivers-535 source package in Noble: Fix Committed Status in nvidia-graphics-drivers-535-server source package in Noble: Fix Committed Status in nvidia-graphics-drivers-550 source package in Noble: Fix Released Status in nvidia-graphics-drivers-550-server source package in Noble: Fix Released 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/2055384/+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 2055384] Re: New NVIDIA release 550.54.14
** Also affects: nvidia-graphics-drivers-550 (Ubuntu) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-550 (Ubuntu Bionic) Status: New => Fix Committed ** Changed in: nvidia-graphics-drivers-550 (Ubuntu Focal) Status: New => Fix Committed ** Changed in: nvidia-graphics-drivers-550 (Ubuntu Jammy) Status: New => Fix Committed ** Changed in: nvidia-graphics-drivers-550 (Ubuntu Noble) Status: New => Fix Committed ** Changed in: nvidia-graphics-drivers-550 (Ubuntu Bionic) Status: Fix Committed => Invalid ** Changed in: nvidia-graphics-drivers-550 (Ubuntu Mantic) Status: New => Fix Committed ** Changed in: nvidia-graphics-drivers-550 (Ubuntu Focal) Status: Fix Committed => Invalid -- 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/2055384 Title: New NVIDIA release 550.54.14 Status in fabric-manager-535 package in Ubuntu: Fix Committed Status in libnvidia-nscq-535 package in Ubuntu: Fix Committed Status in nvidia-graphics-drivers-535 package in Ubuntu: Fix Committed Status in nvidia-graphics-drivers-535-server package in Ubuntu: Fix Committed Status in nvidia-graphics-drivers-550 package in Ubuntu: Fix Committed Status in fabric-manager-535 source package in Bionic: Fix Committed Status in libnvidia-nscq-535 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-535 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-535-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-550 source package in Bionic: Invalid Status in fabric-manager-535 source package in Focal: Fix Committed Status in libnvidia-nscq-535 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-535 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-535-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-550 source package in Focal: Invalid Status in fabric-manager-535 source package in Jammy: Fix Committed Status in libnvidia-nscq-535 source package in Jammy: Fix Committed Status in nvidia-graphics-drivers-535 source package in Jammy: Fix Committed Status in nvidia-graphics-drivers-535-server source package in Jammy: Fix Committed Status in nvidia-graphics-drivers-550 source package in Jammy: Fix Committed Status in fabric-manager-535 source package in Mantic: Fix Committed Status in libnvidia-nscq-535 source package in Mantic: Fix Committed Status in nvidia-graphics-drivers-535 source package in Mantic: Fix Committed Status in nvidia-graphics-drivers-535-server source package in Mantic: Fix Committed Status in nvidia-graphics-drivers-550 source package in Mantic: Fix Committed Status in fabric-manager-535 source package in Noble: Fix Committed Status in libnvidia-nscq-535 source package in Noble: Fix Committed Status in nvidia-graphics-drivers-535 source package in Noble: Fix Committed Status in nvidia-graphics-drivers-535-server source package in Noble: Fix Committed Status in nvidia-graphics-drivers-550 source package in Noble: Fix Committed 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/2055384/+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 2042500] Re: Fix after-suspend-mediacard/sdhc-insert test failed
** Also affects: linux-oem-6.8 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-6.8 (Ubuntu Jammy) Status: New => Invalid ** Changed in: linux-oem-6.8 (Ubuntu Mantic) Status: New => Invalid -- 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/2042500 Title: Fix after-suspend-mediacard/sdhc-insert test failed Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux-oem-6.8 package in Ubuntu: New Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux-oem-6.8 source package in Jammy: Invalid Status in linux source package in Mantic: Won't Fix Status in linux-oem-6.1 source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux-oem-6.8 source package in Mantic: Invalid Status in linux source package in Noble: In Progress Status in linux-oem-6.1 source package in Noble: Invalid Status in linux-oem-6.5 source package in Noble: Invalid Status in linux-oem-6.8 source package in Noble: New Bug description: [Impact] checkbox test case, after-suspend-mediacard/sdhc-insert, failed. [Fix] Commit a7152be79b62 ("Revert "PCI/ASPM: Save L1 PM Substates Capability for suspend/resume"") reverted saving and restoring of ASPM L1 Substates due to a regression that caused resume from suspend to fail on certain systems. However, we never added this capability back and this is now causing systems fail to enter low power CPU states, drawing more power from the battery. The original revert mentioned that we restore L1 PM substate configuration even though ASPM L1 may already be enabled. This is due the fact that the pci_restore_aspm_l1ss_state() was called before pci_restore_pcie_state(). Try to enable this functionality again following PCIe r6.0.1, sec 5.5.4 more closely by: 1) Do not restore ASPM configuration in pci_restore_pcie_state() but do that after PCIe capability is restored in pci_restore_aspm_state() following PCIe r6.0, sec 5.5.4. 2) ASPM is first enabled on the upstream component and then downstream (this is already forced by the parent-child ordering of Linux Device Power Management framework). 3) Program ASPM L1 PM substate configuration before L1 enables. 4) Program ASPM L1 PM substate enables last after rest of the fields in the capability are programmed. 5) Add denylist that skips restoring on the ASUS and TUXEDO systems where these regressions happened, just in case. For the TUXEDO case we only skip restore if the BIOS is involved in system suspend (that's forcing "mem_sleep=deep" in the command line). This is to avoid possible power regression when the default suspend to idle is used, and at the same time make sure the devices continue working after resume when the BIOS is involved. [Test Case] 1. suspend and resume. 2. check if the error appears in dmesg ~~~ pcieport :00:1c.0: pciehp: Slot(5): Card not present rtsx_pci :05:00.0: Unable to change power state from D0 to D3hot, device inaccessible rtsx_pci :05:00.0: Unable to change power state from D3cold to D0, device inaccessible ~~~ [where the issue could happen] low, the patch works well on the reported malfunctioned ASUS platform too. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2042500/+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 2058330] Re: Update amd-pmf for AMD strix series
** Package changed: linux-oem (Ubuntu Noble) => linux-oem-6.8 (Ubuntu Noble) -- 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/2058330 Title: Update amd-pmf for AMD strix series Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux source package in Noble: New Status in linux-oem-6.8 source package in Noble: New Bug description: These updates will be enhanced amd-pmf for family 1AH on the supported OEM platforms, including enabling new revision for BIOS notify events, support static slider by APTS (AMD Performance and Thermal State)...etc. Needs to be backported into oem-6.8. Following are commits merged to linus tree for v6.9-rc1: * 8362e862fb879 platform/x86/amd/pmf: Update sps power thermals according to the platform-profiles * 3eecb434d7f21 platform/x86/amd/pmf: Add support to get sps default APTS index values * 48d38f569261b platform/x86/amd/pmf: Add support to get APTS index numbers for static slider * 6262938eef282 platform/x86/amd/pmf: Add support to notify sbios heart beat event * 5fdc8b82aab4c platform/x86/amd/pmf: Add support to get sbios requests in PMF driver * 233f78e11e1fa platform/x86/amd/pmf: Disable debugfs support for querying power thermals * a33e9e106601b platform/x86/amd/pmf: Differentiate PMF ACPI versions To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2058330/+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 2058808] Re: iwlwifi disconnect and crash - intel wifi7
** Changed in: linux-oem-6.5 (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/2058808 Title: iwlwifi disconnect and crash - intel wifi7 Status in HWE Next: In Progress 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 Mantic: Fix Committed Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: iwlwifi disconnecting and crashing when I using Wifi 2.4GHz. [ cut here ] Invalid rxb from HW 0 WARNING: CPU: 14 PID: 896 at drivers/net/wireless/intel/iwlwifi/pcie/rx.c:1489 iwl_pcie_rx_handle+0x3ce/0x640 [iwlwifi] Modules linked in: ccm vboxdrv(OE) rfcomm cmac algif_hash algif_skcipher af_alg bnep btusb btrtl btbcm btintel btmtk bluetooth ecdh_generic input_leds joydev ecc intel_rapl_msr intel_rapl_common intel_uncore_frequency intel_uncore_frequency_common nft_limit x86_pkg_temp_thermal intel_powerclamp coretemp iwlmvm kvm_intel xt_tcpudp xt_LOG nf_log_syslog kvm mac80211 xt_limit xt_conntrack nf_conntrack libarc4 nf_defrag_ipv6 irqbypass nf_defrag_ipv4 crct10dif_pclmul crc32_pclmul nft_compat polyval_clmulni polyval_generic nf_tables ghash_clmulni_intel libcrc32c sha256_ssse3 iwlwifi sha1_ssse3 sunrpc rapl nvidia_uvm(PO) nfnetlink binfmt_misc n xhci_pci xhci_pci_renesas nvme_common video wmi mac_hid CPU: 14 PID: 896 Comm: irq/160-iwlwifi Tainted: PW OE 6.5.0-26-generic #26~22.04.1-Ubuntu Hardware name: ASRock Z790 Nova WiFi/Z790 Nova WiFi, BIOS 3.09 12/26/2023 RIP: 0010:iwl_pcie_rx_handle+0x3ce/0x640 [iwlwifi] Code: e9 8b 43 34 83 43 30 08 83 e8 08 89 43 34 e9 70 fe ff ff 44 89 f0 89 d6 45 89 e6 41 89 c4 48 c7 c7 a8 cb 53 c4 e8 42 e4 62 e8 <0f> 0b 4c 89 ff e8 e8 3b ff ff 8b 55 d4 85 d2 0f 95 c0 41 21 c6 e9 RSP: 0018:b91d803e0e18 EFLAGS: 00010246 RAX: RBX: 956747353c30 RCX: RDX: RSI: RDI: RBP: b91d803e0e78 R08: R09: R10: R11: R12: 1007 R13: 0015 R14: R15: 956746a30028 FS: () GS:95768f38() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 02659c472000 CR3: 000112e8e000 CR4: 00752ee0 PKRU: 5554 Call Trace: ? show_regs+0x6d/0x80 ? __warn+0x89/0x160 ? iwl_pcie_rx_handle+0x3ce/0x640 [iwlwifi] ? report_bug+0x17e/0x1b0 ? handle_bug+0x46/0x90 ? exc_invalid_op+0x18/0x80 ? asm_exc_invalid_op+0x1b/0x20 ? iwl_pcie_rx_handle+0x3ce/0x640 [iwlwifi] ? iwl_pcie_rx_handle+0x3ce/0x640 [iwlwifi] ? free_unref_page+0x30/0x180 iwl_pcie_napi_poll_msix+0x32/0x100 [iwlwifi] ? skb_free_head+0xa8/0xd0 __napi_poll+0x30/0x1f0 net_rx_action+0x181/0x2e0 ? __irq_wake_thread+0x42/0x50 __do_softirq+0xd9/0x349 ? __pfx_irq_thread_fn+0x10/0x10 do_softirq.part.0+0x41/0x80 __local_bh_enable_ip+0x72/0x80 iwl_pcie_irq_rx_msix_handler+0xd7/0x1a0 [iwlwifi] irq_thread_fn+0x21/0x70 irq_thread+0xf8/0x1c0 ? __pfx_irq_thread_dtor+0x10/0x10 ? __pfx_irq_thread+0x10/0x10 kthread+0xef/0x120 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x44/0x70 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1b/0x30 ---[ end trace ]--- iwlwifi :05:00.0: Microcode SW error detected. Restarting 0x0. iwlwifi :05:00.0: Start IWL Error Log Dump: iwlwifi :05:00.0: Transport status: 0x004A, valid: 6 iwlwifi :05:00.0: Loaded firmware version: 83.ec13314b.0 gl-c0-fm-c0-83.ucode iwlwifi :05:00.0: 0x0084 | NMI_INTERRUPT_UNKNOWN iwlwifi :05:00.0: 0x0003 | trm_hw_status0 iwlwifi :05:00.0: 0x | trm_hw_status1 iwlwifi :05:00.0: 0x002C280A | branchlink2 iwlwifi :05:00.0: 0x9328 | interruptlink1 iwlwifi :05:00.0: 0x9328 | interruptlink2 iwlwifi :05:00.0: 0xF46C | data1 iwlwifi :05:00.0: 0x0100 | data2 iwlwifi :05:00.0: 0x | data3 iwlwifi :05:00.0: 0xA0005E44 | beacon time iwlwifi :05:00.0: 0x2806818F | tsf low iwlwifi :05:00.0: 0x | tsf hi iwlwifi :05:00.0: 0x | time gp1 iwlwifi :05:00.0: 0x0BB840A7 | time gp2 iwlwifi :05:00.0: 0x0001 | uCode revision type iwlwifi :05:00.0: 0x0053 | uCode version major iwlwifi :05:00.0: 0xEC13314B | uCode version minor iwlwifi :05:00.0: 0x0472 | hw version iwlwifi :05:00.0: 0x00C80002 | board version iwlwifi :05:00.0: 0x03B7001C | hcmd iwlwifi :05:00.0:
[Kernel-packages] [Bug 2058452] Re: Support USB serial port for Dell DW5826e WWAN
** Changed in: linux-oem-6.5 (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/2058452 Title: Support USB serial port for Dell DW5826e WWAN Status in HWE Next: New Status in OEM Priority Project: New Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [SRU Justification] [Impact] Missing usb serial interface for Dell DW5826e. [Fix] * commit 129690fb229a ("USB: serial: qcserial: add new usb-id for Dell Wireless DW5826e "): in v6.8 [Test Case] 1. check system with USB\VID_413C_8217 or USB\VID_413C_8218 creates corresponding tty port [Where problems could occur] The commit adds new device ID only, it won't impact devices which are supported originally. [Other Info] Upstream commit: https://github.com/torvalds/linux/commit/129690fb229a20b6e563a77a2c85266acecf20bc Dell new platform with the device will be enabled by linux-oem-6.5. The tty port will be utilized by the userspace fcc unlock program. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2058452/+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 2049714] Re: [RPL-P] igt-gpu-tool enablement
** Also affects: intel-gpu-tools (Ubuntu Noble) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to intel-gpu-tools in Ubuntu. https://bugs.launchpad.net/bugs/2049714 Title: [RPL-P] igt-gpu-tool enablement Status in intel: Fix Released Status in The Kobuk project: In Progress Status in intel-gpu-tools package in Ubuntu: In Progress Status in intel-gpu-tools source package in Noble: In Progress Bug description: [Description] igt-gpu-tool enabling for Raptor Lake-P [Hardware Information] Architecture: Intel Platform(s): Raptor Lake-P Date HW is expected at Canonical: Component(s): itg-gpu-tool [Software Information] Target Version: 22.04 Target Kernel: Commit IDs / External Links: https://gitlab.freedesktop.org/drm/igt-gpu-tools/-/commit/1b32bcdb2d9965090234739aba891a90743e01c4 [Business Justification] [Testing guidance] [External ID] To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/2049714/+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] Update Released
The verification of the Stable Release Update for firmware-sof has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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 firmware-sof package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.5 package in Ubuntu: Invalid Status in firmware-sof source package in Jammy: Fix Released Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: Fix Released Status in firmware-sof source package in Noble: Fix Released Status in linux source package in Noble: Fix Released Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [SRU Justifications] == kernels == [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. It requires the patches in https://lore.kernel.org/all/20230919103115.30783-1-peter.ujfal...@linux.intel.com/ and https://lore.kernel.org/all/20230814232325.86397-1-pierre-louis.boss...@linux.intel.com/ [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. == firmware-sof == [Impact] The mic-mute led not working on Intel MTL powered laptops. [Fix] For firmware-sof, it required the upstream commit fdc884baa4b3 ("Add sof-ipc4-v2.8.1/mtl/, intel-signed + community") and the sof-hda-generic-2ch.tplg from v2.8.1 to make sure the ipc4 topology and control matches with the updated driver. [Test Case] 1. enable -proposed pocket and install firmware-sof-signed 2. press mic-mute hot-key and check if mic-mute is enabled or not by the OSD icon. [Where problems could occur] The updated sof-mtl.ri and the sof-hda-generic-2ch.tplg are shared by all Intel MTL platforms. Need to verify audio function on MTL enpowered machines. 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 2058808] Re: iwlwifi disconnect and crash - intel wifi7
** Package changed: linux-signed-hwe-6.5 (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Importance: High => Undecided ** Changed in: linux (Ubuntu) Status: In Progress => New ** Also affects: linux (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Jammy) Status: New => Invalid ** Changed in: linux-oem-6.5 (Ubuntu Mantic) Status: New => Invalid ** Changed in: linux-oem-6.5 (Ubuntu) Status: New => Invalid -- 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/2058808 Title: iwlwifi disconnect and crash - intel wifi7 Status in linux package in Ubuntu: New 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: New Status in linux source package in Mantic: New Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: iwlwifi disconnecting and crashing when I using Wifi 2.4GHz. [ cut here ] Invalid rxb from HW 0 WARNING: CPU: 14 PID: 896 at drivers/net/wireless/intel/iwlwifi/pcie/rx.c:1489 iwl_pcie_rx_handle+0x3ce/0x640 [iwlwifi] Modules linked in: ccm vboxdrv(OE) rfcomm cmac algif_hash algif_skcipher af_alg bnep btusb btrtl btbcm btintel btmtk bluetooth ecdh_generic input_leds joydev ecc intel_rapl_msr intel_rapl_common intel_uncore_frequency intel_uncore_frequency_common nft_limit x86_pkg_temp_thermal intel_powerclamp coretemp iwlmvm kvm_intel xt_tcpudp xt_LOG nf_log_syslog kvm mac80211 xt_limit xt_conntrack nf_conntrack libarc4 nf_defrag_ipv6 irqbypass nf_defrag_ipv4 crct10dif_pclmul crc32_pclmul nft_compat polyval_clmulni polyval_generic nf_tables ghash_clmulni_intel libcrc32c sha256_ssse3 iwlwifi sha1_ssse3 sunrpc rapl nvidia_uvm(PO) nfnetlink binfmt_misc n xhci_pci xhci_pci_renesas nvme_common video wmi mac_hid CPU: 14 PID: 896 Comm: irq/160-iwlwifi Tainted: PW OE 6.5.0-26-generic #26~22.04.1-Ubuntu Hardware name: ASRock Z790 Nova WiFi/Z790 Nova WiFi, BIOS 3.09 12/26/2023 RIP: 0010:iwl_pcie_rx_handle+0x3ce/0x640 [iwlwifi] Code: e9 8b 43 34 83 43 30 08 83 e8 08 89 43 34 e9 70 fe ff ff 44 89 f0 89 d6 45 89 e6 41 89 c4 48 c7 c7 a8 cb 53 c4 e8 42 e4 62 e8 <0f> 0b 4c 89 ff e8 e8 3b ff ff 8b 55 d4 85 d2 0f 95 c0 41 21 c6 e9 RSP: 0018:b91d803e0e18 EFLAGS: 00010246 RAX: RBX: 956747353c30 RCX: RDX: RSI: RDI: RBP: b91d803e0e78 R08: R09: R10: R11: R12: 1007 R13: 0015 R14: R15: 956746a30028 FS: () GS:95768f38() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 02659c472000 CR3: 000112e8e000 CR4: 00752ee0 PKRU: 5554 Call Trace: ? show_regs+0x6d/0x80 ? __warn+0x89/0x160 ? iwl_pcie_rx_handle+0x3ce/0x640 [iwlwifi] ? report_bug+0x17e/0x1b0 ? handle_bug+0x46/0x90 ? exc_invalid_op+0x18/0x80 ? asm_exc_invalid_op+0x1b/0x20 ? iwl_pcie_rx_handle+0x3ce/0x640 [iwlwifi] ? iwl_pcie_rx_handle+0x3ce/0x640 [iwlwifi] ? free_unref_page+0x30/0x180 iwl_pcie_napi_poll_msix+0x32/0x100 [iwlwifi] ? skb_free_head+0xa8/0xd0 __napi_poll+0x30/0x1f0 net_rx_action+0x181/0x2e0 ? __irq_wake_thread+0x42/0x50 __do_softirq+0xd9/0x349 ? __pfx_irq_thread_fn+0x10/0x10 do_softirq.part.0+0x41/0x80 __local_bh_enable_ip+0x72/0x80 iwl_pcie_irq_rx_msix_handler+0xd7/0x1a0 [iwlwifi] irq_thread_fn+0x21/0x70 irq_thread+0xf8/0x1c0 ? __pfx_irq_thread_dtor+0x10/0x10 ? __pfx_irq_thread+0x10/0x10 kthread+0xef/0x120 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x44/0x70 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1b/0x30 ---[ end trace ]--- iwlwifi :05:00.0: Microcode SW error detected. Restarting 0x0. iwlwifi :05:00.0: Start IWL Error Log Dump: iwlwifi :05:00.0: Transport status: 0x004A, valid: 6 iwlwifi :05:00.0: Loaded firmware version: 83.ec13314b.0 gl-c0-fm-c0-83.ucode iwlwifi :05:00.0: 0x0084 | NMI_INTERRUPT_UNKNOWN iwlwifi :05:00.0: 0x0003 | trm_hw_status0 iwlwifi :05:00.0: 0x | trm_hw_status1 iwlwifi :05:00.0: 0x002C280A | branchlink2 iwlwifi :05:00.0: 0x9328 | interruptlink1 iwlwifi :05:00.0: 0x9328 | interruptlink2 iwlwifi :05:00.0: 0xF46C | data1 iwlwifi :05:00.0: 0x0100 | data2 iwlwifi
[Kernel-packages] [Bug 2058357] Re: noble/linux-oem-6.8: 6.8.0-1001.1 -proposed tracker
** Changed in: kernel-sru-workflow/boot-testing Status: Triaged => Invalid -- 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/2058357 Title: noble/linux-oem-6.8: 6.8.0-1001.1 -proposed tracker Status in canonical-signing-jobs task00 series: In Progress Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow abi-testing series: Invalid Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow boot-testing series: Invalid Status in Kernel SRU Workflow new-review series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-generate series: Fix Released Status in Kernel SRU Workflow prepare-package-lrg series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-lrs series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow sru-review series: Fix Released Status in linux package in Ubuntu: New Status in linux source package in Noble: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- built: from: 5938de740722141b route-entry: 2 delta: promote-to-proposed: [lrm, lrs, main, meta, signed, lrg, generate] flag: boot-testing-requested: true kernel-stable-master-bug: 2058221 packages: generate: linux-generate-oem-6.8 lrg: linux-restricted-generate-oem-6.8 lrm: linux-restricted-modules-oem-6.8 lrs: linux-restricted-signatures-oem-6.8 main: linux-oem-6.8 meta: linux-meta-oem-6.8 signed: linux-signed-oem-6.8 phase: Promote to Proposed phase-changed: Monday, 25. March 2024 15:37 UTC reason: canonical-signing-jobs/task00: Ongoing -s signing request in-progress promote-to-proposed: Ongoing -- promotion in progress variant: debs versions: lrm: 6.8.0-1001.1 main: 6.8.0-1001.1 meta: 6.8.0-1001.1 signed: 6.8.0-1001.1 ~~: clamps: new-review: 5938de740722141b promote-to-proposed: 5938de740722141b self: 6.8.0-1001.1 sru-review: 5938de740722141b tracker: last-message: '2024-03-19 09:46:02.148495+00:00' To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-signing-jobs/task00/+bug/2058357/+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 2055283] Please test proposed package
Hello Hui, 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.30 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/2055283 Title: Intel Bluetooth AX201 needs firmware intel/ibt-0180-4150.sfi 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 Mantic: Fix Committed Bug description: BugLink: https://bugs.launchpad.net/bugs/2055283 [Impact] We have an Lenovo laptop, after installing the oem-ubuntu-22.04 image and booting up, the bluetooth couldn't work at all. Checking the dmesg, the bluetooth driver needs to load the firmware intel/ibt-0180-4150.sfi, but there is no this firmware in the linux-firmware of Jammy, and I also checked the Mantic and Noble, Mandic doesn't have this firmware too, Noble already has the firmware since the upstream linux-firmware integrated the intel/ibt-0180-4150.sfi last year. [Fix] Backport 4 commits from upstream linux-firmware, these 4 commits are all on intel/ibt-0180-4150.sfi|ddc [Test Case] Put the firmware into the /lib/firmware/intel/, reboot the machine, check dmesg, the bluetooth driver loads the firmware successfully, run hciconfig, the hci0 shows up. run checkbox testcase, it could pass. [Checkbox job `com.canonical.certification::bluetooth/detect-output` output] [Where problems could occur] Probably could make the Intel AX201 BT adapter couldn't work, but the possibility is very low, we tested the firmware on different lenovo machines with the BT adapter AX201, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2055283/+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 2055283] Re: Intel Bluetooth AX201 needs firmware intel/ibt-0180-4150.sfi
Hello Hui, 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.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- 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) Status: New => Fix Released -- 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/2055283 Title: Intel Bluetooth AX201 needs firmware intel/ibt-0180-4150.sfi 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 Mantic: Fix Committed Bug description: BugLink: https://bugs.launchpad.net/bugs/2055283 [Impact] We have an Lenovo laptop, after installing the oem-ubuntu-22.04 image and booting up, the bluetooth couldn't work at all. Checking the dmesg, the bluetooth driver needs to load the firmware intel/ibt-0180-4150.sfi, but there is no this firmware in the linux-firmware of Jammy, and I also checked the Mantic and Noble, Mandic doesn't have this firmware too, Noble already has the firmware since the upstream linux-firmware integrated the intel/ibt-0180-4150.sfi last year. [Fix] Backport 4 commits from upstream linux-firmware, these 4 commits are all on intel/ibt-0180-4150.sfi|ddc [Test Case] Put the firmware into the /lib/firmware/intel/, reboot the machine, check dmesg, the bluetooth driver loads the firmware successfully, run hciconfig, the hci0 shows up. run checkbox testcase, it could pass. [Checkbox job `com.canonical.certification::bluetooth/detect-output` output] [Where problems could occur] Probably could make the Intel AX201 BT adapter couldn't work, but the possibility is very low, we tested the firmware on different lenovo machines with the BT adapter AX201, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2055283/+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 2053277] Please test proposed package
Hello Richard, 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.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- 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/2053277 Title: add the updated navi3.x DMCUB FW (ver 0x07002600) to 22.04 Jammy 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 Mantic: Fix Committed Bug description: [SRU Justification] [Impact] Devices hang up at its desktop (Intel based platform + AMD Navi3.x dGPU) during warm boot stress test. [Fix] AMD GPU dcn firmware upgrade to upstream commit bd2ad5e6 needed. The affected blob is amdgpu/dcn_3_2_0_dmcub.bin, which has stayed the first revision since Jammy is ever released. However, the related commits from the upgrade path have also included blob updates to all kinds of different, unrelated hardware models. This pull request bumps only the affected binary to the target commit per online discussion with AMD. [Test Case] Perform checkbox warmboot stress test: $ checkbox-cli run com.canonical.certification::stress/reboot [Where problems could occur] While DCN blob maybe shared with several hardware models, with confirmation from IHV, there should be little risk to upgrade it. [Other Info] Affects both Jammy and Mantic. == original bug report == Dell reported sporadically hang up at its desktop (Intel based platform + AMD Navi3.x dGPU) during warm boot stress test. After updating DMCUB firmware version to 0x07002600, they observed a significant improvement in passing rate. And Dell wants to add the updated DMCUB firmware (ver 0x7002600) to its OEM image. DMCUB firmware (ver 0x7002600) is at https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/commit/amdgpu/dcn_3_2_0_dmcub.bin?id=bd2ad5e65d3bc38fc35eed8c3dbb5e40ae45df20. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2053277/+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 2053277] Please test proposed package
Hello Richard, 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.30 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/2053277 Title: add the updated navi3.x DMCUB FW (ver 0x07002600) to 22.04 Jammy 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 Mantic: Fix Committed Bug description: [SRU Justification] [Impact] Devices hang up at its desktop (Intel based platform + AMD Navi3.x dGPU) during warm boot stress test. [Fix] AMD GPU dcn firmware upgrade to upstream commit bd2ad5e6 needed. The affected blob is amdgpu/dcn_3_2_0_dmcub.bin, which has stayed the first revision since Jammy is ever released. However, the related commits from the upgrade path have also included blob updates to all kinds of different, unrelated hardware models. This pull request bumps only the affected binary to the target commit per online discussion with AMD. [Test Case] Perform checkbox warmboot stress test: $ checkbox-cli run com.canonical.certification::stress/reboot [Where problems could occur] While DCN blob maybe shared with several hardware models, with confirmation from IHV, there should be little risk to upgrade it. [Other Info] Affects both Jammy and Mantic. == original bug report == Dell reported sporadically hang up at its desktop (Intel based platform + AMD Navi3.x dGPU) during warm boot stress test. After updating DMCUB firmware version to 0x07002600, they observed a significant improvement in passing rate. And Dell wants to add the updated DMCUB firmware (ver 0x7002600) to its OEM image. DMCUB firmware (ver 0x7002600) is at https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/commit/amdgpu/dcn_3_2_0_dmcub.bin?id=bd2ad5e65d3bc38fc35eed8c3dbb5e40ae45df20. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2053277/+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 2058483] Re: touchpad not working
** Package changed: linux-signed-hwe-6.5 (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2058483 Title: touchpad not working Status in linux package in Ubuntu: New Bug description: The touchpad is not in the xinput list and it doesn't work. I'm using hp pavilion 15 ec1021nl ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-26-generic 6.5.0-26.26~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Mar 20 14:21:02 2024 InstallationDate: Installed on 2024-03-20 (0 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash 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/+bug/2058483/+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 2058357] Re: noble/linux-oem-6.8: 6.8.0-1001.1 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- built: - from: 5938de740722141b - route-entry: 1 + from: 5938de740722141b + route-entry: 2 kernel-stable-master-bug: 2058221 packages: - generate: linux-generate-oem-6.8 - lrg: linux-restricted-generate-oem-6.8 - lrm: linux-restricted-modules-oem-6.8 - lrs: linux-restricted-signatures-oem-6.8 - main: linux-oem-6.8 - meta: linux-meta-oem-6.8 - signed: linux-signed-oem-6.8 + generate: linux-generate-oem-6.8 + lrg: linux-restricted-generate-oem-6.8 + lrm: linux-restricted-modules-oem-6.8 + lrs: linux-restricted-signatures-oem-6.8 + main: linux-oem-6.8 + meta: linux-meta-oem-6.8 + signed: linux-signed-oem-6.8 phase: Packaging phase-changed: Wednesday, 20. March 2024 14:12 UTC reason: - :prepare-packages: Pending -- building in ppa (generate:M signed:M) - prepare-package-generate: Stalled -- package not uploaded - prepare-package-signed: Stalled -- package not uploaded + :prepare-packages: Pending -- building in ppa (generate:M signed:M) + prepare-package-generate: Stalled -- package not uploaded + prepare-package-signed: Stalled -- package not uploaded variant: debs versions: - lrm: 6.8.0-1001.1 - main: 6.8.0-1001.1 - meta: 6.8.0-1001.1 - signed: 6.8.0-1001.1 + lrm: 6.8.0-1001.1 + main: 6.8.0-1001.1 + meta: 6.8.0-1001.1 + signed: 6.8.0-1001.1 ~~: - clamps: - self: 6.8.0-1001.1 - tracker: - last-message: '2024-03-19 09:46:02.148495+00:00' + clamps: + self: 6.8.0-1001.1 + tracker: + last-message: '2024-03-19 09:46:02.148495+00:00' -- 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/2058357 Title: noble/linux-oem-6.8: 6.8.0-1001.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow abi-testing series: Invalid Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow boot-testing series: Triaged Status in Kernel SRU Workflow new-review series: Triaged Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-generate series: Fix Released Status in Kernel SRU Workflow prepare-package-lrg series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-lrs series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow sru-review series: Triaged Status in linux package in Ubuntu: New Status in linux source package in Noble: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- built: from: 5938de740722141b route-entry: 2 delta: promote-to-proposed: [lrm, lrs, main, meta, signed, lrg, generate] flag: boot-testing-requested: true kernel-stable-master-bug: 2058221 packages: generate: linux-generate-oem-6.8 lrg: linux-restricted-generate-oem-6.8 lrm: linux-restricted-modules-oem-6.8 lrs: linux-restricted-signatures-oem-6.8 main: linux-oem-6.8 meta: linux-meta-oem-6.8 signed: linux-signed-oem-6.8 phase: Testing phase-changed: Thursday, 21. March 2024 08:36 UTC reason: boot-testing: Ongoing -s testing in progress new-review: Stalled -s ready for review (built) sru-review: Stalled -s ready for review (built) variant: debs versions: lrm: 6.8.0-1001.1 main: 6.8.0-1001.1 meta: 6.8.0-1001.1 signed: 6.8.0-1001.1 ~~: clamps: new-review: 5938de740722141b self: 6.8.0-1001.1 sru-review: 5938de740722141b tracker: last-message: '2024-03-19 09:46:02.148495+00:00' To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/2058357/+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 2058357] Re: noble/linux-oem-6.8: -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: - https://wiki.ubuntu.com/Kernel/kernel-sru-workflow + https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 2058221 packages: - generate: linux-generate-oem-6.8 - lrg: linux-restricted-generate-oem-6.8 - lrm: linux-restricted-modules-oem-6.8 - lrs: linux-restricted-signatures-oem-6.8 - main: supported - meta: linux-meta-oem-6.8 - signed: linux-signed-oem-6.8 + generate: linux-generate-oem-6.8 + lrg: linux-restricted-generate-oem-6.8 + lrm: linux-restricted-modules-oem-6.8 + lrs: linux-restricted-signatures-oem-6.8 + main: linux-oem-6.8 + meta: linux-meta-oem-6.8 + signed: linux-signed-oem-6.8 phase: Holding before Packaging phase-changed: Tuesday, 19. March 2024 09:51 UTC reason: - :prepare-packages: Holding -b Not ready to be cranked - prepare-package: Holding -- waiting for parent tracker + :prepare-packages: Holding -b Not ready to be cranked + prepare-package: Holding -- waiting for parent tracker variant: debs ~~: - tracker: - last-message: '2024-03-19 09:46:02.148495+00:00' + tracker: + last-message: '2024-03-19 09:46:02.148495+00:00' ** Summary changed: - noble/linux-oem-6.8: -proposed tracker + noble/linux-oem-6.8: 6.8.0-1001.1 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Timo Aaltonen (tjaalton) ** Changed in: kernel-sru-workflow/prepare-package-generate Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-generate Assignee: (unassigned) => Timo Aaltonen (tjaalton) ** Changed in: kernel-sru-workflow/prepare-package-lrg Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-lrg Assignee: (unassigned) => Timo Aaltonen (tjaalton) ** Changed in: kernel-sru-workflow/prepare-package-lrm Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-lrm Assignee: (unassigned) => Timo Aaltonen (tjaalton) ** Changed in: kernel-sru-workflow/prepare-package-lrs Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-lrs Assignee: (unassigned) => Timo Aaltonen (tjaalton) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Timo Aaltonen (tjaalton) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Timo Aaltonen (tjaalton) -- 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/2058357 Title: noble/linux-oem-6.8: 6.8.0-1001.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow abi-testing series: New Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow boot-testing series: New Status in Kernel SRU Workflow new-review series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-generate series: In Progress Status in Kernel SRU Workflow prepare-package-lrg series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: In Progress Status in Kernel SRU Workflow prepare-package-lrs series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow sru-review series: New Status in linux package in Ubuntu: New Status in linux source package in Noble: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- built: from: 84640a198fbc9fca route-entry: 1 kernel-stable-master-bug: 2058221 packages: generate: linux-generate-oem-6.8 lrg: linux-restricted-generate-oem-6.8 lrm: linux-restricted-modules-oem-6.8 lrs: li
[Kernel-packages] [Bug 2058357] Re: noble/linux-oem-6.8: -proposed tracker
** Summary changed: - noble/linux-oem-6.8: 6.8.0-1001.1 -proposed tracker + noble/linux-oem-6.8: -proposed tracker -- 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/2058357 Title: noble/linux-oem-6.8: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow abi-testing series: New Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow boot-testing series: New Status in Kernel SRU Workflow new-review series: New Status in Kernel SRU Workflow prepare-package series: New Status in Kernel SRU Workflow prepare-package-generate series: New Status in Kernel SRU Workflow prepare-package-lrg series: New Status in Kernel SRU Workflow prepare-package-lrm series: New Status in Kernel SRU Workflow prepare-package-lrs series: New Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed series: New Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow sru-review series: New Status in linux package in Ubuntu: New Status in linux source package in Noble: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 2058221 packages: generate: linux-generate-oem-6.8 lrg: linux-restricted-generate-oem-6.8 lrm: linux-restricted-modules-oem-6.8 lrs: linux-restricted-signatures-oem-6.8 main: supported meta: linux-meta-oem-6.8 signed: linux-signed-oem-6.8 phase: Holding before Packaging phase-changed: Tuesday, 19. March 2024 09:51 UTC reason: :prepare-packages: Holding -b Not ready to be cranked prepare-package: Holding -- waiting for parent tracker variant: debs ~~: clamps: self: 6.8.0-1001.1 tracker: last-message: '2024-03-19 09:46:02.148495+00:00' To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/2058357/+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 2058357] Re: noble/linux-oem-6.8: 6.8.0-1001.1 -proposed tracker
** Summary changed: - noble/linux-oem-6.8: -proposed tracker + noble/linux-oem-6.8: 6.8.0-1001.1 -proposed tracker -- 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/2058357 Title: noble/linux-oem-6.8: 6.8.0-1001.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow abi-testing series: New Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow boot-testing series: New Status in Kernel SRU Workflow new-review series: New Status in Kernel SRU Workflow prepare-package series: New Status in Kernel SRU Workflow prepare-package-generate series: New Status in Kernel SRU Workflow prepare-package-lrg series: New Status in Kernel SRU Workflow prepare-package-lrm series: New Status in Kernel SRU Workflow prepare-package-lrs series: New Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed series: New Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow sru-review series: New Status in linux package in Ubuntu: New Status in linux source package in Noble: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 2058221 packages: generate: linux-generate-oem-6.8 lrg: linux-restricted-generate-oem-6.8 lrm: linux-restricted-modules-oem-6.8 lrs: linux-restricted-signatures-oem-6.8 main: supported meta: linux-meta-oem-6.8 signed: linux-signed-oem-6.8 phase: Holding before Packaging phase-changed: Tuesday, 19. March 2024 09:51 UTC reason: :prepare-packages: Holding -b Not ready to be cranked prepare-package: Holding -- waiting for parent tracker variant: debs ~~: clamps: self: 6.8.0-1001.1 tracker: last-message: '2024-03-19 09:46:02.148495+00:00' To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/2058357/+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 2058357] Re: noble/linux-oem-6.8: -proposed tracker
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Noble) 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/2058357 Title: noble/linux-oem-6.8: 6.8.0-1001.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow abi-testing series: New Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow boot-testing series: New Status in Kernel SRU Workflow new-review series: New Status in Kernel SRU Workflow prepare-package series: New Status in Kernel SRU Workflow prepare-package-generate series: New Status in Kernel SRU Workflow prepare-package-lrg series: New Status in Kernel SRU Workflow prepare-package-lrm series: New Status in Kernel SRU Workflow prepare-package-lrs series: New Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed series: New Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow sru-review series: New Status in linux package in Ubuntu: New Status in linux source package in Noble: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 2058221 packages: generate: linux-generate-oem-6.8 lrg: linux-restricted-generate-oem-6.8 lrm: linux-restricted-modules-oem-6.8 lrs: linux-restricted-signatures-oem-6.8 main: supported meta: linux-meta-oem-6.8 signed: linux-signed-oem-6.8 phase: Holding before Packaging phase-changed: Tuesday, 19. March 2024 09:51 UTC reason: :prepare-packages: Holding -b Not ready to be cranked prepare-package: Holding -- waiting for parent tracker variant: debs ~~: tracker: last-message: '2024-03-19 09:46:02.148495+00:00' To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/2058357/+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 2053277] Re: add the updated navi3.x DMCUB FW (ver 0x07002600) to 22.04 Jammy
** Changed in: linux-firmware (Ubuntu) Status: New => Fix Released -- 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/2053277 Title: add the updated navi3.x DMCUB FW (ver 0x07002600) to 22.04 Jammy Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: New Status in linux-firmware source package in Mantic: New Bug description: Dell reported sporadically hang up at its desktop (Intel based platform + AMD Navi3.x dGPU) during warm boot stress test. After updating DMCUB firmware version to 0x07002600, they observed a significant improvement in passing rate. And Dell wants to add the updated DMCUB firmware (ver 0x7002600) to its OEM image. DMCUB firmware (ver 0x7002600) is at https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/amdgpu/dcn_3_2_0_dmcub.bin?id=bd2ad5e65d3bc38fc35eed8c3dbb5e40ae45df20. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2053277/+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 2006259] Re: net: wwan: t7xx: Fix Runtime PM implementation
** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: Incomplete => Won't Fix ** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/2006259 Title: net: wwan: t7xx: Fix Runtime PM implementation Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.0 source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: Won't Fix Status in linux source package in Kinetic: Won't Fix Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: Fix Released Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: Upstream commit d10b3a695ba0 ("net: wwan: t7xx: Runtime PM") introduced support for Runtime PM for this driver, but due to a bug in the initialization logic the usage refcount would never reach 0, leaving the feature unused. This patchset addresses that, together with a bug found after runtime suspend was enabled. https://lore.kernel.org/netdev/20230126132535.80339-1-min...@semihalf.com/ To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2006259/+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 1995779] Re: [HP Pavilion All-in-One Desktop 27-ca1xxx] USB is broken on resume from suspend
oem-6.1 is about to be EOL ** 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-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/1995779 Title: [HP Pavilion All-in-One Desktop 27-ca1xxx] USB is broken on resume from suspend Status in linux package in Ubuntu: Incomplete Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: Won't Fix Bug description: Ubuntu: 22.04 jammy Computer: HP Pavilion All-in-One Desktop 27-ca1xxx So a desktop but with a hybrid GPU setup like a laptop. GPU: NVIDIA GeForce RTX 3050 Laptop GPU + Intel(R) Graphics (ADL-S GT1) GPU driver: This happens with all Nvidia proprietary drivers tested so far, 510, 515, 520. I reported it on the latest. Kernel: This happens with all kernels tested so far from 5.15 to 6.0 Desktop: This only happens with an X11 session! If I switch to Wayland it doesn't happen. Problem: When you suspend the computer a number of strange things may happen. Lose connection to keyboard and mouse. Lose connection to USB-C Audio speakers. Stuck on black VT terminal screen. Sometimes reproduced on first try, sometimes it takes 5 tries. Switching to Wayland allows to suspend/resume perfectly however. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ernst 113040 F pulseaudio /dev/snd/controlC0: ernst 113040 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-06-15 (290 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: HP HP Pavilion All-in-One Desktop 27-ca1xxx NonfreeKernelModules: nvidia_modeset nvidia Package: linux-oem-6.1 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.1.0-1007-oem root=UUID=72ea78e1-7744-4fcc-b63c-3aa577c86a80 ro quiet splash ibt=off mitigations=off vt.handoff=7 ProcVersionSignature: Ubuntu 6.1.0-1007.7-oem 6.1.6 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-6.1.0-1007-oem N/A linux-backports-modules-6.1.0-1007-oem N/A linux-firmware 20220329.git681281e4-0ubuntu3.12 Tags: jammy wayland-session Uname: Linux 6.1.0-1007-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/09/2022 dmi.bios.release: 15.2 dmi.bios.vendor: AMI dmi.bios.version: F.02 dmi.board.name: 89E9 dmi.board.vendor: HP dmi.board.version: 0100 dmi.chassis.type: 13 dmi.chassis.vendor: HP dmi.ec.firmware.release: 1.16 dmi.modalias: dmi:bvnAMI:bvrF.02:bd02/09/2022:br15.2:efr1.16:svnHP:pnHPPavilionAll-in-OneDesktop27-ca1xxx:pvr:rvnHP:rn89E9:rvr0100:cvnHP:ct13:cvr:sku661Q7EA#UUW: dmi.product.family: 103C_53311M HP Pavilion dmi.product.name: HP Pavilion All-in-One Desktop 27-ca1xxx dmi.product.sku: 661Q7EA#UUW dmi.sys.vendor: HP modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2022-06-15T22:28:44.879144 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1995779/+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 2008188] Re: blacklist: Problem blacklisting hash
** Changed in: linux-oem-6.1 (Ubuntu) Status: Confirmed => Won't Fix ** Changed in: linux (Ubuntu) Status: Confirmed => Won't Fix -- 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/2008188 Title: blacklist: Problem blacklisting hash Status in linux package in Ubuntu: Won't Fix Status in linux-oem-6.1 package in Ubuntu: Won't Fix Bug description: When boot up the system from oem-6.1 kernel, some errors will printed in the console. Jan 04 05:28:09 Fenrir2-AMD-2 kernel: blacklist: Problem blacklisting hash (-13) Jan 04 05:28:09 Fenrir2-AMD-2 kernel: blacklist: Problem blacklisting hash (-13) Jan 04 05:28:09 Fenrir2-AMD-2 kernel: blacklist: Problem blacklisting hash (-13) Jan 04 05:28:09 Fenrir2-AMD-2 kernel: blacklist: Problem blacklisting hash (-13) Jan 04 05:28:09 Fenrir2-AMD-2 kernel: blacklist: Problem blacklisting hash (-13) Jan 04 05:28:09 Fenrir2-AMD-2 kernel: blacklist: Problem blacklisting hash (-13) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008188/+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 2016469] Re: test_maps in ubuntu_bpf failed on J-oem-6.1 ( run_parallel: Assertion `status == 0' failed.)
** 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-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2016469 Title: test_maps in ubuntu_bpf failed on J-oem-6.1 ( run_parallel: Assertion `status == 0' failed.) Status in ubuntu-kernel-tests: New Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.1 source package in Jammy: Won't Fix Bug description: Issue found in J-oem-6.1.0-1009.9 after fixing the build issue in bug 2016455. The test_maps in ubuntu_bpf will fail with: test_maps: test_maps.c:1375: __run_parallel: Assertion `status == 0' failed. Test log: Running './test_maps' Fork 100 tasks to 'test_update_delete' Fork 100 tasks to 'test_update_delete' Fork 100 tasks to 'test_update_delete' Fork 100 tasks to 'test_update_delete' Fork 100 tasks to 'test_update_delete' Fork 100 tasks to 'test_update_delete' Fork 100 tasks to 'test_update_delete' Fork 100 tasks to 'test_update_delete' Fork 100 tasks to 'test_update_delete' Fork 100 tasks to 'test_update_delete' Fork 100 tasks to 'test_update_delete' Fork 100 tasks to 'test_update_delete' Fork 100 tasks to 'test_hashmap_walk' Fork 100 tasks to 'test_hashmap' Fork 100 tasks to 'test_hashmap_percpu' Fork 100 tasks to 'test_hashmap_sizes' Fork 100 tasks to 'test_arraymap' Fork 100 tasks to 'test_arraymap_percpu' Fork 100 tasks to 'test_update_delete' Fork 100 tasks to 'test_update_delete' Fork 100 tasks to 'test_update_delete' Fork 100 tasks to 'test_update_delete' Fork 100 tasks to 'test_update_delete' Fork 100 tasks to 'test_update_delete' Fork 100 tasks to 'test_update_delete' Fork 100 tasks to 'test_update_delete' Fork 100 tasks to 'test_update_delete' Fork 100 tasks to 'test_update_delete' Fork 100 tasks to 'test_update_delete' Fork 100 tasks to 'test_update_delete' Fork 100 tasks to 'test_hashmap_walk' Fork 100 tasks to 'test_hashmap' Fork 100 tasks to 'test_hashmap_percpu' test_maps: test_maps.c:173: test_hashmap_percpu: Assertion `bpf_map_update_elem(fd, , value, BPF_ANY) == 0' failed. test_maps: test_maps.c:173: test_hashmap_percpu: Assertion `bpf_map_update_elem(fd, , value, BPF_ANY) == 0' failed. test_maps: test_maps.c:173: test_hashmap_percpu: Assertion `bpf_map_update_elem(fd, , value, BPF_ANY) == 0' failed. test_maps: test_maps.c:173: test_hashmap_percpu: Assertion `bpf_map_update_elem(fd, , value, BPF_ANY) == 0' failed. test_maps: test_maps.c:173: test_hashmap_percpu: Assertion `bpf_map_update_elem(fd, , value, BPF_ANY) == 0' failed. test_maps: test_maps.c:173: test_hashmap_percpu: Assertion `bpf_map_update_elem(fd, , value, BPF_ANY) == 0' failed. test_maps: test_maps.c:173: test_hashmap_percpu: Assertion `bpf_map_update_elem(fd, , value, BPF_ANY) == 0' failed. test_maps: test_maps.c:173: test_hashmap_percpu: Assertion `bpf_map_update_elem(fd, , value, BPF_ANY) == 0' failed. test_maps: test_maps.c:173: test_hashmap_percpu: Assertion `bpf_map_update_elem(fd, , value, BPF_ANY) == 0' failed. test_maps: test_maps.c:173: test_hashmap_percpu: Assertion `bpf_map_update_elem(fd, , value, BPF_ANY) == 0' failed. test_maps: test_maps.c:173: test_hashmap_percpu: Assertion `bpf_map_update_elem(fd, , value, BPF_ANY) == 0' failed. test_maps: test_maps.c:173: test_hashmap_percpu: Assertion `bpf_map_update_elem(fd, , value, BPF_ANY) == 0' failed. test_maps: test_maps.c:173: test_hashmap_percpu: Assertion `bpf_map_update_elem(fd, , value, BPF_ANY) == 0' failed. test_maps: test_maps.c:173: test_hashmap_percpu: Assertion `bpf_map_update_elem(fd, , value, BPF_ANY) == 0' failed. test_maps: test_maps.c:173: test_hashmap_percpu: Assertion `bpf_map_update_elem(fd, , value, BPF_ANY) == 0' failed. test_maps: test_maps.c:173: test_hashmap_percpu: Assertion `bpf_map_update_elem(fd, , value, BPF_ANY) == 0' failed. test_maps: test_maps.c:173: test_hashmap_percpu: Assertion `bpf_map_update_elem(fd, , value, BPF_ANY) == 0' failed. test_maps: test_maps.c:173: test_hashmap_percpu: Assertion `bpf_map_update_elem(fd, , value, BPF_ANY) == 0' failed. test_maps: test_maps.c:173: test_hashmap_percpu: Assertion `bpf_map_update_elem(fd, , value, BPF_ANY) == 0' failed. test_maps: test_maps.c:173: test_hashmap_percpu: Assertion `bpf_map_update_elem(fd, , value, BPF_ANY) == 0' failed. test_maps: test_maps.c:173: test_hashmap_percpu: Assertion `bpf_map_update_elem(fd, , value, BPF_ANY) == 0' failed. test_maps: test_maps.c:173: test_hashmap_percpu: Assertion `bpf_map_update_elem(fd, , value, BPF_ANY) == 0' failed. test_maps: test_maps.c:173: test_hashmap_percpu: Assertion `bpf_map_update_elem(fd, , value, BPF_ANY) == 0' failed. test_maps: test_maps.c:173: test_hashmap_percpu: Assertion `bpf_map_update_elem(fd, ,
[Kernel-packages] [Bug 2017277] Re: Regression: 6.1.0.9-1009 causes RTL8852BE WiFi to fail randomly
oem-6.1 is about to be EOL ** Changed in: linux-oem-6.1 (Ubuntu) Status: Confirmed => Won't Fix -- 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/2017277 Title: Regression: 6.1.0.9-1009 causes RTL8852BE WiFi to fail randomly Status in linux-oem-6.1 package in Ubuntu: Won't Fix Bug description: The 6.1 OEM kernel contains backported (from 6.2) support for the RTL8852BE wireless adapter. This has worked fine on my laptop since the support was backported. The latest release, 6.1.0.9-1009 is causing my adapter to occasionally stop working completely. The WiFi disconnects, and GNOME tells me an adapter cannot be found. A reboot is required to get the internet working again. This has happened twice. Running `dmesg` reports a lot of error messages with the adapter - find the output in error.txt, attached. Thanks for any help you can offer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.1/+bug/2017277/+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 2025444] Re: Mute/mic LEDs no function on some HP Platforms
** Changed in: linux-oem-6.1 (Ubuntu) Status: New => 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/2025444 Title: Mute/mic LEDs no function on some HP Platforms Status in OEM Priority Project: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Released Bug description: [Impact] The mic mute/audio mute LEDS are not work on some HP Platforms [Fix] It needs the specific quirk for the hardware layout. Thus, add the quirks to make it works. [Test] After applying the quirk on linux-oem-6.1, the audio/mic mute LEDs are working good. [Where problems could occur] If HP ships the different system boards design with the same subsystem ID of audio codec which is using different GPIO pins (different layout), then the quirk will not work (LEDs will not work when muting audio-output or microphone). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2025444/+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 2034535] Re: 6.1.0.1021.21: severe problems with f2fs
oem-6.1 is about to be EOL ** Changed in: linux-oem-6.1 (Ubuntu) Status: New => Won't Fix -- 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/2034535 Title: 6.1.0.1021.21: severe problems with f2fs Status in linux-oem-6.1 package in Ubuntu: Won't Fix Bug description: After updating my system was unusable. The kernel dropped an error message multiple times. Downgrading to 6.1.0.1020.20 fixed the issue. I have 2 f2fs partitions on 2 SSDs - one NVME, the other SATA. Since it happens in recovery mode as well, I assume that it definitively happens on the NVME disk. Not sure about SATA. lsb_release -rd: Description:KDE neon 5.27 Release:22.04 apt-cache policy ..: linux-image-6.1.0-1021-oem: Installed: (none) Candidate: 6.1.0-1021.21 Version table: 6.1.0-1021.21 500 500 http://de.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 Error messages: (from /var/log/syslog) Sep 6 11:00:04 nyarly kernel: [ 21.885763] BUG: kernel NULL pointer dereference, address: 0024 Sep 6 11:00:04 nyarly kernel: [ 21.885769] #PF: supervisor write access in kernel mode Sep 6 11:00:04 nyarly kernel: [ 21.885771] #PF: error_code(0x0002) - not-present page Sep 6 11:00:04 nyarly kernel: [ 21.885772] PGD 0 P4D 0 Sep 6 11:00:04 nyarly kernel: [ 21.885776] Oops: 0002 [#9] PREEMPT SMP PTI Sep 6 11:00:04 nyarly kernel: [ 21.885778] CPU: 3 PID: 1430 Comm: containerd Tainted: P DOE 6.1.0-1021-oem #21-Ubuntu Sep 6 11:00:04 nyarly kernel: [ 21.885781] Hardware name: System manufacturer System Product Name/H170-PRO/USB 3.1, BIOS 2002 09/20/2016 Sep 6 11:00:04 nyarly kernel: [ 21.885783] RIP: 0010:f2fs_issue_flush+0x12f/0x1a0 [f2fs] Sep 6 11:00:04 nyarly kernel: [ 21.885813] Code: c9 ba 01 00 00 00 be 03 00 00 00 e8 5b 42 66 e6 48 83 3b 00 74 1d 4c 89 f7 e8 2d 95 45 e7 f0 ff 4b 24 8b 45 cc e9 5f ff ff ff ff 43 24 e9 43 ff ff ff 31 d2 48 87 53 28 48 85 d2 74 d8 44 89 Sep 6 11:00:04 nyarly kernel: [ 21.885815] RSP: 0018:a79b0924fcb8 EFLAGS: 00010246 Sep 6 11:00:04 nyarly kernel: [ 21.885818] RAX: RBX: RCX: Sep 6 11:00:04 nyarly kernel: [ 21.885819] RDX: 10bc RSI: 001cbbda RDI: a79b0924fcf0 Sep 6 11:00:04 nyarly kernel: [ 21.885821] RBP: a79b0924fd20 R08: R09: Sep 6 11:00:04 nyarly kernel: [ 21.885823] R10: R11: R12: 99821c12a000 Sep 6 11:00:04 nyarly kernel: [ 21.885824] R13: 001cbbda R14: a79b0924fcc0 R15: 0024 Sep 6 11:00:04 nyarly kernel: [ 21.885826] FS: 7faa52ffd640() GS:998525d8() knlGS: Sep 6 11:00:04 nyarly kernel: [ 21.885828] CS: 0010 DS: ES: CR0: 80050033 Sep 6 11:00:04 nyarly kernel: [ 21.885830] CR2: 0024 CR3: 00013b2d8005 CR4: 003706e0 Sep 6 11:00:04 nyarly kernel: [ 21.885832] DR0: DR1: DR2: Sep 6 11:00:04 nyarly kernel: [ 21.885833] DR3: DR6: fffe0ff0 DR7: 0400 Sep 6 11:00:04 nyarly kernel: [ 21.885835] Call Trace: Sep 6 11:00:04 nyarly kernel: [ 21.885836] Sep 6 11:00:04 nyarly kernel: [ 21.885838] ? show_trace_log_lvl+0x1e8/0x30d Sep 6 11:00:04 nyarly kernel: [ 21.885843] ? show_trace_log_lvl+0x1e8/0x30d Sep 6 11:00:04 nyarly kernel: [ 21.885848] ? f2fs_do_sync_file+0x78e/0xaa0 [f2fs] Sep 6 11:00:04 nyarly kernel: [ 21.885865] ? show_regs.part.0+0x23/0x31 Sep 6 11:00:04 nyarly kernel: [ 21.885869] ? __die_body.cold+0x8/0xd Sep 6 11:00:04 nyarly kernel: [ 21.885872] ? __die+0x2a/0x3b Sep 6 11:00:04 nyarly kernel: [ 21.885876] ? page_fault_oops+0x174/0x1b0 Sep 6 11:00:04 nyarly kernel: [ 21.885881] ? do_user_addr_fault+0x2f3/0x5a0 Sep 6 11:00:04 nyarly kernel: [ 21.885884] ? exc_page_fault+0x80/0x1b0 Sep 6 11:00:04 nyarly kernel: [ 21.885888] ? asm_exc_page_fault+0x27/0x30 Sep 6 11:00:04 nyarly kernel: [ 21.885892] ? f2fs_issue_flush+0x12f/0x1a0 [f2fs] Sep 6 11:00:04 nyarly kernel: [ 21.885917] f2fs_do_sync_file+0x78e/0xaa0 [f2fs] Sep 6 11:00:04 nyarly kernel: [ 21.885933] ? f2fs_buffered_write_iter+0x41/0x70 [f2fs] Sep 6 11:00:04 nyarly kernel: [ 21.885950] f2fs_sync_file+0x30/0x60 [f2fs] Sep 6 11:00:04 nyarly kernel: [ 21.885966] __x64_sys_fdatasync+0x4c/0xa0 Sep 6 11:00:04 nyarly kernel: [ 21.885969] do_syscall_64+0x58/0x90 Sep 6 11:00:04 nyarly kernel: [ 21.885972] ? __x64_sys_pwrite64+0xb6/0xd0 Sep 6
[Kernel-packages] [Bug 2036625] Re: package linux-oem-6.1-tools-host (not installed) failed to install/upgrade: próba nadpisania "/lib/systemd/system/kvm_stat.service", który istnieje także w pakiecie
oem-6.1 is about to be EOL ** Changed in: linux-oem-6.1 (Ubuntu) Status: New => Won't Fix -- 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/2036625 Title: package linux-oem-6.1-tools-host (not installed) failed to install/upgrade: próba nadpisania "/lib/systemd/system/kvm_stat.service", który istnieje także w pakiecie linux-oem-5.17-tools-host 5.17.0-1035.36 Status in linux-oem-6.1 package in Ubuntu: Won't Fix Bug description: Install problem ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-oem-6.1-tools-host (not installed) ProcVersionSignature: Ubuntu 6.5.0-1003.3-oem 6.5.0 Uname: Linux 6.5.0-1003-oem x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue Sep 19 17:16:27 2023 ErrorMessage: próba nadpisania "/lib/systemd/system/kvm_stat.service", który istnieje także w pakiecie linux-oem-5.17-tools-host 5.17.0-1035.36 InstallationDate: Installed on 2023-08-27 (23 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.10 SourcePackage: linux-oem-6.1 Title: package linux-oem-6.1-tools-host (not installed) failed to install/upgrade: próba nadpisania "/lib/systemd/system/kvm_stat.service", który istnieje także w pakiecie linux-oem-5.17-tools-host 5.17.0-1035.36 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.1/+bug/2036625/+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 1983357] Re: test_021_aslr_dapper_libs from ubuntu_qrt_kernel_security failed on K-5.19 / J-OEM-6.1 / J-6.2 AMD64
** Changed in: linux-oem-6.1 (Ubuntu Lunar) Status: New => Invalid ** Changed in: linux-oem-6.1 (Ubuntu Mantic) Status: New => Invalid ** 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-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/1983357 Title: test_021_aslr_dapper_libs from ubuntu_qrt_kernel_security failed on K-5.19 / J-OEM-6.1 / J-6.2 AMD64 Status in QA Regression Testing: Invalid Status in ubuntu-kernel-tests: Invalid Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.1 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 source package in Kinetic: Invalid Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: Won't Fix Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: Fix Released Status in linux-oem-6.1 source package in Mantic: Invalid Status in linux source package in Noble: Fix Released Status in linux-oem-6.1 source package in Noble: Invalid Bug description: Issue found on 5.19.0-9.9 Kinetic AMD64 systems Test log: Running test: './test-kernel-security.py' distro: 'Ubuntu 22.10' kernel: '5.19.0-9.9 (Ubuntu 5.19.0-9.9-generic 5.19.0-rc5)' arch: 'amd64' uid: 0/0 SUDO_USER: 'ubuntu') test_021_aslr_dapper_libs (__main__.KernelSecurityTest) ASLR of libs ... (default libs native) (default libs native rekey) (default libs COMPAT) FAIL == FAIL: test_021_aslr_dapper_libs (__main__.KernelSecurityTest) ASLR of libs -- Traceback (most recent call last): File "./test-kernel-security.py", line 1770, in test_021_aslr_dapper_libs self._test_aslr('libs', expected) File "./test-kernel-security.py", line 1727, in _test_aslr self._test_aslr_all(area, expected, "default %s" % area) File "./test-kernel-security.py", line 1720, in _test_aslr_all self._test_aslr_exec(area, expected, target, name) File "./test-kernel-security.py", line 1703, in _test_aslr_exec self.assertShellExitEquals(aslr_expected, ["./%s" % (target), area, "--verbose"], msg="%s:\n" % name) File "/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/testlib.py", line 1203, in assertShellExitEquals self.assertEqual(expected, rc, msg + result + report) AssertionError: default libs COMPAT: Got exit code 1, expected 0 Command: './aslr32', 'libs', '--verbose' Output: Checking ASLR of libs: 0xf7c81790 0xf7c81790 0xf7c81790 FAIL: ASLR not functional (libs always at 0xf7c81790) -- Ran 1 test in 0.144s FAILED (failures=1) To manage notifications about this bug go to: https://bugs.launchpad.net/qa-regression-testing/+bug/1983357/+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 2009952] Re: [amdgpu][psr] Screen flickering/ tearing on 6.1/6.2/6.3 kernel
oem-6.1 is about to be EOL ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: Confirmed => Won't Fix -- 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/2009952 Title: [amdgpu][psr] Screen flickering/ tearing on 6.1/6.2/6.3 kernel Status in linux package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.1 source package in Jammy: Won't Fix Bug description: After upgrading from kernel 5.19.0-35-generic to 6.1.0-1007-oem there is occasional screen flicker/ tear. It happens around every minute; it seems connected to window/ pointer movement, but I have no clear way of reproducing. Disruption is minor, but annoying. I'm running 22.04 LTS on a new Thinkpad T14s with AMD Ryzen 6850u. The system is fully functional. No crashes, nothing breaks. Background on the use of 6.1.0-1007-oem: 5.19.0-35-generic breaks suspend/ resume on my laptop, see https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2007718. In a way, running 6.1 is a 'flight forward', since 5.15.0-67-generic (previous 22.04.1 LTS kernel) works well, with working suspend/ resume, and without screen flicker. But that's an 'old' kernel now, missing some nice improvements for the newer Ryzen APUs. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-oem-22.04c 6.1.0.1007.7 ProcVersionSignature: Ubuntu 6.1.0-1007.7-oem 6.1.6 Uname: Linux 6.1.0-1007-oem x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Mar 10 13:09:20 2023 InstallationDate: Installed on 2023-02-06 (31 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: linux-meta-oem-6.1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009952/+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 2038831] Re: Jammy update: v6.1.55 upstream stable release
** Changed in: linux-oem-6.1 (Ubuntu) Status: Confirmed => Fix Released -- 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/2038831 Title: Jammy update: v6.1.55 upstream stable release Status in linux-oem-6.1 package in Ubuntu: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Released 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.55 upstream stable release from git://git.kernel.org/ Linux 6.1.55 interconnect: Teach lockdep about icc_bw_lock order net/sched: Retire rsvp classifier drm/amdgpu: fix amdgpu_cs_p1_user_fence Revert "memcg: drop kmem.limit_in_bytes" drm/amd/display: fix the white screen issue when >= 64GB DRAM ext4: fix rec_len verify error scsi: pm8001: Setup IRQs on resume scsi: megaraid_sas: Fix deadlock on firmware crashdump ata: libahci: clear pending interrupt status ata: libata: disallow dev-initiated LPM transitions to unsupported states i2c: aspeed: Reset the i2c controller when timeout occurs tracefs: Add missing lockdown check to tracefs_create_dir() nfsd: fix change_info in NFSv4 RENAME replies selinux: fix handling of empty opts in selinux_fs_context_submount() tracing: Have option files inc the trace array ref count tracing: Have current_trace inc the trace array ref count tracing: Increase trace array ref count on enable and filter files tracing: Have event inject files inc the trace array ref count tracing: Have tracing_max_latency inc the trace array ref count btrfs: check for BTRFS_FS_ERROR in pending ordered assert btrfs: release path before inode lookup during the ino lookup ioctl btrfs: fix a compilation error if DEBUG is defined in btree_dirty_folio btrfs: fix lockdep splat and potential deadlock after failure running delayed items dm: don't attempt to queue IO under RCU protection Revert "drm/amd: Disable S/G for APUs when 64GB or more host memory" md: Put the right device in md_seq_next nvme: avoid bogus CRTO values io_uring/net: fix iter retargeting for selected buf ovl: fix incorrect fdput() on aio completion ovl: fix failed copyup of fileattr on a symlink attr: block mode changes of symlinks Revert "SUNRPC: Fail faster on bad verifier" md/raid1: fix error: ISO C90 forbids mixed declarations samples/hw_breakpoint: fix building without module unloading x86/purgatory: Remove LTO flags x86/boot/compressed: Reserve more memory for page tables panic: Reenable preemption in WARN slowpath scsi: lpfc: Fix the NULL vs IS_ERR() bug for debugfs_create_file() scsi: target: core: Fix target_cmd_counter leak riscv: kexec: Align the kexeced kernel entry x86/ibt: Suppress spurious ENDBR selftests: tracing: Fix to unmount tracefs for recovering environment scsi: qla2xxx: Fix NULL vs IS_ERR() bug for debugfs_create_dir() drm: gm12u320: Fix the timeout usage for usb_bulk_msg() nvmet-tcp: pass iov_len instead of sg->length to bvec_set_page() nvmet: use bvec_set_page to initialize bvecs block: factor out a bvec_set_page helper btrfs: compare the correct fsid/metadata_uuid in btrfs_validate_super btrfs: add a helper to read the superblock metadata_uuid MIPS: Use "grep -E" instead of "egrep" misc: fastrpc: Fix incorrect DMA mapping unmap request misc: fastrpc: Prepare to dynamic dma-buf locking specification dma-buf: Add unlocked variant of attachment-mapping functions printk: Consolidate console deferred printing printk: Keep non-panic-CPUs out of console lock interconnect: Fix locking for runpm vs reclaim kobject: Add sanity check for kset->kobj.ktype in kset_register() media: pci: ipu3-cio2: Initialise timing struct to avoid a compiler warning usb: chipidea: add workaround for chipidea PEC bug usb: ehci: add workaround for chipidea PORTSC.PEC bug misc: open-dice: make OPEN_DICE depend on HAS_IOMEM serial: cpm_uart: Avoid suspicious locking scsi: target: iscsi: Fix buffer overflow in lio_target_nacl_info_show() tools: iio: iio_generic_buffer: Fix some integer type and calculation usb: gadget: fsl_qe_udc: validate endpoint index for ch9 udc usb: cdns3: Put the cdns set active part outside the spin lock media: pci: cx23885: replace BUG with error return media: tuners: qt1010: replace BUG_ON with a regular error scsi: lpfc: Abort outstanding ELS cmds when mailbox timeout error is detected media: dvb-usb-v2: gl861: Fix null-ptr-deref in
[Kernel-packages] [Bug 2038830] Re: Jammy update: v6.1.54 upstream stable release
** Changed in: linux-oem-6.1 (Ubuntu) Status: Confirmed => Fix Released -- 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/2038830 Title: Jammy update: v6.1.54 upstream stable release Status in linux-oem-6.1 package in Ubuntu: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Released 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.54 upstream stable release from git://git.kernel.org/ Linux 6.1.54 drm/amd/display: Fix a bug when searching for insert_above_mpcc MIPS: Only fiddle with CHECKFLAGS if `need-compiler' kcm: Fix error handling for SOCK_DGRAM in kcm_sendmsg(). ixgbe: fix timestamp configuration code tcp: Fix bind() regression for v4-mapped-v6 non-wildcard address. tcp: Fix bind() regression for v4-mapped-v6 wildcard address. tcp: Factorise sk_family-independent comparison in inet_bind2_bucket_match(_addr_any). ipv6: Remove in6addr_any alternatives. ipv6: fix ip6_sock_set_addr_preferences() typo net: macb: fix sleep inside spinlock net: macb: Enable PTP unicast net/tls: do not free tls_rec on async operation in bpf_exec_tx_verdict() platform/mellanox: NVSW_SN2201 should depend on ACPI platform/mellanox: mlxbf-pmc: Fix reading of unprogrammed events platform/mellanox: mlxbf-pmc: Fix potential buffer overflows platform/mellanox: mlxbf-tmfifo: Drop jumbo frames platform/mellanox: mlxbf-tmfifo: Drop the Rx packet if no more descriptors kcm: Fix memory leak in error path of kcm_sendmsg() r8152: check budget for r8152_poll() net: dsa: sja1105: block FDB accesses that are concurrent with a switch reset net: dsa: sja1105: serialize sja1105_port_mcast_flood() with other FDB accesses net: dsa: sja1105: fix multicast forwarding working only for last added mdb entry net: dsa: sja1105: propagate exact error code from sja1105_dynamic_config_poll_valid() net: dsa: sja1105: hide all multicast addresses from "bridge fdb show" net:ethernet:adi:adin1110: Fix forwarding offload net: ethernet: adi: adin1110: use eth_broadcast_addr() to assign broadcast address hsr: Fix uninit-value access in fill_frame_info() net: ethernet: mtk_eth_soc: fix possible NULL pointer dereference in mtk_hwlro_get_fdir_all() net: ethernet: mvpp2_main: fix possible OOB write in mvpp2_ethtool_get_rxnfc() net: stmmac: fix handling of zero coalescing tx-usecs net/smc: use smc_lgr_list.lock to protect smc_lgr_list.list iterate in smcr_port_add selftests: Keep symlinks, when possible kselftest/runner.sh: Propagate SIGTERM to runner child net: ipv4: fix one memleak in __inet_del_ifa() kunit: Fix wild-memory-access bug in kunit_free_suite_set() drm/amdgpu: register a dirty framebuffer callback for fbcon drm/amd/display: Remove wait while locked drm/amd/display: always switch off ODM before committing more streams perf hists browser: Fix the number of entries for 'e' key perf tools: Handle old data in PERF_RECORD_ATTR perf test shell stat_bpf_counters: Fix test on Intel perf hists browser: Fix hierarchy mode header MIPS: Fix CONFIG_CPU_DADDI_WORKAROUNDS `modules_install' regression KVM: SVM: Skip VMSA init in sev_es_init_vmcb() if pointer is NULL KVM: SVM: Set target pCPU during IRTE update if target vCPU is running KVM: nSVM: Load L1's TSC multiplier based on L1 state, not L2 state KVM: nSVM: Check instead of asserting on nested TSC scaling support KVM: SVM: Get source vCPUs from source VM for SEV-ES intrahost migration KVM: SVM: Don't inject #UD if KVM attempts to skip SEV guest insn KVM: SVM: Take and hold ir_list_lock when updating vCPU's Physical ID entry drm/amd/display: prevent potential division by zero errors drm/amd/display: enable cursor degamma for DCN3+ DRM legacy gamma mtd: rawnand: brcmnand: Fix ECC level field setting for v7.2 controller mtd: rawnand: brcmnand: Fix potential false time out warning mtd: spi-nor: Correct flags for Winbond w25q128 mtd: rawnand: brcmnand: Fix potential out-of-bounds access in oob write mtd: rawnand: brcmnand: Fix crash during the panic_write drm/mxsfb: Disable overlay plane in mxsfb_plane_overlay_atomic_disable() btrfs: use the correct superblock to compare fsid in btrfs_validate_super btrfs: zoned: re-enable metadata over-commit for zoned mode btrfs: set page extent mapped after read_folio in relocate_one_page btrfs: don't start transaction when joining with
[Kernel-packages] [Bug 2038832] Re: Jammy update: v6.1.56 upstream stable release
** Changed in: linux-oem-6.1 (Ubuntu) Status: Confirmed => Fix Released ** Changed in: oem-priority Status: New => Fix Released -- 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/2038832 Title: Jammy update: v6.1.56 upstream stable release Status in OEM Priority Project: Fix Released Status in linux-oem-6.1 package in Ubuntu: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Released 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.56 upstream stable release from git://git.kernel.org/ Linux 6.1.56 ASoC: amd: yc: Fix a non-functional mic on Lenovo 82TL mm, memcg: reconsider kmem.limit_in_bytes deprecation memcg: drop kmem.limit_in_bytes drm/meson: fix memory leak on ->hpd_notify callback drm/amdkfd: Use gpu_offset for user queue's wptr fs: binfmt_elf_efpic: fix personality for ELF-FDPIC power: supply: ab8500: Set typing and props power: supply: rk817: Add missing module alias drm/i915/gt: Fix reservation address in ggtt_reserve_guc_top ata: libata-sata: increase PMP SRST timeout to 10s ata: libata-core: Do not register PM operations for SAS ports ata: libata-core: Fix port and device removal ata: libata-core: Fix ata_port_request_pm() locking fs/smb/client: Reset password pointer to NULL net: thunderbolt: Fix TCPv6 GSO checksum calculation bpf: Fix BTF_ID symbol generation collision in tools/ bpf: Fix BTF_ID symbol generation collision bpf: Add override check to kprobe multi link attach media: uvcvideo: Fix OOB read btrfs: properly report 0 avail for very full file systems ring-buffer: Update "shortest_full" in polling mm: memcontrol: fix GFP_NOFS recursion in memory.high enforcement mm/slab_common: fix slab_caches list corruption after kmem_cache_destroy() mm/damon/vaddr-test: fix memory leak in damon_do_test_apply_three_regions() arm64: defconfig: remove CONFIG_COMMON_CLK_NPCM8XX=y drm/tests: Fix incorrect argument in drm_test_mm_insert_range timers: Tag (hr)timer softirq as hotplug safe Revert "SUNRPC dont update timeout value on connection reset" netfilter: nf_tables: fix kdoc warnings after gc rework sched/rt: Fix live lock between select_fallback_rq() and RT push kernel/sched: Modify initial boot task idle setup ASoC: amd: yc: Fix non-functional mic on Lenovo 82QF and 82UG i2c: i801: unregister tco_pdev in i801_probe() error path io_uring/fs: remove sqe->rw_flags checking from LINKAT ata: libata-scsi: ignore reserved bits for REPORT SUPPORTED OPERATION CODES ata: libata-scsi: link ata port and scsi device LoongArch: numa: Fix high_memory calculation LoongArch: Define relocation types for ABI v2.10 ALSA: hda: Disable power save for solving pop issue on Lenovo ThinkCentre M70q netfilter: nf_tables: disallow rule removal from chain binding nilfs2: fix potential use after free in nilfs_gccache_submit_read_data() serial: 8250_port: Check IRQ data before use Revert "tty: n_gsm: fix UAF in gsm_cleanup_mux" misc: rtsx: Fix some platforms can not boot and move the l1ss judgment to probe mptcp: fix bogus receive window shrinkage with multiple subflows KVM: x86/mmu: Do not filter address spaces in for_each_tdp_mmu_root_yield_safe() KVM: x86/mmu: Open code leaf invalidation from mmu_notifier KVM: SVM: Fix TSC_AUX virtualization setup KVM: SVM: INTERCEPT_RDTSCP is never intercepted anyway x86/srso: Add SRSO mitigation for Hygon processors x86/sgx: Resolves SECS reclaim vs. page fault for EAUG race iommu/arm-smmu-v3: Fix soft lockup triggered by arm_smmu_mm_invalidate_range smack: Retrieve transmuting information in smack_inode_getsecurity() smack: Record transmuting in smk_transmuted nvme-pci: always return an ERR_PTR from nvme_pci_alloc_dev scsi: qla2xxx: Fix NULL pointer dereference in target mode wifi: ath11k: Don't drop tx_status when peer cannot be found nvme-pci: do not set the NUMA node of device if it has none nvme-pci: factor out a nvme_pci_alloc_dev helper nvme-pci: factor the iod mempool creation into a helper perf build: Define YYNOMEM as YYNOABORT for bison < 3.81 fbdev/sh7760fb: Depend on FB=y LoongArch: Set all reserved memblocks on Node#0 at initialization tsnep: Fix NAPI polling with budget 0 tsnep: Fix NAPI scheduling net: hsr: Add __packed to struct hsr_sup_tlv. ncsi: Propagate carrier gain/loss events to the NCSI controller
[Kernel-packages] [Bug 2039174] Re: Jammy update: v6.1.57 upstream stable release
** Changed in: linux-oem-6.1 (Ubuntu) Status: Confirmed => Fix Released -- 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/2039174 Title: Jammy update: v6.1.57 upstream stable release Status in linux-oem-6.1 package in Ubuntu: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Released 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.57 upstream stable release from git://git.kernel.org/ Linux 6.1.57 xen/events: replace evtchn_rwlock with RCU ipv6: remove one read_lock()/read_unlock() pair in rt6_check_neigh() btrfs: file_remove_privs needs an exclusive lock in direct io write netlink: remove the flex array from struct nlmsghdr btrfs: fix fscrypt name leak after failure to join log transaction btrfs: fix an error handling path in btrfs_rename() vrf: Fix lockdep splat in output path ipv6: remove nexthop_fib6_nh_bh() parisc: Restore __ldcw_align for PA-RISC 2.0 processors ksmbd: fix uaf in smb20_oplock_break_ack ksmbd: fix race condition between session lookup and expire x86/sev: Use the GHCB protocol when available for SNP CPUID requests RDMA/mlx5: Fix NULL string error RDMA/mlx5: Fix mutex unlocking on error flow for steering anchor creation RDMA/siw: Fix connection failure handling RDMA/srp: Do not call scsi_done() from srp_abort() RDMA/uverbs: Fix typo of sizeof argument RDMA/cma: Fix truncation compilation warning in make_cma_ports RDMA/cma: Initialize ib_sa_multicast structure to 0 when join gpio: pxa: disable pinctrl calls for MMP_GPIO gpio: aspeed: fix the GPIO number passed to pinctrl_gpio_set_config() IB/mlx4: Fix the size of a buffer in add_port_entries() of: dynamic: Fix potential memory leak in of_changeset_action() RDMA/core: Require admin capabilities to set system parameters dm zoned: free dmz->ddev array in dmz_put_zoned_devices parisc: Fix crash with nr_cpus=1 option smb: use kernel_connect() and kernel_bind() intel_idle: add Emerald Rapids Xeon support HID: intel-ish-hid: ipc: Disable and reenable ACPI GPE bit HID: sony: remove duplicate NULL check before calling usb_free_urb() netlink: annotate data-races around sk->sk_err netlink: Fix potential skb memleak in netlink_ack netlink: split up copies in the ack construction sctp: update hb timer immediately after users change hb_interval sctp: update transport state when processing a dupcook packet tcp: fix delayed ACKs for MSS boundary condition tcp: fix quick-ack counting to count actual ACKs of new data tipc: fix a potential deadlock on >lock net: stmmac: dwmac-stm32: fix resume on STM32 MCU ipv4: Set offload_failed flag in fibmatch results netfilter: nf_tables: nft_set_rbtree: fix spurious insertion failure netfilter: nf_tables: Deduplicate nft_register_obj audit logs selftests: netfilter: Extend nft_audit.sh selftests: netfilter: Test nf_tables audit logging netfilter: handle the connecting collision properly in nf_conntrack_proto_sctp ibmveth: Remove condition to recompute TCP header checksum. net: ethernet: ti: am65-cpsw: Fix error code in am65_cpsw_nuss_init_tx_chns() net: nfc: llcp: Add lock when modifying device list net: usb: smsc75xx: Fix uninit-value access in __smsc75xx_read_reg ipv6: tcp: add a missing nf_reset_ct() in 3WHS handling net: dsa: mv88e6xxx: Avoid EEPROM timeout when EEPROM is absent ptp: ocp: Fix error handling in ptp_ocp_device_init ipv4, ipv6: Fix handling of transhdrlen in __ip{,6}_append_data() neighbour: fix data-races around n->output neighbour: switch to standard rcu, instead of rcu_bh neighbour: annotate lockless accesses to n->nud_state bpf: Add BPF_FIB_LOOKUP_SKIP_NEIGH for bpf_fib_lookup net: fix possible store tearing in neigh_periodic_work() modpost: add missing else to the "of" check bpf, sockmap: Reject sk_msg egress redirects to non-TCP sockets bpf, sockmap: Do not inc copied_seq when PEEK flag set bpf: tcp_read_skb needs to pop skb regardless of seq NFSv4: Fix a nfs4_state_manager() race ima: rework CONFIG_IMA dependency block scsi: target: core: Fix deadlock due to recursive locking ima: Finish deprecation of IMA_TRUSTED_KEYRING Kconfig regulator/core: regulator_register: set device->class earlier iommu/mediatek: Fix share pgtable for iova over 4GB perf/x86/amd: Do not WARN() on every IRQ wifi: mac80211: fix potential key use-after-free regmap:
[Kernel-packages] [Bug 2006056] Re: package linux-oem-6.1-tools-host (not installed) failed to install/upgrade: trying to overwrite '/lib/systemd/system/kvm_stat.service', which is also in package lin
it shouldn't have built that package, but oem-6.1 is about to EOL so it won't get this fixed ** Changed in: linux-oem-6.1 (Ubuntu) Status: New => Won't Fix -- 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/2006056 Title: package linux-oem-6.1-tools-host (not installed) failed to install/upgrade: trying to overwrite '/lib/systemd/system/kvm_stat.service', which is also in package linux-tools-host 5.15.0-58.64 Status in linux-oem-6.1 package in Ubuntu: Won't Fix Bug description: Faliure to install. trying to overwrite file in linux-ttols-host ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-oem-6.1-tools-host (not installed) ProcVersionSignature: Ubuntu 5.19.0-28.29~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass Date: Sun Feb 5 11:40:05 2023 DuplicateSignature: package:linux-oem-6.1-tools-host:(not installed) Unpacking linux-oem-6.0-tools-host (6.0.0-1010.10) ... dpkg: error processing archive /tmp/apt-dpkg-install-MljDYl/15-linux-oem-6.0-tools-host_6.0.0-1010.10_all.deb (--unpack): trying to overwrite '/lib/systemd/system/kvm_stat.service', which is also in package linux-tools-host 5.15.0-58.64 ErrorMessage: trying to overwrite '/lib/systemd/system/kvm_stat.service', which is also in package linux-tools-host 5.15.0-58.64 InstallationDate: Installed on 2022-12-22 (45 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 SourcePackage: linux-oem-6.1 Title: package linux-oem-6.1-tools-host (not installed) failed to install/upgrade: trying to overwrite '/lib/systemd/system/kvm_stat.service', which is also in package linux-tools-host 5.15.0-58.64 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.1/+bug/2006056/+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 2048077] Re: Migrate oem-6.1 to oem-6.5
** Changed in: linux-meta-oem-6.5 (Ubuntu Jammy) Status: New => Fix Committed ** Changed in: linux-restricted-modules-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-meta-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2048077 Title: Migrate oem-6.1 to oem-6.5 Status in linux-meta-oem-6.5 package in Ubuntu: Invalid Status in linux-restricted-modules-oem-6.5 package in Ubuntu: Invalid Status in linux-meta-oem-6.5 source package in Jammy: Fix Committed Status in linux-restricted-modules-oem-6.5 source package in Jammy: Fix Committed Bug description: [Impact] Migrate oem-6.1 to oem-6.5, because some platforms need it instead of hwe-6.5. [Test case] Update a machine with oem-6.1 metapackages to the proposed ones, and verify that all packages (including nvidia etc) migrate properly. [Where things could go wrong] In theory we might miss a package to transition, but at this point this is unlikely. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-oem-6.5/+bug/2048077/+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 2051612] Re: False key press suspend wakeup on AMD Framework 13
that commit is included since -1014.15 ** No longer affects: ubuntu ** Package changed: linux-meta-oem-6.5 (Ubuntu) => linux-oem-6.5 (Ubuntu) ** Changed in: linux-oem-6.5 (Ubuntu) Status: New => 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/2051612 Title: False key press suspend wakeup on AMD Framework 13 Status in linux-oem-6.5 package in Ubuntu: Fix Released Bug description: Affects: Ubuntu 22.04.3 OEM C kernel. What is expected: Close the lid to suspend, expecting it to remain in a suspended state. What is happening instead: The Laptop 13 (AMD Ryzen 7040Series) BIOS 03.03 has a workaround included in the EC firmware that will cause the EC to emit a "spurious" key press during the resume from s0i3 [1]. There is a workaround described as follows: /etc/udev/rules.d/20-suspend-fixes.rules with ACTION=="add", SUBSYSTEM=="serio", DRIVERS=="atkbd", ATTR{power/wakeup}="disabled" Provides a workaround. Mario Limonciello points out this is not backported to the OEM kernel, so the fix may need to happen here. https://community.frame.work/t/responded-waking-from-sleep-when-plugged-in-amd-k-ubuntu-22-04/44168/10 Here is the Linux commit itself: https://github.com/torvalds/linux/commit/a55bdad5dfd1efd4ed9ffe518897a21ca8e4e193 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.5/+bug/2051612/+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 2057785] Re: Mute/mic LEDs no function on some HP EliteBook
** Changed in: linux-oem-6.5 (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/2057785 Title: Mute/mic LEDs no function on some HP EliteBook Status in OEM Priority Project: Confirmed Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux-oem-6.5 source package in Mantic: Won't Fix Status in linux-oem-6.5 source package in Noble: Won't Fix Bug description: [Impact] The mic mute/audio mute LEDS are not work on HP EliteBook [Fix] It needs the specific quirk for the hardware layout. Thus, add the quirks to make it works. [Test] After applying the quirk, the audio/mic mute LEDs are working good. [Where problems could occur] If HP ships the different system boards design with the same subsystem ID of audio codec which is using different GPIO pins (different layout), then the quirk will not work (LEDs will not work when muting audio-output or microphone). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2057785/+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 2057785] Re: Mute/mic LEDs no function on some HP EliteBook
please add a task for 'linux' even if it's already fixed there ** Changed in: linux-oem-6.5 (Ubuntu) Status: Confirmed => Invalid ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => 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/2057785 Title: Mute/mic LEDs no function on some HP EliteBook Status in OEM Priority Project: Confirmed Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux-oem-6.5 source package in Jammy: In Progress Status in linux-oem-6.5 source package in Mantic: Won't Fix Status in linux-oem-6.5 source package in Noble: Won't Fix Bug description: [Impact] The mic mute/audio mute LEDS are not work on HP EliteBook [Fix] It needs the specific quirk for the hardware layout. Thus, add the quirks to make it works. [Test] After applying the quirk, the audio/mic mute LEDs are working good. [Where problems could occur] If HP ships the different system boards design with the same subsystem ID of audio codec which is using different GPIO pins (different layout), then the quirk will not work (LEDs will not work when muting audio-output or microphone). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2057785/+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 2054773] Re: Fix AMD brightness issue on AUO panel
** Changed in: linux-oem-6.5 (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/2054773 Title: Fix AMD brightness issue on AUO panel 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: Won't Fix 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 Bug description: [Impact] When change brightness quickly on gnome menu, AUO panel will be stuck in previous brightness. [Fix] The TCON is random hung by PSR-SU. Force enable ffu mode on PSR-SU panel. [Test] Tested on hardware, the brightness is changed as expected. [Where problems could occur] It may break AMD display. The commit is already in v6.8-rc5, the platform is not fully supported in Jammy 5.15, So SRU oem-6.5 and mantic. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2054773/+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 2036736] Re: i915: Backport some fixes for Meteor Lake, vol3
not worth it at this point ** Changed in: linux-oem-6.5 (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-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2036736 Title: i915: Backport some fixes for Meteor Lake, vol3 Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux-oem-6.5 source package in Jammy: Won't Fix Bug description: WIP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.5/+bug/2036736/+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 2055866] Re: Simplify kcontrol naming on Intel MTL platforms
** Changed in: linux-oem-6.5 (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/2055866 Title: Simplify kcontrol naming on Intel MTL platforms 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: Fix Committed Status in linux source package in Mantic: New Status in linux-oem-6.5 source package in Mantic: New Status in linux source package in Noble: New Status in linux-oem-6.5 source package in Noble: New Bug description: [Impact] We found some laptops from Lenovo and HP with Intel MTL platform suffer the same MIC-Mute led not working problem just like lp:2049569. [Fix] lp:2049569 adds switch/enum type of control on IPC4 to communicate correctly with MTL SoF FW. However, Lenovo and HP machines requires the additional patches from https://lore.kernel.org/all/20230814232325.86397-1-pierre-louis.boss...@linux.intel.com/ to fix the kcontrol naming problem to align with the MTL SoF FW. [Test Case] 1. Make sure the latest firmware-sof is installed. 2. press mic-mute hot-key and check if mic-mute is enabled or not by the OSD icon. 3. 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. We may need more MTL machines to make sure the behavior is the aligned. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2055866/+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 2056418] Re: Fix headphone mic detection issue on ALC897
** Changed in: linux-oem-6.5 (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/2056418 Title: Fix headphone mic detection issue on ALC897 Status in HWE Next: 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: In Progress Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux source package in Mantic: In Progress Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: In Progress Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] Headphone mic is lost after resume from S3 or reboot with plugin. [Fix] Restore the headphone mic detect logic for ALC897 after lost power. [Test] Tested on hardware, the headphone mic appears as plugin after boot or resume from S3, and works fine. [Where problems could occur] It may break ALC897 sound input. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2056418/+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 2057430] Re: The screen brightness is unable to adjust on BOE panel DPN#R6FD8
** Changed in: linux-oem-6.5 (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/2057430 Title: The screen brightness is unable to adjust on BOE panel DPN#R6FD8 Status in HWE Next: New 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: In Progress 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] The screen brightness is unable to adjust on BOE panel DPN#R6FD8 [Fix] AMD provides a patch which is included in v6.8-rc7 to fix this issue b7cdccc6a849 drm/amd/display: Add monitor patch for specific eDP To avoid conflicts, pull in 3 other small patches c4e532f75336 drm/amd/display: Re-add aux intercept disable delay generically for 2+ LTTPRs 923bbfe6c888 drm/amd/display: Clear dpcd_sink_ext_caps if not set 3d71a8726e05 drm/amd/display: Add monitor patch for specific eDP [Test Case] 1. Boot to OS 2. Adjust the screen brightness via the hotkeys on the keyboard or brightness bar in the setting. 3. The screen brightness should change [Where problems could occur] The first commit introduces no functional changes, it merely relocates the delay flag to dc_debug_options and makes some consequent modifications. The second commit introduce a new flag, but we don't use it. The third and forth commits add 4 panel IDs which should be pretty safe to include them. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2057430/+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 2049358] Re: mtk_t7xx WWAN module fails to probe with: Invalid device status 0x1
** Changed in: linux-oem-6.5 (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/2049358 Title: mtk_t7xx WWAN module fails to probe with: Invalid device status 0x1 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 Mantic: In Progress Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: In Progress Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] No modems were found sometimtes after reboot/poweroff Got below messages when it fails [ 1.294786] mtk_t7xx :05:00.0: enabling device ( -> 0002) [ 1.298085] mtk_t7xx :05:00.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) [ 1.298108] mtk_t7xx :05:00.0: device [14c3:4d75] error status/mask=0010/0040 [ 1.298123] mtk_t7xx :05:00.0: [20] UnsupReq (First) [ 1.298136] mtk_t7xx :05:00.0: AER: TLP Header: 4001 000f 88824030 3e800100 [ 1.298460] mtk_t7xx :05:00.0: AER: can't recover (no error_detected callback) [ 3.302402] mtk_t7xx :05:00.0: Invalid device status 0x1 [Fix] Fibocom provides a fix for this issue which is included in linux-next now https://patchwork.kernel.org/project/netdevbpf/cover/meyp282mb26974aacdba0a16649d6f094bb...@meyp282mb2697.ausp282.prod.outlook.com/ 2dac6381c3da net: wwan: t7xx: Add fastboot WWAN port d27553c14f06 net: wwan: t7xx: Infrastructure for early port configuration 409c38d4f156 net: wwan: t7xx: Add sysfs attribute for device state machine e3caf184107a wwan: core: Add WWAN fastboot port type [Test Case] 1. Boot to OS. 2. Insert sim card to the system. 3. Check the gnome-settings with WWAN settings or check with command mmcli -L 4. Repeat 1, 2, 3 multiple times and make sure WWAN always exists and works well [Where problems could occur] Hard to tell, but ODM and us did some tests and confirmed the WWAN doesn't keep working during 1900 reboot stress test. = At booting up: mtk_t7xx :56:00.0: enabling device ( -> 0002) mtk_t7xx :56:00.0: Invalid device status 0x1 mtk_t7xx :56:00.0: Port AT is not opened, drop packets mtk_t7xx :56:00.0: Packet drop on channel 0x1004, port not found And at suspending: mtk_t7xx :56:00.0: Not ready for system sleep mtk_t7xx :56:00.0: PM: device_prepare(): pci_pm_prepare+0x0/0x80 returns -110 mtk_t7xx :56:00.0: PM: not prepared for power transition: code -110 PM: Some devices failed to suspend, or early wake event detected --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1157 F pulseaudio CasperMD5CheckMismatches: ./preseed/project.cfg CasperMD5CheckResult: fail DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-jammy-amd64-20231228-670 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-12-28 (18 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - pc-stella-jammy-amd64-20231228-670 MachineType: HP HP Elite x360 830 13 inch G11 2-in-1 Notebook PC Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-3011-oem root=UUID=34294b64-68b6-4f94-9606-9be6144aa431 ro automatic-oem-config quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.5.0-3011.12-oem 6.5.3 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.5.0-3011-oem N/A linux-backports-modules-6.5.0-3011-oem N/A linux-firmware 20220329.git681281e4-0ubuntu3.24 Tags: jammy Uname: Linux 6.5.0-3011-oem x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 01/05/2024 dmi.bios.release: 1.1 dmi.bios.vendor: HP dmi.bios.version: W70 Ver. 01.01.01 dmi.board.name: 8C26 dmi.board.vendor: HP dmi.board.version: KBC Version 02.35.00 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.ec.firmware.release: 2.53 dmi.modalias:
[Kernel-packages] [Bug 2049569] Re: Enable the mic-mute led on Dell MTL laptops
Are you able to test this on mantic with mantic kernel? If not, skip mantic. -- 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 firmware-sof package in Ubuntu: Confirmed Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.5 package in Ubuntu: Invalid Status in firmware-sof source package in Jammy: Confirmed Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: Fix Released Status in firmware-sof source package in Noble: Confirmed Status in linux source package in Noble: Fix Released Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [SRU Justifications] == kernels == [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. It requires the patches in https://lore.kernel.org/all/20230919103115.30783-1-peter.ujfal...@linux.intel.com/ and https://lore.kernel.org/all/20230814232325.86397-1-pierre-louis.boss...@linux.intel.com/ [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. == firmware-sof == [Impact] The mic-mute led not working on Intel MTL powered laptops. [Fix] For firmware-sof, it required the upstream commit fdc884baa4b3 ("Add sof-ipc4-v2.8.1/mtl/, intel-signed + community") and the sof-hda-generic-2ch.tplg from v2.8.1 to make sure the ipc4 topology and control matches with the updated driver. [Test Case] 1. enable -proposed pocket and install firmware-sof-signed 2. press mic-mute hot-key and check if mic-mute is enabled or not by the OSD icon. [Where problems could occur] The updated sof-mtl.ri and the sof-hda-generic-2ch.tplg are shared by all Intel MTL platforms. Need to verify audio function on MTL enpowered machines. 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 2049758] Re: DP connection swap to break eDP behavior on AMD 7735U
marking the kernel task as fixed since noble has 6.8 now. ** Changed in: linux (Ubuntu Noble) Status: New => 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/2049758 Title: DP connection swap to break eDP behavior on AMD 7735U Status in linux package in Ubuntu: Fix Released Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Mantic: Won't Fix Status in linux-firmware source package in Mantic: Fix Released Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: Fix Released Status in linux-firmware source package in Noble: Fix Released Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] Some OEM platforms swap DP connections on the Rembrandt-R, which causes improper eDP behavior. The following issues will occur in these designs: - Fn key failed to control brightness - eDP remains black screen during S0i3 cycle AMD has fixed these issues, but it requires both a kernel patch and an updated DMCUB microcode. [Test Plan] Validate brightness control works. Validate that PSR works. Validate that eDP works after suspend/resume. Validate that external display works. Run above test plan on Rembrandt or Rembrandt-R system with swapped DP as well as one without swapped DP. [Where problems can occur] The code and DMCUB microcode are localized to AMD Rembrandt/Rembrandt-R systems. Issues would occur specifically on these designs, which is why they should be tested. [Other Info] Patch: https://github.com/torvalds/linux/commit/b17ef04bf3a4346d66404454d6a646343ddc9749 DMCUB FW: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=2909bf41a051601e86129a9c2fcebf31c15eebc8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049758/+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 2049758] Re: DP connection swap to break eDP behavior on AMD 7735U
even though this wasn't able to get verified with the mantic kernel, I've gone ahead and released it as the update should not break anything -- 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/2049758 Title: DP connection swap to break eDP behavior on AMD 7735U Status in linux package in Ubuntu: Fix Released Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Mantic: Won't Fix Status in linux-firmware source package in Mantic: Fix Released Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: Fix Released Status in linux-firmware source package in Noble: Fix Released Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] Some OEM platforms swap DP connections on the Rembrandt-R, which causes improper eDP behavior. The following issues will occur in these designs: - Fn key failed to control brightness - eDP remains black screen during S0i3 cycle AMD has fixed these issues, but it requires both a kernel patch and an updated DMCUB microcode. [Test Plan] Validate brightness control works. Validate that PSR works. Validate that eDP works after suspend/resume. Validate that external display works. Run above test plan on Rembrandt or Rembrandt-R system with swapped DP as well as one without swapped DP. [Where problems can occur] The code and DMCUB microcode are localized to AMD Rembrandt/Rembrandt-R systems. Issues would occur specifically on these designs, which is why they should be tested. [Other Info] Patch: https://github.com/torvalds/linux/commit/b17ef04bf3a4346d66404454d6a646343ddc9749 DMCUB FW: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=2909bf41a051601e86129a9c2fcebf31c15eebc8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049758/+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 2034103] Update Released
The verification of the Stable Release Update for linux-firmware has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/2034103 Title: Missing firmware for AMD GPU GC 11.0.3 Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux-firmware package in Ubuntu: Fix Released Status in linux source package in Jammy: Invalid Status in linux-firmware source package in Jammy: Fix Committed Status in linux source package in Lunar: Won't Fix Status in linux-firmware source package in Lunar: Won't Fix Bug description: [Impact] linux-firmare is missing updates to amdgpu VCN 4.0.0 firmware for Navi32 hardware. Of the original list below, only VCN fw update is missing still. [Test case] Install the update Validate brightness control works. Validate that PSR works. Validate that eDP works after suspend/resume. Validate that external display works. [Where problems could happen] This is new hw, where the current fw isn't fresh enough. It can't regress other hw. -- Add new FWs for GPU with GC 11.0.3: * https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=d6d655ade8fed37b93631ef17e406afc4fff5f21 ("amdgpu: add initial GC 11.0.3 firmware") * https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=b1a7d7624fd227ebbc46a04a34fdcd08795ee69c ("amdgpu: add initial PSP 13.0.10 firmware") * https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=b3f512fb5386e462269ad5a43fbbed6b19fd4b4f ("amdgpu: add initial SDMA 6.0.3 firmware") * https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=22fb12f2f61a3748b155fe083fe71b79bad7c897 ("amdgpu: add initial SMU 13.0.10 firmware") * https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=59fbffa9ec8e4b0b31d2d13e715cf6580ad0e99c ("amdgpu: update VCN 4.0.0 firmware") To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2034103/+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] Update Released
The verification of the Stable Release Update for linux-firmware has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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: Fix Released Status in linux-firmware source package in Jammy: Fix Committed Status in linux-firmware source package in Lunar: Won't Fix Status in linux-firmware source package in Mantic: Fix Committed Status in linux-firmware source package in Noble: Fix Released Bug description: [SRU Justification] BugLink: https://bugs.launchpad.net/bugs/2048977 [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: 'hot reset' assert 2nd PCIe reset' assert Asmedia 'hot reset' deassert PT21 GPIO13 2nd PCIe reset' deassert. In certain caes, the WIFI link training failed while system resumes from suspend. [Fix] Upstream commits: 5217b76bed90 ("ath11k: WCN6855 hw2.0: update to WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.37") 324cc56975d7 ("ath11k: WCN6855 hw2.0: update board-2.bin") And Jammy takes an additional commit d1dc30480f ("ath11k: WCN6855 hw2.0: update board-2.bin"), 17509e53b97b ("ath11k: WCN6855 hw2.0: update to WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.36") 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 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 2049220] Update Released
The verification of the Stable Release Update for linux-firmware has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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: Fix Released 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: Fix Released Bug description: [SRU Justification] BugLink: https://bugs.launchpad.net/bugs/2049220 [Impact] MT7921 - IPv6 no longer working (Not receiving Multicast). [Fix] Update WiFi/Bluetooth firmware to upstream commits: * WiFI: commit 0a18a7292a66 ("linux-firmware: update firmware for MT7921 WiFi device") * Bluetooth: commit 1366b827c213 ("linux-firmware: update firmware for mediatek bluetooth chip (MT7921)") [Test Case] 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. [Where problems could occur] Opaque binary. No known dependency to kernel version. [Other Info] Nominate Jammy for linux-oem-6.5/jammy and linux-hwe-6.5/jammy, and Mantic. All the commits are in upstream repository, so Noble should have them after rebased. == original bug report == 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 2049758] Update Released
The verification of the Stable Release Update for linux-firmware has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/2049758 Title: DP connection swap to break eDP behavior on AMD 7735U Status in linux package in Ubuntu: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-firmware source package in Jammy: Fix Committed Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Mantic: Won't Fix Status in linux-firmware source package in Mantic: Fix Committed Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: New Status in linux-firmware source package in Noble: Fix Released Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] Some OEM platforms swap DP connections on the Rembrandt-R, which causes improper eDP behavior. The following issues will occur in these designs: - Fn key failed to control brightness - eDP remains black screen during S0i3 cycle AMD has fixed these issues, but it requires both a kernel patch and an updated DMCUB microcode. [Test Plan] Validate brightness control works. Validate that PSR works. Validate that eDP works after suspend/resume. Validate that external display works. Run above test plan on Rembrandt or Rembrandt-R system with swapped DP as well as one without swapped DP. [Where problems can occur] The code and DMCUB microcode are localized to AMD Rembrandt/Rembrandt-R systems. Issues would occur specifically on these designs, which is why they should be tested. [Other Info] Patch: https://github.com/torvalds/linux/commit/b17ef04bf3a4346d66404454d6a646343ddc9749 DMCUB FW: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=2909bf41a051601e86129a9c2fcebf31c15eebc8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049758/+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 2051636] Update Released
The verification of the Stable Release Update for linux-firmware has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/2051636 Title: AMD phoenix/phoenix2 platforms facing amdgpu(PHX) hangs during stress loading 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 Mantic: Fix Committed Status in linux-firmware source package in Noble: Fix Released Bug description: [SRU Justification] [Impact] With stress tool like 3DMark or GravityMark, facing amdgpu(PHX) hangs within a few minutes or sometimes even quicker [Fix] Upstream firmware fixes for Phoenix (GC 11.0.1)/Phoenix 2 (GC 11.0.4), and other prerequisites: * amdgpu/gc_11_0_1_* up to commit 56c0e7e ("amdgpu: update GC 11.0.1 firmware") * amdgpu/psp_13_0_4_ta.bin up to commit ed7ddfb ("amdgpu: update PSP 13.0.4 firmware") * amdgpu/vcn_4_0_2.bin up to commit 34ccb75 ("amdgpu: update VCN 4.0.2 firmware") * amdgpu/gc_11_0_4_* up to commit 680d98c ("amdgpu: update GC 11.0.4 firmware") * amdgpu/psp_13_0_11_ta.bin up to commit 72227fe ("amdgpu: update PSP 13.0.11 firmware") [Test Case] Run stress tool like 3DMark or GravityMark. [Where problems could occur] Binary firmware update recommended by chip vendor. No known issue so far. [Other Info] Phoenix is supported in linux-oem-6.5/jammy, so linux-firmware/jammy is also nominated for fix. == original bug report == With stress tool like 3DMark or GravityMark, facing amdgpu(PHX) hangs within a few minutes or sometimes even quicker. Also using mantic + v6.7 hit the hang, so need to update new FWs to fix this issue. PHX series https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=680d98c62b13bd441949280c77ca31efb021b68a https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=72227fe463af85648523300543287a68e6c6de5f https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=56c0e7e688427270729fce6e85ecd98f1fe2a6e1 https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=ed7ddfb5d136c3b9b1eeb48f7568550c0e5d99da https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=34ccb7502e075607682f0f0984a83022bfa0da85 [ 415.782623] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, signaled seq=27035, emitted seq=27037 [ 415.782833] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process gnome-shell pid 1361 thread gnome-shel:cs0 pid 1421 [ 415.783004] amdgpu :0d:00.0: amdgpu: GPU reset begin! [ 415.944129] [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3 [ 415.944317] [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue [ 416.074161] [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3 [ 416.074327] [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue [ 416.204184] [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3 [ 416.204356] [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue [ 416.334204] [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3 [ 416.334377] [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue [ 416.464226] [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3 [ 416.464398] [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue [ 416.594247] [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3 [ 416.594418] [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue [ 416.724265] [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3 [ 416.724432] [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue [ 416.854275] [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3 [ 416.854437] [drm:amdgpu_mes_unmap_legacy_queue
[Kernel-packages] [Bug 2054487] Re: There is sound from the speakers and headphones at the same time on Oasis 14 and 16 platforms
missing verification for oem-6.1 -- 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/2054487 Title: There is sound from the speakers and headphones at the same time on Oasis 14 and 16 platforms Status in HWE Next: New 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: Fix Committed Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux source package in Mantic: In Progress Status in linux-oem-6.1 source package in Mantic: Invalid 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.1 source package in Noble: Invalid Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] While playing audio with headset plugged, the sound play from both headset and internal speaker. [Fix] The commit from v6.5-rc5 fixes the issue fddab35fd064 ALSA: hda/realtek: add IDs for Dell dual spk platform [Test Case] 1. play an audio file. 2. plug 3.5mm headset. 3. select "headset". 4. sound will play only from headset [Where problems could occur] It simply added 2 IDs to the table, should have no impact to the existing machines. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2054487/+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 1988836] Update Released
The verification of the Stable Release Update for ubuntu-drivers-common has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1988836 Title: LRMv7: Enable the open NVIDIA kernel modules Status in linux-restricted-modules package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-515 package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in linux-restricted-modules source package in Focal: Fix Released Status in nvidia-graphics-drivers-515 source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Focal: Fix Released Status in linux-restricted-modules source package in Jammy: Fix Released Status in nvidia-graphics-drivers-515 source package in Jammy: Fix Released Status in ubuntu-drivers-common source package in Jammy: Fix Released Bug description: [ Impact ] * The 515 series introduced open kernel modules for the NVIDIA driver. They come with an open source licence, and should be provided as an option for datacenter GPUs: https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/ Currently, this is only production-ready (and enabled) on datacenter GPUs. * We should enable signed modules for the 515-open drivers, giving users the option to try the drivers. * The ubuntu-drivers tool should set a lower priority for the -open flavour, so that we do not end up recommending it over the plain 515 flavour. [ Test Plan ] * [ubuntu-drivers-common]: "sudo ubuntu-drivers install (to make sure the driver is not installed by default)" * [nvidia driver] "sudo ubuntu-drivers install nvidia:515-open" to make sure that the driver can be installed manually. Please make sure that this installs the correct linux-restricted- modules. Note: support for GeForce and Workstation GPUs is alpha-quality, and is disabled by default. This means that desktop testing is not needed at the moment. [ Where problems could occur ] * This adds a new driver combination, which is not meant to be default, and is only enabled for a limited amount of devices (datacenter GPUs). * We need to be sure that the driver is not recommended over the other drivers. [ Other Info ] - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+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 1988836] Re: LRMv7: Enable the open NVIDIA kernel modules
fixing the tag, surely that tag was meant to be added on 2023-06-09 instead of "verification-needed-done" :) ** Tags removed: verification-needed-done ** Tags added: verification-done-focal ** Tags removed: removal-candidate -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1988836 Title: LRMv7: Enable the open NVIDIA kernel modules Status in linux-restricted-modules package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-515 package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in linux-restricted-modules source package in Focal: Fix Released Status in nvidia-graphics-drivers-515 source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Focal: Fix Committed Status in linux-restricted-modules source package in Jammy: Fix Released Status in nvidia-graphics-drivers-515 source package in Jammy: Fix Released Status in ubuntu-drivers-common source package in Jammy: Fix Released Bug description: [ Impact ] * The 515 series introduced open kernel modules for the NVIDIA driver. They come with an open source licence, and should be provided as an option for datacenter GPUs: https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/ Currently, this is only production-ready (and enabled) on datacenter GPUs. * We should enable signed modules for the 515-open drivers, giving users the option to try the drivers. * The ubuntu-drivers tool should set a lower priority for the -open flavour, so that we do not end up recommending it over the plain 515 flavour. [ Test Plan ] * [ubuntu-drivers-common]: "sudo ubuntu-drivers install (to make sure the driver is not installed by default)" * [nvidia driver] "sudo ubuntu-drivers install nvidia:515-open" to make sure that the driver can be installed manually. Please make sure that this installs the correct linux-restricted- modules. Note: support for GeForce and Workstation GPUs is alpha-quality, and is disabled by default. This means that desktop testing is not needed at the moment. [ Where problems could occur ] * This adds a new driver combination, which is not meant to be default, and is only enabled for a limited amount of devices (datacenter GPUs). * We need to be sure that the driver is not recommended over the other drivers. [ Other Info ] - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+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 2036742] Re: VI dGPU fails to initialize on Intel platforms w/ 5.14+
** Changed in: linux (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2036742 Title: VI dGPU fails to initialize on Intel platforms w/ 5.14+ Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Confirmed Status in linux source package in Lunar: Won't Fix Status in linux source package in Mantic: Confirmed Bug description: [Impact] Booting from USB the latest Mantic Desktop daily image (2023-09-20), just after the initial logs, nothing is displayed on screen. The system is still alive since _autoinstall_ works as intended. Once provisioned, the problem is still present. It seems related to https://bugs.launchpad.net/ubuntu/+source/linux- firmware/+bug/2029396 . dmesg attached. [Test Case] Live boot Ubuntu Mantic Desktop canary (2023-09-19) [Where Problems Could Occur] Dell Optiplex 5090 - Intel Core(TM) i7-11700 - Advanced Micro Devices, Inc. [AMD/ATI] - 1002:699f To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036742/+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 2049758] Re: DP connection swap to break eDP behavior on AMD 7735U
** Tags added: verification-needed-mantic -- 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/2049758 Title: DP connection swap to break eDP behavior on AMD 7735U Status in linux package in Ubuntu: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-firmware source package in Jammy: Fix Committed Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Mantic: Won't Fix Status in linux-firmware source package in Mantic: Fix Committed Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: New Status in linux-firmware source package in Noble: Fix Released Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] Some OEM platforms swap DP connections on the Rembrandt-R, which causes improper eDP behavior. The following issues will occur in these designs: - Fn key failed to control brightness - eDP remains black screen during S0i3 cycle AMD has fixed these issues, but it requires both a kernel patch and an updated DMCUB microcode. [Test Plan] Validate brightness control works. Validate that PSR works. Validate that eDP works after suspend/resume. Validate that external display works. Run above test plan on Rembrandt or Rembrandt-R system with swapped DP as well as one without swapped DP. [Where problems can occur] The code and DMCUB microcode are localized to AMD Rembrandt/Rembrandt-R systems. Issues would occur specifically on these designs, which is why they should be tested. [Other Info] Patch: https://github.com/torvalds/linux/commit/b17ef04bf3a4346d66404454d6a646343ddc9749 DMCUB FW: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=2909bf41a051601e86129a9c2fcebf31c15eebc8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049758/+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: verification-needed-mantic -- 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: Fix Released 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: Fix Released Bug description: [SRU Justification] BugLink: https://bugs.launchpad.net/bugs/2049220 [Impact] MT7921 - IPv6 no longer working (Not receiving Multicast). [Fix] Update WiFi/Bluetooth firmware to upstream commits: * WiFI: commit 0a18a7292a66 ("linux-firmware: update firmware for MT7921 WiFi device") * Bluetooth: commit 1366b827c213 ("linux-firmware: update firmware for mediatek bluetooth chip (MT7921)") [Test Case] 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. [Where problems could occur] Opaque binary. No known dependency to kernel version. [Other Info] Nominate Jammy for linux-oem-6.5/jammy and linux-hwe-6.5/jammy, and Mantic. All the commits are in upstream repository, so Noble should have them after rebased. == original bug report == 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 2051636] Re: AMD phoenix/phoenix2 platforms facing amdgpu(PHX) hangs during stress loading
** Tags added: verification-needed-mantic -- 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/2051636 Title: AMD phoenix/phoenix2 platforms facing amdgpu(PHX) hangs during stress loading 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 Mantic: Fix Committed Status in linux-firmware source package in Noble: Fix Released Bug description: [SRU Justification] [Impact] With stress tool like 3DMark or GravityMark, facing amdgpu(PHX) hangs within a few minutes or sometimes even quicker [Fix] Upstream firmware fixes for Phoenix (GC 11.0.1)/Phoenix 2 (GC 11.0.4), and other prerequisites: * amdgpu/gc_11_0_1_* up to commit 56c0e7e ("amdgpu: update GC 11.0.1 firmware") * amdgpu/psp_13_0_4_ta.bin up to commit ed7ddfb ("amdgpu: update PSP 13.0.4 firmware") * amdgpu/vcn_4_0_2.bin up to commit 34ccb75 ("amdgpu: update VCN 4.0.2 firmware") * amdgpu/gc_11_0_4_* up to commit 680d98c ("amdgpu: update GC 11.0.4 firmware") * amdgpu/psp_13_0_11_ta.bin up to commit 72227fe ("amdgpu: update PSP 13.0.11 firmware") [Test Case] Run stress tool like 3DMark or GravityMark. [Where problems could occur] Binary firmware update recommended by chip vendor. No known issue so far. [Other Info] Phoenix is supported in linux-oem-6.5/jammy, so linux-firmware/jammy is also nominated for fix. == original bug report == With stress tool like 3DMark or GravityMark, facing amdgpu(PHX) hangs within a few minutes or sometimes even quicker. Also using mantic + v6.7 hit the hang, so need to update new FWs to fix this issue. PHX series https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=680d98c62b13bd441949280c77ca31efb021b68a https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=72227fe463af85648523300543287a68e6c6de5f https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=56c0e7e688427270729fce6e85ecd98f1fe2a6e1 https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=ed7ddfb5d136c3b9b1eeb48f7568550c0e5d99da https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=34ccb7502e075607682f0f0984a83022bfa0da85 [ 415.782623] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, signaled seq=27035, emitted seq=27037 [ 415.782833] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process gnome-shell pid 1361 thread gnome-shel:cs0 pid 1421 [ 415.783004] amdgpu :0d:00.0: amdgpu: GPU reset begin! [ 415.944129] [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3 [ 415.944317] [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue [ 416.074161] [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3 [ 416.074327] [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue [ 416.204184] [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3 [ 416.204356] [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue [ 416.334204] [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3 [ 416.334377] [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue [ 416.464226] [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3 [ 416.464398] [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue [ 416.594247] [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3 [ 416.594418] [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue [ 416.724265] [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3 [ 416.724432] [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue [ 416.854275] [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3 [ 416.854437] [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue [ 416.984284] [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3 [ 416.984456] [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue [ 416.996743] amdgpu :0d:00.0: amdgpu: MODE2 reset [ 417.026498] amdgpu :0d:00.0: amdgpu: GPU reset succeeded, trying to resume [ 417.026909] [drm]