[Kernel-packages] [Bug 2004110] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/2004110/+attachment/5644231/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2004110 Title: Wifi keeps failing with: Failed to run INIT ucode: -110 Status in linux package in Ubuntu: Confirmed Bug description: Quite a few people are complaining about this issue. For example: https://community.frame.work/t/solved-getting-wifi-working-on- ubuntu-22-04/25246. $ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 Something wrong with the iwlwifi firmware and/or driver? On boot it fails many (most?) times. When it does work, it seems to work correctly. Does not seem to be hardware issue. When it fails, on reboot no wifi option exists. When the wifi option does exist, starting and stopping airplane mode can sometime help. Worked with 20.0X ok. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-05-22 (619 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: HP HP ZBook Studio G5 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic root=UUID=ca099c7d-d066-43a9-a0ce-e030a37bf144 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-58-generic N/A linux-backports-modules-5.15.0-58-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.9 RfKill: 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: jammy Uname: Linux 5.15.0-58-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-09-28 (126 days ago) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 07/15/2019 dmi.bios.release: 8.0 dmi.bios.vendor: HP dmi.bios.version: Q71 Ver. 01.08.00 dmi.board.name: 8427 dmi.board.vendor: HP dmi.board.version: KBC Version 16.3A.00 dmi.chassis.asset.tag: 5CD842D0V6 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 22.58 dmi.modalias: dmi:bvnHP:bvrQ71Ver.01.08.00:bd07/15/2019:br8.0:efr22.58:svnHP:pnHPZBookStudioG5:pvr:rvnHP:rn8427:rvrKBCVersion16.3A.00:cvnHP:ct10:cvr:sku2YN56AV: dmi.product.family: 103C_5336AN HP ZBook Studio dmi.product.name: HP ZBook Studio G5 dmi.product.sku: 2YN56AV dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2004110/+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 2004110] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/2004110/+attachment/5644224/+files/PaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2004110 Title: Wifi keeps failing with: Failed to run INIT ucode: -110 Status in linux package in Ubuntu: Confirmed Bug description: Quite a few people are complaining about this issue. For example: https://community.frame.work/t/solved-getting-wifi-working-on- ubuntu-22-04/25246. $ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 Something wrong with the iwlwifi firmware and/or driver? On boot it fails many (most?) times. When it does work, it seems to work correctly. Does not seem to be hardware issue. When it fails, on reboot no wifi option exists. When the wifi option does exist, starting and stopping airplane mode can sometime help. Worked with 20.0X ok. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-05-22 (619 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: HP HP ZBook Studio G5 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic root=UUID=ca099c7d-d066-43a9-a0ce-e030a37bf144 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-58-generic N/A linux-backports-modules-5.15.0-58-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.9 RfKill: 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: jammy Uname: Linux 5.15.0-58-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-09-28 (126 days ago) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 07/15/2019 dmi.bios.release: 8.0 dmi.bios.vendor: HP dmi.bios.version: Q71 Ver. 01.08.00 dmi.board.name: 8427 dmi.board.vendor: HP dmi.board.version: KBC Version 16.3A.00 dmi.chassis.asset.tag: 5CD842D0V6 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 22.58 dmi.modalias: dmi:bvnHP:bvrQ71Ver.01.08.00:bd07/15/2019:br8.0:efr22.58:svnHP:pnHPZBookStudioG5:pvr:rvnHP:rn8427:rvrKBCVersion16.3A.00:cvnHP:ct10:cvr:sku2YN56AV: dmi.product.family: 103C_5336AN HP ZBook Studio dmi.product.name: HP ZBook Studio G5 dmi.product.sku: 2YN56AV dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2004110/+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 2004110] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/2004110/+attachment/5644232/+files/acpidump.txt ** Changed in: linux (Ubuntu) Status: Incomplete => 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/2004110 Title: Wifi keeps failing with: Failed to run INIT ucode: -110 Status in linux package in Ubuntu: Confirmed Bug description: Quite a few people are complaining about this issue. For example: https://community.frame.work/t/solved-getting-wifi-working-on- ubuntu-22-04/25246. $ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 Something wrong with the iwlwifi firmware and/or driver? On boot it fails many (most?) times. When it does work, it seems to work correctly. Does not seem to be hardware issue. When it fails, on reboot no wifi option exists. When the wifi option does exist, starting and stopping airplane mode can sometime help. Worked with 20.0X ok. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-05-22 (619 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: HP HP ZBook Studio G5 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic root=UUID=ca099c7d-d066-43a9-a0ce-e030a37bf144 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-58-generic N/A linux-backports-modules-5.15.0-58-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.9 RfKill: 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: jammy Uname: Linux 5.15.0-58-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-09-28 (126 days ago) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 07/15/2019 dmi.bios.release: 8.0 dmi.bios.vendor: HP dmi.bios.version: Q71 Ver. 01.08.00 dmi.board.name: 8427 dmi.board.vendor: HP dmi.board.version: KBC Version 16.3A.00 dmi.chassis.asset.tag: 5CD842D0V6 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 22.58 dmi.modalias: dmi:bvnHP:bvrQ71Ver.01.08.00:bd07/15/2019:br8.0:efr22.58:svnHP:pnHPZBookStudioG5:pvr:rvnHP:rn8427:rvrKBCVersion16.3A.00:cvnHP:ct10:cvr:sku2YN56AV: dmi.product.family: 103C_5336AN HP ZBook Studio dmi.product.name: HP ZBook Studio G5 dmi.product.sku: 2YN56AV dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2004110/+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 2004110] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/2004110/+attachment/5644222/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2004110 Title: Wifi keeps failing with: Failed to run INIT ucode: -110 Status in linux package in Ubuntu: Confirmed Bug description: Quite a few people are complaining about this issue. For example: https://community.frame.work/t/solved-getting-wifi-working-on- ubuntu-22-04/25246. $ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 Something wrong with the iwlwifi firmware and/or driver? On boot it fails many (most?) times. When it does work, it seems to work correctly. Does not seem to be hardware issue. When it fails, on reboot no wifi option exists. When the wifi option does exist, starting and stopping airplane mode can sometime help. Worked with 20.0X ok. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-05-22 (619 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: HP HP ZBook Studio G5 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic root=UUID=ca099c7d-d066-43a9-a0ce-e030a37bf144 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-58-generic N/A linux-backports-modules-5.15.0-58-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.9 RfKill: 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: jammy Uname: Linux 5.15.0-58-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-09-28 (126 days ago) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 07/15/2019 dmi.bios.release: 8.0 dmi.bios.vendor: HP dmi.bios.version: Q71 Ver. 01.08.00 dmi.board.name: 8427 dmi.board.vendor: HP dmi.board.version: KBC Version 16.3A.00 dmi.chassis.asset.tag: 5CD842D0V6 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 22.58 dmi.modalias: dmi:bvnHP:bvrQ71Ver.01.08.00:bd07/15/2019:br8.0:efr22.58:svnHP:pnHPZBookStudioG5:pvr:rvnHP:rn8427:rvrKBCVersion16.3A.00:cvnHP:ct10:cvr:sku2YN56AV: dmi.product.family: 103C_5336AN HP ZBook Studio dmi.product.name: HP ZBook Studio G5 dmi.product.sku: 2YN56AV dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2004110/+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 2004110] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/2004110/+attachment/5644230/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2004110 Title: Wifi keeps failing with: Failed to run INIT ucode: -110 Status in linux package in Ubuntu: Confirmed Bug description: Quite a few people are complaining about this issue. For example: https://community.frame.work/t/solved-getting-wifi-working-on- ubuntu-22-04/25246. $ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 Something wrong with the iwlwifi firmware and/or driver? On boot it fails many (most?) times. When it does work, it seems to work correctly. Does not seem to be hardware issue. When it fails, on reboot no wifi option exists. When the wifi option does exist, starting and stopping airplane mode can sometime help. Worked with 20.0X ok. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-05-22 (619 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: HP HP ZBook Studio G5 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic root=UUID=ca099c7d-d066-43a9-a0ce-e030a37bf144 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-58-generic N/A linux-backports-modules-5.15.0-58-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.9 RfKill: 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: jammy Uname: Linux 5.15.0-58-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-09-28 (126 days ago) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 07/15/2019 dmi.bios.release: 8.0 dmi.bios.vendor: HP dmi.bios.version: Q71 Ver. 01.08.00 dmi.board.name: 8427 dmi.board.vendor: HP dmi.board.version: KBC Version 16.3A.00 dmi.chassis.asset.tag: 5CD842D0V6 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 22.58 dmi.modalias: dmi:bvnHP:bvrQ71Ver.01.08.00:bd07/15/2019:br8.0:efr22.58:svnHP:pnHPZBookStudioG5:pvr:rvnHP:rn8427:rvrKBCVersion16.3A.00:cvnHP:ct10:cvr:sku2YN56AV: dmi.product.family: 103C_5336AN HP ZBook Studio dmi.product.name: HP ZBook Studio G5 dmi.product.sku: 2YN56AV dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2004110/+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 2004110] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/2004110/+attachment/5644229/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2004110 Title: Wifi keeps failing with: Failed to run INIT ucode: -110 Status in linux package in Ubuntu: Confirmed Bug description: Quite a few people are complaining about this issue. For example: https://community.frame.work/t/solved-getting-wifi-working-on- ubuntu-22-04/25246. $ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 Something wrong with the iwlwifi firmware and/or driver? On boot it fails many (most?) times. When it does work, it seems to work correctly. Does not seem to be hardware issue. When it fails, on reboot no wifi option exists. When the wifi option does exist, starting and stopping airplane mode can sometime help. Worked with 20.0X ok. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-05-22 (619 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: HP HP ZBook Studio G5 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic root=UUID=ca099c7d-d066-43a9-a0ce-e030a37bf144 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-58-generic N/A linux-backports-modules-5.15.0-58-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.9 RfKill: 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: jammy Uname: Linux 5.15.0-58-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-09-28 (126 days ago) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 07/15/2019 dmi.bios.release: 8.0 dmi.bios.vendor: HP dmi.bios.version: Q71 Ver. 01.08.00 dmi.board.name: 8427 dmi.board.vendor: HP dmi.board.version: KBC Version 16.3A.00 dmi.chassis.asset.tag: 5CD842D0V6 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 22.58 dmi.modalias: dmi:bvnHP:bvrQ71Ver.01.08.00:bd07/15/2019:br8.0:efr22.58:svnHP:pnHPZBookStudioG5:pvr:rvnHP:rn8427:rvrKBCVersion16.3A.00:cvnHP:ct10:cvr:sku2YN56AV: dmi.product.family: 103C_5336AN HP ZBook Studio dmi.product.name: HP ZBook Studio G5 dmi.product.sku: 2YN56AV dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2004110/+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 2004110] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/2004110/+attachment/5644228/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2004110 Title: Wifi keeps failing with: Failed to run INIT ucode: -110 Status in linux package in Ubuntu: Confirmed Bug description: Quite a few people are complaining about this issue. For example: https://community.frame.work/t/solved-getting-wifi-working-on- ubuntu-22-04/25246. $ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 Something wrong with the iwlwifi firmware and/or driver? On boot it fails many (most?) times. When it does work, it seems to work correctly. Does not seem to be hardware issue. When it fails, on reboot no wifi option exists. When the wifi option does exist, starting and stopping airplane mode can sometime help. Worked with 20.0X ok. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-05-22 (619 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: HP HP ZBook Studio G5 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic root=UUID=ca099c7d-d066-43a9-a0ce-e030a37bf144 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-58-generic N/A linux-backports-modules-5.15.0-58-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.9 RfKill: 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: jammy Uname: Linux 5.15.0-58-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-09-28 (126 days ago) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 07/15/2019 dmi.bios.release: 8.0 dmi.bios.vendor: HP dmi.bios.version: Q71 Ver. 01.08.00 dmi.board.name: 8427 dmi.board.vendor: HP dmi.board.version: KBC Version 16.3A.00 dmi.chassis.asset.tag: 5CD842D0V6 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 22.58 dmi.modalias: dmi:bvnHP:bvrQ71Ver.01.08.00:bd07/15/2019:br8.0:efr22.58:svnHP:pnHPZBookStudioG5:pvr:rvnHP:rn8427:rvrKBCVersion16.3A.00:cvnHP:ct10:cvr:sku2YN56AV: dmi.product.family: 103C_5336AN HP ZBook Studio dmi.product.name: HP ZBook Studio G5 dmi.product.sku: 2YN56AV dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2004110/+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 2004110] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/2004110/+attachment/5644227/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2004110 Title: Wifi keeps failing with: Failed to run INIT ucode: -110 Status in linux package in Ubuntu: Confirmed Bug description: Quite a few people are complaining about this issue. For example: https://community.frame.work/t/solved-getting-wifi-working-on- ubuntu-22-04/25246. $ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 Something wrong with the iwlwifi firmware and/or driver? On boot it fails many (most?) times. When it does work, it seems to work correctly. Does not seem to be hardware issue. When it fails, on reboot no wifi option exists. When the wifi option does exist, starting and stopping airplane mode can sometime help. Worked with 20.0X ok. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-05-22 (619 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: HP HP ZBook Studio G5 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic root=UUID=ca099c7d-d066-43a9-a0ce-e030a37bf144 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-58-generic N/A linux-backports-modules-5.15.0-58-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.9 RfKill: 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: jammy Uname: Linux 5.15.0-58-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-09-28 (126 days ago) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 07/15/2019 dmi.bios.release: 8.0 dmi.bios.vendor: HP dmi.bios.version: Q71 Ver. 01.08.00 dmi.board.name: 8427 dmi.board.vendor: HP dmi.board.version: KBC Version 16.3A.00 dmi.chassis.asset.tag: 5CD842D0V6 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 22.58 dmi.modalias: dmi:bvnHP:bvrQ71Ver.01.08.00:bd07/15/2019:br8.0:efr22.58:svnHP:pnHPZBookStudioG5:pvr:rvnHP:rn8427:rvrKBCVersion16.3A.00:cvnHP:ct10:cvr:sku2YN56AV: dmi.product.family: 103C_5336AN HP ZBook Studio dmi.product.name: HP ZBook Studio G5 dmi.product.sku: 2YN56AV dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2004110/+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 2004110] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/2004110/+attachment/5644225/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2004110 Title: Wifi keeps failing with: Failed to run INIT ucode: -110 Status in linux package in Ubuntu: Confirmed Bug description: Quite a few people are complaining about this issue. For example: https://community.frame.work/t/solved-getting-wifi-working-on- ubuntu-22-04/25246. $ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 Something wrong with the iwlwifi firmware and/or driver? On boot it fails many (most?) times. When it does work, it seems to work correctly. Does not seem to be hardware issue. When it fails, on reboot no wifi option exists. When the wifi option does exist, starting and stopping airplane mode can sometime help. Worked with 20.0X ok. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-05-22 (619 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: HP HP ZBook Studio G5 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic root=UUID=ca099c7d-d066-43a9-a0ce-e030a37bf144 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-58-generic N/A linux-backports-modules-5.15.0-58-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.9 RfKill: 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: jammy Uname: Linux 5.15.0-58-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-09-28 (126 days ago) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 07/15/2019 dmi.bios.release: 8.0 dmi.bios.vendor: HP dmi.bios.version: Q71 Ver. 01.08.00 dmi.board.name: 8427 dmi.board.vendor: HP dmi.board.version: KBC Version 16.3A.00 dmi.chassis.asset.tag: 5CD842D0V6 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 22.58 dmi.modalias: dmi:bvnHP:bvrQ71Ver.01.08.00:bd07/15/2019:br8.0:efr22.58:svnHP:pnHPZBookStudioG5:pvr:rvnHP:rn8427:rvrKBCVersion16.3A.00:cvnHP:ct10:cvr:sku2YN56AV: dmi.product.family: 103C_5336AN HP ZBook Studio dmi.product.name: HP ZBook Studio G5 dmi.product.sku: 2YN56AV dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2004110/+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 2004110] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/2004110/+attachment/5644226/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2004110 Title: Wifi keeps failing with: Failed to run INIT ucode: -110 Status in linux package in Ubuntu: Confirmed Bug description: Quite a few people are complaining about this issue. For example: https://community.frame.work/t/solved-getting-wifi-working-on- ubuntu-22-04/25246. $ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 Something wrong with the iwlwifi firmware and/or driver? On boot it fails many (most?) times. When it does work, it seems to work correctly. Does not seem to be hardware issue. When it fails, on reboot no wifi option exists. When the wifi option does exist, starting and stopping airplane mode can sometime help. Worked with 20.0X ok. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-05-22 (619 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: HP HP ZBook Studio G5 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic root=UUID=ca099c7d-d066-43a9-a0ce-e030a37bf144 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-58-generic N/A linux-backports-modules-5.15.0-58-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.9 RfKill: 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: jammy Uname: Linux 5.15.0-58-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-09-28 (126 days ago) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 07/15/2019 dmi.bios.release: 8.0 dmi.bios.vendor: HP dmi.bios.version: Q71 Ver. 01.08.00 dmi.board.name: 8427 dmi.board.vendor: HP dmi.board.version: KBC Version 16.3A.00 dmi.chassis.asset.tag: 5CD842D0V6 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 22.58 dmi.modalias: dmi:bvnHP:bvrQ71Ver.01.08.00:bd07/15/2019:br8.0:efr22.58:svnHP:pnHPZBookStudioG5:pvr:rvnHP:rn8427:rvrKBCVersion16.3A.00:cvnHP:ct10:cvr:sku2YN56AV: dmi.product.family: 103C_5336AN HP ZBook Studio dmi.product.name: HP ZBook Studio G5 dmi.product.sku: 2YN56AV dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2004110/+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 2004110] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/2004110/+attachment/5644223/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2004110 Title: Wifi keeps failing with: Failed to run INIT ucode: -110 Status in linux package in Ubuntu: Confirmed Bug description: Quite a few people are complaining about this issue. For example: https://community.frame.work/t/solved-getting-wifi-working-on- ubuntu-22-04/25246. $ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 Something wrong with the iwlwifi firmware and/or driver? On boot it fails many (most?) times. When it does work, it seems to work correctly. Does not seem to be hardware issue. When it fails, on reboot no wifi option exists. When the wifi option does exist, starting and stopping airplane mode can sometime help. Worked with 20.0X ok. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-05-22 (619 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: HP HP ZBook Studio G5 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic root=UUID=ca099c7d-d066-43a9-a0ce-e030a37bf144 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-58-generic N/A linux-backports-modules-5.15.0-58-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.9 RfKill: 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: jammy Uname: Linux 5.15.0-58-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-09-28 (126 days ago) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 07/15/2019 dmi.bios.release: 8.0 dmi.bios.vendor: HP dmi.bios.version: Q71 Ver. 01.08.00 dmi.board.name: 8427 dmi.board.vendor: HP dmi.board.version: KBC Version 16.3A.00 dmi.chassis.asset.tag: 5CD842D0V6 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 22.58 dmi.modalias: dmi:bvnHP:bvrQ71Ver.01.08.00:bd07/15/2019:br8.0:efr22.58:svnHP:pnHPZBookStudioG5:pvr:rvnHP:rn8427:rvrKBCVersion16.3A.00:cvnHP:ct10:cvr:sku2YN56AV: dmi.product.family: 103C_5336AN HP ZBook Studio dmi.product.name: HP ZBook Studio G5 dmi.product.sku: 2YN56AV dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2004110/+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 2004110] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/2004110/+attachment/5644221/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2004110 Title: Wifi keeps failing with: Failed to run INIT ucode: -110 Status in linux package in Ubuntu: Confirmed Bug description: Quite a few people are complaining about this issue. For example: https://community.frame.work/t/solved-getting-wifi-working-on- ubuntu-22-04/25246. $ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 Something wrong with the iwlwifi firmware and/or driver? On boot it fails many (most?) times. When it does work, it seems to work correctly. Does not seem to be hardware issue. When it fails, on reboot no wifi option exists. When the wifi option does exist, starting and stopping airplane mode can sometime help. Worked with 20.0X ok. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-05-22 (619 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: HP HP ZBook Studio G5 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic root=UUID=ca099c7d-d066-43a9-a0ce-e030a37bf144 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-58-generic N/A linux-backports-modules-5.15.0-58-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.9 RfKill: 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: jammy Uname: Linux 5.15.0-58-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-09-28 (126 days ago) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 07/15/2019 dmi.bios.release: 8.0 dmi.bios.vendor: HP dmi.bios.version: Q71 Ver. 01.08.00 dmi.board.name: 8427 dmi.board.vendor: HP dmi.board.version: KBC Version 16.3A.00 dmi.chassis.asset.tag: 5CD842D0V6 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 22.58 dmi.modalias: dmi:bvnHP:bvrQ71Ver.01.08.00:bd07/15/2019:br8.0:efr22.58:svnHP:pnHPZBookStudioG5:pvr:rvnHP:rn8427:rvrKBCVersion16.3A.00:cvnHP:ct10:cvr:sku2YN56AV: dmi.product.family: 103C_5336AN HP ZBook Studio dmi.product.name: HP ZBook Studio G5 dmi.product.sku: 2YN56AV dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2004110/+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 2004110] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/2004110/+attachment/5644219/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2004110 Title: Wifi keeps failing with: Failed to run INIT ucode: -110 Status in linux package in Ubuntu: Confirmed Bug description: Quite a few people are complaining about this issue. For example: https://community.frame.work/t/solved-getting-wifi-working-on- ubuntu-22-04/25246. $ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 Something wrong with the iwlwifi firmware and/or driver? On boot it fails many (most?) times. When it does work, it seems to work correctly. Does not seem to be hardware issue. When it fails, on reboot no wifi option exists. When the wifi option does exist, starting and stopping airplane mode can sometime help. Worked with 20.0X ok. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-05-22 (619 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: HP HP ZBook Studio G5 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic root=UUID=ca099c7d-d066-43a9-a0ce-e030a37bf144 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-58-generic N/A linux-backports-modules-5.15.0-58-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.9 RfKill: 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: jammy Uname: Linux 5.15.0-58-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-09-28 (126 days ago) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 07/15/2019 dmi.bios.release: 8.0 dmi.bios.vendor: HP dmi.bios.version: Q71 Ver. 01.08.00 dmi.board.name: 8427 dmi.board.vendor: HP dmi.board.version: KBC Version 16.3A.00 dmi.chassis.asset.tag: 5CD842D0V6 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 22.58 dmi.modalias: dmi:bvnHP:bvrQ71Ver.01.08.00:bd07/15/2019:br8.0:efr22.58:svnHP:pnHPZBookStudioG5:pvr:rvnHP:rn8427:rvrKBCVersion16.3A.00:cvnHP:ct10:cvr:sku2YN56AV: dmi.product.family: 103C_5336AN HP ZBook Studio dmi.product.name: HP ZBook Studio G5 dmi.product.sku: 2YN56AV dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2004110/+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 2004110] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/2004110/+attachment/5644218/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2004110 Title: Wifi keeps failing with: Failed to run INIT ucode: -110 Status in linux package in Ubuntu: Confirmed Bug description: Quite a few people are complaining about this issue. For example: https://community.frame.work/t/solved-getting-wifi-working-on- ubuntu-22-04/25246. $ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 Something wrong with the iwlwifi firmware and/or driver? On boot it fails many (most?) times. When it does work, it seems to work correctly. Does not seem to be hardware issue. When it fails, on reboot no wifi option exists. When the wifi option does exist, starting and stopping airplane mode can sometime help. Worked with 20.0X ok. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-05-22 (619 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: HP HP ZBook Studio G5 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic root=UUID=ca099c7d-d066-43a9-a0ce-e030a37bf144 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-58-generic N/A linux-backports-modules-5.15.0-58-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.9 RfKill: 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: jammy Uname: Linux 5.15.0-58-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-09-28 (126 days ago) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 07/15/2019 dmi.bios.release: 8.0 dmi.bios.vendor: HP dmi.bios.version: Q71 Ver. 01.08.00 dmi.board.name: 8427 dmi.board.vendor: HP dmi.board.version: KBC Version 16.3A.00 dmi.chassis.asset.tag: 5CD842D0V6 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 22.58 dmi.modalias: dmi:bvnHP:bvrQ71Ver.01.08.00:bd07/15/2019:br8.0:efr22.58:svnHP:pnHPZBookStudioG5:pvr:rvnHP:rn8427:rvrKBCVersion16.3A.00:cvnHP:ct10:cvr:sku2YN56AV: dmi.product.family: 103C_5336AN HP ZBook Studio dmi.product.name: HP ZBook Studio G5 dmi.product.sku: 2YN56AV dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2004110/+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 2004110] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/2004110/+attachment/5644220/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2004110 Title: Wifi keeps failing with: Failed to run INIT ucode: -110 Status in linux package in Ubuntu: Confirmed Bug description: Quite a few people are complaining about this issue. For example: https://community.frame.work/t/solved-getting-wifi-working-on- ubuntu-22-04/25246. $ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 Something wrong with the iwlwifi firmware and/or driver? On boot it fails many (most?) times. When it does work, it seems to work correctly. Does not seem to be hardware issue. When it fails, on reboot no wifi option exists. When the wifi option does exist, starting and stopping airplane mode can sometime help. Worked with 20.0X ok. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-05-22 (619 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: HP HP ZBook Studio G5 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic root=UUID=ca099c7d-d066-43a9-a0ce-e030a37bf144 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-58-generic N/A linux-backports-modules-5.15.0-58-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.9 RfKill: 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: jammy Uname: Linux 5.15.0-58-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-09-28 (126 days ago) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 07/15/2019 dmi.bios.release: 8.0 dmi.bios.vendor: HP dmi.bios.version: Q71 Ver. 01.08.00 dmi.board.name: 8427 dmi.board.vendor: HP dmi.board.version: KBC Version 16.3A.00 dmi.chassis.asset.tag: 5CD842D0V6 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 22.58 dmi.modalias: dmi:bvnHP:bvrQ71Ver.01.08.00:bd07/15/2019:br8.0:efr22.58:svnHP:pnHPZBookStudioG5:pvr:rvnHP:rn8427:rvrKBCVersion16.3A.00:cvnHP:ct10:cvr:sku2YN56AV: dmi.product.family: 103C_5336AN HP ZBook Studio dmi.product.name: HP ZBook Studio G5 dmi.product.sku: 2YN56AV dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2004110/+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 2004110] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/2004110/+attachment/5644217/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2004110 Title: Wifi keeps failing with: Failed to run INIT ucode: -110 Status in linux package in Ubuntu: Confirmed Bug description: Quite a few people are complaining about this issue. For example: https://community.frame.work/t/solved-getting-wifi-working-on- ubuntu-22-04/25246. $ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 Something wrong with the iwlwifi firmware and/or driver? On boot it fails many (most?) times. When it does work, it seems to work correctly. Does not seem to be hardware issue. When it fails, on reboot no wifi option exists. When the wifi option does exist, starting and stopping airplane mode can sometime help. Worked with 20.0X ok. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-05-22 (619 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: HP HP ZBook Studio G5 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic root=UUID=ca099c7d-d066-43a9-a0ce-e030a37bf144 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-58-generic N/A linux-backports-modules-5.15.0-58-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.9 RfKill: 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: jammy Uname: Linux 5.15.0-58-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-09-28 (126 days ago) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 07/15/2019 dmi.bios.release: 8.0 dmi.bios.vendor: HP dmi.bios.version: Q71 Ver. 01.08.00 dmi.board.name: 8427 dmi.board.vendor: HP dmi.board.version: KBC Version 16.3A.00 dmi.chassis.asset.tag: 5CD842D0V6 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 22.58 dmi.modalias: dmi:bvnHP:bvrQ71Ver.01.08.00:bd07/15/2019:br8.0:efr22.58:svnHP:pnHPZBookStudioG5:pvr:rvnHP:rn8427:rvrKBCVersion16.3A.00:cvnHP:ct10:cvr:sku2YN56AV: dmi.product.family: 103C_5336AN HP ZBook Studio dmi.product.name: HP ZBook Studio G5 dmi.product.sku: 2YN56AV dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2004110/+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 2004110] Re: Wifi keeps failing with: Failed to run INIT ucode: -110
apport information ** Tags added: apport-collected jammy ** Description changed: Quite a few people are complaining about this issue. For example: https://community.frame.work/t/solved-getting-wifi-working-on- ubuntu-22-04/25246. $ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 Something wrong with the iwlwifi firmware and/or driver? On boot it fails many (most?) times. When it does work, it seems to work correctly. Does not seem to be hardware issue. When it fails, on reboot no wifi option exists. When the wifi option does exist, starting and stopping airplane mode can sometime help. Worked with 20.0X ok. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu82.3 + Architecture: amd64 + CRDA: N/A + CasperMD5CheckResult: unknown + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 22.04 + InstallationDate: Installed on 2021-05-22 (619 days ago) + InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) + MachineType: HP HP ZBook Studio G5 + NonfreeKernelModules: nvidia_modeset nvidia + Package: linux (not installed) + ProcFB: 0 i915drmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic root=UUID=ca099c7d-d066-43a9-a0ce-e030a37bf144 ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 + PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. + RelatedPackageVersions: + linux-restricted-modules-5.15.0-58-generic N/A + linux-backports-modules-5.15.0-58-generic N/A + linux-firmware 20220329.git681281e4-0ubuntu3.9 + RfKill: + 1: phy0: Wireless LAN + Soft blocked: no + Hard blocked: no + Tags: jammy + Uname: Linux 5.15.0-58-generic x86_64 + UpgradeStatus: Upgraded to jammy on 2022-09-28 (126 days ago) + UserGroups: N/A + _MarkForUpload: True + dmi.bios.date: 07/15/2019 + dmi.bios.release: 8.0 + dmi.bios.vendor: HP + dmi.bios.version: Q71 Ver. 01.08.00 + dmi.board.name: 8427 + dmi.board.vendor: HP + dmi.board.version: KBC Version 16.3A.00 + dmi.chassis.asset.tag: 5CD842D0V6 + dmi.chassis.type: 10 + dmi.chassis.vendor: HP + dmi.ec.firmware.release: 22.58 + dmi.modalias: dmi:bvnHP:bvrQ71Ver.01.08.00:bd07/15/2019:br8.0:efr22.58:svnHP:pnHPZBookStudioG5:pvr:rvnHP:rn8427:rvrKBCVersion16.3A.00:cvnHP:ct10:cvr:sku2YN56AV: + dmi.product.family: 103C_5336AN HP ZBook Studio + dmi.product.name: HP ZBook Studio G5 + dmi.product.sku: 2YN56AV + dmi.sys.vendor: HP ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/2004110/+attachment/5644215/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2004110 Title: Wifi keeps failing with: Failed to run INIT ucode: -110 Status in linux package in Ubuntu: Confirmed Bug description: Quite a few people are complaining about this issue. For example: https://community.frame.work/t/solved-getting-wifi-working-on- ubuntu-22-04/25246. $ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 Something wrong with the iwlwifi firmware and/or driver? On boot it fails many (most?) times. When it does work, it seems to work correctly. Does not seem to be hardware issue. When it fails, on reboot no wifi option exists. When the wifi option does exist, starting and stopping airplane mode can sometime help. Worked with 20.0X ok. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-05-22 (619 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: HP HP ZBook Studio G5 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic root=UUID=ca099c7d-d066-43a9-a0ce-e030a37bf144 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-58-generic N/A linux-backports-modules-5.15.0-58-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.9 RfKill: 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: jammy Uname: Linux 5.15.0-58-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-09-28 (126 days ago) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 07/15/2019 dmi.bios.release: 8.0 dmi.bios.vendor: HP dmi.bios.version: Q71 Ver. 01.08.00 dmi.board.name: 8427 dmi.board.vendor: HP dmi.board.version:
[Kernel-packages] [Bug 2004110] AudioDevicesInUse.txt
apport information ** Attachment added: "AudioDevicesInUse.txt" https://bugs.launchpad.net/bugs/2004110/+attachment/5644216/+files/AudioDevicesInUse.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2004110 Title: Wifi keeps failing with: Failed to run INIT ucode: -110 Status in linux package in Ubuntu: Confirmed Bug description: Quite a few people are complaining about this issue. For example: https://community.frame.work/t/solved-getting-wifi-working-on- ubuntu-22-04/25246. $ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 Something wrong with the iwlwifi firmware and/or driver? On boot it fails many (most?) times. When it does work, it seems to work correctly. Does not seem to be hardware issue. When it fails, on reboot no wifi option exists. When the wifi option does exist, starting and stopping airplane mode can sometime help. Worked with 20.0X ok. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-05-22 (619 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: HP HP ZBook Studio G5 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic root=UUID=ca099c7d-d066-43a9-a0ce-e030a37bf144 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-58-generic N/A linux-backports-modules-5.15.0-58-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.9 RfKill: 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: jammy Uname: Linux 5.15.0-58-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-09-28 (126 days ago) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 07/15/2019 dmi.bios.release: 8.0 dmi.bios.vendor: HP dmi.bios.version: Q71 Ver. 01.08.00 dmi.board.name: 8427 dmi.board.vendor: HP dmi.board.version: KBC Version 16.3A.00 dmi.chassis.asset.tag: 5CD842D0V6 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 22.58 dmi.modalias: dmi:bvnHP:bvrQ71Ver.01.08.00:bd07/15/2019:br8.0:efr22.58:svnHP:pnHPZBookStudioG5:pvr:rvnHP:rn8427:rvrKBCVersion16.3A.00:cvnHP:ct10:cvr:sku2YN56AV: dmi.product.family: 103C_5336AN HP ZBook Studio dmi.product.name: HP ZBook Studio G5 dmi.product.sku: 2YN56AV dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2004110/+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 2004455] [NEW] package nvidia-dkms-525 525.78.01-0ubuntu0.22.04.1 failed to install/upgrade: installed nvidia-dkms-525 package post-installation script subprocess returned error
Public bug reported: Bug happend when I fully loged in to the system ProblemType: Package DistroRelease: Ubuntu 22.04 Package: nvidia-dkms-525 525.78.01-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue Jan 31 11:06:41 2023 ErrorMessage: installed nvidia-dkms-525 package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2023-01-26 (5 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 SourcePackage: nvidia-graphics-drivers-525 Title: package nvidia-dkms-525 525.78.01-0ubuntu0.22.04.1 failed to install/upgrade: installed nvidia-dkms-525 package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-525 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-525 in Ubuntu. https://bugs.launchpad.net/bugs/2004455 Title: package nvidia-dkms-525 525.78.01-0ubuntu0.22.04.1 failed to install/upgrade: installed nvidia-dkms-525 package post-installation script subprocess returned error exit status 1 Status in nvidia-graphics-drivers-525 package in Ubuntu: New Bug description: Bug happend when I fully loged in to the system ProblemType: Package DistroRelease: Ubuntu 22.04 Package: nvidia-dkms-525 525.78.01-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue Jan 31 11:06:41 2023 ErrorMessage: installed nvidia-dkms-525 package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2023-01-26 (5 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 SourcePackage: nvidia-graphics-drivers-525 Title: package nvidia-dkms-525 525.78.01-0ubuntu0.22.04.1 failed to install/upgrade: installed nvidia-dkms-525 package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-525/+bug/2004455/+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 1786013] Autopkgtest regression report (linux-restricted-modules-aws-5.19/5.19.0-1019.20~22.04.1)
All autopkgtests for the newly accepted linux-restricted-modules-aws-5.19 (5.19.0-1019.20~22.04.1) for jammy have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-525/525.78.01-0ubuntu0.22.04.1 (arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#linux-restricted-modules-aws-5.19 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+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 1883493] Re: amdgpu hangs from time to time with *ERROR* Waiting for fences timed out!
** Also affects: linux via https://gitlab.freedesktop.org/drm/amd/-/issues/1318 Importance: Unknown Status: Unknown -- 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/1883493 Title: amdgpu hangs from time to time with *ERROR* Waiting for fences timed out! Status in Linux: Unknown Status in linux package in Ubuntu: Invalid Bug description: un 15 08:30:42 alhazen kernel: [ 1566.155810] [drm:amdgpu_dm_commit_planes.constprop.0 [amdgpu]] *ERROR* Waiting for fences timed out! Jun 15 08:30:47 alhazen kernel: [ 1566.159792] [drm:amdgpu_dm_commit_planes.constprop.0 [amdgpu]] *ERROR* Waiting for fences timed out! Jun 15 08:30:47 alhazen kernel: [ 1571.020144] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, signaled seq=535493, emitted seq=535495 Jun 15 08:30:47 alhazen kernel: [ 1571.020216] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Xorg pid 3664 thread Xorg:cs0 pid 3694 Jun 15 08:30:47 alhazen kernel: [ 1571.020218] [drm] GPU recovery disabled. Mouse pointer still moves, but apart from that the display is frozen. Music keeps playing. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-37-generic 5.4.0-37.41 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jun 15 09:09:56 2020 InstallationDate: Installed on 2020-05-28 (17 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: enp4s0no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-37-generic root=/dev/mapper/vgubuntu-root ro quiet splash acpi-enforce-resources=lax vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-37-generic N/A linux-backports-modules-5.4.0-37-generic N/A linux-firmware1.187 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0604 dmi.board.asset.tag: Default string dmi.board.name: PRIME X570-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0604:bd07/02/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX570-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1883493/+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 1992266] Re: input/keyboard: the keyboard on some Asus laptops can't work
** Tags removed: verification-needed-focal verification-needed-jammy ** Tags added: verification-done-focal verification-done-jammy -- 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/1992266 Title: input/keyboard: the keyboard on some Asus laptops can't work Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Bug description: This is upstream tracking bug: https://bugzilla.kernel.org/show_bug.cgi?id=216158 The bug originates from an upstream bug, and the ubuntu users request me to do a SRU to make the ubuntu linux work on their Asus laptops, so once the pathces are merge to mainline kernel, I start to prepare this SRU. [Impact] Some Asus laptops config the IRQ of keyboard in the BIOS, but kernel will override to a new configuration for that IRQ, this will make the keyboard not work anymore under linux. [Fix] Backport 2 patches from mainlie kernel to fix this problem. [Test] boot the patched kernel on the machine, test the keyboard, all regular keys could work. [Where problems could occur] The patches use the dmi table to match the machines, so only the matched Asus laptops will be impacted by the patches, if there is any regression, the regression only affects those matched Asus laptops, and the regression possibility is very low since ubuntu users already tested the patches on their own Asus laptops. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992266/+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 2004262] Re: Intel E810 NICs driver in causing hangs when booting and bonds configured
** Description changed: jammy 22.04.1 linux-image-generic 5.15.0-58-generic Intel E810-XXV Dual Port NICs in Dell PowerEdge 650 - After beonding is enabled on switch and server side, the system will - hang at initialing ubuntu. The kernel loads but around starting the - Network Services the system can hang for sometimes 5 minutes, and in - other cases, indefinitely. + - 5.15 in jammy -> reproducible + - 5.19 in hwe-edge -> reproducible + - 6.2.rc6 in the mainline build -> works + - Intel's ice driver 1.10.1.2.2 -> works + + + After beonding is enabled on switch and server side, the system will hang at initialing ubuntu. The kernel loads but around starting the Network Services the system can hang for sometimes 5 minutes, and in other cases, indefinitely. The message of: echo 0 > /proc/sys/kernel/hung_task_timeout_sec” systemd-resolve blocked for more than 120 seconds appears, and eventually the Network services just attempts to start and never does. This is with or without DHCP enabled. Tried this same setup with the hwe-22.04, hwe-20.04, hwe-22.04-ege and linux-oem kernels and all exhibit the same failure. To work around this. installing the Intel 'ice' driver of version 1.10.1.2.2 works. The system doesn't even remotely hang at startup and all networking functions remain working (ping, DNS, general accessibility). The driver can be found at https://downloadmirror.intel.com/763930/ice-1.10.1.2.2.tar.gz - --- + --- ProblemType: Bug AlsaDevices: - total 0 - crw-rw 1 root audio 116, 1 Jan 31 13:08 seq - crw-rw 1 root audio 116, 33 Jan 31 13:08 timer + total 0 + crw-rw 1 root audio 116, 1 Jan 31 13:08 seq + crw-rw 1 root audio 116, 33 Jan 31 13:08 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5json: - { -"result": "skip" - } - DistroRelease: Ubuntu 22.04 - InstallationDate: Installed on 2023-01-27 (3 days ago) - InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809) + { + "result": "skip" + }DistroRelease: Ubuntu 22.04 + InstallationDate: Installed on 2023-01-27 (3 days ago)InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Dell Inc. PowerEdge R650 Package: linux (not installed) PciMultimedia: - + ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic root=UUID=668aab7c-abe9-434b-a810-acc6eab76cbc ro fsck.mode=skip ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 RelatedPackageVersions: - linux-restricted-modules-5.15.0-58-generic N/A - linux-backports-modules-5.15.0-58-generic N/A - linux-firmware 20220329.git681281e4-0ubuntu3.9 - RfKill: Error: [Errno 2] No such file or directory: 'rfkill' - Tags: jammy uec-images + linux-restricted-modules-5.15.0-58-generic N/A + linux-backports-modules-5.15.0-58-generic N/A + linux-firmware 20220329.git681281e4-0ubuntu3.9 + RfKill: Error: [Errno 2] No such file or directory: 'rfkill'Tags: jammy uec-images Uname: Linux 5.15.0-58-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 09/14/2022 dmi.bios.release: 1.8 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.2 dmi.board.name: 0PJ7YJ dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.2:bd09/14/2022:br1.8:svnDellInc.:pnPowerEdgeR650:pvr:rvnDellInc.:rn0PJ7YJ:rvrA01:cvnDellInc.:ct23:cvr:skuSKU=0912;ModelName=PowerEdgeR650: dmi.product.family: PowerEdge dmi.product.name: PowerEdge R650 dmi.product.sku: SKU=0912;ModelName=PowerEdge R650 dmi.sys.vendor: Dell Inc. -- 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/2004262 Title: Intel E810 NICs driver in causing hangs when booting and bonds configured Status in linux package in Ubuntu: Incomplete Bug description: jammy 22.04.1 linux-image-generic 5.15.0-58-generic Intel E810-XXV Dual Port NICs in Dell PowerEdge 650 - 5.15 in jammy -> reproducible - 5.19 in hwe-edge -> reproducible - 6.2.rc6 in the mainline build -> works - Intel's ice driver 1.10.1.2.2 -> works After beonding is enabled on switch and server side, the system will hang at initialing ubuntu. The kernel loads but around starting the Network Services the system can hang for sometimes 5 minutes, and in other cases,
[Kernel-packages] [Bug 2004262] Re: Intel E810 NICs driver in causing hangs when booting and bonds configured
https://lore.kernel.org/netdev/20230131213703.1347761-2-anthony.l.ngu...@intel.com/T/#u A possible fix for this problem. The patch was posted on intel-wired- lan a couple weeks ago and just hit netdev today. -- 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/2004262 Title: Intel E810 NICs driver in causing hangs when booting and bonds configured Status in linux package in Ubuntu: Incomplete Bug description: jammy 22.04.1 linux-image-generic 5.15.0-58-generic Intel E810-XXV Dual Port NICs in Dell PowerEdge 650 After beonding is enabled on switch and server side, the system will hang at initialing ubuntu. The kernel loads but around starting the Network Services the system can hang for sometimes 5 minutes, and in other cases, indefinitely. The message of: echo 0 > /proc/sys/kernel/hung_task_timeout_sec” systemd-resolve blocked for more than 120 seconds appears, and eventually the Network services just attempts to start and never does. This is with or without DHCP enabled. Tried this same setup with the hwe-22.04, hwe-20.04, hwe-22.04-ege and linux-oem kernels and all exhibit the same failure. To work around this. installing the Intel 'ice' driver of version 1.10.1.2.2 works. The system doesn't even remotely hang at startup and all networking functions remain working (ping, DNS, general accessibility). The driver can be found at https://downloadmirror.intel.com/763930/ice-1.10.1.2.2.tar.gz --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 31 13:08 seq crw-rw 1 root audio 116, 33 Jan 31 13:08 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5json: { "result": "skip" } DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-01-27 (3 days ago) InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Dell Inc. PowerEdge R650 Package: linux (not installed) PciMultimedia: ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic root=UUID=668aab7c-abe9-434b-a810-acc6eab76cbc ro fsck.mode=skip ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 RelatedPackageVersions: linux-restricted-modules-5.15.0-58-generic N/A linux-backports-modules-5.15.0-58-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.9 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: jammy uec-images Uname: Linux 5.15.0-58-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 09/14/2022 dmi.bios.release: 1.8 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.2 dmi.board.name: 0PJ7YJ dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.2:bd09/14/2022:br1.8:svnDellInc.:pnPowerEdgeR650:pvr:rvnDellInc.:rn0PJ7YJ:rvrA01:cvnDellInc.:ct23:cvr:skuSKU=0912;ModelName=PowerEdgeR650: dmi.product.family: PowerEdge dmi.product.name: PowerEdge R650 dmi.product.sku: SKU=0912;ModelName=PowerEdge R650 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2004262/+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 1988797] Re: pcieport 0000:00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID)
This bug is awaiting verification that the linux-lowlatency- hwe-5.19/5.19.0-1017.18~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. 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! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1988797 Title: pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected (Non- Fatal), type=Transaction Layer, (Requester ID) Status in HWE Next: Fix Released Status in OEM Priority Project: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-5.14 source package in Kinetic: Invalid Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: My kernel log periodically bursts with: [10405.588287] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) [10405.593393] pcieport :00:1b.0: device [8086:7ac4] error status/mask=0010/4000 [10405.598564] pcieport :00:1b.0:[20] UnsupReq (First) [10405.603829] pcieport :00:1b.0: AER: TLP Header: 3400 0152 [10405.609563] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) [10405.614959] pcieport :00:1b.0: device [8086:7ac4] error status/mask=0010/4000 [10405.620296] pcieport :00:1b.0:[20] UnsupReq (First) [10405.625554] pcieport :00:1b.0: AER: TLP Header: 3400 0152 [10405.631180] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) [10405.636495] pcieport :00:1b.0: device [8086:7ac4] error status/mask=0010/4000 [10405.641867] pcieport :00:1b.0:[20] UnsupReq (First) [10405.647169] pcieport :00:1b.0: AER: TLP Header: 3400 0152 [10405.652919] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) [10405.658369] pcieport :00:1b.0: device [8086:7ac4] error status/mask=0010/4000 [10405.663803] pcieport :00:1b.0:[20] UnsupReq (First) [10405.669263] pcieport :00:1b.0: AER: TLP Header: 3400 0152 [10405.675130] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) [10405.680699] pcieport :00:1b.0: device [8086:7ac4] error status/mask=0010/4000 [10405.686267] pcieport :00:1b.0:[20] UnsupReq (First) [10405.691759] pcieport :00:1b.0: AER: TLP Header: 3400 0152 This has happened even since I got the machine. It also happened with 5.15. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-15-generic 5.19.0-15.15 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dan2477 F wireplumber /dev/snd/seq:dan2474 F pipewire CRDA: N/A CasperMD5CheckResult: pass Date: Tue Sep 6 13:52:35 2022 InstallationDate: Installed on 2022-07-20 (47 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220718) MachineType: Intel(R) Client Systems NUC12DCMi7 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-15-generic root=UUID=a69020a6-a1dd-436c-b75a-be890a4063be ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.19.0-15-generic N/A linux-backports-modules-5.19.0-15-generic N/A
[Kernel-packages] [Bug 1988797] Re: pcieport 0000:00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID)
This bug is awaiting verification that the linux-lowlatency- hwe-5.19/5.19.0-1017.18~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-lowlatency-hwe-5.19 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1988797 Title: pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected (Non- Fatal), type=Transaction Layer, (Requester ID) Status in HWE Next: Fix Released Status in OEM Priority Project: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-5.14 source package in Kinetic: Invalid Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: My kernel log periodically bursts with: [10405.588287] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) [10405.593393] pcieport :00:1b.0: device [8086:7ac4] error status/mask=0010/4000 [10405.598564] pcieport :00:1b.0:[20] UnsupReq (First) [10405.603829] pcieport :00:1b.0: AER: TLP Header: 3400 0152 [10405.609563] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) [10405.614959] pcieport :00:1b.0: device [8086:7ac4] error status/mask=0010/4000 [10405.620296] pcieport :00:1b.0:[20] UnsupReq (First) [10405.625554] pcieport :00:1b.0: AER: TLP Header: 3400 0152 [10405.631180] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) [10405.636495] pcieport :00:1b.0: device [8086:7ac4] error status/mask=0010/4000 [10405.641867] pcieport :00:1b.0:[20] UnsupReq (First) [10405.647169] pcieport :00:1b.0: AER: TLP Header: 3400 0152 [10405.652919] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) [10405.658369] pcieport :00:1b.0: device [8086:7ac4] error status/mask=0010/4000 [10405.663803] pcieport :00:1b.0:[20] UnsupReq (First) [10405.669263] pcieport :00:1b.0: AER: TLP Header: 3400 0152 [10405.675130] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) [10405.680699] pcieport :00:1b.0: device [8086:7ac4] error status/mask=0010/4000 [10405.686267] pcieport :00:1b.0:[20] UnsupReq (First) [10405.691759] pcieport :00:1b.0: AER: TLP Header: 3400 0152 This has happened even since I got the machine. It also happened with 5.15. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-15-generic 5.19.0-15.15 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dan2477 F wireplumber /dev/snd/seq:dan2474 F pipewire CRDA: N/A CasperMD5CheckResult: pass Date: Tue Sep 6 13:52:35 2022 InstallationDate: Installed on 2022-07-20 (47 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220718) MachineType: Intel(R) Client Systems NUC12DCMi7 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-15-generic root=UUID=a69020a6-a1dd-436c-b75a-be890a4063be ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.19.0-15-generic N/A
[Kernel-packages] [Bug 1988711] Re: Update Broadcom Emulex FC HBA lpfc driver to 14.2.0.5 for Ubuntu 22.04
This bug is awaiting verification that the linux- aws-5.19/5.19.0-1019.20~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-aws-5.19 verification-needed-jammy -- 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/1988711 Title: Update Broadcom Emulex FC HBA lpfc driver to 14.2.0.5 for Ubuntu 22.04 Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: In Progress Status in linux source package in Kinetic: Fix Released Bug description: [IMPACT/Justification] There are numerous bug fixes included in the more recent version of lpfc That Broadcom has asked to pull into Jammy and Kinetic to better support customers in the field who are using the GA kernel and cant or wont move to the HWE kernels. These all are limited to the lpfc driver itself, no patches to core code are requested. [FIX] A few of these were already landed in Jammy, and all but 6 (ones landed in 6.0 upstream) were already in Kinetic. b3d11f195cbb scsi: lpfc: Copyright updates for 14.2.0.5 patches 71faf8d30fdb scsi: lpfc: Update lpfc version to 14.2.0.5 b21c9deb1479 scsi: lpfc: Refactor lpfc_nvmet_prep_abort_wqe() into lpfc_sli_prep_abort_xri() ffc566411ade scsi: lpfc: Revert RSCN_MEMENTO workaround for misbehaved configuration ea92e173dc55 scsi: lpfc: Fix lost NVMe paths during LIF bounce stress test 2f67dc7970bc scsi: lpfc: Fix possible memory leak when failing to issue CMF WQE 0948a9c53860 scsi: lpfc: Remove extra atomic_inc on cmd_pending in queuecommand after VMID 35251b4d79db scsi: lpfc: Set PU field when providing D_ID in XMIT_ELS_RSP64_CX iocb f8191d40aa61 scsi: lpfc: Prevent buffer overflow crashes in debugfs with malformed user input 4ecc9b0271a7 scsi: lpfc: Fix uninitialized cqe field in lpfc_nvme_cancel_iocb() 1af48fffd7ff scsi: lpfc: Update lpfc version to 14.2.0.4 2e7e9c0c1ec0 scsi: lpfc: Allow reduced polling rate for nvme_admin_async_event cmd completion ea7bd1f39331 scsi: lpfc: Add more logging of cmd and cqe information for aborted NVMe cmds 336d63615466 scsi: lpfc: Fix port stuck in bypassed state after LIP in PT2PT topology b1b3440f437b scsi: lpfc: Resolve NULL ptr dereference after an ELS LOGO is aborted 6f808bd78e82 scsi: lpfc: Address NULL pointer dereference after starget_to_rport() e27f05147bff scsi: lpfc: Resolve some cleanup issues following SLI path refactoring 24e1f056677e scsi: lpfc: Resolve some cleanup issues following abort path refactoring 44ba9786b673 scsi: lpfc: Correct BDE type for XMIT_SEQ64_WQE in lpfc_ct_reject_event() a5b168efba21 scsi: lpfc: Add support for ATTO Fibre Channel devices 348efeca7487 scsi: lpfc: Rework lpfc_vmid_get_appid() to be protocol independent ed913cf4a533 scsi: lpfc: Commonize VMID code location fcb9e738667c scsi: lpfc: Update lpfc version to 14.2.0.3 a14396b6d139 scsi: lpfc: Use sg_dma_address() and sg_dma_len() macros for NVMe I/O e6f510414502 scsi: lpfc: Alter FPIN stat accounting logic de3ec318fee3 scsi: lpfc: Rework FDMI initialization after link up 5099478e436f scsi: lpfc: Change VMID registration to be based on fabric parameters dc8a71bd414f scsi: lpfc: Decrement outstanding gidft_inp counter if lpfc_err_lost_link() 4a0f4aff3ce5 scsi: lpfc: Use list_for_each_entry_safe() in rscn_recovery_check() 596fc8adb171 scsi: lpfc: Fix dmabuf ptr assignment in lpfc_ct_reject_event() ead76d4c09b8 scsi: lpfc: Inhibit aborts if external loopback plug is inserted b7e952cbc63c scsi: lpfc: Fix ndlp put following a LOGO completion ba3d58a1df46 scsi: lpfc: Fill in missing ndlp kref puts in error paths 84c6f99e3907 scsi: lpfc: Fix element offset in __lpfc_sli_release_iocbq_s4() 775266207105 scsi: lpfc: Correct BDE DMA address assignment for GEN_REQ_WQE cc28fac16ab7 scsi: lpfc: Fix split code for FLOGI on FCoE c2024e3b33ee scsi: lpfc: Remove redundant lpfc_sli_prep_wqe() call 92bd903da12b scsi: lpfc: Fix additional reference counting in lpfc_bsg_rport_els() db05628435aa blk-cgroup: move blkcg_{get,set}_fc_appid out of line 646db1a560f4 scsi: lpfc: Fix resource leak in lpfc_sli4_send_seq_to_ulp() 3d1d34ec1fbc scsi: lpfc: Remove unnecessary null ndlp check in lpfc_sli_prep_wqe() a346f28ad231 scsi: lpfc: Remove unneeded variable 66c20a97367a scsi: lpfc: Copyright updates for 14.2.0.2
[Kernel-packages] [Bug 1988797] Re: pcieport 0000:00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID)
This bug is awaiting verification that the linux- aws-5.19/5.19.0-1019.20~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-aws-5.19 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1988797 Title: pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected (Non- Fatal), type=Transaction Layer, (Requester ID) Status in HWE Next: Fix Released Status in OEM Priority Project: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-5.14 source package in Kinetic: Invalid Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: My kernel log periodically bursts with: [10405.588287] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) [10405.593393] pcieport :00:1b.0: device [8086:7ac4] error status/mask=0010/4000 [10405.598564] pcieport :00:1b.0:[20] UnsupReq (First) [10405.603829] pcieport :00:1b.0: AER: TLP Header: 3400 0152 [10405.609563] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) [10405.614959] pcieport :00:1b.0: device [8086:7ac4] error status/mask=0010/4000 [10405.620296] pcieport :00:1b.0:[20] UnsupReq (First) [10405.625554] pcieport :00:1b.0: AER: TLP Header: 3400 0152 [10405.631180] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) [10405.636495] pcieport :00:1b.0: device [8086:7ac4] error status/mask=0010/4000 [10405.641867] pcieport :00:1b.0:[20] UnsupReq (First) [10405.647169] pcieport :00:1b.0: AER: TLP Header: 3400 0152 [10405.652919] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) [10405.658369] pcieport :00:1b.0: device [8086:7ac4] error status/mask=0010/4000 [10405.663803] pcieport :00:1b.0:[20] UnsupReq (First) [10405.669263] pcieport :00:1b.0: AER: TLP Header: 3400 0152 [10405.675130] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) [10405.680699] pcieport :00:1b.0: device [8086:7ac4] error status/mask=0010/4000 [10405.686267] pcieport :00:1b.0:[20] UnsupReq (First) [10405.691759] pcieport :00:1b.0: AER: TLP Header: 3400 0152 This has happened even since I got the machine. It also happened with 5.15. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-15-generic 5.19.0-15.15 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dan2477 F wireplumber /dev/snd/seq:dan2474 F pipewire CRDA: N/A CasperMD5CheckResult: pass Date: Tue Sep 6 13:52:35 2022 InstallationDate: Installed on 2022-07-20 (47 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220718) MachineType: Intel(R) Client Systems NUC12DCMi7 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-15-generic root=UUID=a69020a6-a1dd-436c-b75a-be890a4063be ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.19.0-15-generic N/A
[Kernel-packages] [Bug 1989334] Re: remove circular dep between linux-image and modules
This bug is awaiting verification that the linux-lowlatency- hwe-5.19/5.19.0-1017.18~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-lowlatency-hwe-5.19 verification-needed-jammy -- 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/1989334 Title: remove circular dep between linux-image and modules Status in linux package in Ubuntu: Expired Bug description: remove circular dep between linux-image and modules Currently we have circular dependencies between linux-image and linux- modules/linux-modules-extra packages. This is redundant, and harmful when additional types of linux-images are provided (i.e. kernel.efi). Break the circular dependency by only keeping linux-image -> linux- modules dep, remove linux-modules -> linux-image dep, remove linux- modules-extra -> linux-image dep, add linux-modules-extra -> linux- modules dep. this is now applied in kinetic:linux, next need to apply to this to derivative kernels, and then we can roll it out to jammy too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1989334/+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 1990700] Re: Fibocom WWAN FM350-GL suspend error (notebook not suspend)
This bug is awaiting verification that the linux-lowlatency- hwe-5.19/5.19.0-1017.18~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-lowlatency-hwe-5.19 -- 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/1990700 Title: Fibocom WWAN FM350-GL suspend error (notebook not suspend) Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux source package in Lunar: Fix Released Status in linux-oem-6.0 source package in Lunar: Invalid Bug description: [SRU Justification] [Impact] Fibocom WWAN FM350-GL equipped platform fails to suspend. [Fix] Full t7xx driver is still under development and some of them have already accepted and merged in mainline kernel. The following commits are once in the mainline and are reverted in v6.0: d20ef656f994 net: wwan: t7xx: Add AP CLDMA 007f26f0d68e net: wwan: t7xx: Infrastructure for early port configuration 140424d90165 net: wwan: t7xx: PCIe reset rescan 87dae9e70bf7 net: wwan: t7xx: Enable devlink based fw flashing and coredump collection The first patch implemented the other AP-CLDMA, and with that applied, platforms in question may suspend and resume normally as every bits are in position. However, while these patches had been reverted for another revision that is still being worked on by the hardware vendor, a minimum, sauced patch is created to work-around this first to meet project schedules, and will be reverted and superseded with a final, mainline landing revision. [Test Case] Trigger suspend and there should be no more suspend errors from t7xx: mtk_t7xx :58:00.0: [PM] SAP suspend error: -110 mtk_t7xx :58:00.0: PM: pci_pm_suspend(): t7xx_pci_pm_suspend+0x0/0x20 [mtk_t7xx] returns -110 mtk_t7xx :58:00.0: PM: dpm_run_callback(): pci_pm_suspend+0x0/0x1a0 returns -110 mtk_t7xx :58:00.0: PM: failed to suspend async: error -110 [Where problems could occur] The t7xx driver is still incomplete and we're staging aforementioned 4 patches in internal experimental kernels for development use. [Other Info] This affects Kinetic and above, so only Unstable, Kinetic and OEM-6.0 are nominated for fix. == original bug report == Hi, I found a "little" problem with Fibocom WWAN FM350-GL 5G modem in module mtk_t7xx . Power management for this modem is bad. When the notebook goes to sleep/suspend, kernel module mtk_t7xx return an error: mtk_t7xx :58:00.0: [PM] SAP suspend error: -110 mtk_t7xx :58:00.0: PM: pci_pm_suspend(): t7xx_pci_pm_suspend+0x0/0x20 [mtk_t7xx] returns -110 mtk_t7xx :58:00.0: PM: dpm_run_callback(): pci_pm_suspend+0x0/0x1a0 returns -110 mtk_t7xx :58:00.0: PM: failed to suspend async: error -110 So power management failed to suspend: PM: Some devices failed to suspend, or early wake event detected And the notebook not suspend and wake up again. It must be this module, because if I remove the module first (modprobe -r), the laptop goes to sleep and wakes up normally. However, after reinserting the module, the modem no longer appears in the system. Expected state: sleep occurs when the device is put to sleep - including the modem. When you wake up, you will wake up, including activating the modem and logging into the operator's network. Description:Ubuntu 20.04.5 LTS Release:20.04 lspci -v: 58:00.0 Wireless controller [0d40]: MEDIATEK Corp. Device 4d75 (rev 01) Subsystem: Device 1cf8:3500 Flags: bus master, fast devsel, latency 0, IRQ 17 Memory at 601e80 (64-bit, prefetchable) [size=32K] Memory at 5e80 (64-bit, non-prefetchable) [size=8M] Memory at 601e00 (64-bit, prefetchable) [size=8M] Capabilities: [80] Express Endpoint, MSI 00 Capabilities: [d0] MSI-X: Enable+ Count=34 Masked- Capabilities: [e0] MSI: Enable- Count=1/32 Maskable+ 64bit+ Capabilities: [f8] Power
[Kernel-packages] [Bug 1883493] Re: amdgpu hangs from time to time with *ERROR* Waiting for fences timed out!
Changing status belatedly to invalid. Upstream the issue was diagnosed as insufficient voltage supplied to the SoC, and was worked around by increasing SoC voltage in BIOS. ** Changed in: linux (Ubuntu) Status: Incomplete => 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/1883493 Title: amdgpu hangs from time to time with *ERROR* Waiting for fences timed out! Status in linux package in Ubuntu: Invalid Bug description: un 15 08:30:42 alhazen kernel: [ 1566.155810] [drm:amdgpu_dm_commit_planes.constprop.0 [amdgpu]] *ERROR* Waiting for fences timed out! Jun 15 08:30:47 alhazen kernel: [ 1566.159792] [drm:amdgpu_dm_commit_planes.constprop.0 [amdgpu]] *ERROR* Waiting for fences timed out! Jun 15 08:30:47 alhazen kernel: [ 1571.020144] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, signaled seq=535493, emitted seq=535495 Jun 15 08:30:47 alhazen kernel: [ 1571.020216] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Xorg pid 3664 thread Xorg:cs0 pid 3694 Jun 15 08:30:47 alhazen kernel: [ 1571.020218] [drm] GPU recovery disabled. Mouse pointer still moves, but apart from that the display is frozen. Music keeps playing. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-37-generic 5.4.0-37.41 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jun 15 09:09:56 2020 InstallationDate: Installed on 2020-05-28 (17 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: enp4s0no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-37-generic root=/dev/mapper/vgubuntu-root ro quiet splash acpi-enforce-resources=lax vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-37-generic N/A linux-backports-modules-5.4.0-37-generic N/A linux-firmware1.187 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0604 dmi.board.asset.tag: Default string dmi.board.name: PRIME X570-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0604:bd07/02/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX570-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883493/+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 1990700] Re: Fibocom WWAN FM350-GL suspend error (notebook not suspend)
This bug is awaiting verification that the linux- aws-5.19/5.19.0-1019.20~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags removed: verification-done-jammy ** Tags added: kernel-spammed-jammy-linux-aws-5.19 verification-needed-jammy -- 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/1990700 Title: Fibocom WWAN FM350-GL suspend error (notebook not suspend) Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux source package in Lunar: Fix Released Status in linux-oem-6.0 source package in Lunar: Invalid Bug description: [SRU Justification] [Impact] Fibocom WWAN FM350-GL equipped platform fails to suspend. [Fix] Full t7xx driver is still under development and some of them have already accepted and merged in mainline kernel. The following commits are once in the mainline and are reverted in v6.0: d20ef656f994 net: wwan: t7xx: Add AP CLDMA 007f26f0d68e net: wwan: t7xx: Infrastructure for early port configuration 140424d90165 net: wwan: t7xx: PCIe reset rescan 87dae9e70bf7 net: wwan: t7xx: Enable devlink based fw flashing and coredump collection The first patch implemented the other AP-CLDMA, and with that applied, platforms in question may suspend and resume normally as every bits are in position. However, while these patches had been reverted for another revision that is still being worked on by the hardware vendor, a minimum, sauced patch is created to work-around this first to meet project schedules, and will be reverted and superseded with a final, mainline landing revision. [Test Case] Trigger suspend and there should be no more suspend errors from t7xx: mtk_t7xx :58:00.0: [PM] SAP suspend error: -110 mtk_t7xx :58:00.0: PM: pci_pm_suspend(): t7xx_pci_pm_suspend+0x0/0x20 [mtk_t7xx] returns -110 mtk_t7xx :58:00.0: PM: dpm_run_callback(): pci_pm_suspend+0x0/0x1a0 returns -110 mtk_t7xx :58:00.0: PM: failed to suspend async: error -110 [Where problems could occur] The t7xx driver is still incomplete and we're staging aforementioned 4 patches in internal experimental kernels for development use. [Other Info] This affects Kinetic and above, so only Unstable, Kinetic and OEM-6.0 are nominated for fix. == original bug report == Hi, I found a "little" problem with Fibocom WWAN FM350-GL 5G modem in module mtk_t7xx . Power management for this modem is bad. When the notebook goes to sleep/suspend, kernel module mtk_t7xx return an error: mtk_t7xx :58:00.0: [PM] SAP suspend error: -110 mtk_t7xx :58:00.0: PM: pci_pm_suspend(): t7xx_pci_pm_suspend+0x0/0x20 [mtk_t7xx] returns -110 mtk_t7xx :58:00.0: PM: dpm_run_callback(): pci_pm_suspend+0x0/0x1a0 returns -110 mtk_t7xx :58:00.0: PM: failed to suspend async: error -110 So power management failed to suspend: PM: Some devices failed to suspend, or early wake event detected And the notebook not suspend and wake up again. It must be this module, because if I remove the module first (modprobe -r), the laptop goes to sleep and wakes up normally. However, after reinserting the module, the modem no longer appears in the system. Expected state: sleep occurs when the device is put to sleep - including the modem. When you wake up, you will wake up, including activating the modem and logging into the operator's network. Description:Ubuntu 20.04.5 LTS Release:20.04 lspci -v: 58:00.0 Wireless controller [0d40]: MEDIATEK Corp. Device 4d75 (rev 01) Subsystem: Device 1cf8:3500 Flags: bus master, fast devsel, latency 0, IRQ 17 Memory at 601e80 (64-bit, prefetchable) [size=32K] Memory at 5e80 (64-bit, non-prefetchable) [size=8M] Memory at 601e00 (64-bit, prefetchable) [size=8M] Capabilities: [80] Express Endpoint, MSI 00 Capabilities: [d0] MSI-X: Enable+ Count=34 Masked- Capabilities: [e0] MSI: Enable- Count=1/32 Maskable+
[Kernel-packages] [Bug 1990920] Re: Fix resume on AMD platforms when TBT monitor is plugged
This bug is awaiting verification that the linux-lowlatency- hwe-5.19/5.19.0-1017.18~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-lowlatency-hwe-5.19 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1990920 Title: Fix resume on AMD platforms when TBT monitor is plugged Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-5.14 source package in Kinetic: Invalid Status in linux-oem-5.17 source package in Kinetic: Invalid Bug description: [Impact] When TBT monitor is connected to AMD platform, system resume will hit stack corruption or BUG_ON() macro. [Fix] Revert the offending commit and handle MST properly. [Test] The system can resume normally and no more kernel splat. [Where problems could occur] The new logic is restriced to MST hub, so normal DP/HDMI usage should be unaffected. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1990920/+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 1806488] Re: Support non-strict iommu mode on arm64
This bug is awaiting verification that the linux- aws-5.19/5.19.0-1019.20~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-aws-5.19 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1806488 Title: Support non-strict iommu mode on arm64 Status in linux package in Ubuntu: Fix Released Status in linux-aws package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Released Status in linux-aws source package in Bionic: Invalid Status in linux source package in Cosmic: Fix Released Status in linux-aws source package in Cosmic: Invalid Status in linux source package in Disco: Fix Released Status in linux-aws source package in Disco: Invalid Status in linux source package in Jammy: Invalid Status in linux-aws source package in Jammy: Fix Committed Status in linux source package in Kinetic: Invalid Status in linux-aws source package in Kinetic: Fix Released Status in linux source package in Lunar: Fix Released Status in linux-aws source package in Lunar: Fix Committed Bug description: [Impact] The Intel IOMMU driver provides an option for strict mode. When disabled, batching of IOTLB flush operations is permitted, allowing the user to trade-off isolation for improved performance. Ubuntu's kernel currently lacks a parity for this feature for ARM. There's a significant performance gain to be had by removing the need to flush the IOMMU TLB on every unmap on arm64. I'm seeing a 25% performance gain w/ fio reads on a single NVMe device. This mode of operation is available for x86 via the "intel_iommu=strict" parameter. Upstream now exposes an equivalent feature for ARM platforms via the "iommu.strict=[0|1]" parameter, while retaining the default strict-enabled mode. [Test Case] Run fio with the following config before and after applying the patches and collection IOPS count. Run again after applying the patches. Finally, run a 3rd time after adding iommu.strict=0 to the kernel commandline. Performance should not regress after the update. Performance should further improve after adding iommu.strict=0 - but if it doesn't for some reason, that is not a regression. $ cat fio.rc [global] rw=read direct=1 ioengine=libaio iodepth=2048 numjobs=10 bs=4k group_reporting=1 group_reporting=1 cpumask=0xff runtime=100 loops = 1 [job1] filename=/dev/nvme0n1 [Fix] 44f6876a00e83 iommu/arm-smmu: Support non-strict mode b2dfeba654cb0 iommu/io-pgtable-arm-v7s: Add support for non-strict mode 9662b99a19abc iommu/arm-smmu-v3: Add support for non-strict mode b6b65ca20bc93 iommu/io-pgtable-arm: Add support for non-strict mode 68a6efe86f6a1 iommu: Add "iommu.strict" command line option 2da274cdf998a iommu/dma: Add support for non-strict mode 07fdef34d2be6 iommu/arm-smmu-v3: Implement flush_iotlb_all hook 85c7a0f1ef624 iommu/io-pgtable-arm: Fix race handling in split_blk_unmap() [Regression Risk] Most of these patches are specific to ARM, and have been regression tested on both arm64 (HiSilicon D06) and armhf (QEMU virt) using "stress-ng --vm $(nproc)" 2 patches do touch arch-indep code however: > 68a6efe86f6a1 iommu: Add "iommu.strict" command line option Adds a new command line option and sets an attribute that iommu drivers can optionally react to. Doesn't change default behavior. > 2da274cdf998a iommu/dma: Add support for non-strict mode This driver is only built for arm64 and ppc64el (determined by looking at the build logs). Most of this patch only changes behavior in the non-default (and new) iommu.strict=0 case. The exception, which is called out in the commit message, is this hunk: - WARN_ON(iommu_unmap(domain, dma_addr, size) != size); + WARN_ON(iommu_unmap_fast(domain, dma_addr, size) != size); + if (!cookie->fq_domain) + iommu_tlb_sync(domain); In the default case, where fq_domain will be NULl, we are now factoring iommu_unmap() into: iommu_unmap_fast() iommu_tlb_sync() Looking at the source to iommu_unmap() confirms that this is functionally equivalent. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806488/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
[Kernel-packages] [Bug 1990920] Re: Fix resume on AMD platforms when TBT monitor is plugged
This bug is awaiting verification that the linux- aws-5.19/5.19.0-1019.20~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-aws-5.19 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1990920 Title: Fix resume on AMD platforms when TBT monitor is plugged Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-5.14 source package in Kinetic: Invalid Status in linux-oem-5.17 source package in Kinetic: Invalid Bug description: [Impact] When TBT monitor is connected to AMD platform, system resume will hit stack corruption or BUG_ON() macro. [Fix] Revert the offending commit and handle MST properly. [Test] The system can resume normally and no more kernel splat. [Where problems could occur] The new logic is restriced to MST hub, so normal DP/HDMI usage should be unaffected. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1990920/+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 1978986] Re: [SRU][J/OEM-5.17][PATCH 0/1] Fix oled brightness set above frame-average luminance
This bug is awaiting verification that the linux-lowlatency- hwe-5.19/5.19.0-1017.18~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-lowlatency-hwe-5.19 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1978986 Title: [SRU][J/OEM-5.17][PATCH 0/1] Fix oled brightness set above frame- average luminance Status in HWE Next: Fix Released Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-5.14 source package in Kinetic: Invalid Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: [Impact] The brightness is not changed obviously during 200 to 255 on AMD or 400 to 512 on Intel.. [Fix] Read HDR meta to detect the max and min luminance. max_cll defines the content light luminance for individual pixel. max_fall defines frame-average level luminance. Use max_fall value instead of max_cll as a limit for brightness control. [Test] Verified on AMD Cezanne, Barcelo, Rembrandt and Intel ADL, also on LCD panel and OLED panel. The brightness is changed more obivously on OLED panel, and no affect on LCD panel. [Where problems could occur] Low risk, It may cause the max brightness can't be set. All 3 patches are in drm-misc tree. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1978986/+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 1978986] Re: [SRU][J/OEM-5.17][PATCH 0/1] Fix oled brightness set above frame-average luminance
This bug is awaiting verification that the linux- aws-5.19/5.19.0-1019.20~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags removed: verification-done-jammy ** Tags added: kernel-spammed-jammy-linux-aws-5.19 verification-needed-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1978986 Title: [SRU][J/OEM-5.17][PATCH 0/1] Fix oled brightness set above frame- average luminance Status in HWE Next: Fix Released Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-5.14 source package in Kinetic: Invalid Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: [Impact] The brightness is not changed obviously during 200 to 255 on AMD or 400 to 512 on Intel.. [Fix] Read HDR meta to detect the max and min luminance. max_cll defines the content light luminance for individual pixel. max_fall defines frame-average level luminance. Use max_fall value instead of max_cll as a limit for brightness control. [Test] Verified on AMD Cezanne, Barcelo, Rembrandt and Intel ADL, also on LCD panel and OLED panel. The brightness is changed more obivously on OLED panel, and no affect on LCD panel. [Where problems could occur] Low risk, It may cause the max brightness can't be set. All 3 patches are in drm-misc tree. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1978986/+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 1983656] Re: iavf: SR-IOV VFs error with no traffic flow when MTU greater than 1500
This bug is awaiting verification that the linux-lowlatency- hwe-5.19/5.19.0-1017.18~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-lowlatency-hwe-5.19 -- 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/1983656 Title: iavf: SR-IOV VFs error with no traffic flow when MTU greater than 1500 Status in linux package in Ubuntu: Fix Committed Status in linux source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Bug description: BugLink: https://bugs.launchpad.net/bugs/1983656 [Impact] Virtual Machines with SR-IOV VFs from an Intel E810-XXV [8086:159b] get no traffic flow and produce error messages in both the host and guest during network configuration. Environment: Ubuntu OpenStack Focal-Ussuri with OVN Host Kernel: v5.15.0-41-generic 20.04 Focal-HWE Guest Kernels: v5.4.x Focal, v5.15.0-41-generic Jammy Host Error Messages: ice :98:00.1: VF 7 failed opcode 6, retval: -5 Guest Error Messages: iavf :00:05.0: PF returned error -5 (IAVF_ERR_PARAM) to our request 6 In the context of these errors "6" refers to the value of VIRTCHNL_OP_CONFIG_VSI_QUEUES It was found in these cases that the VM is able to successfully transmit packets but never receives any and the RX packet drop counters for the VF in "ip link" on the host increase equal to the RX packet count. There is a prior commit e6ba5273d4ede03d075d7a116b8edad1f6115f4d claiming to resolve this error in some cases. It is already included in 5.15.0-41-generic and did not resolve the issue. The following conditions are required to trigger the bug: - A port VLAN must be assigned by the host - The MTU must be set >1500 by the guest There is no workaround, Intel E810 SR-IOV VFs with MTU >1500 cannot be used without these patches. [Fix] iavf currently sets the maximum packet size to IAVF_MAX_RXBUFFER, but on the previous ice driver, it was decremented by VLAN_HLEN to make some space to fit the VLAN header. This doesn't happen on iavf, and we end up trying to use a packet size larger than IAVF_MAX_RXBUFFER, causing the IAVF_ERR_PARAM error. The fix is to change the maximum packet size from IAVF_MAX_RXBUFFER to max_mtu received from the PF via GET_VF_RESOURCES msg. Also pick up a necessary commit for i40e to announce the correct maximum packet size by GET_VF_RESOURCES msg. This has been fixed by the following commits: commit 399c98c4dc50b7eb7e9f24da7ffdda6f025676ef Author: Michal Jaron Date: Tue Sep 13 15:38:35 2022 +0200 Subject: iavf: Fix set max MTU size with port VLAN and jumbo frames Link: https://github.com/torvalds/linux/commit/399c98c4dc50b7eb7e9f24da7ffdda6f025676ef commit 372539def2824c43b6afe2403045b140f65c5acc Author: Michal Jaron Date: Tue Sep 13 15:38:36 2022 +0200 Subject: i40e: Fix VF set max MTU size Link: https://github.com/torvalds/linux/commit/372539def2824c43b6afe2403045b140f65c5acc A test kernel is available in the following ppa: https://launchpad.net/~arif-ali/+archive/ubuntu/sf00343742 If you install the test kernel to a compute host and VM, when you attach a VF and set the MTU to 9000, it succeeds, and traffic can flow. [Test Plan] Create a Focal VM and assign an Intel E810 (ice) SR-IOV VF with a port vlan: Openstack works, as does creating a VM directly with uvtool/libvirt. $ uvt-kvm create focal-test release=focal Using the document to understand SRIOV basics in the link below https://www.intel.com/content/www/us/en/developer/articles/technical/configure- sr-iov-network-virtual-functions-in-linux-kvm.html The following command show all the bus info for all the network devices $ lshw -c network -businfo Choose one, as shown below pci@:17:01.4 ens2f0v4 networkEthernet Adaptive Virtual Function We can then add the following into the XML definition via “virsh edit focal-test” Then we stop and start the VM via "virsh shutdown focal-test" and then "virsh start focal-test". We can then login to the VM using the command below $ uvt-kvm ssh focal-test Once you have logged in, run the following ip parameters $ sudo ip a a
[Kernel-packages] [Bug 1983656] Re: iavf: SR-IOV VFs error with no traffic flow when MTU greater than 1500
This bug is awaiting verification that the linux- aws-5.19/5.19.0-1019.20~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-aws-5.19 -- 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/1983656 Title: iavf: SR-IOV VFs error with no traffic flow when MTU greater than 1500 Status in linux package in Ubuntu: Fix Committed Status in linux source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Bug description: BugLink: https://bugs.launchpad.net/bugs/1983656 [Impact] Virtual Machines with SR-IOV VFs from an Intel E810-XXV [8086:159b] get no traffic flow and produce error messages in both the host and guest during network configuration. Environment: Ubuntu OpenStack Focal-Ussuri with OVN Host Kernel: v5.15.0-41-generic 20.04 Focal-HWE Guest Kernels: v5.4.x Focal, v5.15.0-41-generic Jammy Host Error Messages: ice :98:00.1: VF 7 failed opcode 6, retval: -5 Guest Error Messages: iavf :00:05.0: PF returned error -5 (IAVF_ERR_PARAM) to our request 6 In the context of these errors "6" refers to the value of VIRTCHNL_OP_CONFIG_VSI_QUEUES It was found in these cases that the VM is able to successfully transmit packets but never receives any and the RX packet drop counters for the VF in "ip link" on the host increase equal to the RX packet count. There is a prior commit e6ba5273d4ede03d075d7a116b8edad1f6115f4d claiming to resolve this error in some cases. It is already included in 5.15.0-41-generic and did not resolve the issue. The following conditions are required to trigger the bug: - A port VLAN must be assigned by the host - The MTU must be set >1500 by the guest There is no workaround, Intel E810 SR-IOV VFs with MTU >1500 cannot be used without these patches. [Fix] iavf currently sets the maximum packet size to IAVF_MAX_RXBUFFER, but on the previous ice driver, it was decremented by VLAN_HLEN to make some space to fit the VLAN header. This doesn't happen on iavf, and we end up trying to use a packet size larger than IAVF_MAX_RXBUFFER, causing the IAVF_ERR_PARAM error. The fix is to change the maximum packet size from IAVF_MAX_RXBUFFER to max_mtu received from the PF via GET_VF_RESOURCES msg. Also pick up a necessary commit for i40e to announce the correct maximum packet size by GET_VF_RESOURCES msg. This has been fixed by the following commits: commit 399c98c4dc50b7eb7e9f24da7ffdda6f025676ef Author: Michal Jaron Date: Tue Sep 13 15:38:35 2022 +0200 Subject: iavf: Fix set max MTU size with port VLAN and jumbo frames Link: https://github.com/torvalds/linux/commit/399c98c4dc50b7eb7e9f24da7ffdda6f025676ef commit 372539def2824c43b6afe2403045b140f65c5acc Author: Michal Jaron Date: Tue Sep 13 15:38:36 2022 +0200 Subject: i40e: Fix VF set max MTU size Link: https://github.com/torvalds/linux/commit/372539def2824c43b6afe2403045b140f65c5acc A test kernel is available in the following ppa: https://launchpad.net/~arif-ali/+archive/ubuntu/sf00343742 If you install the test kernel to a compute host and VM, when you attach a VF and set the MTU to 9000, it succeeds, and traffic can flow. [Test Plan] Create a Focal VM and assign an Intel E810 (ice) SR-IOV VF with a port vlan: Openstack works, as does creating a VM directly with uvtool/libvirt. $ uvt-kvm create focal-test release=focal Using the document to understand SRIOV basics in the link below https://www.intel.com/content/www/us/en/developer/articles/technical/configure- sr-iov-network-virtual-functions-in-linux-kvm.html The following command show all the bus info for all the network devices $ lshw -c network -businfo Choose one, as shown below pci@:17:01.4 ens2f0v4 networkEthernet Adaptive Virtual Function We can then add the following into the XML definition via “virsh edit focal-test” Then we stop and start the VM via "virsh shutdown focal-test" and then "virsh start focal-test". We can then login to the VM using the command below $ uvt-kvm ssh focal-test Once you have logged in, run the following ip parameters $ sudo ip a a 192.168.1.7/24 dev
[Kernel-packages] [Bug 1988461] Re: intel_pmc_core not load on Raptor Lake
This bug is awaiting verification that the linux-lowlatency- hwe-5.19/5.19.0-1017.18~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-lowlatency-hwe-5.19 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1988461 Title: intel_pmc_core not load on Raptor Lake Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: [SRU Justification] [Impact] Missing kernel pmc sysfs interface in /sys/kernel/debug/pmc_core. [Fix] Two commits for kernel version older than v6.0-rc3, and one for otherwise. [Test Case] $ ls /sys/kernel/debug/pmc_core [Where problems could occur] No. [Other Info] RPL-S is supported since oem-5.17, so unstable/oem-6.0/kinetic/oem-5.17 are affected. oem-5.17/oem-6.0 are skipped here for they have been applied manually. == original bug description == [Summary] intel_pmc_core not load on Raptor Lake [Reproduce Steps] 1. Boot into Ubuntu desktop 2. Check if /sys/kernel/debug/pmc_core folder exist [Results] Expected: folder /sys/kernel/debug/pmc_core folder been created Actual: /sys/kernel/debug/pmc_core not exist To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1988461/+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 1988711] Re: Update Broadcom Emulex FC HBA lpfc driver to 14.2.0.5 for Ubuntu 22.04
This bug is awaiting verification that the linux-lowlatency- hwe-5.19/5.19.0-1017.18~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-lowlatency-hwe-5.19 -- 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/1988711 Title: Update Broadcom Emulex FC HBA lpfc driver to 14.2.0.5 for Ubuntu 22.04 Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: In Progress Status in linux source package in Kinetic: Fix Released Bug description: [IMPACT/Justification] There are numerous bug fixes included in the more recent version of lpfc That Broadcom has asked to pull into Jammy and Kinetic to better support customers in the field who are using the GA kernel and cant or wont move to the HWE kernels. These all are limited to the lpfc driver itself, no patches to core code are requested. [FIX] A few of these were already landed in Jammy, and all but 6 (ones landed in 6.0 upstream) were already in Kinetic. b3d11f195cbb scsi: lpfc: Copyright updates for 14.2.0.5 patches 71faf8d30fdb scsi: lpfc: Update lpfc version to 14.2.0.5 b21c9deb1479 scsi: lpfc: Refactor lpfc_nvmet_prep_abort_wqe() into lpfc_sli_prep_abort_xri() ffc566411ade scsi: lpfc: Revert RSCN_MEMENTO workaround for misbehaved configuration ea92e173dc55 scsi: lpfc: Fix lost NVMe paths during LIF bounce stress test 2f67dc7970bc scsi: lpfc: Fix possible memory leak when failing to issue CMF WQE 0948a9c53860 scsi: lpfc: Remove extra atomic_inc on cmd_pending in queuecommand after VMID 35251b4d79db scsi: lpfc: Set PU field when providing D_ID in XMIT_ELS_RSP64_CX iocb f8191d40aa61 scsi: lpfc: Prevent buffer overflow crashes in debugfs with malformed user input 4ecc9b0271a7 scsi: lpfc: Fix uninitialized cqe field in lpfc_nvme_cancel_iocb() 1af48fffd7ff scsi: lpfc: Update lpfc version to 14.2.0.4 2e7e9c0c1ec0 scsi: lpfc: Allow reduced polling rate for nvme_admin_async_event cmd completion ea7bd1f39331 scsi: lpfc: Add more logging of cmd and cqe information for aborted NVMe cmds 336d63615466 scsi: lpfc: Fix port stuck in bypassed state after LIP in PT2PT topology b1b3440f437b scsi: lpfc: Resolve NULL ptr dereference after an ELS LOGO is aborted 6f808bd78e82 scsi: lpfc: Address NULL pointer dereference after starget_to_rport() e27f05147bff scsi: lpfc: Resolve some cleanup issues following SLI path refactoring 24e1f056677e scsi: lpfc: Resolve some cleanup issues following abort path refactoring 44ba9786b673 scsi: lpfc: Correct BDE type for XMIT_SEQ64_WQE in lpfc_ct_reject_event() a5b168efba21 scsi: lpfc: Add support for ATTO Fibre Channel devices 348efeca7487 scsi: lpfc: Rework lpfc_vmid_get_appid() to be protocol independent ed913cf4a533 scsi: lpfc: Commonize VMID code location fcb9e738667c scsi: lpfc: Update lpfc version to 14.2.0.3 a14396b6d139 scsi: lpfc: Use sg_dma_address() and sg_dma_len() macros for NVMe I/O e6f510414502 scsi: lpfc: Alter FPIN stat accounting logic de3ec318fee3 scsi: lpfc: Rework FDMI initialization after link up 5099478e436f scsi: lpfc: Change VMID registration to be based on fabric parameters dc8a71bd414f scsi: lpfc: Decrement outstanding gidft_inp counter if lpfc_err_lost_link() 4a0f4aff3ce5 scsi: lpfc: Use list_for_each_entry_safe() in rscn_recovery_check() 596fc8adb171 scsi: lpfc: Fix dmabuf ptr assignment in lpfc_ct_reject_event() ead76d4c09b8 scsi: lpfc: Inhibit aborts if external loopback plug is inserted b7e952cbc63c scsi: lpfc: Fix ndlp put following a LOGO completion ba3d58a1df46 scsi: lpfc: Fill in missing ndlp kref puts in error paths 84c6f99e3907 scsi: lpfc: Fix element offset in __lpfc_sli_release_iocbq_s4() 775266207105 scsi: lpfc: Correct BDE DMA address assignment for GEN_REQ_WQE cc28fac16ab7 scsi: lpfc: Fix split code for FLOGI on FCoE c2024e3b33ee scsi: lpfc: Remove redundant lpfc_sli_prep_wqe() call 92bd903da12b scsi: lpfc: Fix additional reference counting in lpfc_bsg_rport_els() db05628435aa blk-cgroup: move blkcg_{get,set}_fc_appid out of line 646db1a560f4 scsi: lpfc: Fix resource leak in lpfc_sli4_send_seq_to_ulp() 3d1d34ec1fbc scsi: lpfc: Remove unnecessary null ndlp check in lpfc_sli_prep_wqe() a346f28ad231 scsi: lpfc: Remove unneeded variable 66c20a97367a scsi: lpfc: Copyright updates for 14.2.0.2 patches
[Kernel-packages] [Bug 1988461] Re: intel_pmc_core not load on Raptor Lake
This bug is awaiting verification that the linux- aws-5.19/5.19.0-1019.20~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags removed: verification-done-jammy ** Tags added: kernel-spammed-jammy-linux-aws-5.19 verification-needed-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1988461 Title: intel_pmc_core not load on Raptor Lake Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: [SRU Justification] [Impact] Missing kernel pmc sysfs interface in /sys/kernel/debug/pmc_core. [Fix] Two commits for kernel version older than v6.0-rc3, and one for otherwise. [Test Case] $ ls /sys/kernel/debug/pmc_core [Where problems could occur] No. [Other Info] RPL-S is supported since oem-5.17, so unstable/oem-6.0/kinetic/oem-5.17 are affected. oem-5.17/oem-6.0 are skipped here for they have been applied manually. == original bug description == [Summary] intel_pmc_core not load on Raptor Lake [Reproduce Steps] 1. Boot into Ubuntu desktop 2. Check if /sys/kernel/debug/pmc_core folder exist [Results] Expected: folder /sys/kernel/debug/pmc_core folder been created Actual: /sys/kernel/debug/pmc_core not exist To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1988461/+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 1990985] Re: ACPI: processor idle: Practically limit "Dummy wait" workaround to old Intel systems
This bug is awaiting verification that the linux-lowlatency- hwe-5.19/5.19.0-1017.18~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-lowlatency-hwe-5.19 -- 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/1990985 Title: ACPI: processor idle: Practically limit "Dummy wait" workaround to old Intel systems Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Bug description: IMPACT: Old, circa 2002 chipsets have a bug: they don't go idle when they are supposed to. So, a workaround was added to slow the CPU down and ensure that the CPU waits a bit for the chipset to actually go idle. This workaround is ancient and has been in place in some form since the original kernel ACPI implementation. But, this workaround is very painful on modern systems. The "inl()" can take thousands of cycles (see Link: for some more detailed numbers and some fun kernel archaeology). First and foremost, modern systems should not be using this code. Typical Intel systems have not used it in over a decade because it is horribly inferior to MWAIT-based idle. Despite this, people do seem to be tripping over this workaround on AMD system today. Limit the "dummy wait" workaround to Intel systems. Keep Modern AMD systems from tripping over the workaround. Remotely modern Intel systems use intel_idle instead of this code and will, in practice, remain unaffected by the dummy wait. Reported-by: K Prateek Nayak Suggested-by: Rafael J. Wysocki Signed-off-by: Dave Hansen Reviewed-by: Mario Limonciello Tested-by: K Prateek Nayak Link: https://lore.kernel.org/all/20220921063638.2489-1-kprateek.na...@amd.com/ Link: https://lkml.kernel.org/r/20220922184745.3252932-1-dave.han...@intel.com FIX: This issue pertains to all Zen based processors starting with Naples(Zen1). All LTS releases will need this fix: https://github.com/torvalds/linux/commit/e400ad8b7e6a1b9102123c6240289a811501f7d9 TESTCASE: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990985/+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 1995573] Re: Screen cannot turn on after screen off with Matrox G200eW3 [102b:0536]
This bug is awaiting verification that the linux-lowlatency- hwe-5.19/5.19.0-1017.18~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-lowlatency-hwe-5.19 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1995573 Title: Screen cannot turn on after screen off with Matrox G200eW3 [102b:0536] Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-5.17 source package in Kinetic: Invalid Bug description: [Impact] Screen cannot turn on after screen is off [Fix] Below commit from v6.0-rc1 fixes the issue c577b2f43e80 drm/mgag200: Enable atomic gamma lut update And applied some other commits to fix the conflicts c48a36301634 drm/mgag200: Optimize damage clips 3064debaf55e drm/mgag200: Add FB_DAMAGE_CLIPS support 5913ab941d6e drm/mgag200: Acquire I/O lock while reading EDID 931e3f3a0e99 drm/mgag200: Protect concurrent access to I/O registers with lock e13f13e039dc drm: Add DRM-managed mutex_init() [Tests] Verified on the machine with Matrox G200eW3 [102b:0536] graphics card. [Where problems could occur] The commits to solve the conflicts are trivial, and not likely to introduce regressions. The fix patch change a lot of code and hard to evaluate the risk, but check the latest linus/master tree and linux-next/master tree, there is no fixed commit for all these cherry-picked commits, so should be safe to include them. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1995573/+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 1990985] Re: ACPI: processor idle: Practically limit "Dummy wait" workaround to old Intel systems
This bug is awaiting verification that the linux- aws-5.19/5.19.0-1019.20~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags removed: verification-done-jammy ** Tags added: kernel-spammed-jammy-linux-aws-5.19 verification-needed-jammy -- 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/1990985 Title: ACPI: processor idle: Practically limit "Dummy wait" workaround to old Intel systems Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Bug description: IMPACT: Old, circa 2002 chipsets have a bug: they don't go idle when they are supposed to. So, a workaround was added to slow the CPU down and ensure that the CPU waits a bit for the chipset to actually go idle. This workaround is ancient and has been in place in some form since the original kernel ACPI implementation. But, this workaround is very painful on modern systems. The "inl()" can take thousands of cycles (see Link: for some more detailed numbers and some fun kernel archaeology). First and foremost, modern systems should not be using this code. Typical Intel systems have not used it in over a decade because it is horribly inferior to MWAIT-based idle. Despite this, people do seem to be tripping over this workaround on AMD system today. Limit the "dummy wait" workaround to Intel systems. Keep Modern AMD systems from tripping over the workaround. Remotely modern Intel systems use intel_idle instead of this code and will, in practice, remain unaffected by the dummy wait. Reported-by: K Prateek Nayak Suggested-by: Rafael J. Wysocki Signed-off-by: Dave Hansen Reviewed-by: Mario Limonciello Tested-by: K Prateek Nayak Link: https://lore.kernel.org/all/20220921063638.2489-1-kprateek.na...@amd.com/ Link: https://lkml.kernel.org/r/20220922184745.3252932-1-dave.han...@intel.com FIX: This issue pertains to all Zen based processors starting with Naples(Zen1). All LTS releases will need this fix: https://github.com/torvalds/linux/commit/e400ad8b7e6a1b9102123c6240289a811501f7d9 TESTCASE: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990985/+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 1991365] Re: Fix Turbostat is not working for fam: 6 model: 191: stepping: 2 CPU
This bug is awaiting verification that the linux- aws-5.19/5.19.0-1019.20~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-aws-5.19 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1991365 Title: Fix Turbostat is not working for fam: 6 model: 191: stepping: 2 CPU Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: [Impact] turbostat doesn't show the correct fields for RPL-S. This's a wrong column. usec,Time_Of_Day_Seconds,Core,CPU,APIC,X2APIC,Avg_MHz,Busy%,Bzy_MHz,TSC_MHz,IPC,IRQ,POLL,C1ACPI,C2ACPI,C3ACPI,POLL%,C1ACPI%,C2ACPI%,C3ACPI%,CoreTmp,CoreThr,PkgTmp,GFX%rc6,GFXMHz,GFXAMHz,CPU%LPI,SYS%LPI [Fix] Add RPL-S support in turbostat [Test Case] 1. run "turbostat --list" 2. check the output, this is a correct column. usec,Time_Of_Day_Seconds,Core,CPU,APIC,X2APIC,Avg_MHz,Busy%,Bzy_MHz,TSC_MHz,IPC,IRQ,SMI,POLL,C1ACPI,C2ACPI,C3ACPI,POLL%,C1ACPI%,C2ACPI%,C3ACPI%,CPU%c1,CPU%c6,CPU%c7,CoreTmp,CoreThr,PkgTmp,GFX%rc6,GFXMHz,GFXAMHz,Totl%C0,Any%C0,GFX%C0,CPUGFX%,Pkg%pc2,Pkg%pc3,Pkg%pc6,Pkg%pc7,Pkg%pc8,Pkg%pc9,Pk%pc10,CPU%LPI,SYS%LPI,PkgWatt,CorWatt,GFXWatt,RAMWatt,PKG_%,RAM_% [Where problems could occur] Low, just add a devcie id to support RPL-S. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1991365/+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 1991365] Re: Fix Turbostat is not working for fam: 6 model: 191: stepping: 2 CPU
This bug is awaiting verification that the linux-lowlatency- hwe-5.19/5.19.0-1017.18~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-lowlatency-hwe-5.19 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1991365 Title: Fix Turbostat is not working for fam: 6 model: 191: stepping: 2 CPU Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: [Impact] turbostat doesn't show the correct fields for RPL-S. This's a wrong column. usec,Time_Of_Day_Seconds,Core,CPU,APIC,X2APIC,Avg_MHz,Busy%,Bzy_MHz,TSC_MHz,IPC,IRQ,POLL,C1ACPI,C2ACPI,C3ACPI,POLL%,C1ACPI%,C2ACPI%,C3ACPI%,CoreTmp,CoreThr,PkgTmp,GFX%rc6,GFXMHz,GFXAMHz,CPU%LPI,SYS%LPI [Fix] Add RPL-S support in turbostat [Test Case] 1. run "turbostat --list" 2. check the output, this is a correct column. usec,Time_Of_Day_Seconds,Core,CPU,APIC,X2APIC,Avg_MHz,Busy%,Bzy_MHz,TSC_MHz,IPC,IRQ,SMI,POLL,C1ACPI,C2ACPI,C3ACPI,POLL%,C1ACPI%,C2ACPI%,C3ACPI%,CPU%c1,CPU%c6,CPU%c7,CoreTmp,CoreThr,PkgTmp,GFX%rc6,GFXMHz,GFXAMHz,Totl%C0,Any%C0,GFX%C0,CPUGFX%,Pkg%pc2,Pkg%pc3,Pkg%pc6,Pkg%pc7,Pkg%pc8,Pkg%pc9,Pk%pc10,CPU%LPI,SYS%LPI,PkgWatt,CorWatt,GFXWatt,RAMWatt,PKG_%,RAM_% [Where problems could occur] Low, just add a devcie id to support RPL-S. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1991365/+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 1995573] Re: Screen cannot turn on after screen off with Matrox G200eW3 [102b:0536]
This bug is awaiting verification that the linux- aws-5.19/5.19.0-1019.20~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags removed: verification-done-jammy ** Tags added: kernel-spammed-jammy-linux-aws-5.19 verification-needed-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1995573 Title: Screen cannot turn on after screen off with Matrox G200eW3 [102b:0536] Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-5.17 source package in Kinetic: Invalid Bug description: [Impact] Screen cannot turn on after screen is off [Fix] Below commit from v6.0-rc1 fixes the issue c577b2f43e80 drm/mgag200: Enable atomic gamma lut update And applied some other commits to fix the conflicts c48a36301634 drm/mgag200: Optimize damage clips 3064debaf55e drm/mgag200: Add FB_DAMAGE_CLIPS support 5913ab941d6e drm/mgag200: Acquire I/O lock while reading EDID 931e3f3a0e99 drm/mgag200: Protect concurrent access to I/O registers with lock e13f13e039dc drm: Add DRM-managed mutex_init() [Tests] Verified on the machine with Matrox G200eW3 [102b:0536] graphics card. [Where problems could occur] The commits to solve the conflicts are trivial, and not likely to introduce regressions. The fix patch change a lot of code and hard to evaluate the risk, but check the latest linus/master tree and linux-next/master tree, there is no fixed commit for all these cherry-picked commits, so should be safe to include them. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1995573/+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 1991608] Re: TEE Support for CCP driver
This bug is awaiting verification that the linux-lowlatency- hwe-5.19/5.19.0-1017.18~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-lowlatency-hwe-5.19 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1991608 Title: TEE Support for CCP driver Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux source package in Lunar: In Progress Status in linux-oem-5.17 source package in Lunar: Invalid Status in linux-oem-6.0 source package in Lunar: Invalid Bug description: [SRU Justification] [Impact] Missing support for of AMD Secure Processor device for PCI ID 0x14CA. [Fix] A patch is being proposed in upstream and CC-ed stable. [Test Case] Without a proper fix, following error appears in dmesg: ccp :02:00.5: tee: missing driver data ccp :02:00.5: tee initialization failed [Where problems could occur] This adds a new driver data entry to support ccp device that provides both sev and tee feature at the same time. [Other Info] While this is proposed to stable 5.15+, all kernels >= 5.15 are nominated for fix. == original bug description == Client and datacenter Zen4 SOC same PCI-ID but offer different functionality from the PSP. Genoa offers SEV, Client part offers TEE. This patch fixes an ERR level message and CCP driver functionality not working. ccp :02:00.5: tee: missing driver data ccp :02:00.5: tee initialization failed https://lore.kernel.org/linux- crypto/20220928184506.13981-1-mario.limoncie...@amd.com/T/#m1b933ea4b961d17cb1be5be74e2d22a860507ca0 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1991608/+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 1992266] Re: input/keyboard: the keyboard on some Asus laptops can't work
This bug is awaiting verification that the linux-lowlatency- hwe-5.19/5.19.0-1017.18~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-lowlatency-hwe-5.19 -- 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/1992266 Title: input/keyboard: the keyboard on some Asus laptops can't work Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Bug description: This is upstream tracking bug: https://bugzilla.kernel.org/show_bug.cgi?id=216158 The bug originates from an upstream bug, and the ubuntu users request me to do a SRU to make the ubuntu linux work on their Asus laptops, so once the pathces are merge to mainline kernel, I start to prepare this SRU. [Impact] Some Asus laptops config the IRQ of keyboard in the BIOS, but kernel will override to a new configuration for that IRQ, this will make the keyboard not work anymore under linux. [Fix] Backport 2 patches from mainlie kernel to fix this problem. [Test] boot the patched kernel on the machine, test the keyboard, all regular keys could work. [Where problems could occur] The patches use the dmi table to match the machines, so only the matched Asus laptops will be impacted by the patches, if there is any regression, the regression only affects those matched Asus laptops, and the regression possibility is very low since ubuntu users already tested the patches on their own Asus laptops. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992266/+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 1991608] Re: TEE Support for CCP driver
This bug is awaiting verification that the linux- aws-5.19/5.19.0-1019.20~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-aws-5.19 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1991608 Title: TEE Support for CCP driver Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux source package in Lunar: In Progress Status in linux-oem-5.17 source package in Lunar: Invalid Status in linux-oem-6.0 source package in Lunar: Invalid Bug description: [SRU Justification] [Impact] Missing support for of AMD Secure Processor device for PCI ID 0x14CA. [Fix] A patch is being proposed in upstream and CC-ed stable. [Test Case] Without a proper fix, following error appears in dmesg: ccp :02:00.5: tee: missing driver data ccp :02:00.5: tee initialization failed [Where problems could occur] This adds a new driver data entry to support ccp device that provides both sev and tee feature at the same time. [Other Info] While this is proposed to stable 5.15+, all kernels >= 5.15 are nominated for fix. == original bug description == Client and datacenter Zen4 SOC same PCI-ID but offer different functionality from the PSP. Genoa offers SEV, Client part offers TEE. This patch fixes an ERR level message and CCP driver functionality not working. ccp :02:00.5: tee: missing driver data ccp :02:00.5: tee initialization failed https://lore.kernel.org/linux- crypto/20220928184506.13981-1-mario.limoncie...@amd.com/T/#m1b933ea4b961d17cb1be5be74e2d22a860507ca0 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1991608/+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 1992266] Re: input/keyboard: the keyboard on some Asus laptops can't work
This bug is awaiting verification that the linux- aws-5.19/5.19.0-1019.20~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-aws-5.19 -- 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/1992266 Title: input/keyboard: the keyboard on some Asus laptops can't work Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Bug description: This is upstream tracking bug: https://bugzilla.kernel.org/show_bug.cgi?id=216158 The bug originates from an upstream bug, and the ubuntu users request me to do a SRU to make the ubuntu linux work on their Asus laptops, so once the pathces are merge to mainline kernel, I start to prepare this SRU. [Impact] Some Asus laptops config the IRQ of keyboard in the BIOS, but kernel will override to a new configuration for that IRQ, this will make the keyboard not work anymore under linux. [Fix] Backport 2 patches from mainlie kernel to fix this problem. [Test] boot the patched kernel on the machine, test the keyboard, all regular keys could work. [Where problems could occur] The patches use the dmi table to match the machines, so only the matched Asus laptops will be impacted by the patches, if there is any regression, the regression only affects those matched Asus laptops, and the regression possibility is very low since ubuntu users already tested the patches on their own Asus laptops. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992266/+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 1993120] Re: armhf kernel compiled with gcc-12 fails to boot on pi 3/2
This bug is awaiting verification that the linux-lowlatency- hwe-5.19/5.19.0-1017.18~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-lowlatency-hwe-5.19 -- 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/1993120 Title: armhf kernel compiled with gcc-12 fails to boot on pi 3/2 Status in gcc-12 package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Status in linux-raspi package in Ubuntu: Fix Released Status in gcc-12 source package in Kinetic: Invalid Status in linux source package in Kinetic: Fix Released Status in linux-raspi source package in Kinetic: Fix Released Bug description: Kinetic 5.19 kernels compiled with gcc-12 for armhf don't boot or hang on Pi 3 and 2. Seems to work fine on Pi 4. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-12/+bug/1993120/+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 1993120] Re: armhf kernel compiled with gcc-12 fails to boot on pi 3/2
This bug is awaiting verification that the linux- aws-5.19/5.19.0-1019.20~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-aws-5.19 verification-needed-jammy -- 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/1993120 Title: armhf kernel compiled with gcc-12 fails to boot on pi 3/2 Status in gcc-12 package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Status in linux-raspi package in Ubuntu: Fix Released Status in gcc-12 source package in Kinetic: Invalid Status in linux source package in Kinetic: Fix Released Status in linux-raspi source package in Kinetic: Fix Released Bug description: Kinetic 5.19 kernels compiled with gcc-12 for armhf don't boot or hang on Pi 3 and 2. Seems to work fine on Pi 4. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-12/+bug/1993120/+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 1993148] Re: Support Icicle Kit reference design v2022.10
This bug is awaiting verification that the linux-lowlatency- hwe-5.19/5.19.0-1017.18~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-lowlatency-hwe-5.19 -- 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/1993148 Title: Support Icicle Kit reference design v2022.10 Status in linux package in Ubuntu: Invalid Status in linux source package in Kinetic: Fix Released Bug description: [ Impact ] * The Michochip PolarFire SoC on the Icicle Kit is an FPGA with 4 + 1 RISC-V cores. So the memory map and some peripherals depend on the FPGA design loaded. * Microchip releases reference designs and are upstreaming support for running Linux on it. Unfortunately the upcoming v2022.10 release changes the memory layout compared to earlier versions, but v6.1-rc1 contains patches for it. * We'd like to support the v2022.10 release and hopefully future versions by backporting these changes. [ Test Plan ] * Update the Icicle Kit to the v2022.10 reference design and check that the generic riscv64 kernel boots. [ Where problems could occur ] * Users who are running v2022.9 or older versions of the reference design may have trouble booting, but the Icicle Kit was never officially supported by Ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1993148/+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 1993715] Re: AMD Cezanne takes 5 minutes to wake up from suspend
This bug is awaiting verification that the linux-lowlatency- hwe-5.19/5.19.0-1017.18~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-lowlatency-hwe-5.19 -- 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/1993715 Title: AMD Cezanne takes 5 minutes to wake up from suspend Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: [SRU Justification] [Impact] AMD Cezanne takes 5 minutes to wake up from suspend. [Fix] A fix originated from AMD is being proposed to upstream mailing list. [Test Case] $ rtcwake -m mem -s 10 [Where problems could occur] This patch fixes the issue we had, but maybe there are still some other corner cases that can cause similar problems. [Other Info] The problematic commit landed in v5.19-rc1, so kernels >= v5.19 are nominated for fix. == original bug description == [Summary] rtcwake may be blocked for 5 minutes. Model name: AMD Ryzen 5 7530U with Radeon Graphics CPU family: 25 Model: 80 Thread(s) per core: 2 Core(s) per socket: 6 Socket(s): 1 Stepping: 0 [Reproduce Steps] 1. $ rtcwake -m mem -s 10 2. The device takes 5 minutes to resume [Results] Expected: Should resume after 10 seconds Actual: System stays asleep for 5 minutes To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1993715/+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 1993315] Re: md: Replace snprintf with scnprintf
This bug is awaiting verification that the linux-lowlatency- hwe-5.19/5.19.0-1017.18~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-lowlatency-hwe-5.19 -- 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/1993315 Title: md: Replace snprintf with scnprintf Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Bug description: SRU Justification [Impact] Current code produces a warning as shown below when total characters in the constituent block device names plus the slashes exceeds 200. snprintf() returns the number of characters generated from the given input, which could cause the expression “200 – len” to wrap around to a large positive number. Fix this by using scnprintf() instead, which returns the actual number of characters written into the buffer. [ 1513.267938] [ cut here ] [ 1513.267943] WARNING: CPU: 15 PID: 37247 at /lib/vsprintf.c:2509 vsnprintf+0x2c8/0x510 [ 1513.267944] Modules linked in: [ 1513.267969] CPU: 15 PID: 37247 Comm: mdadm Not tainted 5.4.0-1085-azure #90~18.04.1-Ubuntu [ 1513.267969] Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS Hyper-V UEFI Release v4.1 05/09/2022 [ 1513.267971] RIP: 0010:vsnprintf+0x2c8/0x510 <-snip-> [ 1513.267982] Call Trace: [ 1513.267986] snprintf+0x45/0x70 [ 1513.267990] ? disk_name+0x71/0xa0 [ 1513.267993] dump_zones+0x114/0x240 [raid0] [ 1513.267996] ? _cond_resched+0x19/0x40 [ 1513.267998] raid0_run+0x19e/0x270 [raid0] [ 1513.268000] md_run+0x5e0/0xc50 [ 1513.268003] ? security_capable+0x3f/0x60 [ 1513.268005] do_md_run+0x19/0x110 [ 1513.268006] md_ioctl+0x195e/0x1f90 [ 1513.268007] blkdev_ioctl+0x91f/0x9f0 [ 1513.268010] block_ioctl+0x3d/0x50 [ 1513.268012] do_vfs_ioctl+0xa9/0x640 [ 1513.268014] ? __fput+0x162/0x260 [ 1513.268016] ksys_ioctl+0x75/0x80 [ 1513.268017] __x64_sys_ioctl+0x1a/0x20 [ 1513.268019] do_syscall_64+0x5e/0x200 [ 1513.268021] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [Fix] https://git.kernel.org/pub/scm/linux/kernel/git/next/linux- next.git/commit/?id=1727fd5015d8f93474148f94e34cda5aa6ad4a43 [Where things could go wrong] This seems unlikely to cause a regression [Other Info] SF: #00346036 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1993315/+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 1993148] Re: Support Icicle Kit reference design v2022.10
This bug is awaiting verification that the linux- aws-5.19/5.19.0-1019.20~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-aws-5.19 -- 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/1993148 Title: Support Icicle Kit reference design v2022.10 Status in linux package in Ubuntu: Invalid Status in linux source package in Kinetic: Fix Released Bug description: [ Impact ] * The Michochip PolarFire SoC on the Icicle Kit is an FPGA with 4 + 1 RISC-V cores. So the memory map and some peripherals depend on the FPGA design loaded. * Microchip releases reference designs and are upstreaming support for running Linux on it. Unfortunately the upcoming v2022.10 release changes the memory layout compared to earlier versions, but v6.1-rc1 contains patches for it. * We'd like to support the v2022.10 release and hopefully future versions by backporting these changes. [ Test Plan ] * Update the Icicle Kit to the v2022.10 reference design and check that the generic riscv64 kernel boots. [ Where problems could occur ] * Users who are running v2022.9 or older versions of the reference design may have trouble booting, but the Icicle Kit was never officially supported by Ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1993148/+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 1993315] Re: md: Replace snprintf with scnprintf
This bug is awaiting verification that the linux- aws-5.19/5.19.0-1019.20~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-aws-5.19 -- 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/1993315 Title: md: Replace snprintf with scnprintf Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Bug description: SRU Justification [Impact] Current code produces a warning as shown below when total characters in the constituent block device names plus the slashes exceeds 200. snprintf() returns the number of characters generated from the given input, which could cause the expression “200 – len” to wrap around to a large positive number. Fix this by using scnprintf() instead, which returns the actual number of characters written into the buffer. [ 1513.267938] [ cut here ] [ 1513.267943] WARNING: CPU: 15 PID: 37247 at /lib/vsprintf.c:2509 vsnprintf+0x2c8/0x510 [ 1513.267944] Modules linked in: [ 1513.267969] CPU: 15 PID: 37247 Comm: mdadm Not tainted 5.4.0-1085-azure #90~18.04.1-Ubuntu [ 1513.267969] Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS Hyper-V UEFI Release v4.1 05/09/2022 [ 1513.267971] RIP: 0010:vsnprintf+0x2c8/0x510 <-snip-> [ 1513.267982] Call Trace: [ 1513.267986] snprintf+0x45/0x70 [ 1513.267990] ? disk_name+0x71/0xa0 [ 1513.267993] dump_zones+0x114/0x240 [raid0] [ 1513.267996] ? _cond_resched+0x19/0x40 [ 1513.267998] raid0_run+0x19e/0x270 [raid0] [ 1513.268000] md_run+0x5e0/0xc50 [ 1513.268003] ? security_capable+0x3f/0x60 [ 1513.268005] do_md_run+0x19/0x110 [ 1513.268006] md_ioctl+0x195e/0x1f90 [ 1513.268007] blkdev_ioctl+0x91f/0x9f0 [ 1513.268010] block_ioctl+0x3d/0x50 [ 1513.268012] do_vfs_ioctl+0xa9/0x640 [ 1513.268014] ? __fput+0x162/0x260 [ 1513.268016] ksys_ioctl+0x75/0x80 [ 1513.268017] __x64_sys_ioctl+0x1a/0x20 [ 1513.268019] do_syscall_64+0x5e/0x200 [ 1513.268021] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [Fix] https://git.kernel.org/pub/scm/linux/kernel/git/next/linux- next.git/commit/?id=1727fd5015d8f93474148f94e34cda5aa6ad4a43 [Where things could go wrong] This seems unlikely to cause a regression [Other Info] SF: #00346036 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1993315/+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 1993563] Re: support for same series backports versioning numbers
This bug is awaiting verification that the linux- aws-5.19/5.19.0-1019.20~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-aws-5.19 -- 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/1993563 Title: support for same series backports versioning numbers Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Committed Status in linux source package in Kinetic: Fix Released Bug description: packaging support for sameport versioning numbers Allow generating kernel packages, that use backports mechanism within the same series. For example linux-lowlatancy linux-riscv. Those kernels already have customized packaging to achieve the above, this is introducing standard support for this in the main kernels for jammy and kinetic series. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1993563/+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 1993563] Re: support for same series backports versioning numbers
This bug is awaiting verification that the linux-lowlatency- hwe-5.19/5.19.0-1017.18~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-lowlatency-hwe-5.19 -- 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/1993563 Title: support for same series backports versioning numbers Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Committed Status in linux source package in Kinetic: Fix Released Bug description: packaging support for sameport versioning numbers Allow generating kernel packages, that use backports mechanism within the same series. For example linux-lowlatancy linux-riscv. Those kernels already have customized packaging to achieve the above, this is introducing standard support for this in the main kernels for jammy and kinetic series. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1993563/+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 1993715] Re: AMD Cezanne takes 5 minutes to wake up from suspend
This bug is awaiting verification that the linux- aws-5.19/5.19.0-1019.20~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags removed: verification-done-jammy ** Tags added: kernel-spammed-jammy-linux-aws-5.19 verification-needed-jammy -- 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/1993715 Title: AMD Cezanne takes 5 minutes to wake up from suspend Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: [SRU Justification] [Impact] AMD Cezanne takes 5 minutes to wake up from suspend. [Fix] A fix originated from AMD is being proposed to upstream mailing list. [Test Case] $ rtcwake -m mem -s 10 [Where problems could occur] This patch fixes the issue we had, but maybe there are still some other corner cases that can cause similar problems. [Other Info] The problematic commit landed in v5.19-rc1, so kernels >= v5.19 are nominated for fix. == original bug description == [Summary] rtcwake may be blocked for 5 minutes. Model name: AMD Ryzen 5 7530U with Radeon Graphics CPU family: 25 Model: 80 Thread(s) per core: 2 Core(s) per socket: 6 Socket(s): 1 Stepping: 0 [Reproduce Steps] 1. $ rtcwake -m mem -s 10 2. The device takes 5 minutes to resume [Results] Expected: Should resume after 10 seconds Actual: System stays asleep for 5 minutes To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1993715/+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 1995041] Re: Fix ath11k deadlock on WCN6855
This bug is awaiting verification that the linux-lowlatency- hwe-5.19/5.19.0-1017.18~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-lowlatency-hwe-5.19 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1995041 Title: Fix ath11k deadlock on WCN6855 Status in HWE Next: In Progress Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: [Impact] ath11k is in deadlock when stress reboot or suspend on WCN6855. sometimes kernel hang. Aug 19 01:29:28 Thor-P3-AMD-2 kernel: Call Trace: Aug 19 01:29:28 Thor-P3-AMD-2 kernel: Aug 19 01:29:28 Thor-P3-AMD-2 kernel: __schedule+0x240/0x5a0 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? resched_curr+0x52/0xc0 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: schedule+0x55/0xd0 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: schedule_timeout+0x115/0x150 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? raw_spin_rq_unlock+0x10/0x30 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? try_to_wake_up+0x211/0x600 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? ath11k_ce_send+0x17a/0x2e0 [ath11k] Aug 19 01:29:28 Thor-P3-AMD-2 kernel: wait_for_completion+0x8b/0xf0 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: __flush_work.isra.0+0x171/0x270 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? flush_workqueue_prep_pwqs+0x140/0x140 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: __cancel_work_timer+0x11b/0x1a0 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? ath11k_mac_config_mon_status_default+0xcc/0x170 [ath11k] Aug 19 01:29:28 Thor-P3-AMD-2 kernel: cancel_work_sync+0x10/0x20 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ath11k_mac_op_stop+0x9f/0x1e0 [ath11k] Aug 19 01:29:28 Thor-P3-AMD-2 kernel: drv_stop+0x45/0x110 [mac80211] [Fix] Fix this by switching from using regulatory_set_wiphy_regd_sync() to regulatory_set_wiphy_regd(). Now cfg80211 will schedule another workqueue which handles the locking on it's own. So the ath11k workqueue can simply exit without taking any locks, avoiding the deadlock. [Test] Verified on hardware, stress reboot and suspend 30 times OK. [Where problems could occur] It may break ath11k wifi driver. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1995041/+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 1995041] Re: Fix ath11k deadlock on WCN6855
This bug is awaiting verification that the linux- aws-5.19/5.19.0-1019.20~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-aws-5.19 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1995041 Title: Fix ath11k deadlock on WCN6855 Status in HWE Next: In Progress Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: [Impact] ath11k is in deadlock when stress reboot or suspend on WCN6855. sometimes kernel hang. Aug 19 01:29:28 Thor-P3-AMD-2 kernel: Call Trace: Aug 19 01:29:28 Thor-P3-AMD-2 kernel: Aug 19 01:29:28 Thor-P3-AMD-2 kernel: __schedule+0x240/0x5a0 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? resched_curr+0x52/0xc0 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: schedule+0x55/0xd0 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: schedule_timeout+0x115/0x150 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? raw_spin_rq_unlock+0x10/0x30 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? try_to_wake_up+0x211/0x600 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? ath11k_ce_send+0x17a/0x2e0 [ath11k] Aug 19 01:29:28 Thor-P3-AMD-2 kernel: wait_for_completion+0x8b/0xf0 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: __flush_work.isra.0+0x171/0x270 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? flush_workqueue_prep_pwqs+0x140/0x140 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: __cancel_work_timer+0x11b/0x1a0 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? ath11k_mac_config_mon_status_default+0xcc/0x170 [ath11k] Aug 19 01:29:28 Thor-P3-AMD-2 kernel: cancel_work_sync+0x10/0x20 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ath11k_mac_op_stop+0x9f/0x1e0 [ath11k] Aug 19 01:29:28 Thor-P3-AMD-2 kernel: drv_stop+0x45/0x110 [mac80211] [Fix] Fix this by switching from using regulatory_set_wiphy_regd_sync() to regulatory_set_wiphy_regd(). Now cfg80211 will schedule another workqueue which handles the locking on it's own. So the ath11k workqueue can simply exit without taking any locks, avoiding the deadlock. [Test] Verified on hardware, stress reboot and suspend 30 times OK. [Where problems could occur] It may break ath11k wifi driver. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1995041/+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 1995957] Re: Add cs35l41 firmware loading support
This bug is awaiting verification that the linux- aws-5.19/5.19.0-1019.20~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-aws-5.19 -- 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/1995957 Title: Add cs35l41 firmware loading support Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-firmware package in Ubuntu: New Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-firmware source package in Kinetic: Fix Released Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: [Impact] Speakers on some laptops are rather quiet even with max volume. [Fix] Loading firmware to make cs35l41 speaker amplifier really work. [Test] With the fix applied, the speaker has become really loud as intended. [Where problems could occur] Most commits are refactoring codes on both ASoC and HDA parts, so things can be missed. Other than that, the change is strictly limited to cs35l41, so the regression scope is rather narrow. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1995957/+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 1995957] Re: Add cs35l41 firmware loading support
This bug is awaiting verification that the linux-lowlatency- hwe-5.19/5.19.0-1017.18~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-lowlatency-hwe-5.19 -- 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/1995957 Title: Add cs35l41 firmware loading support Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-firmware package in Ubuntu: New Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-firmware source package in Kinetic: Fix Released Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: [Impact] Speakers on some laptops are rather quiet even with max volume. [Fix] Loading firmware to make cs35l41 speaker amplifier really work. [Test] With the fix applied, the speaker has become really loud as intended. [Where problems could occur] Most commits are refactoring codes on both ASoC and HDA parts, so things can be missed. Other than that, the change is strictly limited to cs35l41, so the regression scope is rather narrow. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1995957/+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 1996071] Re: [UBUNTU 20.04] boot: Add s390x secure boot trailer
This bug is awaiting verification that the linux-lowlatency- hwe-5.19/5.19.0-1017.18~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-lowlatency-hwe-5.19 -- 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/1996071 Title: [UBUNTU 20.04] boot: Add s390x secure boot trailer Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Bug description: SRU Justification: == [Impact] * Secure boot of Linux on s390x will no longer be possible with an upcoming IBM zSystems firmware update. [Fix] * aa127a069ef3 aa127a069ef312aca02b730d5137e1778d0c3ba7 "s390/boot: add secure boot trailer" for kinetic and jammy * https://launchpadlibrarian.net/633020900/0001-s390-boot-add-secure-boot-trailer.patch backport for focal [Test Plan] * An IBM z15 or LinuxONE III LPAR with zFCP/SCSI disk storage is required. * Ensure that 'Enable Secure Boot for Linux' is marked in case 'SCSI Load' is selected at the HMCs Load task and Activation Profile. * Perform an Ubuntu Server installation, either 20.04 or 22.04 (latest ISO). It will be a secure boot installation by default in case 'Enable Secure Boot for Linux' was marked. * Check sysfs: /sys/firmware/ipl/has_secure '1' indicates hw support for secure boot, otherwise '0' /sys/firmware/ipl/secure '1' indicates that secure IPL was successful, otherwise '0' * Navigate to the HMC task 'System information' and check the active firmware release. * Ensure that Ubuntu is still bootable in secure-boot mode with the updated firmware active, by for example doing a reboot after the firmware upgrade. * There is also a way to test the trailer on systems that do not have the updated firmware yet - in this case use the following script: https://launchpadlibrarian.net/633126861/check_sb_trailer.sh [Where problems could occur] * The 'trailer' might be broken, invalid or in a wrong format and can't be identified or read properly, or may cause issues while compressing/decompressing the kernel. * In worst case secure boot might become broken, even on systems that are still on the unpatched firmware level. * Or secure boot will become broken in general. [Other Info] * The above commit was upstream accepted with v6.1-rc3. * And it got tagged for upstream stable with: "Cc: # 5.2+" * But since this bug is marked as critical, and the patch is relatively short, traceable and s390x-specific, I'll go ahead and submit this patch for Jammy and Focal ahead of upstream stable. * Since on focal file 'vmlinux.lds.S' is at a different location 'arch/s390/boot/compressed/' instead of 'arch/s390/boot/' and the context is slightly different, the backport is needed. * It's planned to have kernel 6.2 in lunar (23.04), hence it will have the patch incl. when at the planned target level. __ Description: boot: Add secure boot trailer Symptom: Secure boot of Linux will no longer be possible with an upcoming IBM Z firmware update. Problem: New IBM Z firmware requires signed bootable images to contain a trailing data block with a specific format. Solution: Add the trailing data block to the Linux kernel image. Reproduction: Apply latest firmware, perform IPL with Secure Boot enabled. Fix: available upstream with Upstream-ID: aa127a069ef312aca02b730d5137e1778d0c3ba7 Preventive:yes Date: 2022-10-27 Author:Peter Oberparleiter Component: kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1996071/+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 1996071] Re: [UBUNTU 20.04] boot: Add s390x secure boot trailer
This bug is awaiting verification that the linux- aws-5.19/5.19.0-1019.20~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags removed: verification-done-jammy ** Tags added: kernel-spammed-jammy-linux-aws-5.19 verification-needed-jammy -- 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/1996071 Title: [UBUNTU 20.04] boot: Add s390x secure boot trailer Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Bug description: SRU Justification: == [Impact] * Secure boot of Linux on s390x will no longer be possible with an upcoming IBM zSystems firmware update. [Fix] * aa127a069ef3 aa127a069ef312aca02b730d5137e1778d0c3ba7 "s390/boot: add secure boot trailer" for kinetic and jammy * https://launchpadlibrarian.net/633020900/0001-s390-boot-add-secure-boot-trailer.patch backport for focal [Test Plan] * An IBM z15 or LinuxONE III LPAR with zFCP/SCSI disk storage is required. * Ensure that 'Enable Secure Boot for Linux' is marked in case 'SCSI Load' is selected at the HMCs Load task and Activation Profile. * Perform an Ubuntu Server installation, either 20.04 or 22.04 (latest ISO). It will be a secure boot installation by default in case 'Enable Secure Boot for Linux' was marked. * Check sysfs: /sys/firmware/ipl/has_secure '1' indicates hw support for secure boot, otherwise '0' /sys/firmware/ipl/secure '1' indicates that secure IPL was successful, otherwise '0' * Navigate to the HMC task 'System information' and check the active firmware release. * Ensure that Ubuntu is still bootable in secure-boot mode with the updated firmware active, by for example doing a reboot after the firmware upgrade. * There is also a way to test the trailer on systems that do not have the updated firmware yet - in this case use the following script: https://launchpadlibrarian.net/633126861/check_sb_trailer.sh [Where problems could occur] * The 'trailer' might be broken, invalid or in a wrong format and can't be identified or read properly, or may cause issues while compressing/decompressing the kernel. * In worst case secure boot might become broken, even on systems that are still on the unpatched firmware level. * Or secure boot will become broken in general. [Other Info] * The above commit was upstream accepted with v6.1-rc3. * And it got tagged for upstream stable with: "Cc: # 5.2+" * But since this bug is marked as critical, and the patch is relatively short, traceable and s390x-specific, I'll go ahead and submit this patch for Jammy and Focal ahead of upstream stable. * Since on focal file 'vmlinux.lds.S' is at a different location 'arch/s390/boot/compressed/' instead of 'arch/s390/boot/' and the context is slightly different, the backport is needed. * It's planned to have kernel 6.2 in lunar (23.04), hence it will have the patch incl. when at the planned target level. __ Description: boot: Add secure boot trailer Symptom: Secure boot of Linux will no longer be possible with an upcoming IBM Z firmware update. Problem: New IBM Z firmware requires signed bootable images to contain a trailing data block with a specific format. Solution: Add the trailing data block to the Linux kernel image. Reproduction: Apply latest firmware, perform IPL with Secure Boot enabled. Fix: available upstream with Upstream-ID: aa127a069ef312aca02b730d5137e1778d0c3ba7 Preventive:yes Date: 2022-10-27 Author:Peter Oberparleiter Component: kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1996071/+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 1996198] Re: Fix rfkill causing soft blocked wifi
This bug is awaiting verification that the linux-lowlatency- hwe-5.19/5.19.0-1017.18~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-lowlatency-hwe-5.19 -- 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/1996198 Title: Fix rfkill causing soft blocked wifi Status in linux package in Ubuntu: In Progress Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Focal: Fix Released Status in linux-oem-6.0 source package in Focal: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: [Impact] Need this patch in so a BIOS upgrade won't cause issues on HP laptops. commit 1598bfa8e1faa932de42e1ee7628a1c4c4263f0a Author: Jorge Lopez Date: Fri Oct 28 10:55:27 2022 -0500 platform/x86: hp_wmi: Fix rfkill causing soft blocked wifi After upgrading BIOS to U82 01.02.01 Rev.A, the console is flooded strange char "^@" which printed out every second and makes login nearly impossible. Also the below messages were shown both in console and journal/dmesg every second: usb 1-3: Device not responding to setup address. usb 1-3: device not accepting address 4, error -71 usb 1-3: device descriptor read/all, error -71 usb usb1-port3: unable to enumerate USB device Wifi is soft blocked by checking rfkill. When unblocked manually, after few seconds it would be soft blocked again. So I was suspecting something triggered rfkill to soft block wifi. At the end it was fixed by removing hp_wmi module. The root cause is the way hp-wmi driver handles command 1B on post-2009 BIOS. In pre-2009 BIOS, command 1Bh return 0x4 to indicate that BIOS no longer controls the power for the wireless devices. Signed-off-by: Jorge Lopez Link: https://bugzilla.kernel.org/show_bug.cgi?id=216468 Reviewed-by: Mario Limonciello Link: https://lore.kernel.org/r/20221028155527.7724-1-jorge.lop...@hp.com Cc: sta...@vger.kernel.org Reviewed-by: Hans de Goede Signed-off-by: Hans de Goede [Test case] test on a HP laptop with the new BIOS [Where problems could occur] from the commit: * In pre-2009 BIOS, command 1Bh return 0x4 to indicate that * BIOS no longer controls the power for the wireless * devices. All features supported by this command will no * longer be supported. anyone running a laptop with obsolete pre-2009 BIOS probably won't notice the missing feature at this point. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996198/+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 1996198] Re: Fix rfkill causing soft blocked wifi
This bug is awaiting verification that the linux- aws-5.19/5.19.0-1019.20~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-aws-5.19 -- 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/1996198 Title: Fix rfkill causing soft blocked wifi Status in linux package in Ubuntu: In Progress Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Focal: Fix Released Status in linux-oem-6.0 source package in Focal: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: [Impact] Need this patch in so a BIOS upgrade won't cause issues on HP laptops. commit 1598bfa8e1faa932de42e1ee7628a1c4c4263f0a Author: Jorge Lopez Date: Fri Oct 28 10:55:27 2022 -0500 platform/x86: hp_wmi: Fix rfkill causing soft blocked wifi After upgrading BIOS to U82 01.02.01 Rev.A, the console is flooded strange char "^@" which printed out every second and makes login nearly impossible. Also the below messages were shown both in console and journal/dmesg every second: usb 1-3: Device not responding to setup address. usb 1-3: device not accepting address 4, error -71 usb 1-3: device descriptor read/all, error -71 usb usb1-port3: unable to enumerate USB device Wifi is soft blocked by checking rfkill. When unblocked manually, after few seconds it would be soft blocked again. So I was suspecting something triggered rfkill to soft block wifi. At the end it was fixed by removing hp_wmi module. The root cause is the way hp-wmi driver handles command 1B on post-2009 BIOS. In pre-2009 BIOS, command 1Bh return 0x4 to indicate that BIOS no longer controls the power for the wireless devices. Signed-off-by: Jorge Lopez Link: https://bugzilla.kernel.org/show_bug.cgi?id=216468 Reviewed-by: Mario Limonciello Link: https://lore.kernel.org/r/20221028155527.7724-1-jorge.lop...@hp.com Cc: sta...@vger.kernel.org Reviewed-by: Hans de Goede Signed-off-by: Hans de Goede [Test case] test on a HP laptop with the new BIOS [Where problems could occur] from the commit: * In pre-2009 BIOS, command 1Bh return 0x4 to indicate that * BIOS no longer controls the power for the wireless * devices. All features supported by this command will no * longer be supported. anyone running a laptop with obsolete pre-2009 BIOS probably won't notice the missing feature at this point. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996198/+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 1996536] Re: selftests/.../nat6to4 breaks the selftests build
This bug is awaiting verification that the linux- aws-5.19/5.19.0-1019.20~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-aws-5.19 verification-needed-jammy -- 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/1996536 Title: selftests/.../nat6to4 breaks the selftests build Status in linux package in Ubuntu: Fix Committed Status in linux source package in Kinetic: Fix Released Status in linux source package in Lunar: Fix Committed Bug description: Unused test program tools/testing/selftests/net/bpf/nat6to4 cannot easily be built in the standard Ubuntu kernel build environment. The "tools/testing/selftests/" are not built at all by Ubuntu kernel package builds, but are part of my build-test workflow, which is interrupted by this breakage. This mainline bpf selftest (nat6to4) requires additional package dependencies not satisfied by the Ubuntu kernel Build-depends and unsatisfiable when cross compilers are installed. Disable it to allow the rest of selftests/ to build. [Impact] * No impact on Ubuntu kernel package builds. [Test Case] * Allows internal (manual) testing of the `fakeroot debian/rules compileselftests` build target. [Regression Potential] * None. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996536/+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 1996536] Re: selftests/.../nat6to4 breaks the selftests build
This bug is awaiting verification that the linux-lowlatency- hwe-5.19/5.19.0-1017.18~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-lowlatency-hwe-5.19 -- 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/1996536 Title: selftests/.../nat6to4 breaks the selftests build Status in linux package in Ubuntu: Fix Committed Status in linux source package in Kinetic: Fix Released Status in linux source package in Lunar: Fix Committed Bug description: Unused test program tools/testing/selftests/net/bpf/nat6to4 cannot easily be built in the standard Ubuntu kernel build environment. The "tools/testing/selftests/" are not built at all by Ubuntu kernel package builds, but are part of my build-test workflow, which is interrupted by this breakage. This mainline bpf selftest (nat6to4) requires additional package dependencies not satisfied by the Ubuntu kernel Build-depends and unsatisfiable when cross compilers are installed. Disable it to allow the rest of selftests/ to build. [Impact] * No impact on Ubuntu kernel package builds. [Test Case] * Allows internal (manual) testing of the `fakeroot debian/rules compileselftests` build target. [Regression Potential] * None. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996536/+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 1999094] Re: mm:vma05 in ubuntu_ltp fails with '[vdso] bug not patched' on kinetic/linux 5.19.0-27.28
This bug is awaiting verification that the linux-lowlatency- hwe-5.19/5.19.0-1017.18~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-lowlatency-hwe-5.19 -- 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/1999094 Title: mm:vma05 in ubuntu_ltp fails with '[vdso] bug not patched' on kinetic/linux 5.19.0-27.28 Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Kinetic: Fix Released Bug description: This test fails on 5.19.0-27.28 in cycle 2022.11.14 on most if not all instances. Running tests... vma05 1 TINFO: timeout per run is 0h 5m 0s vma05 1 TFAIL: [vdso] bug not patched vma05 2 TINFO: AppArmor enabled, this may affect test results vma05 2 TINFO: it can be disabled with TST_DISABLE_APPARMOR=1 (requires super/root) vma05 2 TINFO: loaded AppArmor profiles: none Looking at the contents of the triggered backtrace, on 5.19.0-26 the contents look like this: vma05 1 TPASS: [vsyscall] reported correctly vma05 1 TINFO: TRACE=Reading symbols from vma05_vdso... [New LWP 418325] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `vma05_vdso'. Program terminated with signal SIGSEGV, Segmentation fault. #0 __pthread_kill_implementation (no_tid=0, signo=11, threadid=) at ./nptl/pthread_kill.c:44 Thread 1 (Thread 0x7f3093c4e740 (LWP 418325)): #0 __pthread_kill_implementation (no_tid=0, signo=11, threadid=) at ./nptl/pthread_kill.c:44 #1 __pthread_kill_internal (signo=11, threadid=) at ./nptl/pthread_kill.c:78 #2 __GI___pthread_kill (threadid=, signo=signo@entry=11) at ./nptl/pthread_kill.c:89 #3 0x7f3093a3bc46 in __GI_raise (sig=sig@entry=11) at ../sysdeps/posix/raise.c:26 #4 0x55f54287a072 in main () at vma05_vdso.c:5 vma05 1 TPASS: [vdso] backtrace complete -- while on 5.19.0-27.28 it looks like this: vma05 1 TINFO: TRACE=Reading symbols from vma05_vdso... [New LWP 1501] Core was generated by `vma05_vdso'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x7f9b3c09226b in ?? () Thread 1 (LWP 1501): #0 0x7f9b3c09226b in ?? () Backtrace stopped: Cannot access memory at address 0x7ffc216242b0 vma05 1 TFAIL: [vdso] bug not patched vma05 2 TINFO: AppArmor enabled, this may affect test results vma05 2 TINFO: it can be disabled with TST_DISABLE_APPARMOR=1 (requires super/root) vma05 2 TINFO: loaded AppArmor profiles: none Suggesting that this bug has somehow been reintroduced. Will look into this further. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1999094/+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 2002679] Re: Unset versioned gcc-12 for hwe-5.19 build
This bug is awaiting verification that the linux-lowlatency- hwe-5.19/5.19.0-1017.18~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-lowlatency-hwe-5.19 -- 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/2002679 Title: Unset versioned gcc-12 for hwe-5.19 build Status in linux-hwe-5.19 package in Ubuntu: Invalid Status in linux-hwe-5.19 source package in Jammy: Fix Committed Bug description: [ Impact ] In order to use the same compiler as used for kinetic:linux (gcc-12) we have made some changes to explicitly compile jammy:linux-hwe-5.19 with the same compiler. These changes were mainly part of bug 1999750 and bug 1991664. However, such changes are breaking the build of a number of dkms packages. [ Fix ] The proposed temporary workaround is to revert commit "UBUNTU: [Packaging] use versioned gcc-12", which would make the kernel compile with the default GCC in Jammy (gcc-11), while a proper solution is being worked on. [ Where problems could occur ] gcc-12 is necessary to enable some of the new security-related kernel configs, so going back to gcc-11 will disable such features. However, this would not regress users when upgrading from the generic kernel to hwe-5.19 in Jammy. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2002679/+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 1999094] Re: mm:vma05 in ubuntu_ltp fails with '[vdso] bug not patched' on kinetic/linux 5.19.0-27.28
This bug is awaiting verification that the linux- aws-5.19/5.19.0-1019.20~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-aws-5.19 verification-needed-jammy -- 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/1999094 Title: mm:vma05 in ubuntu_ltp fails with '[vdso] bug not patched' on kinetic/linux 5.19.0-27.28 Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Kinetic: Fix Released Bug description: This test fails on 5.19.0-27.28 in cycle 2022.11.14 on most if not all instances. Running tests... vma05 1 TINFO: timeout per run is 0h 5m 0s vma05 1 TFAIL: [vdso] bug not patched vma05 2 TINFO: AppArmor enabled, this may affect test results vma05 2 TINFO: it can be disabled with TST_DISABLE_APPARMOR=1 (requires super/root) vma05 2 TINFO: loaded AppArmor profiles: none Looking at the contents of the triggered backtrace, on 5.19.0-26 the contents look like this: vma05 1 TPASS: [vsyscall] reported correctly vma05 1 TINFO: TRACE=Reading symbols from vma05_vdso... [New LWP 418325] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `vma05_vdso'. Program terminated with signal SIGSEGV, Segmentation fault. #0 __pthread_kill_implementation (no_tid=0, signo=11, threadid=) at ./nptl/pthread_kill.c:44 Thread 1 (Thread 0x7f3093c4e740 (LWP 418325)): #0 __pthread_kill_implementation (no_tid=0, signo=11, threadid=) at ./nptl/pthread_kill.c:44 #1 __pthread_kill_internal (signo=11, threadid=) at ./nptl/pthread_kill.c:78 #2 __GI___pthread_kill (threadid=, signo=signo@entry=11) at ./nptl/pthread_kill.c:89 #3 0x7f3093a3bc46 in __GI_raise (sig=sig@entry=11) at ../sysdeps/posix/raise.c:26 #4 0x55f54287a072 in main () at vma05_vdso.c:5 vma05 1 TPASS: [vdso] backtrace complete -- while on 5.19.0-27.28 it looks like this: vma05 1 TINFO: TRACE=Reading symbols from vma05_vdso... [New LWP 1501] Core was generated by `vma05_vdso'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x7f9b3c09226b in ?? () Thread 1 (LWP 1501): #0 0x7f9b3c09226b in ?? () Backtrace stopped: Cannot access memory at address 0x7ffc216242b0 vma05 1 TFAIL: [vdso] bug not patched vma05 2 TINFO: AppArmor enabled, this may affect test results vma05 2 TINFO: it can be disabled with TST_DISABLE_APPARMOR=1 (requires super/root) vma05 2 TINFO: loaded AppArmor profiles: none Suggesting that this bug has somehow been reintroduced. Will look into this further. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1999094/+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 1786013] Autopkgtest regression report (linux-restricted-modules-hwe-5.19/5.19.0-31.32~22.04.1)
All autopkgtests for the newly accepted linux-restricted-modules-hwe-5.19 (5.19.0-31.32~22.04.1) for jammy have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-515/515.86.01-0ubuntu0.22.04.1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#linux-restricted-modules-hwe-5.19 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+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 2003714] Re: Azure: TDX enabled hyper-visors cause segfault
This bug is awaiting verification that the linux-azure/5.19.0-1020.21 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-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-kinetic-linux-azure verification-needed-kinetic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/2003714 Title: Azure: TDX enabled hyper-visors cause segfault Status in linux-azure package in Ubuntu: In Progress Bug description: SRU Justification [Impact] Microsoft TDX enabled hyper visors cause a segfault due to an upstream glibc bug. This can be worked around with a kernel patch. Issue Description: When I start an Intel TDX Ubuntu 22.04 (or RHEL 9.0) guest on Hyper-V, the guest always hits segfaults and can’t boot up. Here the kernel running in the guest is the upstream kernel + my TDX patchset, or the 5.19.0-azure kernel + the same TDX patchset: [Fix] We confirmed the segfault also happens to TDX guests on the KVM hypervisor. After I checked with more Intel folks, it turns out this is indeed a glibc bug (https://sourceware.org/bugzilla/show_bug.cgi?id=28784), which has been fixed in the upsteram glibc, but Ubuntu 22.04 and newer haven’t picked up the glibc fix yet. I got a kernel side temporary workarouond from Intel: https://github.com/dcui/tdx/commit/16218cf73491e867fd39c16c9e4b8aa926cbda68, which is on the same existing branch “decui/upstream- kinetic-22.10/master-next/1209”. [ 21.081453] Run /inits init process [ 21.086896] with arguments: [ 21.095790] /init [ 21.100982] with environment: [ 21.106611] HOME=/ [ 21.112463] TERM=linux [ 21.119850] BOOT_IMAGE=/boot/vmlinuz-6.1.0-rc7-decui+ Loading, please wait... Starting version 249.11-0ubuntu3.6 [ 21.253908] udevadm[144]: segfault at 56538d61e0c0 ip 7f8f5899efeb sp 7ffd08fb7648 error 6 in libc.so.6[7f8f5882+195000] likely on CPU 0 (core 0, socket 0) [ 21.316549] Code: 07 62 e1 7d 48 e7 4f 01 62 e1 7d 48 e7 67 40 62 e1 7d 48 e7 6f 41 62 61 7d 48 e7 87 00 20 00 00 62 61 7d 48 e7 8f 40 20 00 00 <62> 61 7d 48 e7 a7 00 30 00 00 62 61 7d 48 e7 af 40 30 00 00 48 83 Segmentation fault [ 22.499317] setfont[153]: segfault at 55ef3b91b000 ip 7f5899899fa4 sp 7ffc8008f628 error 4 in libc.so.6[7f589971b000+195000] likely on CPU 0 (core 0, socket 0) [ 22.602677] Code: 06 62 e1 fe 48 6f 4e 01 62 e1 fe 48 6f 66 40 62 e1 fe 48 6f 6e 41 62 61 fe 48 6f 86 00 20 00 00 62 61 fe 48 6f 8e 40 20 00 00 <62> 61 fe 48 6f a6 00 30 00 00 62 61 fe 48 6f ae 40 30 00 00 48 83 [ 22.732413] loadkeys[156]: segfault at 563ffe292000 ip 7fbff957afa4 sp 7ffe31453808 error 4 in libc.so.6[7fbff93fc000+195000] likely on CPU 0 (core 0, socket 0) [ 22.833061] Code: 06 62 e1 fe 48 6f 4e 01 62 e1 fe 48 6f 66 40 62 e1 fe 48 6f 6e 41 62 61 fe 48 6f 86 00 20 00 00 62 61 fe 48 6f 8e 40 20 00 00 <62> 61 fe 48 6f a6 00 30 00 00 62 61 fe 48 6f ae 40 30 00 00 48 83 The segfault only happens to recent glibc versions (e.g. v2.35 in Ubuntu 22.04, and v2.34 in RHEL 9.0). It doesn’t happens to v2.31 in Ubuntu 20.04, or v2.32 in Ubuntu 20.10. So something in glibc must have changed between v2.32 (good) and 2.34+ (not working for TDX). The oddity is: when I run the same Ubuntu 22.04/RHEL 9.0 image as a regular non-TDX guest, the segfault never happens. If I boot up a Ubuntu 20.04 TDX guest (which works fine), mount a Ubuntu 22.04 VHD image (“mount /dev/sdd1 /mnt”) and try to run “chroot /mnt”, I hit the same segfault: [ 109.478556] EXT4-fs (sdd1): mounted filesystem with ordered data mode. Quota mode: none. [ 129.22] bash[2112]: segfault at 556987854000 ip 7f88468c4ea4 sp 7ffc22ecf158 error 6 in libc.so.6[7f8846828000+195000] likely on CPU 48 (core 0, socket 48) [ 129.242434] Code: e7 bf 30 10 00 00 66 44 0f e7 87 00 20 00 00 66 44 0f e7 8f 10 20 00 00 66 44 0f e7 97 20 20 00 00 66 44 0f e7 9f 30 20 00 00 <66> 44 0f e7 a7 00 30 00 00 66 44 0f e7 af 10 30 00 00 66 44 0f e7 It looks like the application is referencing a memory location that somehow triggers a page fault, which is converted to a sigal SIGSEGV, which causes a segfault and terminates the application (I’m not sure where the below “movntdq” instructions come from): root@decui-u2004-u28:/opt/linus-0824# echo 'Code: e7 bf 30 10 00 00 66 44 0f e7 87 00 20 00
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-restricted-modules-hwe-5.19/5.19.0-31.32~22.04.1)
All autopkgtests for the newly accepted linux-restricted-modules-hwe-5.19 (5.19.0-31.32~22.04.1) for jammy have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-515/515.86.01-0ubuntu0.22.04.1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#linux-restricted-modules-hwe-5.19 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+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 1928855] Re: Please test secure-boot and lockdown on the early 5.13 kernel (s390x)
** 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/1928855 Title: Please test secure-boot and lockdown on the early 5.13 kernel (s390x) Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: The Ubuntu kernel team is working on a kernel 5.13 for impish (which is also supposed to be the target kernel version for impish) and has builds ready for early testing of the secure boot and lockdown functionality. Before this kernel will be moved to the official Ubuntu impish archive, tests are needed from IBM for s390x. The build is located at: https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/unstable/ https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/unstable/+packages (watch out for "linux-signed-unstable - 5.13...") And the PPA key used for signing can be found within the tarballs here: http://ppa.launchpad.net/canonical-kernel- team/unstable/ubuntu/dists/impish/main/signed/linux- unstable-s390x/5.13.0-3.3/signed.tar.gz (Please notice that this kernel is coming from the kernel teams PPA, and is with that not signed with the regular archive/release key, but instead with the above PPA signing key.) It would be ideal if the testing could be done within the next two weeks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1928855/+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 2004262] Re: Intel E810 NICs driver in causing hangs when booting and bonds configured
** Summary changed: - Intel E810 NICs driver in causinghangs when booting and bonds configured + Intel E810 NICs driver in causing hangs when booting and bonds configured -- 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/2004262 Title: Intel E810 NICs driver in causing hangs when booting and bonds configured Status in linux package in Ubuntu: Incomplete Bug description: jammy 22.04.1 linux-image-generic 5.15.0-58-generic Intel E810-XXV Dual Port NICs in Dell PowerEdge 650 After beonding is enabled on switch and server side, the system will hang at initialing ubuntu. The kernel loads but around starting the Network Services the system can hang for sometimes 5 minutes, and in other cases, indefinitely. The message of: echo 0 > /proc/sys/kernel/hung_task_timeout_sec” systemd-resolve blocked for more than 120 seconds appears, and eventually the Network services just attempts to start and never does. This is with or without DHCP enabled. Tried this same setup with the hwe-22.04, hwe-20.04, hwe-22.04-ege and linux-oem kernels and all exhibit the same failure. To work around this. installing the Intel 'ice' driver of version 1.10.1.2.2 works. The system doesn't even remotely hang at startup and all networking functions remain working (ping, DNS, general accessibility). The driver can be found at https://downloadmirror.intel.com/763930/ice-1.10.1.2.2.tar.gz --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 31 13:08 seq crw-rw 1 root audio 116, 33 Jan 31 13:08 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5json: { "result": "skip" } DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-01-27 (3 days ago) InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Dell Inc. PowerEdge R650 Package: linux (not installed) PciMultimedia: ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic root=UUID=668aab7c-abe9-434b-a810-acc6eab76cbc ro fsck.mode=skip ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 RelatedPackageVersions: linux-restricted-modules-5.15.0-58-generic N/A linux-backports-modules-5.15.0-58-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.9 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: jammy uec-images Uname: Linux 5.15.0-58-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 09/14/2022 dmi.bios.release: 1.8 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.2 dmi.board.name: 0PJ7YJ dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.2:bd09/14/2022:br1.8:svnDellInc.:pnPowerEdgeR650:pvr:rvnDellInc.:rn0PJ7YJ:rvrA01:cvnDellInc.:ct23:cvr:skuSKU=0912;ModelName=PowerEdgeR650: dmi.product.family: PowerEdge dmi.product.name: PowerEdge R650 dmi.product.sku: SKU=0912;ModelName=PowerEdge R650 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2004262/+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 1998244] Re: kselftest net/fib_nexthop_nongw.sh fails
** Changed in: linux-kvm (Ubuntu Jammy) Status: Confirmed => Fix Committed ** Changed in: linux-kvm (Ubuntu Kinetic) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1998244 Title: kselftest net/fib_nexthop_nongw.sh fails Status in linux-kvm package in Ubuntu: Confirmed Status in linux-kvm source package in Jammy: Fix Committed Status in linux-kvm source package in Kinetic: Fix Committed Status in linux-kvm source package in Lunar: Confirmed Bug description: 18272 03:33:07 DEBUG| Persistent state client._record_indent now set to 2 18273 03:33:07 DEBUG| Persistent state client.unexpected_reboot now set to ('ubuntu_kernel_selftests.net:fib_nexthop_nongw.sh', 'ubuntu_kernel_selftests.net:fib_nexthop_nongw.sh') 18274 03:33:07 DEBUG| Waiting for pid 58525 for 2700 seconds 18275 03:33:07 WARNI| System python is too old, crash handling disabled 18276 03:33:07 DEBUG| Running 'make run_tests -C net TEST_PROGS=fib_nexthop_nongw.sh TEST_GEN_PROGS='' TEST_CUSTOM_PROGS=''' 18277 03:33:07 DEBUG| [stdout] make: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net' 18278 03:33:07 DEBUG| [stdout] make --no-builtin-rules ARCH=x86 -C ../../../.. headers_install 18279 03:33:07 DEBUG| [stdout] make[1]: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux' 18280 03:33:08 DEBUG| [stdout] INSTALL ./usr/include 18281 03:33:08 DEBUG| [stdout] make[1]: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux' 18282 03:33:08 DEBUG| [stdout] TAP version 13 18283 03:33:08 DEBUG| [stdout] 1..1 18284 03:33:08 DEBUG| [stdout] # selftests: net: fib_nexthop_nongw.sh 18285 03:33:08 DEBUG| [stdout] # Error: Unknown device type. 18286 03:33:08 DEBUG| [stdout] # Cannot find device "eth0" 18287 03:33:08 DEBUG| [stdout] # Cannot find device "eth0" 18288 03:33:08 DEBUG| [stdout] # TEST: nexthop: get route with nexthop without gw[ OK ] 18289 03:33:18 DEBUG| [stdout] # TEST: nexthop: ping through nexthop without gw [FAIL] 18290 03:33:18 DEBUG| [stdout] not ok 1 selftests: net: fib_nexthop_nongw.sh # exit=1 18291 03:33:18 DEBUG| [stdout] make: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net' -- SRU Justification: [Impact] * Without Kernel support for the Dummy net driver, it is not possible to successfully run selftests that use it. This includes as per this bug net/fib_nexthop_nongw.sh, but also could potentially include other such as rtnetlink.sh, fib_rule_tests.sh, forwarding/* etc. [Fix] * Custom patch to enable CONFIG_DUMMY=m [Test Plan] * Before the fix, the net/fib_nexthop_nongw.sh script will fail in the specific line which does $ ip -n h1 link add name eth0 type dummy Error: Unknown device type. After the fix it does not fail. [Where problems could occur] * The regression can be considered as low, since we are adding functionality not previously present. [Other Info] * There does not seem to be a historical reason for removing it from linux-kvm. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1998244/+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 1175465] Re: Alcor AU9520 not recognized by libccid > 1.4.2
Po-Hsu Lin, no progress with Ubuntu 22.04 LTS? -- 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/1175465 Title: Alcor AU9520 not recognized by libccid > 1.4.2 Status in ccid package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: CID: 201205-11052 (Pavilion Slimline S5 Pavilion P6) With this card reader: 058f:6362 Alcor Micro Corp. Flash Card Reader/Writer Steps: 1. Insert a MMC/SD/SDHC card. 2. (The file browser will pop out.) 3. Remove the pre-inserted card. Expected Results: 1. The card will be removed from the /media, the icon will disappear from the launcher. 2. Open a file browser, and it's not in the devices section of the left column. Actual Results: 1. The card will be removed from the /media, the icon will disappear. 2. It still listed in the devices section, if you click on it in the file browser, an error pops, telling you the device was not found, and the disappears from the left column of the file browser. The reason seems to be the eject event is not being sent through dbus. Will try update later to see if it can be solved. The eject event is not being sent through dbus ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.5.0-23-generic 3.5.0-23.35~precise1 ProcVersionSignature: Ubuntu 3.5.0-23.35~precise1-generic 3.5.7.2 Uname: Linux 3.5.0-23-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25. AplayDevices: List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: STAC92xx Analog [STAC92xx Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 ApportVersion: 2.0.1-0ubuntu17.1 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: STAC92xx Analog [STAC92xx Analog] Subdevices: 2/2 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1547 F pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xf7d0 irq 50' Mixer name : 'IDT 92HD73E1X5' Components : 'HDA:111d7676,103c2ada,00100103' Controls : 39 Simple ctrls : 21 Date: Thu May 2 02:11:18 2013 HibernationDevice: RESUME=UUID=0059822b-2011-4dbc-aea6-3e1aff45462e InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130213) IwConfig: eth0 no wireless extensions. lono wireless extensions. MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-23-generic root=UUID=c6420b34-c860-4df2-99fd-9fa1a0b893b7 ro quiet splash initcall_debug vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.5.0-23-generic N/A linux-backports-modules-3.5.0-23-generic N/A linux-firmware1.79.1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/29/2013 dmi.bios.vendor: AMI dmi.bios.version: 00.05 dmi.board.name: 2ADA dmi.board.vendor: Hewlett-Packard dmi.board.version: PVT dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAMI:bvr00.05:bd03/29/2013:svnHewlett-Packard:pn:pvr:rvnHewlett-Packard:rn2ADA:rvrPVT:cvnHewlett-Packard:ct3:cvr: dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ccid/+bug/1175465/+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 2002285] Re: Alder Lake N-Series Enablement
Test kernel: https://kernel.ubuntu.com/~mhcerri/test/lp2002285/jammy- intel-iotg-alder-lake-adl-n.tar.xz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-iotg in Ubuntu. https://bugs.launchpad.net/bugs/2002285 Title: Alder Lake N-Series Enablement Status in linux-intel-iotg package in Ubuntu: New Bug description: [Summary] Alder Lake N-Series Enablement To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-intel-iotg/+bug/2002285/+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 1990849] Re: LXD containers using shiftfs on ZFS or TMPFS broken on 5.15.0-48.54
https://lists.ubuntu.com/archives/kernel-team/2023-January/136731.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1990849 Title: LXD containers using shiftfs on ZFS or TMPFS broken on 5.15.0-48.54 Status in linux package in Ubuntu: Confirmed Status in zfs-linux package in Ubuntu: Confirmed Status in linux source package in Jammy: Confirmed Status in zfs-linux source package in Jammy: Confirmed Status in linux source package in Kinetic: Confirmed Status in zfs-linux source package in Kinetic: Confirmed Status in linux source package in Lunar: Confirmed Status in zfs-linux source package in Lunar: Confirmed Bug description: Since 5.15.0-48.54 LXD containers using shiftfs ontop of ZFS or TMPFS are broken. Reproducer steps: ``` sudo snap install lxd sudo snap set lxd shiftfs.enable=true sudo lxd init --auto lxc storage create zfs zfs lxc launch images:ubuntu/jammy c1 -s zfs lxc exec c1 -- touch /root/foo touch: cannot touch '/root/foo': Value too large for defined data type ``` Expected result can be achieved by disabling shiftfs: ``` sudo snap set lxd shiftfs.enable=false sudo systemctl reload snap.lxd.daemon lxc launch images:ubuntu/jammy c2 -s zfs lxc exec c2 -- touch /root/foo lxc exec c2 -- ls -la /root/foo -rw-r--r-- 1 root root 0 Sep 26 14:00 /root/foo ``` Kernel 5.15.0-47-generic does not exhibit this issue. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-48-generic 5.15.0-48.54 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2240 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Sep 26 14:55:52 2022 InstallationDate: Installed on 2022-03-04 (205 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220228) MachineType: LENOVO 20R1000RUS ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-48-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2021 dmi.bios.release: 1.34 dmi.bios.vendor: LENOVO dmi.bios.version: N2QET40W(1.34 ) dmi.board.asset.tag: Not Available dmi.board.name: 20R1000RUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.15 dmi.modalias: dmi:bvnLENOVO:bvrN2QET40W(1.34):bd04/15/2021:br1.34:efr1.15:svnLENOVO:pn20R1000RUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20R1000RUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20R1_BU_Think_FM_ThinkPadX1Carbon7th: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20R1000RUS dmi.product.sku: LENOVO_MT_20R1_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990849/+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 1968681] Re: rdpru in ubuntu_kvm_unit_tests failed on B-4.15 node riccioli with FAIL: RDPRU raises #UD
** Changed in: linux (Ubuntu Bionic) 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/1968681 Title: rdpru in ubuntu_kvm_unit_tests failed on B-4.15 node riccioli with FAIL: RDPRU raises #UD Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Bug description: [Impact] RDPRU, the Read Processor Register instruction of AMD Zen 2 processors is used to give access to some processor registers that are typically only accessible when the privilege level is zero. rdpru test in ubuntu_kvm_unit_tests is to check if the RDPRU instruction can be intercepted by the Hypervisor. Without this patchset, this test will fail on our AMD Zen 2 system "riccioli" with: FAIL: RDPRU raises #UD [Fix] * fb64f293 x86/cpufeatures: Add feature bit RDPRU on AMD * 0cb8410b kvm: svm: Intercept RDPRU We have these patches in newer releases already, only Bionic 4.15 requires this fix. The first patch needs to be backported with some context adjustment, the second can be cherry-picked. [Test] Test kernel can be found here: https://people.canonical.com/~phlin/kernel/lp-1968681-rdpru/ With the patched kernel, this rdpru test will pass on the target AMD Zen 2 system. $ sudo ./rdpru BUILD_HEAD=d6421940 timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 --no-reboot \ -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 \ -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel \ /tmp/tmp.XOMVxpyNnl -smp 1 -cpu max # -initrd /tmp/tmp.I2TbGXFiaZ enabling apic smp: waiting for 0 APs PASS: RDPRU raises #UD SUMMARY: 1 tests PASS rdpru (1 tests) And the rdpru flag will be available in cpuinfo: $ grep -o rdpru /proc/cpuinfo rdpru [Where problems could occur] This patchset will add a new feature bit RDPRU for AMD Zen 2. We can expect to see new issues coming up when using this bit in the future. [Original Bug Report] Issue found on B-ibm-gt-4.15.0-1116.127 This can be reproduced with B-4.15.0-175 as well. This failure is only visible on this node. Running '/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/tests/rdpru' BUILD_HEAD=16647354 timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 --no-reboot -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel /tmp/tmp.qGIR5tvTw1 -smp 1 -cpu max # -initrd /tmp/tmp.8JuYRCFRUi enabling apic FAIL: RDPRU raises #UD SUMMARY: 1 tests, 1 unexpected failures FAIL rdpru (1 tests, 1 unexpected failures) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1968681/+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 2003053] Re: NFS: client permission error after adding user to permissible group
** Changed in: linux (Ubuntu Bionic) 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/2003053 Title: NFS: client permission error after adding user to permissible group Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Kinetic: Fix Committed Status in linux source package in Lunar: In Progress Bug description: [Impact] The NFS client's access cache becomes stale due to the user's group membership changing on the server after the user has already logged in on the client. The access cache only expires if either NFS_INO_INVALID_ACCESS flag is on or timeout (without delegation). Adding a user to a group in the NFS server will not cause any file attributes to change. The client will encounter permission errors until other file attributes are changed or the memory cache is dropped. [Fix] The access cache shall be cleared once the user logs out and logs back in again. 0eb43812c0270ee3d005ff32f91f7d0a6c4943af NFS: Clear the file access cache upon login 029085b8949f5d269ae2bbd14915407dd0c7f902 NFS: Judge the file access cache's timestamp in rcu path 5e9a7b9c2ea18551759833146a181b14835bfe39 NFS: Fix up a sparse warning [Test Plan] 1.[client side] testuser is not part of testgroup testuser@kinetic:~$ ls -ld /mnt/private/ drwxrwx--- 2 root testgroup 4096 Nov 24 08:23 /mnt/private/ testuser@kinetic:~$ mktemp -p /mnt/private/ mktemp: failed to create file via template ‘/mnt/private/tmp.XX’: Permission denied 2.[server side] add testuser into testgroup, which has access to folder root@kinetic:~$ usermod -aG testgroup testuser && echo `date +'%s'` > /proc/net/rpc/auth.unix.gid/flush 3.[client side] create a file again but still fail testuser@kinetic:~$ mktemp -p /mnt/private/ mktemp: failed to create file via template ‘/mnt/private/tmp.XX’: Permission denied [Where problems could occur] The fix will apply upstream commits, so the regression can be considered as low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2003053/+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 1482304] Re: Upgrade i40e and i40evf driver to latest
** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released -- 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/1482304 Title: Upgrade i40e and i40evf driver to latest Status in linux package in Ubuntu: Fix Released Bug description: It appears that the latest i40e driver in Trusty is 0.3.36-k. We've been experiencing some kernel panics with this driver and have found that it looks like bringing the driver up to the latest 1.2.48 has alleviated some of the kernel panics on boot. Is this something we could look at getting upgraded to a more modern revision of the driver? Thanks Output of Panic (Using Intel x710) [3.143088] i40e :05:00.0 p1p1: NIC Link is Up [3.301138] Switched to clocksource tsc [6.216639] random: nonblocking pool is initialized [8.934783] [ cut here ] [8.934805] WARNING: CPU: 0 PID: 0 at /build/buildd/linux-3.13.0/net/sched/sch_generic.c:264 dev_watchdog+0x276/0x280() [8.934808] NETDEV WATCHDOG: p1p1 (i40e): transmit queue 0 timed out [8.934828] Modules linked in: joydev hid_generic gpio_ich x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd serio_raw usbhid hid lpc_ich hpilo ioatdma dca ipmi_si shpchp wmi acpi_power_meter mac_hid lp parport psmouse i40e vxlan ip_tunnel ptp hpsa pps_core [8.934874] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 3.13.0-57-generic #95-Ubuntu [8.934877] Hardware name: HP ProLiant DL380 Gen9, BIOS P89 05/06/2015 [8.934878] 0009 88103fc03d98 817232f0 88103fc03de0 [8.934891] 88103fc03dd0 8106784d 881028d18000 [8.934895] 881023734f40 0040 88103fc03e30 [8.934904] Call Trace: [8.934905][] dump_stack+0x45/0x56 [8.934921] [] warn_slowpath_common+0x7d/0xa0 [8.934925] [] warn_slowpath_fmt+0x4c/0x50 [8.934928] [] dev_watchdog+0x276/0x280 [8.934935] [] ? dev_graft_qdisc+0x80/0x80 [8.934942] [] call_timer_fn+0x36/0x100 [8.934946] [] ? dev_graft_qdisc+0x80/0x80 [8.934950] [] run_timer_softirq+0x1ef/0x2f0 [8.934957] [] __do_softirq+0xec/0x2c0 [8.934961] [] irq_exit+0x105/0x110 [8.934971] [] smp_apic_timer_interrupt+0x45/0x60 [8.934976] [] apic_timer_interrupt+0x6d/0x80 [8.934977][] ? cpuidle_enter_state+0x52/0xc0 [8.934986] [] cpuidle_idle_call+0xb9/0x1f0 [8.934994] [] arch_cpu_idle+0xe/0x30 [8.935000] [] cpu_startup_entry+0xc5/0x290 [8.935008] [] rest_init+0x77/0x80 [8.935016] [] start_kernel+0x438/0x443 [8.935021] [] ? repair_env_string+0x5c/0x5c [8.935023] [] ? early_idt_handlers+0x120/0x120 [8.935027] [] x86_64_start_reservations+0x2a/0x2c [8.935030] [] x86_64_start_kernel+0x143/0x152 [8.935034] ---[ end trace fabec2b76d314b12 ]--- [8.935037] i40e :05:00.0 p1p1: tx_timeout recovery level 0 [8.935071] i40e :05:00.0: VSI reinit requested [8.945435] i40e :05:00.0 p1p1: NIC Link is Up [ 14.856689] i40e :05:00.0: Detected Tx Unit Hang [ 14.856689] VSI <518> [ 14.856689] Tx Queue <0> [ 14.856689] next_to_use <1> [ 14.856689] next_to_clean<0> [ 14.856697] i40e :05:00.0: tx_bi[next_to_clean] [ 14.856697] time_stamp [ 14.856697] jiffies [ 14.856699] i40e :05:00.0: tx hang detected on queue 0, resetting adapter [ 14.856701] i40e :05:00.0 p1p1: tx_timeout recovery level 1 [ 14.882582] i40e :05:00.0: i40e_ptp_init: added PHC on p1p1 [ 14.899577] i40e :05:00.0 p1p1: NIC Link is Up [ 14.899623] i40e :05:00.0: reset complete [ 24.928762] i40e :05:00.0 p1p1: tx_timeout recovery level 2 [ 25.876839] i40e :05:00.1: i40e_ptp_init: added PHC on p1p2 [ 25.889067] i40e :05:00.1: reset complete [ 25.917938] i40e :05:00.0: i40e_ptp_init: added PHC on p1p1 [ 25.934578] i40e :05:00.0 p1p1: NIC Link is Up [ 25.934621] i40e :05:00.0: reset complete To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1482304/+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 1596550] Re: Metadata corruption detected at xfs_attr3_leaf_write_verify+0xd7/0xf0
Closed as the kernel version is no longer in use ** Changed in: linux (Ubuntu) Status: Confirmed => 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/1596550 Title: Metadata corruption detected at xfs_attr3_leaf_write_verify+0xd7/0xf0 Status in linux package in Ubuntu: Invalid Bug description: We noticed a XFS metadata corruption once we ran a lot of small write IOs on SSDs in our OpenStack swift environment: [1468860.211158] XFS (sdax): Metadata corruption detected at xfs_attr3_leaf_write_verify+0xd7/0xf0 [xfs], block 0x7c99480 [1468860.211195] XFS (sdax): Unmount and run xfs_repair [1468860.211215] XFS (sdax): First 64 bytes of corrupted metadata buffer: [1468860.211247] 880630f66000: 00 00 00 00 00 00 00 00 fb ee 00 00 00 00 00 00 [1468860.211268] 880630f66010: 10 00 00 00 00 20 0f e0 00 00 00 00 00 00 00 00 . .. [1468860.211289] 880630f66020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [1468860.211309] 880630f66030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [1468860.211328] XFS (sdax): xfs_do_force_shutdown(0x8) called from line 1254 of file /build/linux-lts-xenial-7RlTta/linux-lts-xenial-4.4.0/fs/xfs/xfs_buf.c. Return address = 0x c068f616 [1468860.212214] XFS (sdax): Corruption of in-memory data detected. Shutting down filesystem [1468860.212232] XFS (sdax): Please umount the filesystem and rectify the problem(s) [1468860.212323] XFS (sdax): xfs_do_force_shutdown(0x1) called from line 315 of file /build/linux-lts-xenial-7RlTta/linux-lts-xenial-4.4.0/fs/xfs/xfs_trans_buf.c. Return address = 0xc06bdda2 [1468860.261436] XFS (sdax): xfs_log_force: error -5 returned. This error is reported with linux-generic-lts-xenial @4.4.0.22.12 on a XFS filesystem formatted with 1024 as inode size and mounted with rw,noatime,nodiratime,attr2,nobarrier,inode64,logbufs=8,sunit=512,swidth=512,noquota For us this issue seems to be reproducible after several hours of stress testing. cat /proc/version_signature Ubuntu 4.4.0-22.40~14.04.1-generic 4.4.8 Description:Ubuntu 14.04.3 LTS Release:14.04 --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 10 13:19 seq crw-rw 1 root audio 116, 33 Jun 10 13:19 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 14.04 IwConfig: Error: [Errno 2] No such file or directory MachineType: HP ProLiant DL380 Gen9 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic root=/dev/mapper/lxc-root00 ro biosdevname=1 net.ifnames=0 usbcore.autosuspend=-1 vga=normal nomodeset nomdmonddf nomdmonisw crashkernel=1024M-:128M ProcVersionSignature: Ubuntu 4.4.0-22.40~14.04.1-generic 4.4.8 RelatedPackageVersions: linux-restricted-modules-4.4.0-22-generic N/A linux-backports-modules-4.4.0-22-generic N/A linux-firmware1.127.15 RfKill: Error: [Errno 2] No such file or directory Tags: trusty Uname: Linux 4.4.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 07/20/2015 dmi.bios.vendor: HP dmi.bios.version: P89 dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP89:bd07/20/2015:svnHP:pnProLiantDL380Gen9:pvr:cvnHP:ct23:cvr: dmi.product.name: ProLiant DL380 Gen9 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1596550/+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 1993718] Re: Promote to restricted: broadcom-sta & bcmwl are duplicates
Removing packages from lunar: bcmwl 6.30.223.271+bdcom-0ubuntu10 in lunar bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu10 in lunar amd64 Comment: Superseded by broadcom-sta; LP: #1993718 1 package successfully removed. ** Changed in: bcmwl (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1993718 Title: Promote to restricted: broadcom-sta & bcmwl are duplicates Status in bcmwl package in Ubuntu: Fix Released Status in broadcom-sta package in Ubuntu: Fix Released Bug description: Ubuntu archive please promote broadcom-sta from multiverse to restricted. After that's done and migrates, we will be able to remove bcmwl from the archive. --- broadcom-sta & bcmwl are duplicates of each other. One is packaged and maintained by archlinux/debian the other one was our self packaged one. We should merge the two. On the surface the source code is the same, there is slightly better dkms packaging on the broadcom-sta package. However it is missing modaliases stanzas. I think we should port the modaliases to the new package, and remove the old one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1993718/+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 1993718] Re: Promote to restricted: broadcom-sta & bcmwl are duplicates
This has been promoted. ** Changed in: broadcom-sta (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1993718 Title: Promote to restricted: broadcom-sta & bcmwl are duplicates Status in bcmwl package in Ubuntu: Fix Released Status in broadcom-sta package in Ubuntu: Fix Released Bug description: Ubuntu archive please promote broadcom-sta from multiverse to restricted. After that's done and migrates, we will be able to remove bcmwl from the archive. --- broadcom-sta & bcmwl are duplicates of each other. One is packaged and maintained by archlinux/debian the other one was our self packaged one. We should merge the two. On the surface the source code is the same, there is slightly better dkms packaging on the broadcom-sta package. However it is missing modaliases stanzas. I think we should port the modaliases to the new package, and remove the old one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1993718/+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 2004262] Re: Intel E810 NICs driver in causinghangs when booting and bonds configured
Hi, The attached dmesg seems to be from a clean reboot and doesn't contain any information about the hangs. Is there any logs available from an affected boot that provides more information than the systemd-resolved hung task message? The systemd log messages would also help (e.g. 'journalctl -u systemd-resolved'). -- 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/2004262 Title: Intel E810 NICs driver in causinghangs when booting and bonds configured Status in linux package in Ubuntu: Incomplete Bug description: jammy 22.04.1 linux-image-generic 5.15.0-58-generic Intel E810-XXV Dual Port NICs in Dell PowerEdge 650 After beonding is enabled on switch and server side, the system will hang at initialing ubuntu. The kernel loads but around starting the Network Services the system can hang for sometimes 5 minutes, and in other cases, indefinitely. The message of: echo 0 > /proc/sys/kernel/hung_task_timeout_sec” systemd-resolve blocked for more than 120 seconds appears, and eventually the Network services just attempts to start and never does. This is with or without DHCP enabled. Tried this same setup with the hwe-22.04, hwe-20.04, hwe-22.04-ege and linux-oem kernels and all exhibit the same failure. To work around this. installing the Intel 'ice' driver of version 1.10.1.2.2 works. The system doesn't even remotely hang at startup and all networking functions remain working (ping, DNS, general accessibility). The driver can be found at https://downloadmirror.intel.com/763930/ice-1.10.1.2.2.tar.gz --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 31 13:08 seq crw-rw 1 root audio 116, 33 Jan 31 13:08 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5json: { "result": "skip" } DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-01-27 (3 days ago) InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Dell Inc. PowerEdge R650 Package: linux (not installed) PciMultimedia: ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic root=UUID=668aab7c-abe9-434b-a810-acc6eab76cbc ro fsck.mode=skip ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 RelatedPackageVersions: linux-restricted-modules-5.15.0-58-generic N/A linux-backports-modules-5.15.0-58-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.9 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: jammy uec-images Uname: Linux 5.15.0-58-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 09/14/2022 dmi.bios.release: 1.8 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.2 dmi.board.name: 0PJ7YJ dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.2:bd09/14/2022:br1.8:svnDellInc.:pnPowerEdgeR650:pvr:rvnDellInc.:rn0PJ7YJ:rvrA01:cvnDellInc.:ct23:cvr:skuSKU=0912;ModelName=PowerEdgeR650: dmi.product.family: PowerEdge dmi.product.name: PowerEdge R650 dmi.product.sku: SKU=0912;ModelName=PowerEdge R650 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2004262/+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 1990849] Re: LXD containers using shiftfs on ZFS or TMPFS broken on 5.15.0-48.54
** Also affects: linux (Ubuntu Lunar) Importance: Undecided Status: Confirmed ** Also affects: zfs-linux (Ubuntu Lunar) Importance: Undecided Status: Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1990849 Title: LXD containers using shiftfs on ZFS or TMPFS broken on 5.15.0-48.54 Status in linux package in Ubuntu: Confirmed Status in zfs-linux package in Ubuntu: Confirmed Status in linux source package in Jammy: Confirmed Status in zfs-linux source package in Jammy: Confirmed Status in linux source package in Kinetic: Confirmed Status in zfs-linux source package in Kinetic: Confirmed Status in linux source package in Lunar: Confirmed Status in zfs-linux source package in Lunar: Confirmed Bug description: Since 5.15.0-48.54 LXD containers using shiftfs ontop of ZFS or TMPFS are broken. Reproducer steps: ``` sudo snap install lxd sudo snap set lxd shiftfs.enable=true sudo lxd init --auto lxc storage create zfs zfs lxc launch images:ubuntu/jammy c1 -s zfs lxc exec c1 -- touch /root/foo touch: cannot touch '/root/foo': Value too large for defined data type ``` Expected result can be achieved by disabling shiftfs: ``` sudo snap set lxd shiftfs.enable=false sudo systemctl reload snap.lxd.daemon lxc launch images:ubuntu/jammy c2 -s zfs lxc exec c2 -- touch /root/foo lxc exec c2 -- ls -la /root/foo -rw-r--r-- 1 root root 0 Sep 26 14:00 /root/foo ``` Kernel 5.15.0-47-generic does not exhibit this issue. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-48-generic 5.15.0-48.54 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2240 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Sep 26 14:55:52 2022 InstallationDate: Installed on 2022-03-04 (205 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220228) MachineType: LENOVO 20R1000RUS ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-48-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2021 dmi.bios.release: 1.34 dmi.bios.vendor: LENOVO dmi.bios.version: N2QET40W(1.34 ) dmi.board.asset.tag: Not Available dmi.board.name: 20R1000RUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.15 dmi.modalias: dmi:bvnLENOVO:bvrN2QET40W(1.34):bd04/15/2021:br1.34:efr1.15:svnLENOVO:pn20R1000RUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20R1000RUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20R1_BU_Think_FM_ThinkPadX1Carbon7th: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20R1000RUS dmi.product.sku: LENOVO_MT_20R1_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990849/+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 1990849] Re: LXD containers using shiftfs on ZFS or TMPFS broken on 5.15.0-48.54
https://lists.ubuntu.com/archives/kernel-team/2023-January/136719.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1990849 Title: LXD containers using shiftfs on ZFS or TMPFS broken on 5.15.0-48.54 Status in linux package in Ubuntu: Confirmed Status in zfs-linux package in Ubuntu: Confirmed Status in linux source package in Jammy: Confirmed Status in zfs-linux source package in Jammy: Confirmed Status in linux source package in Kinetic: Confirmed Status in zfs-linux source package in Kinetic: Confirmed Status in linux source package in Lunar: Confirmed Status in zfs-linux source package in Lunar: Confirmed Bug description: Since 5.15.0-48.54 LXD containers using shiftfs ontop of ZFS or TMPFS are broken. Reproducer steps: ``` sudo snap install lxd sudo snap set lxd shiftfs.enable=true sudo lxd init --auto lxc storage create zfs zfs lxc launch images:ubuntu/jammy c1 -s zfs lxc exec c1 -- touch /root/foo touch: cannot touch '/root/foo': Value too large for defined data type ``` Expected result can be achieved by disabling shiftfs: ``` sudo snap set lxd shiftfs.enable=false sudo systemctl reload snap.lxd.daemon lxc launch images:ubuntu/jammy c2 -s zfs lxc exec c2 -- touch /root/foo lxc exec c2 -- ls -la /root/foo -rw-r--r-- 1 root root 0 Sep 26 14:00 /root/foo ``` Kernel 5.15.0-47-generic does not exhibit this issue. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-48-generic 5.15.0-48.54 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2240 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Sep 26 14:55:52 2022 InstallationDate: Installed on 2022-03-04 (205 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220228) MachineType: LENOVO 20R1000RUS ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-48-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2021 dmi.bios.release: 1.34 dmi.bios.vendor: LENOVO dmi.bios.version: N2QET40W(1.34 ) dmi.board.asset.tag: Not Available dmi.board.name: 20R1000RUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.15 dmi.modalias: dmi:bvnLENOVO:bvrN2QET40W(1.34):bd04/15/2021:br1.34:efr1.15:svnLENOVO:pn20R1000RUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20R1000RUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20R1_BU_Think_FM_ThinkPadX1Carbon7th: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20R1000RUS dmi.product.sku: LENOVO_MT_20R1_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990849/+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 2004349] [NEW] Display issues on Ubuntu 22.10
Public bug reported: System information: Ubuntu 22.10 x86_64 Kernel: 5.19.0-29-generic Hardware: Dell Inspiron 16 Plus 7620 CPU: Intel i7-12700H GPU: Intel Alder Lake-P GPU: NVIDIA GeForce RTX 3060 Mobile / Max-Q Issues: wayland - Display's native resolution of 3072x1920 (16:10) is unusable. The bottom of the screen creates artifacts every time I move my mouse there. Visually look like horizontal black lines and I am unable to use the bottom portion of the screen. - Using the system, some times the whole screen becomes frozen with graphical artifacts. it then resets, and apparently resumes to normal. Current workaround for both issues is to lower the resolution. Tested working ok with 2560x1600 (16:10) and 1920x122 (16:10) Xorg - If i turn off my internal display, the whole UI freezes. I need to drop to tty to reboot. Then after reboot, only internal display is working, and if I try to enable external display, I get an error reporting there might be an hardware problem. Tested with external display with multiple HDMI cables through a dell thunderbolt dock, and directly connected to laptop. - If i turn off my internal display and only use external display connected to HDMI, Gnome shell on secondary display connected via HDMI becomes very slow and laggy. I have a hard time reproducing this as the secondary display usually becomes unusable. Temporary workaround: Reverting to nvidia-graphics-drivers-515 solves all my issues. None of the issues reported above can be reproduced on 515. ** Affects: nvidia-graphics-drivers-525 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-525 in Ubuntu. https://bugs.launchpad.net/bugs/2004349 Title: Display issues on Ubuntu 22.10 Status in nvidia-graphics-drivers-525 package in Ubuntu: New Bug description: System information: Ubuntu 22.10 x86_64 Kernel: 5.19.0-29-generic Hardware: Dell Inspiron 16 Plus 7620 CPU: Intel i7-12700H GPU: Intel Alder Lake-P GPU: NVIDIA GeForce RTX 3060 Mobile / Max-Q Issues: wayland - Display's native resolution of 3072x1920 (16:10) is unusable. The bottom of the screen creates artifacts every time I move my mouse there. Visually look like horizontal black lines and I am unable to use the bottom portion of the screen. - Using the system, some times the whole screen becomes frozen with graphical artifacts. it then resets, and apparently resumes to normal. Current workaround for both issues is to lower the resolution. Tested working ok with 2560x1600 (16:10) and 1920x122 (16:10) Xorg - If i turn off my internal display, the whole UI freezes. I need to drop to tty to reboot. Then after reboot, only internal display is working, and if I try to enable external display, I get an error reporting there might be an hardware problem. Tested with external display with multiple HDMI cables through a dell thunderbolt dock, and directly connected to laptop. - If i turn off my internal display and only use external display connected to HDMI, Gnome shell on secondary display connected via HDMI becomes very slow and laggy. I have a hard time reproducing this as the secondary display usually becomes unusable. Temporary workaround: Reverting to nvidia-graphics-drivers-515 solves all my issues. None of the issues reported above can be reproduced on 515. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-525/+bug/2004349/+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 1933090] Re: systemd/245.4-4ubuntu3.6 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1
Still failing in Focal, for linux-oracle-5.15 this time. And it's been failing for some time now https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/s/systemd/20221206_050631_237a8@/log.gz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/1933090 Title: systemd/245.4-4ubuntu3.6 ADT test failure with linux- hwe-5.11/5.11.0-20.21~20.04.1 Status in linux-hwe-5.11 package in Ubuntu: Won't Fix Status in linux-hwe-5.15 package in Ubuntu: New Status in systemd package in Ubuntu: New Status in linux-hwe-5.11 source package in Focal: Won't Fix Status in linux-hwe-5.15 source package in Focal: New Status in systemd source package in Focal: New Bug description: This is a scripted bug report about ADT failures while running systemd tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/s/systemd/20210611_220645_bf5b6@/log.gz armhf: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/armhf/s/systemd/20210617_124738_5b554@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/s/systemd/20210611_235629_92856@/log.gz s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/s390x/s/systemd/20210611_214456_6427f@/log.gz In arm64, ppc64el and s390x, 'root-unittests' fails with: /* test_protect_sysctl */ Assertion 'errno == EFAULT' failed at src/test/test-seccomp.c:311, function test_protect_sysctl(). A borting. sysctlseccomp terminated by signal ABRT. Assertion 'wait_for_terminate_and_check("sysctlseccomp", pid, WAIT_LOG) == EXIT_SUCCESS' failed at s rc/test/test-seccomp.c:324, function test_protect_sysctl(). Aborting. FAIL: test-seccomp (code: 134) In amd64, 'upstream' also fails on 'TEST-24-UNIT-TESTS', which apparently is caused by the same 'test-seccomp.c:311' assertion failure. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1933090/+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 2004276] Re: package linux-intel-iotg-tools-common 5.15.0-1021.26 [modified: usr/share/man/man1/perf-annotate.1.gz usr/share/man/man1/perf-archive.1.gz usr/share/man/man1/perf-b
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-iotg in Ubuntu. https://bugs.launchpad.net/bugs/2004276 Title: package linux-intel-iotg-tools-common 5.15.0-1021.26 [modified: usr/share/man/man1/perf-annotate.1.gz usr/share/man/man1/perf- archive.1.gz usr/share/man/man1/perf-bench.1.gz usr/share/man/man1/perf-buildid-cache.1.gz usr/share/man/man1/perf- buildid-list.1.gz usr/share/man/man1/perf-c2c.1.gz usr/share/man/man1/perf-config.1.gz usr/share/man/man1/perf- daemon.1.gz usr/share/man/man1/perf-data.1.gz usr/share/man/man1/perf- diff.1.gz usr/share/man/man1/perf-dlfilter.1.gz usr/share/man/man1/perf-evlist.1.gz usr/share/man/man1/perf- ftrace.1.gz usr/share/man/man1/perf-help.1.gz usr/share/man/man1/perf- inject.1.gz usr/share/man/man1/perf-intel-pt.1.gz usr/share/man/man1/perf-iostat.1.gz usr/share/man/man1/perf- kallsyms.1.gz usr/share/man/man1/perf-kmem.1.gz usr/share/man/man1/perf-kvm.1.gz usr/share/man/man1/perf-list.1.gz usr/share/man/man1/perf-lock.1.gz usr/share/man/man1/perf-mem.1.gz usr/share/man/man1/perf-probe.1.gz usr/share/man/man1/perf-record.1.gz usr/share/man/man1/perf-report.1.gz usr/share/man/man1/perf-sched.1.gz usr/share/man/man1/perf-script-perl.1.gz usr/share/man/man1/perf- script-python.1.gz usr/share/man/man1/perf-script.1.gz usr/share/man/man1/perf-stat.1.gz usr/share/man/man1/perf-test.1.gz usr/share/man/man1/perf-timechart.1.gz usr/share/man/man1/perf- top.1.gz usr/share/man/man1/perf-trace.1.gz usr/share/man/man1/perf- version.1.gz usr/share/man/man1/perf.1.gz] failed to install/upgrade: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-tools-common 5.15.0-58.64 Status in linux-intel-iotg package in Ubuntu: New Bug description: Sometimes it appears the message... Thank you ProblemType: Package DistroRelease: Ubuntu 22.04 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass Date: Sat Jan 28 19:34:54 2023 ErrorMessage: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-tools-common 5.15.0-58.64 InstallationDate: Installed on 2022-07-24 (191 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 SourcePackage: linux-intel-iotg UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-intel-iotg/+bug/2004276/+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 2004276] [NEW] package linux-intel-iotg-tools-common 5.15.0-1021.26 [modified: usr/share/man/man1/perf-annotate.1.gz usr/share/man/man1/perf-archive.1.gz usr/share/man/man1/perf
Public bug reported: Sometimes it appears the message... Thank you ProblemType: Package DistroRelease: Ubuntu 22.04 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass Date: Sat Jan 28 19:34:54 2023 ErrorMessage: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-tools-common 5.15.0-58.64 InstallationDate: Installed on 2022-07-24 (191 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 SourcePackage: linux-intel-iotg UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-intel-iotg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy package-conflict third-party-packages -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-iotg in Ubuntu. https://bugs.launchpad.net/bugs/2004276 Title: package linux-intel-iotg-tools-common 5.15.0-1021.26 [modified: usr/share/man/man1/perf-annotate.1.gz usr/share/man/man1/perf- archive.1.gz usr/share/man/man1/perf-bench.1.gz usr/share/man/man1/perf-buildid-cache.1.gz usr/share/man/man1/perf- buildid-list.1.gz usr/share/man/man1/perf-c2c.1.gz usr/share/man/man1/perf-config.1.gz usr/share/man/man1/perf- daemon.1.gz usr/share/man/man1/perf-data.1.gz usr/share/man/man1/perf- diff.1.gz usr/share/man/man1/perf-dlfilter.1.gz usr/share/man/man1/perf-evlist.1.gz usr/share/man/man1/perf- ftrace.1.gz usr/share/man/man1/perf-help.1.gz usr/share/man/man1/perf- inject.1.gz usr/share/man/man1/perf-intel-pt.1.gz usr/share/man/man1/perf-iostat.1.gz usr/share/man/man1/perf- kallsyms.1.gz usr/share/man/man1/perf-kmem.1.gz usr/share/man/man1/perf-kvm.1.gz usr/share/man/man1/perf-list.1.gz usr/share/man/man1/perf-lock.1.gz usr/share/man/man1/perf-mem.1.gz usr/share/man/man1/perf-probe.1.gz usr/share/man/man1/perf-record.1.gz usr/share/man/man1/perf-report.1.gz usr/share/man/man1/perf-sched.1.gz usr/share/man/man1/perf-script-perl.1.gz usr/share/man/man1/perf- script-python.1.gz usr/share/man/man1/perf-script.1.gz usr/share/man/man1/perf-stat.1.gz usr/share/man/man1/perf-test.1.gz usr/share/man/man1/perf-timechart.1.gz usr/share/man/man1/perf- top.1.gz usr/share/man/man1/perf-trace.1.gz usr/share/man/man1/perf- version.1.gz usr/share/man/man1/perf.1.gz] failed to install/upgrade: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-tools-common 5.15.0-58.64 Status in linux-intel-iotg package in Ubuntu: New Bug description: Sometimes it appears the message... Thank you ProblemType: Package DistroRelease: Ubuntu 22.04 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass Date: Sat Jan 28 19:34:54 2023 ErrorMessage: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-tools-common 5.15.0-58.64 InstallationDate: Installed on 2022-07-24 (191 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 SourcePackage: linux-intel-iotg UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-intel-iotg/+bug/2004276/+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 2004051] Re: Kinetic update: upstream stable patchset 2023-01-27
Skipped "drm/amd/display: No display after resume from WB/CB" since it is already applied for bug #1999836. ** Changed in: linux (Ubuntu Kinetic) 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/2004051 Title: Kinetic update: upstream stable patchset 2023-01-27 Status in linux package in Ubuntu: Invalid Status in linux source package in Kinetic: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2023-01-27 Ported from the following upstream stable releases: v5.15.81, v6.0.11 v5.15.82, v6.0.12 from git://git.kernel.org/ ASoC: fsl_sai: use local device pointer serial: Add rs485_supported to uart_port serial: fsl_lpuart: Fill in rs485_supported x86/sgx: Create utility to validate user provided offset and length x86/sgx: Add overflow check in sgx_validate_offset_length() binder: validate alloc->mm in ->mmap() handler ceph: Use kcalloc for allocating multiple elements ceph: fix NULL pointer dereference for req->r_session wifi: mac80211: fix memory free error when registering wiphy fail wifi: mac80211_hwsim: fix debugfs attribute ps with rc table support riscv: dts: sifive unleashed: Add PWM controlled LEDs audit: fix undefined behavior in bit shift for AUDIT_BIT wifi: airo: do not assign -1 to unsigned char wifi: mac80211: Fix ack frame idr leak when mesh has no route wifi: ath11k: Fix QCN9074 firmware boot on x86 spi: stm32: fix stm32_spi_prepare_mbr() that halves spi clk for every run selftests/bpf: Add verifier test for release_reference() Revert "net: macsec: report real_dev features when HW offloading is enabled" platform/x86: ideapad-laptop: Disable touchpad_switch platform/x86: touchscreen_dmi: Add info for the RCA Cambio W101 v2 2-in-1 platform/x86/intel/pmt: Sapphire Rapids PMT errata fix scsi: ibmvfc: Avoid path failures during live migration scsi: scsi_debug: Make the READ CAPACITY response compliant with ZBC drm: panel-orientation-quirks: Add quirk for Acer Switch V 10 (SW5-017) block, bfq: fix null pointer dereference in bfq_bio_bfqg() arm64/syscall: Include asm/ptrace.h in syscall_wrapper header. nvmet: fix memory leak in nvmet_subsys_attr_model_store_locked Revert "drm/amdgpu: Revert "drm/amdgpu: getting fan speed pwm for vega10 properly"" ALSA: usb-audio: add quirk to fix Hamedal C20 disconnect issue RISC-V: vdso: Do not add missing symbols to version section in linker script MIPS: pic32: treat port as signed integer xfrm: fix "disable_policy" on ipv4 early demux xfrm: replay: Fix ESN wrap around for GSO af_key: Fix send_acquire race with pfkey_register ARM: dts: am335x-pcm-953: Define fixed regulators in root node ASoC: hdac_hda: fix hda pcm buffer overflow issue ASoC: sgtl5000: Reset the CHIP_CLK_CTRL reg on remove ASoC: soc-pcm: Don't zero TDM masks in __soc_pcm_open() x86/hyperv: Restore VP assist page after cpu offlining/onlining scsi: storvsc: Fix handling of srb_status and capacity change events ASoC: max98373: Add checks for devm_kcalloc regulator: core: fix kobject release warning and memory leak in regulator_register() spi: dw-dma: decrease reference count in dw_spi_dma_init_mfld() regulator: core: fix UAF in destroy_regulator() bus: sunxi-rsb: Remove the shutdown callback bus: sunxi-rsb: Support atomic transfers tee: optee: fix possible memory leak in optee_register_device() ARM: dts: at91: sam9g20ek: enable udc vbus gpio pinctrl selftests: mptcp: fix mibit vs mbit mix up net: liquidio: simplify if expression rxrpc: Fix race between conn bundle lookup and bundle removal [ZDI-CAN-15975] net: dsa: sja1105: disallow C45 transactions on the BASE-TX MDIO bus nfc/nci: fix race with opening and closing net: pch_gbe: fix potential memleak in pch_gbe_tx_queue() 9p/fd: fix issue of list_del corruption in p9_fd_cancel() netfilter: conntrack: Fix data-races around ct mark netfilter: nf_tables: do not set up extensions for end interval iavf: Fix a crash during reset task iavf: Do not restart Tx queues after reset task failure iavf: Fix race condition between iavf_shutdown and iavf_remove ARM: mxs: fix memory leak in mxs_machine_init() ARM: dts: imx6q-prti6q: Fix ref/tcxo-clock-frequency properties net: ethernet: mtk_eth_soc: fix error handling in mtk_open()
[Kernel-packages] [Bug 2004262] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/2004262/+attachment/5644123/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2004262 Title: Intel E810 NICs driver in causinghangs when booting and bonds configured Status in linux package in Ubuntu: Incomplete Bug description: jammy 22.04.1 linux-image-generic 5.15.0-58-generic Intel E810-XXV Dual Port NICs in Dell PowerEdge 650 After beonding is enabled on switch and server side, the system will hang at initialing ubuntu. The kernel loads but around starting the Network Services the system can hang for sometimes 5 minutes, and in other cases, indefinitely. The message of: echo 0 > /proc/sys/kernel/hung_task_timeout_sec” systemd-resolve blocked for more than 120 seconds appears, and eventually the Network services just attempts to start and never does. This is with or without DHCP enabled. Tried this same setup with the hwe-22.04, hwe-20.04, hwe-22.04-ege and linux-oem kernels and all exhibit the same failure. To work around this. installing the Intel 'ice' driver of version 1.10.1.2.2 works. The system doesn't even remotely hang at startup and all networking functions remain working (ping, DNS, general accessibility). The driver can be found at https://downloadmirror.intel.com/763930/ice-1.10.1.2.2.tar.gz --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 31 13:08 seq crw-rw 1 root audio 116, 33 Jan 31 13:08 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5json: { "result": "skip" } DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-01-27 (3 days ago) InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Dell Inc. PowerEdge R650 Package: linux (not installed) PciMultimedia: ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic root=UUID=668aab7c-abe9-434b-a810-acc6eab76cbc ro fsck.mode=skip ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 RelatedPackageVersions: linux-restricted-modules-5.15.0-58-generic N/A linux-backports-modules-5.15.0-58-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.9 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: jammy uec-images Uname: Linux 5.15.0-58-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 09/14/2022 dmi.bios.release: 1.8 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.2 dmi.board.name: 0PJ7YJ dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.2:bd09/14/2022:br1.8:svnDellInc.:pnPowerEdgeR650:pvr:rvnDellInc.:rn0PJ7YJ:rvrA01:cvnDellInc.:ct23:cvr:skuSKU=0912;ModelName=PowerEdgeR650: dmi.product.family: PowerEdge dmi.product.name: PowerEdge R650 dmi.product.sku: SKU=0912;ModelName=PowerEdge R650 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2004262/+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 2004262] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/2004262/+attachment/5644128/+files/acpidump.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2004262 Title: Intel E810 NICs driver in causinghangs when booting and bonds configured Status in linux package in Ubuntu: Incomplete Bug description: jammy 22.04.1 linux-image-generic 5.15.0-58-generic Intel E810-XXV Dual Port NICs in Dell PowerEdge 650 After beonding is enabled on switch and server side, the system will hang at initialing ubuntu. The kernel loads but around starting the Network Services the system can hang for sometimes 5 minutes, and in other cases, indefinitely. The message of: echo 0 > /proc/sys/kernel/hung_task_timeout_sec” systemd-resolve blocked for more than 120 seconds appears, and eventually the Network services just attempts to start and never does. This is with or without DHCP enabled. Tried this same setup with the hwe-22.04, hwe-20.04, hwe-22.04-ege and linux-oem kernels and all exhibit the same failure. To work around this. installing the Intel 'ice' driver of version 1.10.1.2.2 works. The system doesn't even remotely hang at startup and all networking functions remain working (ping, DNS, general accessibility). The driver can be found at https://downloadmirror.intel.com/763930/ice-1.10.1.2.2.tar.gz --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 31 13:08 seq crw-rw 1 root audio 116, 33 Jan 31 13:08 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5json: { "result": "skip" } DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-01-27 (3 days ago) InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Dell Inc. PowerEdge R650 Package: linux (not installed) PciMultimedia: ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic root=UUID=668aab7c-abe9-434b-a810-acc6eab76cbc ro fsck.mode=skip ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 RelatedPackageVersions: linux-restricted-modules-5.15.0-58-generic N/A linux-backports-modules-5.15.0-58-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.9 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: jammy uec-images Uname: Linux 5.15.0-58-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 09/14/2022 dmi.bios.release: 1.8 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.2 dmi.board.name: 0PJ7YJ dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.2:bd09/14/2022:br1.8:svnDellInc.:pnPowerEdgeR650:pvr:rvnDellInc.:rn0PJ7YJ:rvrA01:cvnDellInc.:ct23:cvr:skuSKU=0912;ModelName=PowerEdgeR650: dmi.product.family: PowerEdge dmi.product.name: PowerEdge R650 dmi.product.sku: SKU=0912;ModelName=PowerEdge R650 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2004262/+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