[Kernel-packages] [Bug 2045233] Re: [SRU][22.04.04]: mpi3mr driver update
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 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 2045233] Re: [SRU][22.04.04]: mpi3mr driver update
** Description changed: [Impact] - This BZ has been initiated to incorporate the mpi3mr driver from + 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. + 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 -- 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:
[Kernel-packages] [Bug 2045233] Re: [SRU][22.04.04]: mpi3mr driver update
** Description changed: - This BZ has been initiated to incorporate the mpi3mr driver from upstream into the upcoming Ubuntu - releases (Ubuntu 22.04.x point releases). Below are the commit IDs for the latest upstream version (v6.8). + [Impact] + + This BZ 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. + 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 - f762326b2baa scsi: mpi3mr: Propagate sense data for admin queue SCSI I/O - 144679dfb584 scsi: mpi3mr: Fix the type used for pointers to bitmap - 2a954832015d scsi: mpi3mr: Use -ENOMEM instead of -1 in mpi3mr_expander_add() - 2acc635a0e5e scsi: mpi3mr: Use IRQ save variants of spinlock to protect chain frame allocation - a3d27dfdcfc2 scsi: mpi3mr: Handle soft reset in progress fault code (0xF002) - b85f82f3c92a scsi: mpi3mr: Declare SCSI host template const - 1ea41edd88f2 scsi: mpi3mr: Update driver version to 8.4.1.0.0 - e74f2fbd8b06 scsi: mpi3mr: Update copyright year - 80b8fd0231d5 scsi: mpi3mr: Fix W=1 compilation warnings - e5f596bc2592 scsi: mpi3mr: Update MPI Headers to revision 27 - f1dec6b1e25e scsi: mpi3mr: Avoid escalating to higher level reset when target is removed - 22beef38e52c scsi: mpi3mr: Modify MUR timeout value to 120 seconds - 23b3d1cf1572 scsi: mpi3mr: Fix admin queue memory leak upon soft reset - 3f1254ed01d0 scsi: mpi3mr: Successive VD delete and add causes FW fault - ce756daa36e1 scsi: mpi3mr: Fix expander node leak in mpi3mr_remove() - c798304470ca scsi: mpi3mr: Fix memory leaks in mpi3mr_init_ioc() - d4caa1a4255c scsi: mpi3mr: Fix sas_hba.phy memory leak in mpi3mr_remove() - d0f3c3728da8 scsi: mpi3mr: Fix mpi3mr_hba_port memory leak in mpi3mr_remove() - 7d2b02172b6a scsi: mpi3mr: Fix config page DMA memory leak - f305a7b6ca21 scsi: mpi3mr: Fix throttle_groups memory leak - 8e45183978d6 scsi: mpi3mr: Bad drive in topology results kernel crash - 4f297e856a7b scsi: mpi3mr: NVMe command size greater than 8K fails - ba8a9ba41fbd scsi: mpi3mr: Return proper values for failures in firmware init path - 0a319f162949 scsi: mpi3mr: Wait for diagnostic save during controller init - 5b06a7169c59 scsi: mpi3mr: Driver unload crashes host when enhanced logging is enabled - 02ca7da2919a scsi: mpi3mr: ioctl timeout when disabling/enabling interrupt - 66b381d874fa scsi: mpi3mr: Remove unneeded version.h include - e39ea831ebad scsi: mpi3mr: Fix missing mrioc->evtack_cmds initialization - 339e61565f81 scsi: mpi3mr: Use number of bits to manage bitmap sizes - eeb270aee3e0 scsi: mpi3mr: Remove unnecessary memcpy() to alltgt_info->dmi - fb428a2005fc scsi: mpi3mr: Fix issues in mpi3mr_get_all_tgt_info() - ae7d45f5283d scsi:
[Kernel-packages] [Bug 2045233] Re: [SRU][22.04.04]: mpi3mr driver update
These patches are all in Ubuntu from 5.19 to 6.5. I've moved them to this comment and out of the original summary to tidy that up. These are in log order. f762326b2baa scsi: mpi3mr: Propagate sense data for admin queue SCSI I/O 144679dfb584 scsi: mpi3mr: Fix the type used for pointers to bitmap 2a954832015d scsi: mpi3mr: Use -ENOMEM instead of -1 in mpi3mr_expander_add() 2acc635a0e5e scsi: mpi3mr: Use IRQ save variants of spinlock to protect chain frame allocation a3d27dfdcfc2 scsi: mpi3mr: Handle soft reset in progress fault code (0xF002) b85f82f3c92a scsi: mpi3mr: Declare SCSI host template const 1ea41edd88f2 scsi: mpi3mr: Update driver version to 8.4.1.0.0 e74f2fbd8b06 scsi: mpi3mr: Update copyright year 80b8fd0231d5 scsi: mpi3mr: Fix W=1 compilation warnings e5f596bc2592 scsi: mpi3mr: Update MPI Headers to revision 27 f1dec6b1e25e scsi: mpi3mr: Avoid escalating to higher level reset when target is removed 22beef38e52c scsi: mpi3mr: Modify MUR timeout value to 120 seconds 23b3d1cf1572 scsi: mpi3mr: Fix admin queue memory leak upon soft reset 3f1254ed01d0 scsi: mpi3mr: Successive VD delete and add causes FW fault ce756daa36e1 scsi: mpi3mr: Fix expander node leak in mpi3mr_remove() c798304470ca scsi: mpi3mr: Fix memory leaks in mpi3mr_init_ioc() d4caa1a4255c scsi: mpi3mr: Fix sas_hba.phy memory leak in mpi3mr_remove() d0f3c3728da8 scsi: mpi3mr: Fix mpi3mr_hba_port memory leak in mpi3mr_remove() 7d2b02172b6a scsi: mpi3mr: Fix config page DMA memory leak f305a7b6ca21 scsi: mpi3mr: Fix throttle_groups memory leak 8e45183978d6 scsi: mpi3mr: Bad drive in topology results kernel crash 4f297e856a7b scsi: mpi3mr: NVMe command size greater than 8K fails ba8a9ba41fbd scsi: mpi3mr: Return proper values for failures in firmware init path 0a319f162949 scsi: mpi3mr: Wait for diagnostic save during controller init 5b06a7169c59 scsi: mpi3mr: Driver unload crashes host when enhanced logging is enabled 02ca7da2919a scsi: mpi3mr: ioctl timeout when disabling/enabling interrupt 66b381d874fa scsi: mpi3mr: Remove unneeded version.h include e39ea831ebad scsi: mpi3mr: Fix missing mrioc->evtack_cmds initialization 339e61565f81 scsi: mpi3mr: Use number of bits to manage bitmap sizes eeb270aee3e0 scsi: mpi3mr: Remove unnecessary memcpy() to alltgt_info->dmi fb428a2005fc scsi: mpi3mr: Fix issues in mpi3mr_get_all_tgt_info() ae7d45f5283d scsi: mpi3mr: Fix an issue found by KASAN f0a43ba6c66c scsi: mpi3mr: Refer CONFIG_SCSI_MPI3MR in Makefile d347a951906b scsi: mpi3mr: Remove usage of dma_get_required_mask() API 7d21fcfb4095 scsi: mpi3mr: Suppress command reply debug prints 65244389b1b3 scsi: mpi3mr: Select CONFIG_SCSI_SAS_ATTRS c863a2dcb9b0 scsi: mpi3mr: Remove unnecessary cast f616efbee9d6 scsi: mpi3mr: Update driver version to 8.2.0.3.0 2e31be8697b1 scsi: mpi3mr: Fix scheduling while atomic type bug f84e8b5bb57e scsi: mpi3mr: Scan the devices during resume time 130fc180a481 scsi: mpi3mr: Free enclosure objects during driver unload bad2f28da625 scsi: mpi3mr: Handle 0xF003 Fault Code f2a79d2030ad scsi: mpi3mr: Graceful handling of surprise removal of PCIe HBA 7f9f953d537a scsi: mpi3mr: Schedule IRQ kthreads only on non-RT kernels 47cd930ee6ae scsi: mpi3mr: Support new power management framework ee6f2d6bb2a0 scsi: mpi3mr: Update mpi3 header files 5ba207e55e7f scsi: mpi3mr: Fix error code in mpi3mr_transport_smp_handler() a113c02f5738 scsi: mpi3mr: Fix error codes in mpi3mr_report_manufacture() 7f90bc70d1a6 scsi: mpi3mr: Block I/Os while refreshing target dev objects 2745ce0e6d30 scsi: mpi3mr: Refresh SAS ports during soft reset 176d4aa69c6e scsi: mpi3mr: Support SAS transport class callbacks 2bd37e284914 scsi: mpi3mr: Add framework to issue MPT transport cmds 7f56c791969e scsi: mpi3mr: Add SAS SATA end devices to STL 626665e9c38d scsi: mpi3mr: Get target object based on rphy e22bae30667a scsi: mpi3mr: Add expander devices to STL c4723e68a0d8 scsi: mpi3mr: Enable STL on HBAs where multipath is disabled 42fc9fee116f scsi: mpi3mr: Add helper functions to manage device's port 125ad1e6b445 scsi: mpi3mr: Add helper functions to retrieve device objects fc7212fd3100 scsi: mpi3mr: Add framework to add phys to STL 7188c03ff884 scsi: mpi3mr: Enable Enclosure device add event 64a8d9315b85 scsi: mpi3mr: Add helper functions to retrieve config pages 32d457d5a2af scsi: mpi3mr: Add framework to issue config requests 3b73c45e6fd2 scsi: mpi3mr: Add config and transport related debug flags a4e1d0b76e7b block: Change the return type of blk_mq_map_queues() into void --> This patch includes additional kernel changes as well. 502f4c18704d scsi: mpi3mr: Delete a stray tab 2a8a0147cb52 scsi: mpi3mr: Unlock on error path cf1ce8b71524 scsi: mpi3mr: Reduce VD queue depth on detecting throttling f10af057325c scsi: mpi3mr: Resource Based Metering d29ea7b71621 scsi: mpi3mr: Increase cmd_per_lun to 128 465191d6526a scsi: mpi3mr: Enable shared host tagset 2dd6532e9591 blk-mq: Drop 'reserved' arg of busy_tag_iter_fn --> This patch
[Kernel-packages] [Bug 2045233] Re: [SRU][22.04.04]: mpi3mr driver update
** Summary changed: - [Ubuntu 22.04.04]: mpi3mr driver update request + [SRU][22.04.04]: mpi3mr driver update -- 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: This BZ has been initiated to incorporate the mpi3mr driver from upstream into the upcoming Ubuntu releases (Ubuntu 22.04.x point releases). 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. 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 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 f762326b2baa scsi: mpi3mr: Propagate sense data for admin queue SCSI I/O 144679dfb584 scsi: mpi3mr: Fix the type used for pointers to bitmap 2a954832015d scsi: mpi3mr: Use -ENOMEM instead of -1 in mpi3mr_expander_add() 2acc635a0e5e scsi: mpi3mr: Use IRQ save variants of spinlock to protect chain frame allocation a3d27dfdcfc2 scsi: mpi3mr: Handle soft reset in progress fault code (0xF002) b85f82f3c92a scsi: mpi3mr: Declare SCSI host template const 1ea41edd88f2 scsi: mpi3mr: Update driver version to 8.4.1.0.0 e74f2fbd8b06 scsi: mpi3mr: Update copyright year 80b8fd0231d5 scsi: mpi3mr: Fix W=1 compilation warnings e5f596bc2592 scsi: mpi3mr: Update MPI Headers to revision 27 f1dec6b1e25e scsi: mpi3mr: Avoid escalating to higher level reset when target is removed 22beef38e52c scsi: mpi3mr: Modify MUR timeout value to 120 seconds 23b3d1cf1572 scsi: mpi3mr: Fix admin queue memory leak upon soft reset 3f1254ed01d0 scsi: mpi3mr: Successive VD delete and add causes FW fault ce756daa36e1 scsi: mpi3mr: Fix expander node leak in mpi3mr_remove() c798304470ca scsi: mpi3mr: Fix memory leaks in mpi3mr_init_ioc() d4caa1a4255c scsi: mpi3mr: Fix sas_hba.phy memory leak in mpi3mr_remove() d0f3c3728da8 scsi: mpi3mr: Fix mpi3mr_hba_port memory leak in mpi3mr_remove() 7d2b02172b6a scsi: mpi3mr: Fix config page DMA memory leak f305a7b6ca21 scsi: mpi3mr: Fix throttle_groups memory leak 8e45183978d6 scsi: mpi3mr: Bad drive in topology results kernel crash 4f297e856a7b scsi: mpi3mr: NVMe command size greater than 8K fails ba8a9ba41fbd scsi: mpi3mr: Return proper values for failures in firmware init path 0a319f162949 scsi: mpi3mr: Wait for diagnostic save during controller init 5b06a7169c59 scsi: mpi3mr: Driver unload crashes host when enhanced logging is enabled 02ca7da2919a scsi: mpi3mr: ioctl timeout when disabling/enabling interrupt 66b381d874fa scsi: mpi3mr: Remove unneeded version.h include e39ea831ebad scsi: mpi3mr: Fix missing mrioc->evtack_cmds initialization 339e61565f81 scsi: mpi3mr: Use number of bits to manage bitmap sizes eeb270aee3e0 scsi: mpi3mr: Remove unnecessary memcpy() to alltgt_info->dmi fb428a2005fc scsi: mpi3mr: Fix issues in mpi3mr_get_all_tgt_info() ae7d45f5283d scsi: mpi3mr: Fix an issue found by KASAN f0a43ba6c66c scsi: mpi3mr: Refer CONFIG_SCSI_MPI3MR in Makefile d347a951906b scsi: mpi3mr: Remove usage of dma_get_required_mask() API 7d21fcfb4095 scsi: mpi3mr: Suppress command reply debug prints 65244389b1b3 scsi: mpi3mr: Select CONFIG_SCSI_SAS_ATTRS c863a2dcb9b0 scsi: mpi3mr: Remove unnecessary cast f616efbee9d6 scsi: mpi3mr: Update driver version to 8.2.0.3.0 2e31be8697b1 scsi: mpi3mr: Fix scheduling while atomic type bug f84e8b5bb57e scsi: mpi3mr: Scan the devices during resume time 130fc180a481 scsi: mpi3mr: Free enclosure objects during driver unload bad2f28da625 scsi: mpi3mr: Handle 0xF003 Fault Code f2a79d2030ad scsi: mpi3mr: Graceful handling of surprise removal of PCIe HBA 7f9f953d537a scsi: mpi3mr: Schedule IRQ kthreads only on non-RT kernels
[Kernel-packages] [Bug 2037906] Re: [Intel AX201] Bluetooth LE not working after upgrade from 22.04 to 23.10
I have tried that Grzegorz - Thulium suggested but it doesn't work for
me.
--
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/2037906
Title:
[Intel AX201] Bluetooth LE not working after upgrade from 22.04 to
23.10
Status in Linux Firmware:
New
Status in bluez package in Ubuntu:
Confirmed
Status in linux package in Ubuntu:
Confirmed
Bug description:
syslog:
2023-09-20T09:32:54.138852+02:00 zaionc kernel: [ 13.539860] Bluetooth:
hci0: Waiting for firmware download to complete
2023-09-20T09:32:54.138857+02:00 zaionc kernel: [ 13.540223] Bluetooth:
hci0: Firmware loaded in 1706498 usecs
2023-09-20T09:32:54.138858+02:00 zaionc kernel: [ 13.540278] Bluetooth:
hci0: Waiting for device to boot
2023-09-20T09:32:54.154894+02:00 zaionc kernel: [ 13.555430] Bluetooth:
hci0: Malformed MSFT vendor event: 0x02
2023-09-20T09:32:54.154908+02:00 zaionc kernel: [ 13.555482] Bluetooth:
hci0: Device booted in 14872 usecs
2023-09-20T09:32:54.154910+02:00 zaionc kernel: [ 13.555913] Bluetooth:
hci0: Found Intel DDC parameters: intel/ibt-19-0-4.ddc
2023-09-20T09:32:54.158856+02:00 zaionc kernel: [ 13.558300] Bluetooth:
hci0: Applying Intel DDC parameters completed
2023-09-20T09:32:54.158859+02:00 zaionc kernel: [ 13.559326] Bluetooth:
hci0: Firmware revision 0.4 build 249 week 27 2023
lshw:
*-usb:5
description: Bluetooth wireless interface
product: AX201 Bluetooth
vendor: Intel Corp.
physical id: a
bus info: usb@3:a
version: 0.02
capabilities: bluetooth usb-2.01
configuration: driver=btusb maxpower=100mA speed=12Mbit/s
root@zaionc:~# hcitool lescan
Set scan parameters failed: Input/output error
At first bluetooth stopped working at all due to Ubuntu bug = missing
firmware. It was fixed recently and now the bluetooth module seems
fine, but the whole BTLE part is not available. Particularly I cannot
detect/pair Logitech M720 mouse.
Platform: ThinkPad T14 Gen 2i
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu4
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2022-05-28 (494 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64
(20220419)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
Package: linux
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-5-generic
root=UUID=d0002130-adf6-4f18-93b1-fda536d8b499 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
RebootRequiredPkgs: Error: path contained symlinks.
Tags: mantic
Uname: Linux 6.5.0-5-generic x86_64
UpgradeStatus: Upgraded to mantic on 2023-09-03 (30 days ago)
UserGroups: adm cdrom dialout dip docker lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 05/10/2023
dmi.bios.release: 1.56
dmi.bios.vendor: LENOVO
dmi.bios.version: N34ET56W (1.56 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20W000AMPB
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.42
dmi.modalias:
dmi:bvnLENOVO:bvrN34ET56W(1.56):bd05/10/2023:br1.56:efr1.42:svnLENOVO:pn20W000AMPB:pvrThinkPadT14Gen2i:rvnLENOVO:rn20W000AMPB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20W0_BU_Think_FM_ThinkPadT14Gen2i:
dmi.product.family: ThinkPad T14 Gen 2i
dmi.product.name: 20W000AMPB
dmi.product.sku: LENOVO_MT_20W0_BU_Think_FM_ThinkPad T14 Gen 2i
dmi.product.version: ThinkPad T14 Gen 2i
dmi.sys.vendor: LENOVO
hciconfig:
hci0:Type: Primary Bus: USB
BD Address: A0:E7:0B:23:70:E8 ACL MTU: 1021:4 SCO MTU: 96:6
UP RUNNING
RX bytes:22183 acl:0 sco:0 events:3531 errors:0
TX bytes:821193 acl:0 sco:0 commands:3510 errors:0
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux-firmware/+bug/2037906/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2044158] Re: Missing CS35L41 firmware for Dell Oasis Models
SRU: https://lists.ubuntu.com/archives/kernel-
team/2023-December/147591.html (jammy)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2044158
Title:
Missing CS35L41 firmware for Dell Oasis Models
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-firmware source package in Jammy:
In Progress
Status in linux-firmware source package in Mantic:
Fix Released
Status in linux-firmware source package in Noble:
Fix Released
Bug description:
[SRU Justification]
[Impact]
Missing CS35L41 firmware for Dell Oasis models. In dmesg output it has:
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.1: Cirrus Logic CS35L41 (35a40),
Revision: B2
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: Falling back to default firmware.
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: Firmware version: 3
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1:
cirrus/cs35l41-dsp1-spk-prot.wmfw: Fri 24 Jun 2022 14:55:56 GMT Daylight Time
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: Firmware: 400a4 vendor: 0x2
v0.58.0, 2 algorithms
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: 0: ID cd v29.78.0 XM@94 YM@e
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: 1: ID f20b v0.1.0 XM@17c
YM@0
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1:
cirrus/cs35l41-dsp1-spk-prot.bin: v0.58.0
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: spk-prot:
e:\workspace\workspace\tibranch_release_playback_6.76_2\ormis\staging\default_tunings\internal\CS35L53\Fixe
d_Attenuation_Mono_48000_29.78.0\full\Fixed_Attenuation_Mono_48000_29.78.0_full.bin
[Fix]
Upstream commit c8424cf03def ("cirrus: Add CS35L41 firmware for Dell Oasis
Models").
[Test Case]
Expecting the right fw blobs are used:
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.1: Cirrus Logic CS35L41 (35a40),
Revision: B2
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: Firmware version: 3
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1:
cirrus/cs35l41-dsp1-spk-prot-10280cbd.wmfw: Fri 27 Aug 2021 14:58:19 W. Europe
Daylight Time
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: Firmware: 400a4 vendor:
0x2 v0.43.1, 2 algorithms
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: 0: ID cd v29.63.1 XM@94
YM@e
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: 1: ID f20b v0.1.0 XM@176
YM@0
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1:
cirrus/cs35l41-dsp1-spk-prot-10280cbd-spkid0.bin: v0.43.1
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: spk-prot:
C:\Users\dchunyi\Documents\Dell\Oasis\tuning\default_tuning\10280CBD_230621_V01_A01.bin
[Where problems could occur]
That's the official firmware to support this platform. No known
problem so far.
[Other Info]
While this has been available on Mantic and Noble, we only nominate Jammy for
oem-6.5.
== original bug report ==
> cs35l41-hda spi1-CSC3551:00-cs35l41-hda.1: Falling back to default
firmware.
We probably need following firmware first.
$ git show --stat c8424cf03defa4a83b8305d1af7b1321ab62
commit c8424cf03defa4a83b8305d1af7b1321ab62
Author: Stefan Binding
Date: Thu Jul 13 17:16:45 2023 +0100
cirrus: Add CS35L41 firmware for Dell Oasis Models
Signed-off-by: Stefan Binding
WHENCE | 42 ++
cirrus/cs35l41-dsp1-spk-cali-10280cbd-spkid0.bin | Bin 0 -> 1824 bytes
cirrus/cs35l41-dsp1-spk-cali-10280cbd-spkid1.bin | Bin 0 -> 1824 bytes
cirrus/cs35l41-dsp1-spk-prot-10280cbd-spkid0.bin | Bin 0 -> 3980 bytes
cirrus/cs35l41-dsp1-spk-prot-10280cbd-spkid1.bin | Bin 0 -> 3980 bytes
5 files changed, 42 insertions(+)
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ubuntu 1052 F pulseaudio
CasperMD5json:
{
"result": "skip"
}
Dependencies: firmware-sof-signed 2.0-1ubuntu4.4+exp.12 [origin: unknown]
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more
[Kernel-packages] [Bug 2044158] ProcInterrupts.txt
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/2044158/+attachment/5729070/+files/ProcInterrupts.txt
--
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/2044158
Title:
Missing CS35L41 firmware for Dell Oasis Models
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-firmware source package in Jammy:
In Progress
Status in linux-firmware source package in Mantic:
Fix Released
Status in linux-firmware source package in Noble:
Fix Released
Bug description:
[SRU Justification]
[Impact]
Missing CS35L41 firmware for Dell Oasis models. In dmesg output it has:
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.1: Cirrus Logic CS35L41 (35a40),
Revision: B2
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: Falling back to default firmware.
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: Firmware version: 3
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1:
cirrus/cs35l41-dsp1-spk-prot.wmfw: Fri 24 Jun 2022 14:55:56 GMT Daylight Time
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: Firmware: 400a4 vendor: 0x2
v0.58.0, 2 algorithms
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: 0: ID cd v29.78.0 XM@94 YM@e
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: 1: ID f20b v0.1.0 XM@17c
YM@0
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1:
cirrus/cs35l41-dsp1-spk-prot.bin: v0.58.0
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: spk-prot:
e:\workspace\workspace\tibranch_release_playback_6.76_2\ormis\staging\default_tunings\internal\CS35L53\Fixe
d_Attenuation_Mono_48000_29.78.0\full\Fixed_Attenuation_Mono_48000_29.78.0_full.bin
[Fix]
Upstream commit c8424cf03def ("cirrus: Add CS35L41 firmware for Dell Oasis
Models").
[Test Case]
Expecting the right fw blobs are used:
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.1: Cirrus Logic CS35L41 (35a40),
Revision: B2
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: Firmware version: 3
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1:
cirrus/cs35l41-dsp1-spk-prot-10280cbd.wmfw: Fri 27 Aug 2021 14:58:19 W. Europe
Daylight Time
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: Firmware: 400a4 vendor:
0x2 v0.43.1, 2 algorithms
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: 0: ID cd v29.63.1 XM@94
YM@e
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: 1: ID f20b v0.1.0 XM@176
YM@0
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1:
cirrus/cs35l41-dsp1-spk-prot-10280cbd-spkid0.bin: v0.43.1
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: spk-prot:
C:\Users\dchunyi\Documents\Dell\Oasis\tuning\default_tuning\10280CBD_230621_V01_A01.bin
[Where problems could occur]
That's the official firmware to support this platform. No known
problem so far.
[Other Info]
While this has been available on Mantic and Noble, we only nominate Jammy for
oem-6.5.
== original bug report ==
> cs35l41-hda spi1-CSC3551:00-cs35l41-hda.1: Falling back to default
firmware.
We probably need following firmware first.
$ git show --stat c8424cf03defa4a83b8305d1af7b1321ab62
commit c8424cf03defa4a83b8305d1af7b1321ab62
Author: Stefan Binding
Date: Thu Jul 13 17:16:45 2023 +0100
cirrus: Add CS35L41 firmware for Dell Oasis Models
Signed-off-by: Stefan Binding
WHENCE | 42 ++
cirrus/cs35l41-dsp1-spk-cali-10280cbd-spkid0.bin | Bin 0 -> 1824 bytes
cirrus/cs35l41-dsp1-spk-cali-10280cbd-spkid1.bin | Bin 0 -> 1824 bytes
cirrus/cs35l41-dsp1-spk-prot-10280cbd-spkid0.bin | Bin 0 -> 3980 bytes
cirrus/cs35l41-dsp1-spk-prot-10280cbd-spkid1.bin | Bin 0 -> 3980 bytes
5 files changed, 42 insertions(+)
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ubuntu 1052 F pulseaudio
CasperMD5json:
{
"result": "skip"
}
Dependencies: firmware-sof-signed 2.0-1ubuntu4.4+exp.12 [origin: unknown]
DistributionChannelDescriptor:
# This is the
[Kernel-packages] [Bug 2044158] WifiSyslog.txt
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/2044158/+attachment/5729074/+files/WifiSyslog.txt
--
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/2044158
Title:
Missing CS35L41 firmware for Dell Oasis Models
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-firmware source package in Jammy:
In Progress
Status in linux-firmware source package in Mantic:
Fix Released
Status in linux-firmware source package in Noble:
Fix Released
Bug description:
[SRU Justification]
[Impact]
Missing CS35L41 firmware for Dell Oasis models. In dmesg output it has:
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.1: Cirrus Logic CS35L41 (35a40),
Revision: B2
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: Falling back to default firmware.
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: Firmware version: 3
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1:
cirrus/cs35l41-dsp1-spk-prot.wmfw: Fri 24 Jun 2022 14:55:56 GMT Daylight Time
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: Firmware: 400a4 vendor: 0x2
v0.58.0, 2 algorithms
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: 0: ID cd v29.78.0 XM@94 YM@e
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: 1: ID f20b v0.1.0 XM@17c
YM@0
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1:
cirrus/cs35l41-dsp1-spk-prot.bin: v0.58.0
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: spk-prot:
e:\workspace\workspace\tibranch_release_playback_6.76_2\ormis\staging\default_tunings\internal\CS35L53\Fixe
d_Attenuation_Mono_48000_29.78.0\full\Fixed_Attenuation_Mono_48000_29.78.0_full.bin
[Fix]
Upstream commit c8424cf03def ("cirrus: Add CS35L41 firmware for Dell Oasis
Models").
[Test Case]
Expecting the right fw blobs are used:
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.1: Cirrus Logic CS35L41 (35a40),
Revision: B2
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: Firmware version: 3
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1:
cirrus/cs35l41-dsp1-spk-prot-10280cbd.wmfw: Fri 27 Aug 2021 14:58:19 W. Europe
Daylight Time
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: Firmware: 400a4 vendor:
0x2 v0.43.1, 2 algorithms
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: 0: ID cd v29.63.1 XM@94
YM@e
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: 1: ID f20b v0.1.0 XM@176
YM@0
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1:
cirrus/cs35l41-dsp1-spk-prot-10280cbd-spkid0.bin: v0.43.1
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: spk-prot:
C:\Users\dchunyi\Documents\Dell\Oasis\tuning\default_tuning\10280CBD_230621_V01_A01.bin
[Where problems could occur]
That's the official firmware to support this platform. No known
problem so far.
[Other Info]
While this has been available on Mantic and Noble, we only nominate Jammy for
oem-6.5.
== original bug report ==
> cs35l41-hda spi1-CSC3551:00-cs35l41-hda.1: Falling back to default
firmware.
We probably need following firmware first.
$ git show --stat c8424cf03defa4a83b8305d1af7b1321ab62
commit c8424cf03defa4a83b8305d1af7b1321ab62
Author: Stefan Binding
Date: Thu Jul 13 17:16:45 2023 +0100
cirrus: Add CS35L41 firmware for Dell Oasis Models
Signed-off-by: Stefan Binding
WHENCE | 42 ++
cirrus/cs35l41-dsp1-spk-cali-10280cbd-spkid0.bin | Bin 0 -> 1824 bytes
cirrus/cs35l41-dsp1-spk-cali-10280cbd-spkid1.bin | Bin 0 -> 1824 bytes
cirrus/cs35l41-dsp1-spk-prot-10280cbd-spkid0.bin | Bin 0 -> 3980 bytes
cirrus/cs35l41-dsp1-spk-prot-10280cbd-spkid1.bin | Bin 0 -> 3980 bytes
5 files changed, 42 insertions(+)
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ubuntu 1052 F pulseaudio
CasperMD5json:
{
"result": "skip"
}
Dependencies: firmware-sof-signed 2.0-1ubuntu4.4+exp.12 [origin: unknown]
DistributionChannelDescriptor:
# This is the
[Kernel-packages] [Bug 2044158] UdevDb.txt
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/2044158/+attachment/5729073/+files/UdevDb.txt
--
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/2044158
Title:
Missing CS35L41 firmware for Dell Oasis Models
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-firmware source package in Jammy:
In Progress
Status in linux-firmware source package in Mantic:
Fix Released
Status in linux-firmware source package in Noble:
Fix Released
Bug description:
[SRU Justification]
[Impact]
Missing CS35L41 firmware for Dell Oasis models. In dmesg output it has:
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.1: Cirrus Logic CS35L41 (35a40),
Revision: B2
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: Falling back to default firmware.
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: Firmware version: 3
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1:
cirrus/cs35l41-dsp1-spk-prot.wmfw: Fri 24 Jun 2022 14:55:56 GMT Daylight Time
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: Firmware: 400a4 vendor: 0x2
v0.58.0, 2 algorithms
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: 0: ID cd v29.78.0 XM@94 YM@e
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: 1: ID f20b v0.1.0 XM@17c
YM@0
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1:
cirrus/cs35l41-dsp1-spk-prot.bin: v0.58.0
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: spk-prot:
e:\workspace\workspace\tibranch_release_playback_6.76_2\ormis\staging\default_tunings\internal\CS35L53\Fixe
d_Attenuation_Mono_48000_29.78.0\full\Fixed_Attenuation_Mono_48000_29.78.0_full.bin
[Fix]
Upstream commit c8424cf03def ("cirrus: Add CS35L41 firmware for Dell Oasis
Models").
[Test Case]
Expecting the right fw blobs are used:
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.1: Cirrus Logic CS35L41 (35a40),
Revision: B2
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: Firmware version: 3
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1:
cirrus/cs35l41-dsp1-spk-prot-10280cbd.wmfw: Fri 27 Aug 2021 14:58:19 W. Europe
Daylight Time
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: Firmware: 400a4 vendor:
0x2 v0.43.1, 2 algorithms
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: 0: ID cd v29.63.1 XM@94
YM@e
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: 1: ID f20b v0.1.0 XM@176
YM@0
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1:
cirrus/cs35l41-dsp1-spk-prot-10280cbd-spkid0.bin: v0.43.1
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: spk-prot:
C:\Users\dchunyi\Documents\Dell\Oasis\tuning\default_tuning\10280CBD_230621_V01_A01.bin
[Where problems could occur]
That's the official firmware to support this platform. No known
problem so far.
[Other Info]
While this has been available on Mantic and Noble, we only nominate Jammy for
oem-6.5.
== original bug report ==
> cs35l41-hda spi1-CSC3551:00-cs35l41-hda.1: Falling back to default
firmware.
We probably need following firmware first.
$ git show --stat c8424cf03defa4a83b8305d1af7b1321ab62
commit c8424cf03defa4a83b8305d1af7b1321ab62
Author: Stefan Binding
Date: Thu Jul 13 17:16:45 2023 +0100
cirrus: Add CS35L41 firmware for Dell Oasis Models
Signed-off-by: Stefan Binding
WHENCE | 42 ++
cirrus/cs35l41-dsp1-spk-cali-10280cbd-spkid0.bin | Bin 0 -> 1824 bytes
cirrus/cs35l41-dsp1-spk-cali-10280cbd-spkid1.bin | Bin 0 -> 1824 bytes
cirrus/cs35l41-dsp1-spk-prot-10280cbd-spkid0.bin | Bin 0 -> 3980 bytes
cirrus/cs35l41-dsp1-spk-prot-10280cbd-spkid1.bin | Bin 0 -> 3980 bytes
5 files changed, 42 insertions(+)
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ubuntu 1052 F pulseaudio
CasperMD5json:
{
"result": "skip"
}
Dependencies: firmware-sof-signed 2.0-1ubuntu4.4+exp.12 [origin: unknown]
DistributionChannelDescriptor:
# This is the distribution
[Kernel-packages] [Bug 2044158] Lsusb-v.txt
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/2044158/+attachment/5729065/+files/Lsusb-v.txt
--
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/2044158
Title:
Missing CS35L41 firmware for Dell Oasis Models
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-firmware source package in Jammy:
In Progress
Status in linux-firmware source package in Mantic:
Fix Released
Status in linux-firmware source package in Noble:
Fix Released
Bug description:
[SRU Justification]
[Impact]
Missing CS35L41 firmware for Dell Oasis models. In dmesg output it has:
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.1: Cirrus Logic CS35L41 (35a40),
Revision: B2
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: Falling back to default firmware.
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: Firmware version: 3
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1:
cirrus/cs35l41-dsp1-spk-prot.wmfw: Fri 24 Jun 2022 14:55:56 GMT Daylight Time
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: Firmware: 400a4 vendor: 0x2
v0.58.0, 2 algorithms
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: 0: ID cd v29.78.0 XM@94 YM@e
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: 1: ID f20b v0.1.0 XM@17c
YM@0
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1:
cirrus/cs35l41-dsp1-spk-prot.bin: v0.58.0
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: spk-prot:
e:\workspace\workspace\tibranch_release_playback_6.76_2\ormis\staging\default_tunings\internal\CS35L53\Fixe
d_Attenuation_Mono_48000_29.78.0\full\Fixed_Attenuation_Mono_48000_29.78.0_full.bin
[Fix]
Upstream commit c8424cf03def ("cirrus: Add CS35L41 firmware for Dell Oasis
Models").
[Test Case]
Expecting the right fw blobs are used:
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.1: Cirrus Logic CS35L41 (35a40),
Revision: B2
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: Firmware version: 3
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1:
cirrus/cs35l41-dsp1-spk-prot-10280cbd.wmfw: Fri 27 Aug 2021 14:58:19 W. Europe
Daylight Time
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: Firmware: 400a4 vendor:
0x2 v0.43.1, 2 algorithms
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: 0: ID cd v29.63.1 XM@94
YM@e
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: 1: ID f20b v0.1.0 XM@176
YM@0
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1:
cirrus/cs35l41-dsp1-spk-prot-10280cbd-spkid0.bin: v0.43.1
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: spk-prot:
C:\Users\dchunyi\Documents\Dell\Oasis\tuning\default_tuning\10280CBD_230621_V01_A01.bin
[Where problems could occur]
That's the official firmware to support this platform. No known
problem so far.
[Other Info]
While this has been available on Mantic and Noble, we only nominate Jammy for
oem-6.5.
== original bug report ==
> cs35l41-hda spi1-CSC3551:00-cs35l41-hda.1: Falling back to default
firmware.
We probably need following firmware first.
$ git show --stat c8424cf03defa4a83b8305d1af7b1321ab62
commit c8424cf03defa4a83b8305d1af7b1321ab62
Author: Stefan Binding
Date: Thu Jul 13 17:16:45 2023 +0100
cirrus: Add CS35L41 firmware for Dell Oasis Models
Signed-off-by: Stefan Binding
WHENCE | 42 ++
cirrus/cs35l41-dsp1-spk-cali-10280cbd-spkid0.bin | Bin 0 -> 1824 bytes
cirrus/cs35l41-dsp1-spk-cali-10280cbd-spkid1.bin | Bin 0 -> 1824 bytes
cirrus/cs35l41-dsp1-spk-prot-10280cbd-spkid0.bin | Bin 0 -> 3980 bytes
cirrus/cs35l41-dsp1-spk-prot-10280cbd-spkid1.bin | Bin 0 -> 3980 bytes
5 files changed, 42 insertions(+)
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ubuntu 1052 F pulseaudio
CasperMD5json:
{
"result": "skip"
}
Dependencies: firmware-sof-signed 2.0-1ubuntu4.4+exp.12 [origin: unknown]
DistributionChannelDescriptor:
# This is the distribution
[Kernel-packages] [Bug 2044158] RfKill.txt
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/2044158/+attachment/5729072/+files/RfKill.txt
--
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/2044158
Title:
Missing CS35L41 firmware for Dell Oasis Models
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-firmware source package in Jammy:
In Progress
Status in linux-firmware source package in Mantic:
Fix Released
Status in linux-firmware source package in Noble:
Fix Released
Bug description:
[SRU Justification]
[Impact]
Missing CS35L41 firmware for Dell Oasis models. In dmesg output it has:
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.1: Cirrus Logic CS35L41 (35a40),
Revision: B2
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: Falling back to default firmware.
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: Firmware version: 3
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1:
cirrus/cs35l41-dsp1-spk-prot.wmfw: Fri 24 Jun 2022 14:55:56 GMT Daylight Time
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: Firmware: 400a4 vendor: 0x2
v0.58.0, 2 algorithms
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: 0: ID cd v29.78.0 XM@94 YM@e
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: 1: ID f20b v0.1.0 XM@17c
YM@0
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1:
cirrus/cs35l41-dsp1-spk-prot.bin: v0.58.0
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: spk-prot:
e:\workspace\workspace\tibranch_release_playback_6.76_2\ormis\staging\default_tunings\internal\CS35L53\Fixe
d_Attenuation_Mono_48000_29.78.0\full\Fixed_Attenuation_Mono_48000_29.78.0_full.bin
[Fix]
Upstream commit c8424cf03def ("cirrus: Add CS35L41 firmware for Dell Oasis
Models").
[Test Case]
Expecting the right fw blobs are used:
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.1: Cirrus Logic CS35L41 (35a40),
Revision: B2
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: Firmware version: 3
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1:
cirrus/cs35l41-dsp1-spk-prot-10280cbd.wmfw: Fri 27 Aug 2021 14:58:19 W. Europe
Daylight Time
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: Firmware: 400a4 vendor:
0x2 v0.43.1, 2 algorithms
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: 0: ID cd v29.63.1 XM@94
YM@e
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: 1: ID f20b v0.1.0 XM@176
YM@0
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1:
cirrus/cs35l41-dsp1-spk-prot-10280cbd-spkid0.bin: v0.43.1
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: spk-prot:
C:\Users\dchunyi\Documents\Dell\Oasis\tuning\default_tuning\10280CBD_230621_V01_A01.bin
[Where problems could occur]
That's the official firmware to support this platform. No known
problem so far.
[Other Info]
While this has been available on Mantic and Noble, we only nominate Jammy for
oem-6.5.
== original bug report ==
> cs35l41-hda spi1-CSC3551:00-cs35l41-hda.1: Falling back to default
firmware.
We probably need following firmware first.
$ git show --stat c8424cf03defa4a83b8305d1af7b1321ab62
commit c8424cf03defa4a83b8305d1af7b1321ab62
Author: Stefan Binding
Date: Thu Jul 13 17:16:45 2023 +0100
cirrus: Add CS35L41 firmware for Dell Oasis Models
Signed-off-by: Stefan Binding
WHENCE | 42 ++
cirrus/cs35l41-dsp1-spk-cali-10280cbd-spkid0.bin | Bin 0 -> 1824 bytes
cirrus/cs35l41-dsp1-spk-cali-10280cbd-spkid1.bin | Bin 0 -> 1824 bytes
cirrus/cs35l41-dsp1-spk-prot-10280cbd-spkid0.bin | Bin 0 -> 3980 bytes
cirrus/cs35l41-dsp1-spk-prot-10280cbd-spkid1.bin | Bin 0 -> 3980 bytes
5 files changed, 42 insertions(+)
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ubuntu 1052 F pulseaudio
CasperMD5json:
{
"result": "skip"
}
Dependencies: firmware-sof-signed 2.0-1ubuntu4.4+exp.12 [origin: unknown]
DistributionChannelDescriptor:
# This is the distribution
[Kernel-packages] [Bug 2044158] ProcEnviron.txt
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/2044158/+attachment/5729069/+files/ProcEnviron.txt
--
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/2044158
Title:
Missing CS35L41 firmware for Dell Oasis Models
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-firmware source package in Jammy:
In Progress
Status in linux-firmware source package in Mantic:
Fix Released
Status in linux-firmware source package in Noble:
Fix Released
Bug description:
[SRU Justification]
[Impact]
Missing CS35L41 firmware for Dell Oasis models. In dmesg output it has:
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.1: Cirrus Logic CS35L41 (35a40),
Revision: B2
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: Falling back to default firmware.
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: Firmware version: 3
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1:
cirrus/cs35l41-dsp1-spk-prot.wmfw: Fri 24 Jun 2022 14:55:56 GMT Daylight Time
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: Firmware: 400a4 vendor: 0x2
v0.58.0, 2 algorithms
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: 0: ID cd v29.78.0 XM@94 YM@e
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: 1: ID f20b v0.1.0 XM@17c
YM@0
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1:
cirrus/cs35l41-dsp1-spk-prot.bin: v0.58.0
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: spk-prot:
e:\workspace\workspace\tibranch_release_playback_6.76_2\ormis\staging\default_tunings\internal\CS35L53\Fixe
d_Attenuation_Mono_48000_29.78.0\full\Fixed_Attenuation_Mono_48000_29.78.0_full.bin
[Fix]
Upstream commit c8424cf03def ("cirrus: Add CS35L41 firmware for Dell Oasis
Models").
[Test Case]
Expecting the right fw blobs are used:
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.1: Cirrus Logic CS35L41 (35a40),
Revision: B2
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: Firmware version: 3
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1:
cirrus/cs35l41-dsp1-spk-prot-10280cbd.wmfw: Fri 27 Aug 2021 14:58:19 W. Europe
Daylight Time
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: Firmware: 400a4 vendor:
0x2 v0.43.1, 2 algorithms
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: 0: ID cd v29.63.1 XM@94
YM@e
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: 1: ID f20b v0.1.0 XM@176
YM@0
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1:
cirrus/cs35l41-dsp1-spk-prot-10280cbd-spkid0.bin: v0.43.1
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: spk-prot:
C:\Users\dchunyi\Documents\Dell\Oasis\tuning\default_tuning\10280CBD_230621_V01_A01.bin
[Where problems could occur]
That's the official firmware to support this platform. No known
problem so far.
[Other Info]
While this has been available on Mantic and Noble, we only nominate Jammy for
oem-6.5.
== original bug report ==
> cs35l41-hda spi1-CSC3551:00-cs35l41-hda.1: Falling back to default
firmware.
We probably need following firmware first.
$ git show --stat c8424cf03defa4a83b8305d1af7b1321ab62
commit c8424cf03defa4a83b8305d1af7b1321ab62
Author: Stefan Binding
Date: Thu Jul 13 17:16:45 2023 +0100
cirrus: Add CS35L41 firmware for Dell Oasis Models
Signed-off-by: Stefan Binding
WHENCE | 42 ++
cirrus/cs35l41-dsp1-spk-cali-10280cbd-spkid0.bin | Bin 0 -> 1824 bytes
cirrus/cs35l41-dsp1-spk-cali-10280cbd-spkid1.bin | Bin 0 -> 1824 bytes
cirrus/cs35l41-dsp1-spk-prot-10280cbd-spkid0.bin | Bin 0 -> 3980 bytes
cirrus/cs35l41-dsp1-spk-prot-10280cbd-spkid1.bin | Bin 0 -> 3980 bytes
5 files changed, 42 insertions(+)
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ubuntu 1052 F pulseaudio
CasperMD5json:
{
"result": "skip"
}
Dependencies: firmware-sof-signed 2.0-1ubuntu4.4+exp.12 [origin: unknown]
DistributionChannelDescriptor:
# This is the
[Kernel-packages] [Bug 2044158] ProcCpuinfo.txt
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/2044158/+attachment/5729067/+files/ProcCpuinfo.txt
--
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/2044158
Title:
Missing CS35L41 firmware for Dell Oasis Models
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-firmware source package in Jammy:
In Progress
Status in linux-firmware source package in Mantic:
Fix Released
Status in linux-firmware source package in Noble:
Fix Released
Bug description:
[SRU Justification]
[Impact]
Missing CS35L41 firmware for Dell Oasis models. In dmesg output it has:
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.1: Cirrus Logic CS35L41 (35a40),
Revision: B2
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: Falling back to default firmware.
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: Firmware version: 3
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1:
cirrus/cs35l41-dsp1-spk-prot.wmfw: Fri 24 Jun 2022 14:55:56 GMT Daylight Time
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: Firmware: 400a4 vendor: 0x2
v0.58.0, 2 algorithms
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: 0: ID cd v29.78.0 XM@94 YM@e
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: 1: ID f20b v0.1.0 XM@17c
YM@0
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1:
cirrus/cs35l41-dsp1-spk-prot.bin: v0.58.0
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: spk-prot:
e:\workspace\workspace\tibranch_release_playback_6.76_2\ormis\staging\default_tunings\internal\CS35L53\Fixe
d_Attenuation_Mono_48000_29.78.0\full\Fixed_Attenuation_Mono_48000_29.78.0_full.bin
[Fix]
Upstream commit c8424cf03def ("cirrus: Add CS35L41 firmware for Dell Oasis
Models").
[Test Case]
Expecting the right fw blobs are used:
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.1: Cirrus Logic CS35L41 (35a40),
Revision: B2
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: Firmware version: 3
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1:
cirrus/cs35l41-dsp1-spk-prot-10280cbd.wmfw: Fri 27 Aug 2021 14:58:19 W. Europe
Daylight Time
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: Firmware: 400a4 vendor:
0x2 v0.43.1, 2 algorithms
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: 0: ID cd v29.63.1 XM@94
YM@e
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: 1: ID f20b v0.1.0 XM@176
YM@0
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1:
cirrus/cs35l41-dsp1-spk-prot-10280cbd-spkid0.bin: v0.43.1
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: spk-prot:
C:\Users\dchunyi\Documents\Dell\Oasis\tuning\default_tuning\10280CBD_230621_V01_A01.bin
[Where problems could occur]
That's the official firmware to support this platform. No known
problem so far.
[Other Info]
While this has been available on Mantic and Noble, we only nominate Jammy for
oem-6.5.
== original bug report ==
> cs35l41-hda spi1-CSC3551:00-cs35l41-hda.1: Falling back to default
firmware.
We probably need following firmware first.
$ git show --stat c8424cf03defa4a83b8305d1af7b1321ab62
commit c8424cf03defa4a83b8305d1af7b1321ab62
Author: Stefan Binding
Date: Thu Jul 13 17:16:45 2023 +0100
cirrus: Add CS35L41 firmware for Dell Oasis Models
Signed-off-by: Stefan Binding
WHENCE | 42 ++
cirrus/cs35l41-dsp1-spk-cali-10280cbd-spkid0.bin | Bin 0 -> 1824 bytes
cirrus/cs35l41-dsp1-spk-cali-10280cbd-spkid1.bin | Bin 0 -> 1824 bytes
cirrus/cs35l41-dsp1-spk-prot-10280cbd-spkid0.bin | Bin 0 -> 3980 bytes
cirrus/cs35l41-dsp1-spk-prot-10280cbd-spkid1.bin | Bin 0 -> 3980 bytes
5 files changed, 42 insertions(+)
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ubuntu 1052 F pulseaudio
CasperMD5json:
{
"result": "skip"
}
Dependencies: firmware-sof-signed 2.0-1ubuntu4.4+exp.12 [origin: unknown]
DistributionChannelDescriptor:
# This is the
[Kernel-packages] [Bug 2044158] PaInfo.txt
apport information
** Attachment added: "PaInfo.txt"
https://bugs.launchpad.net/bugs/2044158/+attachment/5729066/+files/PaInfo.txt
--
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/2044158
Title:
Missing CS35L41 firmware for Dell Oasis Models
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-firmware source package in Jammy:
In Progress
Status in linux-firmware source package in Mantic:
Fix Released
Status in linux-firmware source package in Noble:
Fix Released
Bug description:
[SRU Justification]
[Impact]
Missing CS35L41 firmware for Dell Oasis models. In dmesg output it has:
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.1: Cirrus Logic CS35L41 (35a40),
Revision: B2
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: Falling back to default firmware.
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: Firmware version: 3
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1:
cirrus/cs35l41-dsp1-spk-prot.wmfw: Fri 24 Jun 2022 14:55:56 GMT Daylight Time
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: Firmware: 400a4 vendor: 0x2
v0.58.0, 2 algorithms
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: 0: ID cd v29.78.0 XM@94 YM@e
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: 1: ID f20b v0.1.0 XM@17c
YM@0
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1:
cirrus/cs35l41-dsp1-spk-prot.bin: v0.58.0
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: spk-prot:
e:\workspace\workspace\tibranch_release_playback_6.76_2\ormis\staging\default_tunings\internal\CS35L53\Fixe
d_Attenuation_Mono_48000_29.78.0\full\Fixed_Attenuation_Mono_48000_29.78.0_full.bin
[Fix]
Upstream commit c8424cf03def ("cirrus: Add CS35L41 firmware for Dell Oasis
Models").
[Test Case]
Expecting the right fw blobs are used:
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.1: Cirrus Logic CS35L41 (35a40),
Revision: B2
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: Firmware version: 3
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1:
cirrus/cs35l41-dsp1-spk-prot-10280cbd.wmfw: Fri 27 Aug 2021 14:58:19 W. Europe
Daylight Time
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: Firmware: 400a4 vendor:
0x2 v0.43.1, 2 algorithms
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: 0: ID cd v29.63.1 XM@94
YM@e
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: 1: ID f20b v0.1.0 XM@176
YM@0
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1:
cirrus/cs35l41-dsp1-spk-prot-10280cbd-spkid0.bin: v0.43.1
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: spk-prot:
C:\Users\dchunyi\Documents\Dell\Oasis\tuning\default_tuning\10280CBD_230621_V01_A01.bin
[Where problems could occur]
That's the official firmware to support this platform. No known
problem so far.
[Other Info]
While this has been available on Mantic and Noble, we only nominate Jammy for
oem-6.5.
== original bug report ==
> cs35l41-hda spi1-CSC3551:00-cs35l41-hda.1: Falling back to default
firmware.
We probably need following firmware first.
$ git show --stat c8424cf03defa4a83b8305d1af7b1321ab62
commit c8424cf03defa4a83b8305d1af7b1321ab62
Author: Stefan Binding
Date: Thu Jul 13 17:16:45 2023 +0100
cirrus: Add CS35L41 firmware for Dell Oasis Models
Signed-off-by: Stefan Binding
WHENCE | 42 ++
cirrus/cs35l41-dsp1-spk-cali-10280cbd-spkid0.bin | Bin 0 -> 1824 bytes
cirrus/cs35l41-dsp1-spk-cali-10280cbd-spkid1.bin | Bin 0 -> 1824 bytes
cirrus/cs35l41-dsp1-spk-prot-10280cbd-spkid0.bin | Bin 0 -> 3980 bytes
cirrus/cs35l41-dsp1-spk-prot-10280cbd-spkid1.bin | Bin 0 -> 3980 bytes
5 files changed, 42 insertions(+)
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ubuntu 1052 F pulseaudio
CasperMD5json:
{
"result": "skip"
}
Dependencies: firmware-sof-signed 2.0-1ubuntu4.4+exp.12 [origin: unknown]
DistributionChannelDescriptor:
# This is the distribution
[Kernel-packages] [Bug 2044158] Lsusb-t.txt
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/2044158/+attachment/5729064/+files/Lsusb-t.txt
--
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/2044158
Title:
Missing CS35L41 firmware for Dell Oasis Models
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-firmware source package in Jammy:
In Progress
Status in linux-firmware source package in Mantic:
Fix Released
Status in linux-firmware source package in Noble:
Fix Released
Bug description:
[SRU Justification]
[Impact]
Missing CS35L41 firmware for Dell Oasis models. In dmesg output it has:
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.1: Cirrus Logic CS35L41 (35a40),
Revision: B2
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: Falling back to default firmware.
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: Firmware version: 3
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1:
cirrus/cs35l41-dsp1-spk-prot.wmfw: Fri 24 Jun 2022 14:55:56 GMT Daylight Time
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: Firmware: 400a4 vendor: 0x2
v0.58.0, 2 algorithms
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: 0: ID cd v29.78.0 XM@94 YM@e
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: 1: ID f20b v0.1.0 XM@17c
YM@0
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1:
cirrus/cs35l41-dsp1-spk-prot.bin: v0.58.0
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: spk-prot:
e:\workspace\workspace\tibranch_release_playback_6.76_2\ormis\staging\default_tunings\internal\CS35L53\Fixe
d_Attenuation_Mono_48000_29.78.0\full\Fixed_Attenuation_Mono_48000_29.78.0_full.bin
[Fix]
Upstream commit c8424cf03def ("cirrus: Add CS35L41 firmware for Dell Oasis
Models").
[Test Case]
Expecting the right fw blobs are used:
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.1: Cirrus Logic CS35L41 (35a40),
Revision: B2
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: Firmware version: 3
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1:
cirrus/cs35l41-dsp1-spk-prot-10280cbd.wmfw: Fri 27 Aug 2021 14:58:19 W. Europe
Daylight Time
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: Firmware: 400a4 vendor:
0x2 v0.43.1, 2 algorithms
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: 0: ID cd v29.63.1 XM@94
YM@e
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: 1: ID f20b v0.1.0 XM@176
YM@0
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1:
cirrus/cs35l41-dsp1-spk-prot-10280cbd-spkid0.bin: v0.43.1
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: spk-prot:
C:\Users\dchunyi\Documents\Dell\Oasis\tuning\default_tuning\10280CBD_230621_V01_A01.bin
[Where problems could occur]
That's the official firmware to support this platform. No known
problem so far.
[Other Info]
While this has been available on Mantic and Noble, we only nominate Jammy for
oem-6.5.
== original bug report ==
> cs35l41-hda spi1-CSC3551:00-cs35l41-hda.1: Falling back to default
firmware.
We probably need following firmware first.
$ git show --stat c8424cf03defa4a83b8305d1af7b1321ab62
commit c8424cf03defa4a83b8305d1af7b1321ab62
Author: Stefan Binding
Date: Thu Jul 13 17:16:45 2023 +0100
cirrus: Add CS35L41 firmware for Dell Oasis Models
Signed-off-by: Stefan Binding
WHENCE | 42 ++
cirrus/cs35l41-dsp1-spk-cali-10280cbd-spkid0.bin | Bin 0 -> 1824 bytes
cirrus/cs35l41-dsp1-spk-cali-10280cbd-spkid1.bin | Bin 0 -> 1824 bytes
cirrus/cs35l41-dsp1-spk-prot-10280cbd-spkid0.bin | Bin 0 -> 3980 bytes
cirrus/cs35l41-dsp1-spk-prot-10280cbd-spkid1.bin | Bin 0 -> 3980 bytes
5 files changed, 42 insertions(+)
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ubuntu 1052 F pulseaudio
CasperMD5json:
{
"result": "skip"
}
Dependencies: firmware-sof-signed 2.0-1ubuntu4.4+exp.12 [origin: unknown]
DistributionChannelDescriptor:
# This is the distribution
[Kernel-packages] [Bug 2044158] Lsusb.txt
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/2044158/+attachment/5729063/+files/Lsusb.txt
--
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/2044158
Title:
Missing CS35L41 firmware for Dell Oasis Models
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-firmware source package in Jammy:
In Progress
Status in linux-firmware source package in Mantic:
Fix Released
Status in linux-firmware source package in Noble:
Fix Released
Bug description:
[SRU Justification]
[Impact]
Missing CS35L41 firmware for Dell Oasis models. In dmesg output it has:
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.1: Cirrus Logic CS35L41 (35a40),
Revision: B2
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: Falling back to default firmware.
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: Firmware version: 3
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1:
cirrus/cs35l41-dsp1-spk-prot.wmfw: Fri 24 Jun 2022 14:55:56 GMT Daylight Time
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: Firmware: 400a4 vendor: 0x2
v0.58.0, 2 algorithms
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: 0: ID cd v29.78.0 XM@94 YM@e
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: 1: ID f20b v0.1.0 XM@17c
YM@0
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1:
cirrus/cs35l41-dsp1-spk-prot.bin: v0.58.0
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: spk-prot:
e:\workspace\workspace\tibranch_release_playback_6.76_2\ormis\staging\default_tunings\internal\CS35L53\Fixe
d_Attenuation_Mono_48000_29.78.0\full\Fixed_Attenuation_Mono_48000_29.78.0_full.bin
[Fix]
Upstream commit c8424cf03def ("cirrus: Add CS35L41 firmware for Dell Oasis
Models").
[Test Case]
Expecting the right fw blobs are used:
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.1: Cirrus Logic CS35L41 (35a40),
Revision: B2
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: Firmware version: 3
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1:
cirrus/cs35l41-dsp1-spk-prot-10280cbd.wmfw: Fri 27 Aug 2021 14:58:19 W. Europe
Daylight Time
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: Firmware: 400a4 vendor:
0x2 v0.43.1, 2 algorithms
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: 0: ID cd v29.63.1 XM@94
YM@e
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: 1: ID f20b v0.1.0 XM@176
YM@0
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1:
cirrus/cs35l41-dsp1-spk-prot-10280cbd-spkid0.bin: v0.43.1
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: spk-prot:
C:\Users\dchunyi\Documents\Dell\Oasis\tuning\default_tuning\10280CBD_230621_V01_A01.bin
[Where problems could occur]
That's the official firmware to support this platform. No known
problem so far.
[Other Info]
While this has been available on Mantic and Noble, we only nominate Jammy for
oem-6.5.
== original bug report ==
> cs35l41-hda spi1-CSC3551:00-cs35l41-hda.1: Falling back to default
firmware.
We probably need following firmware first.
$ git show --stat c8424cf03defa4a83b8305d1af7b1321ab62
commit c8424cf03defa4a83b8305d1af7b1321ab62
Author: Stefan Binding
Date: Thu Jul 13 17:16:45 2023 +0100
cirrus: Add CS35L41 firmware for Dell Oasis Models
Signed-off-by: Stefan Binding
WHENCE | 42 ++
cirrus/cs35l41-dsp1-spk-cali-10280cbd-spkid0.bin | Bin 0 -> 1824 bytes
cirrus/cs35l41-dsp1-spk-cali-10280cbd-spkid1.bin | Bin 0 -> 1824 bytes
cirrus/cs35l41-dsp1-spk-prot-10280cbd-spkid0.bin | Bin 0 -> 3980 bytes
cirrus/cs35l41-dsp1-spk-prot-10280cbd-spkid1.bin | Bin 0 -> 3980 bytes
5 files changed, 42 insertions(+)
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ubuntu 1052 F pulseaudio
CasperMD5json:
{
"result": "skip"
}
Dependencies: firmware-sof-signed 2.0-1ubuntu4.4+exp.12 [origin: unknown]
DistributionChannelDescriptor:
# This is the distribution
[Kernel-packages] [Bug 2044158] acpidump.txt
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/2044158/+attachment/5729075/+files/acpidump.txt
** Description changed:
+ [SRU Justification]
+
+ [Impact]
+
+ Missing CS35L41 firmware for Dell Oasis models. In dmesg output it has:
+
+ cs35l41-hda i2c-CSC3551:00-cs35l41-hda.1: Cirrus Logic CS35L41 (35a40),
Revision: B2
+ cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: Falling back to default firmware.
+ cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: Firmware version: 3
+ cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1:
cirrus/cs35l41-dsp1-spk-prot.wmfw: Fri 24 Jun 2022 14:55:56 GMT Daylight Time
+ cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: Firmware: 400a4 vendor: 0x2
v0.58.0, 2 algorithms
+ cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: 0: ID cd v29.78.0 XM@94 YM@e
+ cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: 1: ID f20b v0.1.0 XM@17c
YM@0
+ cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1:
cirrus/cs35l41-dsp1-spk-prot.bin: v0.58.0
+ cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: spk-prot:
e:\workspace\workspace\tibranch_release_playback_6.76_2\ormis\staging\default_tunings\internal\CS35L53\Fixe
+
d_Attenuation_Mono_48000_29.78.0\full\Fixed_Attenuation_Mono_48000_29.78.0_full.bin
+
+ [Fix]
+
+ Upstream commit c8424cf03def ("cirrus: Add CS35L41 firmware for Dell Oasis
Models").
+
+ [Test Case]
+
+ Expecting the right fw blobs are used:
+
+ cs35l41-hda i2c-CSC3551:00-cs35l41-hda.1: Cirrus Logic CS35L41 (35a40),
Revision: B2
+ cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: Firmware version: 3
+ cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1:
cirrus/cs35l41-dsp1-spk-prot-10280cbd.wmfw: Fri 27 Aug 2021 14:58:19 W. Europe
Daylight Time
+ cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: Firmware: 400a4 vendor:
0x2 v0.43.1, 2 algorithms
+ cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: 0: ID cd v29.63.1 XM@94
YM@e
+ cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: 1: ID f20b v0.1.0 XM@176
YM@0
+ cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1:
cirrus/cs35l41-dsp1-spk-prot-10280cbd-spkid0.bin: v0.43.1
+ cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: spk-prot:
C:\Users\dchunyi\Documents\Dell\Oasis\tuning\default_tuning\10280CBD_230621_V01_A01.bin
+
+ [Where problems could occur]
+
+ That's the official firmware to support this platform. No known problem
+ so far.
+
+ [Other Info]
+
+ While this has been available on Mantic and Noble, we only nominate Jammy for
+ oem-6.5.
+
+ == original bug report ==
+
> cs35l41-hda spi1-CSC3551:00-cs35l41-hda.1: Falling back to default
firmware.
We probably need following firmware first.
$ git show --stat c8424cf03defa4a83b8305d1af7b1321ab62
commit c8424cf03defa4a83b8305d1af7b1321ab62
Author: Stefan Binding
Date: Thu Jul 13 17:16:45 2023 +0100
cirrus: Add CS35L41 firmware for Dell Oasis Models
Signed-off-by: Stefan Binding
WHENCE | 42 ++
cirrus/cs35l41-dsp1-spk-cali-10280cbd-spkid0.bin | Bin 0 -> 1824 bytes
cirrus/cs35l41-dsp1-spk-cali-10280cbd-spkid1.bin | Bin 0 -> 1824 bytes
cirrus/cs35l41-dsp1-spk-prot-10280cbd-spkid0.bin | Bin 0 -> 3980 bytes
cirrus/cs35l41-dsp1-spk-prot-10280cbd-spkid1.bin | Bin 0 -> 3980 bytes
5 files changed, 42 insertions(+)
- ---
+ ---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse:
- USERPID ACCESS COMMAND
- /dev/snd/controlC0: ubuntu 1052 F pulseaudio
+ USERPID ACCESS COMMAND
+ /dev/snd/controlC0: ubuntu 1052 F pulseaudio
CasperMD5json:
- {
-"result": "skip"
- }
+ {
+ "result": "skip"
+ }
Dependencies: firmware-sof-signed 2.0-1ubuntu4.4+exp.12 [origin: unknown]
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-oddish13+X114
+ # This is the distribution channel descriptor for the OEM CDs
+ # For more information see
[Kernel-packages] [Bug 2044158] ProcCpuinfoMinimal.txt
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/2044158/+attachment/5729068/+files/ProcCpuinfoMinimal.txt
--
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/2044158
Title:
Missing CS35L41 firmware for Dell Oasis Models
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-firmware source package in Jammy:
In Progress
Status in linux-firmware source package in Mantic:
Fix Released
Status in linux-firmware source package in Noble:
Fix Released
Bug description:
[SRU Justification]
[Impact]
Missing CS35L41 firmware for Dell Oasis models. In dmesg output it has:
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.1: Cirrus Logic CS35L41 (35a40),
Revision: B2
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: Falling back to default firmware.
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: Firmware version: 3
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1:
cirrus/cs35l41-dsp1-spk-prot.wmfw: Fri 24 Jun 2022 14:55:56 GMT Daylight Time
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: Firmware: 400a4 vendor: 0x2
v0.58.0, 2 algorithms
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: 0: ID cd v29.78.0 XM@94 YM@e
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: 1: ID f20b v0.1.0 XM@17c
YM@0
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1:
cirrus/cs35l41-dsp1-spk-prot.bin: v0.58.0
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: spk-prot:
e:\workspace\workspace\tibranch_release_playback_6.76_2\ormis\staging\default_tunings\internal\CS35L53\Fixe
d_Attenuation_Mono_48000_29.78.0\full\Fixed_Attenuation_Mono_48000_29.78.0_full.bin
[Fix]
Upstream commit c8424cf03def ("cirrus: Add CS35L41 firmware for Dell Oasis
Models").
[Test Case]
Expecting the right fw blobs are used:
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.1: Cirrus Logic CS35L41 (35a40),
Revision: B2
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: Firmware version: 3
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1:
cirrus/cs35l41-dsp1-spk-prot-10280cbd.wmfw: Fri 27 Aug 2021 14:58:19 W. Europe
Daylight Time
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: Firmware: 400a4 vendor:
0x2 v0.43.1, 2 algorithms
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: 0: ID cd v29.63.1 XM@94
YM@e
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: 1: ID f20b v0.1.0 XM@176
YM@0
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1:
cirrus/cs35l41-dsp1-spk-prot-10280cbd-spkid0.bin: v0.43.1
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: spk-prot:
C:\Users\dchunyi\Documents\Dell\Oasis\tuning\default_tuning\10280CBD_230621_V01_A01.bin
[Where problems could occur]
That's the official firmware to support this platform. No known
problem so far.
[Other Info]
While this has been available on Mantic and Noble, we only nominate Jammy for
oem-6.5.
== original bug report ==
> cs35l41-hda spi1-CSC3551:00-cs35l41-hda.1: Falling back to default
firmware.
We probably need following firmware first.
$ git show --stat c8424cf03defa4a83b8305d1af7b1321ab62
commit c8424cf03defa4a83b8305d1af7b1321ab62
Author: Stefan Binding
Date: Thu Jul 13 17:16:45 2023 +0100
cirrus: Add CS35L41 firmware for Dell Oasis Models
Signed-off-by: Stefan Binding
WHENCE | 42 ++
cirrus/cs35l41-dsp1-spk-cali-10280cbd-spkid0.bin | Bin 0 -> 1824 bytes
cirrus/cs35l41-dsp1-spk-cali-10280cbd-spkid1.bin | Bin 0 -> 1824 bytes
cirrus/cs35l41-dsp1-spk-prot-10280cbd-spkid0.bin | Bin 0 -> 3980 bytes
cirrus/cs35l41-dsp1-spk-prot-10280cbd-spkid1.bin | Bin 0 -> 3980 bytes
5 files changed, 42 insertions(+)
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ubuntu 1052 F pulseaudio
CasperMD5json:
{
"result": "skip"
}
Dependencies: firmware-sof-signed 2.0-1ubuntu4.4+exp.12 [origin: unknown]
DistributionChannelDescriptor:
# This
[Kernel-packages] [Bug 2044158] ProcModules.txt
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/2044158/+attachment/5729071/+files/ProcModules.txt
--
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/2044158
Title:
Missing CS35L41 firmware for Dell Oasis Models
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-firmware source package in Jammy:
In Progress
Status in linux-firmware source package in Mantic:
Fix Released
Status in linux-firmware source package in Noble:
Fix Released
Bug description:
[SRU Justification]
[Impact]
Missing CS35L41 firmware for Dell Oasis models. In dmesg output it has:
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.1: Cirrus Logic CS35L41 (35a40),
Revision: B2
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: Falling back to default firmware.
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: Firmware version: 3
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1:
cirrus/cs35l41-dsp1-spk-prot.wmfw: Fri 24 Jun 2022 14:55:56 GMT Daylight Time
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: Firmware: 400a4 vendor: 0x2
v0.58.0, 2 algorithms
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: 0: ID cd v29.78.0 XM@94 YM@e
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: 1: ID f20b v0.1.0 XM@17c
YM@0
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1:
cirrus/cs35l41-dsp1-spk-prot.bin: v0.58.0
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: spk-prot:
e:\workspace\workspace\tibranch_release_playback_6.76_2\ormis\staging\default_tunings\internal\CS35L53\Fixe
d_Attenuation_Mono_48000_29.78.0\full\Fixed_Attenuation_Mono_48000_29.78.0_full.bin
[Fix]
Upstream commit c8424cf03def ("cirrus: Add CS35L41 firmware for Dell Oasis
Models").
[Test Case]
Expecting the right fw blobs are used:
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.1: Cirrus Logic CS35L41 (35a40),
Revision: B2
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: Firmware version: 3
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1:
cirrus/cs35l41-dsp1-spk-prot-10280cbd.wmfw: Fri 27 Aug 2021 14:58:19 W. Europe
Daylight Time
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: Firmware: 400a4 vendor:
0x2 v0.43.1, 2 algorithms
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: 0: ID cd v29.63.1 XM@94
YM@e
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: 1: ID f20b v0.1.0 XM@176
YM@0
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1:
cirrus/cs35l41-dsp1-spk-prot-10280cbd-spkid0.bin: v0.43.1
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: spk-prot:
C:\Users\dchunyi\Documents\Dell\Oasis\tuning\default_tuning\10280CBD_230621_V01_A01.bin
[Where problems could occur]
That's the official firmware to support this platform. No known
problem so far.
[Other Info]
While this has been available on Mantic and Noble, we only nominate Jammy for
oem-6.5.
== original bug report ==
> cs35l41-hda spi1-CSC3551:00-cs35l41-hda.1: Falling back to default
firmware.
We probably need following firmware first.
$ git show --stat c8424cf03defa4a83b8305d1af7b1321ab62
commit c8424cf03defa4a83b8305d1af7b1321ab62
Author: Stefan Binding
Date: Thu Jul 13 17:16:45 2023 +0100
cirrus: Add CS35L41 firmware for Dell Oasis Models
Signed-off-by: Stefan Binding
WHENCE | 42 ++
cirrus/cs35l41-dsp1-spk-cali-10280cbd-spkid0.bin | Bin 0 -> 1824 bytes
cirrus/cs35l41-dsp1-spk-cali-10280cbd-spkid1.bin | Bin 0 -> 1824 bytes
cirrus/cs35l41-dsp1-spk-prot-10280cbd-spkid0.bin | Bin 0 -> 3980 bytes
cirrus/cs35l41-dsp1-spk-prot-10280cbd-spkid1.bin | Bin 0 -> 3980 bytes
5 files changed, 42 insertions(+)
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ubuntu 1052 F pulseaudio
CasperMD5json:
{
"result": "skip"
}
Dependencies: firmware-sof-signed 2.0-1ubuntu4.4+exp.12 [origin: unknown]
DistributionChannelDescriptor:
# This is the
[Kernel-packages] [Bug 2044158] Re: Missing CS35L41 firmware for Dell Oasis Models
apport information
** Tags added: apport-collected jammy third-party-packages
** Description changed:
> cs35l41-hda spi1-CSC3551:00-cs35l41-hda.1: Falling back to default
firmware.
We probably need following firmware first.
$ git show --stat c8424cf03defa4a83b8305d1af7b1321ab62
commit c8424cf03defa4a83b8305d1af7b1321ab62
Author: Stefan Binding
Date: Thu Jul 13 17:16:45 2023 +0100
cirrus: Add CS35L41 firmware for Dell Oasis Models
Signed-off-by: Stefan Binding
WHENCE | 42 ++
cirrus/cs35l41-dsp1-spk-cali-10280cbd-spkid0.bin | Bin 0 -> 1824 bytes
cirrus/cs35l41-dsp1-spk-cali-10280cbd-spkid1.bin | Bin 0 -> 1824 bytes
cirrus/cs35l41-dsp1-spk-prot-10280cbd-spkid0.bin | Bin 0 -> 3980 bytes
cirrus/cs35l41-dsp1-spk-prot-10280cbd-spkid1.bin | Bin 0 -> 3980 bytes
5 files changed, 42 insertions(+)
+ ---
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu82.5
+ Architecture: amd64
+ AudioDevicesInUse:
+ USERPID ACCESS COMMAND
+ /dev/snd/controlC0: ubuntu 1052 F pulseaudio
+ CasperMD5json:
+ {
+"result": "skip"
+ }
+ Dependencies: firmware-sof-signed 2.0-1ubuntu4.4+exp.12 [origin: unknown]
+ 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-oddish13+X114
+ DistroRelease: Ubuntu 22.04
+ InstallationDate: Installed on 2023-12-08 (5 days ago)
+ InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" -
somerville-jammy-amd64-20220504-33
+ IwConfig:
+ lono wireless extensions.
+
+ wlp85s0f0 no wireless extensions.
+
+ enx00e04c680352 no wireless extensions.
+ MachineType: Dell Inc. Latitude 7350
+ Package: linux-firmware 20220329.git681281e4-0ubuntu3.23+exp.92 [origin:
unknown]
+ PackageArchitecture: all
+ ProcFB: 0 i915drmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9009-oem
root=UUID=d3612d22-9573-43a8-919c-c759faa64541 ro automatic-oem-config quiet
splash vt.handoff=7
+ ProcVersionSignature: Ubuntu 6.5.0-9009.10+exp.32-oem 6.5.3
+ PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
+ RelatedPackageVersions:
+ linux-restricted-modules-6.5.0-9009-oem N/A
+ linux-backports-modules-6.5.0-9009-oem N/A
+ linux-firmware
20220329.git681281e4-0ubuntu3.23+exp.92
+ Tags: jammy third-party-packages
+ Uname: Linux 6.5.0-9009-oem x86_64
+ UnreportableReason: This does not seem to be an official Ubuntu package.
Please retry after updating the indexes of available packages, if that does not
work then remove related third party packages and try again.
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: N/A
+ _MarkForUpload: True
+ dmi.bios.date: 12/08/2023
+ dmi.bios.release: 0.4
+ dmi.bios.vendor: Dell Inc.
+ dmi.bios.version: 0.4.35
+ dmi.board.name: 0UB010
+ dmi.board.vendor: Dell Inc.
+ dmi.board.version: D02
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: Dell Inc.
+ dmi.ec.firmware.release: 0.0
+ dmi.modalias:
dmi:bvnDellInc.:bvr0.4.35:bd12/08/2023:br0.4:efr0.0:svnDellInc.:pnLatitude7350:pvr:rvnDellInc.:rn0UB010:rvrD02:cvnDellInc.:ct10:cvr:sku0CBF:
+ dmi.product.family: Latitude
+ dmi.product.name: Latitude 7350
+ dmi.product.sku: 0CBF
+ dmi.sys.vendor: Dell Inc.
** Attachment added: "AlsaInfo.txt"
https://bugs.launchpad.net/bugs/2044158/+attachment/5729057/+files/AlsaInfo.txt
--
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/2044158
Title:
Missing CS35L41 firmware for Dell Oasis Models
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-firmware source package in Jammy:
In Progress
Status in linux-firmware source package in Mantic:
Fix Released
Status in linux-firmware source package in Noble:
Fix Released
Bug description:
[SRU Justification]
[Impact]
Missing CS35L41 firmware for Dell Oasis models. In dmesg output it has:
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.1: Cirrus Logic CS35L41 (35a40),
Revision: B2
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: Falling back to default firmware.
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: Firmware version: 3
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1:
cirrus/cs35l41-dsp1-spk-prot.wmfw: Fri 24 Jun 2022 14:55:56 GMT Daylight Time
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: Firmware: 400a4 vendor: 0x2
v0.58.0, 2 algorithms
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: 0: ID cd v29.78.0 XM@94 YM@e
[Kernel-packages] [Bug 2044158] Lspci-vt.txt
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/2044158/+attachment/5729062/+files/Lspci-vt.txt
--
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/2044158
Title:
Missing CS35L41 firmware for Dell Oasis Models
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-firmware source package in Jammy:
In Progress
Status in linux-firmware source package in Mantic:
Fix Released
Status in linux-firmware source package in Noble:
Fix Released
Bug description:
[SRU Justification]
[Impact]
Missing CS35L41 firmware for Dell Oasis models. In dmesg output it has:
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.1: Cirrus Logic CS35L41 (35a40),
Revision: B2
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: Falling back to default firmware.
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: Firmware version: 3
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1:
cirrus/cs35l41-dsp1-spk-prot.wmfw: Fri 24 Jun 2022 14:55:56 GMT Daylight Time
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: Firmware: 400a4 vendor: 0x2
v0.58.0, 2 algorithms
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: 0: ID cd v29.78.0 XM@94 YM@e
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: 1: ID f20b v0.1.0 XM@17c
YM@0
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1:
cirrus/cs35l41-dsp1-spk-prot.bin: v0.58.0
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: spk-prot:
e:\workspace\workspace\tibranch_release_playback_6.76_2\ormis\staging\default_tunings\internal\CS35L53\Fixe
d_Attenuation_Mono_48000_29.78.0\full\Fixed_Attenuation_Mono_48000_29.78.0_full.bin
[Fix]
Upstream commit c8424cf03def ("cirrus: Add CS35L41 firmware for Dell Oasis
Models").
[Test Case]
Expecting the right fw blobs are used:
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.1: Cirrus Logic CS35L41 (35a40),
Revision: B2
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: Firmware version: 3
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1:
cirrus/cs35l41-dsp1-spk-prot-10280cbd.wmfw: Fri 27 Aug 2021 14:58:19 W. Europe
Daylight Time
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: Firmware: 400a4 vendor:
0x2 v0.43.1, 2 algorithms
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: 0: ID cd v29.63.1 XM@94
YM@e
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: 1: ID f20b v0.1.0 XM@176
YM@0
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1:
cirrus/cs35l41-dsp1-spk-prot-10280cbd-spkid0.bin: v0.43.1
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: spk-prot:
C:\Users\dchunyi\Documents\Dell\Oasis\tuning\default_tuning\10280CBD_230621_V01_A01.bin
[Where problems could occur]
That's the official firmware to support this platform. No known
problem so far.
[Other Info]
While this has been available on Mantic and Noble, we only nominate Jammy for
oem-6.5.
== original bug report ==
> cs35l41-hda spi1-CSC3551:00-cs35l41-hda.1: Falling back to default
firmware.
We probably need following firmware first.
$ git show --stat c8424cf03defa4a83b8305d1af7b1321ab62
commit c8424cf03defa4a83b8305d1af7b1321ab62
Author: Stefan Binding
Date: Thu Jul 13 17:16:45 2023 +0100
cirrus: Add CS35L41 firmware for Dell Oasis Models
Signed-off-by: Stefan Binding
WHENCE | 42 ++
cirrus/cs35l41-dsp1-spk-cali-10280cbd-spkid0.bin | Bin 0 -> 1824 bytes
cirrus/cs35l41-dsp1-spk-cali-10280cbd-spkid1.bin | Bin 0 -> 1824 bytes
cirrus/cs35l41-dsp1-spk-prot-10280cbd-spkid0.bin | Bin 0 -> 3980 bytes
cirrus/cs35l41-dsp1-spk-prot-10280cbd-spkid1.bin | Bin 0 -> 3980 bytes
5 files changed, 42 insertions(+)
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ubuntu 1052 F pulseaudio
CasperMD5json:
{
"result": "skip"
}
Dependencies: firmware-sof-signed 2.0-1ubuntu4.4+exp.12 [origin: unknown]
DistributionChannelDescriptor:
# This is the distribution
[Kernel-packages] [Bug 2044158] Lspci.txt
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/2044158/+attachment/5729061/+files/Lspci.txt
--
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/2044158
Title:
Missing CS35L41 firmware for Dell Oasis Models
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-firmware source package in Jammy:
In Progress
Status in linux-firmware source package in Mantic:
Fix Released
Status in linux-firmware source package in Noble:
Fix Released
Bug description:
[SRU Justification]
[Impact]
Missing CS35L41 firmware for Dell Oasis models. In dmesg output it has:
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.1: Cirrus Logic CS35L41 (35a40),
Revision: B2
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: Falling back to default firmware.
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: Firmware version: 3
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1:
cirrus/cs35l41-dsp1-spk-prot.wmfw: Fri 24 Jun 2022 14:55:56 GMT Daylight Time
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: Firmware: 400a4 vendor: 0x2
v0.58.0, 2 algorithms
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: 0: ID cd v29.78.0 XM@94 YM@e
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: 1: ID f20b v0.1.0 XM@17c
YM@0
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1:
cirrus/cs35l41-dsp1-spk-prot.bin: v0.58.0
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: spk-prot:
e:\workspace\workspace\tibranch_release_playback_6.76_2\ormis\staging\default_tunings\internal\CS35L53\Fixe
d_Attenuation_Mono_48000_29.78.0\full\Fixed_Attenuation_Mono_48000_29.78.0_full.bin
[Fix]
Upstream commit c8424cf03def ("cirrus: Add CS35L41 firmware for Dell Oasis
Models").
[Test Case]
Expecting the right fw blobs are used:
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.1: Cirrus Logic CS35L41 (35a40),
Revision: B2
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: Firmware version: 3
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1:
cirrus/cs35l41-dsp1-spk-prot-10280cbd.wmfw: Fri 27 Aug 2021 14:58:19 W. Europe
Daylight Time
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: Firmware: 400a4 vendor:
0x2 v0.43.1, 2 algorithms
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: 0: ID cd v29.63.1 XM@94
YM@e
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: 1: ID f20b v0.1.0 XM@176
YM@0
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1:
cirrus/cs35l41-dsp1-spk-prot-10280cbd-spkid0.bin: v0.43.1
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: spk-prot:
C:\Users\dchunyi\Documents\Dell\Oasis\tuning\default_tuning\10280CBD_230621_V01_A01.bin
[Where problems could occur]
That's the official firmware to support this platform. No known
problem so far.
[Other Info]
While this has been available on Mantic and Noble, we only nominate Jammy for
oem-6.5.
== original bug report ==
> cs35l41-hda spi1-CSC3551:00-cs35l41-hda.1: Falling back to default
firmware.
We probably need following firmware first.
$ git show --stat c8424cf03defa4a83b8305d1af7b1321ab62
commit c8424cf03defa4a83b8305d1af7b1321ab62
Author: Stefan Binding
Date: Thu Jul 13 17:16:45 2023 +0100
cirrus: Add CS35L41 firmware for Dell Oasis Models
Signed-off-by: Stefan Binding
WHENCE | 42 ++
cirrus/cs35l41-dsp1-spk-cali-10280cbd-spkid0.bin | Bin 0 -> 1824 bytes
cirrus/cs35l41-dsp1-spk-cali-10280cbd-spkid1.bin | Bin 0 -> 1824 bytes
cirrus/cs35l41-dsp1-spk-prot-10280cbd-spkid0.bin | Bin 0 -> 3980 bytes
cirrus/cs35l41-dsp1-spk-prot-10280cbd-spkid1.bin | Bin 0 -> 3980 bytes
5 files changed, 42 insertions(+)
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ubuntu 1052 F pulseaudio
CasperMD5json:
{
"result": "skip"
}
Dependencies: firmware-sof-signed 2.0-1ubuntu4.4+exp.12 [origin: unknown]
DistributionChannelDescriptor:
# This is the distribution
[Kernel-packages] [Bug 2044158] CurrentDmesg.txt
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/2044158/+attachment/5729059/+files/CurrentDmesg.txt
--
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/2044158
Title:
Missing CS35L41 firmware for Dell Oasis Models
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-firmware source package in Jammy:
In Progress
Status in linux-firmware source package in Mantic:
Fix Released
Status in linux-firmware source package in Noble:
Fix Released
Bug description:
[SRU Justification]
[Impact]
Missing CS35L41 firmware for Dell Oasis models. In dmesg output it has:
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.1: Cirrus Logic CS35L41 (35a40),
Revision: B2
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: Falling back to default firmware.
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: Firmware version: 3
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1:
cirrus/cs35l41-dsp1-spk-prot.wmfw: Fri 24 Jun 2022 14:55:56 GMT Daylight Time
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: Firmware: 400a4 vendor: 0x2
v0.58.0, 2 algorithms
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: 0: ID cd v29.78.0 XM@94 YM@e
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: 1: ID f20b v0.1.0 XM@17c
YM@0
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1:
cirrus/cs35l41-dsp1-spk-prot.bin: v0.58.0
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: spk-prot:
e:\workspace\workspace\tibranch_release_playback_6.76_2\ormis\staging\default_tunings\internal\CS35L53\Fixe
d_Attenuation_Mono_48000_29.78.0\full\Fixed_Attenuation_Mono_48000_29.78.0_full.bin
[Fix]
Upstream commit c8424cf03def ("cirrus: Add CS35L41 firmware for Dell Oasis
Models").
[Test Case]
Expecting the right fw blobs are used:
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.1: Cirrus Logic CS35L41 (35a40),
Revision: B2
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: Firmware version: 3
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1:
cirrus/cs35l41-dsp1-spk-prot-10280cbd.wmfw: Fri 27 Aug 2021 14:58:19 W. Europe
Daylight Time
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: Firmware: 400a4 vendor:
0x2 v0.43.1, 2 algorithms
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: 0: ID cd v29.63.1 XM@94
YM@e
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: 1: ID f20b v0.1.0 XM@176
YM@0
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1:
cirrus/cs35l41-dsp1-spk-prot-10280cbd-spkid0.bin: v0.43.1
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: spk-prot:
C:\Users\dchunyi\Documents\Dell\Oasis\tuning\default_tuning\10280CBD_230621_V01_A01.bin
[Where problems could occur]
That's the official firmware to support this platform. No known
problem so far.
[Other Info]
While this has been available on Mantic and Noble, we only nominate Jammy for
oem-6.5.
== original bug report ==
> cs35l41-hda spi1-CSC3551:00-cs35l41-hda.1: Falling back to default
firmware.
We probably need following firmware first.
$ git show --stat c8424cf03defa4a83b8305d1af7b1321ab62
commit c8424cf03defa4a83b8305d1af7b1321ab62
Author: Stefan Binding
Date: Thu Jul 13 17:16:45 2023 +0100
cirrus: Add CS35L41 firmware for Dell Oasis Models
Signed-off-by: Stefan Binding
WHENCE | 42 ++
cirrus/cs35l41-dsp1-spk-cali-10280cbd-spkid0.bin | Bin 0 -> 1824 bytes
cirrus/cs35l41-dsp1-spk-cali-10280cbd-spkid1.bin | Bin 0 -> 1824 bytes
cirrus/cs35l41-dsp1-spk-prot-10280cbd-spkid0.bin | Bin 0 -> 3980 bytes
cirrus/cs35l41-dsp1-spk-prot-10280cbd-spkid1.bin | Bin 0 -> 3980 bytes
5 files changed, 42 insertions(+)
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ubuntu 1052 F pulseaudio
CasperMD5json:
{
"result": "skip"
}
Dependencies: firmware-sof-signed 2.0-1ubuntu4.4+exp.12 [origin: unknown]
DistributionChannelDescriptor:
# This is the
[Kernel-packages] [Bug 2044158] HookError_ubuntu.txt
apport information
** Attachment added: "HookError_ubuntu.txt"
https://bugs.launchpad.net/bugs/2044158/+attachment/5729060/+files/HookError_ubuntu.txt
--
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/2044158
Title:
Missing CS35L41 firmware for Dell Oasis Models
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-firmware source package in Jammy:
In Progress
Status in linux-firmware source package in Mantic:
Fix Released
Status in linux-firmware source package in Noble:
Fix Released
Bug description:
[SRU Justification]
[Impact]
Missing CS35L41 firmware for Dell Oasis models. In dmesg output it has:
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.1: Cirrus Logic CS35L41 (35a40),
Revision: B2
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: Falling back to default firmware.
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: Firmware version: 3
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1:
cirrus/cs35l41-dsp1-spk-prot.wmfw: Fri 24 Jun 2022 14:55:56 GMT Daylight Time
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: Firmware: 400a4 vendor: 0x2
v0.58.0, 2 algorithms
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: 0: ID cd v29.78.0 XM@94 YM@e
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: 1: ID f20b v0.1.0 XM@17c
YM@0
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1:
cirrus/cs35l41-dsp1-spk-prot.bin: v0.58.0
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: spk-prot:
e:\workspace\workspace\tibranch_release_playback_6.76_2\ormis\staging\default_tunings\internal\CS35L53\Fixe
d_Attenuation_Mono_48000_29.78.0\full\Fixed_Attenuation_Mono_48000_29.78.0_full.bin
[Fix]
Upstream commit c8424cf03def ("cirrus: Add CS35L41 firmware for Dell Oasis
Models").
[Test Case]
Expecting the right fw blobs are used:
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.1: Cirrus Logic CS35L41 (35a40),
Revision: B2
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: Firmware version: 3
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1:
cirrus/cs35l41-dsp1-spk-prot-10280cbd.wmfw: Fri 27 Aug 2021 14:58:19 W. Europe
Daylight Time
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: Firmware: 400a4 vendor:
0x2 v0.43.1, 2 algorithms
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: 0: ID cd v29.63.1 XM@94
YM@e
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: 1: ID f20b v0.1.0 XM@176
YM@0
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1:
cirrus/cs35l41-dsp1-spk-prot-10280cbd-spkid0.bin: v0.43.1
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: spk-prot:
C:\Users\dchunyi\Documents\Dell\Oasis\tuning\default_tuning\10280CBD_230621_V01_A01.bin
[Where problems could occur]
That's the official firmware to support this platform. No known
problem so far.
[Other Info]
While this has been available on Mantic and Noble, we only nominate Jammy for
oem-6.5.
== original bug report ==
> cs35l41-hda spi1-CSC3551:00-cs35l41-hda.1: Falling back to default
firmware.
We probably need following firmware first.
$ git show --stat c8424cf03defa4a83b8305d1af7b1321ab62
commit c8424cf03defa4a83b8305d1af7b1321ab62
Author: Stefan Binding
Date: Thu Jul 13 17:16:45 2023 +0100
cirrus: Add CS35L41 firmware for Dell Oasis Models
Signed-off-by: Stefan Binding
WHENCE | 42 ++
cirrus/cs35l41-dsp1-spk-cali-10280cbd-spkid0.bin | Bin 0 -> 1824 bytes
cirrus/cs35l41-dsp1-spk-cali-10280cbd-spkid1.bin | Bin 0 -> 1824 bytes
cirrus/cs35l41-dsp1-spk-prot-10280cbd-spkid0.bin | Bin 0 -> 3980 bytes
cirrus/cs35l41-dsp1-spk-prot-10280cbd-spkid1.bin | Bin 0 -> 3980 bytes
5 files changed, 42 insertions(+)
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ubuntu 1052 F pulseaudio
CasperMD5json:
{
"result": "skip"
}
Dependencies: firmware-sof-signed 2.0-1ubuntu4.4+exp.12 [origin: unknown]
DistributionChannelDescriptor:
# This is
[Kernel-packages] [Bug 2044158] CRDA.txt
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/2044158/+attachment/5729058/+files/CRDA.txt
--
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/2044158
Title:
Missing CS35L41 firmware for Dell Oasis Models
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-firmware source package in Jammy:
In Progress
Status in linux-firmware source package in Mantic:
Fix Released
Status in linux-firmware source package in Noble:
Fix Released
Bug description:
[SRU Justification]
[Impact]
Missing CS35L41 firmware for Dell Oasis models. In dmesg output it has:
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.1: Cirrus Logic CS35L41 (35a40),
Revision: B2
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: Falling back to default firmware.
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: Firmware version: 3
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1:
cirrus/cs35l41-dsp1-spk-prot.wmfw: Fri 24 Jun 2022 14:55:56 GMT Daylight Time
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: Firmware: 400a4 vendor: 0x2
v0.58.0, 2 algorithms
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: 0: ID cd v29.78.0 XM@94 YM@e
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: 1: ID f20b v0.1.0 XM@17c
YM@0
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1:
cirrus/cs35l41-dsp1-spk-prot.bin: v0.58.0
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: DSP1: spk-prot:
e:\workspace\workspace\tibranch_release_playback_6.76_2\ormis\staging\default_tunings\internal\CS35L53\Fixe
d_Attenuation_Mono_48000_29.78.0\full\Fixed_Attenuation_Mono_48000_29.78.0_full.bin
[Fix]
Upstream commit c8424cf03def ("cirrus: Add CS35L41 firmware for Dell Oasis
Models").
[Test Case]
Expecting the right fw blobs are used:
cs35l41-hda i2c-CSC3551:00-cs35l41-hda.1: Cirrus Logic CS35L41 (35a40),
Revision: B2
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: Firmware version: 3
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1:
cirrus/cs35l41-dsp1-spk-prot-10280cbd.wmfw: Fri 27 Aug 2021 14:58:19 W. Europe
Daylight Time
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: Firmware: 400a4 vendor:
0x2 v0.43.1, 2 algorithms
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: 0: ID cd v29.63.1 XM@94
YM@e
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: 1: ID f20b v0.1.0 XM@176
YM@0
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1:
cirrus/cs35l41-dsp1-spk-prot-10280cbd-spkid0.bin: v0.43.1
cs35l41-hda spi1-CSC3551:00-cs35l41-hda.0: DSP1: spk-prot:
C:\Users\dchunyi\Documents\Dell\Oasis\tuning\default_tuning\10280CBD_230621_V01_A01.bin
[Where problems could occur]
That's the official firmware to support this platform. No known
problem so far.
[Other Info]
While this has been available on Mantic and Noble, we only nominate Jammy for
oem-6.5.
== original bug report ==
> cs35l41-hda spi1-CSC3551:00-cs35l41-hda.1: Falling back to default
firmware.
We probably need following firmware first.
$ git show --stat c8424cf03defa4a83b8305d1af7b1321ab62
commit c8424cf03defa4a83b8305d1af7b1321ab62
Author: Stefan Binding
Date: Thu Jul 13 17:16:45 2023 +0100
cirrus: Add CS35L41 firmware for Dell Oasis Models
Signed-off-by: Stefan Binding
WHENCE | 42 ++
cirrus/cs35l41-dsp1-spk-cali-10280cbd-spkid0.bin | Bin 0 -> 1824 bytes
cirrus/cs35l41-dsp1-spk-cali-10280cbd-spkid1.bin | Bin 0 -> 1824 bytes
cirrus/cs35l41-dsp1-spk-prot-10280cbd-spkid0.bin | Bin 0 -> 3980 bytes
cirrus/cs35l41-dsp1-spk-prot-10280cbd-spkid1.bin | Bin 0 -> 3980 bytes
5 files changed, 42 insertions(+)
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ubuntu 1052 F pulseaudio
CasperMD5json:
{
"result": "skip"
}
Dependencies: firmware-sof-signed 2.0-1ubuntu4.4+exp.12 [origin: unknown]
DistributionChannelDescriptor:
# This is the distribution channel
[Kernel-packages] [Bug 2044158] Re: Missing CS35L41 firmware for Dell Oasis Models
** Changed in: linux-firmware (Ubuntu Jammy)
Status: Incomplete => In Progress
** Changed in: linux-firmware (Ubuntu Jammy)
Importance: Undecided => High
** Changed in: linux-firmware (Ubuntu Jammy)
Assignee: (unassigned) => You-Sheng Yang (vicamo)
--
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/2044158
Title:
Missing CS35L41 firmware for Dell Oasis Models
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-firmware source package in Jammy:
In Progress
Status in linux-firmware source package in Mantic:
Fix Released
Status in linux-firmware source package in Noble:
Fix Released
Bug description:
> cs35l41-hda spi1-CSC3551:00-cs35l41-hda.1: Falling back to default
firmware.
We probably need following firmware first.
$ git show --stat c8424cf03defa4a83b8305d1af7b1321ab62
commit c8424cf03defa4a83b8305d1af7b1321ab62
Author: Stefan Binding
Date: Thu Jul 13 17:16:45 2023 +0100
cirrus: Add CS35L41 firmware for Dell Oasis Models
Signed-off-by: Stefan Binding
WHENCE | 42 ++
cirrus/cs35l41-dsp1-spk-cali-10280cbd-spkid0.bin | Bin 0 -> 1824 bytes
cirrus/cs35l41-dsp1-spk-cali-10280cbd-spkid1.bin | Bin 0 -> 1824 bytes
cirrus/cs35l41-dsp1-spk-prot-10280cbd-spkid0.bin | Bin 0 -> 3980 bytes
cirrus/cs35l41-dsp1-spk-prot-10280cbd-spkid1.bin | Bin 0 -> 3980 bytes
5 files changed, 42 insertions(+)
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ubuntu 1052 F pulseaudio
CasperMD5json:
{
"result": "skip"
}
Dependencies: firmware-sof-signed 2.0-1ubuntu4.4+exp.12 [origin: unknown]
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-oddish13+X114
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2023-12-08 (5 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" -
somerville-jammy-amd64-20220504-33
IwConfig:
lono wireless extensions.
wlp85s0f0 no wireless extensions.
enx00e04c680352 no wireless extensions.
MachineType: Dell Inc. Latitude 7350
Package: linux-firmware 20220329.git681281e4-0ubuntu3.23+exp.92 [origin:
unknown]
PackageArchitecture: all
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9009-oem
root=UUID=d3612d22-9573-43a8-919c-c759faa64541 ro automatic-oem-config quiet
splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-9009.10+exp.32-oem 6.5.3
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.5.0-9009-oem N/A
linux-backports-modules-6.5.0-9009-oem N/A
linux-firmware
20220329.git681281e4-0ubuntu3.23+exp.92
Tags: jammy third-party-packages
Uname: Linux 6.5.0-9009-oem x86_64
UnreportableReason: This does not seem to be an official Ubuntu package.
Please retry after updating the indexes of available packages, if that does not
work then remove related third party packages and try again.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
dmi.bios.date: 12/08/2023
dmi.bios.release: 0.4
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 0.4.35
dmi.board.name: 0UB010
dmi.board.vendor: Dell Inc.
dmi.board.version: D02
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.ec.firmware.release: 0.0
dmi.modalias:
dmi:bvnDellInc.:bvr0.4.35:bd12/08/2023:br0.4:efr0.0:svnDellInc.:pnLatitude7350:pvr:rvnDellInc.:rn0UB010:rvrD02:cvnDellInc.:ct10:cvr:sku0CBF:
dmi.product.family: Latitude
dmi.product.name: Latitude 7350
dmi.product.sku: 0CBF
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2044158/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-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: [Ubuntu 22.04.04]: mpi3mr driver update request
Yes, it's an Ubuntu VM running on a RHEL host. It shouldn't make a difference, right? The same issue could occur on bare metal as well. -- 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: [Ubuntu 22.04.04]: mpi3mr driver update request 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: This BZ has been initiated to incorporate the mpi3mr driver from upstream into the upcoming Ubuntu releases (Ubuntu 22.04.x point releases). 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. 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 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 f762326b2baa scsi: mpi3mr: Propagate sense data for admin queue SCSI I/O 144679dfb584 scsi: mpi3mr: Fix the type used for pointers to bitmap 2a954832015d scsi: mpi3mr: Use -ENOMEM instead of -1 in mpi3mr_expander_add() 2acc635a0e5e scsi: mpi3mr: Use IRQ save variants of spinlock to protect chain frame allocation a3d27dfdcfc2 scsi: mpi3mr: Handle soft reset in progress fault code (0xF002) b85f82f3c92a scsi: mpi3mr: Declare SCSI host template const 1ea41edd88f2 scsi: mpi3mr: Update driver version to 8.4.1.0.0 e74f2fbd8b06 scsi: mpi3mr: Update copyright year 80b8fd0231d5 scsi: mpi3mr: Fix W=1 compilation warnings e5f596bc2592 scsi: mpi3mr: Update MPI Headers to revision 27 f1dec6b1e25e scsi: mpi3mr: Avoid escalating to higher level reset when target is removed 22beef38e52c scsi: mpi3mr: Modify MUR timeout value to 120 seconds 23b3d1cf1572 scsi: mpi3mr: Fix admin queue memory leak upon soft reset 3f1254ed01d0 scsi: mpi3mr: Successive VD delete and add causes FW fault ce756daa36e1 scsi: mpi3mr: Fix expander node leak in mpi3mr_remove() c798304470ca scsi: mpi3mr: Fix memory leaks in mpi3mr_init_ioc() d4caa1a4255c scsi: mpi3mr: Fix sas_hba.phy memory leak in mpi3mr_remove() d0f3c3728da8 scsi: mpi3mr: Fix mpi3mr_hba_port memory leak in mpi3mr_remove() 7d2b02172b6a scsi: mpi3mr: Fix config page DMA memory leak f305a7b6ca21 scsi: mpi3mr: Fix throttle_groups memory leak 8e45183978d6 scsi: mpi3mr: Bad drive in topology results kernel crash 4f297e856a7b scsi: mpi3mr: NVMe command size greater than 8K fails ba8a9ba41fbd scsi: mpi3mr: Return proper values for failures in firmware init path 0a319f162949 scsi: mpi3mr: Wait for diagnostic save during controller init 5b06a7169c59 scsi: mpi3mr: Driver unload crashes host when enhanced logging is enabled 02ca7da2919a scsi: mpi3mr: ioctl timeout when disabling/enabling interrupt 66b381d874fa scsi: mpi3mr: Remove unneeded version.h include e39ea831ebad scsi: mpi3mr: Fix missing mrioc->evtack_cmds initialization 339e61565f81 scsi: mpi3mr: Use number of bits to manage bitmap sizes eeb270aee3e0 scsi: mpi3mr: Remove unnecessary memcpy() to alltgt_info->dmi fb428a2005fc scsi: mpi3mr: Fix issues in mpi3mr_get_all_tgt_info() ae7d45f5283d scsi: mpi3mr: Fix an issue found by KASAN f0a43ba6c66c scsi: mpi3mr: Refer CONFIG_SCSI_MPI3MR in Makefile d347a951906b scsi: mpi3mr: Remove usage of dma_get_required_mask() API 7d21fcfb4095 scsi: mpi3mr: Suppress command reply debug prints 65244389b1b3 scsi: mpi3mr: Select CONFIG_SCSI_SAS_ATTRS c863a2dcb9b0 scsi: mpi3mr: Remove unnecessary cast f616efbee9d6 scsi: mpi3mr: Update driver version to 8.2.0.3.0 2e31be8697b1 scsi: mpi3mr: Fix scheduling while atomic type bug f84e8b5bb57e scsi: mpi3mr: Scan the devices during resume time 130fc180a481 scsi: mpi3mr: Free enclosure objects during driver unload bad2f28da625 scsi: mpi3mr: Handle 0xF003 Fault Code f2a79d2030ad scsi: mpi3mr: Graceful handling of surprise removal of PCIe HBA 7f9f953d537a scsi: mpi3mr: Schedule
[Kernel-packages] [Bug 2044158] Re: Missing CS35L41 firmware for Dell Oasis Models
Remove connections to bug 2042510, because the lack of the per platform firmware is not the root cause for it. However, it's still valuable to SRU the firmware as it's meant to be loaded for the hardware. ** Tags removed: oem-priority originate-from-2042510 somerville ** No longer affects: hwe-next -- 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/2044158 Title: Missing CS35L41 firmware for Dell Oasis Models Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: Incomplete Status in linux-firmware source package in Mantic: Fix Released Status in linux-firmware source package in Noble: Fix Released Bug description: > cs35l41-hda spi1-CSC3551:00-cs35l41-hda.1: Falling back to default firmware. We probably need following firmware first. $ git show --stat c8424cf03defa4a83b8305d1af7b1321ab62 commit c8424cf03defa4a83b8305d1af7b1321ab62 Author: Stefan Binding Date: Thu Jul 13 17:16:45 2023 +0100 cirrus: Add CS35L41 firmware for Dell Oasis Models Signed-off-by: Stefan Binding WHENCE | 42 ++ cirrus/cs35l41-dsp1-spk-cali-10280cbd-spkid0.bin | Bin 0 -> 1824 bytes cirrus/cs35l41-dsp1-spk-cali-10280cbd-spkid1.bin | Bin 0 -> 1824 bytes cirrus/cs35l41-dsp1-spk-prot-10280cbd-spkid0.bin | Bin 0 -> 3980 bytes cirrus/cs35l41-dsp1-spk-prot-10280cbd-spkid1.bin | Bin 0 -> 3980 bytes 5 files changed, 42 insertions(+) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2044158/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2043059] Re: Installation errors out when installing in a chroot
Hey Dann, This seems to work ok if I make the changes in our script. Let me propose this script change to the owners I'll get back to you. Thanks, Sam -- 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 2045205] Re: "spi-nor spi0.1:Software reset failed:-524" in shutdown screen
** Tags removed: verification-needed-jammy-linux-oem-6.5 ** Tags added: verification-done-jammy-linux-oem-6.5 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/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 2046225] Re: The eDP OLED panel has no output on MTL platform
** Tags removed: verification-needed-jammy-linux-oem-6.5 ** Tags added: verification-done-jammy-linux-oem-6.5 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2046225 Title: The eDP OLED panel has no output on MTL platform Status in linux package in Ubuntu: In Progress Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux source package in Mantic: In Progress Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: In Progress Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] We got a blank screen when boot into the system with OLED panel. [Fix] Intel provides a patch to fix this https://patchwork.freedesktop.org/patch/570622/?series=127194=2 Which is in drm-intel-next currently 3072a24c778a drm/i915: Introduce crtc_state->enhanced_framing [Test case] 1. Install Ubuntu 22.04 on the system with 6.5+ kernel 2. Check the screen display normally [Where problems could occur] The eDP panel support v1.4 and later may fail if it require the non-standard DP_LINK_BW_SET. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2046225/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2045384] Re: AppArmor patch for mq-posix interface is missing in jammy
If/when this lands in jammy 5.15 it will affect snapd-preseed status in livecd-rootfs which will need to have appropriate adjustment as well, at the same time. ** Changed in: linux (Ubuntu) Status: Incomplete => Triaged ** Also affects: livecd-rootfs (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/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 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 2042090] Re: Orchid Bay MLK2/Maya Bay MLK soundwire support
This bug is awaiting verification that the linux-oem-6.5/6.5.0-1010.11
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.5' to 'verification-done-
jammy-linux-oem-6.5'. If the problem still exists, change the tag
'verification-needed-jammy-linux-oem-6.5' to 'verification-failed-jammy-
linux-oem-6.5'.
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 removed: verification-done
** Tags added: kernel-spammed-jammy-linux-oem-6.5-v2
verification-needed-jammy-linux-oem-6.5
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/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 2038259] Re: Include QCA WWAN 4G Qualcomm SDX12 CAT12/DW5825e support
This bug is awaiting verification that the linux-oem-6.5/6.5.0-1010.11
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.5' to 'verification-done-
jammy-linux-oem-6.5'. If the problem still exists, change the tag
'verification-needed-jammy-linux-oem-6.5' to 'verification-failed-jammy-
linux-oem-6.5'.
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.5-v2
verification-needed-jammy-linux-oem-6.5
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2038259
Title:
Include QCA WWAN 4G Qualcomm SDX12 CAT12/DW5825e support
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:
Won't Fix
Status in linux-oem-6.5 source package in Jammy:
In Progress
Status in linux source package in Mantic:
Won't Fix
Status in linux-oem-6.5 source package in Mantic:
Invalid
Bug description:
[SRU Justification]
[Impact]
Missing usb serial interface for FM101R-GL.
[Fix]
* commit 52480e1f1a25 ("USB: serial: option: add Fibocom to DELL custom modem
FM101R-GL"): in v6.6-rc7
* commit a1092619dd28 ("USB: serial: option: fix FM101R-GL defines"): in
v6.7-rc3
[Test Case]
1. check lsusb & dmesg output
```
$ lsusb
Bus 004 Device 002: ID 413c:8215 Dell Computer Corp. Fibocom FM101-GL Module
...
$ sudo dmesg
[8.460678] usbcore: registered new interface driver usbserial_generic
[8.460690] usbserial: USB Serial support registered for generic
[8.549734] usbcore: registered new interface driver option
[8.550108] usbserial: USB Serial support registered for GSM modem (1-port)
[8.550266] option 4-4:1.2: GSM modem (1-port) converter detected
[8.553584] usb 4-4: GSM modem (1-port) converter now attached to ttyUSB0
[8.556445] usbcore: registered new interface driver cdc_ncm
[8.601187] usbcore: registered new interface driver cdc_wdm
[9.059744] cdc_mbim 4-4:1.0: setting rx_max = 16384
[9.060079] cdc_mbim 4-4:1.0: cdc-wdm0: USB WDM device
[9.060338] wwan wwan0: port wwan0mbim0 attached
```
2. make sure ModemManager has probed it:
```
$ mmcli -L
/org/freedesktop/ModemManager1/Modem/0 [Fibocom Wireless Inc.] Fibocom
FM101-GL Module
```
[Where problems could occur]
New hardware, still under development. Maybe we'll have to
enable/patch for its vendor specific interface or so.
[Other Info]
The first patch is available for v6.6, and the second for v6.7. While
we're enabling it on linux-oem-6.5/jammy, nominate for linux/noble,
which is currently on v6.6, and linux-oem-6.5.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2038259/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2043964] Re: New China SRRC compliance readiness check for Realtek WLAN
This bug is awaiting verification that the linux-oem-6.5/6.5.0-1010.11 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.5' to 'verification-done- jammy-linux-oem-6.5'. If the problem still exists, change the tag 'verification-needed-jammy-linux-oem-6.5' to 'verification-failed-jammy- linux-oem-6.5'. 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.5-v2 verification-needed-jammy-linux-oem-6.5 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2043964 Title: New China SRRC compliance readiness check for Realtek WLAN 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: Won't Fix Status in linux-oem-6.5 source package in Jammy: In Progress Status in linux source package in Noble: In Progress Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [SRU Justification] BugLink: https://bugs.launchpad.net/bugs/2043964 [Impact] SRRC (State Radio Regulation of China) compliance readiness check for Realtek WLAN. [Fix] Capability for Realtek WiFi TX power tables load and report from RFE (RF front end) parameters is needed. Multiple commits from vanilla kernel. [Test Case] ``` $ sudo iw reg set CN # manually connect to 5G ap : center channel 155 bw 80 M $ sudo cat /sys/kernel/debug/ieee80211/phy0/rtw89/txpwr_table | grep -E 'MCS_2TX_80M_0|Regulatory' ``` The expected output s ``` Regulatory: CN MCS_2TX_80M_0 - NON_BF BF | 10, 9, dbm ``` And verification fail output: ``` Regulatory: CN MCS_2TX_80M_0 - NON_BF BF | 15, 10, dbm ``` [Where problems could occur] This updates the behaviors and constraints of radio device power transmission for rtw89 driver, and must be done for regulatory compliance. [Other Info] As needed for oem-6.5/jammy, nominate only for Noble and oem-6.5/jammy. == original bug report == New China SRRC compliance readiness check Proposed Change: - China SRRC updates the testing requirement for 2.4/5GHz, the major changes are the in-band RSE limit, and EIRP limits. - The SRRC updates impact both WLAN modules and platforms. The WLAN modules need to complete the new SRRC testing then platform can start to apply / renew the new SRRC cert. If platform took several WLAN modules but not all of the modules have completed the new SRRC testing updates, platform cannot renew/apply the new SRRC cert. - The platforms which apply/renew SRRC new standards need to ensure the TX power can meet the new RSE/EIRP limits. IHV confirmed below driver version can support these requirements. Realtek: The upstream driver can support SRRC compliance. https://lore.kernel.org/linux-wireless/20230927072156.26336-1-pks...@realtek.com/T/#m4d8acb2697ff2bc07485a6119839e1f96a822340 [lore.kernel.org] To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2043964/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
This bug is awaiting verification that the linux-oem-6.5/6.5.0-1010.11 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.5' to 'verification-done- jammy-linux-oem-6.5'. If the problem still exists, change the tag 'verification-needed-jammy-linux-oem-6.5' to 'verification-failed-jammy- linux-oem-6.5'. 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.5-v2 verification-needed-jammy-linux-oem-6.5 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/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 2045205] Re: "spi-nor spi0.1:Software reset failed:-524" in shutdown screen
This bug is awaiting verification that the linux-oem-6.5/6.5.0-1010.11 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.5' to 'verification-done- jammy-linux-oem-6.5'. If the problem still exists, change the tag 'verification-needed-jammy-linux-oem-6.5' to 'verification-failed-jammy- linux-oem-6.5'. 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.5-v2 verification-needed-jammy-linux-oem-6.5 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/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 2046225] Re: The eDP OLED panel has no output on MTL platform
This bug is awaiting verification that the linux-oem-6.5/6.5.0-1010.11 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.5' to 'verification-done- jammy-linux-oem-6.5'. If the problem still exists, change the tag 'verification-needed-jammy-linux-oem-6.5' to 'verification-failed-jammy- linux-oem-6.5'. 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.5-v2 verification-needed-jammy-linux-oem-6.5 -- 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/2046225 Title: The eDP OLED panel has no output on MTL platform Status in linux package in Ubuntu: In Progress Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux source package in Mantic: In Progress Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: In Progress Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] We got a blank screen when boot into the system with OLED panel. [Fix] Intel provides a patch to fix this https://patchwork.freedesktop.org/patch/570622/?series=127194=2 Which is in drm-intel-next currently 3072a24c778a drm/i915: Introduce crtc_state->enhanced_framing [Test case] 1. Install Ubuntu 22.04 on the system with 6.5+ kernel 2. Check the screen display normally [Where problems could occur] The eDP panel support v1.4 and later may fail if it require the non-standard DP_LINK_BW_SET. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2046225/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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.5/6.5.0-1010.11
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.5' to 'verification-done-
jammy-linux-oem-6.5'. If the problem still exists, change the tag
'verification-needed-jammy-linux-oem-6.5' to 'verification-failed-jammy-
linux-oem-6.5'.
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.5-v2
verification-needed-jammy-linux-oem-6.5
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/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 2046105] Re: Sound: Add rtl quirk of M90-Gen5
This bug is awaiting verification that the linux-oem-6.5/6.5.0-1010.11 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.5' to 'verification-done- jammy-linux-oem-6.5'. If the problem still exists, change the tag 'verification-needed-jammy-linux-oem-6.5' to 'verification-failed-jammy- linux-oem-6.5'. 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.5-v2 verification-needed-jammy-linux-oem-6.5 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/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 2046315] Re: oem-6.5: disable psr2 for some panels according to edid
This bug is awaiting verification that the linux-oem-6.5/6.5.0-1010.11 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.5' to 'verification-done- jammy-linux-oem-6.5'. If the problem still exists, change the tag 'verification-needed-jammy-linux-oem-6.5' to 'verification-failed-jammy- linux-oem-6.5'. 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.5-v2 verification-needed-jammy-linux-oem-6.5 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2046315 Title: oem-6.5: disable psr2 for some panels according to edid Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: New Status in linux-oem-6.5 source package in Jammy: New Bug description: BugLink: https://bugs.launchpad.net/bugs/2046315 [Impact] On serveral Dell laptops, the screen often displays garbage or the screen is flicking [Fix] There is no real fix so far, ODM recommends to use a workaround to disable PSR2, this is a temp solution, after we get the real fix, we could revert the temp workaround. [Test case] booting with the patched kernel, If the pannel's edid is in the qurik list, the PSR2 will be disabled (checking /sys/kernel/debug/dri/0/i915_edp_psr_status; if the pannel's edid is not in the quirk list, the graphic driver will work as before. [Where problems could occur] It is possible that the temp solution couldn't work, then the screen will still show garbage and the screen is flicking, another possible regression is the screen has no problem before, but after running patched kernel, the PSR2 is disabled and the system cost more power, but this possibility is very low, I tested the patched on some dell machines, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2046315/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2016040] Re: Creating bcache backing device using a Dell Ent NVMe CM6 MU 6.4TB storage fails with "cannot allocate memory" error
@noahmehl do you have an environment you can test with? If you can confirm the patch I linked works, I can work towards getting into the GA ubuntu kernels. I built test packages including the patch based on latest ubuntu 22.04 kernels (regular and hwe) here: https://launchpad.net/~rafael.lopez/+archive/ubuntu/bcache-lp2016040 You can try these by adding repo: sudo add-apt-repository ppa:rafael.lopez/bcache-lp2016040 Regular: sudo apt install linux-image-unsigned-5.15.0-91-generic HWE: sudo apt install linux-image-unsigned-6.2.0-39-generic NOTE - since these are unsigned test kernels, you may need to disable secure boot to be able to boot them. I also strongly discourage using these packages in a production setting or critical environment, it is strictly for test purposes. -- 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/2016040 Title: Creating bcache backing device using a Dell Ent NVMe CM6 MU 6.4TB storage fails with "cannot allocate memory" error Status in linux package in Ubuntu: Confirmed Bug description: # make-bcache -B /dev/nvme4n1 UUID: 569e90b3-cc2a-4a0e-a201-476c426a2141 Set UUID: d8d8458a-01df-481e-a7dc-e75843a9608f version:1 block_size: 1 data_offset:16 kern.log: Apr 12 18:21:56 ... kernel: [ 723.854659] bcache: register_bdev() error nvme4n1: cannot allocate memory Apr 12 18:21:56 ... kernel: [ 723.854662] bcache: register_bdev_worker() error /dev/nvme4n1: fail to register backing device Same error message is mentioned in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909518, but the suggested configuration change does not fix the issue: # nvme id-ns /dev/nvme4n1 -n 1 -H |grep "LBA Format" [3:0] : 0x3 Current LBA Format Selected LBA Format 0 : Metadata Size: 0 bytes - Data Size: 512 bytes - Relative Performance: 0 Best LBA Format 1 : Metadata Size: 8 bytes - Data Size: 512 bytes - Relative Performance: 0 Best LBA Format 2 : Metadata Size: 0 bytes - Data Size: 1 bytes - Relative Performance: 0 Best LBA Format 3 : Metadata Size: 0 bytes - Data Size: 4096 bytes - Relative Performance: 0 Best (in use) LBA Format 4 : Metadata Size: 8 bytes - Data Size: 4096 bytes - Relative Performance: 0 Best LBA Format 5 : Metadata Size: 64 bytes - Data Size: 4096 bytes - Relative Performance: 0 Best Using a Dell Ent NVMe P5800x WI U.2 400GB storage works as expected: # make-bcache -B /dev/nvme2n1 UUID: b1405a6d-8732-4175-8aba-d67be23b3ff0 Set UUID: af6b190f-a57e-4f2b-926e-904a95268390 version:1 block_size: 8 data_offset:16 # lsblk NAMEMAJ:MIN RM SIZE RO TYPE MOUNTPOINTS ... nvme2n1 259:10 372.6G 0 disk └─bcache0 252:00 372.6G 0 disk ... kern.log: Apr 12 18:47:33 ... kernel: [ 2261.135332] bcache: register_bdev() registered backing device nvme2n1 Kernel versions tested: 5.19.0-38-generic #39~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC 5.15.0-69-generic #76-Ubuntu SMP --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 12 18:10 seq crw-rw 1 root audio 116, 33 Apr 12 18:10 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Dell Inc. PowerEdge R7525 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic root=UUID=3c0a9c0d-3f5d-4d4d-a571-37298c70a1a3 ro ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-38-generic N/A linux-backports-modules-5.19.0-38-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.12 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: jammy uec-images Uname: Linux 5.19.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 10/25/2022 dmi.bios.release: 2.10 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.10.2 dmi.board.name: 03WYW4 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias:
[Kernel-packages] [Bug 2045969] Re: package linux-image-6.2.0-39-generic 6.2.0-39.40 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
Hello FACELLO, a few thoughts: This bug is specifically due to these log messages. Try installing the packages that the error messages have identified: make -j12 KERNELRELEASE=6.2.0-37-generic all INCLUDEDIR=/lib/modules/6.2.0-37-generic/build/include KVERSION=6.2.0-37-generic DKMS_BUILD=1...(bad exit status: 2) ERROR (dkms apport): binary package for evdi: 1.9.1 not found Error! Bad return status for module build on kernel: 6.2.0-37-generic (x86_64) Consult /var/lib/dkms/evdi/1.9.1/build/make.log for more information. dkms autoinstall on 6.2.0-37-generic/x86_64 succeeded for broadcom-sta broadcom-sta broadcom-sta evdi evdi nvidia nvidia dkms autoinstall on 6.2.0-37-generic/x86_64 failed for evdi(10) Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. * dkms: autoinstall for kernel 6.2.0-37-generic ...fail! run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 dpkg: error processing package linux-image-6.2.0-37-generic (--configure): installed linux-image-6.2.0-37-generic package post-installation script subprocess returned error exit status 1 Processing triggers for linux-image-6.2.0-39-generic (6.2.0-39.40) ... /etc/kernel/postinst.d/dkms: * dkms: running auto installation service for kernel 6.2.0-39-generic Sign command: /usr/bin/kmodsign Signing key: /var/lib/shim-signed/mok/MOK.priv Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der Error! Your kernel headers for kernel 6.2.0-39-generic cannot be found at /lib/modules/6.2.0-39-generic/build or /lib/modules/6.2.0-39-generic/source. Please install the linux-headers-6.2.0-39-generic package or use the --kernelsourcedir option to tell DKMS where it's located. Sign command: /usr/bin/kmodsign Signing key: /var/lib/shim-signed/mok/MOK.priv Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der Error! Your kernel headers for kernel 6.2.0-39-generic cannot be found at /lib/modules/6.2.0-39-generic/build or /lib/modules/6.2.0-39-generic/source. Please install the linux-headers-6.2.0-39-generic package or use the --kernelsourcedir option to tell DKMS where it's located. Sign command: /usr/bin/kmodsign Signing key: /var/lib/shim-signed/mok/MOK.priv Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der Error! Your kernel headers for kernel 6.2.0-39-generic cannot be found at /lib/modules/6.2.0-39-generic/build or /lib/modules/6.2.0-39-generic/source. Please install the linux-headers-6.2.0-39-generic package or use the --kernelsourcedir option to tell DKMS where it's located. dkms autoinstall on 6.2.0-39-generic/x86_64 failed for broadcom-sta(1) evdi(1) nvidia(1) Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. * dkms: autoinstall for kernel 6.2.0-39-generic ...fail! Furthermore, there's a significant number of lines like this in your logs: [ 77.606362] usb 3-1.5: reset high-speed USB device number 4 using xhci_hcd [ 79.078931] usb 3-1.5: reset high-speed USB device number 4 using xhci_hcd [ 80.551609] usb 3-1.5: reset high-speed USB device number 4 using xhci_hcd There's lots of potential reasons for these messages: insufficient power to a motherboard, or hubs, or devices, or poor cables, and probably more reasons I can't think of. You should investigate the cause of these messages. If you're completely lost, try asking for help on https://askubuntu.com/. Thanks -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/2045969 Title: package linux-image-6.2.0-39-generic 6.2.0-39.40 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 Status in linux-signed package in Ubuntu: New Bug description: I don't kno why my computer is blocked just 15 s afeter start up ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-39-generic 6.2.0-39.40 ProcVersionSignature: Ubuntu 6.2.0-32.32-generic 6.2.16 Uname: Linux 6.2.0-32-generic x86_64 NonfreeKernelModules: wl nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2.1 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass Date: Fri Dec 8 12:03:31 2023 DpkgHistoryLog: Start-Date: 2023-12-08 12:03:21 Commandline: /usr/bin/unattended-upgrade Install: linux-signatures-nvidia-6.2.0-39-generic:amd64 (6.2.0-39.40, automatic), linux-modules-6.2.0-39-generic:amd64 (6.2.0-39.40, automatic), linux-modules-nvidia-525-6.2.0-39-generic:amd64 (6.2.0-39.40, automatic), linux-image-6.2.0-39-generic:amd64 (6.2.0-39.40, automatic), linux-objects-nvidia-525-6.2.0-39-generic:amd64 (6.2.0-39.40, automatic) Upgrade: linux-modules-nvidia-525-generic-hwe-22.04:amd64 (6.2.0-37.38+1, 6.2.0-39.40), linux-modules-nvidia-510-generic-hwe-22.04:amd64 (6.2.0-37.38+1, 6.2.0-39.40), linux-libc-dev:amd64 (6.2.0-37.38, 6.2.0-39.40) ErrorMessage: installed
[Kernel-packages] [Bug 2045969] Re: package linux-image-6.2.0-39-generic 6.2.0-39.40 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/2045969 Title: package linux-image-6.2.0-39-generic 6.2.0-39.40 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 Status in linux-signed package in Ubuntu: New Bug description: I don't kno why my computer is blocked just 15 s afeter start up ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-39-generic 6.2.0-39.40 ProcVersionSignature: Ubuntu 6.2.0-32.32-generic 6.2.16 Uname: Linux 6.2.0-32-generic x86_64 NonfreeKernelModules: wl nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2.1 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass Date: Fri Dec 8 12:03:31 2023 DpkgHistoryLog: Start-Date: 2023-12-08 12:03:21 Commandline: /usr/bin/unattended-upgrade Install: linux-signatures-nvidia-6.2.0-39-generic:amd64 (6.2.0-39.40, automatic), linux-modules-6.2.0-39-generic:amd64 (6.2.0-39.40, automatic), linux-modules-nvidia-525-6.2.0-39-generic:amd64 (6.2.0-39.40, automatic), linux-image-6.2.0-39-generic:amd64 (6.2.0-39.40, automatic), linux-objects-nvidia-525-6.2.0-39-generic:amd64 (6.2.0-39.40, automatic) Upgrade: linux-modules-nvidia-525-generic-hwe-22.04:amd64 (6.2.0-37.38+1, 6.2.0-39.40), linux-modules-nvidia-510-generic-hwe-22.04:amd64 (6.2.0-37.38+1, 6.2.0-39.40), linux-libc-dev:amd64 (6.2.0-37.38, 6.2.0-39.40) ErrorMessage: installed linux-image-6.2.0-39-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2022-10-31 (403 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: ASUSTeK COMPUTER INC. ASUS TUF Gaming A17 FA706ICB_TUF706ICB ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-32-generic root=UUID=8e316101-89cb-4820-a4b4-a076b22a5c2c ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.11, Python 3.11.4, python3-minimal, 3.11.2-1 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.06-2ubuntu16 SourcePackage: linux-signed Title: package linux-image-6.2.0-39-generic 6.2.0-39.40 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/11/2022 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FA706ICB.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: FA706ICB dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.2 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFA706ICB.304:bd04/11/2022:br5.16:efr3.2:svnASUSTeKCOMPUTERINC.:pnASUSTUFGamingA17FA706ICB_TUF706ICB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFA706ICB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ASUS TUF Gaming A17 dmi.product.name: ASUS TUF Gaming A17 FA706ICB_TUF706ICB dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/2045969/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038675] Re: mana: Fix some TX processing bugs (CQE Errors , TS0 Bytes, SGe0 GS0 Packet)
This bug was fixed in the package linux-azure - 6.5.0-1010.10 --- linux-azure (6.5.0-1010.10) mantic; urgency=medium * mantic/linux-azure: 6.5.0-1010.10 -proposed tracker (LP: #2041528) * Packaging resync (LP: #1786013) - [Packaging] resync update-dkms-versions helper - debian/dkms-versions -- update from kernel-versions (main/2023.10.30) * Azure: Improve SQL DB latency (LP: #2040300) - tcp: Set pingpong threshold via sysctl * mana: Fix some TX processing bugs (CQE Errors , TS0 Bytes, SGe0 GS0 Packet) (LP: #2038675) - net: mana: Fix TX CQE error handling - net: mana: Fix the tso_bytes calculation - net: mana: Fix oversized sge0 for GSO packets [ Ubuntu: 6.5.0-14.14 ] * mantic/linux: 6.5.0-14.14 -proposed tracker (LP: #2042660) * Boot log print hang on screen, no login prompt on Aspeed 2600 rev 52 BMC (LP: #2042850) - drm/ast: Add BMC virtual connector * arm64 atomic issues cause disk corruption (LP: #2042573) - locking/atomic: scripts: fix fallback ifdeffery * Packaging resync (LP: #1786013) - [Packaging] update annotations scripts [ Ubuntu: 6.5.0-12.12 ] * mantic/linux: 6.5.0-12.12 -proposed tracker (LP: #2041536) * Packaging resync (LP: #1786013) - [Packaging] update annotations scripts - [Packaging] update helper scripts - debian/dkms-versions -- update from kernel-versions (main/2023.10.30) * CVE-2023-5633 - drm/vmwgfx: Keep a gem reference to user bos in surfaces * CVE-2023-5345 - fs/smb/client: Reset password pointer to NULL * CVE-2023-39189 - netfilter: nfnetlink_osf: avoid OOB read * CVE-2023-4244 - netfilter: nft_set_rbtree: skip sync GC for new elements in this transaction * apparmor restricts read access of user namespace mediation sysctls to root (LP: #2040194) - SAUCE: apparmor: open userns related sysctl so lxc can check if restriction are in place * AppArmor spams kernel log with assert when auditing (LP: #2040192) - SAUCE: apparmor: fix request field from a prompt reply that denies all access * apparmor notification files verification (LP: #2040250) - SAUCE: apparmor: fix notification header size * apparmor oops when racing to retrieve a notification (LP: #2040245) - SAUCE: apparmor: fix oops when racing to retrieve notification * SMC stats: Wrong bucket calculation for payload of exactly 4096 bytes (LP: #2039575) - net/smc: Fix pos miscalculation in statistics * Support mipi camera on Intel Meteor Lake platform (LP: #2031412) - SAUCE: iommu: intel-ipu: use IOMMU passthrough mode for Intel IPUs on Meteor Lake - SAUCE: platform/x86: int3472: Add handshake GPIO function * CVE-2023-45898 - ext4: fix slab-use-after-free in ext4_es_insert_extent() * CVE-2023-31085 - ubi: Refuse attaching if mtd's erasesize is 0 * CVE-2023-5717 - perf: Disallow mis-matched inherited group reads * CVE-2023-5178 - nvmet-tcp: Fix a possible UAF in queue intialization setup * CVE-2023-5158 - vringh: don't use vringh_kiov_advance() in vringh_iov_xfer() * CVE-2023-5090 - x86: KVM: SVM: always update the x2avic msr interception * [SRU][J/L/M] UBUNTU: [Packaging] Make WWAN driver a loadable module (LP: #2033406) - [Packaging] Make WWAN driver loadable modules * Unable to power off the system with MTL CPU (LP: #2039405) - Revert "x86/smp: Put CPUs into INIT on shutdown if possible" * usbip: error: failed to open /usr/share/hwdata//usb.ids (LP: #2039439) - [Packaging] Make linux-tools-common depend on hwdata * drop all references to is_rust_module.sh in kernels >= 6.5 (LP: #2038611) - [Packaging] drop references to is_rust_module.sh * disable shiftfs (LP: #2038522) - SAUCE: ceph: enable unsafe idmapped mounts by default - [Config] disable shiftfs * Infinite systemd loop when power off the machine with multiple MD RAIDs (LP: #2036184) - md: Put the right device in md_seq_next * [Mediatek] mt8195-demo: enable CONFIG_MTK_IOMMU as module for multimedia and PCIE peripherals (LP: #2036587) - [Config] Enable CONFIG_MTK_IOMMU on arm64 * Realtek 8852CE WiFi 6E country code udpates (LP: #2037273) - wifi: rtw89: regd: update regulatory map to R64-R43 * Unable to use nvme drive to install Ubuntu 23.10 (LP: #2040157) - misc: rtsx: Fix some platforms can not boot and move the l1ss judgment to probe * CVE-2023-42754 - ipv4: fix null-deref in ipv4_link_failure * linux-*: please enable dm-verity kconfigs to allow MoK/db verified root images (LP: #2019040) - [Config] CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG_SECONDARY_KEYRING=y * Fix RCU warning on AMD laptops (LP: #2036377) - power: supply: core: Use blocking_notifier_call_chain to avoid RCU complaint * allow io_uring to be disabled in runtime (LP: #2035116) - io_uring: add a sysctl to disable io_uring system-wide * Fix unstable audio at low levels on Thinkpad
[Kernel-packages] [Bug 2040300] Re: Azure: Improve SQL DB latency
This bug was fixed in the package linux-azure - 6.5.0-1010.10 --- linux-azure (6.5.0-1010.10) mantic; urgency=medium * mantic/linux-azure: 6.5.0-1010.10 -proposed tracker (LP: #2041528) * Packaging resync (LP: #1786013) - [Packaging] resync update-dkms-versions helper - debian/dkms-versions -- update from kernel-versions (main/2023.10.30) * Azure: Improve SQL DB latency (LP: #2040300) - tcp: Set pingpong threshold via sysctl * mana: Fix some TX processing bugs (CQE Errors , TS0 Bytes, SGe0 GS0 Packet) (LP: #2038675) - net: mana: Fix TX CQE error handling - net: mana: Fix the tso_bytes calculation - net: mana: Fix oversized sge0 for GSO packets [ Ubuntu: 6.5.0-14.14 ] * mantic/linux: 6.5.0-14.14 -proposed tracker (LP: #2042660) * Boot log print hang on screen, no login prompt on Aspeed 2600 rev 52 BMC (LP: #2042850) - drm/ast: Add BMC virtual connector * arm64 atomic issues cause disk corruption (LP: #2042573) - locking/atomic: scripts: fix fallback ifdeffery * Packaging resync (LP: #1786013) - [Packaging] update annotations scripts [ Ubuntu: 6.5.0-12.12 ] * mantic/linux: 6.5.0-12.12 -proposed tracker (LP: #2041536) * Packaging resync (LP: #1786013) - [Packaging] update annotations scripts - [Packaging] update helper scripts - debian/dkms-versions -- update from kernel-versions (main/2023.10.30) * CVE-2023-5633 - drm/vmwgfx: Keep a gem reference to user bos in surfaces * CVE-2023-5345 - fs/smb/client: Reset password pointer to NULL * CVE-2023-39189 - netfilter: nfnetlink_osf: avoid OOB read * CVE-2023-4244 - netfilter: nft_set_rbtree: skip sync GC for new elements in this transaction * apparmor restricts read access of user namespace mediation sysctls to root (LP: #2040194) - SAUCE: apparmor: open userns related sysctl so lxc can check if restriction are in place * AppArmor spams kernel log with assert when auditing (LP: #2040192) - SAUCE: apparmor: fix request field from a prompt reply that denies all access * apparmor notification files verification (LP: #2040250) - SAUCE: apparmor: fix notification header size * apparmor oops when racing to retrieve a notification (LP: #2040245) - SAUCE: apparmor: fix oops when racing to retrieve notification * SMC stats: Wrong bucket calculation for payload of exactly 4096 bytes (LP: #2039575) - net/smc: Fix pos miscalculation in statistics * Support mipi camera on Intel Meteor Lake platform (LP: #2031412) - SAUCE: iommu: intel-ipu: use IOMMU passthrough mode for Intel IPUs on Meteor Lake - SAUCE: platform/x86: int3472: Add handshake GPIO function * CVE-2023-45898 - ext4: fix slab-use-after-free in ext4_es_insert_extent() * CVE-2023-31085 - ubi: Refuse attaching if mtd's erasesize is 0 * CVE-2023-5717 - perf: Disallow mis-matched inherited group reads * CVE-2023-5178 - nvmet-tcp: Fix a possible UAF in queue intialization setup * CVE-2023-5158 - vringh: don't use vringh_kiov_advance() in vringh_iov_xfer() * CVE-2023-5090 - x86: KVM: SVM: always update the x2avic msr interception * [SRU][J/L/M] UBUNTU: [Packaging] Make WWAN driver a loadable module (LP: #2033406) - [Packaging] Make WWAN driver loadable modules * Unable to power off the system with MTL CPU (LP: #2039405) - Revert "x86/smp: Put CPUs into INIT on shutdown if possible" * usbip: error: failed to open /usr/share/hwdata//usb.ids (LP: #2039439) - [Packaging] Make linux-tools-common depend on hwdata * drop all references to is_rust_module.sh in kernels >= 6.5 (LP: #2038611) - [Packaging] drop references to is_rust_module.sh * disable shiftfs (LP: #2038522) - SAUCE: ceph: enable unsafe idmapped mounts by default - [Config] disable shiftfs * Infinite systemd loop when power off the machine with multiple MD RAIDs (LP: #2036184) - md: Put the right device in md_seq_next * [Mediatek] mt8195-demo: enable CONFIG_MTK_IOMMU as module for multimedia and PCIE peripherals (LP: #2036587) - [Config] Enable CONFIG_MTK_IOMMU on arm64 * Realtek 8852CE WiFi 6E country code udpates (LP: #2037273) - wifi: rtw89: regd: update regulatory map to R64-R43 * Unable to use nvme drive to install Ubuntu 23.10 (LP: #2040157) - misc: rtsx: Fix some platforms can not boot and move the l1ss judgment to probe * CVE-2023-42754 - ipv4: fix null-deref in ipv4_link_failure * linux-*: please enable dm-verity kconfigs to allow MoK/db verified root images (LP: #2019040) - [Config] CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG_SECONDARY_KEYRING=y * Fix RCU warning on AMD laptops (LP: #2036377) - power: supply: core: Use blocking_notifier_call_chain to avoid RCU complaint * allow io_uring to be disabled in runtime (LP: #2035116) - io_uring: add a sysctl to disable io_uring system-wide * Fix unstable audio at low levels on Thinkpad
Re: [Kernel-packages] [Bug 2045233] Re: [Ubuntu 22.04.04]: mpi3mr driver update request
Does that warning appear on bare metal running ubuntu, or on a ubuntu vm on an ubuntu host? This appears to be on an ubuntu VM running on a RHEL host? Hardware name: Red Hat KVM/RHEL, BIOS 1.16.1-1.el9 04/01/2014 On Wed, Dec 13, 2023 at 1:25 PM Chandrakanth Patil < 2045...@bugs.launchpad.net> wrote: > This warning will not appear in the 22.04.2 kernel. Maybe UBSAN enabled > in this kernel leads to this warning. > > Note: This is just a warning and there is no functional impact. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/2045233 > > Title: > [Ubuntu 22.04.04]: mpi3mr driver update request > > 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: > This BZ has been initiated to incorporate the mpi3mr driver from > upstream into the upcoming Ubuntu > releases (Ubuntu 22.04.x point releases). 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. > > 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 > 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 > f762326b2baa scsi: mpi3mr: Propagate sense data for admin queue SCSI I/O > 144679dfb584 scsi: mpi3mr: Fix the type used for pointers to bitmap > 2a954832015d scsi: mpi3mr: Use -ENOMEM instead of -1 in > mpi3mr_expander_add() > 2acc635a0e5e scsi: mpi3mr: Use IRQ save variants of spinlock to protect > chain frame allocation > a3d27dfdcfc2 scsi: mpi3mr: Handle soft reset in progress fault code > (0xF002) > b85f82f3c92a scsi: mpi3mr: Declare SCSI host template const > 1ea41edd88f2 scsi: mpi3mr: Update driver version to 8.4.1.0.0 > e74f2fbd8b06 scsi: mpi3mr: Update copyright year > 80b8fd0231d5 scsi: mpi3mr: Fix W=1 compilation warnings > e5f596bc2592 scsi: mpi3mr: Update MPI Headers to revision 27 > f1dec6b1e25e scsi: mpi3mr: Avoid escalating to higher level reset when > target is removed > 22beef38e52c scsi: mpi3mr: Modify MUR timeout value to 120 seconds > 23b3d1cf1572 scsi: mpi3mr: Fix admin queue memory leak upon soft reset > 3f1254ed01d0 scsi: mpi3mr: Successive VD delete and add causes FW fault > ce756daa36e1 scsi: mpi3mr: Fix expander node leak in mpi3mr_remove() > c798304470ca scsi: mpi3mr: Fix memory leaks in mpi3mr_init_ioc() > d4caa1a4255c scsi: mpi3mr: Fix sas_hba.phy memory leak in mpi3mr_remove() > d0f3c3728da8 scsi: mpi3mr: Fix mpi3mr_hba_port memory leak in > mpi3mr_remove() > 7d2b02172b6a scsi: mpi3mr: Fix config page DMA memory leak > f305a7b6ca21 scsi: mpi3mr: Fix throttle_groups memory leak > 8e45183978d6 scsi: mpi3mr: Bad drive in topology results kernel crash > 4f297e856a7b scsi: mpi3mr: NVMe command size greater than 8K fails > ba8a9ba41fbd scsi: mpi3mr: Return proper values for failures in firmware > init path > 0a319f162949 scsi: mpi3mr: Wait for diagnostic save during controller > init > 5b06a7169c59 scsi: mpi3mr: Driver unload crashes host when enhanced > logging is enabled > 02ca7da2919a scsi: mpi3mr: ioctl timeout when disabling/enabling > interrupt > 66b381d874fa scsi: mpi3mr: Remove unneeded version.h include > e39ea831ebad scsi: mpi3mr: Fix missing mrioc->evtack_cmds initialization > 339e61565f81 scsi: mpi3mr: Use number of bits to manage bitmap sizes > eeb270aee3e0 scsi: mpi3mr: Remove unnecessary memcpy() to > alltgt_info->dmi > fb428a2005fc scsi: mpi3mr: Fix issues in mpi3mr_get_all_tgt_info() > ae7d45f5283d scsi: mpi3mr: Fix an issue found by KASAN > f0a43ba6c66c scsi: mpi3mr: Refer CONFIG_SCSI_MPI3MR in Makefile > d347a951906b scsi: mpi3mr: Remove usage of dma_get_required_mask() API > 7d21fcfb4095 scsi: mpi3mr: Suppress command reply debug prints > 65244389b1b3 scsi: mpi3mr: Select CONFIG_SCSI_SAS_ATTRS >
[Kernel-packages] [Bug 2044657] Re: Multiple data corruption issues in zfs
Hi. Will there be a 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 2046082] Re: zed.rc: typo in option ZED_POWER_OFF_ENCLO*US*RE_SLOT_ON_FAULT
I will stage this to mantic with an upload + block-proposed-mantic tag.
The mantic unapproved queue already has zfs-linux 2.2.2-0ubuntu1~23.10,
but it seems it is not going to be accepted per bug 2044657 comment 46.
If that bug gets cherry-pick fixes as requested, that should be simple
to combine with the staged upload. Or if the full upstream backport to
2.2.2 (from 2.2.0) is accepted there, I am happy to re-upload with it.
Attaching the debdiff for reference.
** Patch added: "lp2046082_zfs-linux_mantic_2.2.0.debdiff"
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2046082/+attachment/5728907/+files/lp2046082_zfs-linux_mantic_2.2.0.debdiff
** Tags added: block-proposed-mantic
--
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/2046082
Title:
zed.rc: typo in option ZED_POWER_OFF_ENCLO*US*RE_SLOT_ON_FAULT
Status in zfs-linux package in Ubuntu:
Fix Released
Status in zfs-linux source package in Mantic:
Confirmed
Status in zfs-linux source package in Noble:
Fix Released
Bug description:
[Impact]
* There's a typo in user-visible option (/etc/zfs/zed.d/zed.rc)
ZED_POWER_OFF_ENCLO*US*RE_SLOT_ON_FAULT introduced upstream
in 2.2.0-rc4 and SRU-ed to Mantic with 2.2.0-0ubuntu1~23.10.
* This could be fixed in Ubuntu before users start adopting it.
[Test Plan]
* Check whether /etc/zfs/zed.d/zed.rc ships the correct option.
* Actual:
$ grep ZED_POWER_OFF_ENCLO /etc/zfs/zed.d/zed.rc
#ZED_POWER_OFF_ENCLOUSRE_SLOT_ON_FAULT=1
* Expected:
$ grep ZED_POWER_OFF_ENCLO /etc/zfs/zed.d/zed.rc
#ZED_POWER_OFF_ENCLOSURE_SLOT_ON_FAULT=1
[Regression Potential]
* Users of Mantic who upgraded to zfs-linux 2.2.0-0ubuntu1~23.10
(published to mantic-updates on 2023-12-08) _and_ enabled the
option (with typo) would have such functionality disabled.
[Other Info]
* This option (with typo) was introduced in commit d19304ffeec5
("zed: Add zedlet to power off slot when drive is faulted"),
and is present in:
- ZFS 2.2: zfs-2.2.0-rc4 (mantic-updates)
- ZFS 2.1: zfs-2.1.13
* It affects Ubuntu Noble and Mantic, but not Lunar or older.
* Fixed upstream with commit 3c7650491b9a ("zed: fix typo in
variable ZED_POWER_OFF_ENCLO*US*RE_SLOT_ON_FAULT")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2046082/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2046082] Re: zed.rc: typo in option ZED_POWER_OFF_ENCLO*US*RE_SLOT_ON_FAULT
Testing for Mantic:
mantic-updates:
$ rmadison -a source zfs-linux -s mantic-updates
zfs-linux | 2.2.0-0ubuntu1~23.10 | mantic-updates | source
$ dpkg -s zfs-zed | grep Version:
Version: 2.2.0-0ubuntu1~23.10
$ grep ZED_POWER_OFF_ENCLO /etc/zfs/zed.d/zed.rc
#ZED_POWER_OFF_ENCLOUSRE_SLOT_ON_FAULT=1
$ dpkg -L zfs-zed | xargs grep ZED_POWER_OFF_ENCLOUSRE_SLOT_ON_FAULT
2>/dev/null | sort
/etc/zfs/zed.d/zed.rc:#ZED_POWER_OFF_ENCLOUSRE_SLOT_ON_FAULT=1
/usr/lib/zfs-linux/zed.d/statechange-slot_off.sh:# 2:
ZED_POWER_OFF_ENCLOUSRE_SLOT_ON_FAULT disabled
/usr/lib/zfs-linux/zed.d/statechange-slot_off.sh:#
ZED_POWER_OFF_ENCLOUSRE_SLOT_ON_FAULT is set in zed.rc, and the disk gets
/usr/lib/zfs-linux/zed.d/statechange-slot_off.sh:if [
"${ZED_POWER_OFF_ENCLOUSRE_SLOT_ON_FAULT}" != "1" ] ; then
test package:
$ dpkg-deb -x zfs-zed_2.2.0-0ubuntu1~23.10.1_amd64.deb deb
$ grep ZED_POWER_OFF_ENCLO deb/etc/zfs/zed.d/zed.rc
#ZED_POWER_OFF_ENCLOSURE_SLOT_ON_FAULT=1
- wrong name (no matches anymore):
$ find deb | xargs grep ZED_POWER_OFF_ENCLOUSRE_SLOT_ON_FAULT
2>/dev/null
$
- right name (all matches fixed):
$ find deb | xargs grep ZED_POWER_OFF_ENCLOSURE_SLOT_ON_FAULT
2>/dev/null | sort
deb/etc/zfs/zed.d/zed.rc:#ZED_POWER_OFF_ENCLOSURE_SLOT_ON_FAULT=1
deb/usr/lib/zfs-linux/zed.d/statechange-slot_off.sh:# 2:
ZED_POWER_OFF_ENCLOSURE_SLOT_ON_FAULT disabled
deb/usr/lib/zfs-linux/zed.d/statechange-slot_off.sh:#
ZED_POWER_OFF_ENCLOSURE_SLOT_ON_FAULT is set in zed.rc, and the disk gets
deb/usr/lib/zfs-linux/zed.d/statechange-slot_off.sh:if [
"${ZED_POWER_OFF_ENCLOSURE_SLOT_ON_FAULT}" != "1" ] ; then
--
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/2046082
Title:
zed.rc: typo in option ZED_POWER_OFF_ENCLO*US*RE_SLOT_ON_FAULT
Status in zfs-linux package in Ubuntu:
Fix Released
Status in zfs-linux source package in Mantic:
Confirmed
Status in zfs-linux source package in Noble:
Fix Released
Bug description:
[Impact]
* There's a typo in user-visible option (/etc/zfs/zed.d/zed.rc)
ZED_POWER_OFF_ENCLO*US*RE_SLOT_ON_FAULT introduced upstream
in 2.2.0-rc4 and SRU-ed to Mantic with 2.2.0-0ubuntu1~23.10.
* This could be fixed in Ubuntu before users start adopting it.
[Test Plan]
* Check whether /etc/zfs/zed.d/zed.rc ships the correct option.
* Actual:
$ grep ZED_POWER_OFF_ENCLO /etc/zfs/zed.d/zed.rc
#ZED_POWER_OFF_ENCLOUSRE_SLOT_ON_FAULT=1
* Expected:
$ grep ZED_POWER_OFF_ENCLO /etc/zfs/zed.d/zed.rc
#ZED_POWER_OFF_ENCLOSURE_SLOT_ON_FAULT=1
[Regression Potential]
* Users of Mantic who upgraded to zfs-linux 2.2.0-0ubuntu1~23.10
(published to mantic-updates on 2023-12-08) _and_ enabled the
option (with typo) would have such functionality disabled.
[Other Info]
* This option (with typo) was introduced in commit d19304ffeec5
("zed: Add zedlet to power off slot when drive is faulted"),
and is present in:
- ZFS 2.2: zfs-2.2.0-rc4 (mantic-updates)
- ZFS 2.1: zfs-2.1.13
* It affects Ubuntu Noble and Mantic, but not Lunar or older.
* Fixed upstream with commit 3c7650491b9a ("zed: fix typo in
variable ZED_POWER_OFF_ENCLO*US*RE_SLOT_ON_FAULT")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2046082/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-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: [Ubuntu 22.04.04]: mpi3mr driver update request
This warning will not appear in the 22.04.2 kernel. Maybe UBSAN enabled in this kernel leads to this warning. Note: This is just a warning and there is no functional impact. -- 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: [Ubuntu 22.04.04]: mpi3mr driver update request 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: This BZ has been initiated to incorporate the mpi3mr driver from upstream into the upcoming Ubuntu releases (Ubuntu 22.04.x point releases). 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. 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 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 f762326b2baa scsi: mpi3mr: Propagate sense data for admin queue SCSI I/O 144679dfb584 scsi: mpi3mr: Fix the type used for pointers to bitmap 2a954832015d scsi: mpi3mr: Use -ENOMEM instead of -1 in mpi3mr_expander_add() 2acc635a0e5e scsi: mpi3mr: Use IRQ save variants of spinlock to protect chain frame allocation a3d27dfdcfc2 scsi: mpi3mr: Handle soft reset in progress fault code (0xF002) b85f82f3c92a scsi: mpi3mr: Declare SCSI host template const 1ea41edd88f2 scsi: mpi3mr: Update driver version to 8.4.1.0.0 e74f2fbd8b06 scsi: mpi3mr: Update copyright year 80b8fd0231d5 scsi: mpi3mr: Fix W=1 compilation warnings e5f596bc2592 scsi: mpi3mr: Update MPI Headers to revision 27 f1dec6b1e25e scsi: mpi3mr: Avoid escalating to higher level reset when target is removed 22beef38e52c scsi: mpi3mr: Modify MUR timeout value to 120 seconds 23b3d1cf1572 scsi: mpi3mr: Fix admin queue memory leak upon soft reset 3f1254ed01d0 scsi: mpi3mr: Successive VD delete and add causes FW fault ce756daa36e1 scsi: mpi3mr: Fix expander node leak in mpi3mr_remove() c798304470ca scsi: mpi3mr: Fix memory leaks in mpi3mr_init_ioc() d4caa1a4255c scsi: mpi3mr: Fix sas_hba.phy memory leak in mpi3mr_remove() d0f3c3728da8 scsi: mpi3mr: Fix mpi3mr_hba_port memory leak in mpi3mr_remove() 7d2b02172b6a scsi: mpi3mr: Fix config page DMA memory leak f305a7b6ca21 scsi: mpi3mr: Fix throttle_groups memory leak 8e45183978d6 scsi: mpi3mr: Bad drive in topology results kernel crash 4f297e856a7b scsi: mpi3mr: NVMe command size greater than 8K fails ba8a9ba41fbd scsi: mpi3mr: Return proper values for failures in firmware init path 0a319f162949 scsi: mpi3mr: Wait for diagnostic save during controller init 5b06a7169c59 scsi: mpi3mr: Driver unload crashes host when enhanced logging is enabled 02ca7da2919a scsi: mpi3mr: ioctl timeout when disabling/enabling interrupt 66b381d874fa scsi: mpi3mr: Remove unneeded version.h include e39ea831ebad scsi: mpi3mr: Fix missing mrioc->evtack_cmds initialization 339e61565f81 scsi: mpi3mr: Use number of bits to manage bitmap sizes eeb270aee3e0 scsi: mpi3mr: Remove unnecessary memcpy() to alltgt_info->dmi fb428a2005fc scsi: mpi3mr: Fix issues in mpi3mr_get_all_tgt_info() ae7d45f5283d scsi: mpi3mr: Fix an issue found by KASAN f0a43ba6c66c scsi: mpi3mr: Refer CONFIG_SCSI_MPI3MR in Makefile d347a951906b scsi: mpi3mr: Remove usage of dma_get_required_mask() API 7d21fcfb4095 scsi: mpi3mr: Suppress command reply debug prints 65244389b1b3 scsi: mpi3mr: Select CONFIG_SCSI_SAS_ATTRS c863a2dcb9b0 scsi: mpi3mr: Remove unnecessary cast f616efbee9d6 scsi: mpi3mr: Update driver version to 8.2.0.3.0 2e31be8697b1 scsi: mpi3mr: Fix scheduling while atomic type bug f84e8b5bb57e scsi: mpi3mr: Scan the devices during resume time 130fc180a481 scsi: mpi3mr: Free enclosure objects during driver unload bad2f28da625 scsi: mpi3mr: Handle 0xF003 Fault Code f2a79d2030ad scsi: mpi3mr: Graceful handling of surprise removal of PCIe HBA
[Kernel-packages] [Bug 2043059] Re: Installation errors out when installing in a chroot
hey Sam,
I looked into ways to try to teach the chroot detection tools how to
detect a chroot in a new pid namespace (which is actually the problem,
not the mount namespace), but I didn't find a good solution there.
However, it occurs to me that you can simply override the answer:
ln -sf ../../bin/true ${SW_IMG}/usr/local/bin/ischroot
echo 'DPkg::Path "/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin";' >
/etc/apt/apt.conf.d/99-usr-local-dpkg-path
unshare -p -u -f --mount-proc="${SW_IMG}/proc" chroot "${SW_IMG}"
"${CHROOT_SCRIPT}"
EXIT_CODE=$?
rm ${SW_IMG}/etc/apt/apt.conf.d/99-usr-local-dpkg-path
rm ${SW_IMG}/usr/local/bin/ischroot
That would have the added benefit of solving the problem for
other/future packages as well.
If we were to update kdump-tools to detect a chroot as described in
comment #7 (test build in
https://launchpad.net/~dannf/+archive/ubuntu/lp2043059 ), could you
update your script to do the above?
--
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 2046082] Re: zed.rc: typo in option ZED_POWER_OFF_ENCLO*US*RE_SLOT_ON_FAULT
This bug was fixed in the package zfs-linux - 2.2.2-0ubuntu2
---
zfs-linux (2.2.2-0ubuntu2) noble; urgency=medium
* d/p/u/zed-fix-typo-ZED_POWER_OFF_ENCLOUSRE_SLOT_ON_FAULT.patch:
fix typo in configuration option in zed.rc (LP: #2046082)
-- Mauricio Faria de Oliveira Sat, 09 Dec 2023
16:10:21 -0300
** Changed in: zfs-linux (Ubuntu Noble)
Status: Fix Committed => Fix Released
--
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/2046082
Title:
zed.rc: typo in option ZED_POWER_OFF_ENCLO*US*RE_SLOT_ON_FAULT
Status in zfs-linux package in Ubuntu:
Fix Released
Status in zfs-linux source package in Mantic:
Confirmed
Status in zfs-linux source package in Noble:
Fix Released
Bug description:
[Impact]
* There's a typo in user-visible option (/etc/zfs/zed.d/zed.rc)
ZED_POWER_OFF_ENCLO*US*RE_SLOT_ON_FAULT introduced upstream
in 2.2.0-rc4 and SRU-ed to Mantic with 2.2.0-0ubuntu1~23.10.
* This could be fixed in Ubuntu before users start adopting it.
[Test Plan]
* Check whether /etc/zfs/zed.d/zed.rc ships the correct option.
* Actual:
$ grep ZED_POWER_OFF_ENCLO /etc/zfs/zed.d/zed.rc
#ZED_POWER_OFF_ENCLOUSRE_SLOT_ON_FAULT=1
* Expected:
$ grep ZED_POWER_OFF_ENCLO /etc/zfs/zed.d/zed.rc
#ZED_POWER_OFF_ENCLOSURE_SLOT_ON_FAULT=1
[Regression Potential]
* Users of Mantic who upgraded to zfs-linux 2.2.0-0ubuntu1~23.10
(published to mantic-updates on 2023-12-08) _and_ enabled the
option (with typo) would have such functionality disabled.
[Other Info]
* This option (with typo) was introduced in commit d19304ffeec5
("zed: Add zedlet to power off slot when drive is faulted"),
and is present in:
- ZFS 2.2: zfs-2.2.0-rc4 (mantic-updates)
- ZFS 2.1: zfs-2.1.13
* It affects Ubuntu Noble and Mantic, but not Lunar or older.
* Fixed upstream with commit 3c7650491b9a ("zed: fix typo in
variable ZED_POWER_OFF_ENCLO*US*RE_SLOT_ON_FAULT")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2046082/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-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: [Ubuntu 22.04.04]: mpi3mr driver update request
Hi Jeff, I have covered the required testing and found no critical issues except the below minor issues. [Wed Dec 13 22:05:56 2023] memcpy: detected field-spanning write (size 128) of single field "bsg_reply_buf->reply_buf" at drivers/scsi/mpi3mr/mpi3mr_app.c:1658 (size 1) [Wed Dec 13 22:05:56 2023] WARNING: CPU: 4 PID: 3587 at drivers/scsi/mpi3mr/mpi3mr_app.c:1658 mpi3mr_bsg_process_mpt_cmds+0x1302/0x14c0 [mpi3mr] [Wed Dec 13 22:05:56 2023] Modules linked in: mpi3mr tls intel_rapl_msr intel_rapl_common kvm_amd ccp kvm binfmt_misc irqbypass crct10dif_pclmul polyval_clmulni polyval_generic ghash_clmulni_intel aesni_intel crypto_simd cryptd nls_iso8859_1 input_leds serio_raw joydev bochs drm_vram_helper drm_ttm_helper ttm mac_hid drm_kms_helper qemu_fw_cfg sch_fq_codel msr parport_pc ppdev lp parport drm efi_pstore ip_tables x_tables autofs4 ses enclosure hid_generic usbhid hid crc32_pclmul i2c_i801 ahci psmouse i2c_smbus libahci lpc_ich scsi_transport_sas virtio_rng xhci_pci xhci_pci_renesas [last unloaded: mpi3mr] [Wed Dec 13 22:05:56 2023] CPU: 4 PID: 3587 Comm: kworker/4:2H Tainted: G W OE 6.5.0-14-generic #14 [Wed Dec 13 22:05:56 2023] Hardware name: Red Hat KVM/RHEL, BIOS 1.16.1-1.el9 04/01/2014 [Wed Dec 13 22:05:56 2023] Workqueue: kblockd blk_mq_run_work_fn [Wed Dec 13 22:05:56 2023] RIP: 0010:mpi3mr_bsg_process_mpt_cmds+0x1302/0x14c0 [mpi3mr] [Wed Dec 13 22:05:56 2023] Code: b9 01 00 00 00 48 89 c6 4c 89 55 90 48 c7 c2 58 2f 2a c0 48 c7 c7 a8 2f 2a c0 48 89 45 98 c6 05 4e a8 00 00 01 e8 8e d1 a6 c6 <0f> 0b 4c 8b 55 90 48 8b 45 98 e9 3b ff ff ff 31 db e9 a4 fd ff ff [Wed Dec 13 22:05:56 2023] RSP: 0018:acd300243c38 EFLAGS: 00010246 [Wed Dec 13 22:05:56 2023] RAX: RBX: 9190d4fe7540 RCX: [Wed Dec 13 22:05:56 2023] RDX: RSI: RDI: [Wed Dec 13 22:05:56 2023] RBP: acd300243cf8 R08: R09: [Wed Dec 13 22:05:56 2023] R10: R11: R12: 9191c6ba9100 [Wed Dec 13 22:05:56 2023] R13: 9191c3fb8830 R14: 9190d4fe7000 R15: [Wed Dec 13 22:05:56 2023] FS: () GS:91923bd0() knlGS: [Wed Dec 13 22:05:56 2023] CS: 0010 DS: ES: CR0: 80050033 [Wed Dec 13 22:05:56 2023] CR2: 0213ecf8 CR3: 0a04a000 CR4: 00350ee0 [Wed Dec 13 22:05:56 2023] Call Trace: [Wed Dec 13 22:05:56 2023] [Wed Dec 13 22:05:56 2023] ? show_regs+0x6d/0x80 [Wed Dec 13 22:05:56 2023] ? __warn+0x89/0x160 [Wed Dec 13 22:05:56 2023] ? mpi3mr_bsg_process_mpt_cmds+0x1302/0x14c0 [mpi3mr] [Wed Dec 13 22:05:56 2023] ? report_bug+0x17e/0x1b0 [Wed Dec 13 22:05:56 2023] ? handle_bug+0x51/0xa0 [Wed Dec 13 22:05:56 2023] ? exc_invalid_op+0x18/0x80 [Wed Dec 13 22:05:56 2023] ? asm_exc_invalid_op+0x1b/0x20 [Wed Dec 13 22:05:56 2023] ? mpi3mr_bsg_process_mpt_cmds+0x1302/0x14c0 [mpi3mr] [Wed Dec 13 22:05:56 2023] ? mpi3mr_bsg_process_mpt_cmds+0x1302/0x14c0 [mpi3mr] [Wed Dec 13 22:05:56 2023] mpi3mr_bsg_request+0x23/0x70 [mpi3mr] [Wed Dec 13 22:05:56 2023] bsg_queue_rq+0xac/0x100 [Wed Dec 13 22:05:56 2023] blk_mq_dispatch_rq_list+0x153/0x550 [Wed Dec 13 22:05:56 2023] __blk_mq_sched_dispatch_requests+0xa4/0x190 [Wed Dec 13 22:05:56 2023] ? finish_task_switch.isra.0+0x89/0x2b0 [Wed Dec 13 22:05:56 2023] blk_mq_sched_dispatch_requests+0x37/0x80 [Wed Dec 13 22:05:56 2023] blk_mq_run_work_fn+0x3f/0x90 [Wed Dec 13 22:05:56 2023] process_one_work+0x223/0x440 [Wed Dec 13 22:05:56 2023] worker_thread+0x4d/0x3f0 [Wed Dec 13 22:05:56 2023] ? srso_untrain_ret+0x2/0x2 [Wed Dec 13 22:05:56 2023] ? __pfx_worker_thread+0x10/0x10 [Wed Dec 13 22:05:56 2023] kthread+0xf2/0x120 [Wed Dec 13 22:05:56 2023] ? __pfx_kthread+0x10/0x10 [Wed Dec 13 22:05:56 2023] ret_from_fork+0x47/0x70 [Wed Dec 13 22:05:56 2023] ? __pfx_kthread+0x10/0x10 [Wed Dec 13 22:05:56 2023] ret_from_fork_asm+0x1b/0x30 [Wed Dec 13 22:05:56 2023] [Wed Dec 13 22:05:56 2023] ---[ end trace ]--- - The above warning will appear only once after the driver load and it will not appear for subsequent management commands - The rep_buf is a flexible array which can grow in run time and whose memory is already allocated and it will never grow beyond the allocated memory. - This is a false positive (maybe UBSAN is responsible for throwing this warning) -- 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: [Ubuntu 22.04.04]: mpi3mr driver update request 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: This BZ has been initiated to incorporate the mpi3mr driver from upstream into
[Kernel-packages] [Bug 2046116] Re: bluetooth device connected but not recognised as output device
hi @werdem o/ What bluetooth device are you using? Your version of BlueZ has a security patch for vulnerability CVE-2023-45866 which disables support for certain legacy bluetooth devices. If your device does not support Classic Bonding, you can re-enable it by setting `ClassicBondedOnly=false` in `/etc/bluetooth/input.conf`, and then running `systemctl restart bluetooth`. More info in https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2045931/comments/6 Please let me know if that enables your device. Keep in mind that enabling legacy devices enables the exploit. ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-45866 -- 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 2045931] Re: ps3 sixasis controller request pin to connect to bt
Thank you for the clarification! I'll remove the regression-update tag then, since this is the intended behaviour of the security update, so it shouldn't count towards regression statistics. ** Tags removed: regression-update -- 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/2045931 Title: ps3 sixasis controller request pin to connect to bt Status in bluez package in Ubuntu: Won't Fix Bug description: Once my Ubuntu updated bluez package to 5.64-0ubuntu1.1 I was not able to connect my PS3 Sixasis controller via bluetooth. It is aking to enter a PIN in the device (not possible to enter a pin in the gamepad). Source pacakge (from "apt list -a bluez"): bluez/jammy-updates,jammy-security 5.64-0ubuntu1.1 amd64 Once downgraded to 5.64-0ubuntu1 version, gamepad connects OK again without asking for a connection PIN. Ubuntu release: Description: Ubuntu 22.04.3 LTS Release: 22.04 Package version: bluez: Installed: 5.64-0ubuntu1.1 Expected to happen: Connect PS3 Controller by Bluetooth without asking for a PIN code Happened instead: PS3 Controller cannot connect because PIN code is requested To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2045931/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2045931] Re: ps3 sixasis controller request pin to connect to bt
Hello all o/ This is intentional. And easy to reverse. The patch for CVE-2023-45866 works as intended and is not a regression. https://git.kernel.org/pub/scm/bluetooth/bluez.git/commit/profiles/input?id=25a471a83e02e1effb15d5a488b3f0085eaeb675 If ClassicBondedOnly is not enforced, a nearby attacker can create a HID (like a keyboard and mouse) on the victims PC when bluetooth is discoverable. An HID can be used as a keyloggers or, of course, give direct control of the session. The CVE reporter has discussed this further on https://github.com/skysafe/reblog/tree/main/cve-2023-45866 And a talk and PoC release is forthcoming. Fortunately, it is easy to enable legacy devices by setting `ClassicBondedOnly=false` in `/etc/bluetooth/input.conf`, and then running `systemctl restart bluetooth`. I ver ified that a PS3 controller works well after this :) All other distros *should* be fixing this CVE. I would love it if bloggers in the Linux gaming sphere could raise awareness about this CVE and share how to enable legacy bluetooth device support. ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-45866 ** Changed in: bluez (Ubuntu) Status: Confirmed => Won't Fix ** Changed in: bluez (Ubuntu) Assignee: Nishit Majithia (0xnishit) => Mark Esler (eslerm) -- 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/2045931 Title: ps3 sixasis controller request pin to connect to bt Status in bluez package in Ubuntu: Won't Fix Bug description: Once my Ubuntu updated bluez package to 5.64-0ubuntu1.1 I was not able to connect my PS3 Sixasis controller via bluetooth. It is aking to enter a PIN in the device (not possible to enter a pin in the gamepad). Source pacakge (from "apt list -a bluez"): bluez/jammy-updates,jammy-security 5.64-0ubuntu1.1 amd64 Once downgraded to 5.64-0ubuntu1 version, gamepad connects OK again without asking for a connection PIN. Ubuntu release: Description: Ubuntu 22.04.3 LTS Release: 22.04 Package version: bluez: Installed: 5.64-0ubuntu1.1 Expected to happen: Connect PS3 Controller by Bluetooth without asking for a PIN code Happened instead: PS3 Controller cannot connect because PIN code is requested To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2045931/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2046349] [NEW] Magic Mouse stop to work
Public bug reported: After the last kernel update 5.15.0-91, the magic mouse connects but the pointer isn´t moving. I tried it on other devices such as Android tablet and windows PC. So, it seems me a kernel issue instead of a device one. Thx! ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: bluetooth -- 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/2046349 Title: Magic Mouse stop to work Status in linux package in Ubuntu: New Bug description: After the last kernel update 5.15.0-91, the magic mouse connects but the pointer isn´t moving. I tried it on other devices such as Android tablet and windows PC. So, it seems me a kernel issue instead of a device one. Thx! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2046349/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2046329] Re: Random kernel panics related to page fault in Ubuntu 23.4/23.10 server with QEMU
** Package changed: ubuntu => linux (Ubuntu) ** Summary changed: - Random kernel panics related to page fault in Ubuntu 23.4/23.10 server with QEMU + Random kernel panics related to page fault in Ubuntu 23.04/23.10 server with QEMU ** Tags added: lunar mantic -- 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/2046329 Title: Random kernel panics related to page fault in Ubuntu 23.04/23.10 server with QEMU Status in linux package in Ubuntu: New Bug description: Here are the general info about the server 01:06:49 labs@selfmadeninja ~ → lsb_release -a; uname -a; dpkg -l | grep ' linux-i' No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 23.10 Release: 23.10 Codename: mantic Linux selfmadeninja 6.5.0-14-generic #14-Ubuntu SMP PREEMPT_DYNAMIC Tue Nov 14 14:59:49 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux rc linux-image-6.2.0-20-generic 6.2.0-20.20 amd64Signed kernel image generic rc linux-image-6.2.0-23-generic 6.2.0-23.23 amd64Signed kernel image generic rc linux-image-6.2.0-24-generic 6.2.0-24.24 amd64Signed kernel image generic rc linux-image-6.2.0-25-generic 6.2.0-25.25 amd64Signed kernel image generic rc linux-image-6.2.0-26-generic 6.2.0-26.26 amd64Signed kernel image generic rc linux-image-6.2.0-27-generic 6.2.0-27.28 amd64Signed kernel image generic rc linux-image-6.2.0-31-generic 6.2.0-31.31 amd64Signed kernel image generic rc linux-image-6.2.0-32-generic 6.2.0-32.32 amd64Signed kernel image generic rc linux-image-6.2.0-33-generic 6.2.0-33.33+1 amd64Signed kernel image generic rc linux-image-6.2.0-34-generic 6.2.0-34.34 amd64Signed kernel image generic rc linux-image-6.2.0-35-generic 6.2.0-35.35 amd64Signed kernel image generic rc linux-image-6.2.0-36-generic 6.2.0-36.37 amd64Signed kernel image generic rc linux-image-6.2.0-37-generic 6.2.0-37.38 amd64Signed kernel image generic ii linux-image-6.2.0-39-generic 6.2.0-39.40 amd64Signed kernel image generic ii linux-image-6.5.0-14-generic 6.5.0-14.14 amd64Signed kernel image generic ii linux-image-generic 6.5.0.14.16 amd64Generic Linux kernel image I recently changed to Intel i9 14900K and it was working well for sometime. My system has 128G RAM and I am using QEMU/KVM and running many servers. I also have a Windows VM for gaming with GPU passthrough. I have dual GPUs installed, but using only one GPU at the moment, that too only when the Windows VM is on. I am using integrated graphics for the Ubuntu Server. I am getting random panics, I was clueless and then I installed kdump to capture the panics. All of them point to something like this [34006.012227] BUG: unable to handle page fault for address: 936a8abdd3c8 [34006.012234] #PF: supervisor read access in kernel mode [34006.012235] #PF: error_code(0x) - not-present page but they all originate from different areas. I have zipped all the crash from host I got so far including the kernel dump and its available here (crash.tar.gz- 4.5GB): https://drive.google.com/drive/folders/1faoiKI5Vr2KkwOxHpKQ35TnNcNgjn_Iz?usp=drive_link So I turned off panic_on_oops in the host, and my VM started to panic (I have kdump configuted in one of my vm also) and the crash logs are here: https://drive.google.com/file/d/1yGeNBw9VushW50G1nuePURs0P4PeEsTs/view?usp=sharing This is my current /proc/cmdline: BOOT_IMAGE=/vmlinuz-6.5.0-14-generic root=/dev/mapper/ubuntu--vg- ubuntu--lv ro slub_debug=F intel_iommu=on kvm.ignore_msrs=1 slub_debug=F split_lock_detect=off softlockup_panic=0 nmi_watchdog=0 ubsan=0 panic_on_oops=0 crashkernel=1G-:1G - Panic Examples: Panic 1 on host: [43084.904967] BUG: kernel NULL pointer dereference, address: 0009 [43084.904972] #PF: supervisor instruction fetch in kernel mode [43084.904974] #PF: error_code(0x0010) - not-present page [43084.904975] PGD 0 P4D 0 [43084.904977]
[Kernel-packages] [Bug 2031412] Re: Support mipi camera on Intel Meteor Lake platform
Using that PPA from jammy pocket. Hi, that PPA contains HAL framework packages that are not yet in Ubuntu archive but packaged into Jammy oem image. ** Tags removed: verification-needed-mantic ** Tags added: verification-done-mantic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2031412 Title: Support mipi camera on Intel Meteor Lake platform Status in HWE Next: New Status in ipu6-drivers package in Ubuntu: Fix Released Status in ivsc-driver package in Ubuntu: Fix Released Status in linux package in Ubuntu: Triaged Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-6.5 package in Ubuntu: Invalid Status in ipu6-drivers source package in Jammy: Won't Fix Status in ivsc-driver source package in Jammy: Won't Fix Status in linux source package in Jammy: Won't Fix Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-6.5 source package in Jammy: Fix Released Status in ipu6-drivers source package in Mantic: Fix Committed Status in ivsc-driver source package in Mantic: Fix Committed Status in linux source package in Mantic: Fix Committed Status in linux-firmware source package in Mantic: Fix Released Status in linux-oem-6.5 source package in Mantic: Invalid Status in ipu6-drivers source package in Noble: Fix Released Status in ivsc-driver source package in Noble: Fix Released Status in linux source package in Noble: Triaged Status in linux-firmware source package in Noble: Fix Released Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [SRU Justification] == ipu6-driver == [Impact] Missing Intel MIPI firmware for Meteor Lake platform. [Fix] Based on upstream tag https://github.com/intel/ipu6-drivers/releases/tag/Release_20231019, and an additional patch to enable/fix compilation of additional sensor modules. [Test Case] This is verified on MTL Lattice and VSC platforms, as well as previous generations e.g. TGL and ADL. To actually verify the camera framework: ``` # enable mantic-proposed, update the kernel, make sure you get 6.5.0-14.14 # reboot into the 6.5.0-14.14 kernel $ sudo apt install intel-ipu6-dkms intel-vsc-dkms $ sudo add-apt-repository ppa:oem-solutions-group/intel-ipu6 -y -u $ sudo apt install gstreamer1.0-icamera v4l2-relayd ``` In the above steps, make sure that only gstreamer1.0-icamera, v4l2-relayd, and their dependencies, are fetched from the oem-solutions-group PPA. Everything else must come from the mantic archive. And then browse https://webcamtests.com/ for testing. [Where problems could occur] This is a new platform. We've been verifying its functions and features, and are still polishing it. [Other Info] While Intel Meteor Lake is only supported by linux-oem-6.5/jammy and linux/mantic and on, and yet the lastest stable driver was verified after Mantic was released, it's being proposed to Noble instead. == ivsc-driver == [Impact] Missing Intel MIPI firmware for Meteor Lake platform. Need both firmware and driver change to probe the hardware correctly. [Fix] 4 commits from the latest trunk branch on upstream repository https://github.com/intel/ivsc-driver. [Test Case] With all other changes in position, Intel VSC driver modules are to be loaded as a soft dependency of some selected camera sensor modules. LJCA modules should be loaded automatically on MTL platforms as well. To actually verify the camera framework: ``` # enable mantic-proposed, update the kernel, make sure you get 6.5.0-14.14 # reboot into the 6.5.0-14.14 kernel $ sudo apt install intel-ipu6-dkms intel-vsc-dkms $ sudo add-apt-repository ppa:oem-solutions-group/intel-ipu6 -y -u $ sudo apt install gstreamer1.0-icamera v4l2-relayd ``` In the above steps, make sure that only gstreamer1.0-icamera, v4l2-relayd, and their dependencies, are fetched from the oem-solutions-group PPA. Everything else must come from the mantic archive. And then browse https://webcamtests.com/ for testing. [Where problems could occur] While it changes how LJCA modules match from ACPI ID, it's also tested and verified on previous generations using IVSC, e.g. TGL, ADL. [Other Info] While Intel Meteor Lake is only supported by linux-oem-6.5/jammy and linux/mantic and on, and yet the lastest stable driver was verified after Mantic was released, it's being proposed to Noble instead. == linux/linux-oem-6.5 == [Impact] Need kernel driver fixes for int3472/iommu for Intel IPU6 platform on MTL. [Fix] Two fixes in need. One, we need IOMMU passthrough for MTL platform. The other, fix is for handshake pin support for Lattice MIPI aggregator. The Intel IPU6 camera drivers are not yet all upstreamed yet. So far Intel
[Kernel-packages] [Bug 2046329] [NEW] Random kernel panics related to page fault in Ubuntu 23.4/23.10 server with QEMU
You have been subscribed to a public bug: Here are the general info about the server 01:06:49 labs@selfmadeninja ~ → lsb_release -a; uname -a; dpkg -l | grep ' linux-i' No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 23.10 Release:23.10 Codename: mantic Linux selfmadeninja 6.5.0-14-generic #14-Ubuntu SMP PREEMPT_DYNAMIC Tue Nov 14 14:59:49 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux rc linux-image-6.2.0-20-generic 6.2.0-20.20 amd64Signed kernel image generic rc linux-image-6.2.0-23-generic 6.2.0-23.23 amd64Signed kernel image generic rc linux-image-6.2.0-24-generic 6.2.0-24.24 amd64Signed kernel image generic rc linux-image-6.2.0-25-generic 6.2.0-25.25 amd64Signed kernel image generic rc linux-image-6.2.0-26-generic 6.2.0-26.26 amd64Signed kernel image generic rc linux-image-6.2.0-27-generic 6.2.0-27.28 amd64Signed kernel image generic rc linux-image-6.2.0-31-generic 6.2.0-31.31 amd64Signed kernel image generic rc linux-image-6.2.0-32-generic 6.2.0-32.32 amd64Signed kernel image generic rc linux-image-6.2.0-33-generic 6.2.0-33.33+1 amd64Signed kernel image generic rc linux-image-6.2.0-34-generic 6.2.0-34.34 amd64Signed kernel image generic rc linux-image-6.2.0-35-generic 6.2.0-35.35 amd64Signed kernel image generic rc linux-image-6.2.0-36-generic 6.2.0-36.37 amd64Signed kernel image generic rc linux-image-6.2.0-37-generic 6.2.0-37.38 amd64Signed kernel image generic ii linux-image-6.2.0-39-generic 6.2.0-39.40 amd64Signed kernel image generic ii linux-image-6.5.0-14-generic 6.5.0-14.14 amd64Signed kernel image generic ii linux-image-generic 6.5.0.14.16 amd64Generic Linux kernel image I recently changed to Intel i9 14900K and it was working well for sometime. My system has 128G RAM and I am using QEMU/KVM and running many servers. I also have a Windows VM for gaming with GPU passthrough. I have dual GPUs installed, but using only one GPU at the moment, that too only when the Windows VM is on. I am using integrated graphics for the Ubuntu Server. I am getting random panics, I was clueless and then I installed kdump to capture the panics. All of them point to something like this [34006.012227] BUG: unable to handle page fault for address: 936a8abdd3c8 [34006.012234] #PF: supervisor read access in kernel mode [34006.012235] #PF: error_code(0x) - not-present page but they all originate from different areas. I have zipped all the crash from host I got so far including the kernel dump and its available here (crash.tar.gz- 4.5GB): https://drive.google.com/drive/folders/1faoiKI5Vr2KkwOxHpKQ35TnNcNgjn_Iz?usp=drive_link So I turned off panic_on_oops in the host, and my VM started to panic (I have kdump configuted in one of my vm also) and the crash logs are here: https://drive.google.com/file/d/1yGeNBw9VushW50G1nuePURs0P4PeEsTs/view?usp=sharing This is my current /proc/cmdline: BOOT_IMAGE=/vmlinuz-6.5.0-14-generic root=/dev/mapper/ubuntu--vg-ubuntu --lv ro slub_debug=F intel_iommu=on kvm.ignore_msrs=1 slub_debug=F split_lock_detect=off softlockup_panic=0 nmi_watchdog=0 ubsan=0 panic_on_oops=0 crashkernel=1G-:1G - Panic Examples: Panic 1 on host: [43084.904967] BUG: kernel NULL pointer dereference, address: 0009 [43084.904972] #PF: supervisor instruction fetch in kernel mode [43084.904974] #PF: error_code(0x0010) - not-present page [43084.904975] PGD 0 P4D 0 [43084.904977] Oops: 0010 [#1] PREEMPT SMP NOPTI [43084.904980] CPU: 9 PID: 0 Comm: swapper/9 Kdump: loaded Tainted: P O 6.2.0-37-generic #38-Ubuntu [43084.904982] Hardware name: ASUS System Product Name/PRIME Z790-P WIFI, BIOS 1402 09/08/2023 [43084.904983] RIP: 0010:0x9 [43084.904987] Code: Unable to access opcode bytes at 0xffdf. [43084.904988] RSP: 0018:b9f0001cbdb8 EFLAGS: 00010046 [43084.904990] RAX: RBX: 9fd9419ccd40 RCX: [43084.904991] RDX: RSI: RDI: [43084.904992] RBP: 8957bd15 R08: R09:
[Kernel-packages] [Bug 2020022] Re: [SRU][22.04.2 & 23.10] OS cannot boot successfully when enabling VMD in UEFI setup
Confirmed that the test kernel in Comment #14 fixes the issue.
Thanks.
** Attachment added: "dmesg-6.2.0-39_enableVMD"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2020022/+attachment/572/+files/6.2.0-39_enableVMD.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2020022
Title:
[SRU][22.04.2 & 23.10] OS cannot boot successfully when enabling VMD
in UEFI setup
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Kinetic:
Won't Fix
Status in linux source package in Lunar:
In Progress
Status in linux source package in Mantic:
Fix Released
Status in linux source package in Noble:
Fix Released
Bug description:
[Impact]
When enabling VMD in UEFI setup, OS cannot boot successfully. And, the panic
leads to the system reboot. The following log is shown:
[ 166.605518] DMAR: VT-d detected Invalidation Queue Error: Reason f
[ 166.605522] DMAR: VT-d detected Invalidation Time-out Error: SID
[ 166.612445] DMAR: VT-d detected Invalidation Completion Error: SID
[ 166.612447] DMAR: QI HEAD: UNKNOWN qw0 = 0x0, qw1 = 0x0
[ 166.612449] DMAR: QI PRIOR: UNKNOWN qw0 = 0x0, qw1 = 0x0
...
Additional info:
* The issue happens on both Lenovo SE350 server and Lenovo SR850 v2 server.
Debugging info and fix commit info:
* `git bisect` indicates the offending commit is 6aab5622296b ("PCI: vmd:
Clean up domain before enumeration"). The root cause is that VMD driver tries
to clear a PCI configuration space range when resetting a VMD domain
(https://github.com/torvalds/linux/blob/master/drivers/pci/controller/vmd.c#L544),
which leads to the failure.
[Fix]
* Another `git bisect` indicates the fix commit is 20f3337d350c ("x86:
don't use REP_GOOD or ERMS for small memory clearing). I confirmed that this
commit can fix the issue.
Would it be possible to include the commit 20f3337d350c in Ubuntu
22.04.2/23.10 kernel?
[Test Plan]
Reproduce Step
1.Disable Intel VMD in BIOS settings
System Settings --> Devices and I/O Ports --> Intel VMD technology -->
Enable/Disable Intel VMD : Disabled
2.Install OS
3.Enable Intel VMD in BIOS settings
System Settings --> Devices and I/O Ports --> Intel VMD technology -->
Enable/Disable Intel VMD : Enabled
4.Rebooting will reproduce this issue
[ Where problems could occur ]
* Lenovo SE350 server and Lenovo SR850 v2 server
* The regression leads to the boot failure (cannot boot info OS successfully).
[ Other Info ]
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/lunar/+ref/enable_vmd_lp_2020022
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2020022/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2046082] Re: zed.rc: typo in option ZED_POWER_OFF_ENCLO*US*RE_SLOT_ON_FAULT
Thanks Mauricio, I've uploaded your change to noble now
** Changed in: zfs-linux (Ubuntu Noble)
Status: Confirmed => Fix Committed
--
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/2046082
Title:
zed.rc: typo in option ZED_POWER_OFF_ENCLO*US*RE_SLOT_ON_FAULT
Status in zfs-linux package in Ubuntu:
Fix Committed
Status in zfs-linux source package in Mantic:
Confirmed
Status in zfs-linux source package in Noble:
Fix Committed
Bug description:
[Impact]
* There's a typo in user-visible option (/etc/zfs/zed.d/zed.rc)
ZED_POWER_OFF_ENCLO*US*RE_SLOT_ON_FAULT introduced upstream
in 2.2.0-rc4 and SRU-ed to Mantic with 2.2.0-0ubuntu1~23.10.
* This could be fixed in Ubuntu before users start adopting it.
[Test Plan]
* Check whether /etc/zfs/zed.d/zed.rc ships the correct option.
* Actual:
$ grep ZED_POWER_OFF_ENCLO /etc/zfs/zed.d/zed.rc
#ZED_POWER_OFF_ENCLOUSRE_SLOT_ON_FAULT=1
* Expected:
$ grep ZED_POWER_OFF_ENCLO /etc/zfs/zed.d/zed.rc
#ZED_POWER_OFF_ENCLOSURE_SLOT_ON_FAULT=1
[Regression Potential]
* Users of Mantic who upgraded to zfs-linux 2.2.0-0ubuntu1~23.10
(published to mantic-updates on 2023-12-08) _and_ enabled the
option (with typo) would have such functionality disabled.
[Other Info]
* This option (with typo) was introduced in commit d19304ffeec5
("zed: Add zedlet to power off slot when drive is faulted"),
and is present in:
- ZFS 2.2: zfs-2.2.0-rc4 (mantic-updates)
- ZFS 2.1: zfs-2.1.13
* It affects Ubuntu Noble and Mantic, but not Lunar or older.
* Fixed upstream with commit 3c7650491b9a ("zed: fix typo in
variable ZED_POWER_OFF_ENCLO*US*RE_SLOT_ON_FAULT")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2046082/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2045992] Re: Kubuntu 23.10: Kernel Bug Invoking Undefined Behavior on Boot
** Package changed: ubuntu => linux (Ubuntu) ** Tags added: mantic -- 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/2045992 Title: Kubuntu 23.10: Kernel Bug Invoking Undefined Behavior on Boot Status in linux package in Ubuntu: New Bug description: Apologies if what this post will entail is not the correct way to report a bug. This is my first time reporting one for a linux distro, and I'm more or less doing so based on information I was told while investigating a separate issue related to my audio devices. On boot, along with the error I was looking for, I noticed a number of UBSan errors pop up. I asked about them in a linux-related discord server and their first question was whether the kernel was compiled with Clang. Now, because I never mess with the kernel, I told them I wasn't sure. That was when they told me that it's a kernel bug that invoked undefined behavior and left my kernel in an erroneous state. Here are the errors in question: [ 5.036942] UBSAN: array-index-out-of-bounds in /build/linux-SXblTa/linux-6.5.0/drivers/gpu/drm/amd/amdgpu/../pm/powerplay/hwmgr/smu7_hwmgr.c:3669:4 [ 5.036951] index 2 is out of range for type 'ATOM_Tonga_MCLK_Dependency_Record [1]' [ 5.041843] UBSAN: array-index-out-of-bounds in /build/linux-SXblTa/linux-6.5.0/drivers/gpu/drm/amd/amdgpu/../pm/powerplay/hwmgr/smu7_hwmgr.c:3676:4 [ 5.041852] index 7 is out of range for type 'ATOM_Polaris_SCLK_Dependency_Record [1]' Because I'm not 100% sure what all goes into a bug report like this, I will be providing the output of lsb_release -rd, hyfetch, and creating a list of my system's specs in hopes that it will help provide some sort of clarity. lsb_release -rd Output: --- No LSB modules are available. Description: Ubuntu 23.10 Release: 23.10 Hyfetch Output: --- OS: Kubuntu 23.10 x86_64 Kernel: 6.5.0-14-generic Uptime: 28 mins Packages: 3 (pipx), 4178 (dpkg), 43 (flatpak), 24 (snap) Shell: fish 3.6.1 (yes I know it's deprecated but I prefer it over other shells) Resolution: 1920x1080, 1920x1080 DE: Plasma 5.27.8 [KF5 5.110.0] [Qt 5.15.10] (x11) WM: KWin System Specs: - CPU: AMD Ryzen 5 2600x GPU: Sapphire NITRO+ Radeon RX 570 MOBO: ASUS PRIME B450M-A II RAM: TEAMGROUP TUFF Gaming 2x8 GB at 2400 MHz PSU: Corsair RM850x (850W PSU) SSD: Western Digital Blue 1 TB SSD I'll be honest and say I'm not even sure if my system specs are required for a bug report like this, but just in case I figured I'd provide them anyway, as maybe it's a hardware-specific thing, or something specific to my system entirely. I'm not sure though. I also went ahead and included an attachment of the photo I took of the error itself, maybe it'll help in some way. I'm also unsure if there's a package related to this bug, or what that package would be. Sorry. As for the last two things stated in the guidelines for reporting a bug, what I expected to happen was to see the error about my USB device along with some of the general jargon that pops up on boot that I typically don't have to worry about. Instead what happened is that based on what someone else told me, I found a bug in my kernel, although I'm not knowledgeable enough to know if it's a serious bug, or something that's really not that big of a deal. I'll leave that one up to you guys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045992/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2045992] [NEW] Kubuntu 23.10: Kernel Bug Invoking Undefined Behavior on Boot
You have been subscribed to a public bug: Apologies if what this post will entail is not the correct way to report a bug. This is my first time reporting one for a linux distro, and I'm more or less doing so based on information I was told while investigating a separate issue related to my audio devices. On boot, along with the error I was looking for, I noticed a number of UBSan errors pop up. I asked about them in a linux-related discord server and their first question was whether the kernel was compiled with Clang. Now, because I never mess with the kernel, I told them I wasn't sure. That was when they told me that it's a kernel bug that invoked undefined behavior and left my kernel in an erroneous state. Here are the errors in question: [ 5.036942] UBSAN: array-index-out-of-bounds in /build/linux-SXblTa/linux-6.5.0/drivers/gpu/drm/amd/amdgpu/../pm/powerplay/hwmgr/smu7_hwmgr.c:3669:4 [ 5.036951] index 2 is out of range for type 'ATOM_Tonga_MCLK_Dependency_Record [1]' [ 5.041843] UBSAN: array-index-out-of-bounds in /build/linux-SXblTa/linux-6.5.0/drivers/gpu/drm/amd/amdgpu/../pm/powerplay/hwmgr/smu7_hwmgr.c:3676:4 [ 5.041852] index 7 is out of range for type 'ATOM_Polaris_SCLK_Dependency_Record [1]' Because I'm not 100% sure what all goes into a bug report like this, I will be providing the output of lsb_release -rd, hyfetch, and creating a list of my system's specs in hopes that it will help provide some sort of clarity. lsb_release -rd Output: --- No LSB modules are available. Description: Ubuntu 23.10 Release: 23.10 Hyfetch Output: --- OS: Kubuntu 23.10 x86_64 Kernel: 6.5.0-14-generic Uptime: 28 mins Packages: 3 (pipx), 4178 (dpkg), 43 (flatpak), 24 (snap) Shell: fish 3.6.1 (yes I know it's deprecated but I prefer it over other shells) Resolution: 1920x1080, 1920x1080 DE: Plasma 5.27.8 [KF5 5.110.0] [Qt 5.15.10] (x11) WM: KWin System Specs: - CPU: AMD Ryzen 5 2600x GPU: Sapphire NITRO+ Radeon RX 570 MOBO: ASUS PRIME B450M-A II RAM: TEAMGROUP TUFF Gaming 2x8 GB at 2400 MHz PSU: Corsair RM850x (850W PSU) SSD: Western Digital Blue 1 TB SSD I'll be honest and say I'm not even sure if my system specs are required for a bug report like this, but just in case I figured I'd provide them anyway, as maybe it's a hardware-specific thing, or something specific to my system entirely. I'm not sure though. I also went ahead and included an attachment of the photo I took of the error itself, maybe it'll help in some way. I'm also unsure if there's a package related to this bug, or what that package would be. Sorry. As for the last two things stated in the guidelines for reporting a bug, what I expected to happen was to see the error about my USB device along with some of the general jargon that pops up on boot that I typically don't have to worry about. Instead what happened is that based on what someone else told me, I found a bug in my kernel, although I'm not knowledgeable enough to know if it's a serious bug, or something that's really not that big of a deal. I'll leave that one up to you guys ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- Kubuntu 23.10: Kernel Bug Invoking Undefined Behavior on Boot https://bugs.launchpad.net/bugs/2045992 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 2038492] Re: workqueue: inode_switch_wbs_work_fn hogged CPU for >10000us 16 times, consider switching to WQ_UNBOUND
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-oem-6.5 (Ubuntu) Status: New => Confirmed -- 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/2038492 Title: workqueue: inode_switch_wbs_work_fn hogged CPU for >1us 16 times, consider switching to WQ_UNBOUND Status in linux-oem-6.5 package in Ubuntu: Confirmed Bug description: dmesg has multiple messages: [ 852.580542] evict_inodes inode be24a21a, i_count = 1, was skipped! [ 852.580543] evict_inodes inode 2aea522e, i_count = 1, was skipped! [ 852.580544] evict_inodes inode 48d75a5c, i_count = 1, was skipped! [ 852.580545] evict_inodes inode d8a9e4c2, i_count = 1, was skipped! [ 852.580546] evict_inodes inode 3d2c905c, i_count = 1, was skipped! [ 852.580547] evict_inodes inode e5b1b232, i_count = 1, was skipped! [ 852.580548] evict_inodes inode 97383a6b, i_count = 1, was skipped! [ 852.580549] evict_inodes inode ca8e2b44, i_count = 1, was skipped! [ 1751.869281] workqueue: inode_switch_wbs_work_fn hogged CPU for >1us 4 times, consider switching to WQ_UNBOUND [ 1781.467278] workqueue: inode_switch_wbs_work_fn hogged CPU for >1us 8 times, consider switching to WQ_UNBOUND [ 1806.065364] workqueue: inode_switch_wbs_work_fn hogged CPU for >1us 16 times, consider switching to WQ_UNBOUND [ 1901.993975] evict_inodes inode abaa740e, i_count = 1, was skipped! [ 1901.993981] evict_inodes inode 515b9bf8, i_count = 1, was skipped! [ 1901.993983] evict_inodes inode 1a69d536, i_count = 1, was skipped! [ 1901.993984] evict_inodes inode 1403f675, i_count = 1, was skipped! [ 1901.993985] evict_inodes inode 757de21a, i_count = 1, was skipped! [ 1901.993986] evict_inodes inode 0cee9028, i_count = 1, was skipped! [ 1901.993987] evict_inodes inode d2827e77, i_count = 1, was skipped! Description:Ubuntu 22.04.3 LTS Release:22.04 linux-oem-22.04d: Installed: 6.5.0.1004.4 Candidate: 6.5.0.1004.4 Seems related to #2037214 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.5/+bug/2038492/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2031412] Re: Support mipi camera on Intel Meteor Lake platform
** Tags removed: verification-done-mantic ** Tags added: verification-needed-mantic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2031412 Title: Support mipi camera on Intel Meteor Lake platform Status in HWE Next: New Status in ipu6-drivers package in Ubuntu: Fix Released Status in ivsc-driver package in Ubuntu: Fix Released Status in linux package in Ubuntu: Triaged Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-6.5 package in Ubuntu: Invalid Status in ipu6-drivers source package in Jammy: Won't Fix Status in ivsc-driver source package in Jammy: Won't Fix Status in linux source package in Jammy: Won't Fix Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-6.5 source package in Jammy: Fix Released Status in ipu6-drivers source package in Mantic: Fix Committed Status in ivsc-driver source package in Mantic: Fix Committed Status in linux source package in Mantic: Fix Committed Status in linux-firmware source package in Mantic: Fix Released Status in linux-oem-6.5 source package in Mantic: Invalid Status in ipu6-drivers source package in Noble: Fix Released Status in ivsc-driver source package in Noble: Fix Released Status in linux source package in Noble: Triaged Status in linux-firmware source package in Noble: Fix Released Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [SRU Justification] == ipu6-driver == [Impact] Missing Intel MIPI firmware for Meteor Lake platform. [Fix] Based on upstream tag https://github.com/intel/ipu6-drivers/releases/tag/Release_20231019, and an additional patch to enable/fix compilation of additional sensor modules. [Test Case] This is verified on MTL Lattice and VSC platforms, as well as previous generations e.g. TGL and ADL. To actually verify the camera framework: ``` # enable mantic-proposed, update the kernel, make sure you get 6.5.0-14.14 # reboot into the 6.5.0-14.14 kernel $ sudo apt install intel-ipu6-dkms intel-vsc-dkms $ sudo add-apt-repository ppa:oem-solutions-group/intel-ipu6 -y -u $ sudo apt install gstreamer1.0-icamera v4l2-relayd ``` In the above steps, make sure that only gstreamer1.0-icamera, v4l2-relayd, and their dependencies, are fetched from the oem-solutions-group PPA. Everything else must come from the mantic archive. And then browse https://webcamtests.com/ for testing. [Where problems could occur] This is a new platform. We've been verifying its functions and features, and are still polishing it. [Other Info] While Intel Meteor Lake is only supported by linux-oem-6.5/jammy and linux/mantic and on, and yet the lastest stable driver was verified after Mantic was released, it's being proposed to Noble instead. == ivsc-driver == [Impact] Missing Intel MIPI firmware for Meteor Lake platform. Need both firmware and driver change to probe the hardware correctly. [Fix] 4 commits from the latest trunk branch on upstream repository https://github.com/intel/ivsc-driver. [Test Case] With all other changes in position, Intel VSC driver modules are to be loaded as a soft dependency of some selected camera sensor modules. LJCA modules should be loaded automatically on MTL platforms as well. To actually verify the camera framework: ``` # enable mantic-proposed, update the kernel, make sure you get 6.5.0-14.14 # reboot into the 6.5.0-14.14 kernel $ sudo apt install intel-ipu6-dkms intel-vsc-dkms $ sudo add-apt-repository ppa:oem-solutions-group/intel-ipu6 -y -u $ sudo apt install gstreamer1.0-icamera v4l2-relayd ``` In the above steps, make sure that only gstreamer1.0-icamera, v4l2-relayd, and their dependencies, are fetched from the oem-solutions-group PPA. Everything else must come from the mantic archive. And then browse https://webcamtests.com/ for testing. [Where problems could occur] While it changes how LJCA modules match from ACPI ID, it's also tested and verified on previous generations using IVSC, e.g. TGL, ADL. [Other Info] While Intel Meteor Lake is only supported by linux-oem-6.5/jammy and linux/mantic and on, and yet the lastest stable driver was verified after Mantic was released, it's being proposed to Noble instead. == linux/linux-oem-6.5 == [Impact] Need kernel driver fixes for int3472/iommu for Intel IPU6 platform on MTL. [Fix] Two fixes in need. One, we need IOMMU passthrough for MTL platform. The other, fix is for handshake pin support for Lattice MIPI aggregator. The Intel IPU6 camera drivers are not yet all upstreamed yet. So far Intel VSC, LJCA (the previous MIPI aggregator for ADL/RPL platforms) are in v6.6 already, and IPU6 ISYS is under upstream review. More components to come
[Kernel-packages] [Bug 2031412] Re: Support mipi camera on Intel Meteor Lake platform
I just ran this command on my mantic laptop, according to the [test plan]: sudo add-apt-repository ppa:oem-solutions-group/intel-ipu6 -y -u And that PPA does not have mantic packages: Err:24 https://ppa.launchpadcontent.net/oem-solutions-group/intel-ipu6/ubuntu mantic Release 404 Not Found [IP: 185.125.190.80 443] Reading package lists... Done E: The repository 'https://ppa.launchpadcontent.net/oem-solutions-group/intel-ipu6/ubuntu mantic Release' does not have a Release file. How did you perform the mantic verification of this bug? -- 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/2031412 Title: Support mipi camera on Intel Meteor Lake platform Status in HWE Next: New Status in ipu6-drivers package in Ubuntu: Fix Released Status in ivsc-driver package in Ubuntu: Fix Released Status in linux package in Ubuntu: Triaged Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-6.5 package in Ubuntu: Invalid Status in ipu6-drivers source package in Jammy: Won't Fix Status in ivsc-driver source package in Jammy: Won't Fix Status in linux source package in Jammy: Won't Fix Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-6.5 source package in Jammy: Fix Released Status in ipu6-drivers source package in Mantic: Fix Committed Status in ivsc-driver source package in Mantic: Fix Committed Status in linux source package in Mantic: Fix Committed Status in linux-firmware source package in Mantic: Fix Released Status in linux-oem-6.5 source package in Mantic: Invalid Status in ipu6-drivers source package in Noble: Fix Released Status in ivsc-driver source package in Noble: Fix Released Status in linux source package in Noble: Triaged Status in linux-firmware source package in Noble: Fix Released Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [SRU Justification] == ipu6-driver == [Impact] Missing Intel MIPI firmware for Meteor Lake platform. [Fix] Based on upstream tag https://github.com/intel/ipu6-drivers/releases/tag/Release_20231019, and an additional patch to enable/fix compilation of additional sensor modules. [Test Case] This is verified on MTL Lattice and VSC platforms, as well as previous generations e.g. TGL and ADL. To actually verify the camera framework: ``` # enable mantic-proposed, update the kernel, make sure you get 6.5.0-14.14 # reboot into the 6.5.0-14.14 kernel $ sudo apt install intel-ipu6-dkms intel-vsc-dkms $ sudo add-apt-repository ppa:oem-solutions-group/intel-ipu6 -y -u $ sudo apt install gstreamer1.0-icamera v4l2-relayd ``` In the above steps, make sure that only gstreamer1.0-icamera, v4l2-relayd, and their dependencies, are fetched from the oem-solutions-group PPA. Everything else must come from the mantic archive. And then browse https://webcamtests.com/ for testing. [Where problems could occur] This is a new platform. We've been verifying its functions and features, and are still polishing it. [Other Info] While Intel Meteor Lake is only supported by linux-oem-6.5/jammy and linux/mantic and on, and yet the lastest stable driver was verified after Mantic was released, it's being proposed to Noble instead. == ivsc-driver == [Impact] Missing Intel MIPI firmware for Meteor Lake platform. Need both firmware and driver change to probe the hardware correctly. [Fix] 4 commits from the latest trunk branch on upstream repository https://github.com/intel/ivsc-driver. [Test Case] With all other changes in position, Intel VSC driver modules are to be loaded as a soft dependency of some selected camera sensor modules. LJCA modules should be loaded automatically on MTL platforms as well. To actually verify the camera framework: ``` # enable mantic-proposed, update the kernel, make sure you get 6.5.0-14.14 # reboot into the 6.5.0-14.14 kernel $ sudo apt install intel-ipu6-dkms intel-vsc-dkms $ sudo add-apt-repository ppa:oem-solutions-group/intel-ipu6 -y -u $ sudo apt install gstreamer1.0-icamera v4l2-relayd ``` In the above steps, make sure that only gstreamer1.0-icamera, v4l2-relayd, and their dependencies, are fetched from the oem-solutions-group PPA. Everything else must come from the mantic archive. And then browse https://webcamtests.com/ for testing. [Where problems could occur] While it changes how LJCA modules match from ACPI ID, it's also tested and verified on previous generations using IVSC, e.g. TGL, ADL. [Other Info] While Intel Meteor Lake is only
[Kernel-packages] [Bug 2046345] Re: package linux-modules-nvidia-535-6.5.0-9-generic 6.5.0-9.9 failed to install/upgrade: installed linux-modules-nvidia-535-6.5.0-9-generic package post-installation s
** Package changed: ubuntu => linux-restricted-modules (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/2046345 Title: package linux-modules-nvidia-535-6.5.0-9-generic 6.5.0-9.9 failed to install/upgrade: installed linux-modules-nvidia-535-6.5.0-9-generic package post-installation script subprocess returned error exit status 1 Status in linux-restricted-modules package in Ubuntu: New Bug description: Occurs when upgrading to an unreleased version Setting up linux-modules-nvidia-535-6.5.0-9-generic (6.5.0-9.9) ... linux-image-nvidia-6.5.0-9-generic: constructing .ko files make: arch/x86/Makefile.postlink: No such file or directory make: *** No rule to make target 'arch/x86/Makefile.postlink'. Stop. make: arch/x86/Makefile.postlink: No such file or directory make: *** No rule to make target 'arch/x86/Makefile.postlink'. Stop. make: arch/x86/Makefile.postlink: No such file or directory make: *** No rule to make target 'arch/x86/Makefile.postlink'. Stop. make: arch/x86/Makefile.postlink: No such file or directory make: *** No rule to make target 'arch/x86/Makefile.postlink'. Stop. make: arch/x86/Makefile.postlink: No such file or directory make: *** No rule to make target 'arch/x86/Makefile.postlink'. Stop. nvidia-drm.ko: FAILED nvidia-modeset.ko: FAILED nvidia-peermem.ko: OK nvidia-uvm.ko: FAILED nvidia.ko: FAILED sha256sum: WARNING: 4 computed checksums did NOT match dpkg: error processing package linux-modules-nvidia-535-6.5.0-9-generic (--configure): installed linux-modules-nvidia-535-6.5.0-9-generic package post-installation script subprocess returned error exit status 1 dpkg: dependency problems prevent configuration of linux-modules-nvidia-535-generic-hwe-22.04: linux-modules-nvidia-535-generic-hwe-22.04 depends on linux-modules-nvidia-535-6.5.0-9-generic (= 6.5.0-9.9); however: Package linux-modules-nvidia-535-6.5.0-9-generic is not configured yet. dpkg: error processing package linux-modules-nvidia-535-generic-hwe-22.04 (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of linux-modules-nvidia-530-generic-hwe-22.04: linux-modules-nvidia-530-generic-hwe-22.04 depends on linux-modules-nvidia-535-generic-hwe-22.04; however: Package linux-modules-nvidia-535-generic-hwe-22.04 is not configured yet. dpkg: error processing package linux-modules-nvidia-530-generic-hwe-22.04 (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: linux-modules-nvidia-535-6.5.0-9-generic linux-modules-nvidia-535-generic-hwe-22.04 linux-modules-nvidia-530-generic-hwe-22.04 ProblemType: Package DistroRelease: Ubuntu 24.04 Package: linux-modules-nvidia-535-6.5.0-9-generic 6.5.0-9.9 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.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Dec 13 14:36:34 2023 ErrorMessage: installed linux-modules-nvidia-535-6.5.0-9-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2023-02-17 (299 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Python3Details: /usr/bin/python3.11, Python 3.11.7, python3-minimal, 3.11.4-5 PythonDetails: /usr/bin/python3.11, Python 3.11.7, python-is-python3, 3.11.4-1 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.22.1ubuntu3 apt 2.7.6 SourcePackage: linux-restricted-modules Title: package linux-modules-nvidia-535-6.5.0-9-generic 6.5.0-9.9 failed to install/upgrade: installed linux-modules-nvidia-535-6.5.0-9-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to noble on 2023-12-13 (0 days ago) modified.conffile..etc.apport.report-ignore.README.denylist: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/2046345/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2046345] [NEW] package linux-modules-nvidia-535-6.5.0-9-generic 6.5.0-9.9 failed to install/upgrade: installed linux-modules-nvidia-535-6.5.0-9-generic package post-installation
You have been subscribed to a public bug: Occurs when upgrading to an unreleased version Setting up linux-modules-nvidia-535-6.5.0-9-generic (6.5.0-9.9) ... linux-image-nvidia-6.5.0-9-generic: constructing .ko files make: arch/x86/Makefile.postlink: No such file or directory make: *** No rule to make target 'arch/x86/Makefile.postlink'. Stop. make: arch/x86/Makefile.postlink: No such file or directory make: *** No rule to make target 'arch/x86/Makefile.postlink'. Stop. make: arch/x86/Makefile.postlink: No such file or directory make: *** No rule to make target 'arch/x86/Makefile.postlink'. Stop. make: arch/x86/Makefile.postlink: No such file or directory make: *** No rule to make target 'arch/x86/Makefile.postlink'. Stop. make: arch/x86/Makefile.postlink: No such file or directory make: *** No rule to make target 'arch/x86/Makefile.postlink'. Stop. nvidia-drm.ko: FAILED nvidia-modeset.ko: FAILED nvidia-peermem.ko: OK nvidia-uvm.ko: FAILED nvidia.ko: FAILED sha256sum: WARNING: 4 computed checksums did NOT match dpkg: error processing package linux-modules-nvidia-535-6.5.0-9-generic (--configure): installed linux-modules-nvidia-535-6.5.0-9-generic package post-installation script subprocess returned error exit status 1 dpkg: dependency problems prevent configuration of linux-modules-nvidia-535-generic-hwe-22.04: linux-modules-nvidia-535-generic-hwe-22.04 depends on linux-modules-nvidia-535-6.5.0-9-generic (= 6.5.0-9.9); however: Package linux-modules-nvidia-535-6.5.0-9-generic is not configured yet. dpkg: error processing package linux-modules-nvidia-535-generic-hwe-22.04 (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of linux-modules-nvidia-530-generic-hwe-22.04: linux-modules-nvidia-530-generic-hwe-22.04 depends on linux-modules-nvidia-535-generic-hwe-22.04; however: Package linux-modules-nvidia-535-generic-hwe-22.04 is not configured yet. dpkg: error processing package linux-modules-nvidia-530-generic-hwe-22.04 (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: linux-modules-nvidia-535-6.5.0-9-generic linux-modules-nvidia-535-generic-hwe-22.04 linux-modules-nvidia-530-generic-hwe-22.04 ProblemType: Package DistroRelease: Ubuntu 24.04 Package: linux-modules-nvidia-535-6.5.0-9-generic 6.5.0-9.9 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.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Dec 13 14:36:34 2023 ErrorMessage: installed linux-modules-nvidia-535-6.5.0-9-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2023-02-17 (299 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Python3Details: /usr/bin/python3.11, Python 3.11.7, python3-minimal, 3.11.4-5 PythonDetails: /usr/bin/python3.11, Python 3.11.7, python-is-python3, 3.11.4-1 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.22.1ubuntu3 apt 2.7.6 SourcePackage: linux-restricted-modules Title: package linux-modules-nvidia-535-6.5.0-9-generic 6.5.0-9.9 failed to install/upgrade: installed linux-modules-nvidia-535-6.5.0-9-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to noble on 2023-12-13 (0 days ago) modified.conffile..etc.apport.report-ignore.README.denylist: [deleted] ** Affects: linux-restricted-modules (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check noble third-party-packages -- package linux-modules-nvidia-535-6.5.0-9-generic 6.5.0-9.9 failed to install/upgrade: installed linux-modules-nvidia-535-6.5.0-9-generic package post-installation script subprocess returned error exit status 1 https://bugs.launchpad.net/bugs/2046345 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules 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 2046315] Re: oem-6.5: disable psr2 for some panels according to edid
** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2046315 Title: oem-6.5: disable psr2 for some panels according to edid Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: New Status in linux-oem-6.5 source package in Jammy: New Bug description: BugLink: https://bugs.launchpad.net/bugs/2046315 [Impact] On serveral Dell laptops, the screen often displays garbage or the screen is flicking [Fix] There is no real fix so far, ODM recommends to use a workaround to disable PSR2, this is a temp solution, after we get the real fix, we could revert the temp workaround. [Test case] booting with the patched kernel, If the pannel's edid is in the qurik list, the PSR2 will be disabled (checking /sys/kernel/debug/dri/0/i915_edp_psr_status; if the pannel's edid is not in the quirk list, the graphic driver will work as before. [Where problems could occur] It is possible that the temp solution couldn't work, then the screen will still show garbage and the screen is flicking, another possible regression is the screen has no problem before, but after running patched kernel, the PSR2 is disabled and the system cost more power, but this possibility is very low, I tested the patched on some dell machines, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2046315/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2046315] Re: oem-6.5: disable psr2 for some panels according to edid
is there an upstream bug for this? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2046315 Title: oem-6.5: disable psr2 for some panels according to edid Status in HWE Next: New Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux-oem-6.5 source package in Jammy: New Bug description: BugLink: https://bugs.launchpad.net/bugs/2046315 [Impact] On serveral Dell laptops, the screen often displays garbage or the screen is flicking [Fix] There is no real fix so far, ODM recommends to use a workaround to disable PSR2, this is a temp solution, after we get the real fix, we could revert the temp workaround. [Test case] booting with the patched kernel, If the pannel's edid is in the qurik list, the PSR2 will be disabled (checking /sys/kernel/debug/dri/0/i915_edp_psr_status; if the pannel's edid is not in the quirk list, the graphic driver will work as before. [Where problems could occur] It is possible that the temp solution couldn't work, then the screen will still show garbage and the screen is flicking, another possible regression is the screen has no problem before, but after running patched kernel, the PSR2 is disabled and the system cost more power, but this possibility is very low, I tested the patched on some dell machines, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2046315/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2046225] Re: The eDP OLED panel has no output on MTL platform
** Changed in: linux-oem-6.5 (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2046225 Title: The eDP OLED panel has no output on MTL platform Status in linux package in Ubuntu: In Progress Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux source package in Mantic: In Progress Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: In Progress Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] We got a blank screen when boot into the system with OLED panel. [Fix] Intel provides a patch to fix this https://patchwork.freedesktop.org/patch/570622/?series=127194=2 Which is in drm-intel-next currently 3072a24c778a drm/i915: Introduce crtc_state->enhanced_framing [Test case] 1. Install Ubuntu 22.04 on the system with 6.5+ kernel 2. Check the screen display normally [Where problems could occur] The eDP panel support v1.4 and later may fail if it require the non-standard DP_LINK_BW_SET. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2046225/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2045560] Re: TCP memory leak, slow network (arm64)
** Description changed: Hello! We have Ubuntu OS-based servers running in both AWS and Azure clouds. These servers are handling thousands of connections, and we've been experiencing issues with TCP memory usage since upgrading to Ubuntu - 22.04.3 from 22.04.2. This results in network slowdown + 22.04.3 from 22.04.2. $ cat /proc/net/sockstat sockets: used 6642 TCP: inuse 5962 orphan 0 tw 292 alloc 6008 mem 128989 UDP: inuse 5 mem 0 UDPLITE: inuse 0 RAW: inuse 0 FRAG: inuse 0 memory 0 As shown in the output below, even after stopping all possible services and closing all open connections, the TCP memory usage remains high and only decreases very slowly. $ cat /proc/net/sockstat sockets: used 138 TCP: inuse 2 orphan 0 tw 0 alloc 3 mem 128320 UDP: inuse 3 mem 0 UDPLITE: inuse 0 RAW: inuse 0 FRAG: inuse 0 memory 0 I have attached a screenshot of linear TCP memory usage growth, which we believe may indicate a TCP memory leak + + When net.ipv4.tcp_mem limit is reached, it causes network slowdown We've never had these issues before, and the only solution we've found so far is to reboot the node. Do you have any suggestions on how to troubleshoot further? Thank you for any help or guidance you can provide! ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-1015-aws 6.2.0-1015.15~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-1015.15~22.04.1-aws 6.2.16 Uname: Linux 6.2.0-1015-aws aarch64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: arm64 CasperMD5CheckResult: unknown CloudArchitecture: aarch64 CloudID: aws CloudName: aws CloudPlatform: ec2 CloudRegion: us-west-2 CloudSubPlatform: metadata (http://169.254.169.254) Date: Mon Dec 4 13:13:08 2023 Ec2AMI: ami-095a68e28e781dfe1 Ec2AMIManifest: (unknown) Ec2Architecture: arm64 Ec2AvailabilityZone: us-west-2b Ec2Imageid: ami-095a68e28e781dfe1 Ec2InstanceType: m7g.large Ec2Instancetype: m7g.large Ec2Kernel: unavailable Ec2Ramdisk: unavailable Ec2Region: us-west-2 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: linux-signed-aws-6.2 UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-aws-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2045560 Title: TCP memory leak, slow network (arm64) Status in linux-signed-aws-6.2 package in Ubuntu: Confirmed Bug description: Hello! We have Ubuntu OS-based servers running in both AWS and Azure clouds. These servers are handling thousands of connections, and we've been experiencing issues with TCP memory usage since upgrading to Ubuntu 22.04.3 from 22.04.2. $ cat /proc/net/sockstat sockets: used 6642 TCP: inuse 5962 orphan 0 tw 292 alloc 6008 mem 128989 UDP: inuse 5 mem 0 UDPLITE: inuse 0 RAW: inuse 0 FRAG: inuse 0 memory 0 As shown in the output below, even after stopping all possible services and closing all open connections, the TCP memory usage remains high and only decreases very slowly. $ cat /proc/net/sockstat sockets: used 138 TCP: inuse 2 orphan 0 tw 0 alloc 3 mem 128320 UDP: inuse 3 mem 0 UDPLITE: inuse 0 RAW: inuse 0 FRAG: inuse 0 memory 0 I have attached a screenshot of linear TCP memory usage growth, which we believe may indicate a TCP memory leak When net.ipv4.tcp_mem limit is reached, it causes network slowdown We've never had these issues before, and the only solution we've found so far is to reboot the node. Do you have any suggestions on how to troubleshoot further? Thank you for any help or guidance you can provide! ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-1015-aws 6.2.0-1015.15~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-1015.15~22.04.1-aws 6.2.16 Uname: Linux 6.2.0-1015-aws aarch64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: arm64 CasperMD5CheckResult: unknown CloudArchitecture: aarch64 CloudID: aws CloudName: aws CloudPlatform: ec2 CloudRegion: us-west-2 CloudSubPlatform: metadata (http://169.254.169.254) Date: Mon Dec 4 13:13:08 2023 Ec2AMI: ami-095a68e28e781dfe1 Ec2AMIManifest: (unknown) Ec2Architecture: arm64 Ec2AvailabilityZone: us-west-2b Ec2Imageid: ami-095a68e28e781dfe1 Ec2InstanceType: m7g.large Ec2Instancetype: m7g.large Ec2Kernel: unavailable Ec2Ramdisk: unavailable Ec2Region: us-west-2 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: linux-signed-aws-6.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to:
[Kernel-packages] [Bug 1972832] Re: [Azure] hv_netvsc: Add support for XDP_REDIRECT
Hi, I wanted to check if this is now on Azure. I set up a virtual machine where I want to use XDP_REDIRECT. I am getting an error with XDP_REDIRECT. I have given details of the issue [here](https://github.com/xdp-project/xdp-tools/issues/378). If this is already on Azure, what may be cause of the error? ** Bug watch added: github.com/xdp-project/xdp-tools/issues #378 https://github.com/xdp-project/xdp-tools/issues/378 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1972832 Title: [Azure] hv_netvsc: Add support for XDP_REDIRECT Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Impish: Fix Released Status in linux-azure source package in Jammy: Fix Released Bug description: SRU Justification [Impact] Add support for XDP_REDIRECT to the Azure Hyperv network driver. [Fix] https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net- next.git/commit/?id=1cb9d3b6185b2a4d1d592632a7faf5d8c8e5f9b3 [Where things could go wrong] User space requests to set XDP_REDIRECT could break packet routing. [Other Info] SF: #00336466 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1972832/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2045560] Re: TCP memory leak, slow network
We have confirmed that this issue only related to ARM64 architecture ** Summary changed: - Possible TCP memory leak + TCP memory leak, slow network ** Description changed: Hello! We have Ubuntu OS-based servers running in both AWS and Azure clouds. These servers are handling thousands of connections, and we've been experiencing issues with TCP memory usage since upgrading to Ubuntu - 22.04.3 from 22.04.2. + 22.04.3 from 22.04.2. This results in network slowdown $ cat /proc/net/sockstat sockets: used 6642 TCP: inuse 5962 orphan 0 tw 292 alloc 6008 mem 128989 UDP: inuse 5 mem 0 UDPLITE: inuse 0 RAW: inuse 0 FRAG: inuse 0 memory 0 As shown in the output below, even after stopping all possible services and closing all open connections, the TCP memory usage remains high and only decreases very slowly. $ cat /proc/net/sockstat sockets: used 138 TCP: inuse 2 orphan 0 tw 0 alloc 3 mem 128320 UDP: inuse 3 mem 0 UDPLITE: inuse 0 RAW: inuse 0 FRAG: inuse 0 memory 0 I have attached a screenshot of linear TCP memory usage growth, which we believe may indicate a TCP memory leak We've never had these issues before, and the only solution we've found so far is to reboot the node. Do you have any suggestions on how to troubleshoot further? Thank you for any help or guidance you can provide! ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-1015-aws 6.2.0-1015.15~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-1015.15~22.04.1-aws 6.2.16 Uname: Linux 6.2.0-1015-aws aarch64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: arm64 CasperMD5CheckResult: unknown CloudArchitecture: aarch64 CloudID: aws CloudName: aws CloudPlatform: ec2 CloudRegion: us-west-2 CloudSubPlatform: metadata (http://169.254.169.254) Date: Mon Dec 4 13:13:08 2023 Ec2AMI: ami-095a68e28e781dfe1 Ec2AMIManifest: (unknown) Ec2Architecture: arm64 Ec2AvailabilityZone: us-west-2b Ec2Imageid: ami-095a68e28e781dfe1 Ec2InstanceType: m7g.large Ec2Instancetype: m7g.large Ec2Kernel: unavailable Ec2Ramdisk: unavailable Ec2Region: us-west-2 ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - LANG=C.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + LANG=C.UTF-8 + SHELL=/bin/bash RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: linux-signed-aws-6.2 UpgradeStatus: No upgrade log present (probably fresh install) ** Summary changed: - TCP memory leak, slow network + TCP memory leak, slow network (arm64) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-aws-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2045560 Title: TCP memory leak, slow network (arm64) Status in linux-signed-aws-6.2 package in Ubuntu: Confirmed Bug description: Hello! We have Ubuntu OS-based servers running in both AWS and Azure clouds. These servers are handling thousands of connections, and we've been experiencing issues with TCP memory usage since upgrading to Ubuntu 22.04.3 from 22.04.2. $ cat /proc/net/sockstat sockets: used 6642 TCP: inuse 5962 orphan 0 tw 292 alloc 6008 mem 128989 UDP: inuse 5 mem 0 UDPLITE: inuse 0 RAW: inuse 0 FRAG: inuse 0 memory 0 As shown in the output below, even after stopping all possible services and closing all open connections, the TCP memory usage remains high and only decreases very slowly. $ cat /proc/net/sockstat sockets: used 138 TCP: inuse 2 orphan 0 tw 0 alloc 3 mem 128320 UDP: inuse 3 mem 0 UDPLITE: inuse 0 RAW: inuse 0 FRAG: inuse 0 memory 0 I have attached a screenshot of linear TCP memory usage growth, which we believe may indicate a TCP memory leak When net.ipv4.tcp_mem limit is reached, it causes network slowdown We've never had these issues before, and the only solution we've found so far is to reboot the node. Do you have any suggestions on how to troubleshoot further? Thank you for any help or guidance you can provide! ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-1015-aws 6.2.0-1015.15~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-1015.15~22.04.1-aws 6.2.16 Uname: Linux 6.2.0-1015-aws aarch64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: arm64 CasperMD5CheckResult: unknown CloudArchitecture: aarch64 CloudID: aws CloudName: aws CloudPlatform: ec2 CloudRegion: us-west-2 CloudSubPlatform: metadata (http://169.254.169.254) Date: Mon Dec 4 13:13:08 2023 Ec2AMI: ami-095a68e28e781dfe1 Ec2AMIManifest: (unknown) Ec2Architecture: arm64 Ec2AvailabilityZone: us-west-2b Ec2Imageid: ami-095a68e28e781dfe1 Ec2InstanceType: m7g.large Ec2Instancetype: m7g.large Ec2Kernel: unavailable Ec2Ramdisk: unavailable Ec2Region: us-west-2 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash
[Kernel-packages] [Bug 2045913] Re: Update the NVIDIA 535 driver
** Also affects: nvidia-graphics-drivers-535 (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-535 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-535 (Ubuntu Mantic) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-535 (Ubuntu Focal) Status: New => In Progress ** Changed in: nvidia-graphics-drivers-535 (Ubuntu Lunar) Status: New => In Progress ** Changed in: nvidia-graphics-drivers-535 (Ubuntu Mantic) Status: New => In Progress ** Changed in: nvidia-graphics-drivers-535 (Ubuntu Focal) Importance: Undecided => High ** Changed in: nvidia-graphics-drivers-535 (Ubuntu Lunar) Importance: Undecided => High ** Changed in: nvidia-graphics-drivers-535 (Ubuntu Mantic) Importance: Undecided => High ** Changed in: nvidia-graphics-drivers-535 (Ubuntu Focal) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: nvidia-graphics-drivers-535 (Ubuntu Lunar) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: nvidia-graphics-drivers-535 (Ubuntu Mantic) Assignee: (unassigned) => Alberto Milone (albertomilone) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-535 in Ubuntu. https://bugs.launchpad.net/bugs/2045913 Title: Update the NVIDIA 535 driver Status in nvidia-graphics-drivers-535 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-535 source package in Focal: In Progress Status in nvidia-graphics-drivers-535 source package in Lunar: In Progress Status in nvidia-graphics-drivers-535 source package in Mantic: In Progress Bug description: [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-535/+bug/2045913/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2028065] Re: Support for Intel Discrete Gale Peak2/BE200
Resume SRU while fix available as upstream commit ba1aa06f3747 ("Intel
Bluetooth: Update firmware file for Intel Bluetooth BE200").
linux-firmware SRU:
* https://lists.ubuntu.com/archives/kernel-team/2023-December/147571.html
(jammy)
* https://lists.ubuntu.com/archives/kernel-team/2023-December/147572.html
(mantic)
* https://lists.ubuntu.com/archives/kernel-team/2023-December/147573.html
(noble)
** Changed in: linux-firmware (Ubuntu Jammy)
Status: Incomplete => In Progress
** Changed in: linux-firmware (Ubuntu Mantic)
Status: Incomplete => In Progress
** Changed in: linux-firmware (Ubuntu)
Status: Fix Released => In Progress
** Changed in: linux-firmware (Ubuntu)
Assignee: (unassigned) => You-Sheng Yang (vicamo)
** Changed in: linux-firmware (Ubuntu)
Importance: Undecided => High
** Description changed:
[SRU Justification]
== linux-firmware ==
- [Impact]
+ [Impact]
+
+ Missing firmware for Intel BE200 on Intel Meteor Lake platform.
+
+ [Fix]
+
+ Needed firmware:
+ - WiFi:
+ * a6744df81a30 ("iwlwifi: add FWs for new GL and MA device types with
multiple RF modules")
+ - Bluetooth:
+ * 37761e2b861b ("Intel Bluetooth: Update firmware file for Intel Bluetooth
BE200")
+ * a5a6dded0c7f ("Intel Bluetooth: Update firmware file for Intel Bluetooth
BE200")
+ * ba1aa06f3747 ("Intel Bluetooth: Update firmware file for Intel Bluetooth
BE200")
+
+ The driver parts have been landed to linux-oem-6.5/jammy, linux/mantic and
+ linux/noble.
+
+ [Test Case]
+
+ Boot with firmware blobs installed, and iwlwifi and btintel should probe
+ successfully without error.
+
+ [Where problems could occur]
+
[Kernel-packages] [Bug 2000947] Re: UVC Quanta 0408:4035 camera PROBLEM
Thanks, I did, but same thing happens. Before error written in post #115, I got this message, but it's ok: ./compile_module.sh: line 25: cd: too many arguments mv: cannot stat 'uvc_driver.c': No such file or directory --2023-12-13 09:50:21-- https://raw.githubusercontent.com/Giuliano69/uvc_driver-for-Quanta-HD-User-Facing-0x0408-0x4035-/main/uvc_driver.c Resolving raw.githubusercontent.com (raw.githubusercontent.com)... 2606:50c0:8001::154, 2606:50c0:8003::154, 2606:50c0:8002::154, ... Connecting to raw.githubusercontent.com (raw.githubusercontent.com)|2606:50c0:8001::154|:443... connected. HTTP request sent, awaiting response... 200 OK Length: 85917 (84K) [text/plain] Saving to: ‘uvc_driver.c’ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2000947 Title: UVC Quanta 0408:4035 camera PROBLEM Status in linux package in Ubuntu: Confirmed Bug description: I bought a Acer Nitro 5 AN517-55 with Quanta ACER HD User Facing', USB 0408:4035. The camera is reported to have problems by many users: https://linux-hardware.org/?id=usb:0408-4035 The uvc camera Quanta 0408:4035 does not work with ubuntu 22,04. the camera is “recongized” but fails installation. My console commands report similar info to other users: https://unix.stackexchange.com/questions/723504/integrated-camera-not-detected-working-on-acer-nitro-5-an515-58 PROPOSED SOLUTION I got in contact with laurent.pinch...@ideasonboard.com and with riba...@chromium.org , and subscribed to https://www.linuxtv.org/lists. And me...@vger.kernel.org mailinglist. Laurent proposed me a fix and I modified the 5,15 uvc_driver.c version, and loaded it on github https://github.com/Giuliano69/uvc_driver-for-Quanta-HD-User- Facing-0x0408-0x4035-/blob/main/uvc_driver.c I offered to test the fix, so I tried to compile the module with the new source. COMPILING PROBLEMS I’m running **Ubuntu 22.04.1 LTS, with kernel giuliano@Astra2A:/usr/src$ cat /proc/version_signature Ubuntu 5.15.0-56.62-generic 5.15.64 BUT the linux-source that I found installed seems to be different tgiuliano@Astra2A:/usr/src$ ls -al linux-so* lrwxrwxrwx 1 root root 47 nov 22 16:08 linux-source-5.15.0.tar.bz2 -> linux-source-5.15.0/linux-source-5.15.0.tar.bz2 I expanded the tar file, configured the IDE and compiled without error any errors… I manually copied the uvcvideo.ko in /lib/modules/5.15.0-56- sudo cp…... then tryed to intall the new uvcvideo.ko module sudo rmmod uvcvideo && sudo modprobe uvcvideo BUT… IT FAILS giuliano@Astra2A:~$ sudo rmmod uvcvideo && sudo modprobe uvcvideo modprobe: ERROR: could not insert 'uvcvideo': Exec format error and dmesg shows [25961.151982] usbcore: registered new interface driver uvcvideo [26323.125534] usbcore: deregistering interface driver uvcvideo [26323.189294] uvcvideo: disagrees about version of symbol module_layout These are the TWO modinfo from the old and new uvcvideo modules https://pastebin.com/tSj8Exm6 Basically OLD module: vermagic: 5.15.0-56-generic SMP mod_unload modversions NEW module: vermagic: 5.15.64 SMP mod_unload modversions -kindly ASK HOW can FORCE the uvcdriver.c to match mi kernel version ? Have I got OTHER ways to make the kernel module I’m compiling, match my running system ? I would like to test the module so to confirm the patch and let it enter the kernel main stream... BR Giuliano PS btw…. to allow Eclipse to compile the kernel, I had to pass this commands scripts/config --disable CONFIG_SYSTEM_REVOCATION_KEYS scripts/config --disable SYSTEM_REVOCATION_KEYS scripts/config --disable SYSTEM_TRUSTED_KEYS hope that this does not affect the module layout & checking --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: giuliano 2142 F pulseaudio /dev/snd/pcmC1D0p: giuliano 2142 F...m pulseaudio /dev/snd/controlC0: giuliano 2142 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-11-03 (66 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Acer Nitro AN517-55 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-57-generic root=UUID=f07e25f9-07e7-4a29-a15e-f481aa0ee0f2 ro rootflags=subvol=@ quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-57.63-generic 5.15.74 RelatedPackageVersions: linux-restricted-modules-5.15.0-57-generic N/A
[Kernel-packages] [Bug 2039575] Re: SMC stats: Wrong bucket calculation for payload of exactly 4096 bytes
** Tags removed: verification-done-focal-linux-gcp-tcpx verification-done-jammy-linux verification-done-lunar-linux verification-done-mantic-linux verification-needed-focal-linux-gcp-5.15 verification-needed-jammy-linux-azure-fips verification-needed-jammy-linux-gkeop verification-needed-jammy-linux-hwe-6.2 verification-needed-jammy-linux-hwe-6.5 verification-needed-jammy-linux-intel-iotg verification-needed-jammy-linux-lowlatency verification-needed-jammy-linux-lowlatency-hwe-6.2 verification-needed-jammy-linux-nvidia-6.5 verification-needed-jammy-linux-nvidia-tegra verification-needed-lunar-linux-aws verification-needed-lunar-linux-azure verification-needed-lunar-linux-gcp verification-needed-lunar-linux-kvm verification-needed-lunar-linux-riscv verification-needed-lunar-linux-starfive verification-needed-mantic-linux-azure verification-needed-mantic-linux-gcp verification-needed-mantic-linux-laptop ** Tags added: verification-done -- 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/2039575 Title: SMC stats: Wrong bucket calculation for payload of exactly 4096 bytes Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Released Status in linux source package in Mantic: Fix Committed Bug description: SRU Justification: [Impact] * There is a wrong bucket calculation for payload of exactly 4096 bytes in SMC stats counters. * SMC_STAT_PAYLOAD_SUB and SMC_STAT_RMB_SIZE_SUB have these issues. * The impact is that a system silently updates an incorrect stats counter in case the underlying kernel is not UBSAN enabled. (Difficult to detect.) * But if a kernel is UBSAN enabled, one will see a UBSAN 'array-index-out-of-bounds' warning every time this occurs, like: [ 26.335381] UBSAN: array-index-out-of-bounds in /build/linux-O6Qi7m/linux-5.15.0/net/smc/af_smc.c:2402:3 [ 26.335385] index -1 is out of range for type 'u64 [9]' [ 26.335388] CPU: 0 PID: 274 Comm: iperf3 Tainted: G E 5.15.0-79-generic #86-Ubuntu [ 26.335391] Hardware name: IBM 8561 T01 772 (KVM/Linux) [ 26.335393] Call Trace: [ 26.335397] [] dump_stack_lvl+0x62/0x80 [ 26.335404] [ ] ubsan_epilogue+0x1c/0x48 [ 26.335406] [ ] __ubsan_handle_out_of_bounds+0x94/0xa0 [ 26.335411] [<03ff8033f9da>] smc_sendmsg+0x2aa/0x2d0 [smc] [ 26.335425] [ ] sock_sendmsg+0x64/0x80 [ 26.335431] [ ] sock_write_iter+0x72/0xa0 [ 26.335433] [ ] new_sync_write+0x100/0x190 [ 26.335438] [ ] vfs_write+0x1e8/0x280 [ 26.335440] [ ] ksys_write+0xb4/0x100 [ 26.335442] [ ] __do_syscall+0x1bc/0x1f0 [ 26.335446] [ ] system_call+0x78/0xa0 [Fix] * a950a5921db4 a950a5921db450c74212327f69950ff03419483a "net/smc: Fix pos miscalculation in statistics" [Test Plan] * Since this got identified while the livepatch for jammy patches got added, one could run a simiar (or the same) test like mentioned at LP#1639924 (but only jammy comes with official livepatch support). * Alternatively a dedicated SMC stats counters test with a payload of exactly 4096 bytes could be done (which is probably easier): * Install uperf (https://uperf.org/ - https://github.com/uperf/uperf). (Wondering if it makes sense to pick this up as Debian/Ubuntu package ?!) * Reset SMC-D stats on client and server side. * Start uperf at the server side using: # uperf -vs * Update profile with remote IP (server IP) and start uperf at client: # uperf -vai 5 -m rr1c-4kx4k---1.xml with uperf profile: # cat rr1c-4kx4k---1.xml * The smcd stats output is: # smcd -d stats reset SMC-D Connections Summary Total connections handled 2 SMC connections 2 (client 2, server 0) v1 0 v2 2 Handshake errors 0 (client 0, server 0) Avg requests per SMC conn 14.0 TCP fallback 0 (client 0, server 0) RX Stats Data transmitted (Bytes) 5796 (5.796K) Total requests 9 Buffer full 0 (0.00%) Buffer downgrades 0 Buffer reuses 0 8KB 16KB 32KB 64KB 128KB 256KB 512KB >512KB Bufs 0 0 0 2 0 0 0 1 Reqs 8 0 0 0 0 0 0 0 TX Stats Data transmitted (Bytes) 9960 (9.960K) Total requests 19 Buffer full 0 (0.00%) Buffer full (remote) 0 (0.00%) Buffer too small 0 (0.00%) Buffer too small (remote) 0 (0.00%) Buffer downgrades 0
[Kernel-packages] [Bug 2046184] Re: [arm64] Increase max CPU count to 512
** Changed in: linux-oracle (Ubuntu Jammy) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/2046184 Title: [arm64] Increase max CPU count to 512 Status in linux-oracle package in Ubuntu: In Progress Status in linux-oracle source package in Jammy: In Progress Status in linux-oracle source package in Mantic: In Progress Status in linux-oracle source package in Noble: In Progress Bug description: [Impact] * Request to accommodate new shape with 320 CPUs, greater than current max value of 256. [Fix] * Update CONFIG_NR_CPUS from 256 to 512 for arm64 arch. [Test Case] * Compile tested * Boot tested [Where things could go wrong] * Low chance of regression. Simple config change. [Other Info] * Change proposed in Debian unstable (https://salsa.debian.org/kernel-team/linux/-/merge_requests/937?commit_id=8dfba66465dbf4c3c8ef8998065805b852b34e22#fc973071e6f4da49be1ec7a17e00635dd41dcaf1), but was denied due to additional kernel size. This shouldn't affect Ubuntu kernel so much as it's compressed. * SF #00375112 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oracle/+bug/2046184/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2044096] Re: Support Cirrus CS35L41 codec on Dell Oasis 13/14/16 laptops
** 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-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2044096 Title: Support Cirrus CS35L41 codec on Dell Oasis 13/14/16 laptops Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux-oem-6.5 package in Ubuntu: New Status in linux source package in Jammy: Invalid Status in linux source package in Mantic: In Progress Status in linux source package in Noble: New Status in linux-oem-6.5 source package in Noble: New Bug description: [Impact] Built-in audio speaker function not working on new Dell Oasis 13/14/16 laptops [Fix] Need to backport https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=f0d9da19d7de9e845e7a93a901c4b9658df6b492 to support dual speaker configuration on Dell Oasis series [Test Case] 1. Power on the Dell Oasis 13/14/16 laptops with CS35L41 HDA. 2. Verify the audio functions, including playback and capture [Where problems could occur] Add CS35L41 support on specific Dell laptops. Risk of regression is low. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2044096/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2046315] Re: oem-6.5: disable psr2 for some panels according to edid
** Description changed: - is for tracking purpose. + BugLink: https://bugs.launchpad.net/bugs/2046315 + + [Impact] + On serveral Dell laptops, the screen often displays garbage or the screen is flicking + + [Fix] + There is no real fix so far, ODM recommends to use a workaround to disable PSR2, this is a temp solution, after we get the real fix, we could revert the temp workaround. + + + [Test case] + + booting with the patched kernel, If the pannel's edid is in the qurik + list, the PSR2 will be disabled (checking + /sys/kernel/debug/dri/0/i915_edp_psr_status; if the pannel's edid is not + in the quirk list, the graphic driver will work as before. + + [Where problems could occur] + It is possible that the temp solution couldn't work, then the screen will still show garbage and the screen is flicking, another possible regression is the screen has no problem before, but after running patched kernel, the PSR2 is disabled and the system cost more power, but this possibility is very low, I tested the patched on some dell machines, all worked well. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2046315 Title: oem-6.5: disable psr2 for some panels according to edid Status in HWE Next: New Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux-oem-6.5 source package in Jammy: New Bug description: BugLink: https://bugs.launchpad.net/bugs/2046315 [Impact] On serveral Dell laptops, the screen often displays garbage or the screen is flicking [Fix] There is no real fix so far, ODM recommends to use a workaround to disable PSR2, this is a temp solution, after we get the real fix, we could revert the temp workaround. [Test case] booting with the patched kernel, If the pannel's edid is in the qurik list, the PSR2 will be disabled (checking /sys/kernel/debug/dri/0/i915_edp_psr_status; if the pannel's edid is not in the quirk list, the graphic driver will work as before. [Where problems could occur] It is possible that the temp solution couldn't work, then the screen will still show garbage and the screen is flicking, another possible regression is the screen has no problem before, but after running patched kernel, the PSR2 is disabled and the system cost more power, but this possibility is very low, I tested the patched on some dell machines, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2046315/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
