[Kernel-packages] [Bug 2063529] Re: Add support for Quectel RM520N-GL modem
** Changed in: linux-oem-6.5 (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-oem-6.5 (Ubuntu Mantic) Status: Invalid => In Progress ** Changed in: linux (Ubuntu Mantic) Status: New => In Progress ** Changed in: linux (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/2063529 Title: Add support for Quectel RM520N-GL modem Status in HWE Next: In Progress Status in OEM Priority Project: Confirmed Status in linux package in Ubuntu: New Status in linux-oem-6.5 package in Ubuntu: New Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: In Progress Status in linux source package in Mantic: In Progress Status in linux-oem-6.5 source package in Mantic: In Progress Bug description: [Impact] * Add support for Quectel RM520N-GL modem, so the device could be properly probed. [Test Plan] * Check output of `sudo lspci -vs $DEVICE`, and the `Kernel driver in use` is mht-pci-generic. [Where problems could occur] * These commits only introduces a PID, it won't impact devices which are supported originally. [Other Info] * Upstream commits: https://github.com/torvalds/linux/commit/1cad976a1be9e97ceca5797b7e1000e2f1a9980e https://github.com/torvalds/linux/commit/7b672d703e76094595500afe67db29a4c9763081 * Lenovo with this device will be enabled by linux-oem-6.5. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2063529/+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
I tested linux-image-6.5.0-1021-oem on ThinkPad L15 Gen4 with 10 boots(20
suspends/resumes for each boot).
Cannot reproduce this bug anyway, considered fixed.
---
To: Aussems J.a.c. (ramcsir)
To: Ganton (ganton)
The SKU we hold here, rarely reproduces this issue on the previous
kernels, we would be much appreciated if you can help to verify the fix
as well according to #20 and #22.
** 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/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:
Fix Committed
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 2063529] Re: Add support for Quectel RM520N-GL modem
** Description changed: [Impact] * Add support for Quectel RM520N-GL modem, so the device could be properly probed. [Test Plan] * Check output of `sudo lspci -vs $DEVICE`, and the `Kernel driver in use` is mht-pci-generic. [Where problems could occur] - * The commit only introduces a PID, it won't impact devices which are + * These commits only introduces a PID, it won't impact devices which are supported originally. [Other Info] - * Upstream commits: - https://github.com/torvalds/linux/commit/1cad976a1be9e97ceca5797b7e1000e2f1a9980e - https://github.com/torvalds/linux/commit/7b672d703e76094595500afe67db29a4c9763081 + * Upstream commits: + https://github.com/torvalds/linux/commit/1cad976a1be9e97ceca5797b7e1000e2f1a9980e + https://github.com/torvalds/linux/commit/7b672d703e76094595500afe67db29a4c9763081 * Lenovo with this device will be enabled by linux-oem-6.5. ** Tags added: oem-priority originate-from-2045276 sutton ** Changed in: oem-priority Assignee: (unassigned) => Atlas Yu (pseudoc) ** Changed in: oem-priority Status: New => Confirmed ** Changed in: oem-priority Importance: Undecided => Critical ** Changed in: hwe-next Assignee: (unassigned) => Atlas Yu (pseudoc) ** Changed in: hwe-next Status: New => In Progress -- 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/2063529 Title: Add support for Quectel RM520N-GL modem Status in HWE Next: In Progress Status in OEM Priority Project: Confirmed Status in linux package in Ubuntu: New Status in linux-oem-6.5 package in Ubuntu: New Bug description: [Impact] * Add support for Quectel RM520N-GL modem, so the device could be properly probed. [Test Plan] * Check output of `sudo lspci -vs $DEVICE`, and the `Kernel driver in use` is mht-pci-generic. [Where problems could occur] * These commits only introduces a PID, it won't impact devices which are supported originally. [Other Info] * Upstream commits: https://github.com/torvalds/linux/commit/1cad976a1be9e97ceca5797b7e1000e2f1a9980e https://github.com/torvalds/linux/commit/7b672d703e76094595500afe67db29a4c9763081 * Lenovo with this device will be enabled by linux-oem-6.5. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2063529/+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 2063529] [NEW] Add support for Quectel RM520N-GL modem
Public bug reported: [Impact] * Add support for Quectel RM520N-GL modem, so the device could be properly probed. [Test Plan] * Check output of `sudo lspci -vs $DEVICE`, and the `Kernel driver in use` is mht-pci-generic. [Where problems could occur] * These commits only introduces a PID, it won't impact devices which are supported originally. [Other Info] * Upstream commits: https://github.com/torvalds/linux/commit/1cad976a1be9e97ceca5797b7e1000e2f1a9980e https://github.com/torvalds/linux/commit/7b672d703e76094595500afe67db29a4c9763081 * Lenovo with this device will be enabled by linux-oem-6.5. ** Affects: hwe-next Importance: Undecided Assignee: Atlas Yu (pseudoc) Status: In Progress ** Affects: oem-priority Importance: Critical Assignee: Atlas Yu (pseudoc) Status: Confirmed ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux-oem-6.5 (Ubuntu) Importance: Undecided Status: New ** Tags: oem-priority originate-from-2045276 sutton ** Also affects: hwe-next Importance: Undecided Status: New ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2063529 Title: Add support for Quectel RM520N-GL modem Status in HWE Next: In Progress Status in OEM Priority Project: Confirmed Status in linux package in Ubuntu: New Status in linux-oem-6.5 package in Ubuntu: New Bug description: [Impact] * Add support for Quectel RM520N-GL modem, so the device could be properly probed. [Test Plan] * Check output of `sudo lspci -vs $DEVICE`, and the `Kernel driver in use` is mht-pci-generic. [Where problems could occur] * These commits only introduces a PID, it won't impact devices which are supported originally. [Other Info] * Upstream commits: https://github.com/torvalds/linux/commit/1cad976a1be9e97ceca5797b7e1000e2f1a9980e https://github.com/torvalds/linux/commit/7b672d703e76094595500afe67db29a4c9763081 * Lenovo with this device will be enabled by linux-oem-6.5. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2063529/+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 2063399] Re: Add support for Quectel EM160R-GL modem
** Changed in: hwe-next Status: New => Fix Committed ** Changed in: hwe-next Status: Fix Committed => In Progress ** Tags added: oem-priority originate-from-2045276 sutton ** Changed in: oem-priority Assignee: (unassigned) => Atlas Yu (pseudoc) ** Changed in: oem-priority Status: New => Confirmed ** Changed in: oem-priority Importance: Undecided => Critical -- 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/2063399 Title: Add support for Quectel EM160R-GL modem Status in HWE Next: In Progress Status in OEM Priority Project: Confirmed 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: In Progress Status in linux source package in Mantic: In Progress Status in linux-oem-6.5 source package in Mantic: In Progress Bug description: [Impact] * Add support for Quectel EM160R-GL modem, so the device could be properly probed. [Test Plan] * Check output of `sudo lspci -vs $DEVICE`, and the `Kernel driver in use` is mht-pci-generic. [Where problems could occur] * The commit only introduces a PID, it won't impact devices which are supported originally. [Other Info] * Upstream commit: https://github.com/torvalds/linux/commit/110f113a4898e8a45ea14a3b0108cfcd7ecd52d5 * Lenovo with this device will be enabled by linux-oem-6.5. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2063399/+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 2063399] [NEW] Add support for Quectel EM160R-GL modem
Public bug reported: [Impact] * Add support for Quectel EM160R-GL modem, so the device could be properly probed. [Test Plan] * Check output of `sudo lspci -vs $DEVICE`, and the `Kernel driver in use` is mht-pci-generic. [Where problems could occur] * The commit only introduces a PID, it won't impact devices which are supported originally. [Other Info] * Upstream commit: https://github.com/torvalds/linux/commit/110f113a4898e8a45ea14a3b0108cfcd7ecd52d5 * Lenovo with this device will be enabled by linux-oem-6.5. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux-oem-6.5 (Ubuntu) Importance: Undecided Status: New ** Description changed: [Impact] * Add support for Quectel EM160R-GL modem, so the device could be properly probed. [Test Plan] * Check output of `sudo lspci -vs $DEVICE`, and the `Kernel driver in use` is mht-pci-generic. [Where problems could occur] - The commit only introduces a PID, it won't impact devices which are + * The commit only introduces a PID, it won't impact devices which are supported originally. [Other Info] * Upstream commit: https://github.com/torvalds/linux/commit/110f113a4898e8a45ea14a3b0108cfcd7ecd52d5 * Lenovo with this device will be enabled by linux-oem-6.5. ** Also affects: hwe-next Importance: Undecided Status: New -- 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/2063399 Title: Add support for Quectel EM160R-GL modem Status in HWE Next: New Status in linux-oem-6.5 package in Ubuntu: New Bug description: [Impact] * Add support for Quectel EM160R-GL modem, so the device could be properly probed. [Test Plan] * Check output of `sudo lspci -vs $DEVICE`, and the `Kernel driver in use` is mht-pci-generic. [Where problems could occur] * The commit only introduces a PID, it won't impact devices which are supported originally. [Other Info] * Upstream commit: https://github.com/torvalds/linux/commit/110f113a4898e8a45ea14a3b0108cfcd7ecd52d5 * Lenovo with this device will be enabled by linux-oem-6.5. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2063399/+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 2047518] Re: Fix BCM57416 lost after resume
verified work on a ThinkStation device. -- 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/2047518 Title: Fix BCM57416 lost after resume 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: In Progress 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] BCM57416 is lost after resume. Error log: [ 1261.429834] bnxt_en :82:00.1 enp130s0f1np1: hwrm req_type 0x50 seq id 0x125d error 0x4 [ 1261.429843] bnxt_en :82:00.1 enp130s0f1np1: hwrm_ring_alloc type 1 failed. rc:ffe4 err:4 [ 1261.429846] bnxt_en :82:00.1 enp130s0f1np1: hwrm ring alloc failure rc: fffb [ 1261.437389] bnxt_en :82:00.1 enp130s0f1np1: bnxt_init_nic err: fffb [Fix] Clear the reservations in driver after reset the ethernet card. [Test] Tested on hardware, after 10 times of suspend/resume, bnxt ethernet works fine. [Where problems could occur] It may break broadcom bnxt driver. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2047518/+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 2045205] Re: "spi-nor spi0.1:Software reset failed:-524" in shutdown screen
Lenovo crew also verified this on 2 ThinkStation device. -- 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/2045205 Title: "spi-nor spi0.1:Software reset failed:-524" in shutdown screen 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] There is a spi error message on the screen when shutting down the machine. It won't hurt anything and all device work well in the next boot up. Intel SPI controller doesn't support reset command, but our customer feel bad about this message. [Fix] Distinguish the error code -EOPNOTSUPP from -ENOTSUPP, and not showing the warnning when it's op not supported. https://lkml.org/lkml/2023/11/29/62 [Test case] 1. boot up the system with intel SPI controller on it 2. power off the system and check if there are spi software reset failed errors on the screen. [Where problems could occur] There is a minor risk of breaking user-space applications that rely on specific return codes for unsupported operations. However, this risk is considered low, as such use-cases are unlikely to be common or critical. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2045205/+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 2043786] Re: RTL8111EPP: Fix the network lost after resume with DASH
verified on 1 device with RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10EC:8168] ** 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/2043786 Title: RTL8111EPP: Fix the network lost after resume with DASH Status in HWE Next: In Progress 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 source package in Jammy: Won't Fix 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 Lunar: In Progress Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux-oem-6.5 source package in Lunar: Invalid 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 Bug description: [Impact] On the system installed RTL8111EPP with DASH, unable to get the network back upon system resume [Fix] handle DASH during system suspend and resume. [Test] Vendor tested on hardware, the ethernet is OK after resume. [Where problems could occur] It may break r8169 driver. No SRU for Jammy 5.15 kernel due to too many commits are needed to backport to support DASH. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2043786/+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 2043786] Re: RTL8111EPP: Fix the network lost after resume with DASH
verified on 4 devices with RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10EC:8168] ** Tags removed: verification-needed-jammy-linux-oem-6.1 ** Tags added: verification-done-jammy-linux-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/2043786 Title: RTL8111EPP: Fix the network lost after resume with DASH Status in HWE Next: In Progress 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 source package in Jammy: Won't Fix 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 Lunar: In Progress Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux-oem-6.5 source package in Lunar: Invalid 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 Bug description: [Impact] On the system installed RTL8111EPP with DASH, unable to get the network back upon system resume [Fix] handle DASH during system suspend and resume. [Test] Vendor tested on hardware, the ethernet is OK after resume. [Where problems could occur] It may break r8169 driver. No SRU for Jammy 5.15 kernel due to too many commits are needed to backport to support DASH. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2043786/+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 2038832] Re: Jammy update: v6.1.56 upstream stable release
** Tags added: oem-priority originate-from-2039774 sutton -- 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: New Status in linux-oem-6.1 package in Ubuntu: Confirmed Status in linux-oem-6.1 source package in Jammy: New Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.1.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 powerpc/watchpoints: Annotate atomic context in more places powerpc/watchpoint: Disable pagefaults when getting
[Kernel-packages] [Bug 2035358] Re: Jammy update: v6.1.52 upstream stable release
** Tags added: oem-priority originate-from-2035056 sutton ** 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/2035358 Title: Jammy update: v6.1.52 upstream stable release 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: 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.52 upstream stable release from git://git.kernel.org/ Linux 6.1.52 pinctrl: amd: Don't show `Invalid config param` errors usb: typec: tcpci: clear the fault status bit nilfs2: fix WARNING in mark_buffer_dirty due to discarded buffer reuse nilfs2: fix general protection fault in nilfs_lookup_dirty_data_buffers() dt-bindings: sc16is7xx: Add property to change GPIO function tcpm: Avoid soft reset when partner does not support get_status fsi: master-ast-cf: Add MODULE_FIRMWARE macro firmware: stratix10-svc: Fix an NULL vs IS_ERR() bug in probe serial: sc16is7xx: fix bug when first setting GPIO direction serial: sc16is7xx: fix broken port 0 uart init serial: qcom-geni: fix opp vote on shutdown wifi: mt76: mt7921: fix skb leak by txs missing in AMSDU wifi: mt76: mt7921: do not support one stream on secondary antenna only Bluetooth: btsdio: fix use after free bug in btsdio_remove due to race condition staging: rtl8712: fix race condition HID: wacom: remove the battery when the EKR is off usb: chipidea: imx: improve logic if samsung,picophy-* parameter is 0 usb: dwc3: meson-g12a: do post init to fix broken usb after resumption ALSA: usb-audio: Fix init call orders for UAC1 USB: serial: option: add FOXCONN T99W368/T99W373 product USB: serial: option: add Quectel EM05G variant (0x030e) modules: only allow symbol_get of EXPORT_SYMBOL_GPL modules rtc: ds1685: use EXPORT_SYMBOL_GPL for ds1685_rtc_poweroff net: enetc: use EXPORT_SYMBOL_GPL for enetc_phc_index mmc: au1xmmc: force non-modular build and remove symbol_get usage ARM: pxa: remove use of symbol_get() ksmbd: reduce descriptor size if remaining bytes is less than request size ksmbd: replace one-element array with flex-array member in struct smb2_ea_info ksmbd: fix slub overflow in ksmbd_decode_ntlmssp_auth_blob() ksmbd: fix wrong DataOffset validation of create context erofs: ensure that the post-EOF tails are all zeroed To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2035358/+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 2028740] Re: Fix AMD gpu hang when screen off/on
** Changed in: oem-priority Assignee: (unassigned) => Atlas Yu (pseudoc) ** Changed in: oem-priority Status: New => Confirmed ** Changed in: oem-priority Importance: Undecided => Critical -- 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/2028740 Title: Fix AMD gpu hang when screen off/on Status in HWE Next: In Progress Status in OEM Priority Project: Confirmed Status in linux package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: In Progress Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: In Progress Status in linux source package in Lunar: In Progress Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] AMD GPU hang when screen off/on. error log: kernel: [drm:dc_dmub_srv_wait_idle [amdgpu]] *ERROR* Error waiting for DMUB idle: status=3 [Fix] Keep a PHY active when detecting DP signal + DPMS active. [Test] Tested on 3 AMD platforms, GPU works fine. [Where problems could occur] Low risk, the fix is in v6.4-rc1. Generic Jammy kernel doesn't need this commit because of no support of AMD Phoenix GPU. SRU for Lunar/oem-6.1 kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2028740/+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 2025353] Re: Add support of AMD Pink Sardine and RPL DMIC
Verified on both Pink Sardine and RPL DMIC devices for jammy and lunar, the mic-mute LED works correctly now. ** Tags removed: verification-needed verification-needed-jammy verification-needed-lunar ** Tags added: verification-done verification-done-jammy verification-done-lunar ** Changed in: oem-priority Status: New => Fix Released ** Changed in: oem-priority Assignee: (unassigned) => Atlas Yu (pseudoc) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/2025353 Title: Add support of AMD Pink Sardine and RPL DMIC Status in HWE Next: In Progress Status in OEM Priority Project: Fix Released Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Jammy: Fix Committed Status in alsa-ucm-conf source package in Lunar: Fix Committed Status in alsa-ucm-conf source package in Mantic: Fix Released Bug description: [Impact] Mic-mute LED is not working after press (Mic-mute/F4) key on Thinkpad AMD platform with AMD Pink Sardine and RPL DMIC. [Fix] Add support of AMD Pink Sardine and RPL, DMIC and Micmute LED work fine. [Test] The mic mute LED works fine. [Where problems could occur] Low, upstream fix. It may break mic-mute LED. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2025353/+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 2025353] Re: Add support of AMD Pink Sardine and RPL DMIC
** Tags added: originate-from-2024143 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/2025353 Title: Add support of AMD Pink Sardine and RPL DMIC Status in HWE Next: In Progress Status in OEM Priority Project: New Status in alsa-ucm-conf package in Ubuntu: In Progress Status in alsa-ucm-conf source package in Jammy: In Progress Status in alsa-ucm-conf source package in Lunar: In Progress Status in alsa-ucm-conf source package in Mantic: In Progress Bug description: [Impact] Mic-mute LED is not working after press (Mic-mute/F4) key on Thinkpad AMD platform with AMD Pink Sardine and RPL DMIC. [Fix] Add support of AMD Pink Sardine and RPL, DMIC and Micmute LED work fine. [Test] The mic mute LED works fine. [Where problems could occur] Low, upstream fix. It may break mic-mute LED. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2025353/+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 2018473] Re: Jammy update: v6.1.26 upstream stable release
** Changed in: oem-priority
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/2018473
Title:
Jammy update: v6.1.26 upstream stable release
Status in OEM Priority Project:
Fix Released
Status in linux-oem-6.1 package in Ubuntu:
Confirmed
Status in linux-oem-6.1 source package in Jammy:
New
Bug description:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
v6.1.26 upstream stable release
from git://git.kernel.org/
Linux 6.1.26
ASN.1: Fix check for strdup() success
ASoC: fsl_sai: Fix pins setting for i.MX8QM platform
ASoC: fsl_asrc_dma: fix potential null-ptr-deref
ASoC: SOF: pm: Tear down pipelines only if DSP was active
mm/page_alloc: fix potential deadlock on zonelist_update_seq seqlock
fpga: bridge: properly initialize bridge device before populating children
iio: adc: at91-sama5d2_adc: fix an error code in at91_adc_allocate_trigger()
Input: pegasus-notetaker - check pipe type when probing
gcc: disable '-Warray-bounds' for gcc-13 too
sctp: Call inet6_destroy_sock() via sk->sk_destruct().
dccp: Call inet6_destroy_sock() via sk->sk_destruct().
inet6: Remove inet6_destroy_sock() in sk->sk_prot->destroy().
purgatory: fix disabling debug info
fuse: always revalidate rename target dentry
MIPS: Define RUNTIME_DISCARD_EXIT in LD script
KVM: arm64: Fix buffer overflow in kvm_arm_set_fw_reg()
KVM: arm64: Make vcpu flag updates non-preemptible
sched/fair: Fixes for capacity inversion detection
sched/fair: Consider capacity inversion in util_fits_cpu()
sched/fair: Detect capacity inversion
mm/mmap: regression fix for unmapped_area{_topdown}
mm: page_alloc: skip regions with hugetlbfs pages when allocating 1G pages
mm: kmsan: handle alloc failures in kmsan_vmap_pages_range_noflush()
mm: kmsan: handle alloc failures in kmsan_ioremap_page_range()
mm/huge_memory.c: warn with pr_warn_ratelimited instead of
VM_WARN_ON_ONCE_FOLIO
mm/khugepaged: check again on anon uffd-wp during isolation
mm/userfaultfd: fix uffd-wp handling for THP migration entries
drm/rockchip: vop2: Use regcache_sync() to fix suspend/resume
drm/rockchip: vop2: fix suspend/resume
drm/amd/display: set dcn315 lb bpp to 48
drm/amdgpu: Fix desktop freezed after gpu-reset
drm/i915: Fix fast wake AUX sync len
mmc: sdhci_am654: Set HIGH_SPEED_ENA for SDR12 and SDR25
writeback, cgroup: fix null-ptr-deref write in bdi_split_work_to_wbs
kernel/sys.c: fix and improve control flow in __sys_setres[ug]id()
memstick: fix memory leak if card device is never registered
tools/mm/page_owner_sort.c: fix TGID output when cull=tg is used
nilfs2: initialize unused bytes in segment summary blocks
maple_tree: fix a potential memory leak, OOB access, or other unpredictable
bug
maple_tree: fix mas_empty_area() search
maple_tree: make maple state reusable after mas_empty_area_rev()
LoongArch: Mark 3 symbol exports as non-GPL
LoongArch: Fix probing of the CRC32 feature
rust: kernel: Mark rust_fmt_argument as extern "C"
btrfs: get the next extent map during fiemap/lseek more efficiently
ALSA: hda/realtek: fix mute/micmute LEDs for a HP ProBook
iio: light: tsl2772: fix reading proximity-diodes from device tree
iio: dac: ad5755: Add missing fwnode_handle_put()
drm/amdgpu/vcn: Disable indirect SRAM on Vangogh broken BIOSes
Revert "userfaultfd: don't fail on unrecognized features"
mtd: spi-nor: fix memory leak when using debugfs_lookup()
platform/x86: asus-nb-wmi: Add quirk_asus_tablet_mode to other ROG Flow X13
models
platform/x86: gigabyte-wmi: add support for X570S AORUS ELITE
xen/netback: use same error messages for same errors
nvme-tcp: fix a possible UAF when failing to allocate an io queue
drm: test: Fix 32-bit issue in drm_buddy_test
drm: buddy_allocator: Fix buddy allocator init on 32-bit systems
s390/ptrace: fix PTRACE_GET_LAST_BREAK error handling
platform/x86: gigabyte-wmi: add support for B650 AORUS ELITE AX
net: dsa: b53: mmap: add phy ops
scsi: core: Improve scsi_vpd_inquiry() checks
scsi: megaraid_sas: Fix fw_crash_buffer_show()
selftests: sigaltstack: fix -Wuninitialized
platform/x86 (gigabyte-wmi): Add support for A320M-S2H V2
platform/x86/intel: vsec: Fix a memory leak in intel_vsec_add_aux
f2fs: Fix f2fs_truncate_partial_nodes ftrace event
net: bridge: switchdev: don't notify FDB entries with "master dynamic"
e1000e:
[Kernel-packages] [Bug 2018473] Re: Jammy update: v6.1.26 upstream stable release
I cherry-picked the commit "drm/i915: Fix fast wake AUX sync len" on top
of tag "Ubuntu-oem-6.1-6.1.0-1012.12" and verified if can fix the
related OEM bug.
** Tags added: oem-priority originate-from-2011771 sutton
** Changed in: oem-priority
Status: New => Confirmed
** Changed in: oem-priority
Importance: Undecided => Critical
** Changed in: oem-priority
Assignee: (unassigned) => Atlas Yu (pseudoc)
--
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/2018473
Title:
Jammy update: v6.1.26 upstream stable release
Status in OEM Priority Project:
Confirmed
Status in linux-oem-6.1 package in Ubuntu:
Confirmed
Status in linux-oem-6.1 source package in Jammy:
New
Bug description:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
v6.1.26 upstream stable release
from git://git.kernel.org/
Linux 6.1.26
ASN.1: Fix check for strdup() success
ASoC: fsl_sai: Fix pins setting for i.MX8QM platform
ASoC: fsl_asrc_dma: fix potential null-ptr-deref
ASoC: SOF: pm: Tear down pipelines only if DSP was active
mm/page_alloc: fix potential deadlock on zonelist_update_seq seqlock
fpga: bridge: properly initialize bridge device before populating children
iio: adc: at91-sama5d2_adc: fix an error code in at91_adc_allocate_trigger()
Input: pegasus-notetaker - check pipe type when probing
gcc: disable '-Warray-bounds' for gcc-13 too
sctp: Call inet6_destroy_sock() via sk->sk_destruct().
dccp: Call inet6_destroy_sock() via sk->sk_destruct().
inet6: Remove inet6_destroy_sock() in sk->sk_prot->destroy().
purgatory: fix disabling debug info
fuse: always revalidate rename target dentry
MIPS: Define RUNTIME_DISCARD_EXIT in LD script
KVM: arm64: Fix buffer overflow in kvm_arm_set_fw_reg()
KVM: arm64: Make vcpu flag updates non-preemptible
sched/fair: Fixes for capacity inversion detection
sched/fair: Consider capacity inversion in util_fits_cpu()
sched/fair: Detect capacity inversion
mm/mmap: regression fix for unmapped_area{_topdown}
mm: page_alloc: skip regions with hugetlbfs pages when allocating 1G pages
mm: kmsan: handle alloc failures in kmsan_vmap_pages_range_noflush()
mm: kmsan: handle alloc failures in kmsan_ioremap_page_range()
mm/huge_memory.c: warn with pr_warn_ratelimited instead of
VM_WARN_ON_ONCE_FOLIO
mm/khugepaged: check again on anon uffd-wp during isolation
mm/userfaultfd: fix uffd-wp handling for THP migration entries
drm/rockchip: vop2: Use regcache_sync() to fix suspend/resume
drm/rockchip: vop2: fix suspend/resume
drm/amd/display: set dcn315 lb bpp to 48
drm/amdgpu: Fix desktop freezed after gpu-reset
drm/i915: Fix fast wake AUX sync len
mmc: sdhci_am654: Set HIGH_SPEED_ENA for SDR12 and SDR25
writeback, cgroup: fix null-ptr-deref write in bdi_split_work_to_wbs
kernel/sys.c: fix and improve control flow in __sys_setres[ug]id()
memstick: fix memory leak if card device is never registered
tools/mm/page_owner_sort.c: fix TGID output when cull=tg is used
nilfs2: initialize unused bytes in segment summary blocks
maple_tree: fix a potential memory leak, OOB access, or other unpredictable
bug
maple_tree: fix mas_empty_area() search
maple_tree: make maple state reusable after mas_empty_area_rev()
LoongArch: Mark 3 symbol exports as non-GPL
LoongArch: Fix probing of the CRC32 feature
rust: kernel: Mark rust_fmt_argument as extern "C"
btrfs: get the next extent map during fiemap/lseek more efficiently
ALSA: hda/realtek: fix mute/micmute LEDs for a HP ProBook
iio: light: tsl2772: fix reading proximity-diodes from device tree
iio: dac: ad5755: Add missing fwnode_handle_put()
drm/amdgpu/vcn: Disable indirect SRAM on Vangogh broken BIOSes
Revert "userfaultfd: don't fail on unrecognized features"
mtd: spi-nor: fix memory leak when using debugfs_lookup()
platform/x86: asus-nb-wmi: Add quirk_asus_tablet_mode to other ROG Flow X13
models
platform/x86: gigabyte-wmi: add support for X570S AORUS ELITE
xen/netback: use same error messages for same errors
nvme-tcp: fix a possible UAF when failing to allocate an io queue
drm: test: Fix 32-bit issue in drm_buddy_test
drm: buddy_allocator: Fix buddy allocator init on 32-bit systems
s390/ptrace: fix PTRACE_GET_LAST_BREAK error handling
platform/x86: gigabyte-wmi: add support for B650 AORUS ELITE AX
net: dsa: b53: mmap: add p
[Kernel-packages] [Bug 2007584] Re: Jammy update: v6.1.11 upstream stable release
** 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/2007584
Title:
Jammy update: v6.1.11 upstream stable release
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:
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.11 upstream stable release
from git://git.kernel.org/
Linux 6.1.11
bpf: Skip invalid kfunc call in backtrack_insn
gfs2: Always check inode size of inline inodes
gfs2: Cosmetic gfs2_dinode_{in,out} cleanup
wifi: brcmfmac: Check the count value of channel spec to prevent
out-of-bounds reads
f2fs: fix to do sanity check on i_extra_isize in is_alive()
fbdev: smscufx: fix error handling code in ufx_usb_probe
f2fs: initialize locks earlier in f2fs_fill_super()
ovl: Use "buf" flexible array for memcpy() destination
fs/ntfs3: Validate attribute data and valid sizes
powerpc/imc-pmu: Revert nest_init_lock to being a mutex
powerpc/64s: Fix local irq disable when PMIs are disabled
powerpc/64s/radix: Fix crash with unaligned relocated kernel
iio:adc:twl6030: Enable measurement of VAC
ASoC: SOF: sof-audio: prepare_widgets: Check swidget for NULL on sink failure
platform/x86/amd: pmc: add CONFIG_SERIO dependency
serial: 8250_dma: Fix DMA Rx rearm race
serial: 8250_dma: Fix DMA Rx completion race
phy: qcom-qmp-combo: fix runtime suspend
nvmem: core: fix return value
nvmem: core: fix cell removal on error
nvmem: core: fix device node refcounting
nvmem: core: fix registration vs use race
nvmem: core: fix cleanup after dev_set_name()
nvmem: core: remove nvmem_config wp_gpio
nvmem: core: initialise nvmem->id early
drm/amdgpu: update wave data type to 3 for gfx11
drm/amd/pm: drop unneeded dpm features disablement for SMU 13.0.4/11
drm/amd: Fix initialization for nbio 4.3.0
drm/i915: Fix potential bit_17 double-free
drm/i915: Avoid potential vm use-after-free
serial: stm32: Merge hard IRQ and threaded IRQ handling into single IRQ
handler
dma-buf: actually set signaling bit for private stub fences
migrate: hugetlb: check for hugetlb shared PMD in node migration
maple_tree: fix mas_empty_area_rev() lower bound validation
Squashfs: fix handling and sanity checking of xattr_ids count
ia64: fix build error due to switch case label appearing next to declaration
highmem: round down the address passed to kunmap_flush_on_unmap()
mm/MADV_COLLAPSE: catch !none !huge !bad pmd lookups
mm, mremap: fix mremap() expanding for vma's with vm_ops->close()
mm/khugepaged: fix ->anon_vma race
mm/swapfile: add cond_resched() in get_swap_pages()
mm/uffd: fix pte marker when fork() without fork event
fpga: stratix10-soc: Fix return value check in s10_ops_write_init()
fpga: m10bmc-sec: Fix probe rollback
x86/debug: Fix stack recursion caused by wrongly ordered DR7 accesses
HV: hv_balloon: fix memory leak with using debugfs_lookup()
kernel/irq/irqdomain.c: fix memory leak with using debugfs_lookup()
usb: gadget: udc: do not clear gadget driver.bus
usb: typec: ucsi: Don't attempt to resume the ports before they exist
usb: gadget: f_uac2: Fix incorrect increment of bNumEndpoints
mm: memcg: fix NULL pointer in mem_cgroup_track_foreign_dirty_slowpath()
mm: hugetlb: proc: check for hugetlb shared PMD in /proc/PID/smaps
mm: multi-gen LRU: fix crash during cgroup migration
Revert "mm: kmemleak: alloc gray object for reserved region with direct map"
riscv: disable generation of unwind tables
parisc: Wire up PTRACE_GETREGS/PTRACE_SETREGS for compat case
parisc: Replace hardcoded value with PRIV_USER constant in ptrace.c
parisc: Fix return code of pdc_iodc_print()
nvmem: qcom-spmi-sdam: fix module autoloading
nvmem: sunxi_sid: Always use 32-bit MMIO reads
nvmem: brcm_nvram: Add check for kzalloc
iio: imu: fxos8700: fix MAGN sensor scale and unit
iio: imu: fxos8700: remove definition FXOS8700_CTRL_ODR_MIN
iio: imu: fxos8700: fix failed initialization ODR mode assignment
iio: imu: fxos8700: fix incorrect ODR mode readback
iio: imu: fxos8700: fix swapped ACCEL and MAGN channels readback
iio: imu: fxos8700: fix map label of channel type to MAGN sensor
iio: imu: fxos8700: fix IMU data bits returned to user space
iio: imu: fxos8700: fix incomplete ACCEL and MAGN
[Kernel-packages] [Bug 2007994] Re: Ubuntu 22.04 ThinkPad X13 Yoga Gen2 Kernel 5.19 Causes Screen Flickering
I installed the linux-oem-22.04c (6.1.0-oem-1007), and it's all good. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2007994 Title: Ubuntu 22.04 ThinkPad X13 Yoga Gen2 Kernel 5.19 Causes Screen Flickering Status in linux-signed-hwe-5.19 package in Ubuntu: Confirmed Bug description: Affected machine: Lenovo ThinkPad X13 Yoga Gen 2 OS: Ubuntu 22.04.2 LTS (64-bit) I did a dist-upgrade on Feb. 16th, and every boot after that results in screen flickering, I checked the dpkg history and assume that the kernel upgrade(5.19.0.32.33~22.04.9) is the one to blame. Then I tried to boot the machine with the former kernel(5.15.0.25.27), everything works fine again which confirms my assumption. The following line repeated to show up before entering the desktop: blacklist: Problem blacklisting hash (-13) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-32-generic 5.19.0-32.33~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: Unity Date: Wed Feb 22 00:11:10 2023 InstallationDate: Installed on 2022-08-29 (176 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2007994/+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 2007584] Re: Jammy update: v6.1.11 upstream stable release
** Changed in: oem-priority
Importance: Undecided => Critical
** Changed in: oem-priority
Assignee: (unassigned) => Atlas Yu (pseudoc)
--
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/2007584
Title:
Jammy update: v6.1.11 upstream stable release
Status in OEM Priority Project:
New
Status in linux-oem-6.1 package in Ubuntu:
Invalid
Status in linux-oem-6.1 source package in Jammy:
Confirmed
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.11 upstream stable release
from git://git.kernel.org/
Linux 6.1.11
bpf: Skip invalid kfunc call in backtrack_insn
gfs2: Always check inode size of inline inodes
gfs2: Cosmetic gfs2_dinode_{in,out} cleanup
wifi: brcmfmac: Check the count value of channel spec to prevent
out-of-bounds reads
f2fs: fix to do sanity check on i_extra_isize in is_alive()
fbdev: smscufx: fix error handling code in ufx_usb_probe
f2fs: initialize locks earlier in f2fs_fill_super()
ovl: Use "buf" flexible array for memcpy() destination
fs/ntfs3: Validate attribute data and valid sizes
powerpc/imc-pmu: Revert nest_init_lock to being a mutex
powerpc/64s: Fix local irq disable when PMIs are disabled
powerpc/64s/radix: Fix crash with unaligned relocated kernel
iio:adc:twl6030: Enable measurement of VAC
ASoC: SOF: sof-audio: prepare_widgets: Check swidget for NULL on sink failure
platform/x86/amd: pmc: add CONFIG_SERIO dependency
serial: 8250_dma: Fix DMA Rx rearm race
serial: 8250_dma: Fix DMA Rx completion race
phy: qcom-qmp-combo: fix runtime suspend
nvmem: core: fix return value
nvmem: core: fix cell removal on error
nvmem: core: fix device node refcounting
nvmem: core: fix registration vs use race
nvmem: core: fix cleanup after dev_set_name()
nvmem: core: remove nvmem_config wp_gpio
nvmem: core: initialise nvmem->id early
drm/amdgpu: update wave data type to 3 for gfx11
drm/amd/pm: drop unneeded dpm features disablement for SMU 13.0.4/11
drm/amd: Fix initialization for nbio 4.3.0
drm/i915: Fix potential bit_17 double-free
drm/i915: Avoid potential vm use-after-free
serial: stm32: Merge hard IRQ and threaded IRQ handling into single IRQ
handler
dma-buf: actually set signaling bit for private stub fences
migrate: hugetlb: check for hugetlb shared PMD in node migration
maple_tree: fix mas_empty_area_rev() lower bound validation
Squashfs: fix handling and sanity checking of xattr_ids count
ia64: fix build error due to switch case label appearing next to declaration
highmem: round down the address passed to kunmap_flush_on_unmap()
mm/MADV_COLLAPSE: catch !none !huge !bad pmd lookups
mm, mremap: fix mremap() expanding for vma's with vm_ops->close()
mm/khugepaged: fix ->anon_vma race
mm/swapfile: add cond_resched() in get_swap_pages()
mm/uffd: fix pte marker when fork() without fork event
fpga: stratix10-soc: Fix return value check in s10_ops_write_init()
fpga: m10bmc-sec: Fix probe rollback
x86/debug: Fix stack recursion caused by wrongly ordered DR7 accesses
HV: hv_balloon: fix memory leak with using debugfs_lookup()
kernel/irq/irqdomain.c: fix memory leak with using debugfs_lookup()
usb: gadget: udc: do not clear gadget driver.bus
usb: typec: ucsi: Don't attempt to resume the ports before they exist
usb: gadget: f_uac2: Fix incorrect increment of bNumEndpoints
mm: memcg: fix NULL pointer in mem_cgroup_track_foreign_dirty_slowpath()
mm: hugetlb: proc: check for hugetlb shared PMD in /proc/PID/smaps
mm: multi-gen LRU: fix crash during cgroup migration
Revert "mm: kmemleak: alloc gray object for reserved region with direct map"
riscv: disable generation of unwind tables
parisc: Wire up PTRACE_GETREGS/PTRACE_SETREGS for compat case
parisc: Replace hardcoded value with PRIV_USER constant in ptrace.c
parisc: Fix return code of pdc_iodc_print()
nvmem: qcom-spmi-sdam: fix module autoloading
nvmem: sunxi_sid: Always use 32-bit MMIO reads
nvmem: brcm_nvram: Add check for kzalloc
iio: imu: fxos8700: fix MAGN sensor scale and unit
iio: imu: fxos8700: remove definition FXOS8700_CTRL_ODR_MIN
iio: imu: fxos8700: fix failed initialization ODR mode assignment
iio: imu: fxos8700: fix incorrect ODR mode readback
iio: imu: fxos8700: fix swapped ACCEL and MAGN channels readback
iio: imu: fxos8700: fix map label of channel type to MAGN sensor
iio: imu: f
[Kernel-packages] [Bug 2007584] Re: Jammy update: v6.1.11 upstream stable release
** Also affects: oem-priority
Importance: Undecided
Status: New
** Tags added: oem-priority originate-from-2009584 sutton
--
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/2007584
Title:
Jammy update: v6.1.11 upstream stable release
Status in OEM Priority Project:
New
Status in linux-oem-6.1 package in Ubuntu:
Invalid
Status in linux-oem-6.1 source package in Jammy:
Confirmed
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.11 upstream stable release
from git://git.kernel.org/
Linux 6.1.11
bpf: Skip invalid kfunc call in backtrack_insn
gfs2: Always check inode size of inline inodes
gfs2: Cosmetic gfs2_dinode_{in,out} cleanup
wifi: brcmfmac: Check the count value of channel spec to prevent
out-of-bounds reads
f2fs: fix to do sanity check on i_extra_isize in is_alive()
fbdev: smscufx: fix error handling code in ufx_usb_probe
f2fs: initialize locks earlier in f2fs_fill_super()
ovl: Use "buf" flexible array for memcpy() destination
fs/ntfs3: Validate attribute data and valid sizes
powerpc/imc-pmu: Revert nest_init_lock to being a mutex
powerpc/64s: Fix local irq disable when PMIs are disabled
powerpc/64s/radix: Fix crash with unaligned relocated kernel
iio:adc:twl6030: Enable measurement of VAC
ASoC: SOF: sof-audio: prepare_widgets: Check swidget for NULL on sink failure
platform/x86/amd: pmc: add CONFIG_SERIO dependency
serial: 8250_dma: Fix DMA Rx rearm race
serial: 8250_dma: Fix DMA Rx completion race
phy: qcom-qmp-combo: fix runtime suspend
nvmem: core: fix return value
nvmem: core: fix cell removal on error
nvmem: core: fix device node refcounting
nvmem: core: fix registration vs use race
nvmem: core: fix cleanup after dev_set_name()
nvmem: core: remove nvmem_config wp_gpio
nvmem: core: initialise nvmem->id early
drm/amdgpu: update wave data type to 3 for gfx11
drm/amd/pm: drop unneeded dpm features disablement for SMU 13.0.4/11
drm/amd: Fix initialization for nbio 4.3.0
drm/i915: Fix potential bit_17 double-free
drm/i915: Avoid potential vm use-after-free
serial: stm32: Merge hard IRQ and threaded IRQ handling into single IRQ
handler
dma-buf: actually set signaling bit for private stub fences
migrate: hugetlb: check for hugetlb shared PMD in node migration
maple_tree: fix mas_empty_area_rev() lower bound validation
Squashfs: fix handling and sanity checking of xattr_ids count
ia64: fix build error due to switch case label appearing next to declaration
highmem: round down the address passed to kunmap_flush_on_unmap()
mm/MADV_COLLAPSE: catch !none !huge !bad pmd lookups
mm, mremap: fix mremap() expanding for vma's with vm_ops->close()
mm/khugepaged: fix ->anon_vma race
mm/swapfile: add cond_resched() in get_swap_pages()
mm/uffd: fix pte marker when fork() without fork event
fpga: stratix10-soc: Fix return value check in s10_ops_write_init()
fpga: m10bmc-sec: Fix probe rollback
x86/debug: Fix stack recursion caused by wrongly ordered DR7 accesses
HV: hv_balloon: fix memory leak with using debugfs_lookup()
kernel/irq/irqdomain.c: fix memory leak with using debugfs_lookup()
usb: gadget: udc: do not clear gadget driver.bus
usb: typec: ucsi: Don't attempt to resume the ports before they exist
usb: gadget: f_uac2: Fix incorrect increment of bNumEndpoints
mm: memcg: fix NULL pointer in mem_cgroup_track_foreign_dirty_slowpath()
mm: hugetlb: proc: check for hugetlb shared PMD in /proc/PID/smaps
mm: multi-gen LRU: fix crash during cgroup migration
Revert "mm: kmemleak: alloc gray object for reserved region with direct map"
riscv: disable generation of unwind tables
parisc: Wire up PTRACE_GETREGS/PTRACE_SETREGS for compat case
parisc: Replace hardcoded value with PRIV_USER constant in ptrace.c
parisc: Fix return code of pdc_iodc_print()
nvmem: qcom-spmi-sdam: fix module autoloading
nvmem: sunxi_sid: Always use 32-bit MMIO reads
nvmem: brcm_nvram: Add check for kzalloc
iio: imu: fxos8700: fix MAGN sensor scale and unit
iio: imu: fxos8700: remove definition FXOS8700_CTRL_ODR_MIN
iio: imu: fxos8700: fix failed initialization ODR mode assignment
iio: imu: fxos8700: fix incorrect ODR mode readback
iio: imu: fxos8700: fix swapped ACCEL and MAGN channels readback
iio: imu: fxos8700: fix map label of channel type to MAGN sensor
iio: imu: fxos8700: fix IMU data bits returned to user
[Kernel-packages] [Bug 2007994] Re: Ubuntu 22.04 ThinkPad X13 Yoga Gen2 Kernel 5.19 Causes Screen Flickering
The screencast tool cannot record the flickering, so I have to use my phone for capturing. ** Attachment added: "bug-2007994.mp4" https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2007994/+attachment/5648974/+files/bug-2007994.mp4 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2007994 Title: Ubuntu 22.04 ThinkPad X13 Yoga Gen2 Kernel 5.19 Causes Screen Flickering Status in linux-signed-hwe-5.19 package in Ubuntu: New Bug description: Affected machine: Lenovo ThinkPad X13 Yoga Gen 2 OS: Ubuntu 22.04.2 LTS (64-bit) I did a dist-upgrade on Feb. 16th, and every boot after that results in screen flickering, I checked the dpkg history and assume that the kernel upgrade(5.19.0.32.33~22.04.9) is the one to blame. Then I tried to boot the machine with the former kernel(5.15.0.25.27), everything works fine again which confirms my assumption. The following line repeated to show up before entering the desktop: blacklist: Problem blacklisting hash (-13) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-32-generic 5.19.0-32.33~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: Unity Date: Wed Feb 22 00:11:10 2023 InstallationDate: Installed on 2022-08-29 (176 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2007994/+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 2007994] [NEW] Ubuntu 22.04 ThinkPad X13 Yoga Gen2 Kernel 5.19 Causes Screen Flickering
Public bug reported: Affected machine: Lenovo ThinkPad X13 Yoga Gen 2 OS: Ubuntu 22.04.2 LTS (64-bit) I did a dist-upgrade on Feb. 16th, and every boot after that results in screen flickering, I checked the dpkg history and assume that the kernel upgrade(5.19.0.32.33~22.04.9) is the one to blame. Then I tried to boot the machine with the former kernel(5.15.0.25.27), everything works fine again which confirms my assumption. The following line repeated to show up before entering the desktop: blacklist: Problem blacklisting hash (-13) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-32-generic 5.19.0-32.33~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: Unity Date: Wed Feb 22 00:11:10 2023 InstallationDate: Installed on 2022-08-29 (176 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.19 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy regression-update wayland-session -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2007994 Title: Ubuntu 22.04 ThinkPad X13 Yoga Gen2 Kernel 5.19 Causes Screen Flickering Status in linux-signed-hwe-5.19 package in Ubuntu: New Bug description: Affected machine: Lenovo ThinkPad X13 Yoga Gen 2 OS: Ubuntu 22.04.2 LTS (64-bit) I did a dist-upgrade on Feb. 16th, and every boot after that results in screen flickering, I checked the dpkg history and assume that the kernel upgrade(5.19.0.32.33~22.04.9) is the one to blame. Then I tried to boot the machine with the former kernel(5.15.0.25.27), everything works fine again which confirms my assumption. The following line repeated to show up before entering the desktop: blacklist: Problem blacklisting hash (-13) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-32-generic 5.19.0-32.33~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: Unity Date: Wed Feb 22 00:11:10 2023 InstallationDate: Installed on 2022-08-29 (176 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2007994/+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 2002373] Re: Mic Mute LED doesn't work on DMIC laptops
** Tags added: originate-from-2000769 sutton ** Tags added: originate-from-2001905 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/2002373 Title: Mic Mute LED doesn't work on DMIC laptops Status in HWE Next: New Status in OEM Priority Project: New Status in alsa-ucm-conf package in Ubuntu: Confirmed Status in alsa-ucm-conf source package in Jammy: Confirmed Status in alsa-ucm-conf source package in Kinetic: Confirmed Status in alsa-ucm-conf source package in Lunar: Confirmed Bug description: [Impact] Mic mute LED doesn't work on Intel-based HP laptops. [Fix] Due to recent change on how kernel creates sound LEDs, there are two captures are registered, one from SoF and one from HDA. The SoF one is the "real" capture system uses. Since physical LED only gets light up when _all_ captures are muted, detach the HDA one so micmute LED only need to consider SoF capture's mute status. [Test] The mic mute LED works again on DMIC laptops. The legacy HDA systems are unaffected. [Where problems could occur] Theoretically the system may have more than two internal captures registered, then disabling one will not be enough. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2002373/+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 1998154] Re: dkms (2.8.7-2ubuntu2.1) jammy depends on gcc-12 which is under universe archive
since gcc-12 is now in main, this does not affect the OEM project any longer. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1998154 Title: dkms (2.8.7-2ubuntu2.1) jammy depends on gcc-12 which is under universe archive Status in OEM Priority Project: Fix Released Status in dkms package in Ubuntu: Invalid Bug description: [Description] The latest dkms(2.8.7-2ubuntu2.1) depends on gcc-12 which is in universe archive. https://packages.ubuntu.com/search?keywords=gcc-12 gcc-12 is under main for kinect, and the patches are cherry-picked from kinect/stable, I suppose it is a mistake for jammy in universe. [debian/changelog] dkms (2.8.7-2ubuntu2.1) jammy; urgency=medium Cherry-pick patches from kinetic/stable to address building dkms modules correctly for HWE kernels (LP: #1991664): Fix dkms-autopkgtest when a given dkms package is built into the kernel already of the same version. (i.e. zfs-linux on Ubuntu). Use exact compiler for dkms as used to build the kernel, when possible. Depend on gcc-12 to build modules for HWE kernels correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1998154/+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 1998154] Re: dkms (2.8.7-2ubuntu2.1) jammy depends on gcc-12 which is under universe archive
** 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 dkms in Ubuntu. https://bugs.launchpad.net/bugs/1998154 Title: dkms (2.8.7-2ubuntu2.1) jammy depends on gcc-12 which is under universe archive Status in OEM Priority Project: Fix Released Status in dkms package in Ubuntu: Invalid Bug description: [Description] The latest dkms(2.8.7-2ubuntu2.1) depends on gcc-12 which is in universe archive. https://packages.ubuntu.com/search?keywords=gcc-12 gcc-12 is under main for kinect, and the patches are cherry-picked from kinect/stable, I suppose it is a mistake for jammy in universe. [debian/changelog] dkms (2.8.7-2ubuntu2.1) jammy; urgency=medium Cherry-pick patches from kinetic/stable to address building dkms modules correctly for HWE kernels (LP: #1991664): Fix dkms-autopkgtest when a given dkms package is built into the kernel already of the same version. (i.e. zfs-linux on Ubuntu). Use exact compiler for dkms as used to build the kernel, when possible. Depend on gcc-12 to build modules for HWE kernels correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1998154/+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 1998154] Re: dkms (2.8.7-2ubuntu2.1) jammy depends on gcc-12 which is under universe archive
** Tags added: jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1998154 Title: dkms (2.8.7-2ubuntu2.1) jammy depends on gcc-12 which is under universe archive Status in dkms package in Ubuntu: New Bug description: [Description] The latest dkms(2.8.7-2ubuntu2.1) depends on gcc-12 which is in universe archive. https://packages.ubuntu.com/search?keywords=gcc-12 gcc-12 is under main for kinect, and the patches are cherry-picked from kinect/stable, I suppose it is a mistake for jammy in universe. [debian/changelog] dkms (2.8.7-2ubuntu2.1) jammy; urgency=medium Cherry-pick patches from kinetic/stable to address building dkms modules correctly for HWE kernels (LP: #1991664): Fix dkms-autopkgtest when a given dkms package is built into the kernel already of the same version. (i.e. zfs-linux on Ubuntu). Use exact compiler for dkms as used to build the kernel, when possible. Depend on gcc-12 to build modules for HWE kernels correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1998154/+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 1998154] Re: dkms (2.8.7-2ubuntu2.1) jammy depends on gcc-12 which is under universe archive
** Also affects: dkms Importance: Undecided Status: New ** No longer affects: dkms -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1998154 Title: dkms (2.8.7-2ubuntu2.1) jammy depends on gcc-12 which is under universe archive Status in dkms package in Ubuntu: New Bug description: [Description] The latest dkms(2.8.7-2ubuntu2.1) depends on gcc-12 which is in universe archive. https://packages.ubuntu.com/search?keywords=gcc-12 gcc-12 is under main for kinect, and the patches are cherry-picked from kinect/stable, I suppose it is a mistake for jammy in universe. [debian/changelog] dkms (2.8.7-2ubuntu2.1) jammy; urgency=medium Cherry-pick patches from kinetic/stable to address building dkms modules correctly for HWE kernels (LP: #1991664): Fix dkms-autopkgtest when a given dkms package is built into the kernel already of the same version. (i.e. zfs-linux on Ubuntu). Use exact compiler for dkms as used to build the kernel, when possible. Depend on gcc-12 to build modules for HWE kernels correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1998154/+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 1998154] [NEW] dkms (2.8.7-2ubuntu2.1) jammy depends on gcc-12 which is under universe archive
Public bug reported: [Description] The latest dkms(2.8.7-2ubuntu2.1) depends on gcc-12 which is in universe archive. https://packages.ubuntu.com/search?keywords=gcc-12 gcc-12 is under main for kinect, and the patches are cherry-picked from kinect/stable, I suppose it is a mistake for jammy in universe. [debian/changelog] dkms (2.8.7-2ubuntu2.1) jammy; urgency=medium Cherry-pick patches from kinetic/stable to address building dkms modules correctly for HWE kernels (LP: #1991664): Fix dkms-autopkgtest when a given dkms package is built into the kernel already of the same version. (i.e. zfs-linux on Ubuntu). Use exact compiler for dkms as used to build the kernel, when possible. Depend on gcc-12 to build modules for HWE kernels correctly. ** Affects: dkms (Ubuntu) Importance: Undecided Status: New ** Tags: regression-update -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1998154 Title: dkms (2.8.7-2ubuntu2.1) jammy depends on gcc-12 which is under universe archive Status in dkms package in Ubuntu: New Bug description: [Description] The latest dkms(2.8.7-2ubuntu2.1) depends on gcc-12 which is in universe archive. https://packages.ubuntu.com/search?keywords=gcc-12 gcc-12 is under main for kinect, and the patches are cherry-picked from kinect/stable, I suppose it is a mistake for jammy in universe. [debian/changelog] dkms (2.8.7-2ubuntu2.1) jammy; urgency=medium Cherry-pick patches from kinetic/stable to address building dkms modules correctly for HWE kernels (LP: #1991664): Fix dkms-autopkgtest when a given dkms package is built into the kernel already of the same version. (i.e. zfs-linux on Ubuntu). Use exact compiler for dkms as used to build the kernel, when possible. Depend on gcc-12 to build modules for HWE kernels correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1998154/+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 1997005] Re: Cannot output displays by connecting dual monitor via HP Docking
@jeremyszu Take a look at this: https://bugs.launchpad.net/sutton/+bug/1996502, they are quite alike. -- 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/1997005 Title: Cannot output displays by connecting dual monitor via HP Docking Status in Linux: New Status in OEM Priority Project: New Status in linux package in Ubuntu: New Bug description: [Summary] Connect USB-C to HDMI monitor to USB-C display port and 4K DP monitor to DP port on docking, the external monitors cannot display. Note: 1. Single 4K UHD montior on DP port can output successfully on docking. 2. Single FHD monitor with USB-C to HDMI adapter on USB-C displayport can output successfully on docking. [Steps to reproduce] 1. Poweroff the system and plug docking station to the system 2. Boot up system from docking power button 3. Connect external display with USB-C to HDMI adapter to the USB-C display port on docking 4. Connect 4K UHD monitor with DP cable to DP port on docking station 5. Check the displays. [Expected result] Can output display successfully when the system connects to the dual monitor. [Actual result] Cannot output external displays by connecting USB-C to HDMI on USB-C display port and DP monitor to DP port on docking station. [Failure rate] 1/1 [Additional information] SKU: Alder SKU2(T1000), Alder SKU12(RTX4000) system-manufacturer: HP system-product-name: HP ZBook Fury 17 G7 Mobile Workstation bios-version: S92 Ver. 01.06.00 CPU: Intel(R) Core(TM) i5-10400H CPU @ 2.60GHz (8x) GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:9bc4] (rev 05) 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation Device [10de:1fb9] (rev a1) kernel-version: 5.10.0-1034-oem To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1997005/+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
