[Kernel-packages] [Bug 2033295] Re: AMDGPU: Screen frequently and suddenly freezes. Hard reboot necessary. AMD Ryzen
Same problem here on Ubuntu 22.04.3 with latest and updated 6.2 kernel. On a Thinkpad P14s gen1 20Y with a Ryzen 4750u pro. It is not possible to use this laptop with Ubuntu 23.04 (I tried, same problem because same kernel I guess) nor 22.04.3. -- 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/2033295 Title: AMDGPU: Screen frequently and suddenly freezes. Hard reboot necessary. AMD Ryzen Status in linux package in Ubuntu: Confirmed Bug description: Frequently, when I just use the computer, the mouse cursor freezes, the screen starts to flicker and freezes (screen flickers between entirely black and desktop visible). No interaction possible. In most cases Ctrl-Alt-Prnt-REISUB works to hard reboot the system. Frequency: Freezes happen several times a day. Unsaved work is lost. I noticed that: * The freezes usually happen when an external display is connected (it does not matter whether USB-C or HDMI). The freezes rarely happen when no external display is connected. * The freezes happen with Wayland and X11, with Ubuntu UI and Gnome Shell. * The freezes happen randomly, but I have the feeling that they happen more often when "something graphical" happens, e.g. when I go to the Gnome Shell overview, desktop switching, or when I switch to/from full screen mode, click on an image to scale it, or when I use map services in the web browser like Google Maps or radio.garden. * The freezes even more often happened when WebGL is active in Firefox or Chomium. * I encounter these annoying freezes already for several weeks. Having looked at the log files, I assume that AMDGPU is at the core of the problem. System: Ubuntu 23.04 (up to date), Wayland (freezes also happen with X11), Gnome 44.3. Linux 6.2.0-31-generic Lenovo ThinkPad T14s Gen 1 (with most recent BIOS/UEFI 1.44), AMD Ryzen™ 7 PRO 4750U with Radeon™ Graphics × 16. --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2021-06-06 (813 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 20UJS00K00 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-31-generic root=UUID=9eae73b3-aab9-4f80-9203-01ac00f03c33 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-31.31-generic 6.2.15 RelatedPackageVersions: linux-restricted-modules-6.2.0-31-generic N/A linux-backports-modules-6.2.0-31-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1.6 Tags: lunar wayland-session Uname: Linux 6.2.0-31-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-05-11 (110 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/13/2023 dmi.bios.release: 1.44 dmi.bios.vendor: LENOVO dmi.bios.version: R1CET75W(1.44 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UJS00K00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.44 dmi.modalias: dmi:bvnLENOVO:bvrR1CET75W(1.44):bd06/13/2023:br1.44:efr1.44:svnLENOVO:pn20UJS00K00:pvrThinkPadT14sGen1:rvnLENOVO:rn20UJS00K00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20UJ_BU_Think_FM_ThinkPadT14sGen1: dmi.product.family: ThinkPad T14s Gen 1 dmi.product.name: 20UJS00K00 dmi.product.sku: LENOVO_MT_20UJ_BU_Think_FM_ThinkPad T14s Gen 1 dmi.product.version: ThinkPad T14s Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033295/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037390] Re: Missing firmware for Intel CNVi AX211 on Intel Meteor Lake platform
apport information ** Tags added: apport-collected jammy third-party-packages ** Description changed: WIFI FW: Line 1092: [ 7.971227] iwlwifi :00:14.3: PCI dev 7e40/4090, rev=0x441, rfid=0x2010d000 Line 1118: [ 7.971719] iwlwifi :00:14.3: no suitable firmware found! Line 1119: [ 7.971720] iwlwifi :00:14.3: minimum version required: iwlwifi-ma-b0-gf-a0-59 Line 1120: [ 7.971721] iwlwifi :00:14.3: maximum version supported: iwlwifi-ma-b0-gf-a0-83 Line 1121: [ 7.971721] iwlwifi :00:14.3: check git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git Bluetooth FW: Line 1123: [ 7.974156] Bluetooth: hci0: Failed to load Intel firmware file intel/ibt-0180-0041.sfi (-2) + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu82.5 + Architecture: amd64 + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: + CRDA: N/A + CasperMD5CheckResult: pass + Dependencies: firmware-sof-signed 2.0-1ubuntu4.2+exp.7 [origin: LP-PPA-canonical-hwe-team-linux-firmware-staging] + DistributionChannelDescriptor: + # This is the distribution channel descriptor for the OEM CDs + # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor + canonical-oem-jiayi-jammy-amd64-20230706-44 + DistroRelease: Ubuntu 22.04 + InstallationDate: Installed on 2023-07-06 (82 days ago) + InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - pc-jiayi-jammy-amd64-20230706-44 + MachineType: Intel Corporation Meteor Lake Client Platform + Package: linux-firmware 20220329.git681281e4-0ubuntu3.19+exp.83 [origin: LP-PPA-canonical-hwe-team-linux-firmware-staging] + PackageArchitecture: all + ProcFB: 0 i915drmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9004-oem root=UUID=3019b32e-e421-4827-87dd-877e9cff7126 ro i915.force_probe=7d55 quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 6.5.0-9004.4+exp.11-oem 6.5.3 + PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. + RelatedPackageVersions: + linux-restricted-modules-6.5.0-9004-oem N/A + linux-backports-modules-6.5.0-9004-oem N/A + linux-firmware 20220329.git681281e4-0ubuntu3.19+exp.83 + Tags: third-party-packages jammy + Uname: Linux 6.5.0-9004-oem x86_64 + UnreportableReason: This does not seem to be an official Ubuntu package. Please retry after updating the indexes of available packages, if that does not work then remove related third party packages and try again. + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: N/A + _MarkForUpload: True + dmi.bios.date: 03/21/2023 + dmi.bios.vendor: Intel Corporation + dmi.bios.version: MTLPFWI1.R00.3084.D89.2303211034 + dmi.board.asset.tag: Base Board Asset Tag + dmi.board.name: MTL-P DDR5 SODIMM SBS RVP + dmi.board.vendor: Intel Corporation + dmi.board.version: 1 + dmi.chassis.asset.tag: Chassis Asset Tag + dmi.chassis.type: 9 + dmi.chassis.vendor: Intel Corporation + dmi.chassis.version: 0.1 + dmi.ec.firmware.release: 1.71 + dmi.modalias: dmi:bvnIntelCorporation:bvrMTLPFWI1.R00.3084.D89.2303211034:bd03/21/2023:efr1.71:svnIntelCorporation:pnMeteorLakeClientPlatform:pvr0.1:rvnIntelCorporation:rnMTL-PDDR5SODIMMSBSRVP:rvr1:cvnIntelCorporation:ct9:cvr0.1:sku010010020001: + dmi.product.family: Meteor Lake Client System + dmi.product.name: Meteor Lake Client Platform + dmi.product.sku: 010010020001 + dmi.product.version: 0.1 + dmi.sys.vendor: Intel Corporation ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/2037390/+attachment/5704845/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2037390 Title: Missing firmware for Intel CNVi AX211 on Intel Meteor Lake platform Status in HWE Next: New Status in linux-firmware package in Ubuntu: Triaged Status in linux-firmware source package in Jammy: Triaged Status in linux-firmware source package in Mantic: Triaged Bug description: WIFI FW: Line 1092: [ 7.971227] iwlwifi :00:14.3: PCI dev 7e40/4090, rev=0x441, rfid=0x2010d000 Line 1118: [ 7.971719] iwlwifi :00:14.3: no suitable firmware found! Line 1119: [ 7.971720] iwlwifi :00:14.3: minimum version required: iwlwifi-ma-b0-gf-a0-59 Line 1120: [ 7.971721] iwlwifi :00:14.3: maximum version supported: iwlwifi-ma-b0-gf-a0-83 Line 1121: [ 7.971721] iwlwifi :00:14.3: check git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git Bluetooth FW: Line 1123: [ 7.974156] Bluetooth: hci0: Failed to load Intel firmware file intel/ibt-0180-0041.sfi (-2) --- ProblemType: Bug ApportVers
[Kernel-packages] [Bug 2037390] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/2037390/+attachment/5704846/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2037390 Title: Missing firmware for Intel CNVi AX211 on Intel Meteor Lake platform Status in HWE Next: New Status in linux-firmware package in Ubuntu: Triaged Status in linux-firmware source package in Jammy: Triaged Status in linux-firmware source package in Mantic: Triaged Bug description: WIFI FW: Line 1092: [ 7.971227] iwlwifi :00:14.3: PCI dev 7e40/4090, rev=0x441, rfid=0x2010d000 Line 1118: [ 7.971719] iwlwifi :00:14.3: no suitable firmware found! Line 1119: [ 7.971720] iwlwifi :00:14.3: minimum version required: iwlwifi-ma-b0-gf-a0-59 Line 1120: [ 7.971721] iwlwifi :00:14.3: maximum version supported: iwlwifi-ma-b0-gf-a0-83 Line 1121: [ 7.971721] iwlwifi :00:14.3: check git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git Bluetooth FW: Line 1123: [ 7.974156] Bluetooth: hci0: Failed to load Intel firmware file intel/ibt-0180-0041.sfi (-2) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: pass Dependencies: firmware-sof-signed 2.0-1ubuntu4.2+exp.7 [origin: LP-PPA-canonical-hwe-team-linux-firmware-staging] DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-jiayi-jammy-amd64-20230706-44 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-07-06 (82 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - pc-jiayi-jammy-amd64-20230706-44 MachineType: Intel Corporation Meteor Lake Client Platform Package: linux-firmware 20220329.git681281e4-0ubuntu3.19+exp.83 [origin: LP-PPA-canonical-hwe-team-linux-firmware-staging] PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9004-oem root=UUID=3019b32e-e421-4827-87dd-877e9cff7126 ro i915.force_probe=7d55 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.5.0-9004.4+exp.11-oem 6.5.3 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.5.0-9004-oem N/A linux-backports-modules-6.5.0-9004-oem N/A linux-firmware 20220329.git681281e4-0ubuntu3.19+exp.83 Tags: third-party-packages jammy Uname: Linux 6.5.0-9004-oem x86_64 UnreportableReason: This does not seem to be an official Ubuntu package. Please retry after updating the indexes of available packages, if that does not work then remove related third party packages and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 03/21/2023 dmi.bios.vendor: Intel Corporation dmi.bios.version: MTLPFWI1.R00.3084.D89.2303211034 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: MTL-P DDR5 SODIMM SBS RVP dmi.board.vendor: Intel Corporation dmi.board.version: 1 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.71 dmi.modalias: dmi:bvnIntelCorporation:bvrMTLPFWI1.R00.3084.D89.2303211034:bd03/21/2023:efr1.71:svnIntelCorporation:pnMeteorLakeClientPlatform:pvr0.1:rvnIntelCorporation:rnMTL-PDDR5SODIMMSBSRVP:rvr1:cvnIntelCorporation:ct9:cvr0.1:sku010010020001: dmi.product.family: Meteor Lake Client System dmi.product.name: Meteor Lake Client Platform dmi.product.sku: 010010020001 dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2037390/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037390] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/2037390/+attachment/5704847/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2037390 Title: Missing firmware for Intel CNVi AX211 on Intel Meteor Lake platform Status in HWE Next: New Status in linux-firmware package in Ubuntu: Triaged Status in linux-firmware source package in Jammy: Triaged Status in linux-firmware source package in Mantic: Triaged Bug description: WIFI FW: Line 1092: [ 7.971227] iwlwifi :00:14.3: PCI dev 7e40/4090, rev=0x441, rfid=0x2010d000 Line 1118: [ 7.971719] iwlwifi :00:14.3: no suitable firmware found! Line 1119: [ 7.971720] iwlwifi :00:14.3: minimum version required: iwlwifi-ma-b0-gf-a0-59 Line 1120: [ 7.971721] iwlwifi :00:14.3: maximum version supported: iwlwifi-ma-b0-gf-a0-83 Line 1121: [ 7.971721] iwlwifi :00:14.3: check git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git Bluetooth FW: Line 1123: [ 7.974156] Bluetooth: hci0: Failed to load Intel firmware file intel/ibt-0180-0041.sfi (-2) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: pass Dependencies: firmware-sof-signed 2.0-1ubuntu4.2+exp.7 [origin: LP-PPA-canonical-hwe-team-linux-firmware-staging] DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-jiayi-jammy-amd64-20230706-44 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-07-06 (82 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - pc-jiayi-jammy-amd64-20230706-44 MachineType: Intel Corporation Meteor Lake Client Platform Package: linux-firmware 20220329.git681281e4-0ubuntu3.19+exp.83 [origin: LP-PPA-canonical-hwe-team-linux-firmware-staging] PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9004-oem root=UUID=3019b32e-e421-4827-87dd-877e9cff7126 ro i915.force_probe=7d55 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.5.0-9004.4+exp.11-oem 6.5.3 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.5.0-9004-oem N/A linux-backports-modules-6.5.0-9004-oem N/A linux-firmware 20220329.git681281e4-0ubuntu3.19+exp.83 Tags: third-party-packages jammy Uname: Linux 6.5.0-9004-oem x86_64 UnreportableReason: This does not seem to be an official Ubuntu package. Please retry after updating the indexes of available packages, if that does not work then remove related third party packages and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 03/21/2023 dmi.bios.vendor: Intel Corporation dmi.bios.version: MTLPFWI1.R00.3084.D89.2303211034 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: MTL-P DDR5 SODIMM SBS RVP dmi.board.vendor: Intel Corporation dmi.board.version: 1 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.71 dmi.modalias: dmi:bvnIntelCorporation:bvrMTLPFWI1.R00.3084.D89.2303211034:bd03/21/2023:efr1.71:svnIntelCorporation:pnMeteorLakeClientPlatform:pvr0.1:rvnIntelCorporation:rnMTL-PDDR5SODIMMSBSRVP:rvr1:cvnIntelCorporation:ct9:cvr0.1:sku010010020001: dmi.product.family: Meteor Lake Client System dmi.product.name: Meteor Lake Client Platform dmi.product.sku: 010010020001 dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2037390/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037390] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/2037390/+attachment/5704848/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2037390 Title: Missing firmware for Intel CNVi AX211 on Intel Meteor Lake platform Status in HWE Next: New Status in linux-firmware package in Ubuntu: Triaged Status in linux-firmware source package in Jammy: Triaged Status in linux-firmware source package in Mantic: Triaged Bug description: WIFI FW: Line 1092: [ 7.971227] iwlwifi :00:14.3: PCI dev 7e40/4090, rev=0x441, rfid=0x2010d000 Line 1118: [ 7.971719] iwlwifi :00:14.3: no suitable firmware found! Line 1119: [ 7.971720] iwlwifi :00:14.3: minimum version required: iwlwifi-ma-b0-gf-a0-59 Line 1120: [ 7.971721] iwlwifi :00:14.3: maximum version supported: iwlwifi-ma-b0-gf-a0-83 Line 1121: [ 7.971721] iwlwifi :00:14.3: check git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git Bluetooth FW: Line 1123: [ 7.974156] Bluetooth: hci0: Failed to load Intel firmware file intel/ibt-0180-0041.sfi (-2) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: pass Dependencies: firmware-sof-signed 2.0-1ubuntu4.2+exp.7 [origin: LP-PPA-canonical-hwe-team-linux-firmware-staging] DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-jiayi-jammy-amd64-20230706-44 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-07-06 (82 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - pc-jiayi-jammy-amd64-20230706-44 MachineType: Intel Corporation Meteor Lake Client Platform Package: linux-firmware 20220329.git681281e4-0ubuntu3.19+exp.83 [origin: LP-PPA-canonical-hwe-team-linux-firmware-staging] PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9004-oem root=UUID=3019b32e-e421-4827-87dd-877e9cff7126 ro i915.force_probe=7d55 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.5.0-9004.4+exp.11-oem 6.5.3 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.5.0-9004-oem N/A linux-backports-modules-6.5.0-9004-oem N/A linux-firmware 20220329.git681281e4-0ubuntu3.19+exp.83 Tags: third-party-packages jammy Uname: Linux 6.5.0-9004-oem x86_64 UnreportableReason: This does not seem to be an official Ubuntu package. Please retry after updating the indexes of available packages, if that does not work then remove related third party packages and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 03/21/2023 dmi.bios.vendor: Intel Corporation dmi.bios.version: MTLPFWI1.R00.3084.D89.2303211034 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: MTL-P DDR5 SODIMM SBS RVP dmi.board.vendor: Intel Corporation dmi.board.version: 1 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.71 dmi.modalias: dmi:bvnIntelCorporation:bvrMTLPFWI1.R00.3084.D89.2303211034:bd03/21/2023:efr1.71:svnIntelCorporation:pnMeteorLakeClientPlatform:pvr0.1:rvnIntelCorporation:rnMTL-PDDR5SODIMMSBSRVP:rvr1:cvnIntelCorporation:ct9:cvr0.1:sku010010020001: dmi.product.family: Meteor Lake Client System dmi.product.name: Meteor Lake Client Platform dmi.product.sku: 010010020001 dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2037390/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037390] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/2037390/+attachment/5704849/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2037390 Title: Missing firmware for Intel CNVi AX211 on Intel Meteor Lake platform Status in HWE Next: New Status in linux-firmware package in Ubuntu: Triaged Status in linux-firmware source package in Jammy: Triaged Status in linux-firmware source package in Mantic: Triaged Bug description: WIFI FW: Line 1092: [ 7.971227] iwlwifi :00:14.3: PCI dev 7e40/4090, rev=0x441, rfid=0x2010d000 Line 1118: [ 7.971719] iwlwifi :00:14.3: no suitable firmware found! Line 1119: [ 7.971720] iwlwifi :00:14.3: minimum version required: iwlwifi-ma-b0-gf-a0-59 Line 1120: [ 7.971721] iwlwifi :00:14.3: maximum version supported: iwlwifi-ma-b0-gf-a0-83 Line 1121: [ 7.971721] iwlwifi :00:14.3: check git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git Bluetooth FW: Line 1123: [ 7.974156] Bluetooth: hci0: Failed to load Intel firmware file intel/ibt-0180-0041.sfi (-2) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: pass Dependencies: firmware-sof-signed 2.0-1ubuntu4.2+exp.7 [origin: LP-PPA-canonical-hwe-team-linux-firmware-staging] DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-jiayi-jammy-amd64-20230706-44 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-07-06 (82 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - pc-jiayi-jammy-amd64-20230706-44 MachineType: Intel Corporation Meteor Lake Client Platform Package: linux-firmware 20220329.git681281e4-0ubuntu3.19+exp.83 [origin: LP-PPA-canonical-hwe-team-linux-firmware-staging] PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9004-oem root=UUID=3019b32e-e421-4827-87dd-877e9cff7126 ro i915.force_probe=7d55 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.5.0-9004.4+exp.11-oem 6.5.3 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.5.0-9004-oem N/A linux-backports-modules-6.5.0-9004-oem N/A linux-firmware 20220329.git681281e4-0ubuntu3.19+exp.83 Tags: third-party-packages jammy Uname: Linux 6.5.0-9004-oem x86_64 UnreportableReason: This does not seem to be an official Ubuntu package. Please retry after updating the indexes of available packages, if that does not work then remove related third party packages and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 03/21/2023 dmi.bios.vendor: Intel Corporation dmi.bios.version: MTLPFWI1.R00.3084.D89.2303211034 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: MTL-P DDR5 SODIMM SBS RVP dmi.board.vendor: Intel Corporation dmi.board.version: 1 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.71 dmi.modalias: dmi:bvnIntelCorporation:bvrMTLPFWI1.R00.3084.D89.2303211034:bd03/21/2023:efr1.71:svnIntelCorporation:pnMeteorLakeClientPlatform:pvr0.1:rvnIntelCorporation:rnMTL-PDDR5SODIMMSBSRVP:rvr1:cvnIntelCorporation:ct9:cvr0.1:sku010010020001: dmi.product.family: Meteor Lake Client System dmi.product.name: Meteor Lake Client Platform dmi.product.sku: 010010020001 dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2037390/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037390] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/2037390/+attachment/5704850/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2037390 Title: Missing firmware for Intel CNVi AX211 on Intel Meteor Lake platform Status in HWE Next: New Status in linux-firmware package in Ubuntu: Triaged Status in linux-firmware source package in Jammy: Triaged Status in linux-firmware source package in Mantic: Triaged Bug description: WIFI FW: Line 1092: [ 7.971227] iwlwifi :00:14.3: PCI dev 7e40/4090, rev=0x441, rfid=0x2010d000 Line 1118: [ 7.971719] iwlwifi :00:14.3: no suitable firmware found! Line 1119: [ 7.971720] iwlwifi :00:14.3: minimum version required: iwlwifi-ma-b0-gf-a0-59 Line 1120: [ 7.971721] iwlwifi :00:14.3: maximum version supported: iwlwifi-ma-b0-gf-a0-83 Line 1121: [ 7.971721] iwlwifi :00:14.3: check git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git Bluetooth FW: Line 1123: [ 7.974156] Bluetooth: hci0: Failed to load Intel firmware file intel/ibt-0180-0041.sfi (-2) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: pass Dependencies: firmware-sof-signed 2.0-1ubuntu4.2+exp.7 [origin: LP-PPA-canonical-hwe-team-linux-firmware-staging] DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-jiayi-jammy-amd64-20230706-44 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-07-06 (82 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - pc-jiayi-jammy-amd64-20230706-44 MachineType: Intel Corporation Meteor Lake Client Platform Package: linux-firmware 20220329.git681281e4-0ubuntu3.19+exp.83 [origin: LP-PPA-canonical-hwe-team-linux-firmware-staging] PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9004-oem root=UUID=3019b32e-e421-4827-87dd-877e9cff7126 ro i915.force_probe=7d55 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.5.0-9004.4+exp.11-oem 6.5.3 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.5.0-9004-oem N/A linux-backports-modules-6.5.0-9004-oem N/A linux-firmware 20220329.git681281e4-0ubuntu3.19+exp.83 Tags: third-party-packages jammy Uname: Linux 6.5.0-9004-oem x86_64 UnreportableReason: This does not seem to be an official Ubuntu package. Please retry after updating the indexes of available packages, if that does not work then remove related third party packages and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 03/21/2023 dmi.bios.vendor: Intel Corporation dmi.bios.version: MTLPFWI1.R00.3084.D89.2303211034 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: MTL-P DDR5 SODIMM SBS RVP dmi.board.vendor: Intel Corporation dmi.board.version: 1 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.71 dmi.modalias: dmi:bvnIntelCorporation:bvrMTLPFWI1.R00.3084.D89.2303211034:bd03/21/2023:efr1.71:svnIntelCorporation:pnMeteorLakeClientPlatform:pvr0.1:rvnIntelCorporation:rnMTL-PDDR5SODIMMSBSRVP:rvr1:cvnIntelCorporation:ct9:cvr0.1:sku010010020001: dmi.product.family: Meteor Lake Client System dmi.product.name: Meteor Lake Client Platform dmi.product.sku: 010010020001 dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2037390/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037390] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/2037390/+attachment/5704851/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2037390 Title: Missing firmware for Intel CNVi AX211 on Intel Meteor Lake platform Status in HWE Next: New Status in linux-firmware package in Ubuntu: Triaged Status in linux-firmware source package in Jammy: Triaged Status in linux-firmware source package in Mantic: Triaged Bug description: WIFI FW: Line 1092: [ 7.971227] iwlwifi :00:14.3: PCI dev 7e40/4090, rev=0x441, rfid=0x2010d000 Line 1118: [ 7.971719] iwlwifi :00:14.3: no suitable firmware found! Line 1119: [ 7.971720] iwlwifi :00:14.3: minimum version required: iwlwifi-ma-b0-gf-a0-59 Line 1120: [ 7.971721] iwlwifi :00:14.3: maximum version supported: iwlwifi-ma-b0-gf-a0-83 Line 1121: [ 7.971721] iwlwifi :00:14.3: check git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git Bluetooth FW: Line 1123: [ 7.974156] Bluetooth: hci0: Failed to load Intel firmware file intel/ibt-0180-0041.sfi (-2) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: pass Dependencies: firmware-sof-signed 2.0-1ubuntu4.2+exp.7 [origin: LP-PPA-canonical-hwe-team-linux-firmware-staging] DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-jiayi-jammy-amd64-20230706-44 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-07-06 (82 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - pc-jiayi-jammy-amd64-20230706-44 MachineType: Intel Corporation Meteor Lake Client Platform Package: linux-firmware 20220329.git681281e4-0ubuntu3.19+exp.83 [origin: LP-PPA-canonical-hwe-team-linux-firmware-staging] PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9004-oem root=UUID=3019b32e-e421-4827-87dd-877e9cff7126 ro i915.force_probe=7d55 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.5.0-9004.4+exp.11-oem 6.5.3 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.5.0-9004-oem N/A linux-backports-modules-6.5.0-9004-oem N/A linux-firmware 20220329.git681281e4-0ubuntu3.19+exp.83 Tags: third-party-packages jammy Uname: Linux 6.5.0-9004-oem x86_64 UnreportableReason: This does not seem to be an official Ubuntu package. Please retry after updating the indexes of available packages, if that does not work then remove related third party packages and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 03/21/2023 dmi.bios.vendor: Intel Corporation dmi.bios.version: MTLPFWI1.R00.3084.D89.2303211034 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: MTL-P DDR5 SODIMM SBS RVP dmi.board.vendor: Intel Corporation dmi.board.version: 1 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.71 dmi.modalias: dmi:bvnIntelCorporation:bvrMTLPFWI1.R00.3084.D89.2303211034:bd03/21/2023:efr1.71:svnIntelCorporation:pnMeteorLakeClientPlatform:pvr0.1:rvnIntelCorporation:rnMTL-PDDR5SODIMMSBSRVP:rvr1:cvnIntelCorporation:ct9:cvr0.1:sku010010020001: dmi.product.family: Meteor Lake Client System dmi.product.name: Meteor Lake Client Platform dmi.product.sku: 010010020001 dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2037390/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037390] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/2037390/+attachment/5704852/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2037390 Title: Missing firmware for Intel CNVi AX211 on Intel Meteor Lake platform Status in HWE Next: New Status in linux-firmware package in Ubuntu: Triaged Status in linux-firmware source package in Jammy: Triaged Status in linux-firmware source package in Mantic: Triaged Bug description: WIFI FW: Line 1092: [ 7.971227] iwlwifi :00:14.3: PCI dev 7e40/4090, rev=0x441, rfid=0x2010d000 Line 1118: [ 7.971719] iwlwifi :00:14.3: no suitable firmware found! Line 1119: [ 7.971720] iwlwifi :00:14.3: minimum version required: iwlwifi-ma-b0-gf-a0-59 Line 1120: [ 7.971721] iwlwifi :00:14.3: maximum version supported: iwlwifi-ma-b0-gf-a0-83 Line 1121: [ 7.971721] iwlwifi :00:14.3: check git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git Bluetooth FW: Line 1123: [ 7.974156] Bluetooth: hci0: Failed to load Intel firmware file intel/ibt-0180-0041.sfi (-2) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: pass Dependencies: firmware-sof-signed 2.0-1ubuntu4.2+exp.7 [origin: LP-PPA-canonical-hwe-team-linux-firmware-staging] DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-jiayi-jammy-amd64-20230706-44 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-07-06 (82 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - pc-jiayi-jammy-amd64-20230706-44 MachineType: Intel Corporation Meteor Lake Client Platform Package: linux-firmware 20220329.git681281e4-0ubuntu3.19+exp.83 [origin: LP-PPA-canonical-hwe-team-linux-firmware-staging] PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9004-oem root=UUID=3019b32e-e421-4827-87dd-877e9cff7126 ro i915.force_probe=7d55 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.5.0-9004.4+exp.11-oem 6.5.3 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.5.0-9004-oem N/A linux-backports-modules-6.5.0-9004-oem N/A linux-firmware 20220329.git681281e4-0ubuntu3.19+exp.83 Tags: third-party-packages jammy Uname: Linux 6.5.0-9004-oem x86_64 UnreportableReason: This does not seem to be an official Ubuntu package. Please retry after updating the indexes of available packages, if that does not work then remove related third party packages and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 03/21/2023 dmi.bios.vendor: Intel Corporation dmi.bios.version: MTLPFWI1.R00.3084.D89.2303211034 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: MTL-P DDR5 SODIMM SBS RVP dmi.board.vendor: Intel Corporation dmi.board.version: 1 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.71 dmi.modalias: dmi:bvnIntelCorporation:bvrMTLPFWI1.R00.3084.D89.2303211034:bd03/21/2023:efr1.71:svnIntelCorporation:pnMeteorLakeClientPlatform:pvr0.1:rvnIntelCorporation:rnMTL-PDDR5SODIMMSBSRVP:rvr1:cvnIntelCorporation:ct9:cvr0.1:sku010010020001: dmi.product.family: Meteor Lake Client System dmi.product.name: Meteor Lake Client Platform dmi.product.sku: 010010020001 dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2037390/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037390] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/2037390/+attachment/5704853/+files/PaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2037390 Title: Missing firmware for Intel CNVi AX211 on Intel Meteor Lake platform Status in HWE Next: New Status in linux-firmware package in Ubuntu: Triaged Status in linux-firmware source package in Jammy: Triaged Status in linux-firmware source package in Mantic: Triaged Bug description: WIFI FW: Line 1092: [ 7.971227] iwlwifi :00:14.3: PCI dev 7e40/4090, rev=0x441, rfid=0x2010d000 Line 1118: [ 7.971719] iwlwifi :00:14.3: no suitable firmware found! Line 1119: [ 7.971720] iwlwifi :00:14.3: minimum version required: iwlwifi-ma-b0-gf-a0-59 Line 1120: [ 7.971721] iwlwifi :00:14.3: maximum version supported: iwlwifi-ma-b0-gf-a0-83 Line 1121: [ 7.971721] iwlwifi :00:14.3: check git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git Bluetooth FW: Line 1123: [ 7.974156] Bluetooth: hci0: Failed to load Intel firmware file intel/ibt-0180-0041.sfi (-2) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: pass Dependencies: firmware-sof-signed 2.0-1ubuntu4.2+exp.7 [origin: LP-PPA-canonical-hwe-team-linux-firmware-staging] DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-jiayi-jammy-amd64-20230706-44 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-07-06 (82 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - pc-jiayi-jammy-amd64-20230706-44 MachineType: Intel Corporation Meteor Lake Client Platform Package: linux-firmware 20220329.git681281e4-0ubuntu3.19+exp.83 [origin: LP-PPA-canonical-hwe-team-linux-firmware-staging] PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9004-oem root=UUID=3019b32e-e421-4827-87dd-877e9cff7126 ro i915.force_probe=7d55 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.5.0-9004.4+exp.11-oem 6.5.3 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.5.0-9004-oem N/A linux-backports-modules-6.5.0-9004-oem N/A linux-firmware 20220329.git681281e4-0ubuntu3.19+exp.83 Tags: third-party-packages jammy Uname: Linux 6.5.0-9004-oem x86_64 UnreportableReason: This does not seem to be an official Ubuntu package. Please retry after updating the indexes of available packages, if that does not work then remove related third party packages and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 03/21/2023 dmi.bios.vendor: Intel Corporation dmi.bios.version: MTLPFWI1.R00.3084.D89.2303211034 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: MTL-P DDR5 SODIMM SBS RVP dmi.board.vendor: Intel Corporation dmi.board.version: 1 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.71 dmi.modalias: dmi:bvnIntelCorporation:bvrMTLPFWI1.R00.3084.D89.2303211034:bd03/21/2023:efr1.71:svnIntelCorporation:pnMeteorLakeClientPlatform:pvr0.1:rvnIntelCorporation:rnMTL-PDDR5SODIMMSBSRVP:rvr1:cvnIntelCorporation:ct9:cvr0.1:sku010010020001: dmi.product.family: Meteor Lake Client System dmi.product.name: Meteor Lake Client Platform dmi.product.sku: 010010020001 dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2037390/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037390] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/2037390/+attachment/5704854/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2037390 Title: Missing firmware for Intel CNVi AX211 on Intel Meteor Lake platform Status in HWE Next: New Status in linux-firmware package in Ubuntu: Triaged Status in linux-firmware source package in Jammy: Triaged Status in linux-firmware source package in Mantic: Triaged Bug description: WIFI FW: Line 1092: [ 7.971227] iwlwifi :00:14.3: PCI dev 7e40/4090, rev=0x441, rfid=0x2010d000 Line 1118: [ 7.971719] iwlwifi :00:14.3: no suitable firmware found! Line 1119: [ 7.971720] iwlwifi :00:14.3: minimum version required: iwlwifi-ma-b0-gf-a0-59 Line 1120: [ 7.971721] iwlwifi :00:14.3: maximum version supported: iwlwifi-ma-b0-gf-a0-83 Line 1121: [ 7.971721] iwlwifi :00:14.3: check git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git Bluetooth FW: Line 1123: [ 7.974156] Bluetooth: hci0: Failed to load Intel firmware file intel/ibt-0180-0041.sfi (-2) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: pass Dependencies: firmware-sof-signed 2.0-1ubuntu4.2+exp.7 [origin: LP-PPA-canonical-hwe-team-linux-firmware-staging] DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-jiayi-jammy-amd64-20230706-44 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-07-06 (82 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - pc-jiayi-jammy-amd64-20230706-44 MachineType: Intel Corporation Meteor Lake Client Platform Package: linux-firmware 20220329.git681281e4-0ubuntu3.19+exp.83 [origin: LP-PPA-canonical-hwe-team-linux-firmware-staging] PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9004-oem root=UUID=3019b32e-e421-4827-87dd-877e9cff7126 ro i915.force_probe=7d55 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.5.0-9004.4+exp.11-oem 6.5.3 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.5.0-9004-oem N/A linux-backports-modules-6.5.0-9004-oem N/A linux-firmware 20220329.git681281e4-0ubuntu3.19+exp.83 Tags: third-party-packages jammy Uname: Linux 6.5.0-9004-oem x86_64 UnreportableReason: This does not seem to be an official Ubuntu package. Please retry after updating the indexes of available packages, if that does not work then remove related third party packages and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 03/21/2023 dmi.bios.vendor: Intel Corporation dmi.bios.version: MTLPFWI1.R00.3084.D89.2303211034 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: MTL-P DDR5 SODIMM SBS RVP dmi.board.vendor: Intel Corporation dmi.board.version: 1 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.71 dmi.modalias: dmi:bvnIntelCorporation:bvrMTLPFWI1.R00.3084.D89.2303211034:bd03/21/2023:efr1.71:svnIntelCorporation:pnMeteorLakeClientPlatform:pvr0.1:rvnIntelCorporation:rnMTL-PDDR5SODIMMSBSRVP:rvr1:cvnIntelCorporation:ct9:cvr0.1:sku010010020001: dmi.product.family: Meteor Lake Client System dmi.product.name: Meteor Lake Client Platform dmi.product.sku: 010010020001 dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2037390/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037390] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/2037390/+attachment/5704855/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2037390 Title: Missing firmware for Intel CNVi AX211 on Intel Meteor Lake platform Status in HWE Next: New Status in linux-firmware package in Ubuntu: Triaged Status in linux-firmware source package in Jammy: Triaged Status in linux-firmware source package in Mantic: Triaged Bug description: WIFI FW: Line 1092: [ 7.971227] iwlwifi :00:14.3: PCI dev 7e40/4090, rev=0x441, rfid=0x2010d000 Line 1118: [ 7.971719] iwlwifi :00:14.3: no suitable firmware found! Line 1119: [ 7.971720] iwlwifi :00:14.3: minimum version required: iwlwifi-ma-b0-gf-a0-59 Line 1120: [ 7.971721] iwlwifi :00:14.3: maximum version supported: iwlwifi-ma-b0-gf-a0-83 Line 1121: [ 7.971721] iwlwifi :00:14.3: check git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git Bluetooth FW: Line 1123: [ 7.974156] Bluetooth: hci0: Failed to load Intel firmware file intel/ibt-0180-0041.sfi (-2) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: pass Dependencies: firmware-sof-signed 2.0-1ubuntu4.2+exp.7 [origin: LP-PPA-canonical-hwe-team-linux-firmware-staging] DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-jiayi-jammy-amd64-20230706-44 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-07-06 (82 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - pc-jiayi-jammy-amd64-20230706-44 MachineType: Intel Corporation Meteor Lake Client Platform Package: linux-firmware 20220329.git681281e4-0ubuntu3.19+exp.83 [origin: LP-PPA-canonical-hwe-team-linux-firmware-staging] PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9004-oem root=UUID=3019b32e-e421-4827-87dd-877e9cff7126 ro i915.force_probe=7d55 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.5.0-9004.4+exp.11-oem 6.5.3 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.5.0-9004-oem N/A linux-backports-modules-6.5.0-9004-oem N/A linux-firmware 20220329.git681281e4-0ubuntu3.19+exp.83 Tags: third-party-packages jammy Uname: Linux 6.5.0-9004-oem x86_64 UnreportableReason: This does not seem to be an official Ubuntu package. Please retry after updating the indexes of available packages, if that does not work then remove related third party packages and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 03/21/2023 dmi.bios.vendor: Intel Corporation dmi.bios.version: MTLPFWI1.R00.3084.D89.2303211034 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: MTL-P DDR5 SODIMM SBS RVP dmi.board.vendor: Intel Corporation dmi.board.version: 1 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.71 dmi.modalias: dmi:bvnIntelCorporation:bvrMTLPFWI1.R00.3084.D89.2303211034:bd03/21/2023:efr1.71:svnIntelCorporation:pnMeteorLakeClientPlatform:pvr0.1:rvnIntelCorporation:rnMTL-PDDR5SODIMMSBSRVP:rvr1:cvnIntelCorporation:ct9:cvr0.1:sku010010020001: dmi.product.family: Meteor Lake Client System dmi.product.name: Meteor Lake Client Platform dmi.product.sku: 010010020001 dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2037390/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037390] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/2037390/+attachment/5704856/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2037390 Title: Missing firmware for Intel CNVi AX211 on Intel Meteor Lake platform Status in HWE Next: New Status in linux-firmware package in Ubuntu: Triaged Status in linux-firmware source package in Jammy: Triaged Status in linux-firmware source package in Mantic: Triaged Bug description: WIFI FW: Line 1092: [ 7.971227] iwlwifi :00:14.3: PCI dev 7e40/4090, rev=0x441, rfid=0x2010d000 Line 1118: [ 7.971719] iwlwifi :00:14.3: no suitable firmware found! Line 1119: [ 7.971720] iwlwifi :00:14.3: minimum version required: iwlwifi-ma-b0-gf-a0-59 Line 1120: [ 7.971721] iwlwifi :00:14.3: maximum version supported: iwlwifi-ma-b0-gf-a0-83 Line 1121: [ 7.971721] iwlwifi :00:14.3: check git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git Bluetooth FW: Line 1123: [ 7.974156] Bluetooth: hci0: Failed to load Intel firmware file intel/ibt-0180-0041.sfi (-2) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: pass Dependencies: firmware-sof-signed 2.0-1ubuntu4.2+exp.7 [origin: LP-PPA-canonical-hwe-team-linux-firmware-staging] DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-jiayi-jammy-amd64-20230706-44 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-07-06 (82 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - pc-jiayi-jammy-amd64-20230706-44 MachineType: Intel Corporation Meteor Lake Client Platform Package: linux-firmware 20220329.git681281e4-0ubuntu3.19+exp.83 [origin: LP-PPA-canonical-hwe-team-linux-firmware-staging] PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9004-oem root=UUID=3019b32e-e421-4827-87dd-877e9cff7126 ro i915.force_probe=7d55 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.5.0-9004.4+exp.11-oem 6.5.3 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.5.0-9004-oem N/A linux-backports-modules-6.5.0-9004-oem N/A linux-firmware 20220329.git681281e4-0ubuntu3.19+exp.83 Tags: third-party-packages jammy Uname: Linux 6.5.0-9004-oem x86_64 UnreportableReason: This does not seem to be an official Ubuntu package. Please retry after updating the indexes of available packages, if that does not work then remove related third party packages and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 03/21/2023 dmi.bios.vendor: Intel Corporation dmi.bios.version: MTLPFWI1.R00.3084.D89.2303211034 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: MTL-P DDR5 SODIMM SBS RVP dmi.board.vendor: Intel Corporation dmi.board.version: 1 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.71 dmi.modalias: dmi:bvnIntelCorporation:bvrMTLPFWI1.R00.3084.D89.2303211034:bd03/21/2023:efr1.71:svnIntelCorporation:pnMeteorLakeClientPlatform:pvr0.1:rvnIntelCorporation:rnMTL-PDDR5SODIMMSBSRVP:rvr1:cvnIntelCorporation:ct9:cvr0.1:sku010010020001: dmi.product.family: Meteor Lake Client System dmi.product.name: Meteor Lake Client Platform dmi.product.sku: 010010020001 dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2037390/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037390] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/2037390/+attachment/5704857/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2037390 Title: Missing firmware for Intel CNVi AX211 on Intel Meteor Lake platform Status in HWE Next: New Status in linux-firmware package in Ubuntu: Triaged Status in linux-firmware source package in Jammy: Triaged Status in linux-firmware source package in Mantic: Triaged Bug description: WIFI FW: Line 1092: [ 7.971227] iwlwifi :00:14.3: PCI dev 7e40/4090, rev=0x441, rfid=0x2010d000 Line 1118: [ 7.971719] iwlwifi :00:14.3: no suitable firmware found! Line 1119: [ 7.971720] iwlwifi :00:14.3: minimum version required: iwlwifi-ma-b0-gf-a0-59 Line 1120: [ 7.971721] iwlwifi :00:14.3: maximum version supported: iwlwifi-ma-b0-gf-a0-83 Line 1121: [ 7.971721] iwlwifi :00:14.3: check git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git Bluetooth FW: Line 1123: [ 7.974156] Bluetooth: hci0: Failed to load Intel firmware file intel/ibt-0180-0041.sfi (-2) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: pass Dependencies: firmware-sof-signed 2.0-1ubuntu4.2+exp.7 [origin: LP-PPA-canonical-hwe-team-linux-firmware-staging] DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-jiayi-jammy-amd64-20230706-44 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-07-06 (82 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - pc-jiayi-jammy-amd64-20230706-44 MachineType: Intel Corporation Meteor Lake Client Platform Package: linux-firmware 20220329.git681281e4-0ubuntu3.19+exp.83 [origin: LP-PPA-canonical-hwe-team-linux-firmware-staging] PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9004-oem root=UUID=3019b32e-e421-4827-87dd-877e9cff7126 ro i915.force_probe=7d55 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.5.0-9004.4+exp.11-oem 6.5.3 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.5.0-9004-oem N/A linux-backports-modules-6.5.0-9004-oem N/A linux-firmware 20220329.git681281e4-0ubuntu3.19+exp.83 Tags: third-party-packages jammy Uname: Linux 6.5.0-9004-oem x86_64 UnreportableReason: This does not seem to be an official Ubuntu package. Please retry after updating the indexes of available packages, if that does not work then remove related third party packages and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 03/21/2023 dmi.bios.vendor: Intel Corporation dmi.bios.version: MTLPFWI1.R00.3084.D89.2303211034 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: MTL-P DDR5 SODIMM SBS RVP dmi.board.vendor: Intel Corporation dmi.board.version: 1 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.71 dmi.modalias: dmi:bvnIntelCorporation:bvrMTLPFWI1.R00.3084.D89.2303211034:bd03/21/2023:efr1.71:svnIntelCorporation:pnMeteorLakeClientPlatform:pvr0.1:rvnIntelCorporation:rnMTL-PDDR5SODIMMSBSRVP:rvr1:cvnIntelCorporation:ct9:cvr0.1:sku010010020001: dmi.product.family: Meteor Lake Client System dmi.product.name: Meteor Lake Client Platform dmi.product.sku: 010010020001 dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2037390/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037390] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/2037390/+attachment/5704858/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2037390 Title: Missing firmware for Intel CNVi AX211 on Intel Meteor Lake platform Status in HWE Next: New Status in linux-firmware package in Ubuntu: Triaged Status in linux-firmware source package in Jammy: Triaged Status in linux-firmware source package in Mantic: Triaged Bug description: WIFI FW: Line 1092: [ 7.971227] iwlwifi :00:14.3: PCI dev 7e40/4090, rev=0x441, rfid=0x2010d000 Line 1118: [ 7.971719] iwlwifi :00:14.3: no suitable firmware found! Line 1119: [ 7.971720] iwlwifi :00:14.3: minimum version required: iwlwifi-ma-b0-gf-a0-59 Line 1120: [ 7.971721] iwlwifi :00:14.3: maximum version supported: iwlwifi-ma-b0-gf-a0-83 Line 1121: [ 7.971721] iwlwifi :00:14.3: check git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git Bluetooth FW: Line 1123: [ 7.974156] Bluetooth: hci0: Failed to load Intel firmware file intel/ibt-0180-0041.sfi (-2) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: pass Dependencies: firmware-sof-signed 2.0-1ubuntu4.2+exp.7 [origin: LP-PPA-canonical-hwe-team-linux-firmware-staging] DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-jiayi-jammy-amd64-20230706-44 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-07-06 (82 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - pc-jiayi-jammy-amd64-20230706-44 MachineType: Intel Corporation Meteor Lake Client Platform Package: linux-firmware 20220329.git681281e4-0ubuntu3.19+exp.83 [origin: LP-PPA-canonical-hwe-team-linux-firmware-staging] PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9004-oem root=UUID=3019b32e-e421-4827-87dd-877e9cff7126 ro i915.force_probe=7d55 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.5.0-9004.4+exp.11-oem 6.5.3 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.5.0-9004-oem N/A linux-backports-modules-6.5.0-9004-oem N/A linux-firmware 20220329.git681281e4-0ubuntu3.19+exp.83 Tags: third-party-packages jammy Uname: Linux 6.5.0-9004-oem x86_64 UnreportableReason: This does not seem to be an official Ubuntu package. Please retry after updating the indexes of available packages, if that does not work then remove related third party packages and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 03/21/2023 dmi.bios.vendor: Intel Corporation dmi.bios.version: MTLPFWI1.R00.3084.D89.2303211034 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: MTL-P DDR5 SODIMM SBS RVP dmi.board.vendor: Intel Corporation dmi.board.version: 1 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.71 dmi.modalias: dmi:bvnIntelCorporation:bvrMTLPFWI1.R00.3084.D89.2303211034:bd03/21/2023:efr1.71:svnIntelCorporation:pnMeteorLakeClientPlatform:pvr0.1:rvnIntelCorporation:rnMTL-PDDR5SODIMMSBSRVP:rvr1:cvnIntelCorporation:ct9:cvr0.1:sku010010020001: dmi.product.family: Meteor Lake Client System dmi.product.name: Meteor Lake Client Platform dmi.product.sku: 010010020001 dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2037390/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037390] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/2037390/+attachment/5704860/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2037390 Title: Missing firmware for Intel CNVi AX211 on Intel Meteor Lake platform Status in HWE Next: New Status in linux-firmware package in Ubuntu: Triaged Status in linux-firmware source package in Jammy: Triaged Status in linux-firmware source package in Mantic: Triaged Bug description: WIFI FW: Line 1092: [ 7.971227] iwlwifi :00:14.3: PCI dev 7e40/4090, rev=0x441, rfid=0x2010d000 Line 1118: [ 7.971719] iwlwifi :00:14.3: no suitable firmware found! Line 1119: [ 7.971720] iwlwifi :00:14.3: minimum version required: iwlwifi-ma-b0-gf-a0-59 Line 1120: [ 7.971721] iwlwifi :00:14.3: maximum version supported: iwlwifi-ma-b0-gf-a0-83 Line 1121: [ 7.971721] iwlwifi :00:14.3: check git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git Bluetooth FW: Line 1123: [ 7.974156] Bluetooth: hci0: Failed to load Intel firmware file intel/ibt-0180-0041.sfi (-2) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: pass Dependencies: firmware-sof-signed 2.0-1ubuntu4.2+exp.7 [origin: LP-PPA-canonical-hwe-team-linux-firmware-staging] DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-jiayi-jammy-amd64-20230706-44 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-07-06 (82 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - pc-jiayi-jammy-amd64-20230706-44 MachineType: Intel Corporation Meteor Lake Client Platform Package: linux-firmware 20220329.git681281e4-0ubuntu3.19+exp.83 [origin: LP-PPA-canonical-hwe-team-linux-firmware-staging] PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9004-oem root=UUID=3019b32e-e421-4827-87dd-877e9cff7126 ro i915.force_probe=7d55 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.5.0-9004.4+exp.11-oem 6.5.3 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.5.0-9004-oem N/A linux-backports-modules-6.5.0-9004-oem N/A linux-firmware 20220329.git681281e4-0ubuntu3.19+exp.83 Tags: third-party-packages jammy Uname: Linux 6.5.0-9004-oem x86_64 UnreportableReason: This does not seem to be an official Ubuntu package. Please retry after updating the indexes of available packages, if that does not work then remove related third party packages and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 03/21/2023 dmi.bios.vendor: Intel Corporation dmi.bios.version: MTLPFWI1.R00.3084.D89.2303211034 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: MTL-P DDR5 SODIMM SBS RVP dmi.board.vendor: Intel Corporation dmi.board.version: 1 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.71 dmi.modalias: dmi:bvnIntelCorporation:bvrMTLPFWI1.R00.3084.D89.2303211034:bd03/21/2023:efr1.71:svnIntelCorporation:pnMeteorLakeClientPlatform:pvr0.1:rvnIntelCorporation:rnMTL-PDDR5SODIMMSBSRVP:rvr1:cvnIntelCorporation:ct9:cvr0.1:sku010010020001: dmi.product.family: Meteor Lake Client System dmi.product.name: Meteor Lake Client Platform dmi.product.sku: 010010020001 dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2037390/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037390] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/2037390/+attachment/5704861/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2037390 Title: Missing firmware for Intel CNVi AX211 on Intel Meteor Lake platform Status in HWE Next: New Status in linux-firmware package in Ubuntu: Triaged Status in linux-firmware source package in Jammy: Triaged Status in linux-firmware source package in Mantic: Triaged Bug description: WIFI FW: Line 1092: [ 7.971227] iwlwifi :00:14.3: PCI dev 7e40/4090, rev=0x441, rfid=0x2010d000 Line 1118: [ 7.971719] iwlwifi :00:14.3: no suitable firmware found! Line 1119: [ 7.971720] iwlwifi :00:14.3: minimum version required: iwlwifi-ma-b0-gf-a0-59 Line 1120: [ 7.971721] iwlwifi :00:14.3: maximum version supported: iwlwifi-ma-b0-gf-a0-83 Line 1121: [ 7.971721] iwlwifi :00:14.3: check git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git Bluetooth FW: Line 1123: [ 7.974156] Bluetooth: hci0: Failed to load Intel firmware file intel/ibt-0180-0041.sfi (-2) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: pass Dependencies: firmware-sof-signed 2.0-1ubuntu4.2+exp.7 [origin: LP-PPA-canonical-hwe-team-linux-firmware-staging] DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-jiayi-jammy-amd64-20230706-44 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-07-06 (82 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - pc-jiayi-jammy-amd64-20230706-44 MachineType: Intel Corporation Meteor Lake Client Platform Package: linux-firmware 20220329.git681281e4-0ubuntu3.19+exp.83 [origin: LP-PPA-canonical-hwe-team-linux-firmware-staging] PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9004-oem root=UUID=3019b32e-e421-4827-87dd-877e9cff7126 ro i915.force_probe=7d55 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.5.0-9004.4+exp.11-oem 6.5.3 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.5.0-9004-oem N/A linux-backports-modules-6.5.0-9004-oem N/A linux-firmware 20220329.git681281e4-0ubuntu3.19+exp.83 Tags: third-party-packages jammy Uname: Linux 6.5.0-9004-oem x86_64 UnreportableReason: This does not seem to be an official Ubuntu package. Please retry after updating the indexes of available packages, if that does not work then remove related third party packages and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 03/21/2023 dmi.bios.vendor: Intel Corporation dmi.bios.version: MTLPFWI1.R00.3084.D89.2303211034 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: MTL-P DDR5 SODIMM SBS RVP dmi.board.vendor: Intel Corporation dmi.board.version: 1 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.71 dmi.modalias: dmi:bvnIntelCorporation:bvrMTLPFWI1.R00.3084.D89.2303211034:bd03/21/2023:efr1.71:svnIntelCorporation:pnMeteorLakeClientPlatform:pvr0.1:rvnIntelCorporation:rnMTL-PDDR5SODIMMSBSRVP:rvr1:cvnIntelCorporation:ct9:cvr0.1:sku010010020001: dmi.product.family: Meteor Lake Client System dmi.product.name: Meteor Lake Client Platform dmi.product.sku: 010010020001 dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2037390/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037390] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/2037390/+attachment/5704859/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2037390 Title: Missing firmware for Intel CNVi AX211 on Intel Meteor Lake platform Status in HWE Next: New Status in linux-firmware package in Ubuntu: Triaged Status in linux-firmware source package in Jammy: Triaged Status in linux-firmware source package in Mantic: Triaged Bug description: WIFI FW: Line 1092: [ 7.971227] iwlwifi :00:14.3: PCI dev 7e40/4090, rev=0x441, rfid=0x2010d000 Line 1118: [ 7.971719] iwlwifi :00:14.3: no suitable firmware found! Line 1119: [ 7.971720] iwlwifi :00:14.3: minimum version required: iwlwifi-ma-b0-gf-a0-59 Line 1120: [ 7.971721] iwlwifi :00:14.3: maximum version supported: iwlwifi-ma-b0-gf-a0-83 Line 1121: [ 7.971721] iwlwifi :00:14.3: check git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git Bluetooth FW: Line 1123: [ 7.974156] Bluetooth: hci0: Failed to load Intel firmware file intel/ibt-0180-0041.sfi (-2) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: pass Dependencies: firmware-sof-signed 2.0-1ubuntu4.2+exp.7 [origin: LP-PPA-canonical-hwe-team-linux-firmware-staging] DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-jiayi-jammy-amd64-20230706-44 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-07-06 (82 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - pc-jiayi-jammy-amd64-20230706-44 MachineType: Intel Corporation Meteor Lake Client Platform Package: linux-firmware 20220329.git681281e4-0ubuntu3.19+exp.83 [origin: LP-PPA-canonical-hwe-team-linux-firmware-staging] PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9004-oem root=UUID=3019b32e-e421-4827-87dd-877e9cff7126 ro i915.force_probe=7d55 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.5.0-9004.4+exp.11-oem 6.5.3 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.5.0-9004-oem N/A linux-backports-modules-6.5.0-9004-oem N/A linux-firmware 20220329.git681281e4-0ubuntu3.19+exp.83 Tags: third-party-packages jammy Uname: Linux 6.5.0-9004-oem x86_64 UnreportableReason: This does not seem to be an official Ubuntu package. Please retry after updating the indexes of available packages, if that does not work then remove related third party packages and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 03/21/2023 dmi.bios.vendor: Intel Corporation dmi.bios.version: MTLPFWI1.R00.3084.D89.2303211034 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: MTL-P DDR5 SODIMM SBS RVP dmi.board.vendor: Intel Corporation dmi.board.version: 1 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.71 dmi.modalias: dmi:bvnIntelCorporation:bvrMTLPFWI1.R00.3084.D89.2303211034:bd03/21/2023:efr1.71:svnIntelCorporation:pnMeteorLakeClientPlatform:pvr0.1:rvnIntelCorporation:rnMTL-PDDR5SODIMMSBSRVP:rvr1:cvnIntelCorporation:ct9:cvr0.1:sku010010020001: dmi.product.family: Meteor Lake Client System dmi.product.name: Meteor Lake Client Platform dmi.product.sku: 010010020001 dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2037390/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037390] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/2037390/+attachment/5704862/+files/acpidump.txt ** Also affects: linux-firmware (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-firmware (Ubuntu Mantic) Importance: Undecided Status: New ** Changed in: linux-firmware (Ubuntu Jammy) Status: New => Triaged ** Changed in: linux-firmware (Ubuntu Mantic) Status: New => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2037390 Title: Missing firmware for Intel CNVi AX211 on Intel Meteor Lake platform Status in HWE Next: New Status in linux-firmware package in Ubuntu: Triaged Status in linux-firmware source package in Jammy: Triaged Status in linux-firmware source package in Mantic: Triaged Bug description: WIFI FW: Line 1092: [ 7.971227] iwlwifi :00:14.3: PCI dev 7e40/4090, rev=0x441, rfid=0x2010d000 Line 1118: [ 7.971719] iwlwifi :00:14.3: no suitable firmware found! Line 1119: [ 7.971720] iwlwifi :00:14.3: minimum version required: iwlwifi-ma-b0-gf-a0-59 Line 1120: [ 7.971721] iwlwifi :00:14.3: maximum version supported: iwlwifi-ma-b0-gf-a0-83 Line 1121: [ 7.971721] iwlwifi :00:14.3: check git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git Bluetooth FW: Line 1123: [ 7.974156] Bluetooth: hci0: Failed to load Intel firmware file intel/ibt-0180-0041.sfi (-2) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: pass Dependencies: firmware-sof-signed 2.0-1ubuntu4.2+exp.7 [origin: LP-PPA-canonical-hwe-team-linux-firmware-staging] DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-jiayi-jammy-amd64-20230706-44 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-07-06 (82 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - pc-jiayi-jammy-amd64-20230706-44 MachineType: Intel Corporation Meteor Lake Client Platform Package: linux-firmware 20220329.git681281e4-0ubuntu3.19+exp.83 [origin: LP-PPA-canonical-hwe-team-linux-firmware-staging] PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9004-oem root=UUID=3019b32e-e421-4827-87dd-877e9cff7126 ro i915.force_probe=7d55 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.5.0-9004.4+exp.11-oem 6.5.3 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.5.0-9004-oem N/A linux-backports-modules-6.5.0-9004-oem N/A linux-firmware 20220329.git681281e4-0ubuntu3.19+exp.83 Tags: third-party-packages jammy Uname: Linux 6.5.0-9004-oem x86_64 UnreportableReason: This does not seem to be an official Ubuntu package. Please retry after updating the indexes of available packages, if that does not work then remove related third party packages and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 03/21/2023 dmi.bios.vendor: Intel Corporation dmi.bios.version: MTLPFWI1.R00.3084.D89.2303211034 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: MTL-P DDR5 SODIMM SBS RVP dmi.board.vendor: Intel Corporation dmi.board.version: 1 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.71 dmi.modalias: dmi:bvnIntelCorporation:bvrMTLPFWI1.R00.3084.D89.2303211034:bd03/21/2023:efr1.71:svnIntelCorporation:pnMeteorLakeClientPlatform:pvr0.1:rvnIntelCorporation:rnMTL-PDDR5SODIMMSBSRVP:rvr1:cvnIntelCorporation:ct9:cvr0.1:sku010010020001: dmi.product.family: Meteor Lake Client System dmi.product.name: Meteor Lake Client Platform dmi.product.sku: 010010020001 dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2037390/+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 2034099] Re: Bridge MTU not applied at first boot, only after netplan apply/networkctl reload
Submitted upstream for review:
https://lore.kernel.org/all/20230927075713.1253681-1-trent.ll...@canonical.com/T/#u
--
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/2034099
Title:
Bridge MTU not applied at first boot, only after netplan
apply/networkctl reload
Status in linux package in Ubuntu:
Confirmed
Bug description:
If you set a Bridge's MTU to a specific value using netplan/networkd
which is different to the MTU of the interface you add, it does not
appear to be applied correctly during boot.
However the MTU switches to the correct value when you re-apply the
configuration with "netplan apply" (or "systemctl restart systemd-
networkd"; "networkctl reload")
Additionally:
- It does apply correctly when you create the bridge for the first time
(after boot), I did not debug why.
- When deploying the same configuration with Juju & MAAS it works after first
boot (likely because juju modifies the netplan config and runs netplan apply)
but still fails on reboot.
== Cause ==
Linux bridges, by default, "auto-tune" the bridge MTU to MIN(mtu) of
all member ports. This is updated each time an interface is added or
removed (except with vlan aware mode, which uses MAX(mtu) instead).
If the user changes the MTU of the bridge explicitly, it disables this
behaviour since 804b854d374e ("net: bridge: disable bridge MTU auto
tuning if it was set manually") which landed in v4.17.
This is the expected behaviour, unfortunately that code has a bug in
that it only works if the bridge MTU is changed after it was created.
If the bridge MTU is set during bridge creation by passing IFLA_MTU
(as systemd-networkd and network-manager do), it does not disable
auto-tuning. Subsequently when the interface is added to the bridge,
the MTU is auto-tuned to match.
So while systemd-networkd is setting this MTU initially, it is almost
immediately changed by the auto-tuning when the member port is added.
If you reload, it notices the MTU doesn't match and changes it again.
This change then triggers the relevant code to disable auto-tuning -
so it won't change again after that.
To verify this, you can examine the state of BROPT_MTU_SET_BY_USER
with this drgn
script:
https://gist.github.com/lathiat/7a3cace35bd28413822c362f76ad2f1a
You can also capture the MTU being set at creation with this bpftrace
script:
https://gist.github.com/lathiat/1624723ceef8d17239ae450f03c8eb3b
It can also be helpful to set the following in a drop-in override using
"systemctl edit systemd-networkd":
[Service]
Environment=SYSTEMD_LOG_LEVEL=debug
== Use Case ==
The specific use case that found this bug was wanting to have a VLAN
with MTU 9000 and the default untagged VLAN interface with MTU 1500.
For a VLAN sub-interface (e.g. eth0.42) to have MTU 9000 the parent
interface (eth0) must also have MTU 9000. Even if that's not what you
actually wanted.
One way to work around this is to create eth0 and eth0.42 with MTU
9000 but then create br0 with MTU 1500 containing eth0. Because we are
intentionally setting the MTU of br0 to a value other than the member
interfaces the bug is triggered.
However this also happens in other cases and this bug has often not been
noticed because either
(a) If the same MTU is desired on the bridge and member ports, setting
the MTU of the member ports to match result in auto-tuning still
happening but to the desired value.
(b) When member ports are created by other tools (e.g. virtualisation
software such as LXD) they often (but not always) clone the MTU of the
bridge to the interface before adding it, specifically to avoid this
behaviour. However not all software clones the bridge MTU before
adding an interface (so the bridge MTU will get reduced to 1500 when a
higher value is desired).
(c) ifupdown specifically sets MTU after creation (using ip link X set
mtu N), so does not experience this bug, unlike networkd/Network
Manager which set MTU during creation with IFLA_MTU.
== Test Case ==
# Notes:
# - This requires a multi-core VM to reproduce reliably. Single core VMs
frequently fail to reproduce it.
# - Requires a spare interface separate to the primary interface, in the
exampel we use eth2.
# - You can take the netplan generated configs from /run/systemd/network and
use them directly in /etc/systemd/network and apply with "networkctl reload".
You get the same results.
# 1. Create simple netplan configuration
# Ensure that no eth2 configuration exists in the other files, if so, remove
that.
grep eth2 /etc/netplan/ -Ri
cat >> /etc/netplan/60-br0.yaml
[Kernel-packages] [Bug 2037513] [NEW] HP ProBook 450 G8 Notebook fail to wifi test
Public bug reported: I'm reviewing the SRU test result on this machine. I found that this machine always fails to wifi test and also pop out a lot of error message in dmesg. It's not a regression, since according to previous test run it has failed already. Just because we missed reviewing it for a while. The journal log is attach, please check further hardware informations at https://certification.canonical.com/hardware/202106-29176/ ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.15.0-86-generic 5.15.0-86.96~20.04.1 ProcVersionSignature: Ubuntu 5.15.0-86.96~20.04.1-generic 5.15.122 Uname: Linux 5.15.0-86-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Sep 27 15:47:37 2023 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-focal-amd64-20220621-7+pc-stella-cmit-focal-amd64+X00 InstallationDate: Installed on 2023-09-25 (2 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20220621-04:14 SourcePackage: linux-signed-hwe-5.15 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.15 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cert-sru focal package-from-proposed uec-images ** Attachment added: "journal.log" https://bugs.launchpad.net/bugs/2037513/+attachment/5704864/+files/journal.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2037513 Title: HP ProBook 450 G8 Notebook fail to wifi test Status in linux-signed-hwe-5.15 package in Ubuntu: New Bug description: I'm reviewing the SRU test result on this machine. I found that this machine always fails to wifi test and also pop out a lot of error message in dmesg. It's not a regression, since according to previous test run it has failed already. Just because we missed reviewing it for a while. The journal log is attach, please check further hardware informations at https://certification.canonical.com/hardware/202106-29176/ ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.15.0-86-generic 5.15.0-86.96~20.04.1 ProcVersionSignature: Ubuntu 5.15.0-86.96~20.04.1-generic 5.15.122 Uname: Linux 5.15.0-86-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Sep 27 15:47:37 2023 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-focal-amd64-20220621-7+pc-stella-cmit-focal-amd64+X00 InstallationDate: Installed on 2023-09-25 (2 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20220621-04:14 SourcePackage: linux-signed-hwe-5.15 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.15/+bug/2037513/+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 2036377] Re: Fix RCU warning on AMD laptops
** Changed in: linux-oem-6.5 (Ubuntu Jammy) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2036377 Title: Fix RCU warning on AMD laptops Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: Confirmed Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux source package in Lunar: Fix Committed Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux-oem-6.5 source package in Lunar: Invalid Status in linux source package in Mantic: Confirmed Status in linux-oem-6.1 source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [Impact] Scary kernel splat about RCU can be observed everytime laptop resumes from suspend. [Fix] Use non-atomic notifier for power supply change to relax the constraint. [Test] Once the fix is applied, no more RCU warning can be found after several suspend/resume cycle. [Where problems could occur] Essentially no regression potential. Atomic notifier should be used by core kernel, and things like power supply doesn't need to be atomic anyway. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2036377/+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 2037273] Re: Realtek 8852CE WiFi 6E country code udpates
** Changed in: linux-oem-6.5 (Ubuntu Jammy)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2037273
Title:
Realtek 8852CE WiFi 6E country code udpates
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:
Invalid
Status in linux-oem-6.5 source package in Jammy:
Fix Committed
Status in linux source package in Mantic:
In Progress
Status in linux-oem-6.5 source package in Mantic:
Invalid
Bug description:
[SRU Justification]
[Impact]
Missing WiFi 6G band for interested countries.
[Fix]
Upstream v6.6-rc1 commit f585f4ab0b99 ("wifi: rtw89: regd: update
regulatory map to R64-R43").
[Test Case]
Use `iw list` to check if 6G bands are then enabled.
[Where problems could occur]
This enables corresponding 6G bands for rtw89 driven devices. There
should be no other side effects.
[Other Info]
Nominated for oem-6.5 and mantic. Since this is in v6.6-rc1, Unstable
is skipped.
= original bug report ==
Proposed fix:
https://patchwork.kernel.org/project/linux-wireless/patch/20230815120253.9901-1-pks...@realtek.com/
Accepted in wireless-next as commit f585f4ab0b99 ("wifi: rtw89: regd: update
regulatory map to R64-R43") and is in v6.6-rc1 now.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2037273/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037390] Re: Missing firmware for Intel CNVi AX211 on Intel Meteor Lake platform
Upstream pull request: https://lore.kernel.org/linux- firmware/edb251a86c9cc6c3fcdfa9b4304d9a7ae9c074dc.ca...@intel.com/T/#u -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2037390 Title: Missing firmware for Intel CNVi AX211 on Intel Meteor Lake platform Status in HWE Next: New Status in linux-firmware package in Ubuntu: Triaged Status in linux-firmware source package in Jammy: Triaged Status in linux-firmware source package in Mantic: Triaged Bug description: WIFI FW: Line 1092: [ 7.971227] iwlwifi :00:14.3: PCI dev 7e40/4090, rev=0x441, rfid=0x2010d000 Line 1118: [ 7.971719] iwlwifi :00:14.3: no suitable firmware found! Line 1119: [ 7.971720] iwlwifi :00:14.3: minimum version required: iwlwifi-ma-b0-gf-a0-59 Line 1120: [ 7.971721] iwlwifi :00:14.3: maximum version supported: iwlwifi-ma-b0-gf-a0-83 Line 1121: [ 7.971721] iwlwifi :00:14.3: check git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git Bluetooth FW: Line 1123: [ 7.974156] Bluetooth: hci0: Failed to load Intel firmware file intel/ibt-0180-0041.sfi (-2) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: pass Dependencies: firmware-sof-signed 2.0-1ubuntu4.2+exp.7 [origin: LP-PPA-canonical-hwe-team-linux-firmware-staging] DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-jiayi-jammy-amd64-20230706-44 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-07-06 (82 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - pc-jiayi-jammy-amd64-20230706-44 MachineType: Intel Corporation Meteor Lake Client Platform Package: linux-firmware 20220329.git681281e4-0ubuntu3.19+exp.83 [origin: LP-PPA-canonical-hwe-team-linux-firmware-staging] PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9004-oem root=UUID=3019b32e-e421-4827-87dd-877e9cff7126 ro i915.force_probe=7d55 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.5.0-9004.4+exp.11-oem 6.5.3 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.5.0-9004-oem N/A linux-backports-modules-6.5.0-9004-oem N/A linux-firmware 20220329.git681281e4-0ubuntu3.19+exp.83 Tags: third-party-packages jammy Uname: Linux 6.5.0-9004-oem x86_64 UnreportableReason: This does not seem to be an official Ubuntu package. Please retry after updating the indexes of available packages, if that does not work then remove related third party packages and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 03/21/2023 dmi.bios.vendor: Intel Corporation dmi.bios.version: MTLPFWI1.R00.3084.D89.2303211034 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: MTL-P DDR5 SODIMM SBS RVP dmi.board.vendor: Intel Corporation dmi.board.version: 1 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.71 dmi.modalias: dmi:bvnIntelCorporation:bvrMTLPFWI1.R00.3084.D89.2303211034:bd03/21/2023:efr1.71:svnIntelCorporation:pnMeteorLakeClientPlatform:pvr0.1:rvnIntelCorporation:rnMTL-PDDR5SODIMMSBSRVP:rvr1:cvnIntelCorporation:ct9:cvr0.1:sku010010020001: dmi.product.family: Meteor Lake Client System dmi.product.name: Meteor Lake Client Platform dmi.product.sku: 010010020001 dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2037390/+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 2034099] Re: Bridge MTU not applied at first boot, only after netplan apply/networkctl reload
** Changed in: linux (Ubuntu)
Status: Confirmed => In Progress
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2034099
Title:
Bridge MTU not applied at first boot, only after netplan
apply/networkctl reload
Status in linux package in Ubuntu:
In Progress
Bug description:
If you set a Bridge's MTU to a specific value using netplan/networkd
which is different to the MTU of the interface you add, it does not
appear to be applied correctly during boot.
However the MTU switches to the correct value when you re-apply the
configuration with "netplan apply" (or "systemctl restart systemd-
networkd"; "networkctl reload")
Additionally:
- It does apply correctly when you create the bridge for the first time
(after boot), I did not debug why.
- When deploying the same configuration with Juju & MAAS it works after first
boot (likely because juju modifies the netplan config and runs netplan apply)
but still fails on reboot.
== Cause ==
Linux bridges, by default, "auto-tune" the bridge MTU to MIN(mtu) of
all member ports. This is updated each time an interface is added or
removed (except with vlan aware mode, which uses MAX(mtu) instead).
If the user changes the MTU of the bridge explicitly, it disables this
behaviour since 804b854d374e ("net: bridge: disable bridge MTU auto
tuning if it was set manually") which landed in v4.17.
This is the expected behaviour, unfortunately that code has a bug in
that it only works if the bridge MTU is changed after it was created.
If the bridge MTU is set during bridge creation by passing IFLA_MTU
(as systemd-networkd and network-manager do), it does not disable
auto-tuning. Subsequently when the interface is added to the bridge,
the MTU is auto-tuned to match.
So while systemd-networkd is setting this MTU initially, it is almost
immediately changed by the auto-tuning when the member port is added.
If you reload, it notices the MTU doesn't match and changes it again.
This change then triggers the relevant code to disable auto-tuning -
so it won't change again after that.
To verify this, you can examine the state of BROPT_MTU_SET_BY_USER
with this drgn
script:
https://gist.github.com/lathiat/7a3cace35bd28413822c362f76ad2f1a
You can also capture the MTU being set at creation with this bpftrace
script:
https://gist.github.com/lathiat/1624723ceef8d17239ae450f03c8eb3b
It can also be helpful to set the following in a drop-in override using
"systemctl edit systemd-networkd":
[Service]
Environment=SYSTEMD_LOG_LEVEL=debug
== Use Case ==
The specific use case that found this bug was wanting to have a VLAN
with MTU 9000 and the default untagged VLAN interface with MTU 1500.
For a VLAN sub-interface (e.g. eth0.42) to have MTU 9000 the parent
interface (eth0) must also have MTU 9000. Even if that's not what you
actually wanted.
One way to work around this is to create eth0 and eth0.42 with MTU
9000 but then create br0 with MTU 1500 containing eth0. Because we are
intentionally setting the MTU of br0 to a value other than the member
interfaces the bug is triggered.
However this also happens in other cases and this bug has often not been
noticed because either
(a) If the same MTU is desired on the bridge and member ports, setting
the MTU of the member ports to match result in auto-tuning still
happening but to the desired value.
(b) When member ports are created by other tools (e.g. virtualisation
software such as LXD) they often (but not always) clone the MTU of the
bridge to the interface before adding it, specifically to avoid this
behaviour. However not all software clones the bridge MTU before
adding an interface (so the bridge MTU will get reduced to 1500 when a
higher value is desired).
(c) ifupdown specifically sets MTU after creation (using ip link X set
mtu N), so does not experience this bug, unlike networkd/Network
Manager which set MTU during creation with IFLA_MTU.
== Test Case ==
# Notes:
# - This requires a multi-core VM to reproduce reliably. Single core VMs
frequently fail to reproduce it.
# - Requires a spare interface separate to the primary interface, in the
exampel we use eth2.
# - You can take the netplan generated configs from /run/systemd/network and
use them directly in /etc/systemd/network and apply with "networkctl reload".
You get the same results.
# 1. Create simple netplan configuration
# Ensure that no eth2 configuration exists in the other files, if so, remove
that.
grep eth2 /etc/netplan/ -Ri
cat >> /etc/netplan/60-br0.yaml
[Kernel-packages] [Bug 2037513] Re: HP ProBook 450 G8 Notebook fail to wifi test
** Changed in: linux-signed-hwe-5.15 (Ubuntu) Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2037513 Title: HP ProBook 450 G8 Notebook fail to wifi test Status in linux-signed-hwe-5.15 package in Ubuntu: New Bug description: I'm reviewing the SRU test result on this machine. I found that this machine always fails to wifi test and also pop out a lot of error message in dmesg. It's not a regression, since according to previous test run it has failed already. Just because we missed reviewing it for a while. The journal log is attach, please check further hardware informations at https://certification.canonical.com/hardware/202106-29176/ ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.15.0-86-generic 5.15.0-86.96~20.04.1 ProcVersionSignature: Ubuntu 5.15.0-86.96~20.04.1-generic 5.15.122 Uname: Linux 5.15.0-86-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Sep 27 15:47:37 2023 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-focal-amd64-20220621-7+pc-stella-cmit-focal-amd64+X00 InstallationDate: Installed on 2023-09-25 (2 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20220621-04:14 SourcePackage: linux-signed-hwe-5.15 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.15/+bug/2037513/+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 2024187] Re: xfrm: packets sent trough a raw socket don't match ipsec policies with proto selector
For the record, the patch has been backported in Lunar/Jammy/Focal:
https://lists.ubuntu.com/archives/kernel-team/2023-August/141562.html
--
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/2024187
Title:
xfrm: packets sent trough a raw socket don't match ipsec policies with
proto selector
Status in linux package in Ubuntu:
Expired
Bug description:
[Impact]
When a userland application sends packets through an IPv4 or IPv6 raw
socket, these packets don't match ipsec policies that are configured
with a protocol selector.
The problem has been fixed in linux v6.4 with commit 3632679d9e4f
("ipv{4,6}/raw: fix output xfrm lookup wrt protocol").
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=3632679d9e4f
This commit has been backported in linux 5.15.115:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=395d846c61c5
[Test Case]
Configure an ipsec policy with a protocol selector and send ip packets
that match this policy through an IP raw socket.
Example to match the proto icmp:
ip xfrm policy add src 10.100.0.0/24 dst 10.200.0.0/24 proto icmp dir out
tmpl src 10.125.0.1 dst 10.125.0.2 proto esp mode tunnel reqid 1
[Regression Potential]
The patch introduces a new API to fix this problem, thus the
regression potential is low for existing applications.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2024187/+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 2002226] Re: Add support for kernels compiled with CONFIG_EFI_ZBOOT
** Changed in: grub2-unsigned (Ubuntu Jammy)
Assignee: (unassigned) => Mate Kukri (mkukri)
** Changed in: grub2-unsigned (Ubuntu Lunar)
Assignee: (unassigned) => Mate Kukri (mkukri)
--
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/2002226
Title:
Add support for kernels compiled with CONFIG_EFI_ZBOOT
Status in grub2 package in Ubuntu:
Fix Released
Status in grub2-unsigned package in Ubuntu:
Fix Released
Status in linux package in Ubuntu:
Triaged
Status in grub2 source package in Focal:
New
Status in grub2-unsigned source package in Focal:
New
Status in linux source package in Focal:
New
Status in grub2 source package in Jammy:
New
Status in grub2-unsigned source package in Jammy:
New
Status in linux source package in Jammy:
New
Status in grub2 source package in Lunar:
New
Status in grub2-unsigned source package in Lunar:
New
Status in linux source package in Lunar:
New
Bug description:
[Impact]
Arm64 kernels compiled with CONFIG_EFI_ZBOOT=y don't use the
ARM64_IMAGE_MAGIC ('ARM\x64') but LINUX_PE_MAGIC (0x818223cd) in the PE Header.
Our GRUB fails to boot such a kernel.
We should eliminate the following check:
grub-core/loader/efi/linux.c:75:
if (lh->magic != GRUB_LINUX_ARCH_MAGIC_SIGNATURE)
return grub_error(GRUB_ERR_BAD_OS, "invalid magic number");
This will allow any EFI binary to be run using the linux command.
[Test plan]
* check that grub and EFI based ARM64 machines boot
* check that MAAS deployment works
[Where problems could occur]
* Non-EFI bootloaders want to boot with regular vmlinuz.gz. If one is using
piboot, u-boot, abootimg likely one still wants to build Image.gz and have
CONFIG_EFI_ZBOOT disabled.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2002226/+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 1981658] Re: BUG: kernel NULL pointer dereference, address: 0000000000000008
I have seen the same issue, in my case on a desktop machine when my machine goes to sleep with a dock attached, or, with the dock attached, when I run `xset dpms force off` lsb_release -a Distributor ID: Ubuntu Description:Ubuntu 23.04 Release:23.04 Codename: lunar uname -a Linux hostname 6.2.0-33-generic #33-Ubuntu SMP PREEMPT_DYNAMIC Tue Sep 5 14:49:19 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ** Attachment added: "journalctl -k" https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.2/+bug/1981658/+attachment/5704875/+files/dmesg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1981658 Title: BUG: kernel NULL pointer dereference, address: 0008 Status in linux package in Ubuntu: Confirmed Status in linux-hwe-5.4 package in Ubuntu: Confirmed Status in linux-hwe-6.2 package in Ubuntu: New Status in linux source package in Bionic: Fix Released Status in linux-hwe-5.4 source package in Bionic: Confirmed Status in linux-hwe-6.2 source package in Bionic: New Bug description: Hi, On one of the main US Ubuntu Archive servers (banjo), we decided to reboot into a HWE kernel. The latest being 5.4.0-122 but on doing so, ran into this kernel panic: | [ 350.776585] BUG: kernel NULL pointer dereference, address: 0008 | [ 350.783674] #PF: supervisor read access in kernel mode | [ 350.788846] #PF: error_code(0x) - not-present page | [ 350.794019] PGD 0 P4D 0 | [ 350.796631] Oops: [#1] SMP NOPTI | [ 350.800425] CPU: 8 PID: 0 Comm: swapper/8 Not tainted 5.4.0-122-generic #138~18.04.1-Ubuntu | [ 350.808918] Hardware name: HPE ProLiant DL385 Gen10/ProLiant DL385 Gen10, BIOS A40 02/10/2022 | [ 350.817666] RIP: 0010:tcp_create_openreq_child+0x2e1/0x3e0 | [ 350.823187] Code: 08 00 00 41 8b 84 24 18 01 00 00 48 c7 83 80 08 00 00 00 00 00 00 4c 89 e6 4c 89 ef 89 83 c4 05 00 00 49 8b 84 24 f8 00 00 00 <48> 8b 40 08 e8 96 28 42 00 48 85 c0 0f b7 83 68 05 00 00 74 0a 83 | [ 350.842068] RSP: 0018:9a958cce8858 EFLAGS: 00010246 | [ 350.847324] RAX: RBX: 897618739c80 RCX: 0007 | [ 350.854502] RDX: 0020 RSI: 897607afb0b0 RDI: 897605c85580 | [ 350.861682] RBP: 9a958cce8878 R08: 0178 R09: 89763e407800 | [ 350.868859] R10: 04c4 R11: 9a958cce89c7 R12: 897607afb0b0 | [ 350.876039] R13: 897605c85580 R14: 8976205fbe00 R15: 89762688b400 | [ 350.883219] FS: () GS:89763ec0() knlGS: | [ 350.891358] CS: 0010 DS: ES: CR0: 80050033 | [ 350.897138] CR2: 0008 CR3: 001fd7914000 CR4: 00340ee0 | [ 350.904319] Call Trace: | [ 350.906787] | [ 350.908824] tcp_v6_syn_recv_sock+0x8d/0x710 | [ 350.913259] ? ip6_route_output_flags_noref+0xd0/0x110 | [ 350.918435] tcp_get_cookie_sock+0x48/0x140 | [ 350.922688] cookie_v6_check+0x5a2/0x700 | [ 350.926714] tcp_v6_do_rcv+0x36c/0x3e0 | [ 350.930589] ? tcp_v6_do_rcv+0x36c/0x3e0 | [ 350.934589] tcp_v6_rcv+0xa16/0xa60 | [ 350.938102] ip6_protocol_deliver_rcu+0xd8/0x4d0 | [ 350.942750] ip6_input+0x41/0xb0 | [ 350.946000] ip6_sublist_rcv_finish+0x42/0x60 | [ 350.950385] ip6_sublist_rcv+0x235/0x260 | [ 350.954333] ? __netif_receive_skb_core+0x19d/0xc60 | [ 350.959245] ipv6_list_rcv+0x110/0x140 | [ 350.963018] __netif_receive_skb_list_core+0x157/0x260 | [ 350.968192] ? build_skb+0x17/0x80 | [ 350.971615] netif_receive_skb_list_internal+0x187/0x2a0 | [ 350.976961] gro_normal_list.part.131+0x1e/0x40 | [ 350.981519] napi_complete_done+0x94/0x120 | [ 350.985700] mlx5e_napi_poll+0x178/0x630 [mlx5_core] | [ 350.990697] net_rx_action+0x140/0x3e0 | [ 350.994475] __do_softirq+0xe4/0x2da | [ 350.998079] irq_exit+0xae/0xb0 | [ 351.001239] do_IRQ+0x59/0xe0 | [ 351.004228] common_interrupt+0xf/0xf | [ 351.007913] | [ 351.010029] RIP: 0010:cpuidle_enter_state+0xbc/0x440 | [ 351.015023] Code: ff e8 b8 ca 80 ff 80 7d d3 00 74 17 9c 58 0f 1f 44 00 00 f6 c4 02 0f 85 54 03 00 00 31 ff e8 4b 4f 87 ff fb 66 0f 1f 44 00 00 <45> 85 ed 0f 88 1a 03 00 00 4c 2b 7d c8 48 ba cf f7 53 e3 a5 9b c4 | [ 351.033952] RSP: 0018:9a958026fe48 EFLAGS: 0246 ORIG_RAX: ffd6 | [ 351.041633] RAX: 89763ec2fe00 RBX: 84b66b40 RCX: 001f | [ 351.048816] RDX: 0051abe96150 RSI: 2abf3234 RDI: | [ 351.055997] RBP: 9a958026fe88 R08: 0002 R09: 0002f680 | [ 351.063176] R10: 9a958026fe18 R11: 0115 R12: 8976274c3800 | [ 351.070355] R13: 0001 R14: 84b66bb8 R15: 0051abe96150 | [ 351.077540] ? cpuidle_enter_state+0x98/0x440 | [ 351.081930] ?
[Kernel-packages] [Bug 2036287] Re: 6.2.0-32 kernel doesn't work with Asus Vivobook
Hello, I have encountered a similar issue with a Lenovo Thinkpad P15s after upgrading to Kernel is 6.2.0-26. I encounter a black screen after logging in. What is strange is that entering and leaving the recovery mode allows to correctly boot after login. I have been able to roll back to Kernel 5.15 which does not have this issue. -- 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: Confirmed 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 2037493] Re: Fix ADL: System enabled AHCI can't get into s0ix when attached ODD
** Changed in: linux-oem-6.5 (Ubuntu Jammy) Status: In Progress => Fix Committed ** Changed in: linux-oem-6.5 (Ubuntu Lunar) Status: New => Invalid ** Changed in: linux-oem-6.5 (Ubuntu Mantic) Status: New => Invalid ** Changed in: linux (Ubuntu Jammy) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2037493 Title: Fix ADL: System enabled AHCI can't get into s0ix when attached ODD 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: Invalid Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux source package in Lunar: In Progress Status in linux-oem-6.5 source package in Lunar: Invalid Status in linux source package in Mantic: In Progress Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [Impact] System can't enter suspend on AHCI mode, the CPU FAN and System FAN is running, PSU LED is on. When fail to enter suspend, remove ODD, the system can successfully enter suspend again. [Fix] Enable LPM on Alder Lake-P AHCI. [Test Cases] 1. enabled AHCI on target machine. 2. boot with kernel applied fix. 3. suspend then check slp_s0_residency_usec&package_cstate_show ~~~ u@ubuntu:~$ sudo cat /sys/kernel/debug/pmc_core/slp_s0_residency_usec;sudo cat /sys/kernel/debug/pmc_core/package_cstate_show 4951200 Package C2 : 63571033 Package C3 : 6212 Package C6 : 5633477 Package C7 : 0 Package C8 : 0 Package C9 : 0 Package C10 : 5255561 u@ubuntu:~$ sudo rtcwake -m mem -s 10 rtcwake: assuming RTC uses UTC ... rtcwake: wakeup from "mem" using /dev/rtc0 u@ubuntu:~$ sudo cat /sys/kernel/debug/pmc_core/slp_s0_residency_usec;sudo cat /sys/kernel/debug/pmc_core/package_cstate_show 12965280 Package C2 : 75052691 Package C3 : 46989 Package C6 : 8108332 Package C7 : 0 Package C8 : 0 Package C9 : 0 Package C10 : 13628111 ~~~ [where the issue could happen] Medium, Intel promise there's no issue of ADL AHCI and they will take responsibility after regression. Intel also take LPM as POR so they will fix any issues. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2037493/+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 2036377] Re: Fix RCU warning on AMD laptops
** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2036377 Title: Fix RCU warning on AMD laptops Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux source package in Lunar: Fix Committed Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux-oem-6.5 source package in Lunar: Invalid Status in linux source package in Mantic: Confirmed Status in linux-oem-6.1 source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [Impact] Scary kernel splat about RCU can be observed everytime laptop resumes from suspend. [Fix] Use non-atomic notifier for power supply change to relax the constraint. [Test] Once the fix is applied, no more RCU warning can be found after several suspend/resume cycle. [Where problems could occur] Essentially no regression potential. Atomic notifier should be used by core kernel, and things like power supply doesn't need to be atomic anyway. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2036377/+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 2037493] Re: Fix ADL: System enabled AHCI can't get into s0ix when attached ODD
** Also affects: linux-oem-6.1 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-6.1 (Ubuntu Lunar) Status: New => Invalid ** Changed in: linux-oem-6.1 (Ubuntu Mantic) Status: New => Invalid ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2037493 Title: Fix ADL: System enabled AHCI can't get into s0ix when attached ODD Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux source package in Lunar: In Progress Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux-oem-6.5 source package in Lunar: Invalid Status in linux source package in Mantic: In Progress Status in linux-oem-6.1 source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [Impact] System can't enter suspend on AHCI mode, the CPU FAN and System FAN is running, PSU LED is on. When fail to enter suspend, remove ODD, the system can successfully enter suspend again. [Fix] Enable LPM on Alder Lake-P AHCI. [Test Cases] 1. enabled AHCI on target machine. 2. boot with kernel applied fix. 3. suspend then check slp_s0_residency_usec&package_cstate_show ~~~ u@ubuntu:~$ sudo cat /sys/kernel/debug/pmc_core/slp_s0_residency_usec;sudo cat /sys/kernel/debug/pmc_core/package_cstate_show 4951200 Package C2 : 63571033 Package C3 : 6212 Package C6 : 5633477 Package C7 : 0 Package C8 : 0 Package C9 : 0 Package C10 : 5255561 u@ubuntu:~$ sudo rtcwake -m mem -s 10 rtcwake: assuming RTC uses UTC ... rtcwake: wakeup from "mem" using /dev/rtc0 u@ubuntu:~$ sudo cat /sys/kernel/debug/pmc_core/slp_s0_residency_usec;sudo cat /sys/kernel/debug/pmc_core/package_cstate_show 12965280 Package C2 : 75052691 Package C3 : 46989 Package C6 : 8108332 Package C7 : 0 Package C8 : 0 Package C9 : 0 Package C10 : 13628111 ~~~ [where the issue could happen] Medium, Intel promise there's no issue of ADL AHCI and they will take responsibility after regression. Intel also take LPM as POR so they will fix any issues. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2037493/+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 2037077] Re: Fix unstable audio at low levels on Thinkpad P1G4
** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2037077 Title: Fix unstable audio at low levels on Thinkpad P1G4 Status in HWE Next: In Progress Status in linux package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in linux source package in Lunar: In Progress Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: In Progress Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: [Impact] The audio at low levels is not stable with fluctuating levels. [Fix] Forcibly assign NID 0x03 to HP while NID 0x02 to SPK. [Test] Tested on hardware, the audio output is OK at all levels. [Where problems could occur] It may break audio output on Thinkpad P1G4/5. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2037077/+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 2036184] Re: Infinite systemd loop when power off the machine with multiple MD RAIDs
** Changed in: linux-oem-6.1 (Ubuntu Jammy)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.1 in Ubuntu.
https://bugs.launchpad.net/bugs/2036184
Title:
Infinite systemd loop when power off the machine with multiple MD
RAIDs
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-6.1 package in Ubuntu:
Invalid
Status in linux-oem-6.5 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Invalid
Status in linux-oem-6.1 source package in Jammy:
Fix Committed
Status in linux-oem-6.5 source package in Jammy:
Fix Committed
Status in linux source package in Mantic:
In Progress
Status in linux-oem-6.1 source package in Mantic:
Invalid
Status in linux-oem-6.5 source package in Mantic:
Invalid
Bug description:
[Impact]
The system with multiple MD RAIDs sometimes hangs while rebooting, that's
because of the systemd can't stop and close the MD disk.
[Fix]
This commit fixes the issue, and this issue has been introduced by
12a6caf27324 ("md: only delete entries from all_mddevs when the disk is freed")
after v6.0
https://patchwork.kernel.org/project/linux-
raid/patch/20230914152416.10819-1-mariusz.tkac...@linux.intel.com/
[Test case]
1. Reboot the system with multiple MD RAIDs at least 10 times.
2. Make sure the system can reboot successfully every time.
3. You should not see error messages like below.
[ 205.360738] systemd-shutdown[1]: Stopping MD devices.
[ 205.366384] systemd-shutdown[1]: sd-device-enumerator: Scan all dirs
[ 205.373327] systemd-shutdown[1]: sd-device-enumerator: Scanning /sys/bus
[ 205.380427] systemd-shutdown[1]: sd-device-enumerator: Scanning /sys/class
[ 205.388257] systemd-shutdown[1]: Stopping MD /dev/md127 (9:127).
[ 205.394880] systemd-shutdown[1]: Failed to sync MD block device /dev/md127,
ignoring: Input/output error
[ 205.404975] md: md127 stopped.
[ 205.470491] systemd-shutdown[1]: Stopping MD /dev/md126 (9:126).
[ 205.770179] md: md126: resync interrupted.
[ 205.776258] md126: detected capacity change from 1900396544 to 0
[ 205.783349] md: md126 stopped.
[ 205.862258] systemd-shutdown[1]: Stopping MD /dev/md125 (9:125).
[ 205.862435] md: md126 stopped.
[ 205.868376] systemd-shutdown[1]: Failed to sync MD block device /dev/md125,
ignoring: Input/output error
[ 205.872845] block device autoloading is deprecated and will be removed.
[ 205.880955] md: md125 stopped.
[ 205.934349] systemd-shutdown[1]: Stopping MD /dev/md124p2 (259:7).
[ 205.947707] systemd-shutdown[1]: Could not stop MD /dev/md124p2: Device or
resource busy
[ 205.957004] systemd-shutdown[1]: Stopping MD /dev/md124p1 (259:6).
[ 205.964177] systemd-shutdown[1]: Could not stop MD /dev/md124p1: Device or
resource busy
[ 205.973155] systemd-shutdown[1]: Stopping MD /dev/md124 (9:124).
[ 205.979789] systemd-shutdown[1]: Could not stop MD /dev/md124: Device or
resource busy
[ 205.988475] systemd-shutdown[1]: Not all MD devices stopped, 4 left.
[Where problems could occur]
It fixes the data race issue, should not introduce any regression.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2036184/+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 2033271] Re: Fujitsu keyboard not working after updates
The work-around provided by Johannes does work for me. sudo vi /etc/default/grub # -- GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i8042.nomux=1" # -- Parameter i8042.reset is not working for me, but does not effect the outcome. sudo update-grub -- 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/2033271 Title: Fujitsu keyboard not working after updates Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 22.04.3 LTS Fujitsu Lifebook E5410 Expected to happen is that the keyboard is working as previous before the updates. What instead happens is, that the keyboard is dead and does not work. Attaching an external USB-keyboard works. The keyboard works before boot in the BIOS context, so it is not hardware related. -- There is another user reporting the same issue for a E5510 on ask Ubuntu. https://askubuntu.com/questions/1483381/ubuntu-22-04-fujitsu- lifebook-e5510-keyboard-not-working-after-update-kernel 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: Mon Aug 28 12:01:29 2023 InstallationDate: Installed on 2022-04-21 (493 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: cysec 1698 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-04-21 (497 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: FUJITSU CLIENT COMPUTING LIMITED LIFEBOOK E5410 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-31-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-31.31~22.04.1-generic 6.2.15 RelatedPackageVersions: linux-restricted-modules-6.2.0-31-generic N/A linux-backports-modules-6.2.0-31-generic N/A linux-firmware20220329.git681281e4-0ubuntu3.18 Tags: wayland-session jammy Uname: Linux 6.2.0-31-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: 06/30/2023 dmi.bios.release: 2.30 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 2.30 dmi.board.name: FJNB2D6 dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: A2 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.chassis.version: LIFEBOOK E5410 dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion2.30:bd06/30/2023:br2.30:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnLIFEBOOKE5410:pvr10601736746:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNB2D6:rvrA2:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct10:cvrLIFEBOOKE5410:skuSK01: dmi.product.family: LIFEBOOK-FTS dmi.product.name: LIFEBOOK E5410 dmi.product.sku: SK01 dmi.product.version: 10601736746 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033271/+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 2034619] Re: [amdgpu] gnome-shell gets SIGKILL'd when lock screen in Wayland
** Description changed: + [ Workaround ] + + Add this to /etc/environment: + + MUTTER_DEBUG_KMS_THREAD_TYPE=user + + and then reboot. + + [ Original Description] + I have this issue on Ubuntu 23.10. Lock screen works only with an external monitor connected. Otherwise the session is ended and the user is logged out and brought to the gdm screen. All works in xorg. ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~beta.1-0ubuntu2 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 22:32:22 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2023-09-03 (3 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230901.1) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 45~beta.1-1ubuntu2 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users separator: -- 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/2034619 Title: [amdgpu] gnome-shell gets SIGKILL'd when lock screen in Wayland Status in Linux: New Status in Mutter: New Status in X.Org X server: Fix Released Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: In Progress Status in linux source package in Mantic: Confirmed Status in mutter source package in Mantic: In Progress Bug description: [ Workaround ] Add this to /etc/environment: MUTTER_DEBUG_KMS_THREAD_TYPE=user and then reboot. [ Original Description] I have this issue on Ubuntu 23.10. Lock screen works only with an external monitor connected. Otherwise the session is ended and the user is logged out and brought to the gdm screen. All works in xorg. ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~beta.1-0ubuntu2 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 22:32:22 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2023-09-03 (3 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230901.1) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 45~beta.1-1ubuntu2 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2034619/+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 2002226] Re: Add support for kernels compiled with CONFIG_EFI_ZBOOT
Do we use ZBOOT kernels anywhere in old releases where this is really
necessary?
Is this something we really want in older GRUBs at all?
Removing the magic number check is easy enough, but I am not sure of the
ramifications of allowing random signed EFI binaries through the linux
codepath with those old loaders.
--
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/2002226
Title:
Add support for kernels compiled with CONFIG_EFI_ZBOOT
Status in grub2 package in Ubuntu:
Fix Released
Status in grub2-unsigned package in Ubuntu:
Fix Released
Status in linux package in Ubuntu:
Triaged
Status in grub2 source package in Focal:
New
Status in grub2-unsigned source package in Focal:
New
Status in linux source package in Focal:
New
Status in grub2 source package in Jammy:
New
Status in grub2-unsigned source package in Jammy:
New
Status in linux source package in Jammy:
New
Status in grub2 source package in Lunar:
New
Status in grub2-unsigned source package in Lunar:
New
Status in linux source package in Lunar:
New
Bug description:
[Impact]
Arm64 kernels compiled with CONFIG_EFI_ZBOOT=y don't use the
ARM64_IMAGE_MAGIC ('ARM\x64') but LINUX_PE_MAGIC (0x818223cd) in the PE Header.
Our GRUB fails to boot such a kernel.
We should eliminate the following check:
grub-core/loader/efi/linux.c:75:
if (lh->magic != GRUB_LINUX_ARCH_MAGIC_SIGNATURE)
return grub_error(GRUB_ERR_BAD_OS, "invalid magic number");
This will allow any EFI binary to be run using the linux command.
[Test plan]
* check that grub and EFI based ARM64 machines boot
* check that MAAS deployment works
[Where problems could occur]
* Non-EFI bootloaders want to boot with regular vmlinuz.gz. If one is using
piboot, u-boot, abootimg likely one still wants to build Image.gz and have
CONFIG_EFI_ZBOOT disabled.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2002226/+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 2002226] Re: Add support for kernels compiled with CONFIG_EFI_ZBOOT
@mate I agree with that concern w.r.t. sending random pe binaries to
linux code path.
Separately in Mantic we are reverting zimg boot image format. Kernel
itself fails to kexec it correctly. And mantic kexec tools do not
support this image format correctly. Thus at this point grub 2.12 has
best support for this anyway. And kernel itself & kexec-tools need work.
If/when this gets re-enabled again, breaks will be used to ensure that
grub2 of better than 2.12 is desired to get this going again, likely in
24.04.
** Changed in: linux (Ubuntu)
Milestone: None => later
** Changed in: linux (Ubuntu Focal)
Status: New => Invalid
** Changed in: linux (Ubuntu Jammy)
Status: New => Invalid
** Changed in: linux (Ubuntu Lunar)
Status: New => Invalid
** Changed in: grub2-unsigned (Ubuntu Focal)
Status: New => Invalid
** Changed in: grub2-unsigned (Ubuntu Jammy)
Status: New => Invalid
** Changed in: grub2-unsigned (Ubuntu Lunar)
Status: New => Invalid
** Changed in: grub2 (Ubuntu Focal)
Status: New => Invalid
** Changed in: grub2 (Ubuntu Jammy)
Status: New => Invalid
** Changed in: grub2 (Ubuntu Lunar)
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/2002226
Title:
Add support for kernels compiled with CONFIG_EFI_ZBOOT
Status in grub2 package in Ubuntu:
Fix Released
Status in grub2-unsigned package in Ubuntu:
Fix Released
Status in linux package in Ubuntu:
Triaged
Status in grub2 source package in Focal:
Invalid
Status in grub2-unsigned source package in Focal:
Invalid
Status in linux source package in Focal:
Invalid
Status in grub2 source package in Jammy:
Invalid
Status in grub2-unsigned source package in Jammy:
Invalid
Status in linux source package in Jammy:
Invalid
Status in grub2 source package in Lunar:
Invalid
Status in grub2-unsigned source package in Lunar:
Invalid
Status in linux source package in Lunar:
Invalid
Bug description:
[Impact]
Arm64 kernels compiled with CONFIG_EFI_ZBOOT=y don't use the
ARM64_IMAGE_MAGIC ('ARM\x64') but LINUX_PE_MAGIC (0x818223cd) in the PE Header.
Our GRUB fails to boot such a kernel.
We should eliminate the following check:
grub-core/loader/efi/linux.c:75:
if (lh->magic != GRUB_LINUX_ARCH_MAGIC_SIGNATURE)
return grub_error(GRUB_ERR_BAD_OS, "invalid magic number");
This will allow any EFI binary to be run using the linux command.
[Test plan]
* check that grub and EFI based ARM64 machines boot
* check that MAAS deployment works
[Where problems could occur]
* Non-EFI bootloaders want to boot with regular vmlinuz.gz. If one is using
piboot, u-boot, abootimg likely one still wants to build Image.gz and have
CONFIG_EFI_ZBOOT disabled.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2002226/+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 2028933] Re: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.GPLD], AE_ALREADY_EXISTS (20210730/dswload2-326)
The same issue with: * Dell Precision 7530, BIOS from 07/05/2023 * Nvidia Quadro P1000 Mobile * Ubuntu 22.04.3 LTS * linux-image-5.15.0-84-generic dmesg logs many times this: --- [Wed Sep 27 12:57:06 2023] ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS01._UPC], AE_ALREADY_EXISTS (20210730/dswload2-326) [Wed Sep 27 12:57:06 2023] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20210730/psobject-220) ... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2028933 Title: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.GPLD], AE_ALREADY_EXISTS (20210730/dswload2-326) Status in linux-signed-hwe-5.15 package in Ubuntu: Confirmed Bug description: At boot up after the GRUB selection, these ACPI BIOS Error (bug) appear. These errors were taken from dmesg but they report the similar error at boot up [0.320650] ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.GPLD], AE_ALREADY_EXISTS (20210730/dswload2-326) [0.320680] fbcon: Taking over console [0.320694] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20210730/psobject-220) [0.320700] ACPI: Skipping parse of AML opcode: Method (0x0014) [0.320705] ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.TPLD], AE_ALREADY_EXISTS (20210730/dswload2-326) [0.320712] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20210730/psobject-220) [0.320717] ACPI: Skipping parse of AML opcode: Method (0x0014) [0.320720] ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.GUPC], AE_ALREADY_EXISTS (20210730/dswload2-326) [0.320727] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20210730/psobject-220) [0.320731] ACPI: Skipping parse of AML opcode: Method (0x0014) [0.320734] ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.TUPC], AE_ALREADY_EXISTS (20210730/dswload2-326) [0.320741] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20210730/psobject-220) [0.320745] ACPI: Skipping parse of AML opcode: Method (0x0014) [0.320793] ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS01._UPC], AE_ALREADY_EXISTS (20210730/dswload2-326) [0.320801] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20210730/psobject-220) [0.320806] ACPI: Skipping parse of AML opcode: Method (0x0014) Then at runtime random Multiple Corrected error appear at this PCIe port 1c.0-[01]00.0 Advanced Micro Devices, Inc. [AMD/ATI] Topaz XT [Radeon R7 M260/M265 / M340/M360 / M440/M445 / 530/535 / 620/625 Mobile]1c.0-[01]00.0 Advanced Micro Devices, Inc. [AMD/ATI] Topaz XT [Radeon R7 M260/M265 / M340/M360 / M440/M445 / 530/535 / 620/625 Mobile] Not exactly connected but similar reports of ACPI error above is related to NVIDIA. Not sure if it helps. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.15.0-78-generic 5.15.0-78.85~20.04.1 ProcVersionSignature: Ubuntu 5.15.0-78.85~20.04.1-generic 5.15.99 Uname: Linux 5.15.0-78-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 28 19:17:58 2023 InstallationDate: Installed on 2021-08-15 (712 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: linux-signed-hwe-5.15 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.15/+bug/2028933/+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 2037375] Re: package linux-image-6.2.0-33-generic (not installed) failed to install/upgrade: impossible de copier les données extraites pour « ./boot/vmlinuz-6.2.0-33-generic »
You seem to have HW problems: [ 163.321626] sd 8:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=2s [ 163.321633] sd 8:0:0:0: [sdc] tag#0 Sense Key : Hardware Error [current] [ 163.321635] sd 8:0:0:0: [sdc] tag#0 Add. Sense: Internal target failure [ 163.321638] sd 8:0:0:0: [sdc] tag#0 CDB: Read(10) 28 00 74 6a 91 f8 00 00 10 00 [ 163.321639] critical target error, dev sdc, sector 1953141240 op 0x0:(READ) flags 0x0 phys_seg 2 prio class 0 [ 163.321734] sd 8:0:0:0: [sdc] tag#1 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=2s [ 163.321736] sd 8:0:0:0: [sdc] tag#1 Sense Key : Hardware Error [current] [ 163.321737] sd 8:0:0:0: [sdc] tag#1 Add. Sense: Internal target failure [ 163.321739] sd 8:0:0:0: [sdc] tag#1 CDB: Synchronize Cache(10) 35 00 00 00 00 00 00 00 00 00 [ 163.321741] critical target error, dev sdc, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0 [ 163.321765] JBD2: recovery failed [ 163.321768] EXT4-fs (sdc2): error loading journal ** Changed in: linux-signed-hwe-6.2 (Ubuntu) Status: New => Invalid -- 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/2037375 Title: package linux-image-6.2.0-33-generic (not installed) failed to install/upgrade: impossible de copier les données extraites pour « ./boot/vmlinuz-6.2.0-33-generic » vers « /boot/vmlinuz-6.2.0-33-generic.dpkg-new » : échec d'écriture (Aucun espace disponible sur le périphérique) Status in linux-signed-hwe-6.2 package in Ubuntu: Invalid Bug description: Update manager can't reports a bug. updates are not executed ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-33-generic (not installed) ProcVersionSignature: Ubuntu 5.19.0-46.47~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-46-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue Sep 26 06:16:15 2023 ErrorMessage: impossible de copier les données extraites pour « ./boot/vmlinuz-6.2.0-33-generic » vers « /boot/vmlinuz-6.2.0-33-generic.dpkg-new » : échec d'écriture (Aucun espace disponible sur le périphérique) InstallationDate: Installed on 2023-04-25 (153 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.10 SourcePackage: linux-signed-hwe-6.2 Title: package linux-image-6.2.0-33-generic (not installed) failed to install/upgrade: impossible de copier les données extraites pour « ./boot/vmlinuz-6.2.0-33-generic » vers « /boot/vmlinuz-6.2.0-33-generic.dpkg-new » : échec d'écriture (Aucun espace disponible sur le périphérique) UpgradeStatus: Upgraded to jammy on 2023-04-25 (153 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2037375/+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 2031882] Re: Missing firmware for Intel VPU on Intel Meteor Lake platforms
** Tags added: verification-needed-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2031882 Title: Missing firmware for Intel VPU on Intel Meteor Lake platforms Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: Fix Committed Status in linux-firmware source package in Mantic: Fix Released Bug description: [SRU Justification] [Impact] Missing firmware blobs for Intel VPU support on Intel Meteor Lake platform. intel_vpu :00:0b.0: enabling device ( -> 0002) intel_vpu :00:0b.0: [drm] *ERROR* ivpu_fw_request(): Failed to request firmware: -2 intel_vpu :00:0b.0: [drm] *ERROR* ivpu_dev_init(): Failed to initialize firmware: -2 intel_vpu :00:0b.0: Failed to initialize VPU device: -2 intel_vpu: probe of :00:0b.0 failed with error -2 [Fix] Upstream Intel VPU linux driver project https://github.com/intel/linux-vpu-driver stores firmware blob in git- lfs. [Test Case] Intel VPU support on Intel Meteor Lake platform is part of the OpenVino framework. It takes many more other components to be installed before VPU on MTL may release its power. Here we simply test the firwmare can be found and loaded. [Where problems could occur] Intel VPU firmware is to be loaded by kernel but used by user land frameworks. While OpenVino is not (yet?) supported natively, this firmware blob alone has no observerible effect yet. [Other Info] While MTL is supported by v6.5 kernel or above, only oem-6.5 and Mantic are nominated by default. == original bug report == Intel Meteor Lake platform supports VPU natively and the driver has been upstreamed in v6.3. A few more steps to enable VPU support in https://github.com/intel/linux-vpu-driver, and firmware is the first one missing. [ 68.602028] intel_vpu :00:0b.0: enabling device ( -> 0002) [ 68.604010] intel_vpu :00:0b.0: [drm] *ERROR* ivpu_fw_request(): Failed to request firmware: -2 [ 68.604013] intel_vpu :00:0b.0: [drm] *ERROR* ivpu_dev_init(): Failed to initialize firmware: -2 [ 68.604263] intel_vpu :00:0b.0: Failed to initialize VPU device: -2 [ 68.604272] intel_vpu: probe of :00:0b.0 failed with error -2 The firmware blob can be retrieved by `git lfs pull` from a clone of aforementioned driver repository. The install path would be /lib/firmware/intel/vpu. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2031882/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2031412] Re: Support mipi camera on Intel Meteor Lake platform
** Tags added: verification-needed-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2031412 Title: Support mipi camera on Intel Meteor Lake platform Status in HWE Next: New Status in ipu6-drivers package in Ubuntu: New Status in ivsc-driver package in Ubuntu: New Status in linux-firmware package in Ubuntu: Fix Released Status in ipu6-drivers source package in Jammy: New Status in ivsc-driver source package in Jammy: New Status in linux-firmware source package in Jammy: Fix Committed Status in ipu6-drivers source package in Mantic: New Status in ivsc-driver source package in Mantic: New Status in linux-firmware source package in Mantic: Fix Released Bug description: [SRU Justification] [Impact] Missing Intel MIPI firmware for Meteor Lake platform. [Fix] Firmware blobs from upstream ipu6-camera-bins repository. [Test Case] With firmware loaded correctly, there should be firmware version printed: intel-ipu6 intel-ipu: FW version: 20220510 For camera functions, we'll need also updates in the ipu6-drivers, ivsc-drivers dkms as well. [Where problems could occur] This is a new platform. We've been verifying its functions and features, and are still polishing it. [Other Info] While Intel Meteor Lake is only supported by linux-oem-6.5/jammy and linux/mantic, so only Jammy/Mantic are nominated. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2031412/+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 2031882] Re: Missing firmware for Intel VPU on Intel Meteor Lake platforms
Verified on Intel MTL-P RVP. ** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2031882 Title: Missing firmware for Intel VPU on Intel Meteor Lake platforms Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: Fix Committed Status in linux-firmware source package in Mantic: Fix Released Bug description: [SRU Justification] [Impact] Missing firmware blobs for Intel VPU support on Intel Meteor Lake platform. intel_vpu :00:0b.0: enabling device ( -> 0002) intel_vpu :00:0b.0: [drm] *ERROR* ivpu_fw_request(): Failed to request firmware: -2 intel_vpu :00:0b.0: [drm] *ERROR* ivpu_dev_init(): Failed to initialize firmware: -2 intel_vpu :00:0b.0: Failed to initialize VPU device: -2 intel_vpu: probe of :00:0b.0 failed with error -2 [Fix] Upstream Intel VPU linux driver project https://github.com/intel/linux-vpu-driver stores firmware blob in git- lfs. [Test Case] Intel VPU support on Intel Meteor Lake platform is part of the OpenVino framework. It takes many more other components to be installed before VPU on MTL may release its power. Here we simply test the firwmare can be found and loaded. [Where problems could occur] Intel VPU firmware is to be loaded by kernel but used by user land frameworks. While OpenVino is not (yet?) supported natively, this firmware blob alone has no observerible effect yet. [Other Info] While MTL is supported by v6.5 kernel or above, only oem-6.5 and Mantic are nominated by default. == original bug report == Intel Meteor Lake platform supports VPU natively and the driver has been upstreamed in v6.3. A few more steps to enable VPU support in https://github.com/intel/linux-vpu-driver, and firmware is the first one missing. [ 68.602028] intel_vpu :00:0b.0: enabling device ( -> 0002) [ 68.604010] intel_vpu :00:0b.0: [drm] *ERROR* ivpu_fw_request(): Failed to request firmware: -2 [ 68.604013] intel_vpu :00:0b.0: [drm] *ERROR* ivpu_dev_init(): Failed to initialize firmware: -2 [ 68.604263] intel_vpu :00:0b.0: Failed to initialize VPU device: -2 [ 68.604272] intel_vpu: probe of :00:0b.0 failed with error -2 The firmware blob can be retrieved by `git lfs pull` from a clone of aforementioned driver repository. The install path would be /lib/firmware/intel/vpu. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2031882/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2031412] Re: Support mipi camera on Intel Meteor Lake platform
** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2031412 Title: Support mipi camera on Intel Meteor Lake platform Status in HWE Next: New Status in ipu6-drivers package in Ubuntu: New Status in ivsc-driver package in Ubuntu: New Status in linux-firmware package in Ubuntu: Fix Released Status in ipu6-drivers source package in Jammy: New Status in ivsc-driver source package in Jammy: New Status in linux-firmware source package in Jammy: Fix Committed Status in ipu6-drivers source package in Mantic: New Status in ivsc-driver source package in Mantic: New Status in linux-firmware source package in Mantic: Fix Released Bug description: [SRU Justification] [Impact] Missing Intel MIPI firmware for Meteor Lake platform. [Fix] Firmware blobs from upstream ipu6-camera-bins repository. [Test Case] With firmware loaded correctly, there should be firmware version printed: intel-ipu6 intel-ipu: FW version: 20220510 For camera functions, we'll need also updates in the ipu6-drivers, ivsc-drivers dkms as well. [Where problems could occur] This is a new platform. We've been verifying its functions and features, and are still polishing it. [Other Info] While Intel Meteor Lake is only supported by linux-oem-6.5/jammy and linux/mantic, so only Jammy/Mantic are nominated. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2031412/+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 2003675] Re: [23.10 FEAT] KVM: Implement secrets insertion in the UV Device Driver
Updating to Fix Released, since we meanwhile have kernel 6.5 in mantic as default. ** Changed in: linux (Ubuntu) Status: Fix Committed => Fix Released ** Changed in: ubuntu-z-systems Status: Fix Committed => Fix Released ** Information type changed from Private to Public -- 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/2003675 Title: [23.10 FEAT] KVM: Implement secrets insertion in the UV Device Driver Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: Feature Description: Extend the Ultravisor Device to accept IBK insertion requests. This requires an extension to the IOCTL introduced for Secure Execution Attestation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2003675/+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 2003634] Re: [23.10 FEAT] Secure Execution APQN binding and IBK association - kernel part
Updating to Fix Released, since we meanwhile have kernel 6.5 in mantic as default. ** Changed in: linux (Ubuntu) Status: Fix Committed => Fix Released ** Changed in: ubuntu-z-systems Status: Fix Committed => Fix Released ** Information type changed from Private to Public -- 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/2003634 Title: [23.10 FEAT] Secure Execution APQN binding and IBK association - kernel part Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: Feature Description: The design to support the use Crypto Express adapters in a secure guest requires - that each APQN to be used by a secure guest is bound to the secure guest - that crypto requests that contain secure key objects (in the arguments or result) must be associated with an item binding key (IBK). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2003634/+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 1982370] Re: [23.10 FEAT] DASD auto-quiesce support
Updating to Fix Released, since we meanwhile have kernel 6.5 in mantic as default. ** Changed in: linux (Ubuntu) Status: Fix Committed => Fix Released ** Changed in: ubuntu-z-systems Status: Fix Committed => Fix Released ** Information type changed from Private to Public -- 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/1982370 Title: [23.10 FEAT] DASD auto-quiesce support Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: The DASD driver should provide a way to enable auto-quiescing. Quiesce is a function that tells Linux to stop issuing I/Os to a specific DASD. Resume is the corresponding function that tells Linux to continue issuing I/Os. These are purely Linux-internal functions with no effect on the storage side, except for no new I/Os being issues. Quiesce and resume are functions that are available today in the DASD driver. Autoquiesce is a function that automatically performs the Quiesce operation on a DASD if a certain event occurs. There is no auto- resume, that is, an external entity will need to resume a DASD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1982370/+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 2037288] Re: Suppport LAN8814
** Description changed: - As indicated by the errata for the LAN8814 chip, additional backporting - is required: + [ Impact ] + + The LAN8814 isn't supported. Additional backporting is required as + explained in the errata[1]: ``` This erratum will be addressed in Linux driver micrel.c, with patch uploads in March 2022 to the net-next subsystem tree of the kernel. ``` - https://www.microchip.com/en-us/product/LAN8814 + [ Test Plan ] + + Test with hardware connected and verify that the interface comes up and + running. + + [ Where problems could occur ] + + The micrel driver support multiple chips and this backporting could + induce regression in them. It can also create problems with the whole + net subsystem. + + + + [1]: https://www.microchip.com/en-us/product/LAN8814 -- 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/2037288 Title: Suppport LAN8814 Status in linux package in Ubuntu: Incomplete Status in linux source package in Jammy: Incomplete Bug description: [ Impact ] The LAN8814 isn't supported. Additional backporting is required as explained in the errata[1]: ``` This erratum will be addressed in Linux driver micrel.c, with patch uploads in March 2022 to the net-next subsystem tree of the kernel. ``` [ Test Plan ] Test with hardware connected and verify that the interface comes up and running. [ Where problems could occur ] The micrel driver support multiple chips and this backporting could induce regression in them. It can also create problems with the whole net subsystem. [1]: https://www.microchip.com/en-us/product/LAN8814 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2037288/+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 2037560] [NEW] wireless modules not loaded after suspend?
Public bug reported:
On mantic, after a suspend my network doesn't come up automatically. I
have historically run the following to "reset" networking; not sure what
of it is necessary and what's not, but this brings it up:
$ sudo systemctl stop NetworkManager.service; sudo rmmod ath10k_pci
ath10k_core ath; sleep 3; sudo modprobe ath10k_pci ; sudo systemctl
start NetworkManager.service
rmmod does complain that none of the ath* modules are currently loaded,
so perhaps that's why the network doesn't come up automatically?
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/controlC1: jbarnett 74523 F wireplumber
/dev/snd/controlC0: jbarnett 74523 F wireplumber
/dev/snd/seq:jbarnett 74508 F pipewire
CasperMD5CheckResult: unknown
CurrentDesktop: GNOME
Date: Wed Sep 27 08:12:37 2023
InstallationDate: Installed on 2019-08-17 (1502 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-5-generic
root=UUID=83cade14-7628-437d-8517-36ad82f00d20 ro quiet splash vt.handoff=7
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: Upgraded to mantic on 2023-09-26 (1 days ago)
dmi.bios.date: 03/25/2021
dmi.bios.release: 1.15
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.15.1
dmi.board.name: 0N338G
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 31
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.15.1:bd03/25/2021:br1.15:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0N338G:rvrA00:cvnDellInc.:ct31:cvr:sku080D:
dmi.product.family: XPS
dmi.product.name: XPS 15 9575
dmi.product.sku: 080D
dmi.sys.vendor: Dell Inc.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug mantic 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/2037560
Title:
wireless modules not loaded after suspend?
Status in linux package in Ubuntu:
New
Bug description:
On mantic, after a suspend my network doesn't come up automatically.
I have historically run the following to "reset" networking; not sure
what of it is necessary and what's not, but this brings it up:
$ sudo systemctl stop NetworkManager.service; sudo rmmod ath10k_pci
ath10k_core ath; sleep 3; sudo modprobe ath10k_pci ; sudo systemctl
start NetworkManager.service
rmmod does complain that none of the ath* modules are currently
loaded, so perhaps that's why the network doesn't come up
automatically?
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/controlC1: jbarnett 74523 F wireplumber
/dev/snd/controlC0: jbarnett 74523 F wireplumber
/dev/snd/seq:jbarnett 74508 F pipewire
CasperMD5CheckResult: unknown
CurrentDesktop: GNOME
Date: Wed Sep 27 08:12:37 2023
InstallationDate: Installed on 2019-08-17 (1502 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-5-generic
root=UUID=83cade14-7628-437d-8517-36ad82f00d20 ro quiet splash vt.handoff=7
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: Upgraded to mantic on 2023-09-26 (1 days ago)
dmi.bios.date: 03/25/2021
dmi.bios.release: 1.15
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.15.1
dmi.board.name: 0N338G
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 31
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.15.1:bd03/25/2021:br1.15:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0N338G:rvrA00:cvnDellInc.:ct31:cvr:sku080D:
dmi.product.family: XPS
dmi.product.name: XPS 15 9575
dmi.product.sku: 080D
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2037560/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-
[Kernel-packages] [Bug 2037560] Status changed to Confirmed
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2037560
Title:
wireless modules not loaded after suspend?
Status in linux package in Ubuntu:
Confirmed
Bug description:
On mantic, after a suspend my network doesn't come up automatically.
I have historically run the following to "reset" networking; not sure
what of it is necessary and what's not, but this brings it up:
$ sudo systemctl stop NetworkManager.service; sudo rmmod ath10k_pci
ath10k_core ath; sleep 3; sudo modprobe ath10k_pci ; sudo systemctl
start NetworkManager.service
rmmod does complain that none of the ath* modules are currently
loaded, so perhaps that's why the network doesn't come up
automatically?
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/controlC1: jbarnett 74523 F wireplumber
/dev/snd/controlC0: jbarnett 74523 F wireplumber
/dev/snd/seq:jbarnett 74508 F pipewire
CasperMD5CheckResult: unknown
CurrentDesktop: GNOME
Date: Wed Sep 27 08:12:37 2023
InstallationDate: Installed on 2019-08-17 (1502 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-5-generic
root=UUID=83cade14-7628-437d-8517-36ad82f00d20 ro quiet splash vt.handoff=7
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: Upgraded to mantic on 2023-09-26 (1 days ago)
dmi.bios.date: 03/25/2021
dmi.bios.release: 1.15
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.15.1
dmi.board.name: 0N338G
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 31
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.15.1:bd03/25/2021:br1.15:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0N338G:rvrA00:cvnDellInc.:ct31:cvr:sku080D:
dmi.product.family: XPS
dmi.product.name: XPS 15 9575
dmi.product.sku: 080D
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2037560/+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 2026652] Re: Suspend Broken
I switched back to the NVIDIA drivers. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-lowlatency in Ubuntu. https://bugs.launchpad.net/bugs/2026652 Title: Suspend Broken Status in linux-signed-lowlatency package in Ubuntu: New Bug description: When I go to suspend my system via the UI "Suspend" option, the system fails to suspend. Instead it looks like its going to suspend, and then wakes up but with a locked screen. When I use `pm-suspend` from the command line, it suspends the system, but does not lock the screen. I have the Settings -> Privacy -> Screen Lock -> "Lock Screen on Suspend" setting enabled. I am using the Nouveau driver, with Wayland, using GNOME 44.2. This bug only started when I switched away from using any of the NVIDIA drivers, so its probably partially Nouveau related. Switching back to the NVIDIA drivers (I tried them all) isn't an option, because they break: 1. External monitor connectivity 2. VMWare Horizon Debug info: 1. `lsb_release -rd` Description: Ubuntu 23.04 Release: 23.04 2. `uname -srm` Linux 6.2.0-1007-lowlatency x86_64 Please let me know of any other information needed to debug this. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-1007-lowlatency 6.2.0-1007.7 ProcVersionSignature: Ubuntu 6.2.0-1007.7-lowlatency 6.2.12 Uname: Linux 6.2.0-1007-lowlatency x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Jul 9 10:26:06 2023 InstallationDate: Installed on 2021-12-18 (567 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: linux-signed-lowlatency UpgradeStatus: Upgraded to lunar on 2023-04-26 (73 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-lowlatency/+bug/2026652/+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 2035128] Re: mlxbf-gige: Enable the OOB port in mlxbf_gige_open
This bug is awaiting verification that the linux-bluefield/5.4.0-1072.78 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-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. 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: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2035128 Title: mlxbf-gige: Enable the OOB port in mlxbf_gige_open Status in linux-bluefield package in Ubuntu: New Status in linux-bluefield source package in Focal: Fix Committed Status in linux-bluefield source package in Jammy: Fix Committed Bug description: SRU Justification: [Impact] At the moment, the OOB port is enabled in the mlxbf_gige_probe function. If the mlxbf_gige_open is not executed, this could cause pause frames to increase in the case where there is high backgroud traffic. This results in clogging the BMC port as well. [Fix] * Move enabling the OOB port to mlxbf_gige_open. [Test Case] * Main test for this bug: Check that the BMC is always pingable while pushing a BFB Other tests: * Check if the gige driver is loaded * Check that the oob_net0 interface is up and operational * Do the reboot test and powercycle test and check the oob_net0 interface again * Push BFB multiple times and make sure the OOB is up and running [Regression Potential] Since are moving code that hasn't moved since BF2, it is important to make sure that there is no regression. Make sure that the OOB interface is always up and pingable after the reboot test, the powercycle test and after pushing a BFB. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2035128/+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 2036747] Re: pi-kernel snap is missing modules for microk8s/microceph on UC22
This bug was fixed in the package linux-raspi - 6.5.0-1003.4
---
linux-raspi (6.5.0-1003.4) mantic; urgency=medium
* mantic/linux-raspi: 6.5.0-1003.4 -proposed tracker (LP: #2036576)
* Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions (main/d2023.09.14)
* pi-kernel snap is missing modules for microk8s/microceph on UC22
(LP: #2036747)
- [Packaging] raspi: Include rbd and vxlan modules in linux-modules
* Move nbd module into modules (from -extra) (LP: #2035373)
- [Packaging] raspi: Include nbd module in linux-modules
* pi-kernel 5.15 on UC22 is missing most staging modules (LP: #2024443)
- [Packaging] raspi: Include r8188eu module in linux-modules
* Miscellaneous Ubuntu changes
- SAUCE wifi: brcmfmac: Replace 1-element arrays with flexible arrays
- [Config] raspi: Sync configs with master
- [Packaging] raspi: Add a temporary config check
- SAUCE: usb: dwc_otg: Fix flexible array declarations
* Miscellaneous upstream changes
- gpio-fsm: Sort functions into a more logical order
- gpio_fsm: Rework the atomic-vs-non-atomic split
- ASoC: hdmi-codec: Fix broken channel map reporting
[ Ubuntu: 6.5.0-6.6 ]
* mantic/linux: 6.5.0-6.6 -proposed tracker (LP: #2035595)
* Mantic update: v6.5.3 upstream stable release (LP: #2035588)
- drm/amd/display: ensure async flips are only accepted for fast updates
- cpufreq: intel_pstate: set stale CPU frequency to minimum
- tpm: Enable hwrng only for Pluton on AMD CPUs
- Input: i8042 - add quirk for TUXEDO Gemini 17 Gen1/Clevo PD70PN
- Revert "fuse: in fuse_flush only wait if someone wants the return code"
- Revert "f2fs: clean up w/ sbi->log_sectors_per_block"
- Revert "PCI: tegra194: Enable support for 256 Byte payload"
- Revert "net: macsec: preserve ingress frame ordering"
- reiserfs: Check the return value from __getblk()
- splice: always fsnotify_access(in), fsnotify_modify(out) on success
- splice: fsnotify_access(fd)/fsnotify_modify(fd) in vmsplice
- splice: fsnotify_access(in), fsnotify_modify(out) on success in tee
- eventfd: prevent underflow for eventfd semaphores
- fs: Fix error checking for d_hash_and_lookup()
- iomap: Remove large folio handling in iomap_invalidate_folio()
- tmpfs: verify {g,u}id mount options correctly
- selftests/harness: Actually report SKIP for signal tests
- vfs, security: Fix automount superblock LSM init problem, preventing NFS
sb
sharing
- ARM: ptrace: Restore syscall restart tracing
- ARM: ptrace: Restore syscall skipping for tracers
- btrfs: zoned: skip splitting and logical rewriting on pre-alloc write
- erofs: release ztailpacking pclusters properly
- locking/arch: Avoid variable shadowing in local_try_cmpxchg()
- refscale: Fix uninitalized use of wait_queue_head_t
- clocksource: Handle negative skews in "skew is too large" messages
- powercap: arm_scmi: Remove recursion while parsing zones
- OPP: Fix potential null ptr dereference in
dev_pm_opp_get_required_pstate()
- OPP: Fix passing 0 to PTR_ERR in _opp_attach_genpd()
- selftests/resctrl: Add resctrl.h into build deps
- selftests/resctrl: Don't leak buffer in fill_cache()
- selftests/resctrl: Unmount resctrl FS if child fails to run benchmark
- selftests/resctrl: Close perf value read fd on errors
- sched/fair: remove util_est boosting
- arm64/ptrace: Clean up error handling path in sve_set_common()
- sched/psi: Select KERNFS as needed
- cpuidle: teo: Update idle duration estimate when choosing shallower state
- x86/decompressor: Don't rely on upper 32 bits of GPRs being preserved
- arm64/fpsimd: Only provide the length to cpufeature for xCR registers
- sched/rt: Fix sysctl_sched_rr_timeslice intial value
- perf/imx_ddr: don't enable counter0 if none of 4 counters are used
- selftests/futex: Order calls to futex_lock_pi
- irqchip/loongson-eiointc: Fix return value checking of eiointc_index
- ACPI: x86: s2idle: Post-increment variables when getting constraints
- ACPI: x86: s2idle: Fix a logic error parsing AMD constraints table
- thermal/of: Fix potential uninitialized value access
- cpufreq: amd-pstate-ut: Remove module parameter access
- cpufreq: amd-pstate-ut: Fix kernel panic when loading the driver
- tools/nolibc: arch-*.h: add missing space after ','
- tools/nolibc: fix up startup failures for -O0 under gcc < 11.1.0
- x86/efistub: Fix PCI ROM preservation in mixed mode
- cpufreq: powernow-k8: Use related_cpus instead of cpus in driver.exit()
- cpufreq: tegra194: add online/offline hooks
- cpufreq: tegra194: remove opp table in exit hook
- selftests/bpf: Fix bpf_nf failure upon test rerun
- libbpf: only reset sec_def handler when necessary
- bpftool: use a local copy of perf_event to fix accessing :: Bpf_cookie
- bpftool: Defi
[Kernel-packages] [Bug 2035373] Re: Move nbd module into modules (from -extra)
This bug was fixed in the package linux-raspi - 6.5.0-1003.4
---
linux-raspi (6.5.0-1003.4) mantic; urgency=medium
* mantic/linux-raspi: 6.5.0-1003.4 -proposed tracker (LP: #2036576)
* Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions (main/d2023.09.14)
* pi-kernel snap is missing modules for microk8s/microceph on UC22
(LP: #2036747)
- [Packaging] raspi: Include rbd and vxlan modules in linux-modules
* Move nbd module into modules (from -extra) (LP: #2035373)
- [Packaging] raspi: Include nbd module in linux-modules
* pi-kernel 5.15 on UC22 is missing most staging modules (LP: #2024443)
- [Packaging] raspi: Include r8188eu module in linux-modules
* Miscellaneous Ubuntu changes
- SAUCE wifi: brcmfmac: Replace 1-element arrays with flexible arrays
- [Config] raspi: Sync configs with master
- [Packaging] raspi: Add a temporary config check
- SAUCE: usb: dwc_otg: Fix flexible array declarations
* Miscellaneous upstream changes
- gpio-fsm: Sort functions into a more logical order
- gpio_fsm: Rework the atomic-vs-non-atomic split
- ASoC: hdmi-codec: Fix broken channel map reporting
[ Ubuntu: 6.5.0-6.6 ]
* mantic/linux: 6.5.0-6.6 -proposed tracker (LP: #2035595)
* Mantic update: v6.5.3 upstream stable release (LP: #2035588)
- drm/amd/display: ensure async flips are only accepted for fast updates
- cpufreq: intel_pstate: set stale CPU frequency to minimum
- tpm: Enable hwrng only for Pluton on AMD CPUs
- Input: i8042 - add quirk for TUXEDO Gemini 17 Gen1/Clevo PD70PN
- Revert "fuse: in fuse_flush only wait if someone wants the return code"
- Revert "f2fs: clean up w/ sbi->log_sectors_per_block"
- Revert "PCI: tegra194: Enable support for 256 Byte payload"
- Revert "net: macsec: preserve ingress frame ordering"
- reiserfs: Check the return value from __getblk()
- splice: always fsnotify_access(in), fsnotify_modify(out) on success
- splice: fsnotify_access(fd)/fsnotify_modify(fd) in vmsplice
- splice: fsnotify_access(in), fsnotify_modify(out) on success in tee
- eventfd: prevent underflow for eventfd semaphores
- fs: Fix error checking for d_hash_and_lookup()
- iomap: Remove large folio handling in iomap_invalidate_folio()
- tmpfs: verify {g,u}id mount options correctly
- selftests/harness: Actually report SKIP for signal tests
- vfs, security: Fix automount superblock LSM init problem, preventing NFS
sb
sharing
- ARM: ptrace: Restore syscall restart tracing
- ARM: ptrace: Restore syscall skipping for tracers
- btrfs: zoned: skip splitting and logical rewriting on pre-alloc write
- erofs: release ztailpacking pclusters properly
- locking/arch: Avoid variable shadowing in local_try_cmpxchg()
- refscale: Fix uninitalized use of wait_queue_head_t
- clocksource: Handle negative skews in "skew is too large" messages
- powercap: arm_scmi: Remove recursion while parsing zones
- OPP: Fix potential null ptr dereference in
dev_pm_opp_get_required_pstate()
- OPP: Fix passing 0 to PTR_ERR in _opp_attach_genpd()
- selftests/resctrl: Add resctrl.h into build deps
- selftests/resctrl: Don't leak buffer in fill_cache()
- selftests/resctrl: Unmount resctrl FS if child fails to run benchmark
- selftests/resctrl: Close perf value read fd on errors
- sched/fair: remove util_est boosting
- arm64/ptrace: Clean up error handling path in sve_set_common()
- sched/psi: Select KERNFS as needed
- cpuidle: teo: Update idle duration estimate when choosing shallower state
- x86/decompressor: Don't rely on upper 32 bits of GPRs being preserved
- arm64/fpsimd: Only provide the length to cpufeature for xCR registers
- sched/rt: Fix sysctl_sched_rr_timeslice intial value
- perf/imx_ddr: don't enable counter0 if none of 4 counters are used
- selftests/futex: Order calls to futex_lock_pi
- irqchip/loongson-eiointc: Fix return value checking of eiointc_index
- ACPI: x86: s2idle: Post-increment variables when getting constraints
- ACPI: x86: s2idle: Fix a logic error parsing AMD constraints table
- thermal/of: Fix potential uninitialized value access
- cpufreq: amd-pstate-ut: Remove module parameter access
- cpufreq: amd-pstate-ut: Fix kernel panic when loading the driver
- tools/nolibc: arch-*.h: add missing space after ','
- tools/nolibc: fix up startup failures for -O0 under gcc < 11.1.0
- x86/efistub: Fix PCI ROM preservation in mixed mode
- cpufreq: powernow-k8: Use related_cpus instead of cpus in driver.exit()
- cpufreq: tegra194: add online/offline hooks
- cpufreq: tegra194: remove opp table in exit hook
- selftests/bpf: Fix bpf_nf failure upon test rerun
- libbpf: only reset sec_def handler when necessary
- bpftool: use a local copy of perf_event to fix accessing :: Bpf_cookie
- bpftool: Defi
[Kernel-packages] [Bug 2024443] Re: pi-kernel 5.15 on UC22 is missing most staging modules
This bug was fixed in the package linux-raspi - 6.5.0-1003.4
---
linux-raspi (6.5.0-1003.4) mantic; urgency=medium
* mantic/linux-raspi: 6.5.0-1003.4 -proposed tracker (LP: #2036576)
* Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions (main/d2023.09.14)
* pi-kernel snap is missing modules for microk8s/microceph on UC22
(LP: #2036747)
- [Packaging] raspi: Include rbd and vxlan modules in linux-modules
* Move nbd module into modules (from -extra) (LP: #2035373)
- [Packaging] raspi: Include nbd module in linux-modules
* pi-kernel 5.15 on UC22 is missing most staging modules (LP: #2024443)
- [Packaging] raspi: Include r8188eu module in linux-modules
* Miscellaneous Ubuntu changes
- SAUCE wifi: brcmfmac: Replace 1-element arrays with flexible arrays
- [Config] raspi: Sync configs with master
- [Packaging] raspi: Add a temporary config check
- SAUCE: usb: dwc_otg: Fix flexible array declarations
* Miscellaneous upstream changes
- gpio-fsm: Sort functions into a more logical order
- gpio_fsm: Rework the atomic-vs-non-atomic split
- ASoC: hdmi-codec: Fix broken channel map reporting
[ Ubuntu: 6.5.0-6.6 ]
* mantic/linux: 6.5.0-6.6 -proposed tracker (LP: #2035595)
* Mantic update: v6.5.3 upstream stable release (LP: #2035588)
- drm/amd/display: ensure async flips are only accepted for fast updates
- cpufreq: intel_pstate: set stale CPU frequency to minimum
- tpm: Enable hwrng only for Pluton on AMD CPUs
- Input: i8042 - add quirk for TUXEDO Gemini 17 Gen1/Clevo PD70PN
- Revert "fuse: in fuse_flush only wait if someone wants the return code"
- Revert "f2fs: clean up w/ sbi->log_sectors_per_block"
- Revert "PCI: tegra194: Enable support for 256 Byte payload"
- Revert "net: macsec: preserve ingress frame ordering"
- reiserfs: Check the return value from __getblk()
- splice: always fsnotify_access(in), fsnotify_modify(out) on success
- splice: fsnotify_access(fd)/fsnotify_modify(fd) in vmsplice
- splice: fsnotify_access(in), fsnotify_modify(out) on success in tee
- eventfd: prevent underflow for eventfd semaphores
- fs: Fix error checking for d_hash_and_lookup()
- iomap: Remove large folio handling in iomap_invalidate_folio()
- tmpfs: verify {g,u}id mount options correctly
- selftests/harness: Actually report SKIP for signal tests
- vfs, security: Fix automount superblock LSM init problem, preventing NFS
sb
sharing
- ARM: ptrace: Restore syscall restart tracing
- ARM: ptrace: Restore syscall skipping for tracers
- btrfs: zoned: skip splitting and logical rewriting on pre-alloc write
- erofs: release ztailpacking pclusters properly
- locking/arch: Avoid variable shadowing in local_try_cmpxchg()
- refscale: Fix uninitalized use of wait_queue_head_t
- clocksource: Handle negative skews in "skew is too large" messages
- powercap: arm_scmi: Remove recursion while parsing zones
- OPP: Fix potential null ptr dereference in
dev_pm_opp_get_required_pstate()
- OPP: Fix passing 0 to PTR_ERR in _opp_attach_genpd()
- selftests/resctrl: Add resctrl.h into build deps
- selftests/resctrl: Don't leak buffer in fill_cache()
- selftests/resctrl: Unmount resctrl FS if child fails to run benchmark
- selftests/resctrl: Close perf value read fd on errors
- sched/fair: remove util_est boosting
- arm64/ptrace: Clean up error handling path in sve_set_common()
- sched/psi: Select KERNFS as needed
- cpuidle: teo: Update idle duration estimate when choosing shallower state
- x86/decompressor: Don't rely on upper 32 bits of GPRs being preserved
- arm64/fpsimd: Only provide the length to cpufeature for xCR registers
- sched/rt: Fix sysctl_sched_rr_timeslice intial value
- perf/imx_ddr: don't enable counter0 if none of 4 counters are used
- selftests/futex: Order calls to futex_lock_pi
- irqchip/loongson-eiointc: Fix return value checking of eiointc_index
- ACPI: x86: s2idle: Post-increment variables when getting constraints
- ACPI: x86: s2idle: Fix a logic error parsing AMD constraints table
- thermal/of: Fix potential uninitialized value access
- cpufreq: amd-pstate-ut: Remove module parameter access
- cpufreq: amd-pstate-ut: Fix kernel panic when loading the driver
- tools/nolibc: arch-*.h: add missing space after ','
- tools/nolibc: fix up startup failures for -O0 under gcc < 11.1.0
- x86/efistub: Fix PCI ROM preservation in mixed mode
- cpufreq: powernow-k8: Use related_cpus instead of cpus in driver.exit()
- cpufreq: tegra194: add online/offline hooks
- cpufreq: tegra194: remove opp table in exit hook
- selftests/bpf: Fix bpf_nf failure upon test rerun
- libbpf: only reset sec_def handler when necessary
- bpftool: use a local copy of perf_event to fix accessing :: Bpf_cookie
- bpftool: Defi
[Kernel-packages] [Bug 2036625] Re: package linux-oem-6.1-tools-host (not installed) failed to install/upgrade: próba nadpisania "/lib/systemd/system/kvm_stat.service", który istnieje także w pakiecie
** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2036625 Title: package linux-oem-6.1-tools-host (not installed) failed to install/upgrade: próba nadpisania "/lib/systemd/system/kvm_stat.service", który istnieje także w pakiecie linux-oem-5.17-tools-host 5.17.0-1035.36 Status in linux-oem-6.1 package in Ubuntu: New Bug description: Install problem ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-oem-6.1-tools-host (not installed) ProcVersionSignature: Ubuntu 6.5.0-1003.3-oem 6.5.0 Uname: Linux 6.5.0-1003-oem x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue Sep 19 17:16:27 2023 ErrorMessage: próba nadpisania "/lib/systemd/system/kvm_stat.service", który istnieje także w pakiecie linux-oem-5.17-tools-host 5.17.0-1035.36 InstallationDate: Installed on 2023-08-27 (23 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.10 SourcePackage: linux-oem-6.1 Title: package linux-oem-6.1-tools-host (not installed) failed to install/upgrade: próba nadpisania "/lib/systemd/system/kvm_stat.service", który istnieje także w pakiecie linux-oem-5.17-tools-host 5.17.0-1035.36 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.1/+bug/2036625/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2036623] Re: package linux-oem-6.0-tools-host (not installed) failed to install/upgrade: próba nadpisania "/lib/systemd/system/kvm_stat.service", który istnieje także w pakiecie
** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/2036623 Title: package linux-oem-6.0-tools-host (not installed) failed to install/upgrade: próba nadpisania "/lib/systemd/system/kvm_stat.service", który istnieje także w pakiecie linux-oem-5.17-tools-host 5.17.0-1035.36 Status in linux-oem-6.0 package in Ubuntu: New Bug description: Install problem ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-oem-6.0-tools-host (not installed) ProcVersionSignature: Ubuntu 6.5.0-1003.3-oem 6.5.0 Uname: Linux 6.5.0-1003-oem x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue Sep 19 17:15:26 2023 ErrorMessage: próba nadpisania "/lib/systemd/system/kvm_stat.service", który istnieje także w pakiecie linux-oem-5.17-tools-host 5.17.0-1035.36 InstallationDate: Installed on 2023-08-27 (23 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.10 SourcePackage: linux-oem-6.0 Title: package linux-oem-6.0-tools-host (not installed) failed to install/upgrade: próba nadpisania "/lib/systemd/system/kvm_stat.service", który istnieje także w pakiecie linux-oem-5.17-tools-host 5.17.0-1035.36 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.0/+bug/2036623/+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 1968040] Re: [i915] Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]
Hello. I seem to be hitting the same bug and I have attached the drm_info output while the screen is stuck in the off state. I see the the same Failed to post KMS update: drmModeAtomicCommit: Invalid argument and Page flip discarded: drmModeAtomicCommit: Invalid argument in my logs while the the monitor is stuck. It gets stuck when I turn my monitor off from inactivity or the monitor turns itself off after locking the computer. Putting MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 in /etc/environment fixed it for me. Rarely the screen also flickers at random moment, turns dark for a second, and then turns back on. When I checked the logs after it, I see the drmModeAtomicCommit: Invalid argument lines again. I have Ubuntu 22.04 with an external monitor Single display setup. Also Intel. ** Attachment added: "drm_info.txt" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1968040/+attachment/5705009/+files/drm_info.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/1968040 Title: [i915] Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument] Status in GNOME Shell: New Status in Mutter: New Status in linux package in Ubuntu: Confirmed Status in linux-hwe-5.19 package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: [ Workaround ] Add to /etc/environment (in Ubuntu 22.04): MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 or in Ubuntu 22.10 and later: MUTTER_DEBUG_FORCE_KMS_MODE=simple and then reboot. [ Upstream bugs ] https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5098 https://gitlab.gnome.org/GNOME/mutter/-/issues/2268 https://gitlab.gnome.org/GNOME/mutter/-/issues/2749 [ Original report ] (initially reported as a comment on bug #1965085, and split into a separate bug report) After I lock my screen and let it blank, moving the mouse or pressing any key on the keyboard won't wake it up. The only reliable workaround I've found is to press Ctrl+Alt+F1. That's on a fully up-to-date jammy, my hardware is an Intel NUC with a single Samsung monitor connected with a standard HDMI cable. This is a regression that started happening yesterday (2022-04-05) if I can remember correctly (I do apply pending updates at least once daily). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Apr 6 15:19:30 2022 InstallationDate: Installed on 2020-09-16 (566 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200910) SourcePackage: gdm3 UpgradeStatus: Upgraded to jammy on 2022-03-19 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1968040/+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 2037593] [NEW] Jammy update: v5.15.126 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.15.126 upstream stable release from git://git.kernel.org/ io_uring: gate iowait schedule on having pending requests perf: Fix function pointer case net/mlx5: Free irqs only on shutdown callback arm64: errata: Add workaround for TSB flush failures arm64: errata: Add detection for TRBE write to out-of-range UBUNTU: [Config] updateconfigs for ARM64_ERRATUM_ and ARM64_WORKAROUND_TSB_FLUSH_FAILURE iommu/arm-smmu-v3: Work around MMU-600 erratum 1076982 iommu/arm-smmu-v3: Document MMU-700 erratum 2812531 iommu/arm-smmu-v3: Add explicit feature for nesting iommu/arm-smmu-v3: Document nesting-related errata arm64: dts: imx8mn-var-som: add missing pull-up for onboard PHY reset pinmux word-at-a-time: use the same return type for has_zero regardless of endianness KVM: s390: fix sthyi error handling wifi: cfg80211: Fix return value in scan logic net/mlx5: DR, fix memory leak in mlx5dr_cmd_create_reformat_ctx net/mlx5e: fix return value check in mlx5e_ipsec_remove_trailer() bpf: Add length check for SK_DIAG_BPF_STORAGE_REQ_MAP_FD parsing rtnetlink: let rtnl_bridge_setlink checks IFLA_BRIDGE_MODE length net: dsa: fix value check in bcm_sf2_sw_probe() perf test uprobe_from_different_cu: Skip if there is no gcc net: sched: cls_u32: Fix match key mis-addressing mISDN: hfcpci: Fix potential deadlock on &hc->lock qed: Fix kernel-doc warnings qed: Fix scheduling in a tasklet while getting stats net: annotate data-races around sk->sk_max_pacing_rate net: add missing READ_ONCE(sk->sk_rcvlowat) annotation net: add missing READ_ONCE(sk->sk_sndbuf) annotation net: add missing READ_ONCE(sk->sk_rcvbuf) annotation net: add missing data-race annotations around sk->sk_peek_off net: add missing data-race annotation for sk_ll_usec net/sched: taprio: Limit TCA_TAPRIO_ATTR_SCHED_CYCLE_TIME to INT_MAX. bpf, cpumap: Handle skb as well when clean up ptr_ring bpf: sockmap: Remove preempt_disable in sock_map_sk_acquire net: ll_temac: Switch to use dev_err_probe() helper net: ll_temac: fix error checking of irq_of_parse_and_map() net: korina: handle clk prepare error in korina_probe() net: netsec: Ignore 'phy-mode' on SynQuacer in DT mode net: dcb: choose correct policy to parse DCB_ATTR_BCN s390/qeth: Don't call dev_close/dev_open (DOWN/UP) ip6mr: Fix skb_under_panic in ip6mr_cache_report() vxlan: Fix nexthop hash size net/mlx5: fs_core: Make find_closest_ft more generic net/mlx5: fs_core: Skip the FTs in the same FS_TYPE_PRIO_CHAINS fs_prio prestera: fix fallback to previous version on same major version tcp_metrics: fix addr_same() helper tcp_metrics: annotate data-races around tm->tcpm_stamp tcp_metrics: annotate data-races around tm->tcpm_lock tcp_metrics: annotate data-races around tm->tcpm_vals[] tcp_metrics: annotate data-races around tm->tcpm_net tcp_metrics: fix data-race in tcpm_suck_dst() vs fastopen scsi: zfcp: Defer fc_rport blocking until after ADISC response scsi: storvsc: Limit max_sectors for virtual Fibre Channel devices libceph: fix potential hang in ceph_osdc_notify() USB: zaurus: Add ID for A-300/B-500/C-700 ceph: defer stopping mdsc delayed_work firmware: arm_scmi: Drop OF node reference in the transport channel setup exfat: use kvmalloc_array/kvfree instead of kmalloc_array/kfree exfat: release s_lock before calling dir_emit() mtd: spinand: toshiba: Fix ecc_get_status mtd: rawnand: meson: fix OOB available bytes for ECC arm64: dts: stratix10: fix incorrect I2C property for SCL signal wifi: mt76: mt7615: do not advertise 5 GHz on first phy of MT7615D (DBDC) rbd: prevent busy loop when requesting exclusive lock bpf: Disable preemption in bpf_event_output open: make RESOLVE_CACHED correctly test for O_TMPFILE drm/ttm: check null pointer before accessing when swapping bpf, cpumap: Make sure kthread is running before map update returns file: reinstate f_pos locking optimization for regular files fs/ntfs3: Use __GFP_NOWARN allocation at ntfs_load_attr_list() fs/sysv: Null check to prevent null-ptr-deref bug net: usbnet: Fix WARNING in usbnet_start_xmit/usb_submit_urb fs: Protect reconfiguration of sb read-write from racing writes ext2: Drop fragment support mtd: rawnand: omap_elm: Fix incorrect type in assignment mtd: rawnand: rockchip: fix oobfree offset and description mtd: rawnand: rockchip: Align hwecc vs. raw page helper layouts mtd: rawnand: fsl_upm: Fix an off-by one test in fun_exec_op() powerpc/mm/altmap: Fix altmap boundary check drm/imx/ipuv3: Fix front porch adjustment upon hactive aligning selftests/rseq: check if libc rseq support is re
[Kernel-packages] [Bug 2013236] Re: b43 driver conflicts with bcmwl driver for some Broadcom devices
I tested this today with "Ubuntu Legacy 23.10 "Mantic Minotaur" - Daily amd64 (20230927)" and discovered the b43 driver still does not work with my wireless adapter as I saw the following in dmesg: $ sudo dmesg | grep b43 [sudo] password for bdmurray: [ 18.921934] b43-phy0: Broadcom 4352 WLAN found (core revision 42) [ 18.922272] b43-phy0 ERROR: FOUND UNSUPPORTED PHY (Analog 12, Type 11 (AC), Revision 1) [ 18.922277] b43: probe of bcma0:1 failed with error -95 However, using software-properties-gtk to install the proprietary driver (broadcom-sta-dkms) worked and the b43 driver was blacklisted and I was able to connect to a wireless network. -- 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/2013236 Title: b43 driver conflicts with bcmwl driver for some Broadcom devices Status in broadcom-sta package in Ubuntu: New Status in linux-firmware package in Ubuntu: Invalid Status in ubuntu-drivers-common package in Ubuntu: Incomplete Status in broadcom-sta source package in Lunar: New Status in linux-firmware source package in Lunar: Invalid Status in ubuntu-drivers-common source package in Lunar: Incomplete Status in broadcom-sta source package in Mantic: New Status in linux-firmware source package in Mantic: Invalid Status in ubuntu-drivers-common source package in Mantic: Incomplete Bug description: Specifically for Lunar - using a Macbook Air 2012, its wireless driver was not enabled even though I ticked the wireless tickbox on the installer. A quick look at the installer logs reveals various issues syslog:2023-03-29T18:01:25.141599+00:00 ubuntu-budgie kernel: [ 43.063747] b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141625+00:00 ubuntu-budgie kernel: [ 43.063802] b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [ 43.063862] b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [ 43.063908] b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with error -2 I will attach the installer logs manually since this was captured after the installation Note - on 20.04.6, 22.04.2 and 22.10 with the same laptop bcmwl was installed correctly during the install so this is a regression with the 6.2 kernel Workaround -- You'll first need to blacklist the b43 driver by adding a blacklist file to /etc/modprobe.d/b43.conf with the contents "blacklist b43". Then run "update-initramfs -u". Then install the bcmwl-kernel-source package. After a reboot your wireless device should be available. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/broadcom-sta/+bug/2013236/+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
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nvidia-graphics-drivers-535 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/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
Re: [Kernel-packages] [Bug 2013236] Re: b43 driver conflicts with bcmwl driver for some Broadcom devices
On Wed, Sep 27, 2023 at 11:16:52PM -, Brian Murray wrote: > However, using software-properties-gtk to install the proprietary driver > (broadcom-sta-dkms) worked and the b43 driver was blacklisted and I was > able to connect to a wireless network. Does this mean the driver was not offered to you automatically through ubuntu-drivers-common? -- 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/2013236 Title: b43 driver conflicts with bcmwl driver for some Broadcom devices Status in broadcom-sta package in Ubuntu: New Status in linux-firmware package in Ubuntu: Invalid Status in ubuntu-drivers-common package in Ubuntu: Incomplete Status in broadcom-sta source package in Lunar: New Status in linux-firmware source package in Lunar: Invalid Status in ubuntu-drivers-common source package in Lunar: Incomplete Status in broadcom-sta source package in Mantic: New Status in linux-firmware source package in Mantic: Invalid Status in ubuntu-drivers-common source package in Mantic: Incomplete Bug description: Specifically for Lunar - using a Macbook Air 2012, its wireless driver was not enabled even though I ticked the wireless tickbox on the installer. A quick look at the installer logs reveals various issues syslog:2023-03-29T18:01:25.141599+00:00 ubuntu-budgie kernel: [ 43.063747] b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141625+00:00 ubuntu-budgie kernel: [ 43.063802] b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [ 43.063862] b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [ 43.063908] b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with error -2 I will attach the installer logs manually since this was captured after the installation Note - on 20.04.6, 22.04.2 and 22.10 with the same laptop bcmwl was installed correctly during the install so this is a regression with the 6.2 kernel Workaround -- You'll first need to blacklist the b43 driver by adding a blacklist file to /etc/modprobe.d/b43.conf with the contents "blacklist b43". Then run "update-initramfs -u". Then install the bcmwl-kernel-source package. After a reboot your wireless device should be available. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/broadcom-sta/+bug/2013236/+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 2013236] Re: b43 driver conflicts with bcmwl driver for some Broadcom devices
On Thu, Sep 28, 2023 at 12:34:34AM -, Steve Langasek wrote: > On Wed, Sep 27, 2023 at 11:16:52PM -, Brian Murray wrote: > > However, using software-properties-gtk to install the proprietary driver > > (broadcom-sta-dkms) worked and the b43 driver was blacklisted and I was > > able to connect to a wireless network. > > Does this mean the driver was not offered to you automatically through > ubuntu-drivers-common? I'm not exactly sure what you mean by automatically. The b43 was driver was the in use after installing and rebooting. `ubuntu-drivers list` does show broadcom-sta-dkms as an option however, running `ubuntu-drivers install` indicates that "All the available drivers are already installed". -- Brian Murray -- 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/2013236 Title: b43 driver conflicts with bcmwl driver for some Broadcom devices Status in broadcom-sta package in Ubuntu: New Status in linux-firmware package in Ubuntu: Invalid Status in ubuntu-drivers-common package in Ubuntu: Incomplete Status in broadcom-sta source package in Lunar: New Status in linux-firmware source package in Lunar: Invalid Status in ubuntu-drivers-common source package in Lunar: Incomplete Status in broadcom-sta source package in Mantic: New Status in linux-firmware source package in Mantic: Invalid Status in ubuntu-drivers-common source package in Mantic: Incomplete Bug description: Specifically for Lunar - using a Macbook Air 2012, its wireless driver was not enabled even though I ticked the wireless tickbox on the installer. A quick look at the installer logs reveals various issues syslog:2023-03-29T18:01:25.141599+00:00 ubuntu-budgie kernel: [ 43.063747] b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141625+00:00 ubuntu-budgie kernel: [ 43.063802] b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [ 43.063862] b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [ 43.063908] b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with error -2 I will attach the installer logs manually since this was captured after the installation Note - on 20.04.6, 22.04.2 and 22.10 with the same laptop bcmwl was installed correctly during the install so this is a regression with the 6.2 kernel Workaround -- You'll first need to blacklist the b43 driver by adding a blacklist file to /etc/modprobe.d/b43.conf with the contents "blacklist b43". Then run "update-initramfs -u". Then install the bcmwl-kernel-source package. After a reboot your wireless device should be available. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/broadcom-sta/+bug/2013236/+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 2037513] Re: HP ProBook 450 G8 Notebook fail to wifi test
** Changed in: linux-signed-hwe-5.15 (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2037513 Title: HP ProBook 450 G8 Notebook fail to wifi test Status in linux-signed-hwe-5.15 package in Ubuntu: In Progress Bug description: I'm reviewing the SRU test result on this machine. I found that this machine always fails to wifi test and also pop out a lot of error message in dmesg. It's not a regression, since according to previous test run it has failed already. Just because we missed reviewing it for a while. The journal log is attach, please check further hardware informations at https://certification.canonical.com/hardware/202106-29176/ ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.15.0-86-generic 5.15.0-86.96~20.04.1 ProcVersionSignature: Ubuntu 5.15.0-86.96~20.04.1-generic 5.15.122 Uname: Linux 5.15.0-86-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Sep 27 15:47:37 2023 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-focal-amd64-20220621-7+pc-stella-cmit-focal-amd64+X00 InstallationDate: Installed on 2023-09-25 (2 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20220621-04:14 SourcePackage: linux-signed-hwe-5.15 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.15/+bug/2037513/+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 2034619] Re: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland
** Summary changed: - [amdgpu] gnome-shell gets SIGKILL'd when lock screen in Wayland + [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland -- 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/2034619 Title: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland Status in Linux: New Status in Mutter: New Status in X.Org X server: Fix Released Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: In Progress Status in linux source package in Mantic: Confirmed Status in mutter source package in Mantic: In Progress Bug description: [ Workaround ] Add this to /etc/environment: MUTTER_DEBUG_KMS_THREAD_TYPE=user and then reboot. [ Original Description] I have this issue on Ubuntu 23.10. Lock screen works only with an external monitor connected. Otherwise the session is ended and the user is logged out and brought to the gdm screen. All works in xorg. ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~beta.1-0ubuntu2 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 22:32:22 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2023-09-03 (3 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230901.1) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 45~beta.1-1ubuntu2 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2034619/+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 2035123] Re: scripts/pahole-flags.sh change return to exit 0
** Summary changed:
- scripts/pahole-flags.sh needs upstream fix
+ scripts/pahole-flags.sh change return to exit 0
** Description changed:
- When doing a kernel make in our Jammy repo we notice the follow error
- being emitted:
+ BugLink: https://bugs.launchpad.net/bugs/2035123
+
+ [Impact]
+
+ When building the Jammy linux-bluefield kernel tree on a system without
+ pahole installed, the following warning is emitted:
./scripts/pahole-flags.sh: line 7: return: can only `return' from a
function or sourced script
- It appears that while the Jammy baseline is 5.15.99 (as per the top-level
Makefile)
- the file scripts/pahole-flags.sh is out of date with upstream 5.15.99
+ scripts/pahole-flags.sh attempts to return from an if statement that is
+ not within a function, and generates a warning.
- The upstream 5.15.99 version of scripts/pahole-flags.sh fixes this issue by
making this change:
- 7c7
- < return
- ---
- > exit 0
+ The fix is straightforward, changing return to an exit 0.
- This seems like a simple fix, but not sure who should be fixing this.
+ --- a/scripts/pahole-flags.sh
+ +++ b/scripts/pahole-flags.sh
+ @@ -4,7 +4,7 @@
+ extra_paholeopt=
+
+ if ! [ -x "$(command -v ${PAHOLE})" ]; then
+ - return
+ + exit 0
+ fi
+
+ [Testcase]
+
+ Clone the linux-bluefield kernel tree and build it on a arm64 system without
+ pahole installed.
+
+ A test kernel is available with the fix applied in:
+
+ https://launchpad.net/~mruffell/+archive/ubuntu/sf368560-test
+
+ Both linux-bluefield and ubuntu-jammy build correctly.
+
+ [Fix]
+
+ This was fixed by Linus Torvalds in the following merge commit:
+
+ commit fc02cb2b37fe2cbf1d3334b9f0f0eab9431766c4
+ Merge: bfc484fe6abb 84882cf72cd7
+ Author: Linus Torvalds
+ Date: Tue Nov 2 06:20:58 2021 -0700
+ Subject: Merge tag 'net-next-for-5.16' of
git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next
+ Link:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=fc02cb2b37fe2cbf1d3334b9f0f0eab9431766c4
+
+ Note, the original commit does not have the fix included:
+
+ commit 9741e07ece7c247dd65e1aa01e16b683f01c05a8
+ Author: Jiri Olsa
+ Date: Fri Oct 29 14:57:29 2021 +0200
+ Subject: kbuild: Unify options for BTF generation for vmlinux and modules
+ Link:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9741e07ece7c247dd65e1aa01e16b683f01c05a8
+
+ The Ubuntu kernel cherry-picked the original commit and did not pick up the
+ silent fix made in the merge commit. Submitting the silent fix as a SAUCE
patch
+ with changelog describing the change.
+
+ [Where problems could occur]
+
+ The Ubuntu kernel is built with pahole enabled, and requires pahole to
+ be installed as a build dependency. It is extremely unlikely that any
+ users are disabling pahole at build time, apart from linux-bluefield
+ engineers.
+
+ If a regression were to occur, engineers would see errors during build
+ time about scripts/pahole-flags.sh not executing properly.
+
+ [Other info]
+
+ Linus remarked about the issue in the following lkml discussion:
+
+
https://lore.kernel.org/lkml/CAHk-=wgdE6=ob5nf60gvryag24mkajbgjf3jpufme1k_upb...@mail.gmail.com/
+
https://lore.kernel.org/lkml/CAHk-=wgPZM4bN=LUCrMkG3FX808QSLm6Uv6ixm5P350_7c=x...@mail.gmail.com/
+
+ This was silently Incorporated into the linux-stable commit:
+
+ commit 0baced0e0938f2895ceba54038eaf15ed91032e7 5.15.y
+ From: Jiri Olsa
+ Date: Sun, 4 Sep 2022 15:19:00 +0200
+ Subject: kbuild: Unify options for BTF generation for vmlinux and modules
+ Link:
https://github.com/gregkh/linux/commit/0baced0e0938f2895ceba54038eaf15ed91032e7
** Changed in: linux (Ubuntu)
Status: Incomplete => Fix Released
** Changed in: linux (Ubuntu Jammy)
Status: Triaged => In Progress
** Changed in: linux-bluefield (Ubuntu Jammy)
Status: Triaged => In Progress
** Changed in: linux (Ubuntu Jammy)
Importance: Undecided => Medium
** Changed in: linux-bluefield (Ubuntu Jammy)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Jammy)
Assignee: (unassigned) => Matthew Ruffell (mruffell)
** Changed in: linux-bluefield (Ubuntu Jammy)
Assignee: (unassigned) => Matthew Ruffell (mruffell)
** Description changed:
BugLink: https://bugs.launchpad.net/bugs/2035123
[Impact]
When building the Jammy linux-bluefield kernel tree on a system without
pahole installed, the following warning is emitted:
./scripts/pahole-flags.sh: line 7: return: can only `return' from a
function or sourced script
scripts/pahole-flags.sh attempts to return from an if statement that is
not within a function, and generates a warning.
The fix is straightforward, changing return to an exit 0.
--- a/scripts/pahole-flags.sh
+++ b/scripts/pahole-flags.sh
@@ -4,7 +4,7 @@
- extra_paholeopt=
-
- if ! [ -x "$(command -v ${PAHOLE})" ]; then
+ extra_paholeopt=
+
+ if ! [ -x "$(command -
[Kernel-packages] [Bug 2035123] Re: scripts/pahole-flags.sh change return to exit 0
Patches have been submitted to the kernel team mailing list:
https://lists.ubuntu.com/archives/kernel-team/2023-September/144570.html
https://lists.ubuntu.com/archives/kernel-team/2023-September/144571.html
--
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/2035123
Title:
scripts/pahole-flags.sh change return to exit 0
Status in linux package in Ubuntu:
Fix Released
Status in linux-bluefield package in Ubuntu:
Triaged
Status in linux source package in Jammy:
In Progress
Status in linux-bluefield source package in Jammy:
In Progress
Bug description:
BugLink: https://bugs.launchpad.net/bugs/2035123
[Impact]
When building the Jammy linux-bluefield kernel tree on a system
without pahole installed, the following warning is emitted:
./scripts/pahole-flags.sh: line 7: return: can only `return' from a
function or sourced script
scripts/pahole-flags.sh attempts to return from an if statement that
is not within a function, and generates a warning.
The fix is straightforward, changing return to an exit 0.
--- a/scripts/pahole-flags.sh
+++ b/scripts/pahole-flags.sh
@@ -4,7 +4,7 @@
extra_paholeopt=
if ! [ -x "$(command -v ${PAHOLE})" ]; then
- return
+ exit 0
fi
[Testcase]
Clone the linux-bluefield kernel tree and build it on a arm64 system without
pahole installed.
A test kernel is available with the fix applied in:
https://launchpad.net/~mruffell/+archive/ubuntu/sf368560-test
Both linux-bluefield and ubuntu-jammy build correctly.
[Fix]
This was fixed by Linus Torvalds in the following merge commit:
commit fc02cb2b37fe2cbf1d3334b9f0f0eab9431766c4
Merge: bfc484fe6abb 84882cf72cd7
Author: Linus Torvalds
Date: Tue Nov 2 06:20:58 2021 -0700
Subject: Merge tag 'net-next-for-5.16' of
git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next
Link:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=fc02cb2b37fe2cbf1d3334b9f0f0eab9431766c4
Note, the original commit does not have the fix included:
commit 9741e07ece7c247dd65e1aa01e16b683f01c05a8
Author: Jiri Olsa
Date: Fri Oct 29 14:57:29 2021 +0200
Subject: kbuild: Unify options for BTF generation for vmlinux and modules
Link:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9741e07ece7c247dd65e1aa01e16b683f01c05a8
The Ubuntu kernel cherry-picked the original commit and did not pick up the
silent fix made in the merge commit. Submitting the silent fix as a SAUCE
patch
with changelog describing the change.
Note: I know SAUCE patches are bad, but in this scenario, to revert
the initial commit and re-apply the fixed version would require us to
revert two additional dependency commits, making six patches to
review, vs, a one line change in a SAUCE commit that has a real
changelog entry.
[Where problems could occur]
The Ubuntu kernel is built with pahole enabled, and requires pahole to
be installed as a build dependency. It is extremely unlikely that any
users are disabling pahole at build time, apart from linux-bluefield
engineers.
If a regression were to occur, engineers would see errors during build
time about scripts/pahole-flags.sh not executing properly.
[Other info]
Linus remarked about the issue in the following lkml discussion:
https://lore.kernel.org/lkml/CAHk-=wgdE6=ob5nf60gvryag24mkajbgjf3jpufme1k_upb...@mail.gmail.com/
https://lore.kernel.org/lkml/CAHk-=wgPZM4bN=LUCrMkG3FX808QSLm6Uv6ixm5P350_7c=x...@mail.gmail.com/
This was silently Incorporated into the linux-stable commit:
commit 0baced0e0938f2895ceba54038eaf15ed91032e7 5.15.y
From: Jiri Olsa
Date: Sun, 4 Sep 2022 15:19:00 +0200
Subject: kbuild: Unify options for BTF generation for vmlinux and modules
Link:
https://github.com/gregkh/linux/commit/0baced0e0938f2895ceba54038eaf15ed91032e7
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2035123/+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 1968040] Re: [i915] Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]
Please provide a system log showing the errors: journalctl -b0 > journal.txt and attach the resulting text file here. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/1968040 Title: [i915] Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument] Status in GNOME Shell: New Status in Mutter: New Status in linux package in Ubuntu: Confirmed Status in linux-hwe-5.19 package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: [ Workaround ] Add to /etc/environment (in Ubuntu 22.04): MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 or in Ubuntu 22.10 and later: MUTTER_DEBUG_FORCE_KMS_MODE=simple and then reboot. [ Upstream bugs ] https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5098 https://gitlab.gnome.org/GNOME/mutter/-/issues/2268 https://gitlab.gnome.org/GNOME/mutter/-/issues/2749 [ Original report ] (initially reported as a comment on bug #1965085, and split into a separate bug report) After I lock my screen and let it blank, moving the mouse or pressing any key on the keyboard won't wake it up. The only reliable workaround I've found is to press Ctrl+Alt+F1. That's on a fully up-to-date jammy, my hardware is an Intel NUC with a single Samsung monitor connected with a standard HDMI cable. This is a regression that started happening yesterday (2022-04-05) if I can remember correctly (I do apply pending updates at least once daily). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Apr 6 15:19:30 2022 InstallationDate: Installed on 2020-09-16 (566 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200910) SourcePackage: gdm3 UpgradeStatus: Upgraded to jammy on 2022-03-19 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1968040/+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 2013236] Re: b43 driver conflicts with bcmwl driver for some Broadcom devices
** Changed in: ubuntu-drivers-common (Ubuntu Mantic) Importance: Undecided => High ** Changed in: ubuntu-drivers-common (Ubuntu Mantic) Status: Incomplete => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2013236 Title: b43 driver conflicts with bcmwl driver for some Broadcom devices Status in broadcom-sta package in Ubuntu: New Status in linux-firmware package in Ubuntu: Invalid Status in ubuntu-drivers-common package in Ubuntu: Triaged Status in broadcom-sta source package in Lunar: New Status in linux-firmware source package in Lunar: Invalid Status in ubuntu-drivers-common source package in Lunar: Incomplete Status in broadcom-sta source package in Mantic: New Status in linux-firmware source package in Mantic: Invalid Status in ubuntu-drivers-common source package in Mantic: Triaged Bug description: Specifically for Lunar - using a Macbook Air 2012, its wireless driver was not enabled even though I ticked the wireless tickbox on the installer. A quick look at the installer logs reveals various issues syslog:2023-03-29T18:01:25.141599+00:00 ubuntu-budgie kernel: [ 43.063747] b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141625+00:00 ubuntu-budgie kernel: [ 43.063802] b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [ 43.063862] b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [ 43.063908] b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with error -2 I will attach the installer logs manually since this was captured after the installation Note - on 20.04.6, 22.04.2 and 22.10 with the same laptop bcmwl was installed correctly during the install so this is a regression with the 6.2 kernel Workaround -- You'll first need to blacklist the b43 driver by adding a blacklist file to /etc/modprobe.d/b43.conf with the contents "blacklist b43". Then run "update-initramfs -u". Then install the bcmwl-kernel-source package. After a reboot your wireless device should be available. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/broadcom-sta/+bug/2013236/+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 2033441] Re: linux-firmware is outdated
Jammy and a 6.2 kernel should be sufficient.
--
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/2033441
Title:
linux-firmware is outdated
Status in linux-firmware package in Ubuntu:
Triaged
Status in linux-firmware source package in Lunar:
Fix Committed
Bug description:
[Impact]
This is optimus laptop with Intel 11th Gen and Nvidia.
In recent kernels like 6.2.0 it gives a blank screen after booting and if
nouveau.modset=1 is set, it completely freeze the system.
I remember it was working fine in 5.x kernels.
Now I have to blacklist nouveau and use Nvidia driver instead.
Using this commit of linux-firmware solved the issue:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/nvidia?id=2e92a49f90f73c8edc44b25c6e669d5e70893c90
[Fix]
Upstream commit 2e92a49f90f9 ("nvidia: update Tu10x and Tu11x signed
firmware to support newer Turing HW")
[Test Case]
Boot a machine with relevant GPU.
[Where Problems Could Occur]
Updated Nvidia FW so limited to machines with relevant GPUs.
[Additional Information]
# journalctl -b -2 | grep nouveau
Aug 29 21:07:54 ZB kernel: Command line: BOOT_IMAGE=/vmlinuz-6.2.0-31-generic
root=/dev/mapper/vgubuntu-root ro nouveau.modeset=1 quiet splash
Aug 29 21:07:54 ZB kernel: Kernel command line:
BOOT_IMAGE=/vmlinuz-6.2.0-31-generic root=/dev/mapper/vgubuntu-root ro
nouveau.modeset=1 quiet splash
Aug 29 21:07:54 ZB kernel: nouveau: detected PR support, will not use DSM
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: enabling device ( ->
0003)
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: NVIDIA TU117 (167000a1)
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: bios: version 90.17.61.00.73
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: pmu: firmware unavailable
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: fb: 2048 MiB GDDR6
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: halted
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC SCTL 7021
TIDX 1b1f
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 23ac
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 2055
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 2305
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 201c
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 2303
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 2051
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 269e
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 2617
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25e8
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25b2
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25aa
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 25b9
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 1822
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 1a97
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 26c8
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: sec2: TRACEPC: 2318
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: DRM: VRAM: 2048 MiB
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: DRM: GART: 536870912 MiB
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: DRM: BIT table 'A' not found
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: DRM: BIT table 'L' not found
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: DRM: Pointer to TMDS table
not found
Aug 29 21:07:54 ZB kernel: nouveau :59:00.0: DRM: DCB version 4.1
Aug 29 21:07:54 ZB kernel: nouveau :59:
[Kernel-packages] [Bug 1968040] Re: [i915] Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]
There you go, attached is the journal of the boot when I removed the workaround and got the screen stuck in the off state. I assume this is what you really wanted and not the journal of my current boot. I have since rebooted many times. The messages start at 21:45 which is when I managed to get the screen stuck. I like my privacy, so I also added --no-hostname. ** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1968040/+attachment/5705055/+files/journal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/1968040 Title: [i915] Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument] Status in GNOME Shell: New Status in Mutter: New Status in linux package in Ubuntu: Confirmed Status in linux-hwe-5.19 package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: [ Workaround ] Add to /etc/environment (in Ubuntu 22.04): MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 or in Ubuntu 22.10 and later: MUTTER_DEBUG_FORCE_KMS_MODE=simple and then reboot. [ Upstream bugs ] https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5098 https://gitlab.gnome.org/GNOME/mutter/-/issues/2268 https://gitlab.gnome.org/GNOME/mutter/-/issues/2749 [ Original report ] (initially reported as a comment on bug #1965085, and split into a separate bug report) After I lock my screen and let it blank, moving the mouse or pressing any key on the keyboard won't wake it up. The only reliable workaround I've found is to press Ctrl+Alt+F1. That's on a fully up-to-date jammy, my hardware is an Intel NUC with a single Samsung monitor connected with a standard HDMI cable. This is a regression that started happening yesterday (2022-04-05) if I can remember correctly (I do apply pending updates at least once daily). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Apr 6 15:19:30 2022 InstallationDate: Installed on 2020-09-16 (566 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200910) SourcePackage: gdm3 UpgradeStatus: Upgraded to jammy on 2022-03-19 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1968040/+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 2037490] Re: "call trace" is reported for mptsas driver
Most likely a result of this:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=2d47c6956ab3
** Tags added: kernel-flexible-array
--
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/2037490
Title:
"call trace" is reported for mptsas driver
Status in linux package in Ubuntu:
Confirmed
Bug description:
Steps to reproduce:
1. install a ubuntu 23.10 VM on an ESXi Server
2. hot add a lsilogicsas controller and a lsilogicsas disk
Call Trace will be reported in dmesg log
[ 176.181166]
[ 176.181167] UBSAN: array-index-out-of-bounds in
/build/linux-IPoq5q/linux-6.5.0/drivers/message/fusion/mptsas.c:2448:22
[ 176.181171] index 1 is out of range for type 'MPI_SAS_IO_UNIT0_PHY_DATA
[1]'
[ 176.181174] CPU: 0 PID: 2102 Comm: (udev-worker) Not tainted
6.5.0-5-generic #5-Ubuntu
[ 176.181177] Hardware name: VMware, Inc. VMware20,1/440BX Desktop Reference
Platform, BIOS VMW201.00V.21805430.B64.2305221830 05/22/2023
[ 176.181179] Call Trace:
[ 176.181181]
[ 176.181183] dump_stack_lvl+0x48/0x70
[ 176.181228] dump_stack+0x10/0x20
[ 176.181232] __ubsan_handle_out_of_bounds+0xc6/0x110
[ 176.181236] mptsas_sas_io_unit_pg0+0x3b1/0x3f0 [mptsas]
[ 176.181248] mptsas_probe_hba_phys.isra.0+0x55/0x490 [mptsas]
[ 176.181257] ? __pfx_scsi_runtime_idle+0x10/0x10
[ 176.181264] ? rpm_idle+0x1dc/0x2b0
[ 176.181269] mptsas_scan_sas_topology+0x32/0x210 [mptsas]
[ 176.181277] ? scsi_autopm_put_host+0x1a/0x30
[ 176.181280] mptsas_probe.part.0+0x3cc/0x570 [mptsas]
[ 176.181289] mptsas_probe+0x1e/0x30 [mptsas]
[ 176.181298] local_pci_probe+0x44/0xb0
[ 176.181302] pci_call_probe+0x55/0x190
[ 176.181307] pci_device_probe+0x84/0x120
[ 176.181312] really_probe+0x1c4/0x410
[ 176.181316] __driver_probe_device+0x8c/0x180
[ 176.181320] driver_probe_device+0x24/0xd0
[ 176.181324] __driver_attach+0x10b/0x210
[ 176.181327] ? __pfx___driver_attach+0x10/0x10
[ 176.181330] bus_for_each_dev+0x8a/0xf0
[ 176.181333] driver_attach+0x1e/0x30
[ 176.181336] bus_add_driver+0x127/0x240
[ 176.181340] driver_register+0x5e/0x130
[ 176.181343] ? __pfx_mptsas_init+0x10/0x10 [mptsas]
[ 176.181352] __pci_register_driver+0x62/0x70
[ 176.181356] mptsas_init+0x119/0xff0 [mptsas]
[ 176.181365] do_one_initcall+0x5b/0x340
[ 176.181371] do_init_module+0x68/0x260
[ 176.181375] load_module+0xba1/0xcf0
[ 176.181380] ? vfree+0xff/0x2d0
[ 176.181385] init_module_from_file+0x96/0x100
[ 176.181388] ? init_module_from_file+0x96/0x100
[ 176.181394] idempotent_init_module+0x11c/0x2b0
[ 176.181399] __x64_sys_finit_module+0x64/0xd0
[ 176.181402] do_syscall_64+0x59/0x90
[ 176.181409] ? exit_to_user_mode_prepare+0x30/0xb0
[ 176.181413] ? syscall_exit_to_user_mode+0x37/0x60
[ 176.181417] ? do_syscall_64+0x68/0x90
[ 176.181421] ? syscall_exit_to_user_mode+0x37/0x60
[ 176.181424] ? do_syscall_64+0x68/0x90
[ 176.181428] entry_SYSCALL_64_after_hwframe+0x6e/0xd8
[ 176.181432] RIP: 0033:0x7f847a725c5d
[ 176.181441] Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 48 89
f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01
f0 ff ff 73 01 c3 48 8b 0d 8b 71 13 00 f7 d8 64 89 01 48
[ 176.181481] RSP: 002b:7fff6734e878 EFLAGS: 0246 ORIG_RAX:
0139
[ 176.181484] RAX: ffda RBX: 563ba212a6b0 RCX:
7f847a725c5d
[ 176.181486] RDX: 0004 RSI: 7f847aa0144a RDI:
000d
[ 176.181488] RBP: 7f847aa0144a R08: 0040 R09:
fde0
[ 176.181490] R10: fe18 R11: 0246 R12:
0002
[ 176.181526] R13: 563ba2216ae0 R14: R15:
563ba20dff90
[ 176.181531]
[ 176.181532]
---
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/seq:vmware 950 F pipewire
CRDA: N/A
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 23.10
InstallationDate: Installed on 2023-09-26 (0 days ago)
InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Beta amd64 (20230919.1)
IwConfig:
lono wireless extensions.
ens33 no wireless extensions.
Lsusb: Error: command ['lsusb'] failed with exit code 1:
Lsusb-t:
Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
Package: linux (not installed)
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
