[Kernel-packages] [Bug 2046184] Re: [arm64] Increase max CPU count to 512
** Changed in: linux-oracle (Ubuntu Mantic) Status: New => In Progress ** Changed in: linux-oracle (Ubuntu Mantic) 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: New Status in linux-oracle source package in Mantic: In Progress Status in linux-oracle source package in Noble: New 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 2043964] Re: New China SRRC compliance readiness check for Realtek WLAN
SRU: * https://kernel.ubuntu.com/gitea/kernel/jammy-linux-oem/pulls/103 (oem-6.5) * https://lists.ubuntu.com/archives/kernel-team/2023-December/147538.html (noble) -- 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 2045233] Re: [Ubuntu 22.04.04]: mpi3mr driver update request
Hi Jeff, Please include the below critical defects if enhancement is not possible: 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: [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:
[Kernel-packages] [Bug 2043964] Re: New China SRRC compliance readiness check for Realtek WLAN
** Description changed: + [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. + - 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 + - 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 + - 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] ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Status: Triaged => In Progress ** Changed in: linux (Ubuntu Noble) Status: New => In Progress ** Changed in: linux (Ubuntu Noble) Importance: Undecided => High ** Changed in: linux (Ubuntu Noble) Assignee: (unassigned) => You-Sheng Yang (vicamo) -- 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
[Kernel-packages] [Bug 2045233] Re: [Ubuntu 22.04.04]: mpi3mr driver update request
The cutoff is January 3 for patch submission. And We are closed for the holidays after this friday. I do not nkow that these are going to make 22.04.4 initially. -- 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 2044589] Re: [Ubuntu 24.04 LTS] mpi3mr: Add support for SAS5116 controller and include critical fixes
Hi Jeff, We have a few more critical bug fixes patches and one feature update. Below are the commit IDs: 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/2044589 Title: [Ubuntu 24.04 LTS] mpi3mr: Add support for SAS5116 controller and include critical fixes Status in linux package in Ubuntu: Confirmed Status in linux source package in Noble: Confirmed Bug description: This request is to add support for SAS5116 controller and few critical bug-fixes in Ubuntu 24.04 LTS. Below is the list of upstream commits that adds support for SAS5116: 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2044589/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
Thank you, Jeff. We have a few more critical bug fixes patches and one feature update. And below are the commit IDs: 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: [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
[Kernel-packages] [Bug 2046071] Re: Brightness control is inoperative
5.15.0-25-generic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2046071 Title: Brightness control is inoperative Status in linux-signed-hwe-6.2 package in Ubuntu: Incomplete Bug description: I can't control the brightness at, be it from the fn buttons or the GUI. The brightness is set to the max level with any way to lower it or control it. This problem doesn't exist in older kernels. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-37-generic 6.2.0-37.38~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Dec 10 17:48:35 2023 InstallationDate: Installed on 2023-12-07 (3 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2046071/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039211] Re: nf_nat and macvlan
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2039211 Title: nf_nat and macvlan Status in linux package in Ubuntu: Expired Bug description: [114596.323853] [ cut here ] [114596.323855] WARNING: CPU: 1 PID: 46587 at net/netfilter/nf_nat_core.c:678 nf_nat_setup_info+0x30e/0x360 [nf_nat] [114596.323865] Modules linked in: tls xt_nat xt_tcpudp xt_conntrack nft_chain_nat xt_MASQUERADE nf_nat nf_conntrack_netlink nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xfrm_user xfrm_algo xt_addrtype nft_compat nf_tables nfnetlink br_netfilter rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache netfs overlay macvlan bridge stp llc cfg80211 sunrpc binfmt_misc nls_iso8859_1 intel_rapl_msr intel_rapl_common hyperv_fb serio_raw joydev mac_hid hv_balloon vmgenid msr parport_pc ppdev lp dm_multipath parport efi_pstore dmi_sysfs ip_tables x_tables autofs4 btrfs blake2b_generic raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear hyperv_drm drm_shmem_helper hid_generic drm_kms_helper hid_hyperv drm hid hv_storvsc hyperv_keyboard hv_netvsc scsi_transport_fc hv_utils crct10dif_pclmul crc32_pclmul polyval_clmulni polyval_generic ghash_clmulni_intel aesni_intel crypto_simd cryptd hv_vmbus [114596.323907] CPU: 1 PID: 46587 Comm: kworker/u4:3 Tainted: GB W 6.5.0-9-generic #9-Ubuntu [114596.323909] Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS Hyper-V UEFI Release v4.1 04/06/2022 [114596.323910] Workqueue: events_unbound macvlan_process_broadcast [macvlan] [114596.323914] RIP: 0010:nf_nat_setup_info+0x30e/0x360 [nf_nat] [114596.323919] Code: 8b bb b0 00 00 00 48 83 c8 20 48 89 83 80 00 00 00 48 85 ff 0f 84 d2 fe ff ff 0f b6 07 84 c0 0f 85 75 fe ff ff e9 bb fe ff ff <0f> 0b 31 c0 e9 d2 fe ff ff ba 20 08 00 00 be 02 00 00 00 48 89 df [114596.323920] RSP: 0018:acc1ebd0 EFLAGS: 00010202 [114596.323921] RAX: 0080 RBX: 9773847b0200 RCX: [114596.323922] RDX: RSI: acc1ec8c RDI: 9773847b0200 [114596.323923] RBP: acc1ec70 R08: 2d00a8c0 R09: [114596.323924] R10: R11: R12: [114596.323925] R13: 9075ec40 R14: acc1ec8c R15: 9773847b0200 [114596.323925] FS: () GS:97737fb0() knlGS: [114596.323926] CS: 0010 DS: ES: CR0: 80050033 [114596.323927] CR2: 2a8952d9d000 CR3: 44532000 CR4: 00350ee0 [114596.323929] Call Trace: [114596.323931] [114596.323933] ? show_regs+0x6d/0x80 [114596.323936] ? __warn+0x89/0x160 [114596.323939] ? nf_nat_setup_info+0x30e/0x360 [nf_nat] [114596.323944] ? report_bug+0x17e/0x1b0 [114596.323947] ? handle_bug+0x51/0xa0 [114596.323950] ? exc_invalid_op+0x18/0x80 [114596.323952] ? asm_exc_invalid_op+0x1b/0x20 [114596.323955] ? nf_nat_setup_info+0x30e/0x360 [nf_nat] [114596.323959] __nf_nat_alloc_null_binding+0x5e/0x90 [nf_nat] [114596.323963] nf_nat_inet_fn+0x2da/0x350 [nf_nat] [114596.323967] nf_nat_ipv4_local_in+0x59/0x140 [nf_nat] [114596.323971] nf_hook_slow+0x43/0xd0 [114596.323974] ip_local_deliver+0xe1/0x120 [114596.323977] ? __pfx_ip_local_deliver_finish+0x10/0x10 [114596.323978] ip_rcv+0x175/0x190 [114596.323980] ? __pfx_ip_rcv_finish+0x10/0x10 [114596.323982] __netif_receive_skb_one_core+0x91/0xa0 [114596.323985] __netif_receive_skb+0x15/0x60 [114596.323987] process_backlog+0x8e/0x150 [114596.323989] __napi_poll+0x30/0x1f0 [114596.323990] net_rx_action+0x181/0x2e0 [114596.323993] __do_softirq+0xd6/0x346 [114596.323995] do_softirq.part.0+0x41/0x80 [114596.323997] [114596.323998] [114596.323999] __local_bh_enable_ip+0x72/0x80 [114596.324001] netif_rx+0xec/0x100 [114596.324002] macvlan_broadcast+0x102/0x1d0 [macvlan] [114596.324006] macvlan_multicast_rx+0x66/0x80 [macvlan] [114596.324009] macvlan_process_broadcast+0xe9/0x160 [macvlan] [114596.324012] process_one_work+0x220/0x440 [114596.324014] worker_thread+0x4d/0x3f0 [114596.324016] ? _raw_spin_unlock_irqrestore+0x11/0x60 [114596.324017] ? __pfx_worker_thread+0x10/0x10 [114596.324018] kthread+0xef/0x120 [114596.324021] ? __pfx_kthread+0x10/0x10 [114596.324022] ret_from_fork+0x44/0x70 [114596.324025] ? __pfx_kthread+0x10/0x10 [114596.324027] ret_from_fork_asm+0x1b/0x30 [114596.324029] [114596.324029] ---[ end trace ]--- ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: linux-image-6.5.0-9-generic 6.5.0-9.9
[Kernel-packages] [Bug 2039409] Re: System freezes with UBSAN: array-index-out-of-bounds in iwlwifi code
Seeing an index-out-of-bounds exception in the same file on the same line on Ubuntu 20.04 (5.15.0-89-generic): UBSAN: array-index-out-of-bounds in /build/linux-hwe-5.15-QQdkfv/linux-hwe-5.15-5.15.0/debian/build/build-generic/__dkms/build/backport-iwlwifi/9858/build/drivers/net/wireless/intel/iwlwifi/queue/tx.c:1556:39 Followed by a lockup: watchdog: BUG: soft lockup - CPU#1 stuck for 26s! [irq/167-iwlwifi:1465] -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2039409 Title: System freezes with UBSAN: array-index-out-of-bounds in iwlwifi code Status in linux-signed-hwe-6.2 package in Ubuntu: Confirmed Bug description: System consistently freezes requiring hard reset every few hours. Syslog gives this message at the time of the crash: UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.2-d7iZ5S/linux- hwe-6.2-6.2.0/drivers/net/wireless/intel/iwlwifi/queue/tx.c:1556:39 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-34-generic 6.2.0-34.34~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-34.34~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Oct 15 21:38:57 2023 InstallationDate: Installed on 2021-05-15 (883 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: Upgraded to jammy on 2022-11-28 (322 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2039409/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2046192] [NEW] Disable Legacy TIOCSTI
Public bug reported: [Impact] >From the config option description: Historically the kernel has allowed TIOCSTI, which will push characters into a controlling TTY. This continues to be used as a malicious privilege escalation mechanism, and provides no meaningful real-world utility any more. Its use is considered a dangerous legacy operation, and can be disabled on most systems. [Test case] Test that TIOCSTI is not allowed by unprivileged user, while still allowed by CAP_SYS_ADMIN. [Potential regression] Programs relying on TIOCSTI may break. ** Affects: linux (Ubuntu) Importance: Medium Assignee: Thadeu Lima de Souza Cascardo (cascardo) Status: In Progress ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo) ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2046192 Title: Disable Legacy TIOCSTI Status in linux package in Ubuntu: In Progress Bug description: [Impact] From the config option description: Historically the kernel has allowed TIOCSTI, which will push characters into a controlling TTY. This continues to be used as a malicious privilege escalation mechanism, and provides no meaningful real-world utility any more. Its use is considered a dangerous legacy operation, and can be disabled on most systems. [Test case] Test that TIOCSTI is not allowed by unprivileged user, while still allowed by CAP_SYS_ADMIN. [Potential regression] Programs relying on TIOCSTI may break. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2046192/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2033735] Re: No HDMI in Nvidia on-demand mode
Sorry but now I use a new classical Intel-only laptop so I cannot help
anymore.
--
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/2033735
Title:
No HDMI in Nvidia on-demand mode
Status in linux package in Ubuntu:
Confirmed
Status in nvidia-graphics-drivers-535 package in Ubuntu:
Confirmed
Bug description:
Hi,
Legion laptop with Nvidia.
- Nouveau : no hdmi
- Nvidia 535 dynamic graphics : no HDMI (screen not detected)
- Nvidia 535 discrete graphics : HDMI is detected
So I suppose this bug to be linked to Intel GPU.
All was ok with previous 6.3 kernel.
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: fthx 3395 F wireplumber
/dev/snd/controlC1: fthx 3395 F wireplumber
/dev/snd/seq:fthx 3390 F pipewire
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2021-09-15 (723 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210910)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
NonfreeKernelModules: nvidia_modeset nvidia
Package: linux (not installed)
ProcEnviron:
LANG=fr_FR.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-5-generic
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
RelatedPackageVersions:
linux-restricted-modules-6.5.0-5-generic N/A
linux-backports-modules-6.5.0-5-generic N/A
linux-firmware 20230815.git0e048b06-0ubuntu1
Tags: mantic wayland-session
Uname: Linux 6.5.0-5-generic x86_64
UpgradeStatus: Upgraded to mantic on 2023-03-06 (186 days ago)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers
_MarkForUpload: True
dmi.bios.date: 07/10/2023
dmi.bios.release: 1.54
dmi.bios.vendor: LENOVO
dmi.bios.version: J2CN54WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76461 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Legion 5 Pro 16IAH7H
dmi.ec.firmware.release: 1.54
dmi.modalias:
dmi:bvnLENOVO:bvrJ2CN54WW:bd07/10/2023:br1.54:efr1.54:svnLENOVO:pn82RF:pvrLegion5Pro16IAH7H:rvnLENOVO:rnLNVNB161216:rvrSDK0T76461WIN:cvnLENOVO:ct10:cvrLegion5Pro16IAH7H:skuLENOVO_MT_82RF_BU_idea_FM_Legion5Pro16IAH7H:
dmi.product.family: Legion 5 Pro 16IAH7H
dmi.product.name: 82RF
dmi.product.sku: LENOVO_MT_82RF_BU_idea_FM_Legion 5 Pro 16IAH7H
dmi.product.version: Legion 5 Pro 16IAH7H
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033735/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2033735] Re: No HDMI in Nvidia on-demand mode
I have the exact same Lenovo model, with the same BIOS version.
Tested on Ubuntu 23.10 with kernel 6.6.6, with nvidia driver version
545.29.06 (both the proprietary and open modules), on Wayland and X,
using HDMI or DP.
When "on-demand", there is no HDMI and no option to launch with dGPU. I
do get the same exact messages as here
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033735/comments/39.
--
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/2033735
Title:
No HDMI in Nvidia on-demand mode
Status in linux package in Ubuntu:
Confirmed
Status in nvidia-graphics-drivers-535 package in Ubuntu:
Confirmed
Bug description:
Hi,
Legion laptop with Nvidia.
- Nouveau : no hdmi
- Nvidia 535 dynamic graphics : no HDMI (screen not detected)
- Nvidia 535 discrete graphics : HDMI is detected
So I suppose this bug to be linked to Intel GPU.
All was ok with previous 6.3 kernel.
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: fthx 3395 F wireplumber
/dev/snd/controlC1: fthx 3395 F wireplumber
/dev/snd/seq:fthx 3390 F pipewire
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2021-09-15 (723 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210910)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
NonfreeKernelModules: nvidia_modeset nvidia
Package: linux (not installed)
ProcEnviron:
LANG=fr_FR.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-5-generic
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
RelatedPackageVersions:
linux-restricted-modules-6.5.0-5-generic N/A
linux-backports-modules-6.5.0-5-generic N/A
linux-firmware 20230815.git0e048b06-0ubuntu1
Tags: mantic wayland-session
Uname: Linux 6.5.0-5-generic x86_64
UpgradeStatus: Upgraded to mantic on 2023-03-06 (186 days ago)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers
_MarkForUpload: True
dmi.bios.date: 07/10/2023
dmi.bios.release: 1.54
dmi.bios.vendor: LENOVO
dmi.bios.version: J2CN54WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76461 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Legion 5 Pro 16IAH7H
dmi.ec.firmware.release: 1.54
dmi.modalias:
dmi:bvnLENOVO:bvrJ2CN54WW:bd07/10/2023:br1.54:efr1.54:svnLENOVO:pn82RF:pvrLegion5Pro16IAH7H:rvnLENOVO:rnLNVNB161216:rvrSDK0T76461WIN:cvnLENOVO:ct10:cvrLegion5Pro16IAH7H:skuLENOVO_MT_82RF_BU_idea_FM_Legion5Pro16IAH7H:
dmi.product.family: Legion 5 Pro 16IAH7H
dmi.product.name: 82RF
dmi.product.sku: LENOVO_MT_82RF_BU_idea_FM_Legion 5 Pro 16IAH7H
dmi.product.version: Legion 5 Pro 16IAH7H
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033735/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2042877] Re: kernel: r8169 0000:0d:00.0 enp13s0: rtl_rxtx_empty_cond == 0 (loop: 42, delay: 100).
I download and installed the r8168-dkms package, and it failed again. See dmesg log: [ 196.896686] [ cut here ] [ 196.896689] NETDEV WATCHDOG: enp16s0 (r8169): transmit queue 0 timed out [ 196.896698] WARNING: CPU: 20 PID: 0 at net/sched/sch_generic.c:525 dev_watchdog+0x21f/0x230 [ 196.896706] Modules linked in: ccm nf_conntrack_netlink xfrm_user xfrm_algo xt_addrtype br_netfilter xfs xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp nft_compat nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nf_tables nfnetlink bridge stp llc overlay snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio intel_rapl_msr intel_rapl_common snd_hda_codec_hdmi rtw88_8822bu mt7921e binfmt_misc rtw88_usb edac_mce_amd mt7921_common rtw88_8822b uvcvideo mt76_connac_lib snd_hda_intel snd_usb_audio snd_intel_dspcfg rtw88_core videobuf2_vmalloc mt76 snd_usbmidi_lib snd_intel_sdw_acpi videobuf2_memops kvm_amd snd_seq_midi snd_hda_codec videobuf2_v4l2 nls_iso8859_1 mac80211 snd_seq_midi_event videodev snd_hda_core kvm videobuf2_common snd_rawmidi snd_hwdep irqbypass snd_seq input_leds mc rapl gigabyte_wmi wmi_bmof snd_pcm cfg80211 k10temp snd_seq_device ccp snd_timer snd libarc4 soundcore mac_hid sch_fq_codel msr parport_pc ppdev lp parport efi_ pstore [ 196.896795] ip_tables x_tables autofs4 dm_crypt raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear amdgpu hid_generic iommu_v2 drm_buddy gpu_sched i2c_algo_bit drm_ttm_helper ttm usbhid drm_display_helper hid cec rc_core drm_kms_helper r8125(OE) syscopyarea sysfillrect crct10dif_pclmul crc32_pclmul sysimgblt polyval_clmulni polyval_generic ghash_clmulni_intel sha512_ssse3 aesni_intel crypto_simd nvme cryptd ahci r8169 drm xhci_pci i2c_piix4 libahci xhci_pci_renesas nvme_core realtek nvme_common video wmi [ 196.896856] CPU: 20 PID: 0 Comm: swapper/20 Tainted: GW OE 6.2.0-37-generic #38~22.04.1-Ubuntu [ 196.896859] Hardware name: Gigabyte Technology Co., Ltd. X670 AORUS ELITE AX/X670 AORUS ELITE AX, BIOS F20a 11/10/2023 [ 196.896861] RIP: 0010:dev_watchdog+0x21f/0x230 [ 196.896864] Code: 00 e9 31 ff ff ff 4c 89 e7 c6 05 d9 5f 78 01 01 e8 e6 ff f7 ff 44 89 f1 4c 89 e6 48 c7 c7 b8 8c 64 8b 48 89 c2 e8 81 c3 2b ff <0f> 0b e9 22 ff ff ff 66 2e 0f 1f 84 00 00 00 00 00 90 90 90 90 90 [ 196.896867] RSP: 0018:b813806a0e70 EFLAGS: 00010246 [ 196.896869] RAX: RBX: 9a4f60e804c8 RCX: [ 196.896871] RDX: RSI: RDI: [ 196.896872] RBP: b813806a0e98 R08: R09: [ 196.896874] R10: R11: R12: 9a4f60e8 [ 196.896875] R13: 9a4f60e8041c R14: R15: [ 196.896877] FS: () GS:9a565e50() knlGS: [ 196.896879] CS: 0010 DS: ES: CR0: 80050033 [ 196.896880] CR2: 3887d2229000 CR3: 00017421 CR4: 00750ee0 [ 196.896882] PKRU: 5554 [ 196.896884] Call Trace: [ 196.896886] [ 196.896889] ? show_regs+0x72/0x90 [ 196.896894] ? dev_watchdog+0x21f/0x230 [ 196.896897] ? __warn+0x8d/0x160 [ 196.896901] ? dev_watchdog+0x21f/0x230 [ 196.896904] ? report_bug+0x1bb/0x1d0 [ 196.896909] ? handle_bug+0x46/0x90 [ 196.896913] ? exc_invalid_op+0x19/0x80 [ 196.896915] ? asm_exc_invalid_op+0x1b/0x20 [ 196.896923] ? dev_watchdog+0x21f/0x230 [ 196.896926] ? __pfx_dev_watchdog+0x10/0x10 [ 196.896929] call_timer_fn+0x2c/0x160 [ 196.896934] ? __pfx_dev_watchdog+0x10/0x10 [ 196.896936] __run_timers.part.0+0x1fb/0x2b0 [ 196.896940] ? ktime_get+0x46/0xc0 [ 196.896942] ? __pfx_tick_sched_timer+0x10/0x10 [ 196.896945] ? srso_alias_return_thunk+0x5/0x7f [ 196.896949] ? srso_alias_return_thunk+0x5/0x7f [ 196.896952] ? lapic_next_event+0x20/0x30 [ 196.896956] ? srso_alias_return_thunk+0x5/0x7f [ 196.896959] ? clockevents_program_event+0xb5/0x140 [ 196.896963] run_timer_softirq+0x2a/0x60 [ 196.896966] __do_softirq+0xdd/0x330 [ 196.896969] ? hrtimer_interrupt+0x12b/0x250 [ 196.896974] __irq_exit_rcu+0xa2/0xd0 [ 196.896977] irq_exit_rcu+0xe/0x20 [ 196.896979] sysvec_apic_timer_interrupt+0x96/0xb0 [ 196.896982] [ 196.896984] [ 196.896985] asm_sysvec_apic_timer_interrupt+0x1b/0x20 [ 196.896988] RIP: 0010:cpuidle_enter_state+0xde/0x6f0 [ 196.896993] Code: 4f 71 75 e8 94 1a 45 ff 8b 53 04 49 89 c7 0f 1f 44 00 00 31 ff e8 92 f8 43 ff 80 7d d0 00 0f 85 e8 00 00 00 fb 0f 1f 44 00 00 <45> 85 f6 0f 88 0f 02 00 00 4d 63 ee 49 83 fd 09 0f 87 c4 04 00 00 [ 196.896994] RSP: 0018:b8138022fe28 EFLAGS: 0246 [ 196.896997] RAX: RBX: 9a4f44e95c00 RCX: [ 196.896998] RDX: 0014 RSI: RDI: [ 196.897000] RBP: b8138022fe78 R08:
[Kernel-packages] [Bug 2037214] Re: evict_inodes inode xxx, i_count = 1, was skipped!
It happens each time btrfs usb external drive is mounted, also happens
for ext4 - the same drive, same usb cage. Using systemd-automount.
Linux nas 6.5.0-14-generic
Bus 002 Device 002: ID 174c:1153 ASMedia Technology Inc. ASM1153 SATA
3Gb/s bridge
[397017.384016] BTRFS: device fsid 98b21b16-ff76-4606-b091-117dd57fc825 devid 1
transid 1629 /dev/sdf1 scanned by mount (88452)
[397017.385233] BTRFS info (device sdf1): using crc32c (crc32c-intel) checksum
algorithm
[397017.385251] BTRFS info (device sdf1): using free space tree
[397099.871588] evict_inodes inode ec798847, i_count = 1, was skipped!
[397099.871593] evict_inodes inode cdbf17cc, i_count = 1, was skipped!
[397099.871594] evict_inodes inode 90c65438, i_count = 1, was skipped!
[397099.871596] evict_inodes inode 846a60bd, i_count = 1, was skipped!
[397099.871598] evict_inodes inode 23687c6b, i_count = 1, was skipped!
[397099.871598] evict_inodes inode bb13ceca, i_count = 1, was skipped!
[397099.871602] evict_inodes inode 60410da0, i_count = 1, was skipped!
[397099.871603] evict_inodes inode bfed6dcf, i_count = 1, was skipped!
[397099.871603] evict_inodes inode 9348343d, i_count = 1, was skipped!
[397099.871607] evict_inodes inode a5321882, i_count = 1, was skipped!
[397099.871611] evict_inodes inode 49062c28, i_count = 1, was skipped!
[397099.871611] evict_inodes inode f6e484ef, i_count = 1, was skipped!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2037214
Title:
evict_inodes inode xxx, i_count = 1, was skipped!
Status in linux package in Ubuntu:
Confirmed
Status in linux-oem-6.5 package in Ubuntu:
Confirmed
Bug description:
Hi,
during boot the kernel logs the following messages:
# dmesg | grep evict_inodes
[ 12.784805] evict_inodes inode d69da69b, i_count = 1, was skipped!
[ 12.784810] evict_inodes inode 8b9a7c55, i_count = 1, was skipped!
[ 12.784811] evict_inodes inode 8ff8e64c, i_count = 1, was skipped!
[ 12.784811] evict_inodes inode 194d080e, i_count = 1, was skipped!
[ 12.784812] evict_inodes inode 09b77b7b, i_count = 1, was skipped!
[ 12.811217] evict_inodes inode ec873c71, i_count = 1, was skipped!
[ 12.811222] evict_inodes inode 72bf501d, i_count = 1, was skipped!
[ 12.811223] evict_inodes inode b42b829a, i_count = 1, was skipped!
[ 12.811224] evict_inodes inode c7c5b4ef, i_count = 1, was skipped!
[ 13.412667] evict_inodes inode 61a23a39, i_count = 1, was skipped!
[ 13.412671] evict_inodes inode b42b829a, i_count = 1, was skipped!
[ 13.412671] evict_inodes inode 72bf501d, i_count = 1, was skipped!
[ 13.412672] evict_inodes inode c7c5b4ef, i_count = 1, was skipped!
[ 13.412673] evict_inodes inode ec873c71, i_count = 1, was skipped!
Those messages are not displayed when I boot my system with a mainline Linux
kernel.
Moreover, in the mainline Linux source code, I do not find the lines where
such a message could be printed.
Therefore, those messages are probably caused by an Ubuntu patch.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-5-generic 6.5.0-5.5
ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
Uname: Linux 6.5.0-5-generic x86_64
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: bonnaudl 4827 F wireplumber
/dev/snd/seq:bonnaudl 4808 F pipewire
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Sun Sep 24 14:39:10 2023
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-5-generic
root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor
tpm_tis.interrupts=0 preempt=full split_lock_detect=off quiet splash
vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.5.0-5-generic N/A
linux-backports-modules-6.5.0-5-generic N/A
linux-firmware 20230919.git3672ccab-0ubuntu2
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/26/2022
dmi.bios.release: 7.16
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: 1.07.16NRTR4
dmi.board.asset.tag: Tag 12345
dmi.board.name: NS50_70MU
dmi.board.vendor: TUXEDO
dmi.board.version: Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Notebook
dmi.chassis.version: N/A
dmi.ec.firmware.release: 7.7
dmi.modalias:
[Kernel-packages] [Bug 2046184] [NEW] [arm64] Increase max CPU count to 512
Public bug reported: [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 ** Affects: linux-oracle (Ubuntu) Importance: Undecided Status: New ** Affects: linux-oracle (Ubuntu Mantic) Importance: Undecided Status: New ** Affects: linux-oracle (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux-oracle (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux-oracle (Ubuntu Mantic) Importance: Undecided Status: New ** Description changed: [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 + * 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 its compressed. * SF #00366439 ** Description changed: [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 its compressed. - * SF #00366439 + * SF #00375112 ** Description changed: [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 its compressed. + * 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 -- 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: New Status in linux-oracle source package in Mantic: New Status in linux-oracle source package in Noble: New 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 2030100] Re: zfs-dkms 2.1.5-1ubuntu6~22.04.1: zfs kernel module failed to build
@cement_head - This is what I did just yesterday to solve the issue. I am using kernel Linux 6.2.0-37-generic x86_64 on Ubuntu 22.04. Mind you, my ZFS pool is *not* on the same disk that is running my OS. That disk runs ext4 and I have six disks in a raidz2-0 array that I use for storage. If you are running a kernel put out by one of the Ubuntu apt repo's like I am, then you can do the following: - Write down the names of each of your ZFS pools (for instance, I have one called "z-storage" in a raidz2-0 array) - Uninstall the zfs-dkms package from the Ubuntu repos since it only handles kernels up to 5.19 (sudo apt remove zfs-dkms) - Now re-import your ZFS pool (sudo zpool import ) (i.e. for me - sudo zpool import z-storage) - Reboot - Once your OS comes back up, check the status of any ZFS pools (sudo zpool status -v), or just list them if you prefer (sudo zpool list) - If your ZFS pool does not show up, make sure to check the settings in file "/etc/default/zfs" to make sure that ZFS is loading the key, mounting and unmounting, sharing and unsharing. If not then adjust those settings, reimport the ZFS pool and reboot like above and you should be good to go. Hope that helps and works for you and anyone else that also has this issue. -- 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/2030100 Title: zfs-dkms 2.1.5-1ubuntu6~22.04.1: zfs kernel module failed to build Status in zfs-linux package in Ubuntu: Confirmed Bug description: After this mornings update to Linux Kernel 6.2 ProblemType: Package DistroRelease: Ubuntu 22.04 Package: zfs-dkms 2.1.5-1ubuntu6~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass DKMSBuildLog: DKMS make.log for zfs-2.1.5 for kernel 6.2.0-26-generic (x86_64) Fri Aug 4 10:17:48 AM PDT 2023 make: *** No targets specified and no makefile found. Stop. DKMSKernelVersion: 6.2.0-26-generic Date: Fri Aug 4 10:17:49 2023 InstallationDate: Installed on 2022-11-19 (258 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all PackageVersion: 2.1.5-1ubuntu6~22.04.1 Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.9 SourcePackage: zfs-linux Title: zfs-dkms 2.1.5-1ubuntu6~22.04.1: zfs kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2030100/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 2045586] Re: livecd-rootfs uses losetup -P for theoretically reliable/synchronous partition setup but it's not reliable in noble
> Is only asking kernel to scan the device; to then generate "kernel udev" > events; for then udev to wakeup and process/emit "udev udev" events; and > create the required device nodes. > It's not udev that creates nodes like /dev/loop1p1 though is it? That's devtmpfs surely. -- 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/2045586 Title: livecd-rootfs uses losetup -P for theoretically reliable/synchronous partition setup but it's not reliable in noble Status in linux package in Ubuntu: New Status in livecd-rootfs package in Ubuntu: New Status in util-linux package in Ubuntu: New Bug description: In mantic, we migrated livecd-rootfs to use losetup -P instead of kpartx, with the expectation that this would give us a reliable, race- free way of loop-mounting partitions from a disk image during image build. In noble, we are finding that it is no longer reliable, and in fact fails rather often. It is most noticeable with riscv64 builds, which is the architecture where we most frequently ran into problems before with kpartx. The first riscv64+generic build in noble where the expected loop partition device is not available is https://launchpad.net/~ubuntu- cdimage/+livefs/ubuntu/noble/cpc/+build/531790 The failure is however not unique to riscv64, and the autopkgtest for the latest version of livecd-rootfs (24.04.7) - an update that specifically tries to add more debugging code for this scenario - has also failed on ppc64el. https://autopkgtest.ubuntu.com/packages/l/livecd- rootfs/noble/ppc64el The first failure happened on November 16. While there has been an update to the util-linux package in noble, this did not land until November 23. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045586/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2046176] [NEW] unstable bluetooth, auto restart when sleep, sometime cannot wake up from long time sleep
Public bug reported: unstable bluetooth, auto restart when sleep, sometime cannot wake up from long time sleep ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-37-generic 6.2.0-37.38~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Dec 12 00:12:39 2023 InstallationDate: Installed on 2023-12-10 (1 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-6.2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2046176 Title: unstable bluetooth, auto restart when sleep, sometime cannot wake up from long time sleep Status in linux-signed-hwe-6.2 package in Ubuntu: New Bug description: unstable bluetooth, auto restart when sleep, sometime cannot wake up from long time sleep ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-37-generic 6.2.0-37.38~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Dec 12 00:12:39 2023 InstallationDate: Installed on 2023-12-10 (1 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2046176/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2046085] Re: Problem with driver for Realtek 8852be Wi-Fi pci card
Thanks for the response, Using kernel: Linux slasher 6.6.0-060600-generic #202311151808 SMP PREEMPT_DYNAMIC Thu Nov 16 06:04:00 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux I have the same error: [ 16.995301] rtw89_8852be :03:00.0: loaded firmware rtw89/rtw8852b_fw-1.bin [ 17.084211] rtw89_8852be :03:00.0: enabling device ( -> 0003) [ 17.152030] rtw89_8852be :03:00.0: xtal si not ready(R): offset=41 [ 17.152052] rtw89_8852be :03:00.0: no suitable firmware found [ 17.152076] rtw89_8852be :03:00.0: failed to recognize firmware [ 17.152090] rtw89_8852be :03:00.0: failed to setup chip information [ 17.158335] rtw89_8852be: probe of :03:00.0 failed with error -2 Using kernel: Linux slasher 6.7.0-060700rc5-generic #202312102332 SMP PREEMPT_DYNAMIC Sun Dec 10 23:41:31 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux [ 17.073979] rtw89_8852be :03:00.0: loaded firmware rtw89/rtw8852b_fw-1.bin [ 17.074321] rtw89_8852be :03:00.0: enabling device ( -> 0003) [ 17.133952] rtw89_8852be :03:00.0: xtal si not ready(R): offset=41 [ 17.133980] rtw89_8852be :03:00.0: no suitable firmware found [ 17.134004] rtw89_8852be :03:00.0: failed to recognize firmware [ 17.134018] rtw89_8852be :03:00.0: failed to setup chip information [ 17.150375] rtw89_8852be: probe of :03:00.0 failed with error -2 Please advise the next steps. -- 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/2046085 Title: Problem with driver for Realtek 8852be Wi-Fi pci card Status in linux-firmware package in Ubuntu: Incomplete Bug description: I am not sure that this shall come into Ubuntu bug tracker, but correct me if I am wrong. I have a fan-less media pc that has PCI WI-FI adapter rtl8852be. I know this chipset has support in HWE Ubuntu kernel but for some reason, firmware for it still not being recognized. First I tried to make it work with 6.2 generic HWE kernel and the only strings I have in dmesg: [ 15.034783] rtw89_8852be :03:00.0: enabling device ( -> 0003) [ 15.061504] rtw89_8852be :03:00.0: no suitable firmware found [ 15.061543] rtw89_8852be :03:00.0: failed to recognize firmware [ 15.061557] rtw89_8852be :03:00.0: failed to setup chip information [ 15.075283] rtw89_8852be: probe of :03:00.0 failed with error -2 Then I tried to use linux-image-6.5.0-1009-oem kernel and get a little bit more info: [ 16.501540] rtw89_8852be :03:00.0: loaded firmware rtw89/rtw8852b_fw-1.bin [ 16.503083] rtw89_8852be :03:00.0: enabling device ( -> 0003) [ 16.567443] rtw89_8852be :03:00.0: xtal si not ready(R): offset=41 [ 16.567470] rtw89_8852be :03:00.0: no suitable firmware found [ 16.567494] rtw89_8852be :03:00.0: failed to recognize firmware [ 16.567509] rtw89_8852be :03:00.0: failed to setup chip information [ 16.572860] rtw89_8852be: probe of :03:00.0 failed with error -2 I suspect my PCI WIFI card has different subvendor ID and subdevice ID compare to the popular ones: Lenovo laptops have 8852be has PCI 10ec:b852:17aa:4853 HP laptops have 8852be has PCI 10ec:b852:103c:88e3 Mine is: PCI 10ec:b852:10ec:b852 Any suggestions are welcomed. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-firmware 20220329.git681281e4-0ubuntu3.23 ProcVersionSignature: Ubuntu 6.5.0-1009.10-oem 6.5.3 Uname: Linux 6.5.0-1009-oem x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CasperMD5CheckResult: unknown CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config Date: Sun Dec 10 21:46:40 2023 Dependencies: firmware-sof-signed 2.0-1ubuntu4.4 InstallationDate: Installed on 2023-09-15 (86 days ago) InstallationMedia: Ubuntu-Server 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230810) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:b85b Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 006: ID 1cf1:0030 Dresden Elektronik ZigBee gateway [ConBee II] Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: SDZ X133 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-1009-oem root=UUID=cd870d97-e484-43d5-aafa-2ba1ec68a7a8 ro cpufreq.default_governor=powersave RelatedPackageVersions: linux-restricted-modules-6.5.0-1009-oem N/A linux-backports-modules-6.5.0-1009-oem N/A
[Kernel-packages] [Bug 2031492] Re: zfs-dkms: support Linux 6.5
This doesn't affect me on mantic with the latest packages/kernel from mantic updates ppa. -- 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/2031492 Title: zfs-dkms: support Linux 6.5 Status in zfs-linux package in Ubuntu: New Status in zfs-linux source package in Mantic: New Bug description: [Impact] zfs-dkms fails to build with the latest 6.5 kernel in Mantic: configure: error: *** None of the expected "bops->release()" interfaces were detected. *** This may be because your kernel version is newer than what is *** supported, or you are using a patched custom kernel with *** incompatible modifications. *** *** ZFS Version: zfs-2.2.0~rc1-0ubuntu2 *** Compatible Kernels: 3.10 - 6.3 [Test case] $ sudo apt install zfs-dkms [Fix] Upstream zfs can now be compiled with kernel 6.5, cherry pick the minimum subset of patches to support the new kernel ABI. [Regression potential] We may experience filesystem regressions or potentially kernel crashes with kernels >= 6.5. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: zfs-dkms 2.2.0~rc1-0ubuntu2 ProcVersionSignature: User Name 6.5.0-4.4-generic 6.5.0-rc6 Uname: Linux 6.5.0-4-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CloudArchitecture: x86_64 CloudBuildName: server CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSerial: 20230801 CloudSubPlatform: config-disk (/dev/vdb) Date: Wed Aug 16 07:45:37 2023 PackageArchitecture: all ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: zfs-linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2031492/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038836] Re: HDMI can't display external monitor on HP Zbook Power 15 G9
Hi again, kernel 6.6 fix this issue. I use this tutorial: https://9to5linux.com/you-can-now-install-linux-kernel-6-6-on-ubuntu-heres-how then works fine. Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2038836 Title: HDMI can't display external monitor on HP Zbook Power 15 G9 Status in linux-hwe-6.2 package in Ubuntu: New Status in nvidia-graphics-drivers-535 package in Ubuntu: New Bug description: Can't use external monitor on HP Zbook Power 15 G9 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.9-0ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-34.34~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-34-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Oct 9 12:09:29 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-09-06 (32 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) RelatedPackageVersions: mutter-common 42.9-0ubuntu5 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.2/+bug/2038836/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2030100] Re: zfs-dkms 2.1.5-1ubuntu6~22.04.1: zfs kernel module failed to build
In the meantime, what's the solution? -- 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/2030100 Title: zfs-dkms 2.1.5-1ubuntu6~22.04.1: zfs kernel module failed to build Status in zfs-linux package in Ubuntu: Confirmed Bug description: After this mornings update to Linux Kernel 6.2 ProblemType: Package DistroRelease: Ubuntu 22.04 Package: zfs-dkms 2.1.5-1ubuntu6~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass DKMSBuildLog: DKMS make.log for zfs-2.1.5 for kernel 6.2.0-26-generic (x86_64) Fri Aug 4 10:17:48 AM PDT 2023 make: *** No targets specified and no makefile found. Stop. DKMSKernelVersion: 6.2.0-26-generic Date: Fri Aug 4 10:17:49 2023 InstallationDate: Installed on 2022-11-19 (258 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all PackageVersion: 2.1.5-1ubuntu6~22.04.1 Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.9 SourcePackage: zfs-linux Title: zfs-dkms 2.1.5-1ubuntu6~22.04.1: zfs kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2030100/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2046168] [NEW] perf doesnt work on new intel laptops
Public bug reported: pmilosla@pmilosla-ubuntu22:~> sudo perf record Error: The cpu_core/cycles/ event is not supported. pmilosla@pmilosla-ubuntu22:~> lscpu Architecture:x86_64 CPU op-mode(s):32-bit, 64-bit Address sizes: 45 bits physical, 48 bits virtual Byte Order:Little Endian CPU(s): 8 On-line CPU(s) list: 0-7 Vendor ID: GenuineIntel Model name:13th Gen Intel(R) Core(TM) i9-13900H CPU family: 6 Model: 186 Thread(s) per core: 1 Core(s) per socket: 1 Socket(s): 8 Stepping:2 BogoMIPS:5990.40 sudo perf top works however I need sudo perf record to work with -p option sudo apt-get update sudo apt-get dist-upgrade sudo apt-get install --reinstall linux-tools-common linux-tools-generic linux-tools-`uname -r` ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-tools-common 5.15.0-91.101 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.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pmilosla 1744 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Dec 11 11:30:54 2023 InstallationDate: Installed on 2023-06-14 (180 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) IwConfig: lono wireless extensions. ens33 no wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 004: ID 0e0f:0008 VMware, Inc. Virtual Bluetooth Adapter Bus 001 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 001 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: VMware, Inc. VMware Virtual Platform PackageArchitecture: all ProcFB: 0 vmwgfxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-37-generic root=UUID=bde66501-62d8-4cc1-b37c-b9265a11519a ro find_preseed=/preseed.cfg auto noprompt priority=critical locale=en_US quiet splash RelatedPackageVersions: linux-restricted-modules-6.2.0-37-generic N/A linux-backports-modules-6.2.0-37-generic N/A linux-firmware20220329.git681281e4-0ubuntu3.23 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/12/2020 dmi.bios.release: 4.6 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2023-07-11T12:19:20.955497 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2046168 Title: perf doesnt work on new intel laptops Status in linux package in Ubuntu: New Bug description: pmilosla@pmilosla-ubuntu22:~> sudo perf record Error: The cpu_core/cycles/ event is not supported. pmilosla@pmilosla-ubuntu22:~> lscpu Architecture:x86_64 CPU op-mode(s):32-bit, 64-bit Address sizes: 45 bits physical, 48 bits virtual Byte Order:Little Endian CPU(s): 8 On-line CPU(s) list: 0-7 Vendor ID: GenuineIntel Model name:13th Gen Intel(R) Core(TM) i9-13900H CPU family: 6 Model: 186 Thread(s) per core: 1 Core(s) per socket: 1 Socket(s): 8 Stepping:2 BogoMIPS:5990.40 sudo perf top works however I need sudo perf record to work with -p option sudo apt-get update sudo apt-get dist-upgrade sudo apt-get install --reinstall linux-tools-common linux-tools-generic linux-tools-`uname -r` ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-tools-common 5.15.0-91.101 ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16 Uname: Linux
[Kernel-packages] [Bug 2045407] Re: xhci_hcd usb storage does not boot with kernel 6.5.0-1007 raspi 4
From vanilla kernel 6.6.0 raspi USB boot, works again with https://raw.githubusercontent.com/raspberrypi/linux/rpi-6.1.y/arch/arm64/configs/bcm2711_defconfig as config root@controller:~# uname -a Linux controller 6.6.0-juampe-raspi #3 SMP Mon Dec 11 16:53:54 CET 2023 aarch64 aarch64 aarch64 GNU/Linux [0.684870] serial serial0: tty port ttyAMA0 registered [0.685571] raspberrypi-firmware soc:firmware: Attached to firmware from 2023-03-17T10:50:39 [0.735617] xhci_hcd :01:00.0: xHCI Host Controller [0.735697] xhci_hcd :01:00.0: new USB bus registered, assigned bus number 1 [0.736160] xhci_hcd :01:00.0: hcc params 0x002841eb hci version 0x100 quirks 0x0890 [0.736615] xhci_hcd :01:00.0: xHCI Host Controller [0.736673] xhci_hcd :01:00.0: new USB bus registered, assigned bus number 2 [0.736740] xhci_hcd :01:00.0: Host supports USB 3.0 SuperSpeed [0.737010] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.06 [0.737084] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [0.737146] usb usb1: Product: xHCI Host Controller [0.737190] usb usb1: Manufacturer: Linux 6.6.0-juampe-raspi xhci-hcd [0.737242] usb usb1: SerialNumber: :01:00.0 [0.737781] hub 1-0:1.0: USB hub found [0.740297] hub 1-0:1.0: 1 port detected [0.743219] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 6.06 [0.745647] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [0.748037] usb usb2: Product: xHCI Host Controller [0.750403] usb usb2: Manufacturer: Linux 6.6.0-juampe-raspi xhci-hcd [0.752795] usb usb2: SerialNumber: :01:00.0 [0.755646] hub 2-0:1.0: USB hub found [0.758050] hub 2-0:1.0: 4 ports detected -- 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/2045407 Title: xhci_hcd usb storage does not boot with kernel 6.5.0-1007 raspi 4 Status in linux package in Ubuntu: New Bug description: Differential analisys FAIL BOOT WITH vmlinuz-6.5.0-1007-raspi 2.411312] xhci_hcd :01:00.0: hcc params 0x002841eb hci version 0x100 qu 2.414253] xhci hcd :01:00.0: xHCI Host Controller 2.417066] xhci_hcd :01:00.0: new USB bus registered, assigned bus numbe 2.418935] xhci_hcd :01:00.0: Host supports USB 3.0 SuperSpeed 2.424202] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bc 2.426301] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber= 2.428277] usb usb1: Product: xHCI Host Controller 2.429833] usb usb1: Manufacturer: Linux 6.5.0-1007-raspi xhci-hcd 2.431696] usb usb1: Serial Number: :01:00.0 2.446311] hub 1-0:1.0: USB hub found 2.449294] hub 1-0:1.0: 1 port detected 2.455150] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bc 2.456938] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber= 2.457289] uc2 fe98.usb: supply vusb_d not found, using dummy regulator 2.458707] usb usb2: Product: XHCI Host Controller 2.461093] duc2 fe98.usb: supply vusb_a not found, using dummy regulator 2.481488] usb usb2: Manufacturer: Linux 6.5.0-1007-raspi xhci-hcd 2.483294] usb usb2: SerialNumber: :01:00.0 2.488946] hub 2-0:1.0: USB hub found 2.491438] hub 2-0:1.0: 4 ports detected 2.498162] [drm] Initialized u3d 1.0.0 20180419 for fec0.v3d on minor O 2.5429891 Console: switching to colour dummy device 80x25 2.543898] vc4-drm gpu: bound fe60.firmwarekms (ops vc4_fkms_ops [vc4]) 2.544513] [drm] Initialized uc4 0.0.0 20140616 for gpu on minor 1 2.6726471 dwc2 fe98.usb: EPs: 8, dedicated fifos, 4080 entries in SPRAM 2.672838] dwc2 fe98.usb: DWC OTG Controller 2.672852] dwc2 fe98.usb: new USB bus registered, assigned bus number 3 2.672876] dwc2 fe98.usb: irq 39, io mem 0xfe98 2.673046] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.05 2.673052] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 2.673058] usb usb3: Product: DWC OTG Controller 2.673062] usb usb3: Manufacturer: Linux 6.5.0-1007-raspi duc2_hsotg 2.673066] usb usb3: Serial Number: fe98.usb 2.6734161 hub 3-0:1.0: USB hub found 2.673439] hub 3-0:1.0: 1 port detected 2.791029] Console: switching to colour frame buffer device 480x135 2.7989511 vc4-drm gpu: [drm] fb0: vc4drmfb frame buffer device 9.660608] xhci_hcd :01:00.0: Error while assigning device slot ID: Command Aborted 9.660661] xhci_hcd :01:00.0: Max number of devices this xHCI host supports is 32. 9.660686] usb usb1-port1: couldn't allocate usb_device WORKS WITH initrd.img-6.2.0-1014-raspi [2.632992] xhci_hcd :01:00.0: xHCI Host Controller [2.635543] xhci_hcd :01:00.0: new USB bus registered, assigned bus number 1 [2.639487] xhci_hcd :01:00.0:
[Kernel-packages] [Bug 2044657] Re: Multiple data corruption issues in zfs
** 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/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 2043197] Re: USB bus error after upgrading to proposed kernel on lunar, jammy and focal
This bug is awaiting verification that the linux- raspi-5.4/5.4.0-1100.112~18.04.1 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-bionic-linux- raspi-5.4' to 'verification-done-bionic-linux-raspi-5.4'. If the problem still exists, change the tag 'verification-needed-bionic-linux- raspi-5.4' to 'verification-failed-bionic-linux-raspi-5.4'. 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-bionic-linux-raspi-5.4-v2 verification-needed-bionic-linux-raspi-5.4 -- 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/2043197 Title: USB bus error after upgrading to proposed kernel on lunar, jammy and focal Status in linux package in Ubuntu: Triaged Status in linux source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Released Bug description: == SRU Justification == [Impact] USB SuperSpeed (3.0) devcies can't be enumerated on Lunar/Jammy kernel. [Fix] Use logarithmic encoding for the bMaxPacketSize0 value. [Test] With the patch applied, SuperSpeed devices can be enumerated across several reboots. [Where problems could occur] The switch case for Wireless USB (not USB WiFi dongle) was removed by the fix. I am not aware of the existence of any Wireless USB device. But if they do exist, this patch may the packet size encoding on them. == Original Bug Report == [Summary] Some of machines in cert lab after upgrading to proposed kernel on jammy and lunar, all usb devices were gone. I found this issue on linux-image-6.2.0-38-generic and linux- image-5.15.0-90-generic on some specific machines. Since some of machines are using usb ethernet adapter so after upgrading, those machines are not accessible. Following are the machine list I've seen impacted by this issue, I believe there will be more if I check further. https://certification.canonical.com/hardware/202005-27899/ https://certification.canonical.com/hardware/201903-26881/ https://certification.canonical.com/hardware/201903-26932/ https://certification.canonical.com/hardware/202005-27944/ https://certification.canonical.com/hardware/202008-28166/ https://certification.canonical.com/hardware/202008-28167/ https://certification.canonical.com/hardware/202102-28728/ https://certification.canonical.com/hardware/202008-28176/ https://certification.canonical.com/hardware/202008-28177/ https://certification.canonical.com/hardware/202202-29946/ ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-90-generic 5.15.0-90.100 ProcVersionSignature: Ubuntu 5.15.0-90.100-generic 5.15.131 Uname: Linux 5.15.0-90-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.15.0-90-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D5p', '/dev/snd/pcmC0D4p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D7c', '/dev/snd/pcmC0D6c', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: unknown CloudArchitecture: x86_64 CloudID: maas CloudName: maas CloudPlatform: maas CloudSubPlatform: seed-dir (http://10.102.156.25:5248/MAAS/metadata/) Date: Fri Nov 10 12:04:10 2023 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0026 Intel Corp. AX201 Bluetooth Bus 001 Device 002: ID 05c8:03cb Cheng Uei Precision Industry Co., Ltd (Foxlink) HP Wide Vision HD Integrated Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ProOne 600 G6 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-90-generic root=UUID=6da4d16a-a5a6-47db-a882-3fc3becd4204 ro RelatedPackageVersions: linux-restricted-modules-5.15.0-90-generic N/A linux-backports-modules-5.15.0-90-generic N/A linux-firmware
Re: [Kernel-packages] [Bug 2044657] Re: Multiple data corruption issues in zfs
On Fri, 8 Dec 2023 at 23:35, Steve Langasek <2044...@bugs.launchpad.net> wrote: > > zfs-linux (2.2.2-0ubuntu1~23.10) mantic; urgency=medium > > * New upstream release. LP: #2044657 > - Address potential data corruption > > I'm assuming the plan for fixing it on earlier releases does not involve > updating to 2.2.2. > > And this does not fall under a hardware enablement exception. AND there > are packaging changes under debian/. > > The diff for this new upstream release is 9kloc. I would expect a > cherry-picked fix here for mantic, not a full upstream backport - just > as will be required for releases prior to mantic. My plan was to do updates as follows: - upgrade to 2.2.2 for mantic - upgrade to 2.1.14 for jammy (to cover this issue, but also potential straight line speculation fixes) - cherry-pick of individual bug fix for focal and earlier I also do not understand why I ended up maintaining any of zfs-linux anymore btw. Especially the userspace side of things. I am happy to SRU just the kernel code changes alone, and let foundations handle the zfs userspace fixes. Separately, do note that lxd snap builds and vendors the full multiple zfs userspace tooling. So i'm not sure there is any stability value in not taking the full point releases for the userspace tooling changes in the classic ubuntu release - or try to untangle them. Regards, Dimitri. -- 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 Committed 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 Committed 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 2043197] Re: USB bus error after upgrading to proposed kernel on lunar, jammy and focal
Tested with an USB 3.2 flash drive on Pi4 (5.4.0-1100.112). -- 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/2043197 Title: USB bus error after upgrading to proposed kernel on lunar, jammy and focal Status in linux package in Ubuntu: Triaged Status in linux source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Released Bug description: == SRU Justification == [Impact] USB SuperSpeed (3.0) devcies can't be enumerated on Lunar/Jammy kernel. [Fix] Use logarithmic encoding for the bMaxPacketSize0 value. [Test] With the patch applied, SuperSpeed devices can be enumerated across several reboots. [Where problems could occur] The switch case for Wireless USB (not USB WiFi dongle) was removed by the fix. I am not aware of the existence of any Wireless USB device. But if they do exist, this patch may the packet size encoding on them. == Original Bug Report == [Summary] Some of machines in cert lab after upgrading to proposed kernel on jammy and lunar, all usb devices were gone. I found this issue on linux-image-6.2.0-38-generic and linux- image-5.15.0-90-generic on some specific machines. Since some of machines are using usb ethernet adapter so after upgrading, those machines are not accessible. Following are the machine list I've seen impacted by this issue, I believe there will be more if I check further. https://certification.canonical.com/hardware/202005-27899/ https://certification.canonical.com/hardware/201903-26881/ https://certification.canonical.com/hardware/201903-26932/ https://certification.canonical.com/hardware/202005-27944/ https://certification.canonical.com/hardware/202008-28166/ https://certification.canonical.com/hardware/202008-28167/ https://certification.canonical.com/hardware/202102-28728/ https://certification.canonical.com/hardware/202008-28176/ https://certification.canonical.com/hardware/202008-28177/ https://certification.canonical.com/hardware/202202-29946/ ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-90-generic 5.15.0-90.100 ProcVersionSignature: Ubuntu 5.15.0-90.100-generic 5.15.131 Uname: Linux 5.15.0-90-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.15.0-90-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D5p', '/dev/snd/pcmC0D4p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D7c', '/dev/snd/pcmC0D6c', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: unknown CloudArchitecture: x86_64 CloudID: maas CloudName: maas CloudPlatform: maas CloudSubPlatform: seed-dir (http://10.102.156.25:5248/MAAS/metadata/) Date: Fri Nov 10 12:04:10 2023 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0026 Intel Corp. AX201 Bluetooth Bus 001 Device 002: ID 05c8:03cb Cheng Uei Precision Industry Co., Ltd (Foxlink) HP Wide Vision HD Integrated Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ProOne 600 G6 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-90-generic root=UUID=6da4d16a-a5a6-47db-a882-3fc3becd4204 ro RelatedPackageVersions: linux-restricted-modules-5.15.0-90-generic N/A linux-backports-modules-5.15.0-90-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.22 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2023 dmi.bios.release: 16.0 dmi.bios.vendor: HP dmi.bios.version: S12 Ver. 02.16.00 dmi.board.name: 8810 dmi.board.vendor: HP dmi.board.version: KBC Version 09.08.23 dmi.chassis.type: 13 dmi.chassis.vendor: HP dmi.ec.firmware.release: 9.8 dmi.modalias: dmi:bvnHP:bvrS12Ver.02.16.00:bd06/26/2023:br16.0:efr9.8:svnHP:pnHPProOne600G6:pvr:rvnHP:rn8810:rvrKBCVersion09.08.23:cvnHP:ct13:cvr:sku123456#ABA: dmi.product.family: 103C_53307F HP ProOne dmi.product.name: HP ProOne 600 G6 dmi.product.sku:
[Kernel-packages] [Bug 2043197] Re: USB bus error after upgrading to proposed kernel on lunar, jammy and focal
** Tags removed: verification-needed-focal-linux-raspi ** Tags added: verification-done-focal-linux-raspi -- 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/2043197 Title: USB bus error after upgrading to proposed kernel on lunar, jammy and focal Status in linux package in Ubuntu: Triaged Status in linux source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Released Bug description: == SRU Justification == [Impact] USB SuperSpeed (3.0) devcies can't be enumerated on Lunar/Jammy kernel. [Fix] Use logarithmic encoding for the bMaxPacketSize0 value. [Test] With the patch applied, SuperSpeed devices can be enumerated across several reboots. [Where problems could occur] The switch case for Wireless USB (not USB WiFi dongle) was removed by the fix. I am not aware of the existence of any Wireless USB device. But if they do exist, this patch may the packet size encoding on them. == Original Bug Report == [Summary] Some of machines in cert lab after upgrading to proposed kernel on jammy and lunar, all usb devices were gone. I found this issue on linux-image-6.2.0-38-generic and linux- image-5.15.0-90-generic on some specific machines. Since some of machines are using usb ethernet adapter so after upgrading, those machines are not accessible. Following are the machine list I've seen impacted by this issue, I believe there will be more if I check further. https://certification.canonical.com/hardware/202005-27899/ https://certification.canonical.com/hardware/201903-26881/ https://certification.canonical.com/hardware/201903-26932/ https://certification.canonical.com/hardware/202005-27944/ https://certification.canonical.com/hardware/202008-28166/ https://certification.canonical.com/hardware/202008-28167/ https://certification.canonical.com/hardware/202102-28728/ https://certification.canonical.com/hardware/202008-28176/ https://certification.canonical.com/hardware/202008-28177/ https://certification.canonical.com/hardware/202202-29946/ ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-90-generic 5.15.0-90.100 ProcVersionSignature: Ubuntu 5.15.0-90.100-generic 5.15.131 Uname: Linux 5.15.0-90-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.15.0-90-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D5p', '/dev/snd/pcmC0D4p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D7c', '/dev/snd/pcmC0D6c', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: unknown CloudArchitecture: x86_64 CloudID: maas CloudName: maas CloudPlatform: maas CloudSubPlatform: seed-dir (http://10.102.156.25:5248/MAAS/metadata/) Date: Fri Nov 10 12:04:10 2023 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0026 Intel Corp. AX201 Bluetooth Bus 001 Device 002: ID 05c8:03cb Cheng Uei Precision Industry Co., Ltd (Foxlink) HP Wide Vision HD Integrated Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ProOne 600 G6 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-90-generic root=UUID=6da4d16a-a5a6-47db-a882-3fc3becd4204 ro RelatedPackageVersions: linux-restricted-modules-5.15.0-90-generic N/A linux-backports-modules-5.15.0-90-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.22 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2023 dmi.bios.release: 16.0 dmi.bios.vendor: HP dmi.bios.version: S12 Ver. 02.16.00 dmi.board.name: 8810 dmi.board.vendor: HP dmi.board.version: KBC Version 09.08.23 dmi.chassis.type: 13 dmi.chassis.vendor: HP dmi.ec.firmware.release: 9.8 dmi.modalias: dmi:bvnHP:bvrS12Ver.02.16.00:bd06/26/2023:br16.0:efr9.8:svnHP:pnHPProOne600G6:pvr:rvnHP:rn8810:rvrKBCVersion09.08.23:cvnHP:ct13:cvr:sku123456#ABA: dmi.product.family: 103C_53307F HP ProOne
[Kernel-packages] [Bug 2045586] Re: livecd-rootfs uses losetup -P for theoretically reliable/synchronous partition setup but it's not reliable in noble
I don't have a good explanation, but in the past I've "fixed" such races by adding a `sync "$loop_device"` before using any of the newly created partitons. Maybe it's worth trying. -- 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/2045586 Title: livecd-rootfs uses losetup -P for theoretically reliable/synchronous partition setup but it's not reliable in noble Status in linux package in Ubuntu: New Status in livecd-rootfs package in Ubuntu: New Status in util-linux package in Ubuntu: New Bug description: In mantic, we migrated livecd-rootfs to use losetup -P instead of kpartx, with the expectation that this would give us a reliable, race- free way of loop-mounting partitions from a disk image during image build. In noble, we are finding that it is no longer reliable, and in fact fails rather often. It is most noticeable with riscv64 builds, which is the architecture where we most frequently ran into problems before with kpartx. The first riscv64+generic build in noble where the expected loop partition device is not available is https://launchpad.net/~ubuntu- cdimage/+livefs/ubuntu/noble/cpc/+build/531790 The failure is however not unique to riscv64, and the autopkgtest for the latest version of livecd-rootfs (24.04.7) - an update that specifically tries to add more debugging code for this scenario - has also failed on ppc64el. https://autopkgtest.ubuntu.com/packages/l/livecd- rootfs/noble/ppc64el The first failure happened on November 16. While there has been an update to the util-linux package in noble, this did not land until November 23. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045586/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2045586] Re: livecd-rootfs uses losetup -P for theoretically reliable/synchronous partition setup but it's not reliable in noble
my expectation is that udev should be running (somewhere, not sure if it needs to be both the host and the lxd guest) and that it should process the device using locks https://systemd.io/BLOCK_DEVICE_LOCKING/. After that is done, the device should be safe to operate on, in a consistent manner. After all, -P, --partscan Force the kernel to scan the partition table on a newly created loop device. Note that the partition table parsing depends on sector sizes. The default is sector size is 512 bytes, otherwise you need to use the option --sector-size together with --partscan. Is only asking kernel to scan the device; to then generate "kernel udev" events; for then udev to wakeup and process/emit "udev udev" events; and create the required device nodes. We have always been fixing and supporting running udev inside the lxd containers, because of such things (in contexts of priviledged containers, but outside of lp-buildd) to make all of this work. -- 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/2045586 Title: livecd-rootfs uses losetup -P for theoretically reliable/synchronous partition setup but it's not reliable in noble Status in linux package in Ubuntu: New Status in livecd-rootfs package in Ubuntu: New Status in util-linux package in Ubuntu: New Bug description: In mantic, we migrated livecd-rootfs to use losetup -P instead of kpartx, with the expectation that this would give us a reliable, race- free way of loop-mounting partitions from a disk image during image build. In noble, we are finding that it is no longer reliable, and in fact fails rather often. It is most noticeable with riscv64 builds, which is the architecture where we most frequently ran into problems before with kpartx. The first riscv64+generic build in noble where the expected loop partition device is not available is https://launchpad.net/~ubuntu- cdimage/+livefs/ubuntu/noble/cpc/+build/531790 The failure is however not unique to riscv64, and the autopkgtest for the latest version of livecd-rootfs (24.04.7) - an update that specifically tries to add more debugging code for this scenario - has also failed on ppc64el. https://autopkgtest.ubuntu.com/packages/l/livecd- rootfs/noble/ppc64el The first failure happened on November 16. While there has been an update to the util-linux package in noble, this did not land until November 23. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045586/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2045913] Re: Update the NVIDIA 535 driver
No, it was just a typo. ** Package changed: nvidia-graphics-drivers-525 (Ubuntu) => nvidia- graphics-drivers-535 (Ubuntu) -- 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 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 1855243] Re: pkey01 from ubuntu_ltp_syscalls failed on X-KVM with nr_hugepages = 0
With LTP-20230516 this test will be skipped with <<>> tag=pkey01 stime=1702290779 cmdline="pkey01" contacts="" analysis=exit <<>> incrementing stop tst_hugepage.c:83: TINFO: 1 hugepage(s) reserved tst_test.c:1560: TINFO: Timeout per run is 0h 00m 30s pkey.h:27: TCONF: syscall(330) __NR_pkey_alloc not supported on your arch Summary: passed 0 failed 0 broken 0 skipped 1 warnings 0 <<>> initiation_status="ok" duration=0 termination_type=exited termination_id=32 corefile=no cutime=0 cstime=0 <<>> ** Changed in: ubuntu-kernel-tests Status: New => Fix Released ** Changed in: linux-kvm (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1855243 Title: pkey01 from ubuntu_ltp_syscalls failed on X-KVM with nr_hugepages = 0 Status in ubuntu-kernel-tests: Fix Released Status in linux-kvm package in Ubuntu: Invalid Bug description: Reproduce rate: 4/4 Test failed with: pkey01.c:69: BROK: nr_hugepages = 0, but expect 1 <<>> tag=pkey01 stime=1575532698 cmdline="pkey01" contacts="" analysis=exit <<>> incrementing stop tst_test.c:1217: INFO: Timeout per run is 0h 05m 00s pkey01.c:69: BROK: nr_hugepages = 0, but expect 1 Summary: passed 0 failed 0 skipped 0 warnings 0 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-1063-kvm 4.4.0-1063.70 ProcVersionSignature: User Name 4.4.0-1063.70-kvm 4.4.200 Uname: Linux 4.4.0-1063-kvm x86_64 ApportVersion: 2.20.1-0ubuntu2.21 Architecture: amd64 Date: Thu Dec 5 07:58:24 2019 SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1855243/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
** Description changed:
[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.
--
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:
In Progress
Status in linux-oem-6.5 package in Ubuntu:
In Progress
Status in linux source package in Jammy:
New
Status in linux-oem-6.1 source package in Jammy:
In Progress
Status in linux-oem-6.5 source package in Jammy:
In Progress
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 2046057] Re: package linux-headers-generic-hwe-22.04 6.5.0.14.16 failed to install/upgrade: problèmes de dépendances - laissé non configuré
You have an unsupported DKMS module installed that breaks the
installation of the kernel header package. Please remove it:
$ dkms remove synosnap/0.10.19
** Changed in: linux (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2046057
Title:
package linux-headers-generic-hwe-22.04 6.5.0.14.16 failed to
install/upgrade: problèmes de dépendances - laissé non configuré
Status in linux package in Ubuntu:
Invalid
Bug description:
Just tried to update using the update pop-up.
ProblemType: Package
DistroRelease: Ubuntu 23.10
Package: linux-headers-generic-hwe-22.04 6.5.0.14.16
ProcVersionSignature: Ubuntu 6.5.0-13.13-generic 6.5.3
Uname: Linux 6.5.0-13-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: mael 3312 F pipewire
mael 3320 F wireplumber
/dev/snd/seq:mael 3312 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
Date: Sun Dec 10 11:26:31 2023
ErrorMessage: problèmes de dépendances - laissé non configuré
InstallationDate: Installed on 2023-11-20 (20 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64
(20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-13-generic
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
PythonDetails: N/A
RelatedPackageVersions: grub-pc N/A
SourcePackage: linux
Title: package linux-headers-generic-hwe-22.04 6.5.0.14.16 failed to
install/upgrade: problèmes de dépendances - laissé non configuré
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/23/2023
dmi.bios.release: 1.39
dmi.bios.vendor: LENOVO
dmi.bios.version: N3QET39W (1.39 )
dmi.board.asset.tag: Not Available
dmi.board.name: 21HKCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76530 WIN
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.10
dmi.modalias:
dmi:bvnLENOVO:bvrN3QET39W(1.39):bd10/23/2023:br1.39:efr1.10:svnLENOVO:pn21HKCTO1WW:pvrThinkPadP16sGen2:rvnLENOVO:rn21HKCTO1WW:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21HK_BU_Think_FM_ThinkPadP16sGen2:
dmi.product.family: ThinkPad P16s Gen 2
dmi.product.name: 21HKCTO1WW
dmi.product.sku: LENOVO_MT_21HK_BU_Think_FM_ThinkPad P16s Gen 2
dmi.product.version: ThinkPad P16s Gen 2
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2046057/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2046057] Re: package linux-headers-generic-hwe-22.04 6.5.0.14.16 failed to install/upgrade: problèmes de dépendances - laissé non configuré
Building module:
Cleaning build area...
make -j20 KERNELRELEASE-6.5.0-14-generic -C /lib/modules/6.5.0-14-generic/build
M-/var/lib/dkms/synosnap/0.10.19/build KVER-65.0-14-generic modules... (bad
exit status: 2)
ERROR: Cannot create report: [Errno 17) File exists:
'/var/crash/synosnap.0.crash'
Error Bad return status for module build on kernel: 6.5.0-14-generic (x86-64)
Consult /var/lib/dkms/synosnap/0.10.19/build/make.log for more information.
dkms autoinstall on 6.5.0-14-generic/x86-64 failed for synosnap(10)
Error One or more modules failed to install during autoinstall.
--
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/2046057
Title:
package linux-headers-generic-hwe-22.04 6.5.0.14.16 failed to
install/upgrade: problèmes de dépendances - laissé non configuré
Status in linux package in Ubuntu:
Invalid
Bug description:
Just tried to update using the update pop-up.
ProblemType: Package
DistroRelease: Ubuntu 23.10
Package: linux-headers-generic-hwe-22.04 6.5.0.14.16
ProcVersionSignature: Ubuntu 6.5.0-13.13-generic 6.5.3
Uname: Linux 6.5.0-13-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: mael 3312 F pipewire
mael 3320 F wireplumber
/dev/snd/seq:mael 3312 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
Date: Sun Dec 10 11:26:31 2023
ErrorMessage: problèmes de dépendances - laissé non configuré
InstallationDate: Installed on 2023-11-20 (20 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64
(20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-13-generic
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
PythonDetails: N/A
RelatedPackageVersions: grub-pc N/A
SourcePackage: linux
Title: package linux-headers-generic-hwe-22.04 6.5.0.14.16 failed to
install/upgrade: problèmes de dépendances - laissé non configuré
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/23/2023
dmi.bios.release: 1.39
dmi.bios.vendor: LENOVO
dmi.bios.version: N3QET39W (1.39 )
dmi.board.asset.tag: Not Available
dmi.board.name: 21HKCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76530 WIN
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.10
dmi.modalias:
dmi:bvnLENOVO:bvrN3QET39W(1.39):bd10/23/2023:br1.39:efr1.10:svnLENOVO:pn21HKCTO1WW:pvrThinkPadP16sGen2:rvnLENOVO:rn21HKCTO1WW:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21HK_BU_Think_FM_ThinkPadP16sGen2:
dmi.product.family: ThinkPad P16s Gen 2
dmi.product.name: 21HKCTO1WW
dmi.product.sku: LENOVO_MT_21HK_BU_Think_FM_ThinkPad P16s Gen 2
dmi.product.version: ThinkPad P16s Gen 2
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2046057/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2046085] Re: Problem with driver for Realtek 8852be Wi-Fi pci card
Sorry, no. We can't just pull in any random driver and sign it for secureboot. We'd have to report this to upstream but you need to verify first that the problem still exists with latest kernel and firmware. Can you test the latest mainline kernels from: https://kernel.ubuntu.com/mainline/ You might want to test v6.6 fist, if that fails v6.7-rc5. They're unsigned so you need to temporarily disable secureboot in the BIOS. ** Changed in: linux-firmware (Ubuntu) Status: New => Incomplete -- 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/2046085 Title: Problem with driver for Realtek 8852be Wi-Fi pci card Status in linux-firmware package in Ubuntu: Incomplete Bug description: I am not sure that this shall come into Ubuntu bug tracker, but correct me if I am wrong. I have a fan-less media pc that has PCI WI-FI adapter rtl8852be. I know this chipset has support in HWE Ubuntu kernel but for some reason, firmware for it still not being recognized. First I tried to make it work with 6.2 generic HWE kernel and the only strings I have in dmesg: [ 15.034783] rtw89_8852be :03:00.0: enabling device ( -> 0003) [ 15.061504] rtw89_8852be :03:00.0: no suitable firmware found [ 15.061543] rtw89_8852be :03:00.0: failed to recognize firmware [ 15.061557] rtw89_8852be :03:00.0: failed to setup chip information [ 15.075283] rtw89_8852be: probe of :03:00.0 failed with error -2 Then I tried to use linux-image-6.5.0-1009-oem kernel and get a little bit more info: [ 16.501540] rtw89_8852be :03:00.0: loaded firmware rtw89/rtw8852b_fw-1.bin [ 16.503083] rtw89_8852be :03:00.0: enabling device ( -> 0003) [ 16.567443] rtw89_8852be :03:00.0: xtal si not ready(R): offset=41 [ 16.567470] rtw89_8852be :03:00.0: no suitable firmware found [ 16.567494] rtw89_8852be :03:00.0: failed to recognize firmware [ 16.567509] rtw89_8852be :03:00.0: failed to setup chip information [ 16.572860] rtw89_8852be: probe of :03:00.0 failed with error -2 I suspect my PCI WIFI card has different subvendor ID and subdevice ID compare to the popular ones: Lenovo laptops have 8852be has PCI 10ec:b852:17aa:4853 HP laptops have 8852be has PCI 10ec:b852:103c:88e3 Mine is: PCI 10ec:b852:10ec:b852 Any suggestions are welcomed. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-firmware 20220329.git681281e4-0ubuntu3.23 ProcVersionSignature: Ubuntu 6.5.0-1009.10-oem 6.5.3 Uname: Linux 6.5.0-1009-oem x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CasperMD5CheckResult: unknown CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config Date: Sun Dec 10 21:46:40 2023 Dependencies: firmware-sof-signed 2.0-1ubuntu4.4 InstallationDate: Installed on 2023-09-15 (86 days ago) InstallationMedia: Ubuntu-Server 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230810) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:b85b Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 006: ID 1cf1:0030 Dresden Elektronik ZigBee gateway [ConBee II] Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: SDZ X133 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-1009-oem root=UUID=cd870d97-e484-43d5-aafa-2ba1ec68a7a8 ro cpufreq.default_governor=powersave RelatedPackageVersions: linux-restricted-modules-6.5.0-1009-oem N/A linux-backports-modules-6.5.0-1009-oem N/A linux-firmware 20220329.git681281e4-0ubuntu3.23 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2023 dmi.bios.release: 1.20 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: PC_STICK_8G_D8R2 dmi.board.asset.tag: Default string dmi.board.name: X133 dmi.board.vendor: SDZ dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: SDZ dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrPC_STICK_8G_D8R2:bd05/12/2023:br1.20:svnSDZ:pnX133:pvrDefaultstring:rvnSDZ:rnX133:rvrDefaultstring:cvnSDZ:ct10:cvrDefaultstring:skuDefaultstring: dmi.product.family: Notebook dmi.product.name: X133 dmi.product.sku: Default string
[Kernel-packages] [Bug 2046085] Re: Problem with driver for Realtek 8852be Wi-Fi pci card
** Tags added: kern-8703 -- 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/2046085 Title: Problem with driver for Realtek 8852be Wi-Fi pci card Status in linux-firmware package in Ubuntu: New Bug description: I am not sure that this shall come into Ubuntu bug tracker, but correct me if I am wrong. I have a fan-less media pc that has PCI WI-FI adapter rtl8852be. I know this chipset has support in HWE Ubuntu kernel but for some reason, firmware for it still not being recognized. First I tried to make it work with 6.2 generic HWE kernel and the only strings I have in dmesg: [ 15.034783] rtw89_8852be :03:00.0: enabling device ( -> 0003) [ 15.061504] rtw89_8852be :03:00.0: no suitable firmware found [ 15.061543] rtw89_8852be :03:00.0: failed to recognize firmware [ 15.061557] rtw89_8852be :03:00.0: failed to setup chip information [ 15.075283] rtw89_8852be: probe of :03:00.0 failed with error -2 Then I tried to use linux-image-6.5.0-1009-oem kernel and get a little bit more info: [ 16.501540] rtw89_8852be :03:00.0: loaded firmware rtw89/rtw8852b_fw-1.bin [ 16.503083] rtw89_8852be :03:00.0: enabling device ( -> 0003) [ 16.567443] rtw89_8852be :03:00.0: xtal si not ready(R): offset=41 [ 16.567470] rtw89_8852be :03:00.0: no suitable firmware found [ 16.567494] rtw89_8852be :03:00.0: failed to recognize firmware [ 16.567509] rtw89_8852be :03:00.0: failed to setup chip information [ 16.572860] rtw89_8852be: probe of :03:00.0 failed with error -2 I suspect my PCI WIFI card has different subvendor ID and subdevice ID compare to the popular ones: Lenovo laptops have 8852be has PCI 10ec:b852:17aa:4853 HP laptops have 8852be has PCI 10ec:b852:103c:88e3 Mine is: PCI 10ec:b852:10ec:b852 Any suggestions are welcomed. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-firmware 20220329.git681281e4-0ubuntu3.23 ProcVersionSignature: Ubuntu 6.5.0-1009.10-oem 6.5.3 Uname: Linux 6.5.0-1009-oem x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CasperMD5CheckResult: unknown CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config Date: Sun Dec 10 21:46:40 2023 Dependencies: firmware-sof-signed 2.0-1ubuntu4.4 InstallationDate: Installed on 2023-09-15 (86 days ago) InstallationMedia: Ubuntu-Server 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230810) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:b85b Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 006: ID 1cf1:0030 Dresden Elektronik ZigBee gateway [ConBee II] Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: SDZ X133 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-1009-oem root=UUID=cd870d97-e484-43d5-aafa-2ba1ec68a7a8 ro cpufreq.default_governor=powersave RelatedPackageVersions: linux-restricted-modules-6.5.0-1009-oem N/A linux-backports-modules-6.5.0-1009-oem N/A linux-firmware 20220329.git681281e4-0ubuntu3.23 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2023 dmi.bios.release: 1.20 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: PC_STICK_8G_D8R2 dmi.board.asset.tag: Default string dmi.board.name: X133 dmi.board.vendor: SDZ dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: SDZ dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrPC_STICK_8G_D8R2:bd05/12/2023:br1.20:svnSDZ:pnX133:pvrDefaultstring:rvnSDZ:rnX133:rvrDefaultstring:cvnSDZ:ct10:cvrDefaultstring:skuDefaultstring: dmi.product.family: Notebook dmi.product.name: X133 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: SDZ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2046085/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2042877] Re: kernel: r8169 0000:0d:00.0 enp13s0: rtl_rxtx_empty_cond == 0 (loop: 42, delay: 100).
Ken Sharp: here is part of the dmesg log. I'll try the r8168-dkms package in a minute. [3.026044] r8169 :10:00.0 eth0: RTL8125B, d8:5e:d3:e4:93:62, XID 641, IRQ 56 [3.026047] r8169 :10:00.0 eth0: jumbo features [frames: 9194 bytes, tx checksumming: ko] [5.424645] r8169 :10:00.0 enp16s0: renamed from eth0 [ 88.376390] RTL8226B_RTL8221B 2.5Gbps PHY r8169-0-1000:00: attached PHY driver (mii_bus:phy_addr=r8169-0-1000:00, irq=MAC) [ 88.597726] r8169 :10:00.0 enp16s0: Link is Down [ 88.954450] r8169 :10:00.0: invalid VPD tag 0x00 (size 0) at offset 0; assume missing optional EEPROM [ 91.387970] r8169 :10:00.0 enp16s0: Link is Up - 1Gbps/Full - flow control rx [ 676.228332] NETDEV WATCHDOG: enp16s0 (r8169): transmit queue 0 timed out 8812 ms [ 676.228459] efi_pstore ip_tables x_tables autofs4 dm_crypt raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear amdgpu hid_generic drm_exec amdxcp drm_buddy gpu_sched i2c_algo_bit drm_suballoc_helper drm_ttm_helper usbhid ttm hid drm_display_helper crct10dif_pclmul crc32_pclmul cec polyval_clmulni polyval_generic ghash_clmulni_intel rc_core sha256_ssse3 sha1_ssse3 aesni_intel drm_kms_helper crypto_simd cryptd nvme ahci r8169 i2c_piix4 libahci drm xhci_pci realtek xhci_pci_renesas nvme_core nvme_common video wmi [ 676.251897] r8169 :10:00.0 enp16s0: ASPM disabled on Tx timeout [ 677.182454] r8169 :10:00.0 enp16s0: rtl_rxtx_empty_cond == 0 (loop: 42, delay: 100). [ 687.887349] r8169 :10:00.0 enp16s0: rtl_rxtx_empty_cond == 0 (loop: 42, delay: 100). [ 697.751323] r8169 :10:00.0 enp16s0: rtl_rxtx_empty_cond == 0 (loop: 42, delay: 100). [ 708.256989] r8169 :10:00.0 enp16s0: rtl_rxtx_empty_cond == 0 (loop: 42, delay: 100). [ 708.271577] workqueue: rtl_task [r8169] hogged CPU for >1us 4 times, consider switching to WQ_UNBOUND [ 719.261374] r8169 :10:00.0 enp16s0: rtl_rxtx_empty_cond == 0 (loop: 42, delay: 100). [ 729.243408] r8169 :10:00.0 enp16s0: rtl_rxtx_empty_cond == 0 (loop: 42, delay: 100). [ 756.125596] r8169 :10:00.0 enp16s0: rtl_rxtx_empty_cond == 0 (loop: 42, delay: 100). [ 777.378563] r8169 :10:00.0 enp16s0: rtl_rxtx_empty_cond == 0 (loop: 42, delay: 100). [ 777.393781] workqueue: rtl_task [r8169] hogged CPU for >1us 8 times, consider switching to WQ_UNBOUND [ 783.258565] r8169 :10:00.0 enp16s0: rtl_rxtx_empty_cond == 0 (loop: 42, delay: 100). [ 793.961760] r8169 :10:00.0 enp16s0: rtl_rxtx_empty_cond == 0 (loop: 42, delay: 100). [ 857.275069] workqueue: rtl_task [r8169] hogged CPU for >1us 16 times, consider switching to WQ_UNBOUND [ 879.729545] r8169 :10:00.0 enp16s0: rtl_rxtx_empty_cond == 0 (loop: 42, delay: 100). [ 890.520666] r8169 :10:00.0 enp16s0: rtl_rxtx_empty_cond == 0 (loop: 42, delay: 100). [ 901.070260] r8169 :10:00.0 enp16s0: rtl_rxtx_empty_cond == 0 (loop: 42, delay: 100). [ 912.018121] r8169 :10:00.0 enp16s0: rtl_rxtx_empty_cond == 0 (loop: 42, delay: 100). [ 922.172608] r8169 :10:00.0 enp16s0: rtl_rxtx_empty_cond == 0 (loop: 42, delay: 100). [ 944.126660] r8169 :10:00.0 enp16s0: rtl_rxtx_empty_cond == 0 (loop: 42, delay: 100). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2042877 Title: kernel: r8169 :0d:00.0 enp13s0: rtl_rxtx_empty_cond == 0 (loop: 42, delay: 100). Status in linux-signed-hwe-6.2 package in Ubuntu: Incomplete Bug description: I tried everything. Manually installed the latest kernel, no luck. Updated the driver, also no luck. Here is my lshw output: id: network description: Ethernet interface product: RTL8125 2.5GbE Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:0d:00.0 logical name: enp13s0 version: 05 serial: XXX size: 1Gbit/s capacity: 1Gbit/s width:64 bits clock:33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuration: autonegotiation = on broadcast = yes driver= r8169 driverversion = 6.2.0-36-generic duplex= full firmware = rtl8125b-2_0.0.2 07/13/20 ip= 192.168.0.228 latency = 0 link = yes multicast = yes port = twisted pair speed = 1Gbit/s resources: irq : 34 ioport: f000(size=256) memory: fc70-fc70 memory: fc71-fc713fff
[Kernel-packages] [Bug 2045931] Re: ps3 sixasis controller request pin to connect to bt
Looks like this is a reported regression in the security pocket. ** Information type changed from Public to Public Security -- 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: Confirmed 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
Reopening because a PIN of is not reported to work (and even if it did, that would still be a regression in a stable release). ** Changed in: bluez (Ubuntu) Status: Incomplete => Confirmed ** Changed in: bluez (Ubuntu) Importance: Undecided => Critical -- 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: Confirmed 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 2045951] Re: GpuWatchdog segfault in libcef.so
The mainline kernel mapping has no entry for 6.2 (https://people.canonical.com/~kernel/info/kernel-version-map.html) so I took a guess and installed https://kernel.ubuntu.com/mainline/v6.2/ (AMD64). Testing this. I also tried https://kernel.ubuntu.com/mainline/v6.7-rc5/ but the header package requires a newer libc and so failed. Hence my Nvidia drivers wouldn't build. So that wasn't an option. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2045951 Title: GpuWatchdog segfault in libcef.so Status in linux-signed-hwe-6.2 package in Ubuntu: Confirmed Bug description: The GpuWatchdog can segfault when using apps that use Electron (https://www.electronjs.org/) which uses the Chromium Embedded Framework (CEF) [Steam, Code, Spotify, Teams, Discord...]. Indeed the same crash can occur in Chrome and Brave. In my specific case this occurs when I have switched off my monitor and left the computer go idle for a while (I don't know the timings exactly and I don't know how to force the situation). The computer remains responsive until I log back in from the Mate lock screen [note: if I lock my screen I get the light-locker log-in so I do not know what causes the machine to choose the Mate lock screen]. Upon logging back in the system becomes unresponsive. I can access the machine over SSH and force a reboot. The segfault in GpuWatchdog appears immediately on logging back in. For me, this first appears to have occured on Dec 2. Dec 2 22:49:52 ken kernel: [191969.402923] GpuWatchdog[9387]: segfault at 0 ip 7efc77192336 sp 7efc6b9fd370 error 6 in libcef.so[7efc72cef000+776f000] likely on CPU 3 (core 3, socket 0) Dec 2 22:49:52 ken kernel: [191969.402960] Code: 89 de e8 3d ef 6e ff 80 7d cf 00 79 09 48 8b 7d b8 e8 be 65 2c 03 41 8b 84 24 e0 00 00 00 89 45 b8 48 8d 7d b8 e8 ca d7 b5 fb 04 25 00 00 00 00 37 13 00 00 48 83 c4 38 5b 41 5c 41 5d 41 5e I can find no earlier entry in the syslog. My apt history shows nothing obvious but I'll attach it anyway. This GpuWatchdog segfault in libcef.so seems to occur a surprising amount around the Internet but the trigger seems to vary. Nonetheless CEF shouldn't be causing systems to become unresponsive. It is possible (probable) there is a bug in the CEF, but equally it should not be able to make a system unresponsive unless there is a bug in the kernel or X – this occurs on all kinds of systems with all kinds of graphics so the graphics driver seems an unlikely cause. It is not unique to Ubuntu but I don't know where to start given all the possible components. The only upstream reported kernel bug was closed as not enough information was supplied: https://bugzilla.kernel.org/show_bug.cgi?id=209129 This has been reported for Ubuntu a number of times but I thought it best to start fresh: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-450/+bug/1896560 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861294 https://bugs.launchpad.net/ubuntu/+source/syslog-ng/+bug/1903203 https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1921286 From around the Interwebs: https://bbs.archlinux.org/viewtopic.php?id=263124 https://askubuntu.com/q/1490916/170177 https://github.com/ValveSoftware/steam-for-linux/issues/7370 https://github.com/ValveSoftware/steam-for-linux/issues/9793 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040399 https://unix.stackexchange.com/q/658684/45386 https://www.linuxquestions.org/questions/linux-software-2/kde-plasma-on-wayland-hardware-acceleration-lock-ups-4175718801/ For testing I tried the following but couldn't trigger this manually: Windows+L to lock screen, switch monitor off, switch back on and log back in. Windows+L to lock screen, switch monitor off, switch back on, choose "Switch user" and log back in. xset dpms force off then wake the screen up. Any ideas how to continue would be greatly appreciated. I'll test the upstream kernel and report back. Might take a day or two. I'm not 100% convinced it's a kernel bug at this point though. I also note the --disable-gpu-* options for CEF which I'll also test. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-37-generic 6.2.0-37.38~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: MATE Date: Fri Dec 8 07:09:25 2023 SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2019-08-06T11:56:22.315382 To manage notifications about
[Kernel-packages] [Bug 2042877] Re: kernel: r8169 0000:0d:00.0 enp13s0: rtl_rxtx_empty_cond == 0 (loop: 42, delay: 100).
Please provide the dmesg log. You may have better luck with the r8169 binary package. ** Changed in: linux-signed-hwe-6.2 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2042877 Title: kernel: r8169 :0d:00.0 enp13s0: rtl_rxtx_empty_cond == 0 (loop: 42, delay: 100). Status in linux-signed-hwe-6.2 package in Ubuntu: Incomplete Bug description: I tried everything. Manually installed the latest kernel, no luck. Updated the driver, also no luck. Here is my lshw output: id: network description: Ethernet interface product: RTL8125 2.5GbE Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:0d:00.0 logical name: enp13s0 version: 05 serial: XXX size: 1Gbit/s capacity: 1Gbit/s width:64 bits clock:33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuration: autonegotiation = on broadcast = yes driver= r8169 driverversion = 6.2.0-36-generic duplex= full firmware = rtl8125b-2_0.0.2 07/13/20 ip= 192.168.0.228 latency = 0 link = yes multicast = yes port = twisted pair speed = 1Gbit/s resources: irq : 34 ioport: f000(size=256) memory: fc70-fc70 memory: fc71-fc713fff ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-36-generic 6.2.0-36.37~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Mon Nov 6 22:37:44 2023 InstallationDate: Installed on 2023-06-01 (158 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2042877/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2000947] Re: UVC Quanta 0408:4035 camera PROBLEM
@giuliano69,
when I was following post #19, each command was separately run in
terminal.
I got message from post #115 when I compiled script from directory
("./compile_module.sh").
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2000947
Title:
UVC Quanta 0408:4035 camera PROBLEM
Status in linux package in Ubuntu:
Confirmed
Bug description:
I bought a Acer Nitro 5 AN517-55 with Quanta ACER HD User Facing',
USB 0408:4035.
The camera is reported to have problems by many users:
https://linux-hardware.org/?id=usb:0408-4035
The uvc camera Quanta 0408:4035 does not work with ubuntu 22,04. the camera
is “recongized” but fails installation.
My console commands report similar info to other users:
https://unix.stackexchange.com/questions/723504/integrated-camera-not-detected-working-on-acer-nitro-5-an515-58
PROPOSED SOLUTION
I got in contact with laurent.pinch...@ideasonboard.com and with
riba...@chromium.org , and subscribed to https://www.linuxtv.org/lists. And
me...@vger.kernel.org mailinglist.
Laurent proposed me a fix and I modified the 5,15 uvc_driver.c
version, and loaded it on github
https://github.com/Giuliano69/uvc_driver-for-Quanta-HD-User-
Facing-0x0408-0x4035-/blob/main/uvc_driver.c
I offered to test the fix, so I tried to compile the module with the
new source.
COMPILING PROBLEMS
I’m running **Ubuntu 22.04.1 LTS, with kernel
giuliano@Astra2A:/usr/src$ cat /proc/version_signature
Ubuntu 5.15.0-56.62-generic 5.15.64
BUT the linux-source that I found installed seems to be different
tgiuliano@Astra2A:/usr/src$ ls -al linux-so*
lrwxrwxrwx 1 root root 47 nov 22 16:08 linux-source-5.15.0.tar.bz2 ->
linux-source-5.15.0/linux-source-5.15.0.tar.bz2
I expanded the tar file, configured the IDE and compiled without error any
errors…
I manually copied the uvcvideo.ko in
/lib/modules/5.15.0-56-
sudo cp…...
then tryed to intall the new uvcvideo.ko module
sudo rmmod uvcvideo && sudo modprobe uvcvideo
BUT… IT FAILS
giuliano@Astra2A:~$ sudo rmmod uvcvideo && sudo modprobe uvcvideo
modprobe: ERROR: could not insert 'uvcvideo': Exec format error
and dmesg shows
[25961.151982] usbcore: registered new interface driver uvcvideo
[26323.125534] usbcore: deregistering interface driver uvcvideo
[26323.189294] uvcvideo: disagrees about version of symbol module_layout
These are the TWO modinfo from the old and new uvcvideo modules
https://pastebin.com/tSj8Exm6
Basically
OLD module: vermagic: 5.15.0-56-generic SMP mod_unload modversions
NEW module: vermagic: 5.15.64 SMP mod_unload modversions
-kindly ASK
HOW can FORCE the uvcdriver.c to match mi kernel version ?
Have I got OTHER ways to make the kernel module I’m compiling, match my
running system ?
I would like to test the module so to confirm the patch and let it
enter the kernel main stream...
BR
Giuliano
PS
btw…. to allow Eclipse to compile the kernel, I had to pass this commands
scripts/config --disable CONFIG_SYSTEM_REVOCATION_KEYS
scripts/config --disable SYSTEM_REVOCATION_KEYS
scripts/config --disable SYSTEM_TRUSTED_KEYS
hope that this does not affect the module layout & checking
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: giuliano 2142 F pulseaudio
/dev/snd/pcmC1D0p: giuliano 2142 F...m pulseaudio
/dev/snd/controlC0: giuliano 2142 F pulseaudio
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2022-11-03 (66 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64
(20220809.1)
MachineType: Acer Nitro AN517-55
NonfreeKernelModules: nvidia_modeset nvidia
Package: linux (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=it_IT.UTF-8
SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-57-generic
root=UUID=f07e25f9-07e7-4a29-a15e-f481aa0ee0f2 ro rootflags=subvol=@ quiet
splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.15.0-57.63-generic 5.15.74
RelatedPackageVersions:
linux-restricted-modules-5.15.0-57-generic N/A
linux-backports-modules-5.15.0-57-generic N/A
linux-firmware 20220329.git681281e4-0ubuntu3.9
Tags: jammy
Uname: Linux 5.15.0-57-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark
_MarkForUpload: True
dmi.bios.date: 04/20/2022
dmi.bios.release: 1.6
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.06
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Ignis_ADH
[Kernel-packages] [Bug 2036287] Re: 6.2.0-32 kernel doesn't work with Asus Vivobook
** Changed in: linux-signed-hwe-6.2 (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2036287 Title: 6.2.0-32 kernel doesn't work with Asus Vivobook Status in linux-signed-hwe-6.2 package in Ubuntu: Fix Released Bug description: I have both kernel 6.2.0-32 and 6.2.0-26 installed on my Asus Vivobook. Since 6.2.0-32 install boot has been impossible. I think this may be a common problem as I'm seeing issues with Ubuntu: https://ubuntuforums.org/showthread.php?t=2490616 and Linux Mint: https://forums.linuxmint.com/viewtopic.php?t=403618 https://askubuntu.com/questions/1485350/booting-ubuntu-22-with- kernel-6-2-0-32-is-impossible ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-26-generic 6.2.0-26.26~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Sep 15 20:38:11 2023 InstallationDate: Installed on 2023-01-20 (238 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2036287/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2046071] Re: Brightness control is inoperative
Which older kernels? Also see https://wiki.ubuntu.com/Kernel/Bugs ** Changed in: linux-signed-hwe-6.2 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2046071 Title: Brightness control is inoperative Status in linux-signed-hwe-6.2 package in Ubuntu: Incomplete Bug description: I can't control the brightness at, be it from the fn buttons or the GUI. The brightness is set to the max level with any way to lower it or control it. This problem doesn't exist in older kernels. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-37-generic 6.2.0-37.38~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Dec 10 17:48:35 2023 InstallationDate: Installed on 2023-12-07 (3 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2046071/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039755] Re: kernel crashes in CIFS code
Have you tried the upstream kernel? Also see https://wiki.ubuntu.com/Kernel/Bugs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2039755 Title: kernel crashes in CIFS code Status in linux-signed-hwe-6.2 package in Ubuntu: Confirmed Bug description: I've had several crashes like this on 2 different systems mounting the same SMB server. Oct 19 13:25:47 1y51573u kernel: [ 1103.030468] [ cut here ] Oct 19 13:25:47 1y51573u kernel: [ 1103.030477] WARNING: CPU: 2 PID: 5411 at fs/cifs/connect.c:1979 __cifs_put_smb_ses+0x3dd/0x4d0 [cifs] Oct 19 13:25:47 1y51573u kernel: [ 1103.030684] Modules linked in: nls_utf8 cifs cifs_arc4 cifs_md4 fscache netfs ccm xt_conntrack nft_chain_nat xt_MASQUERADE nf_nat nf_conntrack_netlink nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xfrm_u ser xfrm_algo xt_addrtype nft_compat nf_tables nfnetlink br_netfilter bridge stp llc rfcomm cmac algif_hash algif_skcipher af_alg bnep snd_hda_codec_hdmi overlay zram snd_sof_pci_intel_cnl snd_sof_intel_hda_common soundwire_intel soundw ire_generic_allocation soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_sof_utils snd_soc_hdac_hda snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi soundwire_bus mei_pxp mei_hdcp snd_soc_core snd_ctl_ led snd_compress intel_tcc_cooling ac97_bus snd_hda_codec_realtek snd_pcm_dmaengine snd_hda_codec_generic x86_pkg_temp_thermal intel_rapl_msr binfmt_misc intel_powerclamp joydev coretemp snd_hda_intel dell_rbtn snd_intel_dspcfg snd_inte l_sdw_acpi kvm_intel snd_hda_codec snd_hda_core snd_hwdep dell_laptop dell_smm_hwmon Oct 19 13:25:47 1y51573u kernel: [ 1103.030844] nls_iso8859_1 kvm snd_pcm irqbypass snd_seq_midi rapl snd_seq_midi_event intel_cstate dell_wmi snd_rawmidi serio_raw uvcvideo typec_displayport dell_wmi_sysman dell_smbios snd_seq iwlmvm btusb dcdbas btrtl snd_seq_device firmware_attributes_class ledtrig_audio dell_wmi_descriptor videobuf2_vmalloc wmi_bmof intel_wmi_thunderbolt btbcm mac80211 snd_timer videobuf2_memops cmdlinepart videobuf2_v4l2 btintel spi_nor snd btmt k mtd libarc4 soundcore videodev bluetooth processor_thermal_device_pci_legacy hid_sensor_custom_intel_hinge hid_sensor_als input_leds hid_sensor_gyro_3d videobuf2_common hid_multitouch processor_thermal_device iwlwifi hid_sensor_trigge r mc ecdh_generic processor_thermal_rfim industrialio_triggered_buffer processor_thermal_mbox kfifo_buf mei_me ecc hid_sensor_iio_common cfg80211 processor_thermal_rapl mei industrialio intel_rapl_common intel_soc_dts_iosf intel_pch_the rmal int3403_thermal int340x_thermal_zone mac_hid int3400_thermal intel_hid sparse_keymap Oct 19 13:25:47 1y51573u kernel: [ 1103.030992] soc_button_array acpi_thermal_rel acpi_pad sch_fq_codel msr parport_pc ppdev lp parport efi_pstore ip_tables x_tables autofs4 btrfs blake2b_generic xor raid6_pq libcrc32c r8153_ecm cdc_et her usbnet r8152 dm_crypt mii usbhid hid_sensor_custom hid_sensor_hub intel_ishtp_hid i915 drm_buddy i2c_algo_bit hid_generic ttm crct10dif_pclmul drm_display_helper crc32_pclmul cec polyval_clmulni rc_core polyval_generic ghash_clmulni _intel drm_kms_helper sha512_ssse3 syscopyarea aesni_intel sysfillrect rtsx_pci_sdmmc nvme sysimgblt intel_lpss_pci spi_intel_pc i i2c_i801 ucsi_acpi intel_lpss crypto_simd nvme_core i2c_smbus xhci_pci typec_ucsi spi_intel drm intel_ish_ipc psmouse thunderbolt nvme_common i2c_hid_acpi rtsx_pci xhci_pci_renesas idma64 cryptd typec intel_ishtp i2c_hid hid video wmi pinctrl_cannonlake z3fold zstd Oct 19 13:25:47 1y51573u kernel: [ 1103.031153] CPU: 2 PID: 5411 Comm: kworker/2:1 Not tainted 6.2.0-34-generic #34~22.04.1-Ubuntu Oct 19 13:25:47 1y51573u kernel: [ 1103.031162] Hardware name: Dell Inc. Latitude 7410/0M5G57, BIOS 1.24.0 07/06/2023 Oct 19 13:25:47 1y51573u kernel: [ 1103.031167] Workqueue: events delayed_mntput Oct 19 13:25:47 1y51573u kernel: [ 1103.031180] RIP: 0010:__cifs_put_smb_ses+0x3dd/0x4d0 [cifs] Oct 19 13:25:47 1y51573u kernel: [ 1103.031364] Code: e8 48 c7 c1 70 32 fe c1 48 c7 c2 30 e4 00 c2 41 89 c1 48 c7 c6 68 7f ff c1 48 c7 c7 d0 47 05 c2 e8 a8 b5 4f de e9 21 ff ff ff <0f> 0b e9 a6 fc ff ff 49 8d 5e 20 48 89 df e8 00 47 d4 de 48 c7 c6 Oct 19 13:25:47 1y51573u kernel: [ 1103.031371] RSP: 0018:b01c50b9bd38 EFLAGS: 00010286 Oct 19 13:25:47 1y51573u kernel: [ 1103.031378] RAX: RBX: 9d72da1353c0 RCX: Oct 19 13:25:47 1y51573u kernel: [ 1103.031383] RDX: RSI: RDI: Oct 19 13:25:47 1y51573u kernel: [ 1103.031387] RBP: b01c50b9bd68 R08: R09: Oct 19 13:25:47 1y51573u kernel: [ 1103.031391] R10: R11: R12: 9d72ca687800 Oct 19 13:25:47 1y51573u
[Kernel-packages] [Bug 2046141] Re: os drivers error view in laptop so i want solution
What the hell is this supposed to be? ** Changed in: linux-signed-hwe-6.2 (Ubuntu) Status: New => Invalid ** Changed in: linux-signed-hwe-6.2 (Ubuntu) Assignee: AshimShaheer (ashimsha) => (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2046141 Title: os drivers error view in laptop so i want solution Status in linux-signed-hwe-6.2 package in Ubuntu: Invalid Bug description: The text in the image you sent is: **Send problem report to the developers?** **Package** linux-image-6.2.0-37-generic 6.2.0-37.38~22.04.1 **✓ Problem Type** Bug ** ApportVersion** 2.20.11-0ubuntu82.5 ** Architecture** amd64 **✓ CasperMD5CheckResult** pass **✓ CurrentDesktop** ubuntu:GNOME ** Date** Mon Dec 11 13:51:59 2023 > Dependencies ** DistroRelease** Ubuntu 22.04 **✓ InstallationDate** Installed on 2023-12-04 (7 days ago) ** InstallationMedia** Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) **✓ PackageArchitecture** amd64 > ProcCpuinfoMinimal > ProcEnviron **✓ ProcVersionSignature** Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16 ** SourcePackage** linux-signed-hwe-6.2 **✓ Tags** jammy wayland-session **✓ Uname** Linux 6.2.0-37-generic x86_64 **✓ UpgradeStatus** No upgrade log present (probably fresh install) **Note:** The `>` symbol at the beginning of two lines indicates that the information on those lines is optional. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-37-generic 6.2.0-37.38~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Dec 11 13:27:04 2023 InstallationDate: Installed on 2023-12-04 (7 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2046141/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2018236] Re: Fix ADL: System shutdown automatically when run Prime95 with i9-12900K
** Changed in: thermald (Ubuntu Focal) Status: In Progress => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/2018236 Title: Fix ADL: System shutdown automatically when run Prime95 with i9-12900K Status in linux package in Ubuntu: Fix Released Status in linux-meta-hwe-5.15 package in Ubuntu: New Status in thermald package in Ubuntu: Fix Released Status in linux source package in Focal: New Status in linux-meta-hwe-5.15 source package in Focal: New Status in thermald source package in Focal: Confirmed Status in linux source package in Jammy: New Status in linux-meta-hwe-5.15 source package in Jammy: Invalid Status in thermald source package in Jammy: Fix Released Bug description: [Description] System shutdown automatically when stressing the machine. [Fix] Need these two to fix the issue. cbdd92b) Parse idsp and trips d385f20) Use PL1 max/min from PPCC when policies match https://github.com/intel/thermal_daemon/commit/d385f20764e1e5477450405be71ec719adc973be [Test Case] 1. Find a unit with i9-12900k CPU and air cooling 2. Install tools #sudo apt install stress-ng s-tui #sudo systemctl stop thermald #sudo thermald --no-daemon --loglevel=debug --adaptive --ignore-cpuid-check > thermald_log.txt & #download prime95 linux version: p95v308b15.linux64.tar.gz and decompress 4. Stress test: (you may need to open multiple terminals for the test) #./mprime #sudo stress-ng -a 0 --class cpu,cpu-cache --ignite-cpu -v 5. monitor cpu temperature for 6 hours if you didn’t hit overheat and shutdown issue. #sudo s-tui -c [Where problems could occur] low To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2018236/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2046141] [NEW] os drivers error view in laptop so i want solution
Public bug reported: The text in the image you sent is: **Send problem report to the developers?** **Package** linux-image-6.2.0-37-generic 6.2.0-37.38~22.04.1 **✓ Problem Type** Bug ** ApportVersion** 2.20.11-0ubuntu82.5 ** Architecture** amd64 **✓ CasperMD5CheckResult** pass **✓ CurrentDesktop** ubuntu:GNOME ** Date** Mon Dec 11 13:51:59 2023 > Dependencies ** DistroRelease** Ubuntu 22.04 **✓ InstallationDate** Installed on 2023-12-04 (7 days ago) ** InstallationMedia** Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) **✓ PackageArchitecture** amd64 > ProcCpuinfoMinimal > ProcEnviron **✓ ProcVersionSignature** Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16 ** SourcePackage** linux-signed-hwe-6.2 **✓ Tags** jammy wayland-session **✓ Uname** Linux 6.2.0-37-generic x86_64 **✓ UpgradeStatus** No upgrade log present (probably fresh install) **Note:** The `>` symbol at the beginning of two lines indicates that the information on those lines is optional. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-37-generic 6.2.0-37.38~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Dec 11 13:27:04 2023 InstallationDate: Installed on 2023-12-04 (7 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-6.2 (Ubuntu) Importance: Undecided Assignee: AshimShaheer (ashimsha) Status: New ** Tags: amd64 apport-bug jammy wayland-session ** Changed in: linux-signed-hwe-6.2 (Ubuntu) Assignee: (unassigned) => AshimShaheer (ashimsha) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2046141 Title: os drivers error view in laptop so i want solution Status in linux-signed-hwe-6.2 package in Ubuntu: New Bug description: The text in the image you sent is: **Send problem report to the developers?** **Package** linux-image-6.2.0-37-generic 6.2.0-37.38~22.04.1 **✓ Problem Type** Bug ** ApportVersion** 2.20.11-0ubuntu82.5 ** Architecture** amd64 **✓ CasperMD5CheckResult** pass **✓ CurrentDesktop** ubuntu:GNOME ** Date** Mon Dec 11 13:51:59 2023 > Dependencies ** DistroRelease** Ubuntu 22.04 **✓ InstallationDate** Installed on 2023-12-04 (7 days ago) ** InstallationMedia** Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) **✓ PackageArchitecture** amd64 > ProcCpuinfoMinimal > ProcEnviron **✓ ProcVersionSignature** Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16 ** SourcePackage** linux-signed-hwe-6.2 **✓ Tags** jammy wayland-session **✓ Uname** Linux 6.2.0-37-generic x86_64 **✓ UpgradeStatus** No upgrade log present (probably fresh install) **Note:** The `>` symbol at the beginning of two lines indicates that the information on those lines is optional. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-37-generic 6.2.0-37.38~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Dec 11 13:27:04 2023 InstallationDate: Installed on 2023-12-04 (7 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2046141/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2045951] Re: GpuWatchdog segfault in libcef.so
I left the computer to lock itself and killed all steamwebhelper processes before attempting to log in. The system once again became unusable but no segault occurred. It's possible the segfault is a symptom rather than a cure. Nonetheless there are no logs to help debug any further. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2045951 Title: GpuWatchdog segfault in libcef.so Status in linux-signed-hwe-6.2 package in Ubuntu: Confirmed Bug description: The GpuWatchdog can segfault when using apps that use Electron (https://www.electronjs.org/) which uses the Chromium Embedded Framework (CEF) [Steam, Code, Spotify, Teams, Discord...]. Indeed the same crash can occur in Chrome and Brave. In my specific case this occurs when I have switched off my monitor and left the computer go idle for a while (I don't know the timings exactly and I don't know how to force the situation). The computer remains responsive until I log back in from the Mate lock screen [note: if I lock my screen I get the light-locker log-in so I do not know what causes the machine to choose the Mate lock screen]. Upon logging back in the system becomes unresponsive. I can access the machine over SSH and force a reboot. The segfault in GpuWatchdog appears immediately on logging back in. For me, this first appears to have occured on Dec 2. Dec 2 22:49:52 ken kernel: [191969.402923] GpuWatchdog[9387]: segfault at 0 ip 7efc77192336 sp 7efc6b9fd370 error 6 in libcef.so[7efc72cef000+776f000] likely on CPU 3 (core 3, socket 0) Dec 2 22:49:52 ken kernel: [191969.402960] Code: 89 de e8 3d ef 6e ff 80 7d cf 00 79 09 48 8b 7d b8 e8 be 65 2c 03 41 8b 84 24 e0 00 00 00 89 45 b8 48 8d 7d b8 e8 ca d7 b5 fb 04 25 00 00 00 00 37 13 00 00 48 83 c4 38 5b 41 5c 41 5d 41 5e I can find no earlier entry in the syslog. My apt history shows nothing obvious but I'll attach it anyway. This GpuWatchdog segfault in libcef.so seems to occur a surprising amount around the Internet but the trigger seems to vary. Nonetheless CEF shouldn't be causing systems to become unresponsive. It is possible (probable) there is a bug in the CEF, but equally it should not be able to make a system unresponsive unless there is a bug in the kernel or X – this occurs on all kinds of systems with all kinds of graphics so the graphics driver seems an unlikely cause. It is not unique to Ubuntu but I don't know where to start given all the possible components. The only upstream reported kernel bug was closed as not enough information was supplied: https://bugzilla.kernel.org/show_bug.cgi?id=209129 This has been reported for Ubuntu a number of times but I thought it best to start fresh: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-450/+bug/1896560 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861294 https://bugs.launchpad.net/ubuntu/+source/syslog-ng/+bug/1903203 https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1921286 From around the Interwebs: https://bbs.archlinux.org/viewtopic.php?id=263124 https://askubuntu.com/q/1490916/170177 https://github.com/ValveSoftware/steam-for-linux/issues/7370 https://github.com/ValveSoftware/steam-for-linux/issues/9793 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040399 https://unix.stackexchange.com/q/658684/45386 https://www.linuxquestions.org/questions/linux-software-2/kde-plasma-on-wayland-hardware-acceleration-lock-ups-4175718801/ For testing I tried the following but couldn't trigger this manually: Windows+L to lock screen, switch monitor off, switch back on and log back in. Windows+L to lock screen, switch monitor off, switch back on, choose "Switch user" and log back in. xset dpms force off then wake the screen up. Any ideas how to continue would be greatly appreciated. I'll test the upstream kernel and report back. Might take a day or two. I'm not 100% convinced it's a kernel bug at this point though. I also note the --disable-gpu-* options for CEF which I'll also test. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-37-generic 6.2.0-37.38~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: MATE Date: Fri Dec 8 07:09:25 2023 SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2019-08-06T11:56:22.315382 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2045951/+subscriptions --
[Kernel-packages] [Bug 2046085] Re: Problem with driver for Realtek 8852be Wi-Fi pci card
I contacted device manufacturer, they provided me a driver in .tar.gz format, any chance to sign it to use with secure boot ? I am going to attach this driver just in case someone would need it for their's Higole PC ** Attachment added: "rtl8852BE_WiFi_linux.tar.gz" https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2046085/+attachment/5728206/+files/rtl8852BE_WiFi_linux.tar.gz -- 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/2046085 Title: Problem with driver for Realtek 8852be Wi-Fi pci card Status in linux-firmware package in Ubuntu: New Bug description: I am not sure that this shall come into Ubuntu bug tracker, but correct me if I am wrong. I have a fan-less media pc that has PCI WI-FI adapter rtl8852be. I know this chipset has support in HWE Ubuntu kernel but for some reason, firmware for it still not being recognized. First I tried to make it work with 6.2 generic HWE kernel and the only strings I have in dmesg: [ 15.034783] rtw89_8852be :03:00.0: enabling device ( -> 0003) [ 15.061504] rtw89_8852be :03:00.0: no suitable firmware found [ 15.061543] rtw89_8852be :03:00.0: failed to recognize firmware [ 15.061557] rtw89_8852be :03:00.0: failed to setup chip information [ 15.075283] rtw89_8852be: probe of :03:00.0 failed with error -2 Then I tried to use linux-image-6.5.0-1009-oem kernel and get a little bit more info: [ 16.501540] rtw89_8852be :03:00.0: loaded firmware rtw89/rtw8852b_fw-1.bin [ 16.503083] rtw89_8852be :03:00.0: enabling device ( -> 0003) [ 16.567443] rtw89_8852be :03:00.0: xtal si not ready(R): offset=41 [ 16.567470] rtw89_8852be :03:00.0: no suitable firmware found [ 16.567494] rtw89_8852be :03:00.0: failed to recognize firmware [ 16.567509] rtw89_8852be :03:00.0: failed to setup chip information [ 16.572860] rtw89_8852be: probe of :03:00.0 failed with error -2 I suspect my PCI WIFI card has different subvendor ID and subdevice ID compare to the popular ones: Lenovo laptops have 8852be has PCI 10ec:b852:17aa:4853 HP laptops have 8852be has PCI 10ec:b852:103c:88e3 Mine is: PCI 10ec:b852:10ec:b852 Any suggestions are welcomed. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-firmware 20220329.git681281e4-0ubuntu3.23 ProcVersionSignature: Ubuntu 6.5.0-1009.10-oem 6.5.3 Uname: Linux 6.5.0-1009-oem x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CasperMD5CheckResult: unknown CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config Date: Sun Dec 10 21:46:40 2023 Dependencies: firmware-sof-signed 2.0-1ubuntu4.4 InstallationDate: Installed on 2023-09-15 (86 days ago) InstallationMedia: Ubuntu-Server 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230810) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:b85b Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 006: ID 1cf1:0030 Dresden Elektronik ZigBee gateway [ConBee II] Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: SDZ X133 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-1009-oem root=UUID=cd870d97-e484-43d5-aafa-2ba1ec68a7a8 ro cpufreq.default_governor=powersave RelatedPackageVersions: linux-restricted-modules-6.5.0-1009-oem N/A linux-backports-modules-6.5.0-1009-oem N/A linux-firmware 20220329.git681281e4-0ubuntu3.23 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2023 dmi.bios.release: 1.20 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: PC_STICK_8G_D8R2 dmi.board.asset.tag: Default string dmi.board.name: X133 dmi.board.vendor: SDZ dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: SDZ dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrPC_STICK_8G_D8R2:bd05/12/2023:br1.20:svnSDZ:pnX133:pvrDefaultstring:rvnSDZ:rnX133:rvrDefaultstring:cvnSDZ:ct10:cvrDefaultstring:skuDefaultstring: dmi.product.family: Notebook dmi.product.name: X133 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: SDZ To manage notifications about this bug go to:
[Kernel-packages] [Bug 2046131] Re: drm/amd: Disable PSR-SU to fix the brightness issue
** Also affects: linux-oem-6.1 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-6.1 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux-oem-6.5 (Ubuntu) Status: New => In Progress ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-oem-6.1 (Ubuntu) Status: New => In Progress ** Changed in: hwe-next Status: New => In Progress ** Changed in: hwe-next Importance: Undecided => High ** Changed in: linux-oem-6.1 (Ubuntu) Importance: Undecided => High ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Importance: Undecided => High ** Changed in: linux-oem-6.5 (Ubuntu) Importance: Undecided => High ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Importance: Undecided => High ** Changed in: hwe-next Assignee: (unassigned) => AaronMa (mapengyu) -- 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: In Progress Status in linux-oem-6.5 package in Ubuntu: In Progress Status in linux source package in Jammy: New Status in linux-oem-6.1 source package in Jammy: In Progress Status in linux-oem-6.5 source package in Jammy: In Progress 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. 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 2046131] Re: drm/amd: Disable PSR-SU to fix the brightness issue
** Tags added: oem-priority originate-from-2044994 sutton -- 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/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: In Progress Status in linux-oem-6.5 package in Ubuntu: In Progress Status in linux source package in Jammy: New Status in linux-oem-6.1 source package in Jammy: In Progress Status in linux-oem-6.5 source package in Jammy: In Progress 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. 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 2018236] Re: Fix ADL: System shutdown automatically when run Prime95 with i9-12900K
** Changed in: thermald (Ubuntu Focal) Assignee: koba (kobako) => Kai-Heng Feng (kaihengfeng) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/2018236 Title: Fix ADL: System shutdown automatically when run Prime95 with i9-12900K Status in linux package in Ubuntu: Fix Released Status in linux-meta-hwe-5.15 package in Ubuntu: New Status in thermald package in Ubuntu: Fix Released Status in linux source package in Focal: New Status in linux-meta-hwe-5.15 source package in Focal: New Status in thermald source package in Focal: In Progress Status in linux source package in Jammy: New Status in linux-meta-hwe-5.15 source package in Jammy: Invalid Status in thermald source package in Jammy: Fix Released Bug description: [Description] System shutdown automatically when stressing the machine. [Fix] Need these two to fix the issue. cbdd92b) Parse idsp and trips d385f20) Use PL1 max/min from PPCC when policies match https://github.com/intel/thermal_daemon/commit/d385f20764e1e5477450405be71ec719adc973be [Test Case] 1. Find a unit with i9-12900k CPU and air cooling 2. Install tools #sudo apt install stress-ng s-tui #sudo systemctl stop thermald #sudo thermald --no-daemon --loglevel=debug --adaptive --ignore-cpuid-check > thermald_log.txt & #download prime95 linux version: p95v308b15.linux64.tar.gz and decompress 4. Stress test: (you may need to open multiple terminals for the test) #./mprime #sudo stress-ng -a 0 --class cpu,cpu-cache --ignite-cpu -v 5. monitor cpu temperature for 6 hours if you didn’t hit overheat and shutdown issue. #sudo s-tui -c [Where problems could occur] low To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2018236/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
