Re: [Kernel-packages] [Bug 2045233] Re: [SRU][22.04.04]: mpi3mr driver update
I have picked those into my branch since they were all in linux-next at this point for 6.8 On Thu, Dec 14, 2023 at 2:30 AM Chandrakanth Patil < 2045...@bugs.launchpad.net> wrote: > I didn't get you. These below patches will also be included right? > d0a60e3edaa4 scsi: mpi3mr: Update driver version to 8.5.1.0.0 > 9536af615dc9 scsi: mpi3mr: Support for preallocation of SGL BSG data > buffers part-3 > fb231d7deffb scsi: mpi3mr: Support for preallocation of SGL BSG data > buffers part-2 > c432e1675239 scsi: mpi3mr: Support for preallocation of SGL BSG data > buffers part-1 > 07ac6adda4d3 scsi: mpi3mr: Fetch correct device dev handle for status > reply descriptor > f8fb3f39148e scsi: mpi3mr: Block PEL Enable Command on Controller Reset > and Unrecoverable State > c01d515687e3 scsi: mpi3mr: Clean up block devices post controller reset > e5aab848dfdf scsi: mpi3mr: Refresh sdev queue depth after controller reset > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/2045233 > > Title: > [SRU][22.04.04]: mpi3mr driver update > > Status in linux package in Ubuntu: > Confirmed > Status in linux source package in Jammy: > Opinion > Status in linux source package in Mantic: > Confirmed > Status in linux source package in Noble: > Confirmed > > Bug description: > [Impact] > > This update has been initiated to incorporate the mpi3mr driver from > upstream into the upcoming Ubuntu releases (Ubuntu 22.04.x point > releases). > > This has been requested by both Broadcom as the upstream and by one of > the larger OEM partners who are going to be selling systems with these > storage controllers to customers. This series of patches includes bug > fixes and support for current Broadcom controllers. > > [Fixes] > Below are the commit IDs for the latest upstream version (v6.8). > > The 22.04 LTS point kernel already includes the latest mpi3mr driver > version 8.0.0.69.0. Therefore, the listed commit IDs below correspond > to the subsequent patches. > > The commit IDs listed below are in sequential order from bottom to > top, indicating the order for applying the patches. > > linux-next > d0a60e3edaa4 scsi: mpi3mr: Update driver version to 8.5.1.0.0 > 9536af615dc9 scsi: mpi3mr: Support for preallocation of SGL BSG data > buffers part-3 > fb231d7deffb scsi: mpi3mr: Support for preallocation of SGL BSG data > buffers part-2 > c432e1675239 scsi: mpi3mr: Support for preallocation of SGL BSG data > buffers part-1 > 07ac6adda4d3 scsi: mpi3mr: Fetch correct device dev handle for status > reply descriptor > f8fb3f39148e scsi: mpi3mr: Block PEL Enable Command on Controller Reset > and Unrecoverable State > c01d515687e3 scsi: mpi3mr: Clean up block devices post controller reset > e5aab848dfdf scsi: mpi3mr: Refresh sdev queue depth after controller > reset > b4d94164ff32 scsi: mpi3mr: driver version upgrade to 8.5.0.0.50 > 1193a89d2b6d scsi: mpi3mr: Add support for status reply descriptor > cb5b60894602 scsi: mpi3mr: Increase maximum number of PHYs to 64 from 32 > c9260ff28ee5 scsi: mpi3mr: Add PCI checks where SAS5116 diverges from > SAS4116 > 6fa21eab82be scsi: mpi3mr: Add support for SAS5116 PCI IDs > > Mainline at 6.6/6.7 > 82b2fb52d6ec scsi: mpi3mr: Split off bus_reset function from host_reset > 9a9068b2afa0 scsi: mpi3mr: Update driver version to 8.5.0.0.0 > d9a5ab0ea98f scsi: mpi3mr: Enhance handling of devices removed after > controller reset > e7a8648e1ce2 scsi: mpi3mr: WRITE SAME implementation > d9adb81e67e9 scsi: mpi3mr: Add support for more than 1MB I/O > 6f81b1cfdf33 scsi: mpi3mr: Update MPI Headers to version 3.00.28 > 9134211f7bed scsi: mpi3mr: Invoke soft reset upon TSU or event ack time > out > > [Testing] > verify the mpi3mr driver is loaded > verify the version string shows 8.5.1.0.0 > > [Regression Risk] > Low. These patches are contained to the mpi3mr driver code itself and > are all already accepted upstream. They cleanly pick into our 6.5 kernel > tree. > > Broadcom has tested these and the only concern is the kernel warning > below in Comment #7 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045233/+subscriptions > > Launchpad-Notification-Type: bug > Launchpad-Bug: distribution=ubuntu; sourcepackage=linux; component=main; > status=Confirmed; importance=Medium; assignee=jeffrey.l...@canonical.com; > Launchpad-Bug: distribution=ubuntu; distroseries=jammy; > sourcepackage=linux; component=main; status=Opinion; importance=Wishlist; > assignee=None; > Launchpad-Bug: distribution=ubuntu; distroseries=mantic; > sourcepackage=linux; component=main; status=Confirmed; importance=Medium; > assignee=jeffrey.l...@canonical.com; > Launchpad-Bug: distribution=ubuntu; distroseries=noble; > sourcepackage=linux; component=main; status=Confirmed; importance=Medium; > assignee=jeffrey.l...@canonical.com; > La
[Kernel-packages] [Bug 2045384] Re: AppArmor patch for mq-posix interface is missing in jammy
** Also affects: livecd-rootfs (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Jammy) Status: New => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2045384 Title: AppArmor patch for mq-posix interface is missing in jammy Status in linux package in Ubuntu: Triaged Status in livecd-rootfs package in Ubuntu: New Status in linux source package in Jammy: Triaged Status in livecd-rootfs source package in Jammy: New Bug description: [ Impact ] mq-posix snapd interface does not work on Ubuntu Core 22. It results in permission denied even all interfaces are connected. Our brandstore customer is using posix message queue for IPC between snaps. They added mq-posix interface and connected them properly but getting permission denied error. The AppArmor patch for posix message queue created for other customer did not land in the standard jammy kernel. Userspace support for AppArmor message queue handling is already present in Ubuntu Core 22, it is just missing from the kernel. [ Test Plan ] * Create snaps using the posix-mq snapd interface on Ubuntu Core 22 or Classic 22.04 with the standard kernel. * Example snaps for testing: https://code.launchpad.net/~itrue/+git/mqtest-provider and https://code.launchpad.net/~itrue/+git/mqtest-client [ Where problems could occur ] * The patches already exist for 5.15 and have been used on other private customer kernels and all kernels released after 22.04, so there is already a good track record for this patchset and it shouldn't create any issues. [ Other Info ] * This is a time-sensitive issue for a paying customer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045384/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2045233] Re: [SRU][22.04.04]: mpi3mr driver update
ok, Jeff. Regarding warning: 1. Since there is no functional impact, we can ignore it as of now. 2. We will submit the warning fix to upstream ASAP. Do you have any suggestions on this? -- 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/2045233 Title: [SRU][22.04.04]: mpi3mr driver update Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: Opinion Status in linux source package in Mantic: Confirmed Status in linux source package in Noble: Confirmed Bug description: [Impact] This update has been initiated to incorporate the mpi3mr driver from upstream into the upcoming Ubuntu releases (Ubuntu 22.04.x point releases). This has been requested by both Broadcom as the upstream and by one of the larger OEM partners who are going to be selling systems with these storage controllers to customers. This series of patches includes bug fixes and support for current Broadcom controllers. [Fixes] Below are the commit IDs for the latest upstream version (v6.8). The 22.04 LTS point kernel already includes the latest mpi3mr driver version 8.0.0.69.0. Therefore, the listed commit IDs below correspond to the subsequent patches. The commit IDs listed below are in sequential order from bottom to top, indicating the order for applying the patches. linux-next d0a60e3edaa4 scsi: mpi3mr: Update driver version to 8.5.1.0.0 9536af615dc9 scsi: mpi3mr: Support for preallocation of SGL BSG data buffers part-3 fb231d7deffb scsi: mpi3mr: Support for preallocation of SGL BSG data buffers part-2 c432e1675239 scsi: mpi3mr: Support for preallocation of SGL BSG data buffers part-1 07ac6adda4d3 scsi: mpi3mr: Fetch correct device dev handle for status reply descriptor f8fb3f39148e scsi: mpi3mr: Block PEL Enable Command on Controller Reset and Unrecoverable State c01d515687e3 scsi: mpi3mr: Clean up block devices post controller reset e5aab848dfdf scsi: mpi3mr: Refresh sdev queue depth after controller reset b4d94164ff32 scsi: mpi3mr: driver version upgrade to 8.5.0.0.50 1193a89d2b6d scsi: mpi3mr: Add support for status reply descriptor cb5b60894602 scsi: mpi3mr: Increase maximum number of PHYs to 64 from 32 c9260ff28ee5 scsi: mpi3mr: Add PCI checks where SAS5116 diverges from SAS4116 6fa21eab82be scsi: mpi3mr: Add support for SAS5116 PCI IDs Mainline at 6.6/6.7 82b2fb52d6ec scsi: mpi3mr: Split off bus_reset function from host_reset 9a9068b2afa0 scsi: mpi3mr: Update driver version to 8.5.0.0.0 d9a5ab0ea98f scsi: mpi3mr: Enhance handling of devices removed after controller reset e7a8648e1ce2 scsi: mpi3mr: WRITE SAME implementation d9adb81e67e9 scsi: mpi3mr: Add support for more than 1MB I/O 6f81b1cfdf33 scsi: mpi3mr: Update MPI Headers to version 3.00.28 9134211f7bed scsi: mpi3mr: Invoke soft reset upon TSU or event ack time out [Testing] verify the mpi3mr driver is loaded verify the version string shows 8.5.1.0.0 [Regression Risk] Low. These patches are contained to the mpi3mr driver code itself and are all already accepted upstream. They cleanly pick into our 6.5 kernel tree. Broadcom has tested these and the only concern is the kernel warning below in Comment #7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045233/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2045796] Re: Add Support for Broadcom 5760X Network adapters to 24.04 (patches in 6.8)
** Changed in: linux (Ubuntu Noble) Assignee: (unassigned) => Jeff Lane (bladernr) ** Also affects: linux (Ubuntu Mantic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Mantic) Assignee: (unassigned) => Jeff Lane (bladernr) ** Changed in: linux (Ubuntu Mantic) Status: New => In Progress -- 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/2045796 Title: Add Support for Broadcom 5760X Network adapters to 24.04 (patches in 6.8) Status in linux package in Ubuntu: New Status in linux source package in Mantic: In Progress Status in linux source package in Noble: New Bug description: These patches are needed on top of v6.7 to support Broadcom 5760X Adapters. These patches currently reside in the net-next tree and will be included in v6.8. Prerequisite commits in net-next today: c1056a59aee1 bnxt_en: Optimize xmit_more TX path ba098017791e bnxt_en: Use existing MSIX vectors for all mqprio TX rings f07b58801bef bnxt_en: Add macros related to TC and TX rings f5b29c6afe36 bnxt_en: Add helper to get the number of CP rings required for TX rings 0589a1ed4d33 bnxt_en: Support up to 8 TX rings per MSIX 877edb347323 bnxt_en: Refactor bnxt_hwrm_set_coal() 5a3c585fa83f bnxt_en: New encoding for the TX opaque field ebf72319cef6 bnxt_en: Refactor bnxt_tx_int() 9c0b06de6fb6 bnxt_en: Remove BNXT_RX_HDL and BNXT_TX_HDL 7845b8dfc713 bnxt_en: Add completion ring pointer in TX and RX ring structures d1eec614100c bnxt_en: Restructure cp_ring_arr in struct bnxt_cp_ring_info 7f0a168b0441 bnxt_en: Add completion ring pointer in TX and RX ring structures 34eec1f29a59 bnxt_en: Put the TX producer information in the TX BD opaque field These 13 patches below were submitted on 11/20/23 and accepted on 11/21/23. These are the initial patches with 5760X contents. 1c7fd6ee2fe4 bnxt_en: Rename some macros for the P5 chips f94471f3ce74 bnxt_en: Modify the NAPI logic for the new P7 chips c09d22674b94 bnxt_en: Modify RX ring indexing logic. 6d1add95536b bnxt_en: Modify TX ring indexing logic. b9e0c47ee2ec bnxt_en: Add db_ring_mask and related macro to bnxt_db_info struct. 236e237f8ffe bnxt_en: Add support for HWRM_FUNC_BACKING_STORE_CFG_V2 firmware calls 6a4d0774f02d bnxt_en: Add support for new backing store query firmware API b098dc5a3357 bnxt_en: Add bnxt_setup_ctxm_pg_tbls() helper function 2ad67aea11f2 bnxt_en: Use the pg_info field in bnxt_ctx_mem_type struct 035c57615982 bnxt_en: Add page info to struct bnxt_ctx_mem_type 76087d997a84 bnxt_en: Restructure context memory data structures e50dc4c2206e bnxt_en: Free bp->ctx inside bnxt_free_ctx_mem() aa8460bacf49 bnxt_en: The caller of bnxt_alloc_ctx_mem() should always free bp->ctx The next 15 patches were submitted on 12/1/23 and accepted on 12/4/23. These are all the basic L2 patches for 5760X including the PCI IDs: 2012a6abc876 bnxt_en: Add 5760X (P7) PCI IDs 047a2d38e40c bnxt_en: Report the new ethtool link modes in the new firmware interface 7b60cf2b641a bnxt_en: Support force speed using the new HWRM fields 30c0bb63c2ea bnxt_en: Support new firmware link parameters cf47fa5ca5bb bnxt_en: Refactor ethtool speeds logic a7445d69809f bnxt_en: Add support for new RX and TPA_START completion types for P7 39b2e62be370 bnxt_en: Refactor and refine bnxt_tpa_start() and bnxt_tpa_end(). c2f8063309da bnxt_en: Refactor RX VLAN acceleration logic. 13d2d3d381ee bnxt_en: Add new P7 hardware interface definitions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045796/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 2045233] Re: [SRU][22.04.04]: mpi3mr driver update
If you get a patch to fix the warning upstream we can pull it later once it's accepted. On Thu, Dec 14, 2023 at 3:25 AM Chandrakanth Patil < 2045...@bugs.launchpad.net> wrote: > ok, Jeff. Regarding warning: > > 1. Since there is no functional impact, we can ignore it as of now. > 2. We will submit the warning fix to upstream ASAP. > > > Do you have any suggestions on this? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/2045233 > > Title: > [SRU][22.04.04]: mpi3mr driver update > > Status in linux package in Ubuntu: > Confirmed > Status in linux source package in Jammy: > Opinion > Status in linux source package in Mantic: > Confirmed > Status in linux source package in Noble: > Confirmed > > Bug description: > [Impact] > > This update has been initiated to incorporate the mpi3mr driver from > upstream into the upcoming Ubuntu releases (Ubuntu 22.04.x point > releases). > > This has been requested by both Broadcom as the upstream and by one of > the larger OEM partners who are going to be selling systems with these > storage controllers to customers. This series of patches includes bug > fixes and support for current Broadcom controllers. > > [Fixes] > Below are the commit IDs for the latest upstream version (v6.8). > > The 22.04 LTS point kernel already includes the latest mpi3mr driver > version 8.0.0.69.0. Therefore, the listed commit IDs below correspond > to the subsequent patches. > > The commit IDs listed below are in sequential order from bottom to > top, indicating the order for applying the patches. > > linux-next > d0a60e3edaa4 scsi: mpi3mr: Update driver version to 8.5.1.0.0 > 9536af615dc9 scsi: mpi3mr: Support for preallocation of SGL BSG data > buffers part-3 > fb231d7deffb scsi: mpi3mr: Support for preallocation of SGL BSG data > buffers part-2 > c432e1675239 scsi: mpi3mr: Support for preallocation of SGL BSG data > buffers part-1 > 07ac6adda4d3 scsi: mpi3mr: Fetch correct device dev handle for status > reply descriptor > f8fb3f39148e scsi: mpi3mr: Block PEL Enable Command on Controller Reset > and Unrecoverable State > c01d515687e3 scsi: mpi3mr: Clean up block devices post controller reset > e5aab848dfdf scsi: mpi3mr: Refresh sdev queue depth after controller > reset > b4d94164ff32 scsi: mpi3mr: driver version upgrade to 8.5.0.0.50 > 1193a89d2b6d scsi: mpi3mr: Add support for status reply descriptor > cb5b60894602 scsi: mpi3mr: Increase maximum number of PHYs to 64 from 32 > c9260ff28ee5 scsi: mpi3mr: Add PCI checks where SAS5116 diverges from > SAS4116 > 6fa21eab82be scsi: mpi3mr: Add support for SAS5116 PCI IDs > > Mainline at 6.6/6.7 > 82b2fb52d6ec scsi: mpi3mr: Split off bus_reset function from host_reset > 9a9068b2afa0 scsi: mpi3mr: Update driver version to 8.5.0.0.0 > d9a5ab0ea98f scsi: mpi3mr: Enhance handling of devices removed after > controller reset > e7a8648e1ce2 scsi: mpi3mr: WRITE SAME implementation > d9adb81e67e9 scsi: mpi3mr: Add support for more than 1MB I/O > 6f81b1cfdf33 scsi: mpi3mr: Update MPI Headers to version 3.00.28 > 9134211f7bed scsi: mpi3mr: Invoke soft reset upon TSU or event ack time > out > > [Testing] > verify the mpi3mr driver is loaded > verify the version string shows 8.5.1.0.0 > > [Regression Risk] > Low. These patches are contained to the mpi3mr driver code itself and > are all already accepted upstream. They cleanly pick into our 6.5 kernel > tree. > > Broadcom has tested these and the only concern is the kernel warning > below in Comment #7 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045233/+subscriptions > > Launchpad-Notification-Type: bug > Launchpad-Bug: distribution=ubuntu; sourcepackage=linux; component=main; > status=Confirmed; importance=Medium; assignee=jeffrey.l...@canonical.com; > Launchpad-Bug: distribution=ubuntu; distroseries=jammy; > sourcepackage=linux; component=main; status=Opinion; importance=Wishlist; > assignee=None; > Launchpad-Bug: distribution=ubuntu; distroseries=mantic; > sourcepackage=linux; component=main; status=Confirmed; importance=Medium; > assignee=jeffrey.l...@canonical.com; > Launchpad-Bug: distribution=ubuntu; distroseries=noble; > sourcepackage=linux; component=main; status=Confirmed; importance=Medium; > assignee=jeffrey.l...@canonical.com; > Launchpad-Bug-Information-Type: Public > Launchpad-Bug-Private: no > Launchpad-Bug-Security-Vulnerability: no > Launchpad-Bug-Commenters: bladernr cpatubuntu > Launchpad-Bug-Reporter: Chandrakanth Patil (cpatubuntu) > Launchpad-Bug-Modifier: Chandrakanth Patil (cpatubuntu) > Launchpad-Message-Rationale: Subscriber > Launchpad-Message-For: bladernr > > -- Jeff Lane Engineering Manager IHV/OEM Alliances and Server Certification "Entropy isn't what it used to be." -- You received this bug notification because you are a member of Kernel
[Kernel-packages] [Bug 2045796] Re: Add Support for Broadcom 5760X Network adapters to 24.04 (patches in 6.8)
** Changed in: linux (Ubuntu Mantic) Importance: Undecided => Medium -- 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/2045796 Title: Add Support for Broadcom 5760X Network adapters to 24.04 (patches in 6.8) Status in linux package in Ubuntu: New Status in linux source package in Mantic: In Progress Status in linux source package in Noble: New Bug description: These patches are needed on top of v6.7 to support Broadcom 5760X Adapters. These patches currently reside in the net-next tree and will be included in v6.8. Prerequisite commits in net-next today: c1056a59aee1 bnxt_en: Optimize xmit_more TX path ba098017791e bnxt_en: Use existing MSIX vectors for all mqprio TX rings f07b58801bef bnxt_en: Add macros related to TC and TX rings f5b29c6afe36 bnxt_en: Add helper to get the number of CP rings required for TX rings 0589a1ed4d33 bnxt_en: Support up to 8 TX rings per MSIX 877edb347323 bnxt_en: Refactor bnxt_hwrm_set_coal() 5a3c585fa83f bnxt_en: New encoding for the TX opaque field ebf72319cef6 bnxt_en: Refactor bnxt_tx_int() 9c0b06de6fb6 bnxt_en: Remove BNXT_RX_HDL and BNXT_TX_HDL 7845b8dfc713 bnxt_en: Add completion ring pointer in TX and RX ring structures d1eec614100c bnxt_en: Restructure cp_ring_arr in struct bnxt_cp_ring_info 7f0a168b0441 bnxt_en: Add completion ring pointer in TX and RX ring structures 34eec1f29a59 bnxt_en: Put the TX producer information in the TX BD opaque field These 13 patches below were submitted on 11/20/23 and accepted on 11/21/23. These are the initial patches with 5760X contents. 1c7fd6ee2fe4 bnxt_en: Rename some macros for the P5 chips f94471f3ce74 bnxt_en: Modify the NAPI logic for the new P7 chips c09d22674b94 bnxt_en: Modify RX ring indexing logic. 6d1add95536b bnxt_en: Modify TX ring indexing logic. b9e0c47ee2ec bnxt_en: Add db_ring_mask and related macro to bnxt_db_info struct. 236e237f8ffe bnxt_en: Add support for HWRM_FUNC_BACKING_STORE_CFG_V2 firmware calls 6a4d0774f02d bnxt_en: Add support for new backing store query firmware API b098dc5a3357 bnxt_en: Add bnxt_setup_ctxm_pg_tbls() helper function 2ad67aea11f2 bnxt_en: Use the pg_info field in bnxt_ctx_mem_type struct 035c57615982 bnxt_en: Add page info to struct bnxt_ctx_mem_type 76087d997a84 bnxt_en: Restructure context memory data structures e50dc4c2206e bnxt_en: Free bp->ctx inside bnxt_free_ctx_mem() aa8460bacf49 bnxt_en: The caller of bnxt_alloc_ctx_mem() should always free bp->ctx The next 15 patches were submitted on 12/1/23 and accepted on 12/4/23. These are all the basic L2 patches for 5760X including the PCI IDs: 2012a6abc876 bnxt_en: Add 5760X (P7) PCI IDs 047a2d38e40c bnxt_en: Report the new ethtool link modes in the new firmware interface 7b60cf2b641a bnxt_en: Support force speed using the new HWRM fields 30c0bb63c2ea bnxt_en: Support new firmware link parameters cf47fa5ca5bb bnxt_en: Refactor ethtool speeds logic a7445d69809f bnxt_en: Add support for new RX and TPA_START completion types for P7 39b2e62be370 bnxt_en: Refactor and refine bnxt_tpa_start() and bnxt_tpa_end(). c2f8063309da bnxt_en: Refactor RX VLAN acceleration logic. 13d2d3d381ee bnxt_en: Add new P7 hardware interface definitions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045796/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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 2046430] [NEW] 22.04 kdump generate failed
Public bug reported: We use apt install kdump-tools without recommend package, and it will not install makedumpfile package, it will make the kdump generate failed. Check the console will notice: [ 18.580478] kdump-tools[578]: Starting kdump-tools: [ 18.596729] kdump-tools[583]: * running makedumpfile -F -c -d 31 /proc/vmcore | compress > /var/crash/202312140833/dump-incomplete [ 18.617167] kdump-tools[600]: /usr/sbin/kdump-config: 783: makedumpfile: not found [ 18.636226] kdump-tools[583]: * kdump-tools: saved vmcore in /var/crash/202312140833 [ 18.652078] kdump-tools[583]: * running makedumpfile --dump-dmesg /proc/vmcore /var/crash/202312140833/dmesg.202312140833 [ 18.672111] kdump-tools[583]: /usr/sbin/kdump-config: 808: makedumpfile: not found [ 18.688081] kdump-tools[583]: * kdump-tools: makedumpfile --dump-dmesg failed. dmesg content will be unavailable [ 18.708078] kdump-tools[583]: * kdump-tools: failed to save dmesg content in /var/crash/202312140833 [ 18.728308] kdump-tools[608]: Thu, 14 Dec 2023 08:33:18 + [ 18.744403] kdump-tools[609]: Rebooting. After we install makedumpfile package, kdump will generated well. I notice the relateion been change by Debian upstream, and I have no idea about it, should we change kdump-tools relationship in ubuntu source? System info before here: Description:Ubuntu 22.04.1 LTS Release:22.04 Kernel: Linux [hostname] 6.5.0-14-generic #14~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Mon Nov 20 18:15:30 UTC 2 x86_64 x86_64 x86_64 GNU/Linux Package info kdump-tools: Installed: 1:1.6.10ubuntu2.1 Candidate: 1:1.6.10ubuntu2.1 Version table: *** 1:1.6.10ubuntu2.1 500 500 https://mirrors.ustc.edu.cn/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:1.6.10ubuntu1 500 500 https://mirrors.ustc.edu.cn/ubuntu jammy/main amd64 Packages makedumpfile: Installed: 1:1.7.0-1ubuntu0.1 Candidate: 1:1.7.0-1ubuntu0.1 Version table: *** 1:1.7.0-1ubuntu0.1 500 500 https://mirrors.ustc.edu.cn/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:1.7.0-1build1 500 500 https://mirrors.ustc.edu.cn/ubuntu jammy/main amd64 Packages ** Affects: kexec-tools (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in Ubuntu. https://bugs.launchpad.net/bugs/2046430 Title: 22.04 kdump generate failed Status in kexec-tools package in Ubuntu: New Bug description: We use apt install kdump-tools without recommend package, and it will not install makedumpfile package, it will make the kdump generate failed. Check the console will notice: [ 18.580478] kdump-tools[578]: Starting kdump-tools: [ 18.596729] kdump-tools[583]: * running makedumpfile -F -c -d 31 /proc/vmcore | compress > /var/crash/202312140833/dump-incomplete [ 18.617167] kdump-tools[600]: /usr/sbin/kdump-config: 783: makedumpfile: not found [ 18.636226] kdump-tools[583]: * kdump-tools: saved vmcore in /var/crash/202312140833 [ 18.652078] kdump-tools[583]: * running makedumpfile --dump-dmesg /proc/vmcore /var/crash/202312140833/dmesg.202312140833 [ 18.672111] kdump-tools[583]: /usr/sbin/kdump-config: 808: makedumpfile: not found [ 18.688081] kdump-tools[583]: * kdump-tools: makedumpfile --dump-dmesg failed. dmesg content will be unavailable [ 18.708078] kdump-tools[583]: * kdump-tools: failed to save dmesg content in /var/crash/202312140833 [ 18.728308] kdump-tools[608]: Thu, 14 Dec 2023 08:33:18 + [ 18.744403] kdump-tools[609]: Rebooting. After we install makedumpfile package, kdump will generated well. I notice the relateion been change by Debian upstream, and I have no idea about it, should we change kdump-tools relationship in ubuntu source? System info before here: Description: Ubuntu 22.04.1 LTS Release: 22.04 Kernel: Linux [hostname] 6.5.0-14-generic #14~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Mon Nov 20 18:15:30 UTC 2 x86_64 x86_64 x86_64 GNU/Linux Package info kdump-tools: Installed: 1:1.6.10ubuntu2.1 Candidate: 1:1.6.10ubuntu2.1 Version table: *** 1:1.6.10ubuntu2.1 500 500 https://mirrors.ustc.edu.cn/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:1.6.10ubuntu1 500 500 https://mirrors.ustc.edu.cn/ubuntu jammy/main amd64 Packages makedumpfile: Installed: 1:1.7.0-1ubuntu0.1 Candidate: 1:1.7.0-1ubuntu0.1 Version table: *** 1:1.7.0-1ubuntu0.1 500 500 https://mirrors.ustc.edu.cn/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:1.7.0-1build1 500 500 https://mirrors.ustc.edu.cn/ubuntu jammy/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/20
[Kernel-packages] [Bug 2037390] Re: Missing firmware for Intel CNVi AX211 on Intel Meteor Lake platform
** Changed in: linux-firmware (Ubuntu)
Status: Fix Released => In Progress
** Changed in: linux-firmware (Ubuntu)
Importance: Undecided => High
** Changed in: linux-firmware (Ubuntu)
Assignee: (unassigned) => You-Sheng Yang (vicamo)
** Changed in: linux-firmware (Ubuntu Jammy)
Status: Incomplete => In Progress
** Changed in: linux-firmware (Ubuntu Mantic)
Status: Incomplete => In Progress
--
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/2037390
Title:
Missing firmware for Intel CNVi AX211 on Intel Meteor Lake platform
Status in HWE Next:
New
Status in OEM Priority Project:
New
Status in linux-firmware package in Ubuntu:
In Progress
Status in linux-firmware source package in Jammy:
In Progress
Status in linux-firmware source package in Mantic:
In Progress
Bug description:
[SRU Justification]
[Impact]
[98/17872]
Missing firmware for Intel CNVi AX211/AX201 on Intel MTL/RPL platforms. For
example:
iwlwifi :00:14.3: PCI dev 7e40/4090, rev=0x441, rfid=0x2010d000
iwlwifi :00:14.3: no suitable firmware found!
iwlwifi :00:14.3: minimum version required: iwlwifi-ma-b0-gf-a0-59
iwlwifi :00:14.3: maximum version supported: iwlwifi-ma-b0-gf-a0-83
iwlwifi :00:14.3: check
git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
And Bluetooth:
Bluetooth: hci0: Failed to load Intel firmware file intel/ibt-0180-0041.sfi
(-2)
[Fix]
There are plenty of commits to be SRUed in the WiFi part due to modifications
to
pnvm files. Intel may and may not update their unversioned pnvm file upon new
releases, therefore on pulling any ucode version of iwlwifi firmware, the full
history of an unversioned pnvm file has to be pulled as well, and each may or
may not pull an older ucode version of that firmware.
Most of the commits have been included in Mantic and newer. For Noble, it
depends on an additional commit 92e24e048136 ("iwlwifi: add a missing FW from
core80-39 release") that has been backported to Jammy and Mantic in bug
2042716.
Also note that commit a6744df81a30 ("iwlwifi: add FWs for new GL and MA device
types with multiple RF modules") is also being backported in bug 2028065.
[Test Case]
Boot with firmware blobs installed, and iwlwifi and btintel should probe
successfully without error.
[Where problems could occur]
[Kernel-packages] [Bug 2042090] Re: Orchid Bay MLK2/Maya Bay MLK soundwire support
There doesn't seem to be anything to sponsor here, so I'm unsubscribing
ubuntu-sponsors. Please make sure to keep your ubuntu-sponsors
subscriptions current so we don't waste time in complex multi package
bugs trying to figure out if there's anything to do for us.
--
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/2042090
Title:
Orchid Bay MLK2/Maya Bay MLK soundwire support
Status in HWE Next:
New
Status in firmware-sof package in Ubuntu:
Fix Released
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-6.5 package in Ubuntu:
Invalid
Status in firmware-sof source package in Jammy:
Fix Committed
Status in linux source package in Jammy:
Invalid
Status in linux-oem-6.5 source package in Jammy:
Fix Committed
Status in firmware-sof source package in Mantic:
Fix Committed
Status in linux source package in Mantic:
Fix Committed
Status in linux-oem-6.5 source package in Mantic:
Invalid
Status in firmware-sof source package in Noble:
Fix Released
Status in linux source package in Noble:
In Progress
Status in linux-oem-6.5 source package in Noble:
Invalid
Bug description:
[SRU Justifications]
== kernels ==
[Impact]
Audio doesn't work on Dell Orchid Bay MLK2/Maya Bay MLK platforms.
[Fix]
Kernel driver, ALSA ucm, and firmware fixes are needed. For the kernel part,
following upstream commits are mandatory:
* commit e70ca580e9c8 ("ASoC: Intel: soc-acpi-intel-mtl-match: add rt713
rt1316 config")
* commit b6d6e5abf645 ("ASoC: Intel: sof_sdw_rt_sdca_jack_common: add rt713
support")
* commit 5124d08d0ea4 ("ASoC: Intel: sof_sdw_rt712_sdca: construct
cards->components by name_prefix")
* commit 817178e7674b ("ASoC: Intel: soc-acpi: rt713+rt1316, no sdw-dmic
config"): linux-next
[Test Case]
1. enable -proposed pocket and install the latest kernel
2. browse youtube, hold backspace on virtual terminal or whatever makes some
noises
3. expected sound system brought up and reacts accordingly
[Where problems could occur]
While this enables new devices on new platforms, we may bump into
burst noises, power consumption problems at corner cases not covered
by test program.
[Other Info]
This is to enable sof devices on Intel MTL platform, which is only
supported since 6.5 kernels, e.g. oem-6.5. Nominate Noble, Mantic, and
Jammy.
== firmware-sof ==
[Impact]
Audio doesn't work on Dell Orchid Bay MLK2/Maya Bay MLK platforms.
[Fix]
Kernel driver, ALSA ucm, and firmware fixes are needed. For firmware-
sof, it's the upstream commit 99466c05f15f ("Add Intel SOF2.7.2
topology files").
[Test Case]
1. enable -proposed pocket and install firmware-sof-signed
2. browse youtube, hold backspace on virtual terminal or whatever makes some
noises
3. expected sound system brought up and reacts accordingly
[Where problems could occur]
While this enables new devices on new platforms, we may bump into
burst noises, power consumption problems at corner cases not covered
by test program.
[Other Info]
This is to enable sof devices on Intel MTL platform, which is only
supported since 6.5 kernels, e.g. oem-6.5. Nominate Noble, Mantic, and
Jammy.
== original bug report ==
The kernel patches has been applied in the ASoC tree.
Re: [PATCH 00/23] ASoC: Intel: boards: updates for 6.7 — ALSA Devel
(spinics.net) [spinics.net]
https://www.spinics.net/lists/alsa-devel/msg167273.html
We need 3/23, 4/23, 6/23, and
https://github.com/thesofproject/linux/commit/037809ef79874a610216fd6b6d50f53e069b5176
And the UCM PR is submitted
ucm2: soundwire: add rt713 SDCA device by shumingfan · Pull Request #363 ·
alsa-project/alsa-ucm-conf (github.com) [github.com]
https://github.com/alsa-project/alsa-ucm-conf/pull/363
See bug 2042902.
For firmware-sof, need upstream commit 99466c05f15f ("Add Intel
SOF2.7.2 topology files").
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2042090/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037390] Re: Missing firmware for Intel CNVi AX211 on Intel Meteor Lake platform
SRU:
* https://lists.ubuntu.com/archives/kernel-team/2023-December/147593.html
(jammy)
* https://lists.ubuntu.com/archives/kernel-team/2023-December/147594.html
(mantic)
* https://lists.ubuntu.com/archives/kernel-team/2023-December/147595.html
(noble)
** Description changed:
[SRU Justification]
- [Impact]
-
- Missing firmware for Intel CNVi AX211 on Intel Meteor Lake platform.
-
- iwlwifi :00:14.3: PCI dev 7e40/4090, rev=0x441, rfid=0x2010d000
- iwlwifi :00:14.3: no suitable firmware found!
- iwlwifi :00:14.3: minimum version required: iwlwifi-ma-b0-gf-a0-59
- iwlwifi :00:14.3: maximum version supported: iwlwifi-ma-b0-gf-a0-83
+ [Impact]
[98/17872]
+
+ Missing firmware for Intel CNVi AX211/AX201 on Intel MTL/RPL platforms. For
+ example:
+
+ iwlwifi :00:14.3: PCI dev 7e40/4090, rev=0x441, rfid=0x2010d000
+ iwlwifi :00:14.3: no suitable firmware found!
+ iwlwifi :00:14.3: minimum version required: iwlwifi-ma-b0-gf-a0-59
+ iwlwifi :00:14.3: maximum version supported: iwlwifi-ma-b0-gf-a0-83
iwlwifi :00:14.3: check
git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
-
- And Bluetooth:
-
- Bluetooth: hci0: Failed to load Intel firmware file
- intel/ibt-0180-0041.sfi (-2)
-
- [Fix]
-
- 3 upstream commits needed.
-
- For the first commit for iwlwifi, it supports both AX211 and BE200 (for bug
- 2028065).
-
- [Test Case]
-
+
+ And Bluetooth:
+
+ Bluetooth: hci0: Failed to load Intel firmware file intel/ibt-0180-0041.sfi
(-2)
+
+ [Fix]
+
+ There are plenty of commits to be SRUed in the WiFi part due to modifications
to
+ pnvm files. Intel may and may not update their unversioned pnvm file upon new
+ releases, therefore on pulling any ucode version of iwlwifi firmware, the full
+ history of an unversioned pnvm file has to be pulled as well, and each may or
+ may not pull an older ucode version of that firmware.
+
+ Most of the commits have been included in Mantic and newer. For Noble, it
+ depends on an additional commit 92e24e048136 ("iwlwifi: add a missing FW from
+ core80-39 release") that has been backported to Jammy and Mantic in bug
2042716.
+
+ Also note that commit a6744df81a30 ("iwlwifi: add FWs for new GL and MA device
+ types with multiple RF modules") is also being backported in bug 2028065.
+
+ [Test Case]
+
Boot with firmware blobs installed, and iwlwifi and btintel should probe
- successfully without error.
-
- [Where problems could occur]
-
- While this introduces support for new hardware on new platforms, expect every
- possible problem.
-
- [Other Info]
-
- We're to support oem-6.5/jammy, and mantic for best effort. While there is no
- Noble branch yet, Noble is not nominated.
+ successfully without error.
[Kernel-packages] [Bug 2037214] Re: evict_inodes inode xxx, i_count = 1, was skipped!
I do have the same messages (6.5.0-14-generic #14~22.04.1-Ubuntu) in the
dmesg after booting, but I don't use ceph nor do I have an usb drive
connected.
--
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/2037214
Title:
evict_inodes inode xxx, i_count = 1, was skipped!
Status in linux package in Ubuntu:
Confirmed
Status in linux-meta-hwe-6.5 package in Ubuntu:
New
Status in linux-oem-6.5 package in Ubuntu:
Confirmed
Bug description:
Hi,
during boot the kernel logs the following messages:
# dmesg | grep evict_inodes
[ 12.784805] evict_inodes inode d69da69b, i_count = 1, was skipped!
[ 12.784810] evict_inodes inode 8b9a7c55, i_count = 1, was skipped!
[ 12.784811] evict_inodes inode 8ff8e64c, i_count = 1, was skipped!
[ 12.784811] evict_inodes inode 194d080e, i_count = 1, was skipped!
[ 12.784812] evict_inodes inode 09b77b7b, i_count = 1, was skipped!
[ 12.811217] evict_inodes inode ec873c71, i_count = 1, was skipped!
[ 12.811222] evict_inodes inode 72bf501d, i_count = 1, was skipped!
[ 12.811223] evict_inodes inode b42b829a, i_count = 1, was skipped!
[ 12.811224] evict_inodes inode c7c5b4ef, i_count = 1, was skipped!
[ 13.412667] evict_inodes inode 61a23a39, i_count = 1, was skipped!
[ 13.412671] evict_inodes inode b42b829a, i_count = 1, was skipped!
[ 13.412671] evict_inodes inode 72bf501d, i_count = 1, was skipped!
[ 13.412672] evict_inodes inode c7c5b4ef, i_count = 1, was skipped!
[ 13.412673] evict_inodes inode ec873c71, i_count = 1, was skipped!
Those messages are not displayed when I boot my system with a mainline Linux
kernel.
Moreover, in the mainline Linux source code, I do not find the lines where
such a message could be printed.
Therefore, those messages are probably caused by an Ubuntu patch.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-5-generic 6.5.0-5.5
ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
Uname: Linux 6.5.0-5-generic x86_64
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: bonnaudl 4827 F wireplumber
/dev/snd/seq:bonnaudl 4808 F pipewire
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Sun Sep 24 14:39:10 2023
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-5-generic
root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor
tpm_tis.interrupts=0 preempt=full split_lock_detect=off quiet splash
vt.handoff=7
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-5-generic N/A
linux-backports-modules-6.5.0-5-generic N/A
linux-firmware 20230919.git3672ccab-0ubuntu2
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/26/2022
dmi.bios.release: 7.16
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: 1.07.16NRTR4
dmi.board.asset.tag: Tag 12345
dmi.board.name: NS50_70MU
dmi.board.vendor: TUXEDO
dmi.board.version: Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Notebook
dmi.chassis.version: N/A
dmi.ec.firmware.release: 7.7
dmi.modalias:
dmi:bvnINSYDECorp.:bvr1.07.16NRTR4:bd05/26/2022:br7.16:efr7.7:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50_70MU:rvrApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable:
dmi.product.family: Not Applicable
dmi.product.name: TUXEDO InfinityBook S 15 Gen6
dmi.product.sku: Not Applicable
dmi.product.version: Not Applicable
dmi.sys.vendor: TUXEDO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2037214/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037214] Re: evict_inodes inode xxx, i_count = 1, was skipped!
** Also affects: linux-meta-hwe-6.5 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2037214
Title:
evict_inodes inode xxx, i_count = 1, was skipped!
Status in linux package in Ubuntu:
Confirmed
Status in linux-meta-hwe-6.5 package in Ubuntu:
New
Status in linux-oem-6.5 package in Ubuntu:
Confirmed
Bug description:
Hi,
during boot the kernel logs the following messages:
# dmesg | grep evict_inodes
[ 12.784805] evict_inodes inode d69da69b, i_count = 1, was skipped!
[ 12.784810] evict_inodes inode 8b9a7c55, i_count = 1, was skipped!
[ 12.784811] evict_inodes inode 8ff8e64c, i_count = 1, was skipped!
[ 12.784811] evict_inodes inode 194d080e, i_count = 1, was skipped!
[ 12.784812] evict_inodes inode 09b77b7b, i_count = 1, was skipped!
[ 12.811217] evict_inodes inode ec873c71, i_count = 1, was skipped!
[ 12.811222] evict_inodes inode 72bf501d, i_count = 1, was skipped!
[ 12.811223] evict_inodes inode b42b829a, i_count = 1, was skipped!
[ 12.811224] evict_inodes inode c7c5b4ef, i_count = 1, was skipped!
[ 13.412667] evict_inodes inode 61a23a39, i_count = 1, was skipped!
[ 13.412671] evict_inodes inode b42b829a, i_count = 1, was skipped!
[ 13.412671] evict_inodes inode 72bf501d, i_count = 1, was skipped!
[ 13.412672] evict_inodes inode c7c5b4ef, i_count = 1, was skipped!
[ 13.412673] evict_inodes inode ec873c71, i_count = 1, was skipped!
Those messages are not displayed when I boot my system with a mainline Linux
kernel.
Moreover, in the mainline Linux source code, I do not find the lines where
such a message could be printed.
Therefore, those messages are probably caused by an Ubuntu patch.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-5-generic 6.5.0-5.5
ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
Uname: Linux 6.5.0-5-generic x86_64
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: bonnaudl 4827 F wireplumber
/dev/snd/seq:bonnaudl 4808 F pipewire
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Sun Sep 24 14:39:10 2023
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-5-generic
root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor
tpm_tis.interrupts=0 preempt=full split_lock_detect=off quiet splash
vt.handoff=7
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-5-generic N/A
linux-backports-modules-6.5.0-5-generic N/A
linux-firmware 20230919.git3672ccab-0ubuntu2
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/26/2022
dmi.bios.release: 7.16
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: 1.07.16NRTR4
dmi.board.asset.tag: Tag 12345
dmi.board.name: NS50_70MU
dmi.board.vendor: TUXEDO
dmi.board.version: Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Notebook
dmi.chassis.version: N/A
dmi.ec.firmware.release: 7.7
dmi.modalias:
dmi:bvnINSYDECorp.:bvr1.07.16NRTR4:bd05/26/2022:br7.16:efr7.7:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50_70MU:rvrApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable:
dmi.product.family: Not Applicable
dmi.product.name: TUXEDO InfinityBook S 15 Gen6
dmi.product.sku: Not Applicable
dmi.product.version: Not Applicable
dmi.sys.vendor: TUXEDO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2037214/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2045233] Re: [SRU][22.04.04]: mpi3mr driver update
OK. I will submit the patch to upstream ASAP. -- 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/2045233 Title: [SRU][22.04.04]: mpi3mr driver update Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: Opinion Status in linux source package in Mantic: Confirmed Status in linux source package in Noble: Confirmed Bug description: [Impact] This update has been initiated to incorporate the mpi3mr driver from upstream into the upcoming Ubuntu releases (Ubuntu 22.04.x point releases). This has been requested by both Broadcom as the upstream and by one of the larger OEM partners who are going to be selling systems with these storage controllers to customers. This series of patches includes bug fixes and support for current Broadcom controllers. [Fixes] Below are the commit IDs for the latest upstream version (v6.8). The 22.04 LTS point kernel already includes the latest mpi3mr driver version 8.0.0.69.0. Therefore, the listed commit IDs below correspond to the subsequent patches. The commit IDs listed below are in sequential order from bottom to top, indicating the order for applying the patches. linux-next d0a60e3edaa4 scsi: mpi3mr: Update driver version to 8.5.1.0.0 9536af615dc9 scsi: mpi3mr: Support for preallocation of SGL BSG data buffers part-3 fb231d7deffb scsi: mpi3mr: Support for preallocation of SGL BSG data buffers part-2 c432e1675239 scsi: mpi3mr: Support for preallocation of SGL BSG data buffers part-1 07ac6adda4d3 scsi: mpi3mr: Fetch correct device dev handle for status reply descriptor f8fb3f39148e scsi: mpi3mr: Block PEL Enable Command on Controller Reset and Unrecoverable State c01d515687e3 scsi: mpi3mr: Clean up block devices post controller reset e5aab848dfdf scsi: mpi3mr: Refresh sdev queue depth after controller reset b4d94164ff32 scsi: mpi3mr: driver version upgrade to 8.5.0.0.50 1193a89d2b6d scsi: mpi3mr: Add support for status reply descriptor cb5b60894602 scsi: mpi3mr: Increase maximum number of PHYs to 64 from 32 c9260ff28ee5 scsi: mpi3mr: Add PCI checks where SAS5116 diverges from SAS4116 6fa21eab82be scsi: mpi3mr: Add support for SAS5116 PCI IDs Mainline at 6.6/6.7 82b2fb52d6ec scsi: mpi3mr: Split off bus_reset function from host_reset 9a9068b2afa0 scsi: mpi3mr: Update driver version to 8.5.0.0.0 d9a5ab0ea98f scsi: mpi3mr: Enhance handling of devices removed after controller reset e7a8648e1ce2 scsi: mpi3mr: WRITE SAME implementation d9adb81e67e9 scsi: mpi3mr: Add support for more than 1MB I/O 6f81b1cfdf33 scsi: mpi3mr: Update MPI Headers to version 3.00.28 9134211f7bed scsi: mpi3mr: Invoke soft reset upon TSU or event ack time out [Testing] verify the mpi3mr driver is loaded verify the version string shows 8.5.1.0.0 [Regression Risk] Low. These patches are contained to the mpi3mr driver code itself and are all already accepted upstream. They cleanly pick into our 6.5 kernel tree. Broadcom has tested these and the only concern is the kernel warning below in Comment #7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045233/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2046439] [NEW] Wrong code execution of s390x code with qemu TCG
You have been subscribed to a public bug: ---Problem Description--- Wrong code execution with qemu ---Steps to Reproduce--- please have a look at the following bug: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112986 Contact Information = Andreas Krebbel Machine Type = IBM Z Userspace tool common name: qemu The userspace tool has the following bit modes: 64 bit Userspace deb: - 1:6.2+dfsg-2ubuntu6.15 Frequently used s390x code sequences are wrongly executed when running with qemu instruction set emulation. The problem has been fixed in upstream qemu already. A backport for qemu 7 branch has been committed as well. The qemu 6.2.0 version used in Ubuntu 22.04 needs a backport of a trivial fix to work properly: >From the GCC BZ: Problem fixed in v8.0.0 (https://gitlab.com/qemu-project/qemu/-/commit/54fce97cfcaf5463ee5f325bc1f1d4adc2772f38). The fix was backported to v7.2.2 (https://gitlab.com/qemu-project/qemu/-/commit/17b032c6598ea756889f25e8d3e4cd9f2036669b), but not to v6. Please consider picking up https://gitlab.com/qemu-project/qemu/-/commit/17b032c6598ea756889f25e8d3e4cd9f2036669b for the Ubuntu 22.04 qemu package 1:6.2+dfsg-2ubuntu6.15 ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-204491 severity-high targetmilestone-inin--- -- Wrong code execution of s390x code with qemu TCG https://bugs.launchpad.net/bugs/2046439 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2046439] [NEW] Wrong code execution of s390x code with qemu TCG
Public bug reported: ---Problem Description--- Wrong code execution with qemu ---Steps to Reproduce--- please have a look at the following bug: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112986 Contact Information = Andreas Krebbel Machine Type = IBM Z Userspace tool common name: qemu The userspace tool has the following bit modes: 64 bit Userspace deb: - 1:6.2+dfsg-2ubuntu6.15 Frequently used s390x code sequences are wrongly executed when running with qemu instruction set emulation. The problem has been fixed in upstream qemu already. A backport for qemu 7 branch has been committed as well. The qemu 6.2.0 version used in Ubuntu 22.04 needs a backport of a trivial fix to work properly: >From the GCC BZ: Problem fixed in v8.0.0 (https://gitlab.com/qemu-project/qemu/-/commit/54fce97cfcaf5463ee5f325bc1f1d4adc2772f38). The fix was backported to v7.2.2 (https://gitlab.com/qemu-project/qemu/-/commit/17b032c6598ea756889f25e8d3e4cd9f2036669b), but not to v6. Please consider picking up https://gitlab.com/qemu-project/qemu/-/commit/17b032c6598ea756889f25e8d3e4cd9f2036669b for the Ubuntu 22.04 qemu package 1:6.2+dfsg-2ubuntu6.15 ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-204491 severity-high targetmilestone-inin--- ** Tags added: architecture-s39064 bugnameltc-204491 severity-high targetmilestone-inin--- ** Changed in: ubuntu Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Package changed: 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/2046439 Title: Wrong code execution of s390x code with qemu TCG Status in linux package in Ubuntu: New Bug description: ---Problem Description--- Wrong code execution with qemu ---Steps to Reproduce--- please have a look at the following bug: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112986 Contact Information = Andreas Krebbel Machine Type = IBM Z Userspace tool common name: qemu The userspace tool has the following bit modes: 64 bit Userspace deb: - 1:6.2+dfsg-2ubuntu6.15 Frequently used s390x code sequences are wrongly executed when running with qemu instruction set emulation. The problem has been fixed in upstream qemu already. A backport for qemu 7 branch has been committed as well. The qemu 6.2.0 version used in Ubuntu 22.04 needs a backport of a trivial fix to work properly: From the GCC BZ: Problem fixed in v8.0.0 (https://gitlab.com/qemu-project/qemu/-/commit/54fce97cfcaf5463ee5f325bc1f1d4adc2772f38). The fix was backported to v7.2.2 (https://gitlab.com/qemu-project/qemu/-/commit/17b032c6598ea756889f25e8d3e4cd9f2036669b), but not to v6. Please consider picking up https://gitlab.com/qemu-project/qemu/-/commit/17b032c6598ea756889f25e8d3e4cd9f2036669b for the Ubuntu 22.04 qemu package 1:6.2+dfsg-2ubuntu6.15 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2046439/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2046439] Re: Wrong code execution of s390x code with qemu TCG
** Package changed: linux (Ubuntu) => qemu (Ubuntu) ** Also affects: ubuntu-z-systems Importance: Undecided Status: New ** Changed in: ubuntu-z-systems Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Changed in: qemu (Ubuntu) Assignee: Skipper Bug Screeners (skipper-screen-team) => (unassigned) ** Changed in: ubuntu-z-systems Importance: Undecided => High ** Changed in: ubuntu-z-systems Status: New => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2046439 Title: Wrong code execution of s390x code with qemu TCG Status in Ubuntu on IBM z Systems: Triaged Status in qemu package in Ubuntu: New Bug description: ---Problem Description--- Wrong code execution with qemu ---Steps to Reproduce--- please have a look at the following bug: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112986 Contact Information = Andreas Krebbel Machine Type = IBM Z Userspace tool common name: qemu The userspace tool has the following bit modes: 64 bit Userspace deb: - 1:6.2+dfsg-2ubuntu6.15 Frequently used s390x code sequences are wrongly executed when running with qemu instruction set emulation. The problem has been fixed in upstream qemu already. A backport for qemu 7 branch has been committed as well. The qemu 6.2.0 version used in Ubuntu 22.04 needs a backport of a trivial fix to work properly: From the GCC BZ: Problem fixed in v8.0.0 (https://gitlab.com/qemu-project/qemu/-/commit/54fce97cfcaf5463ee5f325bc1f1d4adc2772f38). The fix was backported to v7.2.2 (https://gitlab.com/qemu-project/qemu/-/commit/17b032c6598ea756889f25e8d3e4cd9f2036669b), but not to v6. Please consider picking up https://gitlab.com/qemu-project/qemu/-/commit/17b032c6598ea756889f25e8d3e4cd9f2036669b for the Ubuntu 22.04 qemu package 1:6.2+dfsg-2ubuntu6.15 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2046439/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2046440] [NEW] Enforce RETPOLINE and SLS mitigrations
Public bug reported: Enforce RETPOLINE and SLS mitigrations Currently retpoline ABI checks in the kernel build do nothing. They produce no output, as if everything is fine. And if one manually hacks makefile to "forget" retpoline & SLS mitigration flags, objtool prints lots of warnings, retpoline ABI check passes and the build is succesful. Yet totally vulnerable. Proposal is to enforce objtool warnings as fatal errors for RETPOLINE and SLS, as tested to be passed on mantic for both kernel and all available dkms. And otherwise rip out custom Ubuntu retpoline abi checks. I have prepared this for noble v6.7 kernel, once this lands, I will make appropriate backports for earlier series as we likely want usable retpoline build time enforcement in earlier series too where possible. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2046440 Title: Enforce RETPOLINE and SLS mitigrations Status in linux package in Ubuntu: New Bug description: Enforce RETPOLINE and SLS mitigrations Currently retpoline ABI checks in the kernel build do nothing. They produce no output, as if everything is fine. And if one manually hacks makefile to "forget" retpoline & SLS mitigration flags, objtool prints lots of warnings, retpoline ABI check passes and the build is succesful. Yet totally vulnerable. Proposal is to enforce objtool warnings as fatal errors for RETPOLINE and SLS, as tested to be passed on mantic for both kernel and all available dkms. And otherwise rip out custom Ubuntu retpoline abi checks. I have prepared this for noble v6.7 kernel, once this lands, I will make appropriate backports for earlier series as we likely want usable retpoline build time enforcement in earlier series too where possible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2046440/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2046440] Re: Enforce RETPOLINE and SLS mitigrations
** Description changed: + [ Impact ] + Enforce RETPOLINE and SLS mitigrations Currently retpoline ABI checks in the kernel build do nothing. They produce no output, as if everything is fine. And if one manually hacks makefile to "forget" retpoline & SLS mitigration flags, objtool prints lots of warnings, retpoline ABI check passes and the build is succesful. Yet totally vulnerable. Proposal is to enforce objtool warnings as fatal errors for RETPOLINE and SLS, as tested to be passed on mantic for both kernel and all available dkms. And otherwise rip out custom Ubuntu retpoline abi checks. I have prepared this for noble v6.7 kernel, once this lands, I will make appropriate backports for earlier series as we likely want usable retpoline build time enforcement in earlier series too where possible. + + [ Test Plan ] + + * Hack arch/x86/Makefile and comment out KBUILD_CFLAGS += + $(RETPOLINE_CFLAGS) + + This simulate a build infrastructure, or toolchain regression, or hand- + written assembly code that is susceptible to speculative attacks. + + Attempt to build the kernel. + + The kernel build must fail. Currently it doesn't, and retpoline ABI + checks do not catch it. + + + [ Where problems could occur ] + + * This change will make our kernel build more strict, especially for + dkms packages. dkms packages that ship in Ubuntu archive have been build + tested to pass with these more strict requirements in place. Other + external modules that fail with such strict configuration should either + fix their code to be retpoline/redbleed safe - or use a config override + CONFIG_RETPOLINE=n to disable retpoline during their build, or otherwise + use one of the OBJTOOL_ settings in their dkms Makefiles to skip objtool + on given portions of code, or otherwise mark things as retpoline_safe / + noreturn / etc. See examples in the linux upstream source code. + + [ Other Info ] + + * This work was done as part of hackathon questioning abi checks usefulness, given I have never experienced retpoline check failure. And they have always been empty since early v4.15 days https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/bionic/tree/debian.master/abi/4.15.0-13.14/amd64/generic.retpoline?h=Ubuntu-4.15.0-14.15 ** Description changed: [ Impact ] Enforce RETPOLINE and SLS mitigrations Currently retpoline ABI checks in the kernel build do nothing. They produce no output, as if everything is fine. And if one manually hacks makefile to "forget" retpoline & SLS mitigration flags, objtool prints lots of warnings, retpoline ABI check passes and the build is succesful. Yet totally vulnerable. Proposal is to enforce objtool warnings as fatal errors for RETPOLINE and SLS, as tested to be passed on mantic for both kernel and all available dkms. And otherwise rip out custom Ubuntu retpoline abi checks. I have prepared this for noble v6.7 kernel, once this lands, I will make appropriate backports for earlier series as we likely want usable retpoline build time enforcement in earlier series too where possible. [ Test Plan ] - * Hack arch/x86/Makefile and comment out KBUILD_CFLAGS += + Hack arch/x86/Makefile and comment out KBUILD_CFLAGS += $(RETPOLINE_CFLAGS) This simulate a build infrastructure, or toolchain regression, or hand- written assembly code that is susceptible to speculative attacks. Attempt to build the kernel. The kernel build must fail. Currently it doesn't, and retpoline ABI checks do not catch it. + Another approach is to build a known buggy dkms modules on x86 - for + example zfs-dkms with ret -> RET changes reverted in assembly + accelerated code. [ Where problems could occur ] - * This change will make our kernel build more strict, especially for - dkms packages. dkms packages that ship in Ubuntu archive have been build + This change will make our kernel build more strict, especially for dkms + packages. dkms packages that ship in Ubuntu archive have been build tested to pass with these more strict requirements in place. Other external modules that fail with such strict configuration should either fix their code to be retpoline/redbleed safe - or use a config override CONFIG_RETPOLINE=n to disable retpoline during their build, or otherwise use one of the OBJTOOL_ settings in their dkms Makefiles to skip objtool on given portions of code, or otherwise mark things as retpoline_safe / noreturn / etc. See examples in the linux upstream source code. [ Other Info ] - - * This work was done as part of hackathon questioning abi checks usefulness, given I have never experienced retpoline check failure. And they have always been empty since early v4.15 days https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/bionic/tree/debian.master/abi/4.15.0-13.14/amd64/generic.retpoline?h=Ubuntu-4.15.0-14.15 + + This work was done as part of hackathon questi
[Kernel-packages] [Bug 2046444] [NEW] Missing tp_smapi dkms module in 6.5-hwe
Public bug reported: During the 6.5-hwe migration test, I found that there was a missing dkms which is tp_smapi. I just randomly picked some test results for your reference. https://certification.canonical.com/hardware/202106-29206/submission/344990/test/71814/result/37864278/ https://certification.canonical.com/hardware/202005-27944/submission/344995/test/71814/result/37864862/ https://certification.canonical.com/hardware/202008-28111/submission/344988/test/71814/result/37863988/ ** Affects: linux-signed-hwe-6.5 (Ubuntu) Importance: Undecided Status: New ** Tags: cert-sru -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2046444 Title: Missing tp_smapi dkms module in 6.5-hwe Status in linux-signed-hwe-6.5 package in Ubuntu: New Bug description: During the 6.5-hwe migration test, I found that there was a missing dkms which is tp_smapi. I just randomly picked some test results for your reference. https://certification.canonical.com/hardware/202106-29206/submission/344990/test/71814/result/37864278/ https://certification.canonical.com/hardware/202005-27944/submission/344995/test/71814/result/37864862/ https://certification.canonical.com/hardware/202008-28111/submission/344988/test/71814/result/37863988/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2046444/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2046451] [NEW] SSD read/write error on ASUS Vivobook S15 S533 (11th Gen Intel) running Ubuntu 22.04 after update
Public bug reported: Here is the full description of the problem: https://superuser.com/questions/1819429/ssd-read-write-error-on-asus- vivobook-s15-s533-11th-gen-intel-running-ubuntu-2 I have Ubuntu 22.04 upgraded from 20.04 installed in 2020. This machine]1 worked well with kernel 5.15.0-43. After recent update (2023.11.28) it often crashes random with I/O error. While crashing it does not write into log file as the ssd is not writable(!). It should be a firmware or kernel error as Ubuntu 22.04 with kernel 5.15.0-43 works well from pendrive. Windows 11 also works well from its partition. I did not find any hardware issue. Root / is mounted at /dev/nvme0n1p5 and /home is at /dev/nvme0n1p6 After setting grub to: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvme_core.default_ps_max_latency_us=0 pcie_aspm=off*" the notebook stopped crashing ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-37-generic 6.2.0-37.38~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Thu Dec 14 14:48:18 2023 InstallationDate: Installed on 2023-12-02 (11 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-6.2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2046451 Title: SSD read/write error on ASUS Vivobook S15 S533 (11th Gen Intel) running Ubuntu 22.04 after update Status in linux-signed-hwe-6.2 package in Ubuntu: New Bug description: Here is the full description of the problem: https://superuser.com/questions/1819429/ssd-read-write-error-on-asus- vivobook-s15-s533-11th-gen-intel-running-ubuntu-2 I have Ubuntu 22.04 upgraded from 20.04 installed in 2020. This machine]1 worked well with kernel 5.15.0-43. After recent update (2023.11.28) it often crashes random with I/O error. While crashing it does not write into log file as the ssd is not writable(!). It should be a firmware or kernel error as Ubuntu 22.04 with kernel 5.15.0-43 works well from pendrive. Windows 11 also works well from its partition. I did not find any hardware issue. Root / is mounted at /dev/nvme0n1p5 and /home is at /dev/nvme0n1p6 After setting grub to: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvme_core.default_ps_max_latency_us=0 pcie_aspm=off*" the notebook stopped crashing ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-37-generic 6.2.0-37.38~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Thu Dec 14 14:48:18 2023 InstallationDate: Installed on 2023-12-02 (11 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2046451/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2044657] Re: Multiple data corruption issues in zfs
I am also interested if there will be release for Jammy soon? -- 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/2044657 Title: Multiple data corruption issues in zfs Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Xenial: Confirmed Status in zfs-linux source package in Bionic: Confirmed Status in zfs-linux source package in Focal: Confirmed Status in zfs-linux source package in Jammy: Confirmed Status in zfs-linux source package in Lunar: Confirmed Status in zfs-linux source package in Mantic: Incomplete Status in zfs-linux source package in Noble: Fix Released Bug description: [ Impact ] * Multiple data corruption issues have been identified and fixed in ZFS. Some of them, at varying real-life reproducibility frequency have been deterimed to affect very old zfs releases. Recommendation is to upgrade to 2.2.2 or 2.1.14 or backport dnat patch alone. This is to ensure users get other potentially related fixes and runtime tunables to possibly mitigate other bugs that are related and are being fixed upstream for future releases. * For jammy the 2.1.14 upgrade will bring HWE kernel support and also compatiblity/support for hardened kernel builds that mitigate SLS (straight-line-speculation). [ Test Plan ] * !!! Danger !!! use reproducer from https://zfsonlinux.topicbox.com/groups/zfs-discuss/T12876116b8607cdb and confirm if that issue is resolved or not. Do not run on production ZFS pools / systems. * autopkgtest pass (from https://ubuntu-archive- team.ubuntu.com/proposed-migration/ ) * adt-matrix pass (from https://kernel.ubuntu.com/adt-matrix/ ) * kernel regression zfs testsuite pass (from Kernel team RT test results summary, private) * zsys integration test pass (upgrade of zsys installed systems for all releases) * zsys install test pass (for daily images of LTS releases only that have such installer support, as per iso tracker test case) * LXD (ping LXD team to upgrade vendored in tooling to 2.2.2 and 2.1.14, and test LXD on these updated kernels) [ Where problems could occur ] * Upgrade to 2.1.14 on jammy with SLS mitigations compatiblity will introduce slight slow down on amd64 (for hw accelerated assembly code-paths only in the encryption primitives) * Uncertain of the perfomance impact of the extra checks in dnat patch fix itself. Possibly affecting speed of operation, at the benefit of correctness. [ Other Info ] * https://github.com/openzfs/zfs/pull/15571 is most current consideration of affairs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2044657/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2045796] Re: Add Support for Broadcom 5760X Network adapters to 24.04 (patches in 6.8)
** Changed in: linux (Ubuntu Noble) Importance: Undecided => Medium -- 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/2045796 Title: Add Support for Broadcom 5760X Network adapters to 24.04 (patches in 6.8) Status in linux package in Ubuntu: New Status in linux source package in Mantic: In Progress Status in linux source package in Noble: New Bug description: These patches are needed on top of v6.7 to support Broadcom 5760X Adapters. These patches currently reside in the net-next tree and will be included in v6.8. Prerequisite commits in net-next today: c1056a59aee1 bnxt_en: Optimize xmit_more TX path ba098017791e bnxt_en: Use existing MSIX vectors for all mqprio TX rings f07b58801bef bnxt_en: Add macros related to TC and TX rings f5b29c6afe36 bnxt_en: Add helper to get the number of CP rings required for TX rings 0589a1ed4d33 bnxt_en: Support up to 8 TX rings per MSIX 877edb347323 bnxt_en: Refactor bnxt_hwrm_set_coal() 5a3c585fa83f bnxt_en: New encoding for the TX opaque field ebf72319cef6 bnxt_en: Refactor bnxt_tx_int() 9c0b06de6fb6 bnxt_en: Remove BNXT_RX_HDL and BNXT_TX_HDL 7845b8dfc713 bnxt_en: Add completion ring pointer in TX and RX ring structures d1eec614100c bnxt_en: Restructure cp_ring_arr in struct bnxt_cp_ring_info 7f0a168b0441 bnxt_en: Add completion ring pointer in TX and RX ring structures 34eec1f29a59 bnxt_en: Put the TX producer information in the TX BD opaque field These 13 patches below were submitted on 11/20/23 and accepted on 11/21/23. These are the initial patches with 5760X contents. 1c7fd6ee2fe4 bnxt_en: Rename some macros for the P5 chips f94471f3ce74 bnxt_en: Modify the NAPI logic for the new P7 chips c09d22674b94 bnxt_en: Modify RX ring indexing logic. 6d1add95536b bnxt_en: Modify TX ring indexing logic. b9e0c47ee2ec bnxt_en: Add db_ring_mask and related macro to bnxt_db_info struct. 236e237f8ffe bnxt_en: Add support for HWRM_FUNC_BACKING_STORE_CFG_V2 firmware calls 6a4d0774f02d bnxt_en: Add support for new backing store query firmware API b098dc5a3357 bnxt_en: Add bnxt_setup_ctxm_pg_tbls() helper function 2ad67aea11f2 bnxt_en: Use the pg_info field in bnxt_ctx_mem_type struct 035c57615982 bnxt_en: Add page info to struct bnxt_ctx_mem_type 76087d997a84 bnxt_en: Restructure context memory data structures e50dc4c2206e bnxt_en: Free bp->ctx inside bnxt_free_ctx_mem() aa8460bacf49 bnxt_en: The caller of bnxt_alloc_ctx_mem() should always free bp->ctx The next 15 patches were submitted on 12/1/23 and accepted on 12/4/23. These are all the basic L2 patches for 5760X including the PCI IDs: 2012a6abc876 bnxt_en: Add 5760X (P7) PCI IDs 047a2d38e40c bnxt_en: Report the new ethtool link modes in the new firmware interface 7b60cf2b641a bnxt_en: Support force speed using the new HWRM fields 30c0bb63c2ea bnxt_en: Support new firmware link parameters cf47fa5ca5bb bnxt_en: Refactor ethtool speeds logic a7445d69809f bnxt_en: Add support for new RX and TPA_START completion types for P7 39b2e62be370 bnxt_en: Refactor and refine bnxt_tpa_start() and bnxt_tpa_end(). c2f8063309da bnxt_en: Refactor RX VLAN acceleration logic. 13d2d3d381ee bnxt_en: Add new P7 hardware interface definitions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045796/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2045698] Re: Lunar update: upstream stable patchset 2023-12-05
** Changed in: linux (Ubuntu Lunar) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2045698 Title: Lunar update: upstream stable patchset 2023-12-05 Status in linux package in Ubuntu: Invalid Status in linux source package in Lunar: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2023-12-05 Ported from the following upstream stable releases: v6.1.55, v6.5.5 from git://git.kernel.org/ autofs: fix memory leak of waitqueues in autofs_catatonic_mode btrfs: output extra debug info if we failed to find an inline backref locks: fix KASAN: use-after-free in trace_event_raw_event_filelock_lock ACPICA: Add AML_NO_OPERAND_RESOLVE flag to Timer kernel/fork: beware of __put_task_struct() calling context rcuscale: Move rcu_scale_writer() schedule_timeout_uninterruptible() to _idle() scftorture: Forgive memory-allocation failure if KASAN ACPI: video: Add backlight=native DMI quirk for Lenovo Ideapad Z470 perf/smmuv3: Enable HiSilicon Erratum 162001900 quirk for HIP08/09 perf/imx_ddr: speed up overflow frequency of cycle hw_breakpoint: fix single-stepping when using bpf_overflow_handler ACPI: x86: s2idle: Catch multiple ACPI_TYPE_PACKAGE objects selftests/nolibc: fix up kernel parameters support devlink: remove reload failed checks in params get/set callbacks crypto: lrw,xts - Replace strlcpy with strscpy ice: Don't tx before switchdev is fully configured wifi: ath9k: fix fortify warnings wifi: ath9k: fix printk specifier wifi: mwifiex: fix fortify warning mt76: mt7921: don't assume adequate headroom for SDIO headers wifi: wil6210: fix fortify warnings can: sun4i_can: Add acceptance register quirk UBUNTU: [Config] updateconfigs for CAN_SUN4I can: sun4i_can: Add support for the Allwinner D1 net: Use sockaddr_storage for getsockopt(SO_PEERNAME). net/ipv4: return the real errno instead of -EINVAL crypto: lib/mpi - avoid null pointer deref in mpi_cmp_ui() Bluetooth: Fix hci_suspend_sync crash netlink: convert nlk->flags to atomic flags tpm_tis: Resend command to recover from data transfer errors mmc: sdhci-esdhc-imx: improve ESDHC_FLAG_ERR010450 alx: fix OOB-read compiler warning wifi: mac80211: check S1G action frame size netfilter: ebtables: fix fortify warnings in size_entry_mwt() wifi: cfg80211: reject auth/assoc to AP with our address wifi: cfg80211: ocb: don't leave if not joined wifi: mac80211: check for station first in client probe wifi: mac80211_hwsim: drop short frames libbpf: Free btf_vmlinux when closing bpf_object drm/bridge: tc358762: Instruct DSI host to generate HSE packets drm/edid: Add quirk for OSVR HDK 2.0 arm64: dts: qcom: sm6125-pdx201: correct ramoops pmsg-size arm64: dts: qcom: sm6350: correct ramoops pmsg-size arm64: dts: qcom: sm8150-kumano: correct ramoops pmsg-size arm64: dts: qcom: sm8250-edo: correct ramoops pmsg-size samples/hw_breakpoint: Fix kernel BUG 'invalid opcode: ' drm/amd/display: Fix underflow issue on 175hz timing ASoC: SOF: topology: simplify code to prevent static analysis warnings ASoC: Intel: sof_sdw: Update BT offload config for soundwire config ALSA: hda: intel-dsp-cfg: add LunarLake support drm/amd/display: Use DTBCLK as refclk instead of DPREFCLK drm/amd/display: Blocking invalid 420 modes on HDMI TMDS for DCN31 drm/amd/display: Blocking invalid 420 modes on HDMI TMDS for DCN314 drm/exynos: fix a possible null-pointer dereference due to data race in exynos_drm_crtc_atomic_disable() drm/mediatek: dp: Change logging to dev for mtk_dp_aux_transfer() bus: ti-sysc: Configure uart quirks for k3 SoC md: raid1: fix potential OOB in raid1_remove_disk() ext2: fix datatype of block number in ext2_xattr_set2() fs/jfs: prevent double-free in dbUnmount() after failed jfs_remount() jfs: fix invalid free of JFS_IP(ipimap)->i_imap in diUnmount PCI: dwc: Provide deinit callback for i.MX ARM: 9317/1: kexec: Make smp stop calls asynchronous powerpc/pseries: fix possible memory leak in ibmebus_bus_init() PCI: vmd: Disable bridge window for domain reset PCI: fu740: Set the number of MSI vectors media: mdp3: Fix resource leaks in of_find_device_by_node media: dvb-usb-v2: af9035: Fix null-ptr-deref in af9035_i2c_master_xfer media: dw2102: Fix null-ptr-deref in dw2102_i2c_tran
[Kernel-packages] [Bug 2045958] Re: Avoid using damage rectangle under hardware rotation mode when PSR is enabled
This bug is awaiting verification that the linux-oem-6.1/6.1.0-1028.28 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-oem-6.1' to 'verification-done- jammy-linux-oem-6.1'. If the problem still exists, change the tag 'verification-needed-jammy-linux-oem-6.1' to 'verification-failed-jammy- linux-oem-6.1'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-oem-6.1-v2 verification-needed-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/2045958 Title: Avoid using damage rectangle under hardware rotation mode when PSR is enabled Status in HWE Next: New Status in linux package in Ubuntu: Confirmed 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: Confirmed 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: Confirmed 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: Confirmed 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] When hardware rotation feature is used by compositor, the clip damage on cursor plane causes screen glitches on AMD platforms with PSR panel. [Fix] Disable clip damage when hardware rotation is used. [Test] With the patch applied, the issue can't be observed when the screen is rotated 180 degree. 90 and 270 degrees are unaffected since no compositor is using hardware rotation for those two angles. [Where problems could occur] The power consumption in theory will higher for 180 degree rotation because now the full screen may need to be redrawn when cursor moves. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2045958/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2046105] Re: Sound: Add rtl quirk of M90-Gen5
This bug is awaiting verification that the linux-oem-6.1/6.1.0-1028.28 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-oem-6.1' to 'verification-done- jammy-linux-oem-6.1'. If the problem still exists, change the tag 'verification-needed-jammy-linux-oem-6.1' to 'verification-failed-jammy- linux-oem-6.1'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-oem-6.1-v2 verification-needed-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/2046105 Title: Sound: Add rtl quirk of M90-Gen5 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: In Progress 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 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 Bug description: [Impact] When plugin the headset jack, only speaker is identified. [Fix] Add ALC897_FIXUP_HEADSET_MIC_PIN quirk to make its headset mic work. [Test] Vendor tested on hardware, headset mic works fine. [Where problems could occur] It may break audio. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2046105/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2046444] Re: Missing tp_smapi dkms module in 6.5-hwe
duplicate of https://bugs.launchpad.net/ubuntu/+source/tp- smapi/+bug/2046450 ** Package changed: linux-signed-hwe-6.5 (Ubuntu) => linux-hwe-6.5 (Ubuntu) ** Package changed: linux-hwe-6.5 (Ubuntu) => tp-smapi (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2046444 Title: Missing tp_smapi dkms module in 6.5-hwe Status in tp-smapi package in Ubuntu: New Bug description: During the 6.5-hwe migration test, I found that there was a missing dkms which is tp_smapi. I just randomly picked some test results for your reference. https://certification.canonical.com/hardware/202106-29206/submission/344990/test/71814/result/37864278/ https://certification.canonical.com/hardware/202005-27944/submission/344995/test/71814/result/37864862/ https://certification.canonical.com/hardware/202008-28111/submission/344988/test/71814/result/37863988/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tp-smapi/+bug/2046444/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2046131] Re: drm/amd: Disable PSR-SU to fix the brightness issue
This bug is awaiting verification that the linux-oem-6.1/6.1.0-1028.28
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy-linux-oem-6.1' to 'verification-done-
jammy-linux-oem-6.1'. If the problem still exists, change the tag
'verification-needed-jammy-linux-oem-6.1' to 'verification-failed-jammy-
linux-oem-6.1'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: kernel-spammed-jammy-linux-oem-6.1-v2
verification-needed-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/2046131
Title:
drm/amd: Disable PSR-SU to fix the brightness issue
Status in HWE Next:
In Progress
Status in linux package in Ubuntu:
New
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
Bug description:
[Impact]
Sometimes the brightness isn't changed on gnome menu.
[Fix]
The TCON is random hung by PSR-SU.
Add a workaround to disable PSR-SU until the real fix.
[Test]
Tested on hardware, the brightness is changed as expected.
[Where problems could occur]
It may break AMD display.
Note: This commit is replaced by commit: cd2e31a9ab93d13c4
("drm/amd/display: Set minimum requirement for using PSR-SU on
Phoenix") in v6.5, but new commit failed to fix the original issue,
disable PSR-SU again by this commit.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2046131/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2045809] Re: Jammy update: v5.15.135 upstream stable release
** Changed in: linux (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 in Ubuntu.
https://bugs.launchpad.net/bugs/2045809
Title:
Jammy update: v5.15.135 upstream stable release
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Fix Committed
Bug description:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
v5.15.135 upstream stable release
from git://git.kernel.org/
spi: zynqmp-gqspi: Convert to platform remove callback returning void
spi: zynqmp-gqspi: fix clock imbalance on probe failure
ASoC: soc-utils: Export snd_soc_dai_is_dummy() symbol
ASoC: tegra: Fix redundant PLLA and PLLA_OUT0 updates
NFS: Cleanup unused rpc_clnt variable
NFS: rename nfs_client_kset to nfs_kset
NFSv4: Fix a state manager thread deadlock regression
ring-buffer: remove obsolete comment for free_buffer_page()
ring-buffer: Fix bytes info in per_cpu buffer stats
arm64: Avoid repeated AA64MMFR1_EL1 register read on pagefault path
iommu/arm-smmu-v3: Set TTL invalidation hint better
iommu/arm-smmu-v3: Avoid constructing invalid range commands
rbd: move rbd_dev_refresh() definition
rbd: decouple header read-in from updating rbd_dev->header
rbd: decouple parent info read-in from updating rbd_dev
rbd: take header_rwsem in rbd_dev_refresh() only when updating
block: fix use-after-free of q->q_usage_counter
scsi: zfcp: Fix a double put in zfcp_port_enqueue()
qed/red_ll2: Fix undefined behavior bug in struct qed_ll2_info
wifi: mwifiex: Fix tlv_buf_left calculation
net: replace calls to sock->ops->connect() with kernel_connect()
net: prevent rewrite of msg_name in sock_sendmsg()
drm/amd: Fix detection of _PR3 on the PCIe root port
arm64: Add Cortex-A520 CPU part definition
HID: sony: Fix a potential memory leak in sony_probe()
ubi: Refuse attaching if mtd's erasesize is 0
wifi: iwlwifi: dbg_ini: fix structure packing
iwlwifi: avoid void pointer arithmetic
wifi: iwlwifi: mvm: Fix a memory corruption issue
wifi: mwifiex: Fix oob check condition in mwifiex_process_rx_packet
bpf: Fix tr dereferencing
drivers/net: process the result of hdlc_open() and add call of hdlc_close()
in uhdlc_close()
wifi: mt76: mt76x02: fix MT76x0 external LNA gain handling
regmap: rbtree: Fix wrong register marked as in-cache when creating new node
ima: Finish deprecation of IMA_TRUSTED_KEYRING Kconfig
UBUNTU: [Config] updateconfigs for IMA_BLACKLIST_KEYRING
scsi: target: core: Fix deadlock due to recursive locking
ima: rework CONFIG_IMA dependency block
NFSv4: Fix a nfs4_state_manager() race
bpf, sockmap: Reject sk_msg egress redirects to non-TCP sockets
modpost: add missing else to the "of" check
net: fix possible store tearing in neigh_periodic_work()
ipv4, ipv6: Fix handling of transhdrlen in __ip{,6}_append_data()
ptp: ocp: Fix error handling in ptp_ocp_device_init
net: dsa: mv88e6xxx: Avoid EEPROM timeout when EEPROM is absent
net: usb: smsc75xx: Fix uninit-value access in __smsc75xx_read_reg
net: nfc: llcp: Add lock when modifying device list
net: ethernet: ti: am65-cpsw: Fix error code in am65_cpsw_nuss_init_tx_chns()
ibmveth: Remove condition to recompute TCP header checksum.
netfilter: handle the connecting collision properly in nf_conntrack_proto_sctp
netfilter: nf_tables: nft_set_rbtree: fix spurious insertion failure
ipv4: Set offload_failed flag in fibmatch results
net: stmmac: dwmac-stm32: fix resume on STM32 MCU
tipc: fix a potential deadlock on &tx->lock
tcp: fix quick-ack counting to count actual ACKs of new data
tcp: fix delayed ACKs for MSS boundary condition
sctp: update transport state when processing a dupcook packet
sctp: update hb timer immediately after users change hb_interval
HID: sony: remove duplicate NULL check before calling usb_free_urb()
HID: intel-ish-hid: ipc: Disable and reenable ACPI GPE bit
dm zoned: free dmz->ddev array in dmz_put_zoned_devices
RDMA/core: Require admin capabilities to set system parameters
of: dynamic: Fix potential memory leak in of_changeset_action()
IB/mlx4: Fix the size of a buffer in add_port_entries()
gpio: aspeed: fix the GPIO number passed to pinctrl_gpio_set_config()
gpio: pxa: disable pinctrl calls for MMP_GPIO
RDMA/cma: Initialize ib_sa_multicast structure to 0 when join
RDMA/cma: Fix truncation compilation warning in make_cma_ports
RDMA/uverbs: Fix typo of sizeof argument
RDMA/s
[Kernel-packages] [Bug 2046197] Re: Lunar update: upstream stable patchset 2023-12-11
** Changed in: linux (Ubuntu Lunar) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2046197 Title: Lunar update: upstream stable patchset 2023-12-11 Status in linux package in Ubuntu: Invalid Status in linux source package in Lunar: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2023-12-11 Ported from the following upstream stable releases: v6.1.56, v6.5.6 v6.1.57, v6.5.7 from git://git.kernel.org/ NFS/pNFS: Report EINVAL errors from connect() to the server SUNRPC: Mark the cred for revalidation if the server rejects it NFSv4.1: use EXCHGID4_FLAG_USE_PNFS_DS for DS server NFSv4.1: fix pnfs MDS=DS session trunking media: v4l: Use correct dependency for camera sensor drivers media: via: Use correct dependency for camera sensor drivers netfs: Only call folio_start_fscache() one time for each folio dm: fix a race condition in retrieve_deps btrfs: improve error message after failure to add delayed dir index item btrfs: remove BUG() after failure to insert delayed dir index item ext4: replace the traditional ternary conditional operator with with max()/min() ext4: move setting of trimmed bit into ext4_try_to_trim_range() ext4: do not let fstrim block system suspend netfilter: nft_set_rbtree: use read spinlock to avoid datapath contention netfilter: nft_set_pipapo: call nft_trans_gc_queue_sync() in catchall GC netfilter: nft_set_pipapo: stop GC iteration if GC transaction allocation fails netfilter: nft_set_hash: try later when GC hits EAGAIN on iteration netfilter: nf_tables: fix memleak when more than 255 elements expired ASoC: meson: spdifin: start hw on dai probe netfilter: nf_tables: disallow element removal on anonymous sets bpf: Avoid deadlock when using queue and stack maps from NMI ASoC: rt5640: Revert "Fix sleep in atomic context" ASoC: rt5640: Fix IRQ not being free-ed for HDA jack detect mode ALSA: hda/realtek: Splitting the UX3402 into two separate models netfilter: conntrack: fix extension size table selftests: tls: swap the TX and RX sockets in some tests net/core: Fix ETH_P_1588 flow dissector ASoC: hdaudio.c: Add missing check for devm_kstrdup ASoC: imx-audmix: Fix return error with devm_clk_get() octeon_ep: fix tx dma unmap len values in SG iavf: do not process adminq tasks when __IAVF_IN_REMOVE_TASK is set ASoC: SOF: core: Only call sof_ops_free() on remove if the probe was successful iavf: add iavf_schedule_aq_request() helper iavf: schedule a request immediately after add/delete vlan i40e: Fix VF VLAN offloading when port VLAN is configured netfilter, bpf: Adjust timeouts of non-confirmed CTs in bpf_ct_insert_entry() ionic: fix 16bit math issue when PAGE_SIZE >= 64KB igc: Fix infinite initialization loop with early XDP redirect scsi: iscsi_tcp: restrict to TCP sockets powerpc/perf/hv-24x7: Update domain value check dccp: fix dccp_v4_err()/dccp_v6_err() again x86/mm, kexec, ima: Use memblock_free_late() from ima_free_kexec_buffer() net: hsr: Properly parse HSRv1 supervisor frames. platform/x86: intel_scu_ipc: Check status after timeout in busy_loop() platform/x86: intel_scu_ipc: Check status upon timeout in ipc_wait_for_interrupt() platform/x86: intel_scu_ipc: Don't override scu in intel_scu_ipc_dev_simple_command() platform/x86: intel_scu_ipc: Fail IPC send if still busy x86/srso: Fix srso_show_state() side effect x86/srso: Fix SBPB enablement for spec_rstack_overflow=off net: hns3: add cmdq check for vf periodic service task net: hns3: fix GRE checksum offload issue net: hns3: only enable unicast promisc when mac table full net: hns3: fix fail to delete tc flower rules during reset issue net: hns3: add 5ms delay before clear firmware reset irq source net: bridge: use DEV_STATS_INC() team: fix null-ptr-deref when team device type is changed net: rds: Fix possible NULL-pointer dereference netfilter: nf_tables: disable toggling dormant table state more than once i915/pmu: Move execlist stats initialization to execlist specific setup locking/seqlock: Do the lockdep annotation before locking in do_write_seqcount_begin_nested() net: ena: Flush XDP packets on error. bnxt_en: Flush XDP for bnxt_poll_nitroa0()'s NAPI octeontx2-pf: Do xdp_do_flush() after redir
[Kernel-packages] [Bug 2046008] Re: Jammy update: v5.15.136 upstream stable release
** Changed in: linux (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 in Ubuntu. https://bugs.launchpad.net/bugs/2046008 Title: Jammy update: v5.15.136 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.15.136 upstream stable release from git://git.kernel.org/ iommu/vt-d: Avoid memory allocation in iommu_suspend() scsi: core: Use a structure member to track the SCSI command submitter scsi: core: Rename scsi_mq_done() into scsi_done() and export it scsi: ib_srp: Call scsi_done() directly RDMA/srp: Do not call scsi_done() from srp_abort() RDMA/cxgb4: Check skb value for failure to allocate perf/arm-cmn: Fix the unhandled overflow status of counter 4 to 7 of: overlay: Reorder struct fragment fields kerneldoc platform/x86: think-lmi: Fix reference leak platform/x86: hp-wmi:: Mark driver struct with __refdata to prevent section mismatch warning lib/test_meminit: fix off-by-one error in test_pages() HID: logitech-hidpp: Fix kernel crash on receiver USB disconnect quota: Fix slow quotaoff net: prevent address rewrite in kernel_bind() ALSA: usb-audio: Fix microphone sound on Opencomm2 Headset KEYS: trusted: allow use of kernel RNG for key material KEYS: trusted: Remove redundant static calls usage drm/msm/dp: do not reinitialize phy unless retry during link training drm/msm/dsi: skip the wait for video mode done if not applicable drm/msm/dsi: fix irq_of_parse_and_map() error checking drm/msm/dpu: change _dpu_plane_calc_bw() to use u64 to avoid overflow ravb: Fix up dma_free_coherent() call in ravb_remove() ravb: Fix use-after-free issue in ravb_tx_timeout_work() ieee802154: ca8210: Fix a potential UAF in ca8210_probe mlxsw: fix mlxsw_sp2_nve_vxlan_learning_set() return type eth: remove copies of the NAPI_POLL_WEIGHT define xen-netback: use default TX queue size for vifs riscv, bpf: Factor out emit_call for kernel and bpf context riscv, bpf: Sign-extend return values drm/vmwgfx: fix typo of sizeof argument bpf: Fix verifier log for async callback return values net: macsec: indicate next pn update when offloading net: phy: mscc: macsec: reject PN update requests ixgbe: fix crash with empty VF macvlan list net/mlx5e: Again mutually exclude RX-FCS and RX-port-timestamp net: nfc: fix races in nfc_llcp_sock_get() and nfc_llcp_sock_get_sn() pinctrl: renesas: rzn1: Enable missing PINMUX nfc: nci: assert requested protocol is valid workqueue: Override implicit ordered attribute in workqueue_apply_unbound_cpumask() net: add sysctl accept_ra_min_rtr_lft net: change accept_ra_min_rtr_lft to affect all RA lifetimes net: release reference to inet6_dev pointer media: mtk-jpeg: Fix use after free bug due to uncanceled work dmaengine: stm32-mdma: abort resume if no ongoing transfer xhci: Keep interrupt disabled in initialization until host is running. usb: xhci: xhci-ring: Use sysdev for mapping bounce buffer net: usb: dm9601: fix uninitialized variable use in dm9601_mdio_read usb: dwc3: Soft reset phy on probe for host usb: cdns3: Modify the return value of cdns_set_active () to void when CONFIG_PM_SLEEP is disabled usb: musb: Get the musb_qh poniter after musb_giveback usb: musb: Modify the "HWVers" register address iio: pressure: bmp280: Fix NULL pointer exception iio: pressure: dps310: Adjust Timeout Settings iio: pressure: ms5611: ms5611_prom_is_valid false negative bug drm/amdgpu: add missing NULL check drm/amd/display: Don't set dpms_off for seamless boot ACPI: resource: Skip IRQ override on ASUS ExpertBook B1402CBA x86/cpu: Fix AMD erratum #1485 on Zen4-based CPUs mcb: remove is_added flag from mcb_device struct thunderbolt: Workaround an IOMMU fault on certain systems with Intel Maple Ridge thunderbolt: Check that lane 1 is in CL0 before enabling lane bonding libceph: use kernel_connect() ceph: fix incorrect revoked caps assert in ceph_fill_file_size() ceph: fix type promotion bug on 32bit systems Input: powermate - fix use-after-free in powermate_config_complete Input: psmouse - fix fast_reconnect function for PS/2 mode Input: xpad - add PXN V900 support Input: i8042 - add Fujitsu Lifebook E5411 to i8042 quirk table Input: goodix - ensure int GPIO is in input for gpio_count == 1 && gpio_i
[Kernel-packages] [Bug 2046466] [NEW] Noble update: v6.6.7 upstream stable release
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
v6.6.7 upstream stable release
from git://git.kernel.org/
Linux 6.6.7
drm/amdgpu: Restrict extended wait to PSP v13.0.6
drm/amdgpu: update retry times for psp BL wait
drm/amdgpu: Fix refclk reporting for SMU v13.0.6
riscv: Kconfig: Add select ARM_AMBA to SOC_STARFIVE
gcc-plugins: randstruct: Update code comment in relayout_struct()
ASoC: qcom: sc8280xp: Limit speaker digital volumes
netfilter: nft_set_pipapo: skip inactive elements during set walk
MIPS: Loongson64: Enable DMA noncoherent support
MIPS: Loongson64: Handle more memory types passed from firmware
MIPS: Loongson64: Reserve vgabios memory on boot
perf metrics: Avoid segv if default metricgroup isn't set
perf list: Fix JSON segfault by setting the used skip_duplicate_pmus callback
KVM: SVM: Update EFER software model on CR0 trap for SEV-ES
KVM: s390/mm: Properly reset no-dat
MIPS: kernel: Clear FPU states when setting up kernel threads
cifs: Fix flushing, invalidation and file size with FICLONE
cifs: Fix flushing, invalidation and file size with copy_file_range()
USB: gadget: core: adjust uevent timing on gadget unbind
powerpc/ftrace: Fix stack teardown in ftrace_no_trace
x86/CPU/AMD: Check vendor in the AMD microcode callback
devcoredump: Send uevent once devcd is ready
serial: 8250_omap: Add earlycon support for the AM654 UART controller
serial: 8250: 8250_omap: Do not start RX DMA on THRI interrupt
serial: 8250: 8250_omap: Clear UART_HAS_RHR_IT_DIS bit
serial: sc16is7xx: address RX timeout interrupt errata
ARM: PL011: Fix DMA support
usb: typec: class: fix typec_altmode_put_partner to put plugs
smb: client: fix potential NULL deref in parse_dfs_referrals()
Revert "xhci: Loosen RPM as default policy to cover for AMD xHC 1.1"
cifs: Fix non-availability of dedup breaking generic/304
parport: Add support for Brainboxes IX/UC/PX parallel cards
serial: ma35d1: Validate console index before assignment
serial: 8250_dw: Add ACPI ID for Granite Rapids-D UART
nvmem: Do not expect fixed layouts to grab a layout driver
usb: gadget: f_hid: fix report descriptor allocation
kprobes: consistent rcu api usage for kretprobe holder
ASoC: ops: add correct range check for limiting volume
gpiolib: sysfs: Fix error handling on failed export
x86/sev: Fix kernel crash due to late update to read-only ghcb_version
perf: Fix perf_event_validate_size()
drm/amdgpu: disable MCBP by default
arm64: dts: mt8183: kukui: Fix underscores in node names
arm64: dts: mediatek: add missing space before {
parisc: Fix asm operand number out of range build error in bug table
parisc: Reduce size of the bug_table on 64-bit kernel by half
LoongArch: BPF: Don't sign extend function return value
LoongArch: BPF: Don't sign extend memory load operand
perf vendor events arm64: AmpereOne: Add missing DefaultMetricgroupName fields
misc: mei: client.c: fix problem of return '-EOVERFLOW' in mei_cl_write
misc: mei: client.c: return negative error code in mei_cl_write
coresight: ultrasoc-smb: Fix uninitialized before use buf_hw_base
coresight: ultrasoc-smb: Config SMB buffer before register sink
coresight: ultrasoc-smb: Fix sleep while close preempt in enable_smb
hwtracing: hisi_ptt: Add dummy callback pmu::read()
coresight: Fix crash when Perf and sysfs modes are used concurrently
coresight: etm4x: Remove bogous __exit annotation for some functions
arm64: dts: mediatek: mt8186: Change gpu speedbin nvmem cell name
arm64: dts: mediatek: mt8186: fix clock names for power domains
arm64: dts: mediatek: mt8183-evb: Fix unit_address_vs_reg warning on ntc
arm64: dts: mediatek: mt8183: Move thermal-zones to the root node
arm64: dts: mediatek: mt8183: Fix unit address for scp reserved memory
arm64: dts: mediatek: mt8195: Fix PM suspend/resume with venc clocks
arm64: dts: mediatek: mt8173-evb: Fix regulator-fixed node names
arm64: dts: mediatek: cherry: Fix interrupt cells for MT6360 on I2C7
arm64: dts: mediatek: mt8183-kukui-jacuzzi: fix dsi unnecessary cells properties
arm64: dts: mediatek: mt7622: fix memory node warning check
arm64: dts: mt7986: fix emmc hs400 mode without uboot initialization
arm64: dts: mt7986: define 3W max power to both SFP on BPI-R3
arm64: dts: mt7986: change cooling trips
drm/i915: Skip some timing checks on BXT/GLK DSI transcoders
drm/i915/mst: Reject modes that require the bigjoiner
drm/i915/mst: Fix .mode_valid_ctx() return values
drm/atomic-helpers: Invoke end_fb_access while owning plane state
md/raid6: use valid sector values to determine if an I/O should wait on the
reshape
powercap: DT
[Kernel-packages] [Bug 2046464] [NEW] Noble update: v6.6.5 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.6.5 upstream stable release from git://git.kernel.org/ Linux 6.6.5 vfio: Drop vfio_file_iommu_group() stub to fudge around a KVM wart x86/xen: fix percpu vcpu_info allocation vfio/pds: Fix possible sleep while in atomic context vfio/pds: Fix mutex lock->magic != lock warning drm/amd/display: Fix MPCC 1DLUT programming drm/amd/display: Simplify brightness initialization drm/amd/display: Reduce default backlight min from 5 nits to 1 nits drm/amd/display: refactor ILR to make it work iommu: Fix printk arg in of_iommu_get_resv_regions() drm/amd/pm: fix a memleak in aldebaran_tables_init cpufreq/amd-pstate: Only print supported EPP values for performance governor cpufreq/amd-pstate: Fix scaling_min_freq and scaling_max_freq update drm/panel: nt36523: fix return value check in nt36523_probe() drm/panel: starry-2081101qfh032011-53g: Fine tune the panel power sequence drm/i915/gsc: Mark internal GSC engine with reserved uabi class iommu/vt-d: Make context clearing consistent with context mapping iommu/vt-d: Disable PCI ATS in legacy passthrough mode iommu/vt-d: Omit devTLB invalidation requests when TES=0 cpufreq: imx6q: Don't disable 792 Mhz OPP unnecessarily drm/amd/display: Remove power sequencing check drm/amd/display: Refactor edp power control s390/cmma: fix handling of swapper_pg_dir and invalid_pg_dir powerpc/pseries/iommu: enable_ddw incorrectly returns direct mapping for SR-IOV device net: ravb: Keep reverse order of operations in ravb_remove() net: ravb: Stop DMA in case of failures on ravb_open() net: ravb: Start TX queues after HW initialization succeeded net: ravb: Make write access to CXR35 first before accessing other EMAC registers net: ravb: Use pm_runtime_resume_and_get() net: ravb: Check return value of reset_control_deassert() ice: Fix VF Reset paths when interface in a failed over aggregate bpf, sockmap: af_unix stream sockets need to hold ref for pair sock ethtool: don't propagate EOPNOTSUPP from dumps ravb: Fix races between ravb_tx_timeout_work() and net related ops r8169: prevent potential deadlock in rtl8169_close efi/unaccepted: Fix off-by-one when checking for overlapping ranges neighbour: Fix __randomize_layout crash in struct neighbour octeontx2-pf: Restore TC ingress police rules when interface is up octeontx2-pf: Fix adding mbox work queue entry when num_vfs > 64 net: stmmac: xgmac: Disable FPE MMC interrupts octeontx2-af: Fix possible buffer overflow selftests/net: mptcp: fix uninitialized variable warnings selftests/net: unix: fix unused variable compiler warning selftests/net: fix a char signedness issue selftests/net: ipsec: fix constant out of range uapi: propagate __struct_group() attributes to the container union bpf: Add missed allocation hint for bpf_mem_cache_alloc_flags() dpaa2-eth: recycle the RX buffer only after all processing done dpaa2-eth: increase the needed headroom to account for alignment net: dsa: mv88e6xxx: fix marvell 6350 probe crash net: dsa: mv88e6xxx: fix marvell 6350 switch probing wifi: mac80211: do not pass AP_VLAN vif pointer to drivers during flush wifi: iwlwifi: mvm: fix an error code in iwl_mvm_mld_add_sta() ipv4: igmp: fix refcnt uaf issue when receiving igmp query packet net: rswitch: Fix missing dev_kfree_skb_any() in error path net: rswitch: Fix return value in rswitch_start_xmit() net: rswitch: Fix type of ret in rswitch_start_xmit() netdevsim: Don't accept device bound programs media: v4l2-subdev: Fix a 64bit bug pinctrl: stm32: fix array read out of bound pinctrl: stm32: Add check for devm_kcalloc wifi: cfg80211: fix CQM for non-range use io_uring/kbuf: recycle freed mapped buffer ring entries io_uring/kbuf: defer release of mapped buffer rings io_uring: enable io_mem_alloc/free to be used in other parts btrfs: fix 64bit compat send ioctl arguments not initializing version member btrfs: free the allocated memory if btrfs_alloc_page_array() fails btrfs: make error messages more clear when getting a chunk map btrfs: send: ensure send_fd is writable btrfs: fix off-by-one when checking chunk map includes logical address btrfs: ref-verify: fix memory leaks in btrfs_ref_tree_mod() btrfs: add dmesg output for first mount and last unmount of a filesystem parisc: Mark altinstructions read-only and 32-bit aligned parisc: Ensure 32-bit alignment on parisc unwind section parisc: Mark jump_table naturally aligned parisc: Drop the HP-UX ENOSYM and EREMOTERELEASE error codes parisc: Mark lock_aligned variables 16-byte aligned on SMP parisc: Use natural CPU a
[Kernel-packages] [Bug 2046463] [NEW] Noble update: v6.6.4 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.6.4 upstream stable release from git://git.kernel.org/ Linux 6.6.4 USB: dwc3: qcom: fix wakeup after probe deferral USB: dwc3: qcom: fix software node leak on probe errors usb: dwc3: set the dma max_seg_size usb: dwc3: Fix default mode initialization USB: dwc2: write HCINT with INTMASK applied usb: typec: tcpm: Skip hard reset when in error recovery usb: typec: tcpm: Fix sink caps op current check USB: serial: option: don't claim interface 4 for ZTE MF290 USB: serial: option: fix FM101R-GL defines USB: serial: option: add Fibocom L7xx modules usb: cdnsp: Fix deadlock issue during using NCM gadget usb: config: fix iteration issue in 'usb_get_bos_descriptor()' USB: xhci-plat: fix legacy PHY double init bcache: fixup lock c->root error bcache: fixup init dirty data errors bcache: prevent potential division by zero error bcache: check return value from btree_node_alloc_replacement() veth: Use tstats per-CPU traffic counters dm-delay: fix a race between delay_presuspend and delay_bio ALSA: hda/realtek: Add quirks for ASUS 2024 Zenbooks ALSA: hda: ASUS UM5302LA: Added quirks for cs35L41/10431A83 on i2c bus cifs: fix leak of iface for primary channel cifs: account for primary channel in the interface list cifs: distribute channels across interfaces based on speed Revert "phy: realtek: usb: Add driver for the Realtek SoC USB 2.0 PHY" Revert "phy: realtek: usb: Add driver for the Realtek SoC USB 3.0 PHY" Revert "usb: phy: add usb phy notify port status API" hv_netvsc: Mark VF as slave before exposing it to user-mode hv_netvsc: Fix race of register_netdevice_notifier and VF register hv_netvsc: fix race of netvsc and VF register_netdevice platform/x86: ideapad-laptop: Set max_brightness before using it platform/x86/amd/pmc: adjust getting DRAM size behavior USB: serial: option: add Luat Air72*U series products usb: misc: onboard-hub: add support for Microchip USB5744 dt-bindings: usb: microchip,usb5744: Add second supply platform/x86: hp-bioscfg: Fix error handling in hp_add_other_attributes() platform/x86: hp-bioscfg: move mutex_lock() down in hp_add_other_attributes() platform/x86: hp-bioscfg: Simplify return check in hp_add_other_attributes() s390/dasd: protect device queue against concurrent access io_uring/fs: consider link->flags when getting path for LINKAT bcache: fixup multi-threaded bch_sectors_dirty_init() wake-up race md: fix bi_status reporting in md_end_clone_io bcache: replace a mistaken IS_ERR() by IS_ERR_OR_NULL() in btree_gc_coalesce() io_uring: fix off-by one bvec index tls: fix NULL deref on tls_sw_splice_eof() with empty record swiotlb-xen: provide the "max_mapping_size" method ACPI: PM: Add acpi_device_fix_up_power_children() function ACPI: resource: Skip IRQ override on ASUS ExpertBook B1402CVA ACPI: processor_idle: use raw_safe_halt() in acpi_idle_play_dead() ACPI: video: Use acpi_device_fix_up_power_children() thunderbolt: Set lane bonding bit only for downstream port drm/ast: Disconnect BMC if physical connector is connected drm/msm/dpu: Add missing safe_lut_tbl in sc8280xp catalog kselftest/arm64: Fix output formatting for za-fork prctl: Disable prctl(PR_SET_MDWE) on parisc mm: add a NO_INHERIT flag to the PR_SET_MDWE prctl lockdep: Fix block chain corruption USB: dwc3: qcom: fix ACPI platform device leak USB: dwc3: qcom: fix resource leaks on probe deferral nvmet: nul-terminate the NQNs passed in the connect command nvme: blank out authentication fabrics options if not configured afs: Fix file locking on R/O volumes to operate in local mode afs: Return ENOENT if no cell DNS record can be found net: ipa: fix one GSI register field width net: axienet: Fix check for partial TX checksum vsock/test: fix SEQPACKET message bounds test i40e: Fix adding unsupported cloud filters amd-xgbe: propagate the correct speed and duplex status amd-xgbe: handle the corner-case during tx completion amd-xgbe: handle corner-case during sfp hotplug net: veth: fix ethtool stats reporting octeontx2-pf: Fix ntuple rule creation to direct packet to VF with higher Rx queue than its PF arm/xen: fix xen_vcpu_info allocation alignment arm64: mm: Fix "rodata=on" when CONFIG_RODATA_FULL_DEFAULT_ENABLED=y s390/ipl: add missing IPL_TYPE_ECKD_DUMP case to ipl_init() net/smc: avoid data corruption caused by decline net: usb: ax88179_178a: fix failed operations during ax88179_reset drm/panel: boe-tv101wum-nl6: Fine tune Himax83102-j02 panel HFP and HBP ipv4: Correct/silence an endian warning in __ip_do_redirect HID: fix HID device
[Kernel-packages] [Bug 2046465] [NEW] Noble update: v6.6.6 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.6.6 upstream stable release from git://git.kernel.org/ Linux 6.6.6 Revert "wifi: cfg80211: fix CQM for non-range use" ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux (Ubuntu Noble) Importance: Undecided Status: Confirmed ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2046465 Title: Noble update: v6.6.6 upstream stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Noble: 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.6.6 upstream stable release from git://git.kernel.org/ Linux 6.6.6 Revert "wifi: cfg80211: fix CQM for non-range use" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2046465/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2045584] Re: Firefox/brave browser causes GPU reset
Can be easily replicated by having vega64 gpu:
- create ubuntu live cd with 23.10.1
- login computer using livecd and select to test ubuntu
- open firefox
- run a few tests using speedtest.net
- open a few other sites and wait a few mins until you are logged out.
--
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/2045584
Title:
Firefox/brave browser causes GPU reset
Status in linux package in Ubuntu:
New
Bug description:
I am using UBUNTU 23.10 with Vega 64 using the latest amdgpu drivers.
This started when I upgraded to 23.10. Was not happening in 22.04 or
23.04.
In Wayland, it always crashes the gnome session and I have to hardware
power off the system. It also sometimes makes a weird pixelated image
on the screen, kind of like static with both firefox and brave
broswers.
In xorg session only firefox seems to crash the session but weirdly it
just "logs me out" to the welcome screen. Brave works fine.
I thought it was a mem issue but I have run memtest twice now with all
tests passing for the whole night. I have also run prime95
successfully on both windows and ubuntu now for 5-6 hours as well just
to stress the system for both CPU and mem and no issues there.
Its fairly reproducible so please let me know how I can help.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-13-generic 6.5.0-13.13
ProcVersionSignature: Ubuntu 6.5.0-13.13-generic 6.5.3
Uname: Linux 6.5.0-13-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: awaahm 6528 F wireplumber
/dev/snd/controlC2: awaahm 6528 F wireplumber
/dev/snd/controlC0: awaahm 6528 F wireplumber
/dev/snd/seq:awaahm 6512 F pipewire
CRDA: N/A
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon Dec 4 20:05:05 2023
InstallationDate: Installed on 2021-03-30 (979 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64
(20210209.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-13-generic
root=UUID=0392d1e9-f9ce-4e11-a853-626267f141ac ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-6.5.0-13-generic N/A
linux-backports-modules-6.5.0-13-generic N/A
linux-firmware20230919.git3672ccab-0ubuntu2.4
SourcePackage: linux
UpgradeStatus: Upgraded to mantic on 2023-11-10 (24 days ago)
dmi.bios.date: 08/10/2023
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 8702
dmi.board.asset.tag: Default string
dmi.board.name: ROG CROSSHAIR VI HERO (WI-FI AC)
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr8702:bd08/10/2023:br5.17:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGCROSSHAIRVIHERO(WI-FIAC):rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: ASUS
modified.conffile..etc.default.apport:
# set this to 0 to disable apport, or to 1 to enable it
# you can temporarily override this with
# sudo service apport start force_start=1
enabled=0
mtime.conffile..etc.default.apport: 2023-07-26T18:11:44.877297
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045584/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2045958] Re: Avoid using damage rectangle under hardware rotation mode when PSR is enabled
** Changed in: linux (Ubuntu Mantic) 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/2045958 Title: Avoid using damage rectangle under hardware rotation mode when PSR is enabled Status in HWE Next: New Status in linux package in Ubuntu: Confirmed 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: Confirmed 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: Fix Committed 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: Confirmed 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] When hardware rotation feature is used by compositor, the clip damage on cursor plane causes screen glitches on AMD platforms with PSR panel. [Fix] Disable clip damage when hardware rotation is used. [Test] With the patch applied, the issue can't be observed when the screen is rotated 180 degree. 90 and 270 degrees are unaffected since no compositor is using hardware rotation for those two angles. [Where problems could occur] The power consumption in theory will higher for 180 degree rotation because now the full screen may need to be redrawn when cursor moves. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2045958/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2045958] Re: Avoid using damage rectangle under hardware rotation mode when PSR is enabled
** Changed in: linux (Ubuntu Lunar) 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/2045958 Title: Avoid using damage rectangle under hardware rotation mode when PSR is enabled Status in HWE Next: New Status in linux package in Ubuntu: Confirmed 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: Fix Committed 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: Fix Committed 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: Confirmed 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] When hardware rotation feature is used by compositor, the clip damage on cursor plane causes screen glitches on AMD platforms with PSR panel. [Fix] Disable clip damage when hardware rotation is used. [Test] With the patch applied, the issue can't be observed when the screen is rotated 180 degree. 90 and 270 degrees are unaffected since no compositor is using hardware rotation for those two angles. [Where problems could occur] The power consumption in theory will higher for 180 degree rotation because now the full screen may need to be redrawn when cursor moves. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2045958/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2000785] Re: package linux-intel-iotg-tools-common 5.15.0-1018.23 failed to install/upgrade: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-tools-common
This is reproduced again when using 5.15.0-1045-intel-iotg or 5.15.0-1046-intel-iotg. sudo apt install linux-tools-intel-iotg -f Reading package lists... Done Building dependency tree... Done Reading state information... Done linux-tools-intel-iotg is already the newest version (5.15.0.1045.45). You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: linux-intel-iotg-tools-5.15.0-1045 : Depends: linux-tools-common but it is not going to be installed E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-iotg in Ubuntu. https://bugs.launchpad.net/bugs/2000785 Title: package linux-intel-iotg-tools-common 5.15.0-1018.23 failed to install/upgrade: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-tools-common 5.15.0-56.62 Status in linux-intel-iotg package in Ubuntu: Confirmed Bug description: Does not let me upgrade with sudo apt upgrade says there is an error even though I have not changed anything in the system files. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-intel-iotg-tools-common 5.15.0-1018.23 ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64 Uname: Linux 5.15.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 AptOrdering: linux-intel-iotg-tools-common:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Dec 30 13:50:37 2022 DpkgTerminalLog: Preparing to unpack .../linux-intel-iotg-tools-common_5.15.0-1021.26_all.deb ... Unpacking linux-intel-iotg-tools-common (5.15.0-1021.26) over (5.15.0-1018.23) ... dpkg: error processing archive /var/cache/apt/archives/linux-intel-iotg-tools-common_5.15.0-1021.26_all.deb (--unpack): trying to overwrite '/usr/bin/acpidbg', which is also in package linux-tools-common 5.15.0-56.62 DuplicateSignature: package:linux-intel-iotg-tools-common:5.15.0-1018.23 Unpacking linux-intel-iotg-tools-common (5.15.0-1021.26) over (5.15.0-1018.23) ... dpkg: error processing archive /var/cache/apt/archives/linux-intel-iotg-tools-common_5.15.0-1021.26_all.deb (--unpack): trying to overwrite '/usr/bin/acpidbg', which is also in package linux-tools-common 5.15.0-56.62 ErrorMessage: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-tools-common 5.15.0-56.62 InstallationDate: Installed on 2022-10-06 (84 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) PackageArchitecture: all 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-intel-iotg Title: package linux-intel-iotg-tools-common 5.15.0-1018.23 failed to install/upgrade: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-tools-common 5.15.0-56.62 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-intel-iotg/+bug/2000785/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2045425] Re: Windows VM slower performance with Passmark vs Ubuntu VM
It appears the CPU boost support on KVM doesn't handle Windows VM, hence the lower numbers on a Windows VM vs a Ubuntu VM. PassMark – Single Threading measurement, the majority of Perf Score are relied on vCPU Clock Speed. Is this a know limitation? -- 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/2045425 Title: Windows VM slower performance with Passmark vs Ubuntu VM Status in linux package in Ubuntu: New Bug description: Summary : A Windows VM(KVM) on 22.04.3 is 10%(SMT off) to 16%(SMT on) slower running Passmark vs a Ubuntu 22.04.3 VM(KVM). The results should be within 1% of each other. System Information : Dell - AMD EPYC 7543 32-Core Processor, 2801 Mhz, 32 Core(s), 32 Logical Processor(s) Zen 3 (Milan) BIOS - 2.12.4 FW (iDRAC Firmware Version7.00.30.00) NUMA Nodes Per Socket 1(default) Memory - 512 GB of DRAM DDR4 OS : Ubuntu 22.04.3 Setup: Install Ubuntu 22.04.3 and then setup 2 VMs one with Win 22 std. and another one with Ubuntu 22.04.3. Install Passmark benchmark on both the VMs and then run the “Single CPU Threaded” benchmark on both the OS with SMT enable and disable mode. Passmark Download link : https://www.passmark.com/products/pt_linux/download.php Linux Setup version: PerformanceTest Linux x86 64-bit 5.4 MB, v11.0 Build 1002, October 19 2023 Microsoft setup version: Download PerformanceTest 11.0 x86 102 MB, Build 1007 For Intel and AMD x86 CPUs Results : *** Bare metal *** Windows 2022 SMT ON: Win22 VM 1% slower SMT OFF: Win22 VM 1% slower SMT Run1Run2Run3Average On2766276827712768.33 OFF 2773276627652768 Ubuntu 22.04 SMT Run1Run2Run3Average On2777277727752776.33 OFF 2798279227922794 KVM SMT ON : Win22 VM 16% slower SMT OFF: Win22 VM 10% slower Host: Ubuntu 22.04 VM: Win server 22 VM - Single CPU Threaded SMT Run1Run2Run3AVERAGE On2356228722892310.67 OFF 2424245925662483 Host Ubuntu 22.04 KVM with Ubuntu 22.04 VM - Single CPU Threaded SMT Run1Run2Run3AVERAGE On2730274127292733.33 OFF 2745274627462745.67 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045425/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834085] Re: Bluetooth touchpad (Apple Magic Trackpad) disconnects every few minutes
Happy to report, my problem solved with Gnome 45.1 & Fedora 39. No disconnect or freeze with apple trackpad. Fedora 39 Silverblue Intel AX200 bluetooth Apple Magic Trackpad V1 (05AC:030E) ``` $ uname -r 6.6.3-200.fc39.x86_64 $ rpm -qa iwlwifi* iwlwifi-dvm-firmware-2023-1.fc39.noarch iwlwifi-mvm-firmware-2023-1.fc39.noarch ``` -- 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/1834085 Title: Bluetooth touchpad (Apple Magic Trackpad) disconnects every few minutes Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I recently got an Apple's Magic Trackpad. I paired it with Ubuntu 18.04.2 LTS and worked out of the box, no special drivers needed. However, I experience frequent disconnections that last a few seconds (5-15 seconds usually), which are quite annoying, as the cursor stops responding during that interval. The trackpad connects by itself after that period. That usually happens every 20-40 minutes. I use the onboard bluetooth device of my laptop. I also have, at the same time, two more bluetooth devices (keyboard and mouse) and they do not experience that issue, just the trackpad. On ocassion I use bluetooth headphones which work just fine. First of all: Using the command "bluetoothctl" I get the following every time I experience a disconnection: [CHG] Device F4:1B:A1:33:F9:8D Connected: no [CHG] Device F4:1B:A1:33:F9:8D Connected: yes Checking "dmesg" I can see more information: (if I am not mistaken, this shows 4 disconnections) [ 1609.070538] magicmouse 0005:05AC:030E.0007: unknown main item tag 0x0 [ 1609.070797] input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0007/input/input23 [ 1609.071460] magicmouse 0005:05AC:030E.0007: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 [ 1676.917377] NET: Registered protocol family 38 [ 1872.815348] magicmouse 0005:05AC:030E.0008: unknown main item tag 0x0 [ 1872.815559] input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0008/input/input24 [ 1872.816248] magicmouse 0005:05AC:030E.0008: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 [ 3101.682671] magicmouse 0005:05AC:030E.0009: unknown main item tag 0x0 [ 3101.683100] input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0009/input/input25 [ 3101.683673] magicmouse 0005:05AC:030E.0009: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 [ 3110.683360] magicmouse 0005:05AC:030E.000A: unknown main item tag 0x0 [ 3110.683929] input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:1024/0005:05AC:030E.000A/input/input26 [ 3110.684487] magicmouse 0005:05AC:030E.000A: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 And this is what journalctl -b shows at the moment of the disconnection/reconnection: de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) config/udev: removing device Apple Wireless Trackpad de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (**) Option "fd" "64" (1,63 m)˜ de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) event16 - Apple Wireless Trackpad: device removed de juny 13 21:37:49 TM1703 gnome-shell[5071]: g_array_unref: assertion 'array' failed de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) UnloadModule: "libinput" de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) systemd-logind: releasing fd for 13:80 de juny 13 21:37:49 TM1703 upowerd[1271]: unhandled action 'unbind' on /sys/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0008 de juny 13 21:37:50 TM1703 kernel: magicmouse 0005:05AC:030E.0009: unknown main item tag 0x0 de juny 13 21:37:50 TM1703 kernel: input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0009/input/input25 de juny 13 21:37:50 TM1703 kernel: magicmouse 0005:05AC:030E.0009: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) config/udev: Adding input device Apple Wireless Trackpad (/dev/input/mouse1) de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) No input driver specified, ignoring this device. de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) This device may have been added with another device file. de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[
[Kernel-packages] [Bug 2043059] Re: Installation errors out when installing in a chroot
Cool, thanks for testing Sam. Apologies for the missing ${SW_IMG}.
And thanks for the 'unshare -U true' suggestion. I gather your point is
that 'unshare -U' will fail in any chroot environment. I'm not an expert
on namespaces but, from what I can tell, that does seem to be true in
all modern kernels as you say. However, 'unshare -U' can fail for other
reasons too - say, if the admin set /proc/sys/user/max_user_namespaces
to 0, or when running a kernel with CONFIG_USER_NS=n. If we assume all
failures mean we are in a chroot, then we risk not configuring kdump in
such environments.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-nvidia in Ubuntu.
https://bugs.launchpad.net/bugs/2043059
Title:
Installation errors out when installing in a chroot
Status in kdump-tools package in Ubuntu:
Triaged
Status in linux-nvidia package in Ubuntu:
Invalid
Bug description:
Processing triggers for linux-image-5.15.0-1040-nvidia (5.15.0-1040.40) ...
/etc/kernel/postinst.d/dkms:
* dkms: running auto installation service for kernel 5.15.0-1040-nvidia
...done.
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-5.15.0-1040-nvidia
cryptsetup: WARNING: Couldn't determine root device
W: Couldn't identify type of root file system for fsck hook
cp: cannot stat '/etc/iscsi/initiatorname.iscsi': No such file or directory
/etc/kernel/postinst.d/kdump-tools:
kdump-tools: Generating /var/lib/kdump/initrd.img-5.15.0-1040-nvidia
mkinitramfs: failed to determine device for /
mkinitramfs: workaround is MODULES=most, check:
grep -r MODULES /var/lib/kdump/initramfs-tools
Error please report bug on initramfs-tools
Include the output of 'mount' and 'cat /proc/mounts'
update-initramfs: failed for /var/lib/kdump/initrd.img-5.15.0-1040-nvidia
with 1.
run-parts: /etc/kernel/postinst.d/kdump-tools exited with return code 1
dpkg: error processing package linux-image-5.15.0-1040-nvidia (--configure):
installed linux-image-5.15.0-1040-nvidia package post-installation script
subprocess returned error exit status 1
Errors were encountered while processing:
linux-image-5.15.0-1040-nvidia
E: Sub-process /usr/bin/dpkg returned an error code (1)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kdump-tools/+bug/2043059/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1970672] Re: makedumpfile falls back to cp with "__vtop4_x86_64: Can't get a valid pmd_pte."
Hi Chris,
You're correct, I'm sorry. My test on comment #23 is the 3rd item you
listed.
Let me work on 1 and 2 and I'll get back here.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1970672
Title:
makedumpfile falls back to cp with "__vtop4_x86_64: Can't get a valid
pmd_pte."
Status in makedumpfile package in Ubuntu:
Fix Released
Status in makedumpfile source package in Focal:
Fix Committed
Bug description:
[Impact]
* On Focal with an HWE (>=5.12) kernel, makedumpfile can sometimes fail with
"__vtop4_x86_64: Can't get a valid pmd_pte."
* makedumpfile falls back to cp for the dump, resulting in extremely
large vmcores. This can impact both collection and analysis due to
lack of space for the resulting vmcore.
* This is fixed in upstream commit present in versions 1.7.0 and 1.7.1:
https://github.com/makedumpfile/makedumpfile/commit/646456862df8926ba10dd7330abf3bf0f887e1b6
commit 646456862df8926ba10dd7330abf3bf0f887e1b6
Author: Kazuhito Hagio
Date: Wed May 26 14:31:26 2021 +0900
[PATCH] Increase SECTION_MAP_LAST_BIT to 5
* Required for kernel 5.12
Kernel commit 1f90a3477df3 ("mm: teach pfn_to_online_page() about
ZONE_DEVICE section collisions") added a section flag
(SECTION_TAINT_ZONE_DEVICE) and causes makedumpfile an error on
some machines like this:
__vtop4_x86_64: Can't get a valid pmd_pte.
readmem: Can't convert a virtual address(e2bdc200) to physical
address.
readmem: type_addr: 0, addr:e2bdc200, size:32768
__exclude_unnecessary_pages: Can't read the buffer of struct page.
create_2nd_bitmap: Can't exclude unnecessary pages.
Increase SECTION_MAP_LAST_BIT to 5 to fix this. The bit had not
been used until the change, so we can just increase the value.
Signed-off-by: Kazuhito Hagio
[Test Plan]
* Confirm that makedumpfile works as expected by triggering a kdump.
* Confirm that the patched makedumpfile works as expected on a system
known to experience the issue.
* Confirm that the patched makedumpfile is able to work with a cp-
generated known affected vmcore to compress it. The unpatched version
fails.
[Where problems could occur]
* This change could adversely affect the collection/compression of
vmcores during a kdump situation resulting in fallback to cp.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1970672/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2046504] [NEW] Fix AMDGPU display on lower resolution modes
Public bug reported: [Impact] AMD GPU display is blank when set lower resolution than native mode on eDP. [Fix] On eDP the invalid modes is set, call mode set for valid modes instead. [Test] Tested on hardware, all the modes shown in gnome menu can be set OK. [Where problems could occur] It may break AMD display. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2046504 Title: Fix AMDGPU display on lower resolution modes Status in linux package in Ubuntu: New Bug description: [Impact] AMD GPU display is blank when set lower resolution than native mode on eDP. [Fix] On eDP the invalid modes is set, call mode set for valid modes instead. [Test] Tested on hardware, all the modes shown in gnome menu can be set OK. [Where problems could occur] It may break AMD display. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2046504/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2046504] Re: Fix AMDGPU display on lower resolution modes
** Tags added: oem-priority originate-from-2045225 sutton ** Tags added: originate-from-2045201 -- 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/2046504 Title: Fix AMDGPU display on lower resolution modes Status in HWE Next: New Status in linux package in Ubuntu: New Bug description: [Impact] AMD GPU display is blank when set lower resolution than native mode on eDP. [Fix] On eDP the invalid modes is set, call mode set for valid modes instead. [Test] Tested on hardware, all the modes shown in gnome menu can be set OK. [Where problems could occur] It may break AMD display. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2046504/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2046504] Re: Fix AMDGPU display on lower resolution modes
** 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: hwe-next Assignee: (unassigned) => AaronMa (mapengyu) ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-oem-6.5 (Ubuntu) Status: New => In Progress ** Changed in: hwe-next Status: New => In Progress ** Description changed: [Impact] AMD GPU display is blank when set lower resolution than native mode on eDP. [Fix] On eDP the invalid modes is set, call mode set for valid modes instead. [Test] Tested on hardware, all the modes shown in gnome menu can be set OK. [Where problems could occur] It may break AMD display. + + This issue is not reproduced on v6.4- kernel versions, so SRU for + oem-6.5 only. ** Description changed: [Impact] AMD GPU display is blank when set lower resolution than native mode on eDP. [Fix] On eDP the invalid modes is set, call mode set for valid modes instead. [Test] Tested on hardware, all the modes shown in gnome menu can be set OK. [Where problems could occur] It may break AMD display. - This issue is not reproduced on v6.4- kernel versions, so SRU for + This issue is not reproduced on v6.2- kernel versions, so SRU for oem-6.5 only. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2046504 Title: Fix AMDGPU display on lower resolution modes Status in HWE Next: In Progress Status in linux package in Ubuntu: New Status in linux-oem-6.5 package in Ubuntu: In Progress Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: In Progress Bug description: [Impact] AMD GPU display is blank when set lower resolution than native mode on eDP. [Fix] On eDP the invalid modes is set, call mode set for valid modes instead. [Test] Tested on hardware, all the modes shown in gnome menu can be set OK. [Where problems could occur] It may break AMD display. This issue is not reproduced on v6.2- kernel versions, so SRU for oem-6.5 only. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2046504/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2046504] Re: Fix AMDGPU display on lower resolution modes
** Description changed: [Impact] AMD GPU display is blank when set lower resolution than native mode on eDP. [Fix] - On eDP the invalid modes is set, call mode set for valid modes instead. + On eDP the invalid modes are set, call mode set for valid modes instead. [Test] Tested on hardware, all the modes shown in gnome menu can be set OK. [Where problems could occur] It may break AMD display. This issue is not reproduced on v6.2- kernel versions, so SRU for oem-6.5 only. ** Changed in: hwe-next Importance: Undecided => High ** Changed in: linux-oem-6.5 (Ubuntu) Importance: Undecided => High ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2046504 Title: Fix AMDGPU display on lower resolution modes Status in HWE Next: In Progress Status in linux package in Ubuntu: New Status in linux-oem-6.5 package in Ubuntu: In Progress Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: In Progress Bug description: [Impact] AMD GPU display is blank when set lower resolution than native mode on eDP. [Fix] On eDP the invalid modes are set, call mode set for valid modes instead. [Test] Tested on hardware, all the modes shown in gnome menu can be set OK. [Where problems could occur] It may break AMD display. This issue is not reproduced on v6.2- kernel versions, so SRU for oem-6.5 only. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2046504/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2046071] Re: Brightness control is inoperative
It doesn't work as well on kernel 6.2.0-39 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2046071 Title: Brightness control is inoperative Status in linux-signed-hwe-6.2 package in Ubuntu: Incomplete Bug description: I can't control the brightness at, be it from the fn buttons or the GUI. The brightness is set to the max level with any way to lower it or control it. This problem doesn't exist in older kernels. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-37-generic 6.2.0-37.38~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Dec 10 17:48:35 2023 InstallationDate: Installed on 2023-12-07 (3 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2046071/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2046116] Re: bluetooth device connected but not recognised as output device
Hi Mark,thanks for your help, I am not technical expert but I don't think it is because of my headset since it is relatively new device and, the other thing is that I was using this Bluetooth devices(headset, sound bar) without any problem but this problem started couple of weeks ago, so my initial thought was it was because of an OS update,so I created this bug report.From my observation I would say , it might be related to pulseaudio, because the first thing I recognized was that pulseaudio was not starting automatically at the start, then when i started it, it recognizes Bluetooth devices but they are not listed in Settings->Sound->Output, so there is no sound output from the headset.I have tried your suggested solution but no change, also tried some solutions suggested on the web. @:~/Desktop/TradeWeb/tradestats$ sudo hcitool info F4:4E:FD:00:5A:65 Requesting information ... BD Address: F4:4E:FD:00:5A:65 OUI Company: Actions Semiconductor Co.,Ltd.(Cayman Islands) (F4-4E-FD) Device Name: Srhythm NC25 LMP Version: 5.0 (0x9) LMP Subversion: 0x201 Manufacturer: Actions (Zhuhai) Technology Co., Limited (992) Features page 0: 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2046116 Title: bluetooth device connected but not recognised as output device Status in bluez package in Ubuntu: New Bug description: bluetooth device connected but not recognised as output device ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1.1 ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Dec 11 15:28:00 2023 InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 81EK ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-37-generic root=UUID=6f698382-a806-46af-9a4b-472e96795c6f ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/02/2018 dmi.bios.release: 1.28 dmi.bios.vendor: LENOVO dmi.bios.version: 7QCN28WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 530-14IKB dmi.ec.firmware.release: 1.28 dmi.modalias: dmi:bvnLENOVO:bvr7QCN28WW:bd08/02/2018:br1.28:efr1.28:svnLENOVO:pn81EK:pvrLenovoYOGA530-14IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA530-14IKB:skuLENOVO_MT_81EK_BU_idea_FM_YOGA530-14IKB: dmi.product.family: YOGA 530-14IKB dmi.product.name: 81EK dmi.product.sku: LENOVO_MT_81EK_BU_idea_FM_YOGA 530-14IKB dmi.product.version: Lenovo YOGA 530-14IKB dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: 0C:54:15:91:FA:4F ACL MTU: 1021:5 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:83770 acl:295 sco:0 events:4208 errors:0 TX bytes:879445 acl:1667 sco:0 commands:1184 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2046116/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2033452] Re: Enable D3cold at s2idle for Intel DG2 GPU
** Changed in: hwe-next Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2033452 Title: Enable D3cold at s2idle for Intel DG2 GPU Status in HWE Next: Fix Released Status in linux 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.1 source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Released Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: Invalid Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: [Impact] The system wakes up during s2idle with Intel DG2 GPU. It causes high power consumption during suspend. [Fix] Enable D3cold at s2idle. [Test] Tested on hardware, the system sleeps as long as expected, the power consumption is lower. [Where problems could occur] It may break i915 driver. It's a fix of regression in v6.1, no need for jammy and already in 6.5. SRU for lunar and oem-6.1. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2033452/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2020627] Re: upgrade iwlwifi firmware of FW API 72 for WiFi 6E support in Malaysia and Morocco
** 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-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2020627
Title:
upgrade iwlwifi firmware of FW API 72 for WiFi 6E support in Malaysia
and Morocco
Status in HWE Next:
Fix Released
Status in linux-firmware package in Ubuntu:
Invalid
Status in linux-firmware source package in Jammy:
Fix Released
Bug description:
[SRU Justification]
[Impact]
iwlwifi takes firmware updates to support WiFi 6E in Malaysia and
Morocco. The models in concern are AX210 (iwlwifi-ty-a0-gf-a0-*),
AX211 (iwlwifi-so-a0-gf-a0-*) and AX411 (iwlwifi-so-a0-gf4-a0-*).
[Fix]
pnvm along with the ucode firmware from upstream commit 5bc279fb161d
("iwlwifi: update core69 and core72 firmwares for So device") are
required. While the pnvm and ucode blobs may not be upgraded
simultaneously in one single commit, those involved in the upgrade
path are also pulled.
[Test Case]
Use `iw` to enumerate supported WiFi 6E band:
$ iw reg get
global
country : DFS-FCC
...
(5925 - 7125 @ 320), (N/A, 12), (N/A), NO-OUTDOOR, PASSIVE-SCAN
[Where problems could occur]
Currently linux-5.15 has FW API 66, linux-hwe-5.19 or above has 72,
linux-6.3 has 74, and linux-unstable (v6.4) or above has 78, so this
will update iwlwifi firmware usage for kernels <= 6.2 in Jammy, e.g.
linux-oem-6.1, linux-5.15.
[Other Info]
Blobs with FW APIs >= 72 do no harm to jammy kernels, but will be
referenced in oem-6.5 if planned.
These commits have been included in linux-firmware/lunar, so only
Jammy is nominated for fix.
== original bug report ==
AX210:
-72 ucode:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/iwlwifi-ty-a0-gf-a0-72.ucode?id=4309412c0d872897dc913c7d2797bb5ce05893ad
pnvm:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=20d9516de4cdc041e2aa83009e5b0464b1c3ed81
AX211:
-72 ucode:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/iwlwifi-so-a0-gf-a0-72.ucode?id=5bc279fb161d529baaf8e837d900235fbbe9bf2f
pnvm:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=20d9516de4cdc041e2aa83009e5b0464b1c3ed81
AX411:
-72 ucode:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/iwlwifi-so-a0-gf4-a0-72.ucode?id=5bc279fb161d529baaf8e837d900235fbbe9bf2f
pnvm:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/iwlwifi-so-a0-gf4-a0.pnvm?id=78a8782a9e51e502a6ed267d270c6925fb738805
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2020627/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2025672] Re: Support Realtek RTL8852CE WiFi 6E/BT Combo
** 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.5 in Ubuntu. https://bugs.launchpad.net/bugs/2025672 Title: Support Realtek RTL8852CE WiFi 6E/BT Combo Status in HWE Next: Fix Released 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: Invalid 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 Lunar: Invalid Status in linux-firmware source package in Lunar: Invalid Status in linux-oem-6.5 source package in Lunar: Invalid Status in linux source package in Mantic: Fix Released Status in linux-firmware source package in Mantic: Fix Released Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [SRU Justification] BugLink: https://bugs.launchpad.net/bugs/2025672 [Impact] Realtek RTL8852CE WiFi 6E/BT Combo takes new firmware to enable 6E features. [Fix] * Bluetooth - kernel + 8b1d66b50437 Bluetooth: btrtl: Add support for RTL8852C (v5.19-rc1) + 9a24ce5e29b1 Bluetooth: btrtl: Firmware format v2 support (v6.4-rc1) + bd003fb338af Bluetooth: btrtl: Load FW v2 otherwise FW v1 for RTL8852C (linux-next) - firmware + 8a2d81176 rtl_bt: Add firmware and config files for RTL8852C (jammy) + d3c922805 rtl_bt: Update RTL8852C BT USB firmware to 0xDFB8_5A33 (jammy) + cfbd66816 rtl_bt: Update RTL8852C BT USB firmware to 0xD5B8_A40A (jammy) + c51488ffb rtl_bt: Update RTL8852C BT USB firmware to 0xD7B8_FABF (lunar) + 55e744853 rtl_bt: Update RTL8852C BT USB firmware to 0x040D_7225 (mantic, change binary format) + 7ed62638b Revert "rtl_bt: Update RTL8852C BT USB firmware to 0x040D_7225" (mantic) + 42d31f8f6 rtl_bt: Add firmware v2 file for RTL8852C (mantic) * WiFi - kernel + 59b4cc439f18 wifi: rtw89: debug: Fix error handling in rtw89_debug_priv_btc_manual_set() (linux-next) - firmware + d2aac63b8 rtw89: 8852c: update fw to v0.27.56.1 (jammy) + 9e91f0ce6 rtw89: 8852c: update fw to v0.27.56.8 (lunar) + c9c19583f rtw89: 8852c: update fw to v0.27.56.9 (lunar) + fc5a25fa0 rtw89: 8852c: update fw to v0.27.56.10 (lunar) + b9c8e9f70 rtw89: 8852c: update fw to v0.27.56.13 (mantic) [Test Case] Basic bluetooth, wifi operations. This is verified with all related kernel/series combinations: * linux-hwe5.19/jammy * linux-hwe-6.2/jammy * linux-oem-6.0/jammy * linux-oem-6.1/jammy * linux-oem-6.5/jammy * ilnux/mantic [Where problems could occur] New device firmware blob, even blob format changes. Expect bugs, power consumption issues, etc. [Other Info] Bluetooth V2 firmware support was first landed to v6.4, and the binary rename in linux-next now. To preserve consistency, Unstable, Mantic and OEM-6.5 kernels are nominated for fix. As for linux-firmware, the only target is Jammy. == original bug description == Support Realtek RTL8852CE WiFi 6E/BT Combo * Bluetooth - kernel + 8b1d66b50437 Bluetooth: btrtl: Add support for RTL8852C (v5.19-rc1) + 9a24ce5e29b1 Bluetooth: btrtl: Firmware format v2 support (v6.4-rc1) + bd003fb338af Bluetooth: btrtl: Load FW v2 otherwise FW v1 for RTL8852C (linux-next) - firmware + 8a2d81176 rtl_bt: Add firmware and config files for RTL8852C (jammy) + d3c922805 rtl_bt: Update RTL8852C BT USB firmware to 0xDFB8_5A33 (jammy) + cfbd66816 rtl_bt: Update RTL8852C BT USB firmware to 0xD5B8_A40A (jammy) + c51488ffb rtl_bt: Update RTL8852C BT USB firmware to 0xD7B8_FABF (lunar) + 55e744853 rtl_bt: Update RTL8852C BT USB firmware to 0x040D_7225 (mantic, change binary format) + 7ed62638b Revert "rtl_bt: Update RTL8852C BT USB firmware to 0x040D_7225" (mantic) + 42d31f8f6 rtl_bt: Add firmware v2 file for RTL8852C (mantic) * WiFi - kernel + 59b4cc439f18 wifi: rtw89: debug: Fix error handling in rtw89_debug_priv_btc_manual_set() (linux-next) - firmware + d2aac63b8 rtw89: 8852c: update fw to v0.27.56.1 (jammy) + 9e91f0ce6 rtw89: 8852c: update fw to v0.27.56.8 (lunar) + c9c19583f rtw89: 8852c: update fw to v0.27.56.9 (lunar) + fc5a25fa0 rtw89: 8852c: update fw to v0.27.56.10 (lunar) + b9c8e9f70 rtw89: 8852c: update fw to v0.27.56.13 (mantic) To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2025672/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2023307] Re: System hang at reading amdgpu sysfs attribute psp_vbflash
The fix has been upstreamed in v6.5-rc1 as commit 3537d6a48c50
("drm/amd: Make sure image is written to trigger VBIOS image update
flow"). It follows the only thing left behind is linux/lunar, which is
affected by commit 8424f2ccb3c0 ("drm/amdgpu/psp: Add vbflash sysfs
interface support") and neither stable linux-6.2.y and Ubuntu lunar
master-next doesn't have the fix yet.
** Changed in: linux-oem-6.1 (Ubuntu Mantic)
Status: Confirmed => Invalid
** Changed in: linux-oem-6.1 (Ubuntu)
Status: Confirmed => Invalid
** Changed in: linux (Ubuntu Mantic)
Status: In Progress => Fix Released
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Released
** Changed in: linux (Ubuntu)
Assignee: You-Sheng Yang (vicamo) => (unassigned)
--
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/2023307
Title:
System hang at reading amdgpu sysfs attribute psp_vbflash
Status in HWE Next:
New
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:
Fix Released
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:
In Progress
Status in linux-oem-6.0 source package in Lunar:
Invalid
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.0 source package in Mantic:
Invalid
Status in linux-oem-6.1 source package in Mantic:
Invalid
Bug description:
[Summary]
1. System hang on starting checkbox test.
2. Hang on collecting device information during start Auto and Stress test.
3. This issue exist on GPU with W7500 & W7600.
[Steps to reproduce]
1. Boot into OS
2. Start Auto test or Stress test(checkbox-cli run
com.canonical.certification::sysfs_attachment)
AMD proposed fix in
https://lore.kernel.org/amd-gfx/20230607065259.48516-1-mario.limoncie...@amd.com/T/#mc5c38f31129f23e498d669734cafe96474a8f8ba
.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.4
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: u 1442 F pulseaudio
/dev/snd/controlC0: u 1442 F pulseaudio
CasperMD5CheckResult: pass
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-jammy-amd64-20220504-33+jellyfish-tynamo+X81
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2023-05-16 (23 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" -
somerville-jammy-amd64-20220504-33
IwConfig:
lono wireless extensions.
enp5s0f0 no wireless extensions.
enp4s0no wireless extensions.
MachineType: Dell Inc. Precision 7875 Tower
Package: linux (not installed)
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.1.0-1014-oem
root=UUID=e9463c30-0a89-4838-a9fa-3296791ccd2a ro log_buf_len=64M quiet splash
vt.handoff=7
ProcVersionSignature: Ubuntu 6.1.0-1014.14-oem 6.1.29
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.1.0-1014-oem N/A
linux-backports-modules-6.1.0-1014-oem N/A
linux-firmware 20220329.git681281e4-0ubuntu3.13
RfKill:
Tags: jammy
Uname: Linux 6.1.0-1014-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: 05/10/2023
dmi.bios.release: 0.4
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 0.4.28
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.ec.firmware.release: 0.18
dmi.modalias:
dmi:bvnDellInc.:bvr0.4.28:bd05/10/2023:br0.4:efr0.18:svnDellInc.:pnPrecision7875Tower:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct3:cvr:sku0C61:
dmi.product.family: Precision
dmi.product.name: Precision 7875 Tower
dmi.product.sku: 0C61
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2023307/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2046502] [NEW] Ubuntu 23.10 hangs when waking up
You have been subscribed to a public bug: Hangs when waking up. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- Ubuntu 23.10 hangs when waking up https://bugs.launchpad.net/bugs/2046502 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2023307] Re: System hang at reading amdgpu sysfs attribute psp_vbflash
** Changed in: linux (Ubuntu Lunar) Status: In Progress => Fix Released ** 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/2023307 Title: System hang at reading amdgpu sysfs attribute psp_vbflash 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: Fix Released 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 Status in linux source package in Mantic: Fix Released Status in linux-oem-6.0 source package in Mantic: Invalid Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: [Summary] 1. System hang on starting checkbox test. 2. Hang on collecting device information during start Auto and Stress test. 3. This issue exist on GPU with W7500 & W7600. [Steps to reproduce] 1. Boot into OS 2. Start Auto test or Stress test(checkbox-cli run com.canonical.certification::sysfs_attachment) AMD proposed fix in https://lore.kernel.org/amd-gfx/20230607065259.48516-1-mario.limoncie...@amd.com/T/#mc5c38f31129f23e498d669734cafe96474a8f8ba . --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: u 1442 F pulseaudio /dev/snd/controlC0: u 1442 F pulseaudio CasperMD5CheckResult: pass DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-jammy-amd64-20220504-33+jellyfish-tynamo+X81 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-05-16 (23 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - somerville-jammy-amd64-20220504-33 IwConfig: lono wireless extensions. enp5s0f0 no wireless extensions. enp4s0no wireless extensions. MachineType: Dell Inc. Precision 7875 Tower Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.1.0-1014-oem root=UUID=e9463c30-0a89-4838-a9fa-3296791ccd2a ro log_buf_len=64M quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.1.0-1014.14-oem 6.1.29 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.1.0-1014-oem N/A linux-backports-modules-6.1.0-1014-oem N/A linux-firmware 20220329.git681281e4-0ubuntu3.13 RfKill: Tags: jammy Uname: Linux 6.1.0-1014-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: 05/10/2023 dmi.bios.release: 0.4 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.4.28 dmi.board.vendor: Dell Inc. dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 0.18 dmi.modalias: dmi:bvnDellInc.:bvr0.4.28:bd05/10/2023:br0.4:efr0.18:svnDellInc.:pnPrecision7875Tower:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct3:cvr:sku0C61: dmi.product.family: Precision dmi.product.name: Precision 7875 Tower dmi.product.sku: 0C61 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2023307/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2019072] Re: 600+ duplicate or duplicated firmware files exist.
** Changed in: linux-firmware (Ubuntu Lunar) Status: Triaged => Won't Fix ** Changed in: linux-firmware (Ubuntu Bionic) Status: Triaged => Won't Fix -- 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/2019072 Title: 600+ duplicate or duplicated firmware files exist. Status in Linux Firmware: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Bionic: Won't Fix Status in linux-firmware source package in Focal: Triaged Status in linux-firmware source package in Jammy: Triaged Status in linux-firmware source package in Lunar: Won't Fix Status in linux-firmware source package in Mantic: Fix Released Bug description: Over 600 duplicate or duplicated firmware files exist. Less than two years ago it was 650~MB on disk. Three years ago it was 500~MB. Today it hovers around 900MB To manage notifications about this bug go to: https://bugs.launchpad.net/linux-firmware/+bug/2019072/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2017877] Re: Intel Wireless 7260 - bluetooth drops from USB bus almost immediately after connecting a device on the lastest firmware
** Changed in: linux-firmware (Ubuntu) Status: Incomplete => Triaged -- 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/2017877 Title: Intel Wireless 7260 - bluetooth drops from USB bus almost immediately after connecting a device on the lastest firmware Status in linux-firmware package in Ubuntu: Triaged Bug description: The bluetooth in my Intel Wireless 7260 on my Thinkpad W541 resets almost immediately after a device connects. This is seen in dmesg as the device disconnecting and reconnecting to the USB bus with no other error messages, like this: [603851.305788] Bluetooth: hci0: Legacy ROM 2.5 revision 8.0 build 1 week 45 2013 [603851.305827] Bluetooth: hci0: Intel Bluetooth firmware file: intel/ibt-hw-37.7.10-fw-1.80.1.2d.d.bseq [603851.443776] Bluetooth: hci0: unexpected event for opcode 0xfc2f [603851.460922] Bluetooth: hci0: Intel BT fw patch 0x2a completed & activated [603871.948430] usb 3-11: USB disconnect, device number 36 [603872.273696] usb 3-11: new full-speed USB device number 37 using xhci_hcd [603872.422912] usb 3-11: New USB device found, idVendor=8087, idProduct=07dc, bcdDevice= 0.01 [603872.422916] usb 3-11: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [603872.437854] Bluetooth: hci0: Legacy ROM 2.5 revision 8.0 build 1 week 45 2013 [603872.437873] Bluetooth: hci0: Intel device is already patched. patch num: 2a [603894.932755] input: JBL TUNE700BT (AVRCP) as /devices/virtual/input/input113 [603898.742664] usb 3-11: USB disconnect, device number 37 [603899.057916] usb 3-11: new full-speed USB device number 38 using xhci_hcd [603899.211235] usb 3-11: New USB device found, idVendor=8087, idProduct=07dc, bcdDevice= 0.01 [603899.211241] usb 3-11: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [603899.226972] Bluetooth: hci0: Legacy ROM 2.5 revision 8.0 build 1 week 45 2013 [603899.226988] Bluetooth: hci0: Intel device is already patched. patch num: 2a [603909.785396] input: JBL TUNE700BT (AVRCP) as /devices/virtual/input/input114 [603914.565733] usb 3-11: USB disconnect, device number 38 [603916.905954] usb 3-11: new full-speed USB device number 39 using xhci_hcd [603917.055128] usb 3-11: New USB device found, idVendor=8087, idProduct=07dc, bcdDevice= 0.01 [603917.055147] usb 3-11: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [603917.071869] Bluetooth: hci0: Legacy ROM 2.5 revision 8.0 build 1 week 45 2013 [603917.071877] Bluetooth: hci0: Intel device is already patched. patch num: 2a This has been a problem ever since I got this laptop, but recently I managed to fix it by downgrading the ibt firmware. I downgraded the /lib/firmware/intel/ibt-hw-37.7.10-fw-1.80.1.2d.d.bseq file to this version https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/commit/intel/ibt- hw-37.7.10-fw-1.80.1.2d.d.bseq?id=fb328183532ffc7a1a54e84fb53467e275a95b79 and after that all problems stopped. System info: $ lsb_release -rd Description: Ubuntu 22.04.2 LTS Release: 22.04 $ apt-cache policy linux-firmware linux-firmware: Installed: 20220329.git681281e4-0ubuntu3.12 Candidate: 20220329.git681281e4-0ubuntu3.12 Version table: *** 20220329.git681281e4-0ubuntu3.12 500 500 http://pl.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://pl.archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main i386 Packages 100 /var/lib/dpkg/status 20220329.git681281e4-0ubuntu1 500 500 http://pl.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 500 http://pl.archive.ubuntu.com/ubuntu jammy/main i386 Packages $ lspci - (see attachment) $ lsusb -v (see attachment) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: krzys_h1511 F pulseaudio /dev/snd/controlC2: krzys_h1511 F pulseaudio /dev/snd/controlC0: krzys_h1511 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: GNOME Dependencies: firmware-sof-signed 2.0-1ubuntu4.1 DistroRelease: Ubuntu 22.04 EcryptfsInUse: Yes InstallationDate: Installed on 2014-02-28 (3346 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: LENOVO 20EGS2G300 Package: linux-firmware 20220329.git681281e4-0ubuntu3.12 [modified: lib/firmware/intel/ibt-hw-37.7.10-fw-1.80.1.2d.d.bseq] PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-71-generic root=UUID=4270eaa2-2664-4fb3-9d5f-f2432845
[Kernel-packages] [Bug 2046502] Re: Ubuntu 23.10 hangs when waking up
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Please also ensure that you include the release and flavour of Ubuntu that you are using. You've not said if your machine is Ubuntu 23.10 Server, Ubuntu 23.10 Desktop, or provided few specifics (is this a new install; did behavior change recently after upgrade; or because of change made by user of the machine) Thank you! Bug reporting is about finding & fixing problems thus preventing future users from hitting the same bug. A Support site would be more appropriate, eg. https://answers.launchpad.net/ubuntu. You can also find help with your problem in the support forum of your local Ubuntu community http://loco.ubuntu.com/ or asking at https://askubuntu.com or https://ubuntuforums.org, or for more support options please look at https://discourse.ubuntu.com/t/community-support/709 ** Package changed: 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/2046502 Title: Ubuntu 23.10 hangs when waking up Status in linux package in Ubuntu: New Bug description: Hangs when waking up. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2046502/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2046525] [NEW] Ubuntu-hwe-6.5-6.5.0-14.14_22.04.1 boot fail due to volume group not found
Public bug reported: CPU: INTEL(R) XEON(R) PLATINUM 8592+ * 2 Memory: Micron MTC10F1084S1RC56BG1 16G * 8 PSU: CFF V4 GREA 1100 *2 original kernel: 6.2.0-39 ubuntu 22.04.03 upgrade kernel: Ubuntu-hwe-6.5-6.5.0-14.14_22.04.1 reproduce step: 1.enable vmd and wait os 6.2.0-39 kernel up 2.upgrade kerenl use "apt install linux-image-6.5.0-14" 3.after upgrading, reboot Than occur the issue: volume group "ubuntu-vg" not found Cannot process volume group ubuntu-vg Note:we use Ubuntu-hwe-6.5-6.5.0-14.14_22.04.1 to verify ubantu"MD:md:124 stopped" issue which occured on ubuntu 22.04.03. But after upgrading, we found this new issue. you can check detail on attachment. ** Affects: linux-hwe (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe in Ubuntu. https://bugs.launchpad.net/bugs/2046525 Title: Ubuntu-hwe-6.5-6.5.0-14.14_22.04.1 boot fail due to volume group not found Status in linux-hwe package in Ubuntu: New Bug description: CPU: INTEL(R) XEON(R) PLATINUM 8592+ * 2 Memory: Micron MTC10F1084S1RC56BG1 16G * 8 PSU: CFF V4 GREA 1100 *2 original kernel: 6.2.0-39 ubuntu 22.04.03 upgrade kernel: Ubuntu-hwe-6.5-6.5.0-14.14_22.04.1 reproduce step: 1.enable vmd and wait os 6.2.0-39 kernel up 2.upgrade kerenl use "apt install linux-image-6.5.0-14" 3.after upgrading, reboot Than occur the issue: volume group "ubuntu-vg" not found Cannot process volume group ubuntu-vg Note:we use Ubuntu-hwe-6.5-6.5.0-14.14_22.04.1 to verify ubantu"MD:md:124 stopped" issue which occured on ubuntu 22.04.03. But after upgrading, we found this new issue. you can check detail on attachment. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/2046525/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
