[Kernel-packages] [Bug 2021970] Re: HP EliteBook 650 G9 fails to wake from sleep, reboots instead
apport information ** Tags added: apport-collected ** Description changed: Hi Team, My laptop HP EliteBook 650 G9 gets stuck after sleep mode. Not always, but every 2-3 times, it reboots itself while trying to wake up. Release: Ubuntu 23.04 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed May 31 20:44:32 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-05-30 (1 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) RelatedPackageVersions: mutter-common 44.0-2ubuntu4.23.04.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2023-05-30 (0 days ago) + --- + ProblemType: Bug + ApportVersion: 2.26.1-0ubuntu2 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: reymbergen 6138 F pipewire + reymbergen 6142 F wireplumber + /dev/snd/seq:reymbergen 6138 F pipewire + CRDA: N/A + CasperMD5CheckResult: pass + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 23.04 + InstallationDate: Installed on 2023-05-30 (1 days ago) + InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) + MachineType: HP HP EliteBook 650 15.6 inch G9 Notebook PC + Package: linux (not installed) + ProcFB: 0 i915drmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=86f01b4f-db0d-4b50-b951-6b12abd24c79 ro quiet splash resume=UUID=86f01b4f-db0d-4b50-b951-6b12abd24c79 resume_offset=37726208 vt.handoff=7 + ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 + RelatedPackageVersions: + linux-restricted-modules-6.2.0-20-generic N/A + linux-backports-modules-6.2.0-20-generic N/A + linux-firmware20230323.gitbcdcfbcf-0ubuntu1.1 + Tags: lunar wayland-session + Uname: Linux 6.2.0-20-generic x86_64 + UpgradeStatus: Upgraded to lunar on 2023-05-30 (1 days ago) + UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 03/10/2023 + dmi.bios.release: 6.1 + dmi.bios.vendor: HP + dmi.bios.version: U75 Ver. 01.06.01 + dmi.board.name: 897C + dmi.board.vendor: HP + dmi.board.version: KBC Version 07.5E.00 + dmi.chassis.type: 10 + dmi.chassis.vendor: HP + dmi.ec.firmware.release: 7.94 + dmi.modalias: dmi:bvnHP:bvrU75Ver.01.06.01:bd03/10/2023:br6.1:efr7.94:svnHP:pnHPEliteBook65015.6inchG9NotebookPC:pvr:rvnHP:rn897C:rvrKBCVersion07.5E.00:cvnHP:ct10:cvr:sku6G9E2PA#ABG: + dmi.product.family: 103C_5336AN HP EliteBook + dmi.product.name: HP EliteBook 650 15.6 inch G9 Notebook PC + dmi.product.sku: 6G9E2PA#ABG + dmi.sys.vendor: HP ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/2021970/+attachment/5677103/+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/2021970 Title: HP EliteBook 650 G9 fails to wake from sleep, reboots instead Status in linux package in Ubuntu: Confirmed Bug description: Hi Team, My laptop HP EliteBook 650 G9 gets stuck after sleep mode. Not always, but every 2-3 times, it reboots itself while trying to wake up. Release: Ubuntu 23.04 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed May 31 20:44:32 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-05-30 (1 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) RelatedPackageVersions: mutter-common 44.0-2ubuntu4.23.04.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2023-05-30 (0 days ago) --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: reymbergen 6138 F pipewire reymbergen 6142 F wireplumber /dev/snd/seq:reymbergen 6138 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2023-05-30 (1 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: HP HP EliteBook 650 15.6 inch G9 Notebook PC Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=86f01b4f-db0d-4b50-b951-6b12abd24c79 ro quiet splash resume=UUID=86f01b4f-db0d-4b50-b951-6b12abd24c79 resume_offset=37726208 vt.handoff=7
[Kernel-packages] [Bug 2021970] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/2021970/+attachment/5677106/+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/2021970 Title: HP EliteBook 650 G9 fails to wake from sleep, reboots instead Status in linux package in Ubuntu: Confirmed Bug description: Hi Team, My laptop HP EliteBook 650 G9 gets stuck after sleep mode. Not always, but every 2-3 times, it reboots itself while trying to wake up. Release: Ubuntu 23.04 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed May 31 20:44:32 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-05-30 (1 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) RelatedPackageVersions: mutter-common 44.0-2ubuntu4.23.04.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2023-05-30 (0 days ago) --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: reymbergen 6138 F pipewire reymbergen 6142 F wireplumber /dev/snd/seq:reymbergen 6138 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2023-05-30 (1 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: HP HP EliteBook 650 15.6 inch G9 Notebook PC Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=86f01b4f-db0d-4b50-b951-6b12abd24c79 ro quiet splash resume=UUID=86f01b4f-db0d-4b50-b951-6b12abd24c79 resume_offset=37726208 vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 RelatedPackageVersions: linux-restricted-modules-6.2.0-20-generic N/A linux-backports-modules-6.2.0-20-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1.1 Tags: lunar wayland-session Uname: Linux 6.2.0-20-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-05-30 (1 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/10/2023 dmi.bios.release: 6.1 dmi.bios.vendor: HP dmi.bios.version: U75 Ver. 01.06.01 dmi.board.name: 897C dmi.board.vendor: HP dmi.board.version: KBC Version 07.5E.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 7.94 dmi.modalias: dmi:bvnHP:bvrU75Ver.01.06.01:bd03/10/2023:br6.1:efr7.94:svnHP:pnHPEliteBook65015.6inchG9NotebookPC:pvr:rvnHP:rn897C:rvrKBCVersion07.5E.00:cvnHP:ct10:cvr:sku6G9E2PA#ABG: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 650 15.6 inch G9 Notebook PC dmi.product.sku: 6G9E2PA#ABG dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2021970/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2021970] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/2021970/+attachment/5677105/+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/2021970 Title: HP EliteBook 650 G9 fails to wake from sleep, reboots instead Status in linux package in Ubuntu: Confirmed Bug description: Hi Team, My laptop HP EliteBook 650 G9 gets stuck after sleep mode. Not always, but every 2-3 times, it reboots itself while trying to wake up. Release: Ubuntu 23.04 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed May 31 20:44:32 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-05-30 (1 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) RelatedPackageVersions: mutter-common 44.0-2ubuntu4.23.04.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2023-05-30 (0 days ago) --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: reymbergen 6138 F pipewire reymbergen 6142 F wireplumber /dev/snd/seq:reymbergen 6138 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2023-05-30 (1 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: HP HP EliteBook 650 15.6 inch G9 Notebook PC Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=86f01b4f-db0d-4b50-b951-6b12abd24c79 ro quiet splash resume=UUID=86f01b4f-db0d-4b50-b951-6b12abd24c79 resume_offset=37726208 vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 RelatedPackageVersions: linux-restricted-modules-6.2.0-20-generic N/A linux-backports-modules-6.2.0-20-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1.1 Tags: lunar wayland-session Uname: Linux 6.2.0-20-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-05-30 (1 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/10/2023 dmi.bios.release: 6.1 dmi.bios.vendor: HP dmi.bios.version: U75 Ver. 01.06.01 dmi.board.name: 897C dmi.board.vendor: HP dmi.board.version: KBC Version 07.5E.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 7.94 dmi.modalias: dmi:bvnHP:bvrU75Ver.01.06.01:bd03/10/2023:br6.1:efr7.94:svnHP:pnHPEliteBook65015.6inchG9NotebookPC:pvr:rvnHP:rn897C:rvrKBCVersion07.5E.00:cvnHP:ct10:cvr:sku6G9E2PA#ABG: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 650 15.6 inch G9 Notebook PC dmi.product.sku: 6G9E2PA#ABG dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2021970/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2021970] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/2021970/+attachment/5677104/+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/2021970 Title: HP EliteBook 650 G9 fails to wake from sleep, reboots instead Status in linux package in Ubuntu: Confirmed Bug description: Hi Team, My laptop HP EliteBook 650 G9 gets stuck after sleep mode. Not always, but every 2-3 times, it reboots itself while trying to wake up. Release: Ubuntu 23.04 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed May 31 20:44:32 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-05-30 (1 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) RelatedPackageVersions: mutter-common 44.0-2ubuntu4.23.04.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2023-05-30 (0 days ago) --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: reymbergen 6138 F pipewire reymbergen 6142 F wireplumber /dev/snd/seq:reymbergen 6138 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2023-05-30 (1 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: HP HP EliteBook 650 15.6 inch G9 Notebook PC Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=86f01b4f-db0d-4b50-b951-6b12abd24c79 ro quiet splash resume=UUID=86f01b4f-db0d-4b50-b951-6b12abd24c79 resume_offset=37726208 vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 RelatedPackageVersions: linux-restricted-modules-6.2.0-20-generic N/A linux-backports-modules-6.2.0-20-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1.1 Tags: lunar wayland-session Uname: Linux 6.2.0-20-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-05-30 (1 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/10/2023 dmi.bios.release: 6.1 dmi.bios.vendor: HP dmi.bios.version: U75 Ver. 01.06.01 dmi.board.name: 897C dmi.board.vendor: HP dmi.board.version: KBC Version 07.5E.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 7.94 dmi.modalias: dmi:bvnHP:bvrU75Ver.01.06.01:bd03/10/2023:br6.1:efr7.94:svnHP:pnHPEliteBook65015.6inchG9NotebookPC:pvr:rvnHP:rn897C:rvrKBCVersion07.5E.00:cvnHP:ct10:cvr:sku6G9E2PA#ABG: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 650 15.6 inch G9 Notebook PC dmi.product.sku: 6G9E2PA#ABG dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2021970/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2021970] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/2021970/+attachment/5677107/+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/2021970 Title: HP EliteBook 650 G9 fails to wake from sleep, reboots instead Status in linux package in Ubuntu: Confirmed Bug description: Hi Team, My laptop HP EliteBook 650 G9 gets stuck after sleep mode. Not always, but every 2-3 times, it reboots itself while trying to wake up. Release: Ubuntu 23.04 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed May 31 20:44:32 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-05-30 (1 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) RelatedPackageVersions: mutter-common 44.0-2ubuntu4.23.04.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2023-05-30 (0 days ago) --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: reymbergen 6138 F pipewire reymbergen 6142 F wireplumber /dev/snd/seq:reymbergen 6138 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2023-05-30 (1 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: HP HP EliteBook 650 15.6 inch G9 Notebook PC Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=86f01b4f-db0d-4b50-b951-6b12abd24c79 ro quiet splash resume=UUID=86f01b4f-db0d-4b50-b951-6b12abd24c79 resume_offset=37726208 vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 RelatedPackageVersions: linux-restricted-modules-6.2.0-20-generic N/A linux-backports-modules-6.2.0-20-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1.1 Tags: lunar wayland-session Uname: Linux 6.2.0-20-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-05-30 (1 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/10/2023 dmi.bios.release: 6.1 dmi.bios.vendor: HP dmi.bios.version: U75 Ver. 01.06.01 dmi.board.name: 897C dmi.board.vendor: HP dmi.board.version: KBC Version 07.5E.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 7.94 dmi.modalias: dmi:bvnHP:bvrU75Ver.01.06.01:bd03/10/2023:br6.1:efr7.94:svnHP:pnHPEliteBook65015.6inchG9NotebookPC:pvr:rvnHP:rn897C:rvrKBCVersion07.5E.00:cvnHP:ct10:cvr:sku6G9E2PA#ABG: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 650 15.6 inch G9 Notebook PC dmi.product.sku: 6G9E2PA#ABG dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2021970/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2021970] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/2021970/+attachment/5677108/+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/2021970 Title: HP EliteBook 650 G9 fails to wake from sleep, reboots instead Status in linux package in Ubuntu: Confirmed Bug description: Hi Team, My laptop HP EliteBook 650 G9 gets stuck after sleep mode. Not always, but every 2-3 times, it reboots itself while trying to wake up. Release: Ubuntu 23.04 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed May 31 20:44:32 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-05-30 (1 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) RelatedPackageVersions: mutter-common 44.0-2ubuntu4.23.04.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2023-05-30 (0 days ago) --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: reymbergen 6138 F pipewire reymbergen 6142 F wireplumber /dev/snd/seq:reymbergen 6138 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2023-05-30 (1 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: HP HP EliteBook 650 15.6 inch G9 Notebook PC Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=86f01b4f-db0d-4b50-b951-6b12abd24c79 ro quiet splash resume=UUID=86f01b4f-db0d-4b50-b951-6b12abd24c79 resume_offset=37726208 vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 RelatedPackageVersions: linux-restricted-modules-6.2.0-20-generic N/A linux-backports-modules-6.2.0-20-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1.1 Tags: lunar wayland-session Uname: Linux 6.2.0-20-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-05-30 (1 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/10/2023 dmi.bios.release: 6.1 dmi.bios.vendor: HP dmi.bios.version: U75 Ver. 01.06.01 dmi.board.name: 897C dmi.board.vendor: HP dmi.board.version: KBC Version 07.5E.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 7.94 dmi.modalias: dmi:bvnHP:bvrU75Ver.01.06.01:bd03/10/2023:br6.1:efr7.94:svnHP:pnHPEliteBook65015.6inchG9NotebookPC:pvr:rvnHP:rn897C:rvrKBCVersion07.5E.00:cvnHP:ct10:cvr:sku6G9E2PA#ABG: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 650 15.6 inch G9 Notebook PC dmi.product.sku: 6G9E2PA#ABG dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2021970/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2021970] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/2021970/+attachment/5677110/+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/2021970 Title: HP EliteBook 650 G9 fails to wake from sleep, reboots instead Status in linux package in Ubuntu: Confirmed Bug description: Hi Team, My laptop HP EliteBook 650 G9 gets stuck after sleep mode. Not always, but every 2-3 times, it reboots itself while trying to wake up. Release: Ubuntu 23.04 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed May 31 20:44:32 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-05-30 (1 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) RelatedPackageVersions: mutter-common 44.0-2ubuntu4.23.04.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2023-05-30 (0 days ago) --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: reymbergen 6138 F pipewire reymbergen 6142 F wireplumber /dev/snd/seq:reymbergen 6138 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2023-05-30 (1 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: HP HP EliteBook 650 15.6 inch G9 Notebook PC Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=86f01b4f-db0d-4b50-b951-6b12abd24c79 ro quiet splash resume=UUID=86f01b4f-db0d-4b50-b951-6b12abd24c79 resume_offset=37726208 vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 RelatedPackageVersions: linux-restricted-modules-6.2.0-20-generic N/A linux-backports-modules-6.2.0-20-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1.1 Tags: lunar wayland-session Uname: Linux 6.2.0-20-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-05-30 (1 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/10/2023 dmi.bios.release: 6.1 dmi.bios.vendor: HP dmi.bios.version: U75 Ver. 01.06.01 dmi.board.name: 897C dmi.board.vendor: HP dmi.board.version: KBC Version 07.5E.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 7.94 dmi.modalias: dmi:bvnHP:bvrU75Ver.01.06.01:bd03/10/2023:br6.1:efr7.94:svnHP:pnHPEliteBook65015.6inchG9NotebookPC:pvr:rvnHP:rn897C:rvrKBCVersion07.5E.00:cvnHP:ct10:cvr:sku6G9E2PA#ABG: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 650 15.6 inch G9 Notebook PC dmi.product.sku: 6G9E2PA#ABG dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2021970/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2021970] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/2021970/+attachment/5677109/+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/2021970 Title: HP EliteBook 650 G9 fails to wake from sleep, reboots instead Status in linux package in Ubuntu: Confirmed Bug description: Hi Team, My laptop HP EliteBook 650 G9 gets stuck after sleep mode. Not always, but every 2-3 times, it reboots itself while trying to wake up. Release: Ubuntu 23.04 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed May 31 20:44:32 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-05-30 (1 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) RelatedPackageVersions: mutter-common 44.0-2ubuntu4.23.04.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2023-05-30 (0 days ago) --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: reymbergen 6138 F pipewire reymbergen 6142 F wireplumber /dev/snd/seq:reymbergen 6138 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2023-05-30 (1 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: HP HP EliteBook 650 15.6 inch G9 Notebook PC Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=86f01b4f-db0d-4b50-b951-6b12abd24c79 ro quiet splash resume=UUID=86f01b4f-db0d-4b50-b951-6b12abd24c79 resume_offset=37726208 vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 RelatedPackageVersions: linux-restricted-modules-6.2.0-20-generic N/A linux-backports-modules-6.2.0-20-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1.1 Tags: lunar wayland-session Uname: Linux 6.2.0-20-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-05-30 (1 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/10/2023 dmi.bios.release: 6.1 dmi.bios.vendor: HP dmi.bios.version: U75 Ver. 01.06.01 dmi.board.name: 897C dmi.board.vendor: HP dmi.board.version: KBC Version 07.5E.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 7.94 dmi.modalias: dmi:bvnHP:bvrU75Ver.01.06.01:bd03/10/2023:br6.1:efr7.94:svnHP:pnHPEliteBook65015.6inchG9NotebookPC:pvr:rvnHP:rn897C:rvrKBCVersion07.5E.00:cvnHP:ct10:cvr:sku6G9E2PA#ABG: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 650 15.6 inch G9 Notebook PC dmi.product.sku: 6G9E2PA#ABG dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2021970/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2021970] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/2021970/+attachment/5677111/+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/2021970 Title: HP EliteBook 650 G9 fails to wake from sleep, reboots instead Status in linux package in Ubuntu: Confirmed Bug description: Hi Team, My laptop HP EliteBook 650 G9 gets stuck after sleep mode. Not always, but every 2-3 times, it reboots itself while trying to wake up. Release: Ubuntu 23.04 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed May 31 20:44:32 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-05-30 (1 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) RelatedPackageVersions: mutter-common 44.0-2ubuntu4.23.04.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2023-05-30 (0 days ago) --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: reymbergen 6138 F pipewire reymbergen 6142 F wireplumber /dev/snd/seq:reymbergen 6138 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2023-05-30 (1 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: HP HP EliteBook 650 15.6 inch G9 Notebook PC Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=86f01b4f-db0d-4b50-b951-6b12abd24c79 ro quiet splash resume=UUID=86f01b4f-db0d-4b50-b951-6b12abd24c79 resume_offset=37726208 vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 RelatedPackageVersions: linux-restricted-modules-6.2.0-20-generic N/A linux-backports-modules-6.2.0-20-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1.1 Tags: lunar wayland-session Uname: Linux 6.2.0-20-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-05-30 (1 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/10/2023 dmi.bios.release: 6.1 dmi.bios.vendor: HP dmi.bios.version: U75 Ver. 01.06.01 dmi.board.name: 897C dmi.board.vendor: HP dmi.board.version: KBC Version 07.5E.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 7.94 dmi.modalias: dmi:bvnHP:bvrU75Ver.01.06.01:bd03/10/2023:br6.1:efr7.94:svnHP:pnHPEliteBook65015.6inchG9NotebookPC:pvr:rvnHP:rn897C:rvrKBCVersion07.5E.00:cvnHP:ct10:cvr:sku6G9E2PA#ABG: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 650 15.6 inch G9 Notebook PC dmi.product.sku: 6G9E2PA#ABG dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2021970/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2021970] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/2021970/+attachment/5677113/+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/2021970 Title: HP EliteBook 650 G9 fails to wake from sleep, reboots instead Status in linux package in Ubuntu: Confirmed Bug description: Hi Team, My laptop HP EliteBook 650 G9 gets stuck after sleep mode. Not always, but every 2-3 times, it reboots itself while trying to wake up. Release: Ubuntu 23.04 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed May 31 20:44:32 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-05-30 (1 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) RelatedPackageVersions: mutter-common 44.0-2ubuntu4.23.04.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2023-05-30 (0 days ago) --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: reymbergen 6138 F pipewire reymbergen 6142 F wireplumber /dev/snd/seq:reymbergen 6138 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2023-05-30 (1 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: HP HP EliteBook 650 15.6 inch G9 Notebook PC Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=86f01b4f-db0d-4b50-b951-6b12abd24c79 ro quiet splash resume=UUID=86f01b4f-db0d-4b50-b951-6b12abd24c79 resume_offset=37726208 vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 RelatedPackageVersions: linux-restricted-modules-6.2.0-20-generic N/A linux-backports-modules-6.2.0-20-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1.1 Tags: lunar wayland-session Uname: Linux 6.2.0-20-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-05-30 (1 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/10/2023 dmi.bios.release: 6.1 dmi.bios.vendor: HP dmi.bios.version: U75 Ver. 01.06.01 dmi.board.name: 897C dmi.board.vendor: HP dmi.board.version: KBC Version 07.5E.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 7.94 dmi.modalias: dmi:bvnHP:bvrU75Ver.01.06.01:bd03/10/2023:br6.1:efr7.94:svnHP:pnHPEliteBook65015.6inchG9NotebookPC:pvr:rvnHP:rn897C:rvrKBCVersion07.5E.00:cvnHP:ct10:cvr:sku6G9E2PA#ABG: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 650 15.6 inch G9 Notebook PC dmi.product.sku: 6G9E2PA#ABG dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2021970/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2021970] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/2021970/+attachment/5677112/+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/2021970 Title: HP EliteBook 650 G9 fails to wake from sleep, reboots instead Status in linux package in Ubuntu: Confirmed Bug description: Hi Team, My laptop HP EliteBook 650 G9 gets stuck after sleep mode. Not always, but every 2-3 times, it reboots itself while trying to wake up. Release: Ubuntu 23.04 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed May 31 20:44:32 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-05-30 (1 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) RelatedPackageVersions: mutter-common 44.0-2ubuntu4.23.04.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2023-05-30 (0 days ago) --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: reymbergen 6138 F pipewire reymbergen 6142 F wireplumber /dev/snd/seq:reymbergen 6138 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2023-05-30 (1 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: HP HP EliteBook 650 15.6 inch G9 Notebook PC Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=86f01b4f-db0d-4b50-b951-6b12abd24c79 ro quiet splash resume=UUID=86f01b4f-db0d-4b50-b951-6b12abd24c79 resume_offset=37726208 vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 RelatedPackageVersions: linux-restricted-modules-6.2.0-20-generic N/A linux-backports-modules-6.2.0-20-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1.1 Tags: lunar wayland-session Uname: Linux 6.2.0-20-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-05-30 (1 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/10/2023 dmi.bios.release: 6.1 dmi.bios.vendor: HP dmi.bios.version: U75 Ver. 01.06.01 dmi.board.name: 897C dmi.board.vendor: HP dmi.board.version: KBC Version 07.5E.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 7.94 dmi.modalias: dmi:bvnHP:bvrU75Ver.01.06.01:bd03/10/2023:br6.1:efr7.94:svnHP:pnHPEliteBook65015.6inchG9NotebookPC:pvr:rvnHP:rn897C:rvrKBCVersion07.5E.00:cvnHP:ct10:cvr:sku6G9E2PA#ABG: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 650 15.6 inch G9 Notebook PC dmi.product.sku: 6G9E2PA#ABG dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2021970/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2021970] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/2021970/+attachment/5677117/+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/2021970 Title: HP EliteBook 650 G9 fails to wake from sleep, reboots instead Status in linux package in Ubuntu: Confirmed Bug description: Hi Team, My laptop HP EliteBook 650 G9 gets stuck after sleep mode. Not always, but every 2-3 times, it reboots itself while trying to wake up. Release: Ubuntu 23.04 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed May 31 20:44:32 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-05-30 (1 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) RelatedPackageVersions: mutter-common 44.0-2ubuntu4.23.04.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2023-05-30 (0 days ago) --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: reymbergen 6138 F pipewire reymbergen 6142 F wireplumber /dev/snd/seq:reymbergen 6138 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2023-05-30 (1 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: HP HP EliteBook 650 15.6 inch G9 Notebook PC Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=86f01b4f-db0d-4b50-b951-6b12abd24c79 ro quiet splash resume=UUID=86f01b4f-db0d-4b50-b951-6b12abd24c79 resume_offset=37726208 vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 RelatedPackageVersions: linux-restricted-modules-6.2.0-20-generic N/A linux-backports-modules-6.2.0-20-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1.1 Tags: lunar wayland-session Uname: Linux 6.2.0-20-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-05-30 (1 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/10/2023 dmi.bios.release: 6.1 dmi.bios.vendor: HP dmi.bios.version: U75 Ver. 01.06.01 dmi.board.name: 897C dmi.board.vendor: HP dmi.board.version: KBC Version 07.5E.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 7.94 dmi.modalias: dmi:bvnHP:bvrU75Ver.01.06.01:bd03/10/2023:br6.1:efr7.94:svnHP:pnHPEliteBook65015.6inchG9NotebookPC:pvr:rvnHP:rn897C:rvrKBCVersion07.5E.00:cvnHP:ct10:cvr:sku6G9E2PA#ABG: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 650 15.6 inch G9 Notebook PC dmi.product.sku: 6G9E2PA#ABG dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2021970/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2021970] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/2021970/+attachment/5677119/+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/2021970 Title: HP EliteBook 650 G9 fails to wake from sleep, reboots instead Status in linux package in Ubuntu: Confirmed Bug description: Hi Team, My laptop HP EliteBook 650 G9 gets stuck after sleep mode. Not always, but every 2-3 times, it reboots itself while trying to wake up. Release: Ubuntu 23.04 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed May 31 20:44:32 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-05-30 (1 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) RelatedPackageVersions: mutter-common 44.0-2ubuntu4.23.04.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2023-05-30 (0 days ago) --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: reymbergen 6138 F pipewire reymbergen 6142 F wireplumber /dev/snd/seq:reymbergen 6138 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2023-05-30 (1 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: HP HP EliteBook 650 15.6 inch G9 Notebook PC Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=86f01b4f-db0d-4b50-b951-6b12abd24c79 ro quiet splash resume=UUID=86f01b4f-db0d-4b50-b951-6b12abd24c79 resume_offset=37726208 vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 RelatedPackageVersions: linux-restricted-modules-6.2.0-20-generic N/A linux-backports-modules-6.2.0-20-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1.1 Tags: lunar wayland-session Uname: Linux 6.2.0-20-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-05-30 (1 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/10/2023 dmi.bios.release: 6.1 dmi.bios.vendor: HP dmi.bios.version: U75 Ver. 01.06.01 dmi.board.name: 897C dmi.board.vendor: HP dmi.board.version: KBC Version 07.5E.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 7.94 dmi.modalias: dmi:bvnHP:bvrU75Ver.01.06.01:bd03/10/2023:br6.1:efr7.94:svnHP:pnHPEliteBook65015.6inchG9NotebookPC:pvr:rvnHP:rn897C:rvrKBCVersion07.5E.00:cvnHP:ct10:cvr:sku6G9E2PA#ABG: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 650 15.6 inch G9 Notebook PC dmi.product.sku: 6G9E2PA#ABG dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2021970/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2021970] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/2021970/+attachment/5677118/+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/2021970 Title: HP EliteBook 650 G9 fails to wake from sleep, reboots instead Status in linux package in Ubuntu: Confirmed Bug description: Hi Team, My laptop HP EliteBook 650 G9 gets stuck after sleep mode. Not always, but every 2-3 times, it reboots itself while trying to wake up. Release: Ubuntu 23.04 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed May 31 20:44:32 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-05-30 (1 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) RelatedPackageVersions: mutter-common 44.0-2ubuntu4.23.04.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2023-05-30 (0 days ago) --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: reymbergen 6138 F pipewire reymbergen 6142 F wireplumber /dev/snd/seq:reymbergen 6138 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2023-05-30 (1 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: HP HP EliteBook 650 15.6 inch G9 Notebook PC Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=86f01b4f-db0d-4b50-b951-6b12abd24c79 ro quiet splash resume=UUID=86f01b4f-db0d-4b50-b951-6b12abd24c79 resume_offset=37726208 vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 RelatedPackageVersions: linux-restricted-modules-6.2.0-20-generic N/A linux-backports-modules-6.2.0-20-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1.1 Tags: lunar wayland-session Uname: Linux 6.2.0-20-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-05-30 (1 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/10/2023 dmi.bios.release: 6.1 dmi.bios.vendor: HP dmi.bios.version: U75 Ver. 01.06.01 dmi.board.name: 897C dmi.board.vendor: HP dmi.board.version: KBC Version 07.5E.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 7.94 dmi.modalias: dmi:bvnHP:bvrU75Ver.01.06.01:bd03/10/2023:br6.1:efr7.94:svnHP:pnHPEliteBook65015.6inchG9NotebookPC:pvr:rvnHP:rn897C:rvrKBCVersion07.5E.00:cvnHP:ct10:cvr:sku6G9E2PA#ABG: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 650 15.6 inch G9 Notebook PC dmi.product.sku: 6G9E2PA#ABG dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2021970/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2021970] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/2021970/+attachment/5677115/+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/2021970 Title: HP EliteBook 650 G9 fails to wake from sleep, reboots instead Status in linux package in Ubuntu: Confirmed Bug description: Hi Team, My laptop HP EliteBook 650 G9 gets stuck after sleep mode. Not always, but every 2-3 times, it reboots itself while trying to wake up. Release: Ubuntu 23.04 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed May 31 20:44:32 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-05-30 (1 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) RelatedPackageVersions: mutter-common 44.0-2ubuntu4.23.04.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2023-05-30 (0 days ago) --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: reymbergen 6138 F pipewire reymbergen 6142 F wireplumber /dev/snd/seq:reymbergen 6138 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2023-05-30 (1 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: HP HP EliteBook 650 15.6 inch G9 Notebook PC Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=86f01b4f-db0d-4b50-b951-6b12abd24c79 ro quiet splash resume=UUID=86f01b4f-db0d-4b50-b951-6b12abd24c79 resume_offset=37726208 vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 RelatedPackageVersions: linux-restricted-modules-6.2.0-20-generic N/A linux-backports-modules-6.2.0-20-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1.1 Tags: lunar wayland-session Uname: Linux 6.2.0-20-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-05-30 (1 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/10/2023 dmi.bios.release: 6.1 dmi.bios.vendor: HP dmi.bios.version: U75 Ver. 01.06.01 dmi.board.name: 897C dmi.board.vendor: HP dmi.board.version: KBC Version 07.5E.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 7.94 dmi.modalias: dmi:bvnHP:bvrU75Ver.01.06.01:bd03/10/2023:br6.1:efr7.94:svnHP:pnHPEliteBook65015.6inchG9NotebookPC:pvr:rvnHP:rn897C:rvrKBCVersion07.5E.00:cvnHP:ct10:cvr:sku6G9E2PA#ABG: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 650 15.6 inch G9 Notebook PC dmi.product.sku: 6G9E2PA#ABG dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2021970/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2021970] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/2021970/+attachment/5677116/+files/RfKill.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/2021970 Title: HP EliteBook 650 G9 fails to wake from sleep, reboots instead Status in linux package in Ubuntu: Confirmed Bug description: Hi Team, My laptop HP EliteBook 650 G9 gets stuck after sleep mode. Not always, but every 2-3 times, it reboots itself while trying to wake up. Release: Ubuntu 23.04 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed May 31 20:44:32 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-05-30 (1 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) RelatedPackageVersions: mutter-common 44.0-2ubuntu4.23.04.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2023-05-30 (0 days ago) --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: reymbergen 6138 F pipewire reymbergen 6142 F wireplumber /dev/snd/seq:reymbergen 6138 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2023-05-30 (1 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: HP HP EliteBook 650 15.6 inch G9 Notebook PC Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=86f01b4f-db0d-4b50-b951-6b12abd24c79 ro quiet splash resume=UUID=86f01b4f-db0d-4b50-b951-6b12abd24c79 resume_offset=37726208 vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 RelatedPackageVersions: linux-restricted-modules-6.2.0-20-generic N/A linux-backports-modules-6.2.0-20-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1.1 Tags: lunar wayland-session Uname: Linux 6.2.0-20-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-05-30 (1 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/10/2023 dmi.bios.release: 6.1 dmi.bios.vendor: HP dmi.bios.version: U75 Ver. 01.06.01 dmi.board.name: 897C dmi.board.vendor: HP dmi.board.version: KBC Version 07.5E.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 7.94 dmi.modalias: dmi:bvnHP:bvrU75Ver.01.06.01:bd03/10/2023:br6.1:efr7.94:svnHP:pnHPEliteBook65015.6inchG9NotebookPC:pvr:rvnHP:rn897C:rvrKBCVersion07.5E.00:cvnHP:ct10:cvr:sku6G9E2PA#ABG: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 650 15.6 inch G9 Notebook PC dmi.product.sku: 6G9E2PA#ABG dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2021970/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2021970] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/2021970/+attachment/5677114/+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/2021970 Title: HP EliteBook 650 G9 fails to wake from sleep, reboots instead Status in linux package in Ubuntu: Confirmed Bug description: Hi Team, My laptop HP EliteBook 650 G9 gets stuck after sleep mode. Not always, but every 2-3 times, it reboots itself while trying to wake up. Release: Ubuntu 23.04 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed May 31 20:44:32 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-05-30 (1 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) RelatedPackageVersions: mutter-common 44.0-2ubuntu4.23.04.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2023-05-30 (0 days ago) --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: reymbergen 6138 F pipewire reymbergen 6142 F wireplumber /dev/snd/seq:reymbergen 6138 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2023-05-30 (1 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: HP HP EliteBook 650 15.6 inch G9 Notebook PC Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=86f01b4f-db0d-4b50-b951-6b12abd24c79 ro quiet splash resume=UUID=86f01b4f-db0d-4b50-b951-6b12abd24c79 resume_offset=37726208 vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 RelatedPackageVersions: linux-restricted-modules-6.2.0-20-generic N/A linux-backports-modules-6.2.0-20-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1.1 Tags: lunar wayland-session Uname: Linux 6.2.0-20-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-05-30 (1 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/10/2023 dmi.bios.release: 6.1 dmi.bios.vendor: HP dmi.bios.version: U75 Ver. 01.06.01 dmi.board.name: 897C dmi.board.vendor: HP dmi.board.version: KBC Version 07.5E.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 7.94 dmi.modalias: dmi:bvnHP:bvrU75Ver.01.06.01:bd03/10/2023:br6.1:efr7.94:svnHP:pnHPEliteBook65015.6inchG9NotebookPC:pvr:rvnHP:rn897C:rvrKBCVersion07.5E.00:cvnHP:ct10:cvr:sku6G9E2PA#ABG: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 650 15.6 inch G9 Notebook PC dmi.product.sku: 6G9E2PA#ABG dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2021970/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2022036] Re: package linux-image-5.19.0-43-generic 5.19.0-43.44~22.04.1 failed to install/upgrade: installed linux-image-5.19.0-43-generic package post-installation script subpr
Thank you for taking the time to report this bug and helping to make Ubuntu better. Reviewing your dmesg attachment in this bug report it seems that there is a problem with your hardware. I recommend performing a back up and then investigating the situation. Measures you might take include checking cable connections and using software tools to investigate the health of your hardware. In the event that is is not in fact an error with your hardware please set the bug's status back to New. Thanks and good luck! [This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.] ** Tags added: hardware-error ** Changed in: linux-signed-hwe-5.19 (Ubuntu) Importance: Undecided => Low ** Changed in: linux-signed-hwe-5.19 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2022036 Title: package linux-image-5.19.0-43-generic 5.19.0-43.44~22.04.1 failed to install/upgrade: installed linux-image-5.19.0-43-generic package post- installation script subprocess returned error exit status 135 Status in linux-signed-hwe-5.19 package in Ubuntu: Invalid Bug description: Very slow startup ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-43-generic 5.19.0-43.44~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-41.42~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Jun 1 09:49:26 2023 ErrorMessage: installed linux-image-5.19.0-43-generic package post-installation script subprocess returned error exit status 135 InstallationDate: Installed on 2023-03-19 (73 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: /usr/bin/python3.10, Python 3.10.6, python-is-python3, 3.9.2-2 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.9 SourcePackage: linux-signed-hwe-5.19 Title: package linux-image-5.19.0-43-generic 5.19.0-43.44~22.04.1 failed to install/upgrade: installed linux-image-5.19.0-43-generic package post-installation script subprocess returned error exit status 135 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2022036/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2019450] Re: zfs-linux FTBFS with v6.2.8 stable updates
Everything works as expected against newly upgraded kernels in lunar with zfs-linux 2.1.9-2ubuntu1.1 as seen in RT testing, autopkgtests, and kernel builds. Please release this update. ** Tags added: verification-done verification-done-lunar -- 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/2019450 Title: zfs-linux FTBFS with v6.2.8 stable updates Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Jammy: New Status in zfs-linux source package in Lunar: Fix Committed Status in zfs-linux source package in Mantic: Fix Released Bug description: [ Impact ] * Stable kernel updates changed signature of a function call, thus zfs-linux needs adapting. Otherwise it fallsback to older symbols, which are GPL only. [ Test Plan ] * linux 6.2 with 6.2.8 stable updates builds with zfs, without this fix build fails with MODPOST <>/build/zfs/2.1.9/build/module/Module.symvers ERROR: modpost: GPL-incompatible module zfs.ko uses GPL-only symbol 'bio_start_io_acct' ERROR: modpost: GPL-incompatible module zfs.ko uses GPL-only symbol 'bio_end_io_acct_remapped' make[5]: *** [scripts/Makefile.modpost:138: <>/build/zfs/2.1.9/build/module/Module.symvers] Error 1 as the signature of the non-gpl function call has changed, zfs configure scripts fail to detect it as available, fallback on a gpl symbol, which we then prohibit from using. [ Where problems could occur ] * This is a cherry-pick of build-compat only, without any other changes [ Other Info ] * Upstream commit https://github.com/openzfs/zfs/pull/14677/commits/1a951502f0b4200a13f23f0d2f5759ef60188c17 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2019450/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2020901] Re: io_uring regression in the Ubuntu kernel (deadlock)
** Information type changed from Private Security to Public Security -- 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/2020901 Title: io_uring regression in the Ubuntu kernel (deadlock) Status in linux package in Ubuntu: Triaged Bug description: Whenever using io_uring on the Ubuntu 5.15 or 5.19 kernel, one gets: ``` [ 123.226074] BUG: kernel NULL pointer dereference, address: 001d [ 123.226160] #PF: supervisor read access in kernel mode [ 123.226201] #PF: error_code(0x) - not-present page [ 123.226241] PGD 0 P4D 0 [ 123.226272] Oops: [#1] PREEMPT SMP PTI [ 123.226310] CPU: 2 PID: 4326 Comm: qemu-system-x86 Tainted: P O 5.19.0-42-generic #43~22.04.1-Ubuntu [ 123.226381] Hardware name: /D33217GKE, BIOS GKPPT10H.86A.0069.2019.1104.1340 11/04/2019 [ 123.228698] RIP: 0010:__blk_queue_split+0x53/0x1f0 [ 123.231029] Code: 00 00 83 f8 09 0f 84 e7 00 00 00 83 f8 03 0f 84 15 01 00 00 48 89 d1 4c 89 c6 4c 89 ca e8 b5 f2 ff ff 48 89 c3 48 85 db 74 5f <44> 8b 63 28 81 4b 10 00 40 00 00 49 be 00 00 00 00 00 00 00 80 4c [ 123.235909] RSP: 0018:9bb3414779e8 EFLAGS: 00010286 [ 123.238328] RAX: fff5 RBX: fff5 RCX: [ 123.240737] RDX: RSI: RDI: [ 123.243093] RBP: 9bb341477a08 R08: R09: [ 123.245435] R10: R11: R12: 8e095d629ac0 [ 123.247735] R13: 9bb341477a18 R14: 8e0940df2040 R15: 0140 [ 123.250024] FS: 7fa1cff602c0() GS:8e0a5730() knlGS: [ 123.252306] CS: 0010 DS: ES: CR0: 80050033 [ 123.254591] CR2: 001d CR3: 000111ccc006 CR4: 001726e0 [ 123.256899] Call Trace: [ 123.259174] [ 123.261406] blk_mq_submit_bio+0x8c/0x440 [ 123.263626] __submit_bio+0x109/0x1a0 [ 123.265795] __submit_bio_noacct+0x81/0x1f0 [ 123.267922] submit_bio_noacct_nocheck+0x91/0x120 [ 123.270016] ? blk_cgroup_bio_start+0xac/0x130 [ 123.272076] ? recalibrate_cpu_khz+0x10/0x10 [ 123.274114] ? ktime_get+0x46/0xc0 [ 123.276126] submit_bio_noacct+0x209/0x590 [ 123.278132] submit_bio+0x40/0xf0 [ 123.280121] __blkdev_direct_IO_async+0x146/0x1f0 [ 123.282108] blkdev_direct_IO.part.0+0x40/0xa0 [ 123.284097] blkdev_read_iter+0x9f/0x1a0 [ 123.286065] io_read+0xea/0x510 [ 123.288080] ? fget+0x83/0xc0 [ 123.290031] io_issue_sqe+0x61/0x440 [ 123.291960] ? io_init_req+0xfa/0x2f0 [ 123.293847] io_submit_sqes+0x141/0x4a0 [ 123.295703] ? __fget_light+0xb5/0x160 [ 123.297537] __do_sys_io_uring_enter+0x316/0x670 [ 123.299345] ? __secure_computing+0x9b/0x110 [ 123.301153] __x64_sys_io_uring_enter+0x22/0x40 [ 123.302900] do_syscall_64+0x5c/0x90 [ 123.304608] ? do_syscall_64+0x69/0x90 [ 123.306286] ? exit_to_user_mode_prepare+0x3b/0xd0 [ 123.307969] ? syscall_exit_to_user_mode+0x2a/0x50 [ 123.309605] ? do_syscall_64+0x69/0x90 [ 123.311176] ? do_syscall_64+0x69/0x90 [ 123.312717] ? sysvec_reschedule_ipi+0x7b/0x120 [ 123.314252] entry_SYSCALL_64_after_hwframe+0x63/0xcd [ 123.315791] RIP: 0033:0x7fa1d28855e1 [ 123.317314] Code: 89 55 e4 89 4d e0 4c 89 45 d8 4c 89 4d d0 44 8b 55 e0 4c 8b 45 d8 4c 8b 4d d0 b8 aa 01 00 00 8b 7d ec 8b 75 e8 8b 55 e4 0f 05 <48> 89 45 f8 48 8b 45 f8 5d c3 55 48 89 e5 48 83 ec 18 89 7d fc 89 [ 123.320664] RSP: 002b:7fa17550ae68 EFLAGS: 0216 ORIG_RAX: 01aa [ 123.322364] RAX: ffda RBX: 5603c0418a28 RCX: 7fa1d28855e1 [ 123.324060] RDX: RSI: 0001 RDI: 002d [ 123.325684] RBP: 7fa17550ae68 R08: R09: 0008 [ 123.327225] R10: R11: 0216 R12: 5603c0418b10 [ 123.328734] R13: 5603bdc48948 R14: 5603bdc48988 R15: [ 123.330247] [ 123.331740] Modules linked in: nft_masq nft_chain_nat zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) ebtable_filter ebtables ip6table_raw ip6table_mangle ip6table_nat ip6table_filter ip6_tables iptable_raw iptable_mangle iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 iptable_filter bpfilter nf_tables nfnetlink vhost_vsock vmw_vsock_virtio_transport_common vhost vhost_iotlb vsock unix_diag tls bridge stp llc binfmt_misc intel_rapl_msr mei_pxp mei_hdcp intel_rapl_common x86_pkg_temp_thermal intel_powerclamp snd_hda_codec_hdmi coretemp snd_hda_intel kvm_intel snd_intel_dspcfg kvm snd_intel_sdw_acpi snd_hda_codec rapl intel_cstate snd_hda_core joydev snd_hwdep input_leds at24 mei_me snd_pcm snd_timer mei snd soundcore mac_hid sch_fq_codel dm_multipath scsi_dh_rdac scsi_dh_
[Kernel-packages] [Bug 2009253] Re: nvidia-dkms-450-server FTBS with linux 6.2
** Also affects: nvidia-graphics-drivers-450-server (Ubuntu Jammy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-450-server in Ubuntu. https://bugs.launchpad.net/bugs/2009253 Title: nvidia-dkms-450-server FTBS with linux 6.2 Status in nvidia-graphics-drivers-450-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450-server source package in Jammy: New Status in nvidia-graphics-drivers-450-server source package in Lunar: Fix Released Bug description: [Impact] nvidia-dkms-450-server fails to build with linux 6.2, reporting the following error: /var/lib/dkms/nvidia-srv/450.216.04/build/nvidia/nv-acpi.c:84:19: error: initialization of ‘void (*)(struct acpi_device *)’ from incompatible pointer type ‘int (*)(struct acpi_device *, int)’ [-Werror=incompatible-pointer-types] 84 | .remove = nv_acpi_remove_two_args, | ^~~ [Fix] Change the driver to support also the 6.2 kernel ABI. [Test case] With linux 6.2 installed, run: $ sudo apt install nvidia-dkms-450-server [Regression potential] We may experience regressions in newer kernels (>= 6.2) that are using nvidia-dkms-450-server (source code for previous kernels remain unchanged). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-450-server/+bug/2009253/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1758512] Re: No virtual terminals (CTRL+ALT+F?) when no user logged in
** Tags removed: bionic ** Tags added: focal -- 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/1758512 Title: No virtual terminals (CTRL+ALT+F?) when no user logged in Status in gdm3 package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in plasma-desktop package in Ubuntu: Confirmed Bug description: As of today's 18.04 version, on a dell xps-13 (the old i7-4500U one), to reproduce: - boot Ubuntu - Press Ctrl+Alt+F2 (or F3 or...) Expected behaviour: virtual console should appear with login prompt. Actual behaviour: nothing happens. When a user is logged in, Ctrl+Alt+F3 switches to terminal tty3... However, hitting first Ctrl+Alt+F1 and, subsequently, hitting Ctrl+Alt+F3 does not show tty3, and remains at the graphical login screen but keyboard and mouse are unresponsive until either Ctrl+Alt+F1 or Ctrl+Alt+F? are pressed, being ? the virtual terminal the ubuntu session is running at. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.27.92-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Mar 24 10:11:26 2018 InstallationDate: Installed on 2014-05-05 (1418 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: Upgraded to bionic on 2018-03-22 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1758512/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1760201] Re: ubuntu 18.04 GDM - missing icons and letters on login screen with nouveau + Wayland
Thank you for reporting this bug to Ubuntu. Ubuntu 18.04 (bionic) reached end-of-standard-support on May 31, 2023. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it anymore. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in. ** Changed in: linux (Ubuntu) Status: Incomplete => Won't Fix ** Changed in: mesa (Ubuntu) Status: Confirmed => Won't Fix ** Changed in: mutter (Ubuntu) Status: Confirmed => Won't Fix -- 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/1760201 Title: ubuntu 18.04 GDM - missing icons and letters on login screen with nouveau + Wayland Status in linux package in Ubuntu: Won't Fix Status in mesa package in Ubuntu: Won't Fix Status in mutter package in Ubuntu: Won't Fix Bug description: WORKAROUND: Edit /etc/gdm3/custom.conf and uncomment: #WaylandEnable=false --- Ubuntu 18.04(Updated 30.03.2018) System Language: Turkish Please check screenshots --- ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-03-24 (9 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180324) Package: gnome-shell PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Tags: bionic Uname: Linux 4.15.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1760201/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1782347] Re: [radeon] GDM3 fails to load without nomodeset
Thank you for reporting this bug to Ubuntu. Ubuntu 18.04 (bionic) reached end-of-standard-support on May 31, 2023. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it anymore. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in. ** Changed in: gdm3 (Ubuntu) Status: Confirmed => Won't Fix ** Changed in: linux (Ubuntu) Status: Confirmed => Won't Fix ** Changed in: mutter (Ubuntu) Status: Confirmed => Won't Fix -- 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/1782347 Title: [radeon] GDM3 fails to load without nomodeset Status in gdm3 package in Ubuntu: Won't Fix Status in linux package in Ubuntu: Won't Fix Status in mutter package in Ubuntu: Won't Fix Bug description: Both with the livecd (usb drive) and the installed version, I must boot with the 'nomodeset' kernel parameter at GRUB; otherwise GDM3 will not boot (the screen will keep on flashing in semi-textual mode, with a white mouse arrow stuck). This, however, prevents me from using the 'radeon' video driver, dropping me to a very basic 1024x768 vesa mode. The bug did NOT occur on Ubuntu 12.04, so it is a regression. Also, the bug does NOT occur on XUbuntu/XFCE 18.04, so it is a GDM3-Gnome related thing. Thanks, MZ ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CasperVersion: 1.394 CurrentDesktop: ubuntu:GNOME Date: Wed Jul 18 12:18:06 2018 LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2018-07-18T12:14:53.871895 --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CasperVersion: 1.394 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: linux PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.gdm3.custom.conf: 2018-07-19T11:39:06.027905 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-07-12 (13 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: linux PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1782347/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860483] Re: [nouveau, GeForce 7300 LE] screen background overlaid with scan type artifact in red
Thank you for reporting this bug to Ubuntu. Ubuntu 18.04 (bionic) reached end-of-standard-support on May 31, 2023. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it anymore. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in. ** Changed in: linux (Ubuntu) Status: Confirmed => Won't Fix ** Changed in: mesa (Ubuntu) Status: Confirmed => Won't Fix ** Changed in: mutter (Ubuntu) Status: Confirmed => Won't Fix ** Changed in: xserver-xorg-video-nouveau (Ubuntu) Status: Confirmed => Won't Fix -- 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/1860483 Title: [nouveau, GeForce 7300 LE] screen background overlaid with scan type artifact in red Status in linux package in Ubuntu: Won't Fix Status in mesa package in Ubuntu: Won't Fix Status in mutter package in Ubuntu: Won't Fix Status in xserver-xorg-video-nouveau package in Ubuntu: Won't Fix Bug description: My desktop has both it's usual items in place; toolbar on left and desktop icons distributed around the screen. Then there's what appears to be a bunch of scan line, raster line artifacts, in red, laid over my normal background, which is a star field photo on what is ordinarily a black field. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18 Uname: Linux 4.15.0-74-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 21 13:04:20 2020 DistUpgraded: 2018-10-03 14:38:19,863 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G72 [GeForce 7300 LE] [10de:01d1] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell G72 [GeForce 7300 LE] [1028:0405] InstallationDate: Installed on 2016-08-19 (1249 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Inspiron 531 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-74-generic root=UUID=08d8f7c1-e351-4abe-8ebe-443d6a751497 ro plymouth:debug=1 quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2018-10-03 (474 days ago) dmi.bios.date: 11/09/2007 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.7 dmi.board.name: 0RY206 dmi.board.vendor: Dell Inc. dmi.board.version: ��� dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnDellInc.:bvr1.0.7:bd11/09/2007:svnDellInc.:pnInspiron531:pvr00:rvnDellInc.:rn0RY206:rvr:cvnDellInc.:ct3:cvrChassisVersion: dmi.product.name: Inspiron 531 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Wed Oct 3 10:41:28 2018 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputDell Dell USB Keyboard KEYBOARD, id 8 inputLogitech USB Trackball MOUSE, id 9 xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.8 xserver.video_driver: nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860483/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860178] Re: [nouveau] Desktop wallpaper is corrupt noise on GeForce 6150SE nForce 430
Thank you for reporting this bug to Ubuntu. Ubuntu 18.04 (bionic) reached end-of-standard-support on May 31, 2023. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it anymore. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in. ** Changed in: linux (Ubuntu) Status: Confirmed => Won't Fix ** Changed in: mesa (Ubuntu) Status: Confirmed => Won't Fix ** Changed in: mutter (Ubuntu) Status: Confirmed => Won't Fix -- 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/1860178 Title: [nouveau] Desktop wallpaper is corrupt noise on GeForce 6150SE nForce 430 Status in linux package in Ubuntu: Won't Fix Status in mesa package in Ubuntu: Won't Fix Status in mutter package in Ubuntu: Won't Fix Bug description: Graphic environment unstable, desktop background degraded. Seems consequently to last system upgrade (2020.jan.17) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompositorRunning: None Date: Fri Jan 17 21:55:59 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation C61 [GeForce 6150SE nForce 430] [10de:03d0] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] C61 [GeForce 6150SE nForce 430] [1025:0394] InstallationDate: Installed on 2019-08-03 (167 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 001 Device 003: ID 0bda:0158 Realtek Semiconductor Corp. USB 2.0 multicard reader Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 04f9:0027 Brother Industries, Ltd HL-2030 Laser Printer Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: eMachines EL1358 ProcEnviron: PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=52e5db54-2ea1-48ba-9efe-6b23d1188404 ro SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/20/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P01-B1 dmi.board.name: EL1358 dmi.board.vendor: eMachines dmi.chassis.type: 3 dmi.chassis.vendor: eMachines dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP01-B1:bd04/20/2011:svneMachines:pnEL1358:pvr:rvneMachines:rnEL1358:rvr:cvneMachines:ct3:cvr: dmi.product.family: eMachines Desktop dmi.product.name: EL1358 dmi.product.sku: To Be Filled By O.E.M. dmi.sys.vendor: eMachines version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860178/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1825626] Re: nvLock: client timed out, taking the lock
Thank you for reporting this bug to Ubuntu. Ubuntu 18.04 (bionic) reached end-of-standard-support on May 31, 2023. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it anymore. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in. ** Changed in: mutter (Ubuntu) Status: Confirmed => Won't Fix ** Changed in: nvidia-graphics-drivers-418 (Ubuntu) Status: Confirmed => Won't Fix ** Changed in: nvidia-graphics-drivers-430 (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-418 in Ubuntu. https://bugs.launchpad.net/bugs/1825626 Title: nvLock: client timed out, taking the lock Status in gnome-desktop: New Status in mutter package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-418 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-430 package in Ubuntu: Won't Fix Bug description: While launching an app or performing an operation, the screen has a certain chance to freeze for a few seconds and then recover. [ System Info ] Version : Ubuntu 19.04 Kernel : x86_64 Linux 5.0.0-13-generic GPU : NVIDIA GeForce GTX 1050 Xorg version : 1:7.7+19ubuntu12 Product Name : Aspire VX5-591G (Acer) [ Log File ] Uploaded as an attachment *Sorry for my not-good English. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] 是一个目录: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 418.56 Fri Mar 15 12:59:26 CDT 2019 GCC version: gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1) ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] 权限不够: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 20 17:19:29 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu DkmsStatus: nvidia, 418.56, 5.0.0-13-generic, x86_64: installed virtualbox, 6.0.6, 4.18.0-17-generic, x86_64: installed virtualbox, 6.0.6, 5.0.0-13-generic, x86_64: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] HD Graphics 630 [1025:1127] Subsystem: Acer Incorporated [ALI] GP107M [GeForce GTX 1050 Mobile] [1025:1128] MachineType: Acer Aspire VX5-591G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=a0525f6e-8c28-4e08-9c6e-9745ee51c18a ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/07/2017 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.06 dmi.board.asset.tag: Type2 - Board Serial Number dmi.board.name: Wish_KLS dmi.board.vendor: KBL dmi.board.version: V1.06 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.06 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.06:bd07/07/2017:svnAcer:pnAspireVX5-591G:pvrV1.06:rvnKBL:rnWish_KLS:rvrV1.06:cvnAcer:ct10:cvrV1.06: dmi.product.family: Aspire VX 15 dmi.product.name: Aspire VX5-591G dmi.product.sku: dmi.product.version: V1.06 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-desktop/+bug/1825626/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881909] Re: Screen tearing with Nvidia Optimus
** Tags removed: bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-440 in Ubuntu. https://bugs.launchpad.net/bugs/1881909 Title: Screen tearing with Nvidia Optimus Status in mutter package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Bug description: I have screen tearing when using nvidia card with 390 driver, affect browsers such as firefox and chromium also desktop since I have screen tearing when moving window around. I have no such problem when using using 18.04.4 and nvidia card with 390 driver. Intel graphic have no such problem weather in 18.04 or 20.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.132 Fri Nov 1 00:40:14 PDT 2019 GCC version: ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jun 3 21:18:49 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family Integrated Graphics Controller [1043:1652] NVIDIA Corporation GF119M [GeForce 610M] [10de:1058] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GeForce GT 610M [1043:1652] InstallationDate: Installed on 2020-06-01 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: ASUSTeK Computer Inc. K43SD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=8f02391a-a313-4598-b702-db7eccd55312 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/10/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: K43SD.208 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: K43SD dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrK43SD.208:bd08/10/2012:svnASUSTeKComputerInc.:pnK43SD:pvr1.0:rvnASUSTeKComputerInc.:rnK43SD:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.family: K dmi.product.name: K43SD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1881909/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2022053] [NEW] docker container cannot reach host with firewall enabled after kernel upgrade
Public bug reported:
$ lsb_release -rd
Description:Ubuntu 22.04.2 LTS
Release:22.04
I have the following kernels installed:
$ apt list --installed | grep linux-image
linux-image-5.19.0-41-generic/jammy-updates,jammy-security,now
5.19.0-41.42~22.04.1 amd64 [installed,auto-removable]
linux-image-5.19.0-42-generic/jammy-updates,jammy-security,now
5.19.0-42.43~22.04.1 amd64 [installed,automatic]
linux-image-5.19.0-43-generic/jammy-updates,jammy-security,now
5.19.0-43.44~22.04.1 amd64 [installed,automatic]
linux-image-generic-hwe-22.04/jammy-updates,jammy-security,now
5.19.0.43.44~22.04.17 amd64 [installed,automatic]
The following setup worked with 41 (and still works when I just boot
using that kernel) but broke with 42 (and does not work in 43 either).
I have docker installed (tried both version 23 and recently released
24).
I have ufw installed with the following extra setup:
$ sudo cat /etc/ufw/after.rules
#
# rules.input-after
#
# Rules that should be run after the ufw command line added rules. Custom
# rules should be added to one of these chains:
# ufw-after-input
# ufw-after-output
# ufw-after-forward
#
# Don't delete these required lines, otherwise there will be errors
*filter
:ufw-after-input - [0:0]
:ufw-after-output - [0:0]
:ufw-after-forward - [0:0]
# End required lines
# Allow containers to access host
-A ufw-after-input -p tcp -m physdev --physdev-in veth+ -j ACCEPT -m comment
--comment 'Allow_docker_tcp'
-A ufw-after-input -p udp -m physdev --physdev-in veth+ -j ACCEPT -m comment
--comment 'Allow_docker_udp'
-A ufw-after-input -p icmp -m physdev --physdev-in veth+ -j ACCEPT -m comment
--comment 'Allow_docker_icmp'
# don't log noisy services by default
-A ufw-after-input -p udp --dport 137 -j ufw-skip-to-policy-input
-A ufw-after-input -p udp --dport 138 -j ufw-skip-to-policy-input
-A ufw-after-input -p tcp --dport 139 -j ufw-skip-to-policy-input
-A ufw-after-input -p tcp --dport 445 -j ufw-skip-to-policy-input
-A ufw-after-input -p udp --dport 67 -j ufw-skip-to-policy-input
-A ufw-after-input -p udp --dport 68 -j ufw-skip-to-policy-input
# don't log noisy broadcast
-A ufw-after-input -m addrtype --dst-type BROADCAST -j ufw-skip-to-policy-input
# don't delete the 'COMMIT' line or these rules won't be processed
COMMIT
Note those three rules for docker; these work in 41 but stop working
afterwards.
How to reproduce:
$ docker run --rm curlimages/curl http://172.17.0.1
% Total% Received % Xferd Average Speed TimeTime Time Current
Dload Upload Total SpentLeft Speed
0 00 00 0 0 0 --:--:-- 0:02:10 --:--:-- 0
curl: (28) Failed to connect to 172.17.0.1 port 80 after 130429 ms: Couldn't
connect to server
It times out after a long time. dmesg contains the following message:
[ 872.069093] [UFW BLOCK] IN=docker0 OUT=
MAC=02:42:55:c9:a5:6e:02:42:ac:11:00:03:08:00 SRC=172.17.0.3
DST=172.17.0.1 LEN=60 TOS=0x00 PREC=0x00 TTL=64 ID=27268 DF PROTO=TCP
SPT=56862 DPT=80 WINDOW=64240 RES=0x00 SYN URGP=0
To explain docker networking:
$ ip addr
1: lo: mtu 65536 qdisc noqueue state UNKNOWN group
default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eno1: mtu 1500 qdisc fq_codel state DOWN
group default qlen 1000
link/ether 34:48:ed:08:e1:f5 brd ff:ff:ff:ff:ff:ff
altname enp0s31f6
3: gpd0: mtu 1500 qdisc noop state DOWN group
default qlen 500
link/none
4: wlp59s0: mtu 1500 qdisc noqueue state UP
group default qlen 1000
link/ether 24:41:8c:c3:1d:01 brd ff:ff:ff:ff:ff:ff
inet 192.168.0.138/24 brd 192.168.0.255 scope global dynamic noprefixroute
wlp59s0
valid_lft 2519sec preferred_lft 2519sec
inet6 fe80::cb8e:fe0e:6131:d3fc/64 scope link noprefixroute
valid_lft forever preferred_lft forever
6: docker0: mtu 1500 qdisc noqueue state UP
group default
link/ether 02:42:55:c9:a5:6e brd ff:ff:ff:ff:ff:ff
inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0
valid_lft forever preferred_lft forever
inet6 fe80::42:55ff:fec9:a56e/64 scope link
valid_lft forever preferred_lft forever
8: veth17e77be@if7: mtu 1500 qdisc noqueue
master docker0 state UP group default
link/ether 72:cd:15:f8:84:2d brd ff:ff:ff:ff:ff:ff link-netnsid 0
inet6 fe80::70cd:15ff:fef8:842d/64 scope link
valid_lft forever preferred_lft forever
$ brctl show
bridge name bridge id STP enabled interfaces
docker0 8000.024255c9a56e no veth17e77be
$ docker network inspect bridge
[
{
"Name": "bridge",
"Id":
"f17a627c3397d0aaf496b7cac59a23a902fe66e14f2e820cd097f313680ccb88",
"Created": "2023-06-01T12:33:14.87479534+02:00",
"Scope": "local",
"Driver": "b
[Kernel-packages] [Bug 2020279] Re: Kernel warning after upgrade to 4.15.0.211.194
Thanks for the extra details. I tried to reproduce it locally today, and I couldn't. While checking the code and your logs, I suspect this is IPv6-specific, and my testing env is IPv4-only. I'll come back when I manage to reproduce it. My current suspicion is: commit e198bdd7ad2834c77567d59158e88363d2f0e05d Author: Kuniyuki Iwashima Date: Thu Feb 9 16:22:01 2023 -0800 dccp/tcp: Avoid negative sk_forward_alloc by ipv6_pinfo.pktoptions. BugLink: https://bugs.launchpad.net/bugs/2015399 commit ca43ccf41224b023fc290073d5603a755fd12eed upstream. This would confirm the above IPv6 theory. PS: The warning is generated by WARN_ON(sk->sk_forward_alloc) in sk_stream_kill_queues. -- 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/2020279 Title: Kernel warning after upgrade to 4.15.0.211.194 Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Confirmed Bug description: After rebooting into 4.15.0.211.194 on Ubuntu 18.04.6 the kernel started to produce the below warning. It did not seem to cause any major issue. Revering to 4.15.0.210 stopped the warning. The server is a Droplet at DigitalOcean with their monitoring/management agent installed. May 21 19:09:59 esolr kernel: [ 18.787737] [ cut here ] May 21 19:09:59 esolr kernel: [ 18.787803] WARNING: CPU: 0 PID: 1027 at /build/linux-RlFMDZ/linux-4.15.0/net/core/stream.c:212 sk_stream_kill_queues+0xed/0x110 May 21 19:09:59 esolr kernel: [ 18.787804] Modules linked in: isofs xt_set nf_conntrack_ipv4 nf_defrag_ipv4 iptable_filter xt_conntrack nf_conntrack ip_set_hash_net ip_set nfnetlink nls_iso8859_1 kvm_intel kvm binfmt_misc irqbypass input_leds joydev serio_raw sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd glue_helper cryptd psmouse virtio_blk virtio_scsi virtio_net May 21 19:09:59 esolr kernel: [ 18.787835] CPU: 0 PID: 1027 Comm: unattended-upgr Not tainted 4.15.0-211-generic #222-Ubuntu May 21 19:09:59 esolr kernel: [ 18.787836] Hardware name: DigitalOcean Droplet/Droplet, BIOS 20171212 12/12/2017 May 21 19:09:59 esolr kernel: [ 18.787839] RIP: 0010:sk_stream_kill_queues+0xed/0x110 May 21 19:09:59 esolr kernel: [ 18.787840] RSP: :94bf7fc038c0 EFLAGS: 00010282 May 21 19:09:59 esolr kernel: [ 18.787841] RAX: 0024 RBX: 94bf79565500 RCX: 0006 May 21 19:09:59 esolr kernel: [ 18.787842] RDX: RSI: 94bf7fc1b4d8 RDI: 94bf7fc1b4d0 May 21 19:09:59 esolr kernel: [ 18.787842] RBP: 94bf7fc038d0 R08: 0222 R09: 0004 May 21 19:09:59 esolr kernel: [ 18.787843] R10: 94bf7fc03860 R11: 0001 R12: 94bf795655c8 May 21 19:09:59 esolr kernel: [ 18.787844] R13: 0006 R14: 003b R15: May 21 19:09:59 esolr kernel: [ 18.787845] FS: 7f04071d4740() GS:94bf7fc0() knlGS: May 21 19:09:59 esolr kernel: [ 18.787846] CS: 0010 DS: ES: CR0: 80050033 May 21 19:09:59 esolr kernel: [ 18.787846] CR2: 7f0401995e60 CR3: 67586002 CR4: 001606f0 May 21 19:09:59 esolr kernel: [ 18.787850] DR0: DR1: DR2: May 21 19:09:59 esolr kernel: [ 18.787851] DR3: DR6: fffe0ff0 DR7: 0400 May 21 19:09:59 esolr kernel: [ 18.787851] Call Trace: May 21 19:09:59 esolr kernel: [ 18.787853] May 21 19:09:59 esolr kernel: [ 18.787866] inet_csk_destroy_sock+0x59/0x150 May 21 19:09:59 esolr kernel: [ 18.787868] tcp_done+0x96/0xa0 May 21 19:09:59 esolr kernel: [ 18.787872] tcp_time_wait+0x1be/0x280 May 21 19:09:59 esolr kernel: [ 18.787874] tcp_fin+0x16b/0x180 May 21 19:09:59 esolr kernel: [ 18.787876] tcp_data_queue+0x594/0xc20 May 21 19:09:59 esolr kernel: [ 18.787881] tcp_rcv_state_process+0x5dd/0xe70 May 21 19:09:59 esolr kernel: [ 18.787887] ? __slab_alloc+0x20/0x40 May 21 19:09:59 esolr kernel: [ 18.787889] ? kmem_cache_alloc+0x161/0x1c0 May 21 19:09:59 esolr kernel: [ 18.787891] ? skb_clone+0x56/0xc0 May 21 19:09:59 esolr kernel: [ 18.787897] tcp_v6_do_rcv+0x1ca/0x440 May 21 19:09:59 esolr kernel: [ 18.787898] ? tcp_v6_do_rcv+0x1ca/0x440 May 21 19:09:59 esolr kernel: [ 18.787899] tcp_v6_rcv+0x9b6/0xa60 May 21 19:09:59 esolr kernel: [ 18.787907] ? update_load_avg+0x5f9/0x780 May 21 19:09:59 esolr kernel: [ 18.787909] ip6_input_finish+0xcc/0x470
[Kernel-packages] [Bug 2019979] Re: nvidia-dkms-* FTBS with linux 6.3
** Patch added: "nvidia-graphics-drivers-450-server_450.236.01-0ubuntu3.debdiff" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2019979/+attachment/5677154/+files/nvidia-graphics-drivers-450-server_450.236.01-0ubuntu3.debdiff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/2019979 Title: nvidia-dkms-* FTBS with linux 6.3 Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450-server package in Ubuntu: New Status in nvidia-graphics-drivers-470 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-470-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-510 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-515 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-515-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 source package in Mantic: Fix Released Status in nvidia-graphics-drivers-450-server source package in Mantic: New Status in nvidia-graphics-drivers-470 source package in Mantic: Fix Released Status in nvidia-graphics-drivers-470-server source package in Mantic: Fix Released Status in nvidia-graphics-drivers-510 source package in Mantic: Fix Released Status in nvidia-graphics-drivers-515 source package in Mantic: Fix Released Status in nvidia-graphics-drivers-515-server source package in Mantic: Fix Released Bug description: [Impact] /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c: In function ‘nvidia_mmap_helper’: /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:474:23: error: assignment of read-only member ‘vm_flags’ 474 | vma->vm_flags |= VM_IO; | ^~ /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:536:23: error: assignment of read-only member ‘vm_flags’ 536 | vma->vm_flags |= (VM_IO | VM_LOCKED | VM_RESERVED); | ^~ /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:537:23: error: assignment of read-only member ‘vm_flags’ 537 | vma->vm_flags |= (VM_DONTEXPAND | VM_DONTDUMP); | ^~ /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:543:23: error: assignment of read-only member ‘vm_flags’ 543 | vma->vm_flags &= ~VM_WRITE; | ^~ /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:544:23: error: assignment of read-only member ‘vm_flags’ 544 | vma->vm_flags &= ~VM_MAYWRITE; | ^~ [Fix] Apply the attached patch. [How to test] Build the dkms package and install it. [Regression potential] This patch doesn't come from NVIDIA itself, so there's a regression potential, though i can't state how severe that could be. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2019979/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2022061] [NEW] package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: installed linux-headers-6.2.0-20-generic package post-installation script subprocess
Public bug reported: this bug appeared after I tried to upgrade to 23.04 from 22.10, every time I tried to restart the computer, the computer ended up in kernel panic. I was not able to remove the extra package and instead I am starting the computer with an older version of kernel (Ubuntu 5.19.0-41.42-generic 5.19.17 as stated in the version.log). The information from the ubuntu-bug linux is therefore not too helpful as it only reports that I am running an unsupported kernel and I should try again to run the report with a new kernel which is not possible. I am using release 23.04 The system was not able to to locate package pkgname. I expected the kernel to be upgraded with the new one 6.20.* and the computer run smoothly, instead, the computer ends up in kernel panic and I needed to start the machine with an older version of kernel. ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-headers-6.2.0-20-generic 6.2.0-20.20 ProcVersionSignature: Ubuntu 5.19.0-41.42-generic 5.19.17 Uname: Linux 5.19.0-41-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 AptOrdering: snapd:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: unknown Date: Thu Jun 1 07:56:17 2023 DpkgHistoryLog: Start-Date: 2023-06-01 07:55:39 Commandline: /usr/bin/unattended-upgrade Upgrade: snapd:amd64 (2.59.1+23.04ubuntu1, 2.59.1+23.04ubuntu1.1) ErrorMessage: installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-02-25 (1191 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. Precision 7920 Tower ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-41-generic root=UUID=380d0a7f-8500-4b5f-b8ba-80548f634c14 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. Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.06-2ubuntu16 RfKill: SourcePackage: linux Title: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to lunar on 2023-05-12 (19 days ago) dmi.bios.date: 07/29/2019 dmi.bios.release: 2.1 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.1.4 dmi.board.name: 060K5C dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.1.4:bd07/29/2019:br2.1:svnDellInc.:pnPrecision7920Tower:pvr:rvnDellInc.:rn060K5C:rvrA00:cvnDellInc.:ct3:cvr:sku073A: dmi.product.family: Precision dmi.product.name: Precision 7920 Tower dmi.product.sku: 073A dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package lunar ** Attachment added: "lspci-vnvn.log" https://bugs.launchpad.net/bugs/2022061/+attachment/5677155/+files/lspci-vnvn.log -- 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/2022061 Title: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 Status in linux package in Ubuntu: New Bug description: this bug appeared after I tried to upgrade to 23.04 from 22.10, every time I tried to restart the computer, the computer ended up in kernel panic. I was not able to remove the extra package and instead I am starting the computer with an older version of kernel (Ubuntu 5.19.0-41.42-generic 5.19.17 as stated in the version.log). The information from the ubuntu-bug linux is therefore not too helpful as it only reports that I am running an unsupported kernel and I should try again to run the report with a new kernel which is not possible. I am using release23.04 The system was not able to to locate package pkgname. I expected the kernel to be upgraded with the new one 6.20.* and the computer run smoothly, instead, the computer ends up in kernel panic and I needed to start the machine with an older version of kernel. ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-headers-6.2.0-20-generic 6.2.0-20.20 ProcVersionSignature: Ubuntu 5.19.0-41.42-generic 5.19.17 Uname: Linux 5.19.0-41-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 AptOrdering: snapd:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: unknown Date: Thu Jun 1 07:56:17 2023 DpkgHistoryLog: Start-Date: 2023-06-01 07:55:39 Commandline: /usr/bin/unattended-upgrade Upgrade: snapd:amd64 (2.59.1+23.04ubuntu1, 2.59.1+23.04ubuntu1.1
[Kernel-packages] [Bug 2022061] Re: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: installed linux-headers-6.2.0-20-generic package post-installation script subprocess r
** Tags removed: need-duplicate-check -- 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/2022061 Title: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 Status in linux package in Ubuntu: Confirmed Bug description: this bug appeared after I tried to upgrade to 23.04 from 22.10, every time I tried to restart the computer, the computer ended up in kernel panic. I was not able to remove the extra package and instead I am starting the computer with an older version of kernel (Ubuntu 5.19.0-41.42-generic 5.19.17 as stated in the version.log). The information from the ubuntu-bug linux is therefore not too helpful as it only reports that I am running an unsupported kernel and I should try again to run the report with a new kernel which is not possible. I am using release23.04 The system was not able to to locate package pkgname. I expected the kernel to be upgraded with the new one 6.20.* and the computer run smoothly, instead, the computer ends up in kernel panic and I needed to start the machine with an older version of kernel. ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-headers-6.2.0-20-generic 6.2.0-20.20 ProcVersionSignature: Ubuntu 5.19.0-41.42-generic 5.19.17 Uname: Linux 5.19.0-41-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 AptOrdering: snapd:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: unknown Date: Thu Jun 1 07:56:17 2023 DpkgHistoryLog: Start-Date: 2023-06-01 07:55:39 Commandline: /usr/bin/unattended-upgrade Upgrade: snapd:amd64 (2.59.1+23.04ubuntu1, 2.59.1+23.04ubuntu1.1) ErrorMessage: installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-02-25 (1191 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. Precision 7920 Tower ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-41-generic root=UUID=380d0a7f-8500-4b5f-b8ba-80548f634c14 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. Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.06-2ubuntu16 RfKill: SourcePackage: linux Title: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to lunar on 2023-05-12 (19 days ago) dmi.bios.date: 07/29/2019 dmi.bios.release: 2.1 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.1.4 dmi.board.name: 060K5C dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.1.4:bd07/29/2019:br2.1:svnDellInc.:pnPrecision7920Tower:pvr:rvnDellInc.:rn060K5C:rvrA00:cvnDellInc.:ct3:cvr:sku073A: dmi.product.family: Precision dmi.product.name: Precision 7920 Tower dmi.product.sku: 073A dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2022061/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2022061] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2022061 Title: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 Status in linux package in Ubuntu: Confirmed Bug description: this bug appeared after I tried to upgrade to 23.04 from 22.10, every time I tried to restart the computer, the computer ended up in kernel panic. I was not able to remove the extra package and instead I am starting the computer with an older version of kernel (Ubuntu 5.19.0-41.42-generic 5.19.17 as stated in the version.log). The information from the ubuntu-bug linux is therefore not too helpful as it only reports that I am running an unsupported kernel and I should try again to run the report with a new kernel which is not possible. I am using release23.04 The system was not able to to locate package pkgname. I expected the kernel to be upgraded with the new one 6.20.* and the computer run smoothly, instead, the computer ends up in kernel panic and I needed to start the machine with an older version of kernel. ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-headers-6.2.0-20-generic 6.2.0-20.20 ProcVersionSignature: Ubuntu 5.19.0-41.42-generic 5.19.17 Uname: Linux 5.19.0-41-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 AptOrdering: snapd:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: unknown Date: Thu Jun 1 07:56:17 2023 DpkgHistoryLog: Start-Date: 2023-06-01 07:55:39 Commandline: /usr/bin/unattended-upgrade Upgrade: snapd:amd64 (2.59.1+23.04ubuntu1, 2.59.1+23.04ubuntu1.1) ErrorMessage: installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-02-25 (1191 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. Precision 7920 Tower ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-41-generic root=UUID=380d0a7f-8500-4b5f-b8ba-80548f634c14 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. Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.06-2ubuntu16 RfKill: SourcePackage: linux Title: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to lunar on 2023-05-12 (19 days ago) dmi.bios.date: 07/29/2019 dmi.bios.release: 2.1 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.1.4 dmi.board.name: 060K5C dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.1.4:bd07/29/2019:br2.1:svnDellInc.:pnPrecision7920Tower:pvr:rvnDellInc.:rn060K5C:rvrA00:cvnDellInc.:ct3:cvr:sku073A: dmi.product.family: Precision dmi.product.name: Precision 7920 Tower dmi.product.sku: 073A dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2022061/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2019869] Re: nvidia-dkms-390: better support for kernel 6.2
I've been able to install the latest package from lunar-proposed on my HP Elitebook 8570W. Ubuntu boots but as with the previous version, no GUI but just a black screen with white blinking underscore. Only fix is to change to another tty and deinstall. I have searched in dmesg for any errors but there were none. What logs are of interest to share? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/2019869 Title: nvidia-dkms-390: better support for kernel 6.2 Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 source package in Jammy: Fix Committed Status in nvidia-graphics-drivers-390 source package in Lunar: Fix Released Status in nvidia-graphics-drivers-390 source package in Mantic: Fix Released Bug description: [Impact] Instead of disabling acpi support completely with nvidia-dkms-390, we should try instead to see if it's possible to support it somehow. [Fix] This patch looks promising (even if it says huge hack in the comments...): https://gitlab.com/herecura/packages/nvidia-390xx-dkms/-/blob/780a3c8b159f24c14e6c1cb35fd747338aefea39/kernel-6.2.patch Apply this patch and drop any 6.0 and 6.2 related patches. [Regression potential] With this patch nvidia-dkms-390 should build against 6.2 kernels without disabling any feature, but users of this driver may experience kernel bugs / crashes. However, the nvidia 390 driver is unmaintained so we should start to consider phasing it out. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2019869/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2019869] Re: nvidia-dkms-390: better support for kernel 6.2
** Changed in: nvidia-graphics-drivers-390 (Ubuntu Lunar) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/2019869 Title: nvidia-dkms-390: better support for kernel 6.2 Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 source package in Jammy: Fix Committed Status in nvidia-graphics-drivers-390 source package in Lunar: Fix Released Status in nvidia-graphics-drivers-390 source package in Mantic: Fix Released Bug description: [Impact] Instead of disabling acpi support completely with nvidia-dkms-390, we should try instead to see if it's possible to support it somehow. [Fix] This patch looks promising (even if it says huge hack in the comments...): https://gitlab.com/herecura/packages/nvidia-390xx-dkms/-/blob/780a3c8b159f24c14e6c1cb35fd747338aefea39/kernel-6.2.patch Apply this patch and drop any 6.0 and 6.2 related patches. [Regression potential] With this patch nvidia-dkms-390 should build against 6.2 kernels without disabling any feature, but users of this driver may experience kernel bugs / crashes. However, the nvidia 390 driver is unmaintained so we should start to consider phasing it out. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2019869/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2020279] Re: Kernel warning after upgrade to 4.15.0.211.194
My Droplet has an IPv6 address, and traffic on that is even less frequent than IPv4, so the sporadic occurrence we saw could be explained by that. -- 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/2020279 Title: Kernel warning after upgrade to 4.15.0.211.194 Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Confirmed Bug description: After rebooting into 4.15.0.211.194 on Ubuntu 18.04.6 the kernel started to produce the below warning. It did not seem to cause any major issue. Revering to 4.15.0.210 stopped the warning. The server is a Droplet at DigitalOcean with their monitoring/management agent installed. May 21 19:09:59 esolr kernel: [ 18.787737] [ cut here ] May 21 19:09:59 esolr kernel: [ 18.787803] WARNING: CPU: 0 PID: 1027 at /build/linux-RlFMDZ/linux-4.15.0/net/core/stream.c:212 sk_stream_kill_queues+0xed/0x110 May 21 19:09:59 esolr kernel: [ 18.787804] Modules linked in: isofs xt_set nf_conntrack_ipv4 nf_defrag_ipv4 iptable_filter xt_conntrack nf_conntrack ip_set_hash_net ip_set nfnetlink nls_iso8859_1 kvm_intel kvm binfmt_misc irqbypass input_leds joydev serio_raw sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd glue_helper cryptd psmouse virtio_blk virtio_scsi virtio_net May 21 19:09:59 esolr kernel: [ 18.787835] CPU: 0 PID: 1027 Comm: unattended-upgr Not tainted 4.15.0-211-generic #222-Ubuntu May 21 19:09:59 esolr kernel: [ 18.787836] Hardware name: DigitalOcean Droplet/Droplet, BIOS 20171212 12/12/2017 May 21 19:09:59 esolr kernel: [ 18.787839] RIP: 0010:sk_stream_kill_queues+0xed/0x110 May 21 19:09:59 esolr kernel: [ 18.787840] RSP: :94bf7fc038c0 EFLAGS: 00010282 May 21 19:09:59 esolr kernel: [ 18.787841] RAX: 0024 RBX: 94bf79565500 RCX: 0006 May 21 19:09:59 esolr kernel: [ 18.787842] RDX: RSI: 94bf7fc1b4d8 RDI: 94bf7fc1b4d0 May 21 19:09:59 esolr kernel: [ 18.787842] RBP: 94bf7fc038d0 R08: 0222 R09: 0004 May 21 19:09:59 esolr kernel: [ 18.787843] R10: 94bf7fc03860 R11: 0001 R12: 94bf795655c8 May 21 19:09:59 esolr kernel: [ 18.787844] R13: 0006 R14: 003b R15: May 21 19:09:59 esolr kernel: [ 18.787845] FS: 7f04071d4740() GS:94bf7fc0() knlGS: May 21 19:09:59 esolr kernel: [ 18.787846] CS: 0010 DS: ES: CR0: 80050033 May 21 19:09:59 esolr kernel: [ 18.787846] CR2: 7f0401995e60 CR3: 67586002 CR4: 001606f0 May 21 19:09:59 esolr kernel: [ 18.787850] DR0: DR1: DR2: May 21 19:09:59 esolr kernel: [ 18.787851] DR3: DR6: fffe0ff0 DR7: 0400 May 21 19:09:59 esolr kernel: [ 18.787851] Call Trace: May 21 19:09:59 esolr kernel: [ 18.787853] May 21 19:09:59 esolr kernel: [ 18.787866] inet_csk_destroy_sock+0x59/0x150 May 21 19:09:59 esolr kernel: [ 18.787868] tcp_done+0x96/0xa0 May 21 19:09:59 esolr kernel: [ 18.787872] tcp_time_wait+0x1be/0x280 May 21 19:09:59 esolr kernel: [ 18.787874] tcp_fin+0x16b/0x180 May 21 19:09:59 esolr kernel: [ 18.787876] tcp_data_queue+0x594/0xc20 May 21 19:09:59 esolr kernel: [ 18.787881] tcp_rcv_state_process+0x5dd/0xe70 May 21 19:09:59 esolr kernel: [ 18.787887] ? __slab_alloc+0x20/0x40 May 21 19:09:59 esolr kernel: [ 18.787889] ? kmem_cache_alloc+0x161/0x1c0 May 21 19:09:59 esolr kernel: [ 18.787891] ? skb_clone+0x56/0xc0 May 21 19:09:59 esolr kernel: [ 18.787897] tcp_v6_do_rcv+0x1ca/0x440 May 21 19:09:59 esolr kernel: [ 18.787898] ? tcp_v6_do_rcv+0x1ca/0x440 May 21 19:09:59 esolr kernel: [ 18.787899] tcp_v6_rcv+0x9b6/0xa60 May 21 19:09:59 esolr kernel: [ 18.787907] ? update_load_avg+0x5f9/0x780 May 21 19:09:59 esolr kernel: [ 18.787909] ip6_input_finish+0xcc/0x470 May 21 19:09:59 esolr kernel: [ 18.787911] ip6_input+0x3f/0xb0 May 21 19:09:59 esolr kernel: [ 18.787914] ? ip6_dst_check+0xb1/0xf0 May 21 19:09:59 esolr kernel: [ 18.787915] ip6_rcv_finish+0xd8/0x120 May 21 19:09:59 esolr kernel: [ 18.787916] ipv6_rcv+0x347/0x510 May 21 19:09:59 esolr kernel: [ 18.787917] ? __pskb_pull_tail+0x7f/0x4b0 May 21 19:09:59 esolr kernel: [ 18.787918] ? skb_copy_bits+0x141/0x280 May 21 19:09:59 esolr kernel: [ 18.787920] ? __kmalloc_node_track_caller+0x216/0x2b0 May 21 19:09:59 e
[Kernel-packages] [Bug 2019450] Re: zfs-linux FTBFS with v6.2.8 stable updates
This bug was fixed in the package zfs-linux - 2.1.9-2ubuntu1.1 --- zfs-linux (2.1.9-2ubuntu1.1) lunar; urgency=medium * Cherry-pick upstream fix to address FTBFS with v6.2.8+. LP: #2019450 -- Dimitri John Ledkov Sat, 13 May 2023 00:49:15 +0100 ** Changed in: zfs-linux (Ubuntu Lunar) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/2019450 Title: zfs-linux FTBFS with v6.2.8 stable updates Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Jammy: New Status in zfs-linux source package in Lunar: Fix Released Status in zfs-linux source package in Mantic: Fix Released Bug description: [ Impact ] * Stable kernel updates changed signature of a function call, thus zfs-linux needs adapting. Otherwise it fallsback to older symbols, which are GPL only. [ Test Plan ] * linux 6.2 with 6.2.8 stable updates builds with zfs, without this fix build fails with MODPOST <>/build/zfs/2.1.9/build/module/Module.symvers ERROR: modpost: GPL-incompatible module zfs.ko uses GPL-only symbol 'bio_start_io_acct' ERROR: modpost: GPL-incompatible module zfs.ko uses GPL-only symbol 'bio_end_io_acct_remapped' make[5]: *** [scripts/Makefile.modpost:138: <>/build/zfs/2.1.9/build/module/Module.symvers] Error 1 as the signature of the non-gpl function call has changed, zfs configure scripts fail to detect it as available, fallback on a gpl symbol, which we then prohibit from using. [ Where problems could occur ] * This is a cherry-pick of build-compat only, without any other changes [ Other Info ] * Upstream commit https://github.com/openzfs/zfs/pull/14677/commits/1a951502f0b4200a13f23f0d2f5759ef60188c17 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2019450/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2019450] Update Released
The verification of the Stable Release Update for zfs-linux has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/2019450 Title: zfs-linux FTBFS with v6.2.8 stable updates Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Jammy: New Status in zfs-linux source package in Lunar: Fix Released Status in zfs-linux source package in Mantic: Fix Released Bug description: [ Impact ] * Stable kernel updates changed signature of a function call, thus zfs-linux needs adapting. Otherwise it fallsback to older symbols, which are GPL only. [ Test Plan ] * linux 6.2 with 6.2.8 stable updates builds with zfs, without this fix build fails with MODPOST <>/build/zfs/2.1.9/build/module/Module.symvers ERROR: modpost: GPL-incompatible module zfs.ko uses GPL-only symbol 'bio_start_io_acct' ERROR: modpost: GPL-incompatible module zfs.ko uses GPL-only symbol 'bio_end_io_acct_remapped' make[5]: *** [scripts/Makefile.modpost:138: <>/build/zfs/2.1.9/build/module/Module.symvers] Error 1 as the signature of the non-gpl function call has changed, zfs configure scripts fail to detect it as available, fallback on a gpl symbol, which we then prohibit from using. [ Where problems could occur ] * This is a cherry-pick of build-compat only, without any other changes [ Other Info ] * Upstream commit https://github.com/openzfs/zfs/pull/14677/commits/1a951502f0b4200a13f23f0d2f5759ef60188c17 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2019450/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2019869] Re: nvidia-dkms-390: better support for kernel 6.2
ho i clicked too quickly somewhere i changed something please do something to revert my stupidity -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/2019869 Title: nvidia-dkms-390: better support for kernel 6.2 Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 source package in Jammy: Fix Committed Status in nvidia-graphics-drivers-390 source package in Lunar: Fix Released Status in nvidia-graphics-drivers-390 source package in Mantic: Fix Released Bug description: [Impact] Instead of disabling acpi support completely with nvidia-dkms-390, we should try instead to see if it's possible to support it somehow. [Fix] This patch looks promising (even if it says huge hack in the comments...): https://gitlab.com/herecura/packages/nvidia-390xx-dkms/-/blob/780a3c8b159f24c14e6c1cb35fd747338aefea39/kernel-6.2.patch Apply this patch and drop any 6.0 and 6.2 related patches. [Regression potential] With this patch nvidia-dkms-390 should build against 6.2 kernels without disabling any feature, but users of this driver may experience kernel bugs / crashes. However, the nvidia 390 driver is unmaintained so we should start to consider phasing it out. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2019869/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2020757] Re: Kernel BUG (null ptr dereference) with linux-image-5.19.0-42-generic (HWE kernel on 22.04)
It's affecting me as well. Had to roll back to 5.19.0-41 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2020757 Title: Kernel BUG (null ptr dereference) with linux-image-5.19.0-42-generic (HWE kernel on 22.04) Status in linux-signed-hwe-5.19 package in Ubuntu: Confirmed Bug description: I use Ubuntu 22.04 in VMWare Player 17.0.2 (Windows host, due to corporate IT...). I installed the HWE kernel since I have an Intel CPU with P/E-cores. 3D acceleration is enabled in VMWare. With linux-image-5.19.0-41-generic it is rock solid. With linux- image-5.19.0-42-generic it invariably crashes after anything between a minute and an hour. In the journalctl after rebooting it showed that X.Org had crashed followed by a Kernel BUG/Oops due to NULL pointer dereference in drm_gem_object_release_handle. A journalctl log from the Xorg crash up until the kernel OOPS has been attached to this case. This issue happened twice with this kernel. In addition, after trying to reproduce it with kdump tools installed, I got a different issue: refcount_t: saturated; leaking memory. in the log, leading to the OOM killing everything on the system, including (based on what was printed on the terminal), systemd-udevd and journald. That OOM killing never made it into the journal however, as can be expected. I have attached what I could get from the journal for this case as well. One thing that helped trigger this bug (but not every time) was launching Firefox, but once it didn't crash from that and only crashed much much later. Unfortunately I could not get ubuntu-bug to work for this case. I tried "ubuntu-bug --package linux-image-5.19.0-42-generic" but it did absolutely nothing. I'm happy to provide any additional information you require however. $ lsb_release -rd Description: Ubuntu 22.04.2 LTS Release: 22.04 $ apt-cache policy linux-generic-hwe-22.04 linux-generic-hwe-22.04: Installed: 5.19.0.42.43~22.04.15 Candidate: 5.19.0.42.43~22.04.15 Version table: *** 5.19.0.42.43~22.04.15 500 500 http://se.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 100 /var/lib/dpkg/status 5.15.0.25.27 500 500 http://se.archive.ubuntu.com/ubuntu jammy/main amd64 Packages $ apt-cache policy linux-image-5.19.0-42-generic linux-image-5.19.0-42-generic: Installed: 5.19.0-42.43~22.04.1 Candidate: 5.19.0-42.43~22.04.1 Version table: *** 5.19.0-42.43~22.04.1 500 500 http://se.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 100 /var/lib/dpkg/status What I expected to happen: No crash. What happened instead: The crash in the attached log. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2020757/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2015369] Re: Azure: Add PCI pass-thru support to Hyper-V Confidential VMs
** Changed in: linux-azure (Ubuntu Lunar) Status: Fix Released => Fix Committed ** Changed in: linux-azure (Ubuntu Jammy) Status: In Progress => Won't Fix -- 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/2015369 Title: Azure: Add PCI pass-thru support to Hyper-V Confidential VMs Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Jammy: Won't Fix Status in linux-azure source package in Kinetic: Fix Committed Status in linux-azure source package in Lunar: Fix Committed Bug description: SRU Justification [Impact] Microsoft has requested the inclusion of this patch set: https://lore.kernel.org/linux-hyperv/1679838727-87310-1-git-send- email-mikel...@microsoft.com/T/ [Regression Potential] Private memory mappings could be incorrect. [Test Plan] Microsoft tested. [Other Info] SF: #00355859 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2015369/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950627] Re: ubuntu_kernel_selftests:net:udpgro_fwd.sh: udpgso_bench_tx: sendmsg: Connection refused
** Merge proposal linked: https://code.launchpad.net/~canonical-kernel-team/+git/rt-hints/+merge/443985 -- 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/1950627 Title: ubuntu_kernel_selftests:net:udpgro_fwd.sh: udpgso_bench_tx: sendmsg: Connection refused Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Jammy: Confirmed Status in linux source package in Kinetic: Confirmed Bug description: This is from ADT testing (amd64) but I believe I occasionally saw this before. It feels like sometimes the receiver does not get ready before the transmission starts. IIRC this goes away when re-trying. 02:52:31 DEBUG| [stdout] # selftests: net: udpgro_fwd.sh 02:52:31 DEBUG| [stdout] # IPv4 02:52:31 DEBUG| [stdout] # No GRO ok 02:52:32 DEBUG| [stdout] # GRO frag listok 02:52:32 DEBUG| [stdout] # GRO fwd ok 02:52:33 DEBUG| [stdout] # UDP fwd perfudp rx: 333 MB/s 271894 calls/s 02:52:33 DEBUG| [stdout] # udp tx:378 MB/s 6422 calls/s 6422 msg/s 02:52:34 DEBUG| [stdout] # udp rx:383 MB/s 312480 calls/s 02:52:34 DEBUG| [stdout] # udp tx:383 MB/s 6506 calls/s 6506 msg/s 02:52:35 DEBUG| [stdout] # udp rx:381 MB/s 310202 calls/s 02:52:35 DEBUG| [stdout] # udp tx:380 MB/s 6458 calls/s 6458 msg/s 02:52:36 DEBUG| [stdout] # UDP GRO fwd perfudp rx: 344 MB/s 280814 calls/s 02:52:36 DEBUG| [stdout] # udp tx:389 MB/s 6612 calls/s 6612 msg/s 02:52:37 DEBUG| [stdout] # udp rx:364 MB/s 297088 calls/s 02:52:37 DEBUG| [stdout] # udp tx:383 MB/s 6512 calls/s 6512 msg/s 02:52:38 DEBUG| [stdout] # udp rx:448 MB/s 365435 calls/s 02:52:38 DEBUG| [stdout] # udp tx:453 MB/s 7686 calls/s 7686 msg/s 02:52:39 DEBUG| [stdout] # GRO frag list over UDP tunnelok 02:52:39 DEBUG| [stdout] # GRO fwd over UDP tunnel ok 02:52:39 DEBUG| [stdout] # UDP tunnel fwd perf ./udpgso_bench_tx: sendmsg: Connection refused 02:52:39 DEBUG| [stdout] # fail client exit code 1, server 0 02:52:40 DEBUG| [stdout] # UDP tunnel GRO fwd perf udp rx: 236 MB/s 192389 calls/s 02:52:41 DEBUG| [stdout] # udp tx:284 MB/s 4826 calls/s 4826 msg/s 02:52:41 DEBUG| [stdout] # udp rx:295 MB/s 240586 calls/s 02:52:42 DEBUG| [stdout] # udp tx:306 MB/s 5206 calls/s 5206 msg/s 02:52:42 DEBUG| [stdout] # udp rx:306 MB/s 249784 calls/s 02:52:43 DEBUG| [stdout] # udp tx:310 MB/s 5263 calls/s 5263 msg/s 02:52:43 DEBUG| [stdout] # IPv6 02:52:43 DEBUG| [stdout] # No GRO ok 02:52:43 DEBUG| [stdout] # GRO frag listok 02:52:43 DEBUG| [stdout] # GRO fwd ok 02:52:44 DEBUG| [stdout] # UDP fwd perfudp rx: 82 MB/s66844 calls/s 02:52:45 DEBUG| [stdout] # udp tx:334 MB/s 5668 calls/s 5668 msg/s 02:52:45 DEBUG| [stdout] # udp rx:374 MB/s 305206 calls/s 02:52:46 DEBUG| [stdout] # udp tx:375 MB/s 6377 calls/s 6377 msg/s 02:52:46 DEBUG| [stdout] # udp rx:373 MB/s 303948 calls/s 02:52:47 DEBUG| [stdout] # udp tx:371 MB/s 6299 calls/s 6299 msg/s 02:52:48 DEBUG| [stdout] # UDP GRO fwd perfudp rx: 340 MB/s 277046 calls/s 02:52:48 DEBUG| [stdout] # udp tx:389 MB/s 6601 calls/s 6601 msg/s 02:52:49 DEBUG| [stdout] # udp rx:390 MB/s 318311 calls/s 02:52:49 DEBUG| [stdout] # udp tx:391 MB/s 6639 calls/s 6639 msg/s 02:52:50 DEBUG| [stdout] # udp rx:396 MB/s 322528 calls/s 02:52:50 DEBUG| [stdout] # udp tx:406 MB/s 6891 calls/s 6891 msg/s 02:52:50 DEBUG| [stdout] # GRO frag list over UDP tunnelok 02:52:50 DEBUG| [stdout] # GRO fwd over UDP tunnel ok 02:52:52 DEBUG| [stdout] # UDP tunnel fwd perf udp rx: 93 MB/s76354 calls/s 02:52:52 DEBUG| [stdout] # udp tx:257 MB/s 4360 calls/s 4360 msg/s 02:52:53 DEBUG| [stdout] # udp rx:297 MB/s 241883 calls/s 02:52:53 DEBUG| [stdout] # udp tx:315 MB/s 5352 calls/s 5352 msg/s 02:52:54 DEBUG| [stdout] # udp rx:286 MB/s 233207 calls/s 02:52:54 DEBUG| [stdout] # udp tx:304 MB/s 5172 calls/s 5172 msg/s 02:52:55 DEBUG| [stdout] # UDP tunnel GRO fwd perf udp rx: 267 MB/s 217607 calls/s 02:52:55 DEBUG| [stdout] # udp tx:297 MB/s 5039 calls/s 5039 msg/s 02:52:56 DEBUG| [stdout] # udp rx:300 MB/s 244255 calls/s 02:52:56 DEBUG| [stdout] # udp tx:304 MB/s 5164 c
[Kernel-packages] [Bug 2018960] Re: linux-image-5.4.0-149-generic (regression): 0 at net/core/stream.c:212 sk_stream_kill_queues+0xcf/0xe0
** Also affects: linux-meta-kvm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/2018960 Title: linux-image-5.4.0-149-generic (regression): 0 at net/core/stream.c:212 sk_stream_kill_queues+0xcf/0xe0 Status in linux-meta-kvm package in Ubuntu: New Status in linux-signed package in Ubuntu: Confirmed Bug description: After upgrading and rebooting this Ubuntu 20.04 LTS server (Ubuntu Focal), I noticed that it was suddenly getting a bunch of kernel log (dmesg) reports like: WARNING: CPU: 4 PID: 0 at net/core/stream.c:212 sk_stream_kill_queues+0xcf/0xe0 while investigating I determined that it is currently running the focal-proposed kernel (linux-image-5.4.0-149-generic), which it turns out was enabled for this server (clearly it seemed like a good idea at the time). I'm not expecting focal-proposed to be fixed as if it were a release package, but since I couldn't find any reports on Launchpad I figured I should let y'all know this focal-proposed package could do with some additional work before it's actually released :-) There have been at least 80 such reports in the last 5 hours since the server was rebooted, differing only by the CPU core and the process reported, although it seems the last one was a couple of hours ago, so I guess it's traffic dependent/timing dependent. ewen@naosr620:~$ uptime 16:27:32 up 5:19, 1 user, load average: 0.08, 0.14, 0.06 ewen@naosr620:~$ dmesg -t | grep WARNING | sed 's/CPU: [0-9]*/CPU: N/; s/PID: [0-9]*/PID: N/;' | uniq -c 88 WARNING: CPU: N PID: N at net/core/stream.c:212 sk_stream_kill_queues+0xcf/0xe0 ewen@naosr620:~$ Ubuntu Release: ewen@naosr620:~$ lsb_release -rd Description: Ubuntu 20.04.6 LTS Release: 20.04 ewen@naosr620:~$ Kernel/package version affected: ewen@naosr620:~$ uname -a Linux naosr620 5.4.0-149-generic #166-Ubuntu SMP Tue Apr 18 16:51:45 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ewen@naosr620:~$ dpkg -l | grep linux-image | grep 149 ii linux-image-5.4.0-149-generic 5.4.0-149.166 amd64Signed kernel image generic ii linux-image-generic5.4.0.149.147 amd64Generic Linux kernel image ewen@naosr620:~$ apt-cache policy linux-image-5.4.0-149-generic linux-image-5.4.0-149-generic: Installed: 5.4.0-149.166 Candidate: 5.4.0-149.166 Version table: *** 5.4.0-149.166 500 500 https://mirror.fsmg.org.nz/ubuntu focal-proposed/main amd64 Packages 100 /var/lib/dpkg/status ewen@naosr620:~$ apt-cache policy linux-image-generic linux-image-generic: Installed: 5.4.0.149.147 Candidate: 5.4.0.149.147 Version table: *** 5.4.0.149.147 500 500 https://mirror.fsmg.org.nz/ubuntu focal-proposed/main amd64 Packages 100 /var/lib/dpkg/status 5.4.0.148.146 500 500 https://mirror.fsmg.org.nz/ubuntu focal-updates/main amd64 Packages 500 https://mirror.fsmg.org.nz/ubuntu focal-security/main amd64 Packages 5.4.0.26.32 500 500 https://mirror.fsmg.org.nz/ubuntu focal/main amd64 Packages ewen@naosr620:~$ ewen@naosr620:~$ apt-cache show linux-image-5.4.0-149-generic | grep Source: Source: linux-signed ewen@naosr620:~$ Full example dmesg, including stack trace (they all seem to be WARNINGs, and other than filling dmesg / system logs the system "appears to be running okay", so I'm not going to rush another reboot now -- near end of business day): ewen@naosr620:~$ date Tue 09 May 2023 16:34:56 NZST ewen@naosr620:~$ dmesg -T | tail -100 | grep -B 150 "end trace" | grep -A 999 "cut here" [Tue May 9 14:21:18 2023] [ cut here ] [Tue May 9 14:21:18 2023] WARNING: CPU: 10 PID: 0 at net/core/stream.c:212 sk_stream_kill_queues+0xcf/0xe0 [Tue May 9 14:21:18 2023] Modules linked in: mpt3sas raid_class scsi_transport_sas mptctl mptbase vhost_net vhost tap ip6t_REJECT nf_reject_ipv6 ip6table_mangle ip6table_nat ip6table_raw nf_log_ipv6 xt_recent ipt_REJECT nf_reject_ipv4 xt_hashlimit xt_addrtype xt_multiport xt_comment xt_conntrack xt_mark iptable_mangle xt_MASQUERADE iptable_nat xt_CT xt_tcpudp iptable_raw nfnetlink_log xt_NFLOG nf_log_ipv4 nf_log_common xt_LOG nf_nat_tftp nf_nat_snmp_basic nf_conntrack_snmp nf_nat_sip nf_nat_pptp nf_nat_irc ebtable_filter nf_nat_h323 ebtables nf_nat_ftp nf_nat_amanda ts_kmp ip6table_filter nf_conntrack_amanda nf_nat ip6_tables nf_conntrack_sane nf_conntrack_tftp nf_conntrack_sip nf_conntrack_pptp nf_conntrack_netlink nfnetlink nf_conntrack_netbios_ns nf_conntrack_broadcast nf_conntrack_irc nf_conntrack_h323 nf_conntrack_ftp nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 iptable_filter bpfilter dell_rbu nls_iso8859_1 ipmi_ss
[Kernel-packages] [Bug 2019979] Re: nvidia-dkms-* FTBS with linux 6.3
This bug was fixed in the package nvidia-graphics-drivers-450-server - 450.236.01-0ubuntu3 --- nvidia-graphics-drivers-450-server (450.236.01-0ubuntu3) mantic; urgency=medium * debian/dkms_nvidia/patches/buildfix_kernel_6.3.patch: - Add a missing include. -- Paolo Pisati Thu, 01 Jun 2023 11:32:51 + ** Changed in: nvidia-graphics-drivers-450-server (Ubuntu Mantic) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470-server in Ubuntu. https://bugs.launchpad.net/bugs/2019979 Title: nvidia-dkms-* FTBS with linux 6.3 Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-470 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-470-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-510 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-515 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-515-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 source package in Mantic: Fix Released Status in nvidia-graphics-drivers-450-server source package in Mantic: Fix Released Status in nvidia-graphics-drivers-470 source package in Mantic: Fix Released Status in nvidia-graphics-drivers-470-server source package in Mantic: Fix Released Status in nvidia-graphics-drivers-510 source package in Mantic: Fix Released Status in nvidia-graphics-drivers-515 source package in Mantic: Fix Released Status in nvidia-graphics-drivers-515-server source package in Mantic: Fix Released Bug description: [Impact] /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c: In function ‘nvidia_mmap_helper’: /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:474:23: error: assignment of read-only member ‘vm_flags’ 474 | vma->vm_flags |= VM_IO; | ^~ /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:536:23: error: assignment of read-only member ‘vm_flags’ 536 | vma->vm_flags |= (VM_IO | VM_LOCKED | VM_RESERVED); | ^~ /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:537:23: error: assignment of read-only member ‘vm_flags’ 537 | vma->vm_flags |= (VM_DONTEXPAND | VM_DONTDUMP); | ^~ /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:543:23: error: assignment of read-only member ‘vm_flags’ 543 | vma->vm_flags &= ~VM_WRITE; | ^~ /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:544:23: error: assignment of read-only member ‘vm_flags’ 544 | vma->vm_flags &= ~VM_MAYWRITE; | ^~ [Fix] Apply the attached patch. [How to test] Build the dkms package and install it. [Regression potential] This patch doesn't come from NVIDIA itself, so there's a regression potential, though i can't state how severe that could be. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2019979/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2018960] Re: linux-image-5.4.0-149-generic (regression): 0 at net/core/stream.c:212 sk_stream_kill_queues+0xcf/0xe0
I am experiencing this issue on all of my virtual servers running linux- image-kvm-1091 and 1092. I have downgraded to 1090, which does not have the issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/2018960 Title: linux-image-5.4.0-149-generic (regression): 0 at net/core/stream.c:212 sk_stream_kill_queues+0xcf/0xe0 Status in linux-meta-kvm package in Ubuntu: New Status in linux-signed package in Ubuntu: Confirmed Bug description: After upgrading and rebooting this Ubuntu 20.04 LTS server (Ubuntu Focal), I noticed that it was suddenly getting a bunch of kernel log (dmesg) reports like: WARNING: CPU: 4 PID: 0 at net/core/stream.c:212 sk_stream_kill_queues+0xcf/0xe0 while investigating I determined that it is currently running the focal-proposed kernel (linux-image-5.4.0-149-generic), which it turns out was enabled for this server (clearly it seemed like a good idea at the time). I'm not expecting focal-proposed to be fixed as if it were a release package, but since I couldn't find any reports on Launchpad I figured I should let y'all know this focal-proposed package could do with some additional work before it's actually released :-) There have been at least 80 such reports in the last 5 hours since the server was rebooted, differing only by the CPU core and the process reported, although it seems the last one was a couple of hours ago, so I guess it's traffic dependent/timing dependent. ewen@naosr620:~$ uptime 16:27:32 up 5:19, 1 user, load average: 0.08, 0.14, 0.06 ewen@naosr620:~$ dmesg -t | grep WARNING | sed 's/CPU: [0-9]*/CPU: N/; s/PID: [0-9]*/PID: N/;' | uniq -c 88 WARNING: CPU: N PID: N at net/core/stream.c:212 sk_stream_kill_queues+0xcf/0xe0 ewen@naosr620:~$ Ubuntu Release: ewen@naosr620:~$ lsb_release -rd Description: Ubuntu 20.04.6 LTS Release: 20.04 ewen@naosr620:~$ Kernel/package version affected: ewen@naosr620:~$ uname -a Linux naosr620 5.4.0-149-generic #166-Ubuntu SMP Tue Apr 18 16:51:45 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ewen@naosr620:~$ dpkg -l | grep linux-image | grep 149 ii linux-image-5.4.0-149-generic 5.4.0-149.166 amd64Signed kernel image generic ii linux-image-generic5.4.0.149.147 amd64Generic Linux kernel image ewen@naosr620:~$ apt-cache policy linux-image-5.4.0-149-generic linux-image-5.4.0-149-generic: Installed: 5.4.0-149.166 Candidate: 5.4.0-149.166 Version table: *** 5.4.0-149.166 500 500 https://mirror.fsmg.org.nz/ubuntu focal-proposed/main amd64 Packages 100 /var/lib/dpkg/status ewen@naosr620:~$ apt-cache policy linux-image-generic linux-image-generic: Installed: 5.4.0.149.147 Candidate: 5.4.0.149.147 Version table: *** 5.4.0.149.147 500 500 https://mirror.fsmg.org.nz/ubuntu focal-proposed/main amd64 Packages 100 /var/lib/dpkg/status 5.4.0.148.146 500 500 https://mirror.fsmg.org.nz/ubuntu focal-updates/main amd64 Packages 500 https://mirror.fsmg.org.nz/ubuntu focal-security/main amd64 Packages 5.4.0.26.32 500 500 https://mirror.fsmg.org.nz/ubuntu focal/main amd64 Packages ewen@naosr620:~$ ewen@naosr620:~$ apt-cache show linux-image-5.4.0-149-generic | grep Source: Source: linux-signed ewen@naosr620:~$ Full example dmesg, including stack trace (they all seem to be WARNINGs, and other than filling dmesg / system logs the system "appears to be running okay", so I'm not going to rush another reboot now -- near end of business day): ewen@naosr620:~$ date Tue 09 May 2023 16:34:56 NZST ewen@naosr620:~$ dmesg -T | tail -100 | grep -B 150 "end trace" | grep -A 999 "cut here" [Tue May 9 14:21:18 2023] [ cut here ] [Tue May 9 14:21:18 2023] WARNING: CPU: 10 PID: 0 at net/core/stream.c:212 sk_stream_kill_queues+0xcf/0xe0 [Tue May 9 14:21:18 2023] Modules linked in: mpt3sas raid_class scsi_transport_sas mptctl mptbase vhost_net vhost tap ip6t_REJECT nf_reject_ipv6 ip6table_mangle ip6table_nat ip6table_raw nf_log_ipv6 xt_recent ipt_REJECT nf_reject_ipv4 xt_hashlimit xt_addrtype xt_multiport xt_comment xt_conntrack xt_mark iptable_mangle xt_MASQUERADE iptable_nat xt_CT xt_tcpudp iptable_raw nfnetlink_log xt_NFLOG nf_log_ipv4 nf_log_common xt_LOG nf_nat_tftp nf_nat_snmp_basic nf_conntrack_snmp nf_nat_sip nf_nat_pptp nf_nat_irc ebtable_filter nf_nat_h323 ebtables nf_nat_ftp nf_nat_amanda ts_kmp ip6table_filter nf_conntrack_amanda nf_nat ip6_tables nf_conntrack_sane nf_conntrack_tftp nf_conntrack_sip nf_conntrack_pptp nf_conntrack_netlink nfnetlink nf_conntrack_netbios_ns nf_conntrack_broadcast nf_conntrack_irc nf_conntrack_h323 nf_conntrack_ftp nf_conntrack nf_defrag_ipv
[Kernel-packages] [Bug 2018960] Re: linux-image-5.4.0-149-generic (regression): 0 at net/core/stream.c:212 sk_stream_kill_queues+0xcf/0xe0
** Package changed: linux-meta-kvm (Ubuntu) => linux-signed-kvm (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/2018960 Title: linux-image-5.4.0-149-generic (regression): 0 at net/core/stream.c:212 sk_stream_kill_queues+0xcf/0xe0 Status in linux-signed package in Ubuntu: Confirmed Status in linux-signed-kvm package in Ubuntu: New Bug description: After upgrading and rebooting this Ubuntu 20.04 LTS server (Ubuntu Focal), I noticed that it was suddenly getting a bunch of kernel log (dmesg) reports like: WARNING: CPU: 4 PID: 0 at net/core/stream.c:212 sk_stream_kill_queues+0xcf/0xe0 while investigating I determined that it is currently running the focal-proposed kernel (linux-image-5.4.0-149-generic), which it turns out was enabled for this server (clearly it seemed like a good idea at the time). I'm not expecting focal-proposed to be fixed as if it were a release package, but since I couldn't find any reports on Launchpad I figured I should let y'all know this focal-proposed package could do with some additional work before it's actually released :-) There have been at least 80 such reports in the last 5 hours since the server was rebooted, differing only by the CPU core and the process reported, although it seems the last one was a couple of hours ago, so I guess it's traffic dependent/timing dependent. ewen@naosr620:~$ uptime 16:27:32 up 5:19, 1 user, load average: 0.08, 0.14, 0.06 ewen@naosr620:~$ dmesg -t | grep WARNING | sed 's/CPU: [0-9]*/CPU: N/; s/PID: [0-9]*/PID: N/;' | uniq -c 88 WARNING: CPU: N PID: N at net/core/stream.c:212 sk_stream_kill_queues+0xcf/0xe0 ewen@naosr620:~$ Ubuntu Release: ewen@naosr620:~$ lsb_release -rd Description: Ubuntu 20.04.6 LTS Release: 20.04 ewen@naosr620:~$ Kernel/package version affected: ewen@naosr620:~$ uname -a Linux naosr620 5.4.0-149-generic #166-Ubuntu SMP Tue Apr 18 16:51:45 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ewen@naosr620:~$ dpkg -l | grep linux-image | grep 149 ii linux-image-5.4.0-149-generic 5.4.0-149.166 amd64Signed kernel image generic ii linux-image-generic5.4.0.149.147 amd64Generic Linux kernel image ewen@naosr620:~$ apt-cache policy linux-image-5.4.0-149-generic linux-image-5.4.0-149-generic: Installed: 5.4.0-149.166 Candidate: 5.4.0-149.166 Version table: *** 5.4.0-149.166 500 500 https://mirror.fsmg.org.nz/ubuntu focal-proposed/main amd64 Packages 100 /var/lib/dpkg/status ewen@naosr620:~$ apt-cache policy linux-image-generic linux-image-generic: Installed: 5.4.0.149.147 Candidate: 5.4.0.149.147 Version table: *** 5.4.0.149.147 500 500 https://mirror.fsmg.org.nz/ubuntu focal-proposed/main amd64 Packages 100 /var/lib/dpkg/status 5.4.0.148.146 500 500 https://mirror.fsmg.org.nz/ubuntu focal-updates/main amd64 Packages 500 https://mirror.fsmg.org.nz/ubuntu focal-security/main amd64 Packages 5.4.0.26.32 500 500 https://mirror.fsmg.org.nz/ubuntu focal/main amd64 Packages ewen@naosr620:~$ ewen@naosr620:~$ apt-cache show linux-image-5.4.0-149-generic | grep Source: Source: linux-signed ewen@naosr620:~$ Full example dmesg, including stack trace (they all seem to be WARNINGs, and other than filling dmesg / system logs the system "appears to be running okay", so I'm not going to rush another reboot now -- near end of business day): ewen@naosr620:~$ date Tue 09 May 2023 16:34:56 NZST ewen@naosr620:~$ dmesg -T | tail -100 | grep -B 150 "end trace" | grep -A 999 "cut here" [Tue May 9 14:21:18 2023] [ cut here ] [Tue May 9 14:21:18 2023] WARNING: CPU: 10 PID: 0 at net/core/stream.c:212 sk_stream_kill_queues+0xcf/0xe0 [Tue May 9 14:21:18 2023] Modules linked in: mpt3sas raid_class scsi_transport_sas mptctl mptbase vhost_net vhost tap ip6t_REJECT nf_reject_ipv6 ip6table_mangle ip6table_nat ip6table_raw nf_log_ipv6 xt_recent ipt_REJECT nf_reject_ipv4 xt_hashlimit xt_addrtype xt_multiport xt_comment xt_conntrack xt_mark iptable_mangle xt_MASQUERADE iptable_nat xt_CT xt_tcpudp iptable_raw nfnetlink_log xt_NFLOG nf_log_ipv4 nf_log_common xt_LOG nf_nat_tftp nf_nat_snmp_basic nf_conntrack_snmp nf_nat_sip nf_nat_pptp nf_nat_irc ebtable_filter nf_nat_h323 ebtables nf_nat_ftp nf_nat_amanda ts_kmp ip6table_filter nf_conntrack_amanda nf_nat ip6_tables nf_conntrack_sane nf_conntrack_tftp nf_conntrack_sip nf_conntrack_pptp nf_conntrack_netlink nfnetlink nf_conntrack_netbios_ns nf_conntrack_broadcast nf_conntrack_irc nf_conntrack_h323 nf_conntrack_ftp nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 iptable_filter bpfilter dell_rbu nls_iso8859_1 ipmi_ssif input_l
[Kernel-packages] [Bug 2018960] Re: linux-image-5.4.0-149-generic (regression): 0 at net/core/stream.c:212 sk_stream_kill_queues+0xcf/0xe0
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-signed-kvm (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/2018960 Title: linux-image-5.4.0-149-generic (regression): 0 at net/core/stream.c:212 sk_stream_kill_queues+0xcf/0xe0 Status in linux-signed package in Ubuntu: Confirmed Status in linux-signed-kvm package in Ubuntu: New Bug description: After upgrading and rebooting this Ubuntu 20.04 LTS server (Ubuntu Focal), I noticed that it was suddenly getting a bunch of kernel log (dmesg) reports like: WARNING: CPU: 4 PID: 0 at net/core/stream.c:212 sk_stream_kill_queues+0xcf/0xe0 while investigating I determined that it is currently running the focal-proposed kernel (linux-image-5.4.0-149-generic), which it turns out was enabled for this server (clearly it seemed like a good idea at the time). I'm not expecting focal-proposed to be fixed as if it were a release package, but since I couldn't find any reports on Launchpad I figured I should let y'all know this focal-proposed package could do with some additional work before it's actually released :-) There have been at least 80 such reports in the last 5 hours since the server was rebooted, differing only by the CPU core and the process reported, although it seems the last one was a couple of hours ago, so I guess it's traffic dependent/timing dependent. ewen@naosr620:~$ uptime 16:27:32 up 5:19, 1 user, load average: 0.08, 0.14, 0.06 ewen@naosr620:~$ dmesg -t | grep WARNING | sed 's/CPU: [0-9]*/CPU: N/; s/PID: [0-9]*/PID: N/;' | uniq -c 88 WARNING: CPU: N PID: N at net/core/stream.c:212 sk_stream_kill_queues+0xcf/0xe0 ewen@naosr620:~$ Ubuntu Release: ewen@naosr620:~$ lsb_release -rd Description: Ubuntu 20.04.6 LTS Release: 20.04 ewen@naosr620:~$ Kernel/package version affected: ewen@naosr620:~$ uname -a Linux naosr620 5.4.0-149-generic #166-Ubuntu SMP Tue Apr 18 16:51:45 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ewen@naosr620:~$ dpkg -l | grep linux-image | grep 149 ii linux-image-5.4.0-149-generic 5.4.0-149.166 amd64Signed kernel image generic ii linux-image-generic5.4.0.149.147 amd64Generic Linux kernel image ewen@naosr620:~$ apt-cache policy linux-image-5.4.0-149-generic linux-image-5.4.0-149-generic: Installed: 5.4.0-149.166 Candidate: 5.4.0-149.166 Version table: *** 5.4.0-149.166 500 500 https://mirror.fsmg.org.nz/ubuntu focal-proposed/main amd64 Packages 100 /var/lib/dpkg/status ewen@naosr620:~$ apt-cache policy linux-image-generic linux-image-generic: Installed: 5.4.0.149.147 Candidate: 5.4.0.149.147 Version table: *** 5.4.0.149.147 500 500 https://mirror.fsmg.org.nz/ubuntu focal-proposed/main amd64 Packages 100 /var/lib/dpkg/status 5.4.0.148.146 500 500 https://mirror.fsmg.org.nz/ubuntu focal-updates/main amd64 Packages 500 https://mirror.fsmg.org.nz/ubuntu focal-security/main amd64 Packages 5.4.0.26.32 500 500 https://mirror.fsmg.org.nz/ubuntu focal/main amd64 Packages ewen@naosr620:~$ ewen@naosr620:~$ apt-cache show linux-image-5.4.0-149-generic | grep Source: Source: linux-signed ewen@naosr620:~$ Full example dmesg, including stack trace (they all seem to be WARNINGs, and other than filling dmesg / system logs the system "appears to be running okay", so I'm not going to rush another reboot now -- near end of business day): ewen@naosr620:~$ date Tue 09 May 2023 16:34:56 NZST ewen@naosr620:~$ dmesg -T | tail -100 | grep -B 150 "end trace" | grep -A 999 "cut here" [Tue May 9 14:21:18 2023] [ cut here ] [Tue May 9 14:21:18 2023] WARNING: CPU: 10 PID: 0 at net/core/stream.c:212 sk_stream_kill_queues+0xcf/0xe0 [Tue May 9 14:21:18 2023] Modules linked in: mpt3sas raid_class scsi_transport_sas mptctl mptbase vhost_net vhost tap ip6t_REJECT nf_reject_ipv6 ip6table_mangle ip6table_nat ip6table_raw nf_log_ipv6 xt_recent ipt_REJECT nf_reject_ipv4 xt_hashlimit xt_addrtype xt_multiport xt_comment xt_conntrack xt_mark iptable_mangle xt_MASQUERADE iptable_nat xt_CT xt_tcpudp iptable_raw nfnetlink_log xt_NFLOG nf_log_ipv4 nf_log_common xt_LOG nf_nat_tftp nf_nat_snmp_basic nf_conntrack_snmp nf_nat_sip nf_nat_pptp nf_nat_irc ebtable_filter nf_nat_h323 ebtables nf_nat_ftp nf_nat_amanda ts_kmp ip6table_filter nf_conntrack_amanda nf_nat ip6_tables nf_conntrack_sane nf_conntrack_tftp nf_conntrack_sip nf_conntrack_pptp nf_conntrack_netlink nfnetlink nf_conntrack_netbios_ns nf_conntrack_broadcast nf_conntrack_irc nf_conntrack_h323 nf_conntrack_ftp nf_conntrack nf_defrag_ipv6 nf_defrag
[Kernel-packages] [Bug 2018960] Re: linux-image-5.4.0-149-generic (regression): 0 at net/core/stream.c:212 sk_stream_kill_queues+0xcf/0xe0
We have a handful of Ubuntu systems logging this warning since rebooting for kernel updates near the end of May, including: Ubuntu 20.04 - kernels 5.4.0-150-generic, 5.4.0-149-generic Ubuntu 18.04 - kernel 4.15.0-211-generic Warning on 18.04 is just slightly different: WARNING: CPU: 1 PID: 0 at /build/linux-RlFMDZ/linux-4.15.0/net/core/stream.c:212 sk_stream_kill_queues+0xed/0x110 Looks like it could be related to this reported Oracle Linux issue? - https://github.com/oracle/linux-uek/issues/15 ** Bug watch added: github.com/oracle/linux-uek/issues #15 https://github.com/oracle/linux-uek/issues/15 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/2018960 Title: linux-image-5.4.0-149-generic (regression): 0 at net/core/stream.c:212 sk_stream_kill_queues+0xcf/0xe0 Status in linux-signed package in Ubuntu: Confirmed Status in linux-signed-kvm package in Ubuntu: New Bug description: After upgrading and rebooting this Ubuntu 20.04 LTS server (Ubuntu Focal), I noticed that it was suddenly getting a bunch of kernel log (dmesg) reports like: WARNING: CPU: 4 PID: 0 at net/core/stream.c:212 sk_stream_kill_queues+0xcf/0xe0 while investigating I determined that it is currently running the focal-proposed kernel (linux-image-5.4.0-149-generic), which it turns out was enabled for this server (clearly it seemed like a good idea at the time). I'm not expecting focal-proposed to be fixed as if it were a release package, but since I couldn't find any reports on Launchpad I figured I should let y'all know this focal-proposed package could do with some additional work before it's actually released :-) There have been at least 80 such reports in the last 5 hours since the server was rebooted, differing only by the CPU core and the process reported, although it seems the last one was a couple of hours ago, so I guess it's traffic dependent/timing dependent. ewen@naosr620:~$ uptime 16:27:32 up 5:19, 1 user, load average: 0.08, 0.14, 0.06 ewen@naosr620:~$ dmesg -t | grep WARNING | sed 's/CPU: [0-9]*/CPU: N/; s/PID: [0-9]*/PID: N/;' | uniq -c 88 WARNING: CPU: N PID: N at net/core/stream.c:212 sk_stream_kill_queues+0xcf/0xe0 ewen@naosr620:~$ Ubuntu Release: ewen@naosr620:~$ lsb_release -rd Description: Ubuntu 20.04.6 LTS Release: 20.04 ewen@naosr620:~$ Kernel/package version affected: ewen@naosr620:~$ uname -a Linux naosr620 5.4.0-149-generic #166-Ubuntu SMP Tue Apr 18 16:51:45 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ewen@naosr620:~$ dpkg -l | grep linux-image | grep 149 ii linux-image-5.4.0-149-generic 5.4.0-149.166 amd64Signed kernel image generic ii linux-image-generic5.4.0.149.147 amd64Generic Linux kernel image ewen@naosr620:~$ apt-cache policy linux-image-5.4.0-149-generic linux-image-5.4.0-149-generic: Installed: 5.4.0-149.166 Candidate: 5.4.0-149.166 Version table: *** 5.4.0-149.166 500 500 https://mirror.fsmg.org.nz/ubuntu focal-proposed/main amd64 Packages 100 /var/lib/dpkg/status ewen@naosr620:~$ apt-cache policy linux-image-generic linux-image-generic: Installed: 5.4.0.149.147 Candidate: 5.4.0.149.147 Version table: *** 5.4.0.149.147 500 500 https://mirror.fsmg.org.nz/ubuntu focal-proposed/main amd64 Packages 100 /var/lib/dpkg/status 5.4.0.148.146 500 500 https://mirror.fsmg.org.nz/ubuntu focal-updates/main amd64 Packages 500 https://mirror.fsmg.org.nz/ubuntu focal-security/main amd64 Packages 5.4.0.26.32 500 500 https://mirror.fsmg.org.nz/ubuntu focal/main amd64 Packages ewen@naosr620:~$ ewen@naosr620:~$ apt-cache show linux-image-5.4.0-149-generic | grep Source: Source: linux-signed ewen@naosr620:~$ Full example dmesg, including stack trace (they all seem to be WARNINGs, and other than filling dmesg / system logs the system "appears to be running okay", so I'm not going to rush another reboot now -- near end of business day): ewen@naosr620:~$ date Tue 09 May 2023 16:34:56 NZST ewen@naosr620:~$ dmesg -T | tail -100 | grep -B 150 "end trace" | grep -A 999 "cut here" [Tue May 9 14:21:18 2023] [ cut here ] [Tue May 9 14:21:18 2023] WARNING: CPU: 10 PID: 0 at net/core/stream.c:212 sk_stream_kill_queues+0xcf/0xe0 [Tue May 9 14:21:18 2023] Modules linked in: mpt3sas raid_class scsi_transport_sas mptctl mptbase vhost_net vhost tap ip6t_REJECT nf_reject_ipv6 ip6table_mangle ip6table_nat ip6table_raw nf_log_ipv6 xt_recent ipt_REJECT nf_reject_ipv4 xt_hashlimit xt_addrtype xt_multiport xt_comment xt_conntrack xt_mark iptable_mangle xt_MASQUERADE iptable_nat xt_CT xt_tcpudp iptable_raw nfnetlink_log xt_NFLOG nf_log_ipv4
[Kernel-packages] [Bug 2022097] [NEW] Ubuntu 20.04 Stuck at reboot in Virtualbox kernel version 5.4.0-149-generic #166 SMP
Public bug reported:
The problem occurs whilst sequentially rebooting the Ubuntu20.04 freshly
installed inside the VirtualBox.
Host os:
```
No LSB modules are available.
Description:Ubuntu 23.04
Release:23.04
```
Guest os:
```
Description:Ubuntu 20.04.6 LTS
Release:20.04
```
VirtualBox version:
```
VirtualBox Graphical User Interface Version 7.0.6_Ubuntu r155176
7.0.6_Ubuntur155176
```
Steps to reproduce:
reboot the virtual machine several times via the `reboot` command.
Actual behavior:
At a certain reboot, the Ubuntu gets stuck with the last message being
`[0.00] Linux agpgart interface v0.103`. After that the machine gets
stuck. Before that there are significant discrepancies in timestamp.
Expected behavior:
Normal boot.
The issue consistently reproduces on different VirtualBox versions (from
6.1.28r147628 to 7.0) and on
different host kernel versions, also tried 5.16 and 5.19 kernels.
The issue persists after changing various VirtualBox VM options. Disabling
sound control, disabling graphics, disabling PAE/NX, VT/X nested virtualization
and KVM nested paging does not make the issue go away. Enabling/disabling
serial port does not influence the issue. Changing the VirtualBox System/Enable
Hardware Clock in UTC time to unchecked does not help too.
Whilst being stuck the kernel inside the VM ignores sysrq sent via:
```
VM="Ubuntu"
PRESS="26"
RELEASE=$(printf "%X\n" $((0x${PRESS} + 0x80)))
VBoxManage controlvm "$VM" keyboardputscancode 1d 38 54 "${PRESS}" "${RELEASE}"
d4 b8 9d
```
(All the other sysrq interrupts were tried, in order to make sure I have double
checked that the sysrq was enabled, and sent all sysrq's to the normally booted
VM, and it did work).
Kernel rebuilt with debug symbols does not affect the problem. Changing the
verbosity level did not yield any additional results. Enabling/disabling KASLR
and ASLR did not yield any results. Changing the clocksource to kvm-clock , tsc
and acpi_pm did not fix the problem.
SIGNIFICANT NOTE: The problem goes away in case of > 2 CPU and 1GB ram.
Attaching kdb/kgdb does not seem possible since the sysrq is being ignored.
The issue does reproduce for other users:
https://www.reddit.com/r/linuxquestions/comments/ols6f1/ubuntu_server_2004_boot_suddenly_it_freezes_at/
After a bit of printk I have managed to find the source of the problem and take
a stack trace with the VirtualBox debugger. The problem is the
`blk_mq_freeze_queue_wait` being stuck at the loop driver initialization.
```
# RBP Ret SS:RBPRet RIP CS:RIP / Symbol
[line]
00 c9013c80 :c9013c90 81aaf4ba
kallsyms!blk_mq_freeze_queue_wait
retn/64
01 c9013c90 :c9013cc0 81ab0d47
kallsyms!blk_mq_freeze_queue+e
retn/64
02 c9013cc0 :c9013ce0 81ab0f29 kallsyms!wbt_init+1af
retn/64
03 c9013ce0 :c9013d28 81aaef13
kallsyms!wbt_enable_default+b6
retn/64
04 c9013d28 :c9013d90 814f2760
kallsyms!blk_register_queue+358
retn/64
05 c9013d90 :c9013da0 814f27a3
kallsyms!__device_add_disk+450
retn/64
06 c9013da0 :c9013dd8 81aca41c
kallsyms!device_add_disk+13
retn/64
07 c9013dd8 :c9013e10 82d0f072 kallsyms!loop_add+327
retn/64
08 c9013e10 :c9013e88 810037da
kallsyms!loop_init+134
retn/64
09 c9013e88 :c9013f38 82ca240c
kallsyms!do_one_initcall+4a
retn/64
0a c9013f38 :c9013f48 81aedd6e
kallsyms!kernel_init_freeable+1e6
retn/64
0b c9013f48 : 81c00255
kallsyms!kernel_init+e
retn/64
0c :
kallsyms!ret_from_fork+35
```
blk_mq_freeze_queue_wait just calls the `wait_event` for the
`percpu_ref_is_zero(&q->q_usage_counter)`, which is not being zero before the
wait.
Inside the wait_event macro, prepare_to_wait_event function is reached,
finish_wait is not reached. (Checked with the debuggers breakpoints).
Thank you for your efforts in addressing this matter. I appreciate your
attention and assistance in resolving the issue. If there is any
additional information or logs that would be helpful in investigating
the problem, please let me know. I have confidence in your expertise and
appreciate your support. Best regards.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: kernel-bug
** Attachment added: "Ubuntu boot log file"
https://bugs.launchpad.net/bugs/2022097/+attachment/5677206/+files/ubuntu_dmesg.log
--
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/2022097
Title:
Ubuntu 20.04 Stuck at reboot in Virtualbox kernel version
5.4.0-149-gen
[Kernel-packages] [Bug 2022098] [NEW] Severe NFS performance degradation after LP #2003053
Public bug reported: The fix to LP #2003053 has caused massively increased NFS server access in some use-cases, which caused severe performance degradation to the point of being unusable in some cases. ** Affects: linux-gke (Ubuntu) Importance: Critical Assignee: Khaled El Mously (kmously) Status: New ** Affects: linux-gke (Ubuntu Focal) Importance: Critical Assignee: Khaled El Mously (kmously) Status: New ** Affects: linux-gke (Ubuntu Jammy) Importance: Critical Assignee: Khaled El Mously (kmously) Status: New ** Also affects: linux-gke (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux (Ubuntu) ** Also affects: linux-gke (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-gke (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-gke (Ubuntu) Assignee: (unassigned) => Khaled El Mously (kmously) ** Changed in: linux-gke (Ubuntu Focal) Assignee: (unassigned) => Khaled El Mously (kmously) ** Changed in: linux-gke (Ubuntu Jammy) Assignee: (unassigned) => Khaled El Mously (kmously) ** Changed in: linux-gke (Ubuntu) Importance: Undecided => Critical ** Changed in: linux-gke (Ubuntu Focal) Importance: Undecided => Critical ** Changed in: linux-gke (Ubuntu Jammy) Importance: Undecided => Critical -- 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/2022098 Title: Severe NFS performance degradation after LP #2003053 Status in linux-gke package in Ubuntu: New Status in linux-gke source package in Focal: New Status in linux-gke source package in Jammy: New Bug description: The fix to LP #2003053 has caused massively increased NFS server access in some use-cases, which caused severe performance degradation to the point of being unusable in some cases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gke/+bug/2022098/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2022098] Re: Severe NFS performance degradation after LP #2003053
** Description changed: The fix to LP #2003053 has caused massively increased NFS server access in some use-cases, which caused severe performance degradation to the point of being unusable in some cases. + + + The solution to this issue, at least temporarily and at least for linux-gke, is to make the new behaviour optional using the "nfs_fasc=1" module parameter. Without this parameter specified, (or specified as =0) will keep the old behaviour. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gke in Ubuntu. https://bugs.launchpad.net/bugs/2022098 Title: Severe NFS performance degradation after LP #2003053 Status in linux-gke package in Ubuntu: New Status in linux-gke source package in Focal: New Status in linux-gke source package in Jammy: New Bug description: The fix to LP #2003053 has caused massively increased NFS server access in some use-cases, which caused severe performance degradation to the point of being unusable in some cases. The solution to this issue, at least temporarily and at least for linux-gke, is to make the new behaviour optional using the "nfs_fasc=1" module parameter. Without this parameter specified, (or specified as =0) will keep the old behaviour. Regresion potential: - Regression potential is considered low considering the scope of the change and is limited to NFS only. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gke/+bug/2022098/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2022097] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 2022097
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
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/2022097
Title:
Ubuntu 20.04 Stuck at reboot in Virtualbox kernel version
5.4.0-149-generic #166 SMP
Status in linux package in Ubuntu:
Incomplete
Bug description:
The problem occurs whilst sequentially rebooting the Ubuntu20.04 freshly
installed inside the VirtualBox.
Host os:
```
No LSB modules are available.
Description: Ubuntu 23.04
Release: 23.04
```
Guest os:
```
Description: Ubuntu 20.04.6 LTS
Release: 20.04
```
VirtualBox version:
```
VirtualBox Graphical User Interface Version 7.0.6_Ubuntu r155176
7.0.6_Ubuntur155176
```
Steps to reproduce:
reboot the virtual machine several times via the `reboot` command.
Actual behavior:
At a certain reboot, the Ubuntu gets stuck with the last message being
`[0.00] Linux agpgart interface v0.103`. After that the machine gets
stuck. Before that there are significant discrepancies in timestamp.
Expected behavior:
Normal boot.
The issue consistently reproduces on different VirtualBox versions (from
6.1.28r147628 to 7.0) and on
different host kernel versions, also tried 5.16 and 5.19 kernels.
The issue persists after changing various VirtualBox VM options. Disabling
sound control, disabling graphics, disabling PAE/NX, VT/X nested virtualization
and KVM nested paging does not make the issue go away. Enabling/disabling
serial port does not influence the issue. Changing the VirtualBox System/Enable
Hardware Clock in UTC time to unchecked does not help too.
Whilst being stuck the kernel inside the VM ignores sysrq sent via:
```
VM="Ubuntu"
PRESS="26"
RELEASE=$(printf "%X\n" $((0x${PRESS} + 0x80)))
VBoxManage controlvm "$VM" keyboardputscancode 1d 38 54 "${PRESS}"
"${RELEASE}" d4 b8 9d
```
(All the other sysrq interrupts were tried, in order to make sure I have
double checked that the sysrq was enabled, and sent all sysrq's to the normally
booted VM, and it did work).
Kernel rebuilt with debug symbols does not affect the problem. Changing the
verbosity level did not yield any additional results. Enabling/disabling KASLR
and ASLR did not yield any results. Changing the clocksource to kvm-clock , tsc
and acpi_pm did not fix the problem.
SIGNIFICANT NOTE: The problem goes away in case of > 2 CPU and 1GB ram.
Attaching kdb/kgdb does not seem possible since the sysrq is being ignored.
The issue does reproduce for other users:
https://www.reddit.com/r/linuxquestions/comments/ols6f1/ubuntu_server_2004_boot_suddenly_it_freezes_at/
After a bit of printk I have managed to find the source of the problem and
take a stack trace with the VirtualBox debugger. The problem is the
`blk_mq_freeze_queue_wait` being stuck at the loop driver initialization.
```
# RBP Ret SS:RBPRet RIP CS:RIP / Symbol
[line]
00 c9013c80 :c9013c90 81aaf4ba
kallsyms!blk_mq_freeze_queue_wait
retn/64
01 c9013c90 :c9013cc0 81ab0d47
kallsyms!blk_mq_freeze_queue+e
retn/64
02 c9013cc0 :c9013ce0 81ab0f29
kallsyms!wbt_init+1af
retn/64
03 c9013ce0 :c9013d28 81aaef13
kallsyms!wbt_enable_default+b6
retn/64
04 c9013d28 :c9013d90 814f2760
kallsyms!blk_register_queue+358
retn/64
05 c9013d90 :c9013da0 814f27a3
kallsyms!__device_add_disk+450
retn/64
06 c9013da0 :c9013dd8 81aca41c
kallsyms!device_add_disk+13
retn/64
07 c9013dd8 :c9013e10 82d0f072
kallsyms!loop_add+327
retn/64
08 c9013e10 :c9013e88 810037da
kallsyms!loop_init+134
retn/64
09 c9013e88 :c9013f38 82ca240c
kallsyms!do_one_initcall+4a
retn/64
0a c9013f38 :c9013f48 81aedd6e
kallsyms!kernel_init_freeable+1e6
retn/64
0b c9013f48 : 81c00255
kallsyms!kernel_init+e
retn/64
0c :
kallsyms!ret_from_fork+35
```
blk_mq_freeze_queue_wait just calls the `
[Kernel-packages] [Bug 2022098] Re: Severe NFS performance degradation after LP #2003053
** Description changed: The fix to LP #2003053 has caused massively increased NFS server access in some use-cases, which caused severe performance degradation to the point of being unusable in some cases. + The solution to this issue, at least temporarily and at least for linux- + gke, is to make the new behaviour optional using the "nfs_fasc=1" module + parameter. Without this parameter specified, (or specified as =0) will + keep the old behaviour. - The solution to this issue, at least temporarily and at least for linux-gke, is to make the new behaviour optional using the "nfs_fasc=1" module parameter. Without this parameter specified, (or specified as =0) will keep the old behaviour. + + Regresion potential: + - Regression potential is considered low considering the scope of the change and is limited to NFS only. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gke in Ubuntu. https://bugs.launchpad.net/bugs/2022098 Title: Severe NFS performance degradation after LP #2003053 Status in linux-gke package in Ubuntu: New Status in linux-gke source package in Focal: New Status in linux-gke source package in Jammy: New Bug description: The fix to LP #2003053 has caused massively increased NFS server access in some use-cases, which caused severe performance degradation to the point of being unusable in some cases. The solution to this issue, at least temporarily and at least for linux-gke, is to make the new behaviour optional using the "nfs_fasc=1" module parameter. Without this parameter specified, (or specified as =0) will keep the old behaviour. Regresion potential: - Regression potential is considered low considering the scope of the change and is limited to NFS only. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gke/+bug/2022098/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2022097] Re: Ubuntu 20.04 Stuck at reboot in Virtualbox kernel version 5.4.0-149-generic #166 SMP
Adding the VirtualBox log. UPD: Please, notify me If I need to run the
`apport-collect 2022097` at the normal ubuntu state, it seems like I do
not.
** Attachment added: "VBox.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2022097/+attachment/5677207/+files/VBox.log
** 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/2022097
Title:
Ubuntu 20.04 Stuck at reboot in Virtualbox kernel version
5.4.0-149-generic #166 SMP
Status in linux package in Ubuntu:
Confirmed
Bug description:
The problem occurs whilst sequentially rebooting the Ubuntu20.04 freshly
installed inside the VirtualBox.
Host os:
```
No LSB modules are available.
Description: Ubuntu 23.04
Release: 23.04
```
Guest os:
```
Description: Ubuntu 20.04.6 LTS
Release: 20.04
```
VirtualBox version:
```
VirtualBox Graphical User Interface Version 7.0.6_Ubuntu r155176
7.0.6_Ubuntur155176
```
Steps to reproduce:
reboot the virtual machine several times via the `reboot` command.
Actual behavior:
At a certain reboot, the Ubuntu gets stuck with the last message being
`[0.00] Linux agpgart interface v0.103`. After that the machine gets
stuck. Before that there are significant discrepancies in timestamp.
Expected behavior:
Normal boot.
The issue consistently reproduces on different VirtualBox versions (from
6.1.28r147628 to 7.0) and on
different host kernel versions, also tried 5.16 and 5.19 kernels.
The issue persists after changing various VirtualBox VM options. Disabling
sound control, disabling graphics, disabling PAE/NX, VT/X nested virtualization
and KVM nested paging does not make the issue go away. Enabling/disabling
serial port does not influence the issue. Changing the VirtualBox System/Enable
Hardware Clock in UTC time to unchecked does not help too.
Whilst being stuck the kernel inside the VM ignores sysrq sent via:
```
VM="Ubuntu"
PRESS="26"
RELEASE=$(printf "%X\n" $((0x${PRESS} + 0x80)))
VBoxManage controlvm "$VM" keyboardputscancode 1d 38 54 "${PRESS}"
"${RELEASE}" d4 b8 9d
```
(All the other sysrq interrupts were tried, in order to make sure I have
double checked that the sysrq was enabled, and sent all sysrq's to the normally
booted VM, and it did work).
Kernel rebuilt with debug symbols does not affect the problem. Changing the
verbosity level did not yield any additional results. Enabling/disabling KASLR
and ASLR did not yield any results. Changing the clocksource to kvm-clock , tsc
and acpi_pm did not fix the problem.
SIGNIFICANT NOTE: The problem goes away in case of > 2 CPU and 1GB ram.
Attaching kdb/kgdb does not seem possible since the sysrq is being ignored.
The issue does reproduce for other users:
https://www.reddit.com/r/linuxquestions/comments/ols6f1/ubuntu_server_2004_boot_suddenly_it_freezes_at/
After a bit of printk I have managed to find the source of the problem and
take a stack trace with the VirtualBox debugger. The problem is the
`blk_mq_freeze_queue_wait` being stuck at the loop driver initialization.
```
# RBP Ret SS:RBPRet RIP CS:RIP / Symbol
[line]
00 c9013c80 :c9013c90 81aaf4ba
kallsyms!blk_mq_freeze_queue_wait
retn/64
01 c9013c90 :c9013cc0 81ab0d47
kallsyms!blk_mq_freeze_queue+e
retn/64
02 c9013cc0 :c9013ce0 81ab0f29
kallsyms!wbt_init+1af
retn/64
03 c9013ce0 :c9013d28 81aaef13
kallsyms!wbt_enable_default+b6
retn/64
04 c9013d28 :c9013d90 814f2760
kallsyms!blk_register_queue+358
retn/64
05 c9013d90 :c9013da0 814f27a3
kallsyms!__device_add_disk+450
retn/64
06 c9013da0 :c9013dd8 81aca41c
kallsyms!device_add_disk+13
retn/64
07 c9013dd8 :c9013e10 82d0f072
kallsyms!loop_add+327
retn/64
08 c9013e10 :c9013e88 810037da
kallsyms!loop_init+134
retn/64
09 c9013e88 :c9013f38 82ca240c
kallsyms!do_one_initcall+4a
retn/64
0a c9013f38 :c9013f48 81aedd6e
kallsyms!kernel_init_freeable+1e6
retn/64
0b c9013f48 : 81c00255
kallsyms!kernel_init+e
retn/64
0c :
kallsyms!ret_from_fork+35
```
blk_mq_freeze_queue_wait just calls the `wait_event` for the
`percpu_ref_is_zero(&q->q_usage_counter)`, which is not being zero before the
wait.
Inside the wait_event macro, prepare_to_wait_event function is reached,
finish_wait is not reached. (Checked with the debuggers breakpoints).
[Kernel-packages] [Bug 2022001] Re: Kernel 5.19.0-42 onward crashes with VMSVGA + 3D acceleration
Journalctl excerpt from crash tonight, starts around line 1716: kesä 01 21:57:26 neon kaccess[1218]: The X11 connection broke (error 1). Did the X11 server die? ** Attachment added: "Journalctl from the crash" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2022001/+attachment/5677208/+files/journalctl.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/2022001 Title: Kernel 5.19.0-42 onward crashes with VMSVGA + 3D acceleration Status in linux package in Ubuntu: Confirmed Bug description: KDE Neon 5.27 (Ubuntu 22.04 Jammy) Kernel: linux-image-5.19.0-43-generic Steps to reproduce: 0. Install KDE Neon into Virtualbox 1. Install kernel version 5.19.0-42 or -43 (-generic) 2. Boot the system 3. Log in to KDE desktop 4. Try and open a window or right-click on the desktop Expected outcome: A window opens, or a desktop context menu opens Actual outcome: - opening a window: X server crashes. Logging in again and opening a window: system crash - opening a desktop context menu: desktop crashes, after that system freezes Additional info: - dmesg shows a kernel crash trace - kernel 5.19.0-38-generic works OK. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2022001/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2022001] Re: Kernel 5.19.0-42 onward crashes with VMSVGA + 3D acceleration
Dmesg around last night's crash. Might be IRRELEVANT? ** Attachment added: "Dmesg from kernel 5.19.0-42" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2022001/+attachment/5677209/+files/dmesg-vmsvga-crash-%205.19.0-42.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/2022001 Title: Kernel 5.19.0-42 onward crashes with VMSVGA + 3D acceleration Status in linux package in Ubuntu: Confirmed Bug description: KDE Neon 5.27 (Ubuntu 22.04 Jammy) Kernel: linux-image-5.19.0-43-generic Steps to reproduce: 0. Install KDE Neon into Virtualbox 1. Install kernel version 5.19.0-42 or -43 (-generic) 2. Boot the system 3. Log in to KDE desktop 4. Try and open a window or right-click on the desktop Expected outcome: A window opens, or a desktop context menu opens Actual outcome: - opening a window: X server crashes. Logging in again and opening a window: system crash - opening a desktop context menu: desktop crashes, after that system freezes Additional info: - dmesg shows a kernel crash trace - kernel 5.19.0-38-generic works OK. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2022001/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2021474] Re: Linux kernel image 5.19-0-42.43~22.04.1 crashs VM in Virtualbox
Maybe you should tell your bot to read the bug description carefully - how should I supply logfiles if no interaction with the Ubuntu system in the VM is possible anymore ? ** 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/2021474 Title: Linux kernel image 5.19-0-42.43~22.04.1 crashs VM in Virtualbox Status in linux package in Ubuntu: Confirmed Bug description: After upgrading the Linux kernel of an Ubuntu 22.04.2 VM in Virtualbox (version 6.1.44 r156814) to version 5.19-0-42.43 the VM crashs on some graphical operations, e.g. starting Firefox. The VM lgofile shows at this moment: 03:08:01.362162 Display::i_handleDisplayResize: uScreenId=0 pvVRAM= w=1920 h=1200 bpp=0 cbLine=0x0 flags=0x2 origin=0,0 There is no reset of these settings to reasonable values as in an similar operation before: 03:06:14.431345 Display::i_handleDisplayResize: uScreenId=0 pvVRAM= w=1920 h=1200 bpp=0 cbLine=0x0 flags=0x2 origin=0,0 03:06:14.433677 Display::i_handleDisplayResize: uScreenId=0 pvVRAM=7f354df0 w=1920 h=1200 bpp=32 cbLine=0x1E00 flags=0x1 origin=0,0 The VM display is completely black and no input is accepted anymore even Virtualbox control commands like "VBoxManage controlvm VM acpipowerbutton" are ignored. There were no such problems with kernels up to 5.19-0-41. To be exact the system in the VM doesn't really crashs, it is still working in some way (I was able to verify that by the load generated by scheduled virus scan runs in the VM) but no output is shown nor any input is accepted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2021474/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2020531] Re: support python < 3.9 with annotations
This bug is awaiting verification that the linux-raspi/5.15.0-1031.34 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-raspi 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/2020531 Title: support python < 3.9 with annotations Status in linux package in Ubuntu: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Lunar: Fix Committed Status in linux source package in Mantic: Fix Committed Bug description: [Impact] At the moment we can't use the annotations scripts in focal, because we are using the'|=' update operator for merging dicts, that has been introduced with python 3.9. Rewrite the code that is using this operator in a more portable way and apply this change everywhere, so that annotations will work on any backport/derivative kernels. [Test case] Run `fakeroot debian/rules updateconfigs` in focal (using the new annotations model). [Fix] Try to use the '|=' operator in a try/except block, if it fails fallback to a more portable way. [Regression potential] With this change applied we may experience regressions during the updateconfigs phase. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2020531/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2020413] Re: fix typo in config-checks invocation
This bug is awaiting verification that the linux-raspi/5.15.0-1031.34 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-raspi -- 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/2020413 Title: fix typo in config-checks invocation Status in linux package in Ubuntu: Incomplete Status in linux-kvm package in Ubuntu: New Status in linux source package in Jammy: Incomplete Status in linux-kvm source package in Jammy: Confirmed Bug description: [Impact] After migrating to the new annotations-only model in jammy we introduced a typo in debian/rules.d/4-checks.mk, that is triggered if we opt to not migrate to the new model and still use the old configs+annotations. [Test case] With debian./config/config.common.ubuntu present run the following command: $ fakeroot debian/rules clean updateconfigs [Fix] Replace @perl -> perl. [Regression potential] It's a trivial typo fix. Regressions can be introduced only if we are still using the old configs+annotations model. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2020413/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009136] Re: No HDMI audio under 5.19.0-35 & -37 (regression from -32)
Additional information, obviously there is something wrong. SW will be modified without test purpose, UHD + AMD GPU is not verifiable by Canonical. But why the modification of the SW without possibilities to verify the modification ??? Please confirm to ISO9001 ! -- 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/2009136 Title: No HDMI audio under 5.19.0-35 & -37 (regression from -32) Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: Invalid Status in linux source package in Kinetic: Fix Released Bug description: [Impact] For amdgpu/i915, hdmi audio output device has disappeared. [Fix] The latest fix for the non-contiguous memalloc helper changed the allocation method for a non-IOMMU system to use only the fallback allocator. This should have worked, but it caused a problem sometimes when too many non-contiguous pages are allocated that can't be treated by HD-audio controller. As a quirk workaround, go back to the original strategy: use dma_alloc_noncontiguous() at first, and apply the fallback only when it fails, but only for non-IOMMU case [Test Case] 1. boot with kernel applied the patches. 2. check the cards in /proc/asound/cards. Get the hdmi cards. 0 [PCH ]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0xe232 irq 137 1 [HDMI ]: HDA-Intel - HDA ATI HDMI HDA ATI HDMI at 0xe226 irq 134 [Where problems could occur] Low, this is just workaround and may have a better solution in the future. [Misc] All patches has been landed on OEM-6.1 and lunar. ~~ CLARIFICATION: Just to avoid any confusion for those coming to this bug report; the "Jammy: invalid" status above does *not* mean that this bug doesn't affect jammy -- it does, and the kernel team is aware of this. All it reflects is that the fix has to go into the kinetic kernel package which will then flow into the kernel-hwe package implicitly. Currently known affected cards: * HD 7700 (comment 8) * R9 290 (comment 21) * RX 550 (LP: #2012141, and comment 27) * RX 570 (mine) * RX 580 (LP: #2009276, and comment 28) * WX 3200 (comment 29) * RX 6600 (LP: #2009542) * RX 6700 (LP: #2009275) [ Original Description ] After upgrading my Ubuntu jammy (22.04) desktop to the -35 release of the kernel, I found my HDMI audio output device had disappeared. Reverting to the -32 release caused it to appear again (hence why I'm filing the bug against the kernel rather than pulseaudio). I'm attaching the dmesg output from immediately after booting each kernel, but after a bit of trimming and diffing I *think* the following lines are the salient ones: input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input12 input: HDA ATI HDMI HDMI/DP,pcm=7 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input13 input: HDA ATI HDMI HDMI/DP,pcm=8 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input14 input: HDA ATI HDMI HDMI/DP,pcm=9 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input15 input: HDA ATI HDMI HDMI/DP,pcm=10 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input16 input: HDA ATI HDMI HDMI/DP,pcm=11 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input17 snd_hda_intel :2b:00.1: bound :2b:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu]) These lines appear in the dmesg of the -32 kernel, but not in the -35 kernel's log. Meanwhile, the following lines appear in the -35 kernel's log but not in the -32: hdaudio hdaudioC0D0: no AFG or MFG node found snd_hda_intel :2b:00.1: no codecs initialized I'll also attach the output of "pactl list" under each kernel (this shows the HDMI audio sink showing up under -32, but not -35) just in case that helps shed any light on things. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009136/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2018960] Re: linux-image-5.4.0-149-generic (regression): 0 at net/core/stream.c:212 sk_stream_kill_queues+0xcf/0xe0
Based on the comments above, and the Oracle Linux report that Leif M found (thanks!) it seems likely that this is an upstream Linux kernel "stable" backport which (probably in the upstream Linux kernel "stable") was incomplete. Which now a bunch of Linux distros (including Ubuntu and Oracle Linux) have imported. (I really wish the upstream Linux kernel "stable" process had a more thorough process than just randomly cherry picking patches made to later kernels and hoping for the best :-/ ) >From the Oracle Linux report (https://github.com/oracle/linux- uek/issues/15 -- found by Leif M above) it looks like one of the triggering factors is that the Linux kernel is doing NAT. That's also consistent with my experience -- the server with problems hosts several KVM virtual machines, and has a NAT firewall in front of them. But I've not seen similar reports on a laptop or a desktop running the 149 kernel, which don't normally run any virtual machines or do NAT themselves. Some of the patches linked from the Oracle Linux bug report also seem to suggest that in certain control flows one of the values that's being relied on to be a pointer actually isn't used/used as a pointer (presumably hence 0). Which makes me think "improperly back ported" (most likely by the Linux kernel "stable" process) is the most likely cause, and a state check got missed. Ewen -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/2018960 Title: linux-image-5.4.0-149-generic (regression): 0 at net/core/stream.c:212 sk_stream_kill_queues+0xcf/0xe0 Status in linux-signed package in Ubuntu: Confirmed Status in linux-signed-kvm package in Ubuntu: New Bug description: After upgrading and rebooting this Ubuntu 20.04 LTS server (Ubuntu Focal), I noticed that it was suddenly getting a bunch of kernel log (dmesg) reports like: WARNING: CPU: 4 PID: 0 at net/core/stream.c:212 sk_stream_kill_queues+0xcf/0xe0 while investigating I determined that it is currently running the focal-proposed kernel (linux-image-5.4.0-149-generic), which it turns out was enabled for this server (clearly it seemed like a good idea at the time). I'm not expecting focal-proposed to be fixed as if it were a release package, but since I couldn't find any reports on Launchpad I figured I should let y'all know this focal-proposed package could do with some additional work before it's actually released :-) There have been at least 80 such reports in the last 5 hours since the server was rebooted, differing only by the CPU core and the process reported, although it seems the last one was a couple of hours ago, so I guess it's traffic dependent/timing dependent. ewen@naosr620:~$ uptime 16:27:32 up 5:19, 1 user, load average: 0.08, 0.14, 0.06 ewen@naosr620:~$ dmesg -t | grep WARNING | sed 's/CPU: [0-9]*/CPU: N/; s/PID: [0-9]*/PID: N/;' | uniq -c 88 WARNING: CPU: N PID: N at net/core/stream.c:212 sk_stream_kill_queues+0xcf/0xe0 ewen@naosr620:~$ Ubuntu Release: ewen@naosr620:~$ lsb_release -rd Description: Ubuntu 20.04.6 LTS Release: 20.04 ewen@naosr620:~$ Kernel/package version affected: ewen@naosr620:~$ uname -a Linux naosr620 5.4.0-149-generic #166-Ubuntu SMP Tue Apr 18 16:51:45 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ewen@naosr620:~$ dpkg -l | grep linux-image | grep 149 ii linux-image-5.4.0-149-generic 5.4.0-149.166 amd64Signed kernel image generic ii linux-image-generic5.4.0.149.147 amd64Generic Linux kernel image ewen@naosr620:~$ apt-cache policy linux-image-5.4.0-149-generic linux-image-5.4.0-149-generic: Installed: 5.4.0-149.166 Candidate: 5.4.0-149.166 Version table: *** 5.4.0-149.166 500 500 https://mirror.fsmg.org.nz/ubuntu focal-proposed/main amd64 Packages 100 /var/lib/dpkg/status ewen@naosr620:~$ apt-cache policy linux-image-generic linux-image-generic: Installed: 5.4.0.149.147 Candidate: 5.4.0.149.147 Version table: *** 5.4.0.149.147 500 500 https://mirror.fsmg.org.nz/ubuntu focal-proposed/main amd64 Packages 100 /var/lib/dpkg/status 5.4.0.148.146 500 500 https://mirror.fsmg.org.nz/ubuntu focal-updates/main amd64 Packages 500 https://mirror.fsmg.org.nz/ubuntu focal-security/main amd64 Packages 5.4.0.26.32 500 500 https://mirror.fsmg.org.nz/ubuntu focal/main amd64 Packages ewen@naosr620:~$ ewen@naosr620:~$ apt-cache show linux-image-5.4.0-149-generic | grep Source: Source: linux-signed ewen@naosr620:~$ Full example dmesg, including stack trace (they all seem to be WARNINGs, and other than filling dmesg / system logs the system "appears to be running okay", so I'm not going to rush another reboot now -- near end o
[Kernel-packages] [Bug 2018960] Re: linux-image-5.4.0-149-generic (regression): 0 at net/core/stream.c:212 sk_stream_kill_queues+0xcf/0xe0
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-signed-kvm (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/2018960 Title: linux-image-5.4.0-149-generic (regression): 0 at net/core/stream.c:212 sk_stream_kill_queues+0xcf/0xe0 Status in linux-signed package in Ubuntu: Confirmed Status in linux-signed-kvm package in Ubuntu: Confirmed Bug description: After upgrading and rebooting this Ubuntu 20.04 LTS server (Ubuntu Focal), I noticed that it was suddenly getting a bunch of kernel log (dmesg) reports like: WARNING: CPU: 4 PID: 0 at net/core/stream.c:212 sk_stream_kill_queues+0xcf/0xe0 while investigating I determined that it is currently running the focal-proposed kernel (linux-image-5.4.0-149-generic), which it turns out was enabled for this server (clearly it seemed like a good idea at the time). I'm not expecting focal-proposed to be fixed as if it were a release package, but since I couldn't find any reports on Launchpad I figured I should let y'all know this focal-proposed package could do with some additional work before it's actually released :-) There have been at least 80 such reports in the last 5 hours since the server was rebooted, differing only by the CPU core and the process reported, although it seems the last one was a couple of hours ago, so I guess it's traffic dependent/timing dependent. ewen@naosr620:~$ uptime 16:27:32 up 5:19, 1 user, load average: 0.08, 0.14, 0.06 ewen@naosr620:~$ dmesg -t | grep WARNING | sed 's/CPU: [0-9]*/CPU: N/; s/PID: [0-9]*/PID: N/;' | uniq -c 88 WARNING: CPU: N PID: N at net/core/stream.c:212 sk_stream_kill_queues+0xcf/0xe0 ewen@naosr620:~$ Ubuntu Release: ewen@naosr620:~$ lsb_release -rd Description: Ubuntu 20.04.6 LTS Release: 20.04 ewen@naosr620:~$ Kernel/package version affected: ewen@naosr620:~$ uname -a Linux naosr620 5.4.0-149-generic #166-Ubuntu SMP Tue Apr 18 16:51:45 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ewen@naosr620:~$ dpkg -l | grep linux-image | grep 149 ii linux-image-5.4.0-149-generic 5.4.0-149.166 amd64Signed kernel image generic ii linux-image-generic5.4.0.149.147 amd64Generic Linux kernel image ewen@naosr620:~$ apt-cache policy linux-image-5.4.0-149-generic linux-image-5.4.0-149-generic: Installed: 5.4.0-149.166 Candidate: 5.4.0-149.166 Version table: *** 5.4.0-149.166 500 500 https://mirror.fsmg.org.nz/ubuntu focal-proposed/main amd64 Packages 100 /var/lib/dpkg/status ewen@naosr620:~$ apt-cache policy linux-image-generic linux-image-generic: Installed: 5.4.0.149.147 Candidate: 5.4.0.149.147 Version table: *** 5.4.0.149.147 500 500 https://mirror.fsmg.org.nz/ubuntu focal-proposed/main amd64 Packages 100 /var/lib/dpkg/status 5.4.0.148.146 500 500 https://mirror.fsmg.org.nz/ubuntu focal-updates/main amd64 Packages 500 https://mirror.fsmg.org.nz/ubuntu focal-security/main amd64 Packages 5.4.0.26.32 500 500 https://mirror.fsmg.org.nz/ubuntu focal/main amd64 Packages ewen@naosr620:~$ ewen@naosr620:~$ apt-cache show linux-image-5.4.0-149-generic | grep Source: Source: linux-signed ewen@naosr620:~$ Full example dmesg, including stack trace (they all seem to be WARNINGs, and other than filling dmesg / system logs the system "appears to be running okay", so I'm not going to rush another reboot now -- near end of business day): ewen@naosr620:~$ date Tue 09 May 2023 16:34:56 NZST ewen@naosr620:~$ dmesg -T | tail -100 | grep -B 150 "end trace" | grep -A 999 "cut here" [Tue May 9 14:21:18 2023] [ cut here ] [Tue May 9 14:21:18 2023] WARNING: CPU: 10 PID: 0 at net/core/stream.c:212 sk_stream_kill_queues+0xcf/0xe0 [Tue May 9 14:21:18 2023] Modules linked in: mpt3sas raid_class scsi_transport_sas mptctl mptbase vhost_net vhost tap ip6t_REJECT nf_reject_ipv6 ip6table_mangle ip6table_nat ip6table_raw nf_log_ipv6 xt_recent ipt_REJECT nf_reject_ipv4 xt_hashlimit xt_addrtype xt_multiport xt_comment xt_conntrack xt_mark iptable_mangle xt_MASQUERADE iptable_nat xt_CT xt_tcpudp iptable_raw nfnetlink_log xt_NFLOG nf_log_ipv4 nf_log_common xt_LOG nf_nat_tftp nf_nat_snmp_basic nf_conntrack_snmp nf_nat_sip nf_nat_pptp nf_nat_irc ebtable_filter nf_nat_h323 ebtables nf_nat_ftp nf_nat_amanda ts_kmp ip6table_filter nf_conntrack_amanda nf_nat ip6_tables nf_conntrack_sane nf_conntrack_tftp nf_conntrack_sip nf_conntrack_pptp nf_conntrack_netlink nfnetlink nf_conntrack_netbios_ns nf_conntrack_broadcast nf_conntrack_irc nf_conntrack_h323 nf_conntrack_ftp nf_conntrack nf_defrag_ipv6 nf_
[Kernel-packages] [Bug 2018960] Re: linux-image-5.4.0-149-generic (regression): 0 at net/core/stream.c:212 sk_stream_kill_queues+0xcf/0xe0
FWIW none of my affected systems are using NAT/conntrack, although they do have nftables rules loaded. Loaded modules: kvm_intel nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_counter nf_tables_set nf_tables ip_tables x_tables pata_acpi -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/2018960 Title: linux-image-5.4.0-149-generic (regression): 0 at net/core/stream.c:212 sk_stream_kill_queues+0xcf/0xe0 Status in linux-signed package in Ubuntu: Confirmed Status in linux-signed-kvm package in Ubuntu: Confirmed Bug description: After upgrading and rebooting this Ubuntu 20.04 LTS server (Ubuntu Focal), I noticed that it was suddenly getting a bunch of kernel log (dmesg) reports like: WARNING: CPU: 4 PID: 0 at net/core/stream.c:212 sk_stream_kill_queues+0xcf/0xe0 while investigating I determined that it is currently running the focal-proposed kernel (linux-image-5.4.0-149-generic), which it turns out was enabled for this server (clearly it seemed like a good idea at the time). I'm not expecting focal-proposed to be fixed as if it were a release package, but since I couldn't find any reports on Launchpad I figured I should let y'all know this focal-proposed package could do with some additional work before it's actually released :-) There have been at least 80 such reports in the last 5 hours since the server was rebooted, differing only by the CPU core and the process reported, although it seems the last one was a couple of hours ago, so I guess it's traffic dependent/timing dependent. ewen@naosr620:~$ uptime 16:27:32 up 5:19, 1 user, load average: 0.08, 0.14, 0.06 ewen@naosr620:~$ dmesg -t | grep WARNING | sed 's/CPU: [0-9]*/CPU: N/; s/PID: [0-9]*/PID: N/;' | uniq -c 88 WARNING: CPU: N PID: N at net/core/stream.c:212 sk_stream_kill_queues+0xcf/0xe0 ewen@naosr620:~$ Ubuntu Release: ewen@naosr620:~$ lsb_release -rd Description: Ubuntu 20.04.6 LTS Release: 20.04 ewen@naosr620:~$ Kernel/package version affected: ewen@naosr620:~$ uname -a Linux naosr620 5.4.0-149-generic #166-Ubuntu SMP Tue Apr 18 16:51:45 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ewen@naosr620:~$ dpkg -l | grep linux-image | grep 149 ii linux-image-5.4.0-149-generic 5.4.0-149.166 amd64Signed kernel image generic ii linux-image-generic5.4.0.149.147 amd64Generic Linux kernel image ewen@naosr620:~$ apt-cache policy linux-image-5.4.0-149-generic linux-image-5.4.0-149-generic: Installed: 5.4.0-149.166 Candidate: 5.4.0-149.166 Version table: *** 5.4.0-149.166 500 500 https://mirror.fsmg.org.nz/ubuntu focal-proposed/main amd64 Packages 100 /var/lib/dpkg/status ewen@naosr620:~$ apt-cache policy linux-image-generic linux-image-generic: Installed: 5.4.0.149.147 Candidate: 5.4.0.149.147 Version table: *** 5.4.0.149.147 500 500 https://mirror.fsmg.org.nz/ubuntu focal-proposed/main amd64 Packages 100 /var/lib/dpkg/status 5.4.0.148.146 500 500 https://mirror.fsmg.org.nz/ubuntu focal-updates/main amd64 Packages 500 https://mirror.fsmg.org.nz/ubuntu focal-security/main amd64 Packages 5.4.0.26.32 500 500 https://mirror.fsmg.org.nz/ubuntu focal/main amd64 Packages ewen@naosr620:~$ ewen@naosr620:~$ apt-cache show linux-image-5.4.0-149-generic | grep Source: Source: linux-signed ewen@naosr620:~$ Full example dmesg, including stack trace (they all seem to be WARNINGs, and other than filling dmesg / system logs the system "appears to be running okay", so I'm not going to rush another reboot now -- near end of business day): ewen@naosr620:~$ date Tue 09 May 2023 16:34:56 NZST ewen@naosr620:~$ dmesg -T | tail -100 | grep -B 150 "end trace" | grep -A 999 "cut here" [Tue May 9 14:21:18 2023] [ cut here ] [Tue May 9 14:21:18 2023] WARNING: CPU: 10 PID: 0 at net/core/stream.c:212 sk_stream_kill_queues+0xcf/0xe0 [Tue May 9 14:21:18 2023] Modules linked in: mpt3sas raid_class scsi_transport_sas mptctl mptbase vhost_net vhost tap ip6t_REJECT nf_reject_ipv6 ip6table_mangle ip6table_nat ip6table_raw nf_log_ipv6 xt_recent ipt_REJECT nf_reject_ipv4 xt_hashlimit xt_addrtype xt_multiport xt_comment xt_conntrack xt_mark iptable_mangle xt_MASQUERADE iptable_nat xt_CT xt_tcpudp iptable_raw nfnetlink_log xt_NFLOG nf_log_ipv4 nf_log_common xt_LOG nf_nat_tftp nf_nat_snmp_basic nf_conntrack_snmp nf_nat_sip nf_nat_pptp nf_nat_irc ebtable_filter nf_nat_h323 ebtables nf_nat_ftp nf_nat_amanda ts_kmp ip6table_filter nf_conntrack_amanda nf_nat ip6_tables nf_conntrack_sane nf_conntrack_tftp nf_conntrack_sip nf_conntrack_pptp nf_conntrack_netlink nfnetlink nf_conntrack_netbios_ns
[Kernel-packages] [Bug 2018960] Re: linux-image-5.4.0-149-generic (regression): 0 at net/core/stream.c:212 sk_stream_kill_queues+0xcf/0xe0
I can add to this saying that the machine I'm seeing this on is behind a NAT (being done by another firewall device), but it does not do any NAT itself. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/2018960 Title: linux-image-5.4.0-149-generic (regression): 0 at net/core/stream.c:212 sk_stream_kill_queues+0xcf/0xe0 Status in linux-signed package in Ubuntu: Confirmed Status in linux-signed-kvm package in Ubuntu: Confirmed Bug description: After upgrading and rebooting this Ubuntu 20.04 LTS server (Ubuntu Focal), I noticed that it was suddenly getting a bunch of kernel log (dmesg) reports like: WARNING: CPU: 4 PID: 0 at net/core/stream.c:212 sk_stream_kill_queues+0xcf/0xe0 while investigating I determined that it is currently running the focal-proposed kernel (linux-image-5.4.0-149-generic), which it turns out was enabled for this server (clearly it seemed like a good idea at the time). I'm not expecting focal-proposed to be fixed as if it were a release package, but since I couldn't find any reports on Launchpad I figured I should let y'all know this focal-proposed package could do with some additional work before it's actually released :-) There have been at least 80 such reports in the last 5 hours since the server was rebooted, differing only by the CPU core and the process reported, although it seems the last one was a couple of hours ago, so I guess it's traffic dependent/timing dependent. ewen@naosr620:~$ uptime 16:27:32 up 5:19, 1 user, load average: 0.08, 0.14, 0.06 ewen@naosr620:~$ dmesg -t | grep WARNING | sed 's/CPU: [0-9]*/CPU: N/; s/PID: [0-9]*/PID: N/;' | uniq -c 88 WARNING: CPU: N PID: N at net/core/stream.c:212 sk_stream_kill_queues+0xcf/0xe0 ewen@naosr620:~$ Ubuntu Release: ewen@naosr620:~$ lsb_release -rd Description: Ubuntu 20.04.6 LTS Release: 20.04 ewen@naosr620:~$ Kernel/package version affected: ewen@naosr620:~$ uname -a Linux naosr620 5.4.0-149-generic #166-Ubuntu SMP Tue Apr 18 16:51:45 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ewen@naosr620:~$ dpkg -l | grep linux-image | grep 149 ii linux-image-5.4.0-149-generic 5.4.0-149.166 amd64Signed kernel image generic ii linux-image-generic5.4.0.149.147 amd64Generic Linux kernel image ewen@naosr620:~$ apt-cache policy linux-image-5.4.0-149-generic linux-image-5.4.0-149-generic: Installed: 5.4.0-149.166 Candidate: 5.4.0-149.166 Version table: *** 5.4.0-149.166 500 500 https://mirror.fsmg.org.nz/ubuntu focal-proposed/main amd64 Packages 100 /var/lib/dpkg/status ewen@naosr620:~$ apt-cache policy linux-image-generic linux-image-generic: Installed: 5.4.0.149.147 Candidate: 5.4.0.149.147 Version table: *** 5.4.0.149.147 500 500 https://mirror.fsmg.org.nz/ubuntu focal-proposed/main amd64 Packages 100 /var/lib/dpkg/status 5.4.0.148.146 500 500 https://mirror.fsmg.org.nz/ubuntu focal-updates/main amd64 Packages 500 https://mirror.fsmg.org.nz/ubuntu focal-security/main amd64 Packages 5.4.0.26.32 500 500 https://mirror.fsmg.org.nz/ubuntu focal/main amd64 Packages ewen@naosr620:~$ ewen@naosr620:~$ apt-cache show linux-image-5.4.0-149-generic | grep Source: Source: linux-signed ewen@naosr620:~$ Full example dmesg, including stack trace (they all seem to be WARNINGs, and other than filling dmesg / system logs the system "appears to be running okay", so I'm not going to rush another reboot now -- near end of business day): ewen@naosr620:~$ date Tue 09 May 2023 16:34:56 NZST ewen@naosr620:~$ dmesg -T | tail -100 | grep -B 150 "end trace" | grep -A 999 "cut here" [Tue May 9 14:21:18 2023] [ cut here ] [Tue May 9 14:21:18 2023] WARNING: CPU: 10 PID: 0 at net/core/stream.c:212 sk_stream_kill_queues+0xcf/0xe0 [Tue May 9 14:21:18 2023] Modules linked in: mpt3sas raid_class scsi_transport_sas mptctl mptbase vhost_net vhost tap ip6t_REJECT nf_reject_ipv6 ip6table_mangle ip6table_nat ip6table_raw nf_log_ipv6 xt_recent ipt_REJECT nf_reject_ipv4 xt_hashlimit xt_addrtype xt_multiport xt_comment xt_conntrack xt_mark iptable_mangle xt_MASQUERADE iptable_nat xt_CT xt_tcpudp iptable_raw nfnetlink_log xt_NFLOG nf_log_ipv4 nf_log_common xt_LOG nf_nat_tftp nf_nat_snmp_basic nf_conntrack_snmp nf_nat_sip nf_nat_pptp nf_nat_irc ebtable_filter nf_nat_h323 ebtables nf_nat_ftp nf_nat_amanda ts_kmp ip6table_filter nf_conntrack_amanda nf_nat ip6_tables nf_conntrack_sane nf_conntrack_tftp nf_conntrack_sip nf_conntrack_pptp nf_conntrack_netlink nfnetlink nf_conntrack_netbios_ns nf_conntrack_broadcast nf_conntrack_irc nf_conntrack_h323 nf_conntrack_ftp nf_conntrack nf_defrag
[Kernel-packages] [Bug 2018960] Re: linux-image-5.4.0-149-generic (regression): 0 at net/core/stream.c:212 sk_stream_kill_queues+0xcf/0xe0
I also just updated to 5.4.0-150-generic and I'm still seeing this issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/2018960 Title: linux-image-5.4.0-149-generic (regression): 0 at net/core/stream.c:212 sk_stream_kill_queues+0xcf/0xe0 Status in linux-signed package in Ubuntu: Confirmed Status in linux-signed-kvm package in Ubuntu: Confirmed Bug description: After upgrading and rebooting this Ubuntu 20.04 LTS server (Ubuntu Focal), I noticed that it was suddenly getting a bunch of kernel log (dmesg) reports like: WARNING: CPU: 4 PID: 0 at net/core/stream.c:212 sk_stream_kill_queues+0xcf/0xe0 while investigating I determined that it is currently running the focal-proposed kernel (linux-image-5.4.0-149-generic), which it turns out was enabled for this server (clearly it seemed like a good idea at the time). I'm not expecting focal-proposed to be fixed as if it were a release package, but since I couldn't find any reports on Launchpad I figured I should let y'all know this focal-proposed package could do with some additional work before it's actually released :-) There have been at least 80 such reports in the last 5 hours since the server was rebooted, differing only by the CPU core and the process reported, although it seems the last one was a couple of hours ago, so I guess it's traffic dependent/timing dependent. ewen@naosr620:~$ uptime 16:27:32 up 5:19, 1 user, load average: 0.08, 0.14, 0.06 ewen@naosr620:~$ dmesg -t | grep WARNING | sed 's/CPU: [0-9]*/CPU: N/; s/PID: [0-9]*/PID: N/;' | uniq -c 88 WARNING: CPU: N PID: N at net/core/stream.c:212 sk_stream_kill_queues+0xcf/0xe0 ewen@naosr620:~$ Ubuntu Release: ewen@naosr620:~$ lsb_release -rd Description: Ubuntu 20.04.6 LTS Release: 20.04 ewen@naosr620:~$ Kernel/package version affected: ewen@naosr620:~$ uname -a Linux naosr620 5.4.0-149-generic #166-Ubuntu SMP Tue Apr 18 16:51:45 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ewen@naosr620:~$ dpkg -l | grep linux-image | grep 149 ii linux-image-5.4.0-149-generic 5.4.0-149.166 amd64Signed kernel image generic ii linux-image-generic5.4.0.149.147 amd64Generic Linux kernel image ewen@naosr620:~$ apt-cache policy linux-image-5.4.0-149-generic linux-image-5.4.0-149-generic: Installed: 5.4.0-149.166 Candidate: 5.4.0-149.166 Version table: *** 5.4.0-149.166 500 500 https://mirror.fsmg.org.nz/ubuntu focal-proposed/main amd64 Packages 100 /var/lib/dpkg/status ewen@naosr620:~$ apt-cache policy linux-image-generic linux-image-generic: Installed: 5.4.0.149.147 Candidate: 5.4.0.149.147 Version table: *** 5.4.0.149.147 500 500 https://mirror.fsmg.org.nz/ubuntu focal-proposed/main amd64 Packages 100 /var/lib/dpkg/status 5.4.0.148.146 500 500 https://mirror.fsmg.org.nz/ubuntu focal-updates/main amd64 Packages 500 https://mirror.fsmg.org.nz/ubuntu focal-security/main amd64 Packages 5.4.0.26.32 500 500 https://mirror.fsmg.org.nz/ubuntu focal/main amd64 Packages ewen@naosr620:~$ ewen@naosr620:~$ apt-cache show linux-image-5.4.0-149-generic | grep Source: Source: linux-signed ewen@naosr620:~$ Full example dmesg, including stack trace (they all seem to be WARNINGs, and other than filling dmesg / system logs the system "appears to be running okay", so I'm not going to rush another reboot now -- near end of business day): ewen@naosr620:~$ date Tue 09 May 2023 16:34:56 NZST ewen@naosr620:~$ dmesg -T | tail -100 | grep -B 150 "end trace" | grep -A 999 "cut here" [Tue May 9 14:21:18 2023] [ cut here ] [Tue May 9 14:21:18 2023] WARNING: CPU: 10 PID: 0 at net/core/stream.c:212 sk_stream_kill_queues+0xcf/0xe0 [Tue May 9 14:21:18 2023] Modules linked in: mpt3sas raid_class scsi_transport_sas mptctl mptbase vhost_net vhost tap ip6t_REJECT nf_reject_ipv6 ip6table_mangle ip6table_nat ip6table_raw nf_log_ipv6 xt_recent ipt_REJECT nf_reject_ipv4 xt_hashlimit xt_addrtype xt_multiport xt_comment xt_conntrack xt_mark iptable_mangle xt_MASQUERADE iptable_nat xt_CT xt_tcpudp iptable_raw nfnetlink_log xt_NFLOG nf_log_ipv4 nf_log_common xt_LOG nf_nat_tftp nf_nat_snmp_basic nf_conntrack_snmp nf_nat_sip nf_nat_pptp nf_nat_irc ebtable_filter nf_nat_h323 ebtables nf_nat_ftp nf_nat_amanda ts_kmp ip6table_filter nf_conntrack_amanda nf_nat ip6_tables nf_conntrack_sane nf_conntrack_tftp nf_conntrack_sip nf_conntrack_pptp nf_conntrack_netlink nfnetlink nf_conntrack_netbios_ns nf_conntrack_broadcast nf_conntrack_irc nf_conntrack_h323 nf_conntrack_ftp nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 iptable_filter bpfilter dell_rbu nls_iso8859_1 ipmi_ssif
[Kernel-packages] [Bug 2020531] Re: support python < 3.9 with annotations
This bug is awaiting verification that the linux-aws/5.15.0-1038.43 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 -- 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/2020531 Title: support python < 3.9 with annotations Status in linux package in Ubuntu: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Lunar: Fix Committed Status in linux source package in Mantic: Fix Committed Bug description: [Impact] At the moment we can't use the annotations scripts in focal, because we are using the'|=' update operator for merging dicts, that has been introduced with python 3.9. Rewrite the code that is using this operator in a more portable way and apply this change everywhere, so that annotations will work on any backport/derivative kernels. [Test case] Run `fakeroot debian/rules updateconfigs` in focal (using the new annotations model). [Fix] Try to use the '|=' operator in a try/except block, if it fails fallback to a more portable way. [Regression potential] With this change applied we may experience regressions during the updateconfigs phase. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2020531/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2020413] Re: fix typo in config-checks invocation
This bug is awaiting verification that the linux-aws/5.15.0-1038.43 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 -- 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/2020413 Title: fix typo in config-checks invocation Status in linux package in Ubuntu: Incomplete Status in linux-kvm package in Ubuntu: New Status in linux source package in Jammy: Incomplete Status in linux-kvm source package in Jammy: Confirmed Bug description: [Impact] After migrating to the new annotations-only model in jammy we introduced a typo in debian/rules.d/4-checks.mk, that is triggered if we opt to not migrate to the new model and still use the old configs+annotations. [Test case] With debian./config/config.common.ubuntu present run the following command: $ fakeroot debian/rules clean updateconfigs [Fix] Replace @perl -> perl. [Regression potential] It's a trivial typo fix. Regressions can be introduced only if we are still using the old configs+annotations model. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2020413/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2015855] Re: Add split lock detection for EMR
This bug is awaiting verification that the linux-aws/5.15.0-1038.43 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 -- 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/2015855 Title: Add split lock detection for EMR Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Bug description: SRU Justification [Impact] Intel has introduced support for their new Emerald Rapids CPU. It was backported to Jammy in #lp2015372 The remaining feature needed to fully support EMR is the split lock detection mechanism. So far, bit 5 in IA32_CORE_CAPABILITIES says whether split lock detection is supported or not, but this is not architectural, meaning that this should be trusted only if it’s confirmed that a specific CPU model implements it. This lead to a mapping between a CPU model and whether it supports split lock detection by default (no need to check IA32_CORE_CAPABILITIES) or they may support the split lock detection → IA32_CORE_CAPABILITIES bit 5 has to be checked. With more and more CPU models, this becomes hard to maintain. Moreover, the December 2022 edition of the Intel Instruction Set Extensions manual defined that the split lock disable bit in the IA32_CORE_CAPABILITIES MSR is (and retrospectively always has been) architectural. Documentation also mentions “All processors that enumerate support for MSR_IA32_CORE_CAPS and set MSR_IA32_CORE_CAPS_SPLIT_LOCK_DETECT support split lock detection.” Thus, commit d7ce15e1d4162ab5e56dead10d4ae69a6b5c8ee8: “ x86/split_lock: Enumerate architectural split lock disable bit” from linux-next removes the need of adding a new CPU model in that mapping. This is needed to support split lock detection for the new EMR CPU and future models that don’t suffer architectural changes. [Testing] Kernel was built on cbd and boot tested on a VM. Intel was asked to install and test the new kernel from this ppa https://launchpad.net/~roxanan/+archive/ubuntu/lp2015855 [Regression potential] Very low, it is a small refactor and in essence, it does the exact same thing for existing cpu models: 1. For Icelake which does not have IA32_CORE_CAPABILITIES it always assumes the mechanism is supported. 2. For the rest, it automatically checks bit 5 of IA32_CORE_CAPABILITIES without the extra step of checking the map if the CPU supports this (which was always true) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015855/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2015956] Re: selftest: fib_tests: Always cleanup before exit
This bug is awaiting verification that the linux-aws/5.15.0-1038.43 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 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/2015956 Title: selftest: fib_tests: Always cleanup before exit Status in ubuntu-kernel-tests: 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-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Focal: Fix Released Status in linux-oem-5.17 source package in Focal: Invalid Status in linux-oem-6.0 source package in Focal: Invalid Status in linux-oem-6.1 source package in Focal: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.17 source package in Jammy: Fix Committed Status in linux-oem-6.0 source package in Jammy: Fix Committed Status in linux-oem-6.1 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-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: Fix Released Status in linux-oem-5.17 source package in Lunar: Invalid Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] Copied from the commit message: Usage of `set -e` before executing a command causes immediate exit on failure, without cleanup up the resources allocated at setup. This can affect the next tests that use the same resources, leading to a chain of failures. A simple fix is to always call cleanup function when the script exists. This approach is already used by other existing tests. [Fix] * b60417a9f2 selftest: fib_tests: Always cleanup before exit This patch can be cherry-picked into affected kernels. [Test] Run the patched fib_tests.sh on KVM kernels, which is expected to fail due to bug 2007458. Check with `ip netns`, the ns1 added during setup() should be removed. [Where problems could occur] Test robustness improvement, this should not break things. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2015956/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2015498] Re: Debian autoreconstruct Fix restoration of execute permissions
This bug is awaiting verification that the linux-aws/5.15.0-1038.43 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 -- 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/2015498 Title: Debian autoreconstruct Fix restoration of execute permissions Status in linux package in Ubuntu: Confirmed 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 Status in linux source package in Lunar: Confirmed Bug description: SRU justification [Impact] Debian source package diffs cannot represent that a file should be executable. gen-auto-reconstruct detects when a commit adds a script that is supposed to be invoked during the build and restores the execute permissions in the reconstruct script by adding `chmod +x $file`. But, if a file removes its execute permission, this will change it back. This happened in the last jammy release (version 5.15.0-70.77) where a commit from upstream removed the execute permission for a header file but then our scripts brought it back. [Fix] Andy proposed the following fix https://dpaste.com/6SJ8YR3BM Basically it checks if the permission was added or removed and uses either +x or -x. [Test plan] Easily tested with jammy-kvm, latest release where a rebase picked this commit "treewide: fix up files incorrectly marked executable" where `drivers/gpu/drm/vmwgfx/vmwgfx_msg_arm64.h` changed its permission from 755 to 644 (removed execute). When debian packages are prepared, you'll notice the file has changed its permission back to 755. With the fix, it should be the same. [Regression potential] Low, it is a small fix. Scripts will still have execute permission. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015498/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2015097] Re: Kernel crash during Mellanox performance testing
This bug is awaiting verification that the linux-aws/5.15.0-1038.43 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 -- 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/2015097 Title: Kernel crash during Mellanox performance testing Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Bug description: [Impact] * When performance testing using Mellanox driver, an early decrement within an if condition rather than as a result of an if condition is causing null pointer crashes. [Fix] * Clean cherry-pick from upstream (https://lore.kernel.org/netdev/20220503044209.622171-10-sae...@nvidia.com/) * Change landed v5.19 upstream, Kinetic onward not affected [Test Case] * Compile test * Boot test * Performance test [Where things could go wrong] * Regression risk is low, localized fix, purely fixes incorrect logic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015097/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2015372] Re: Add support for intel EMR cpu
This bug is awaiting verification that the linux-aws/5.15.0-1038.43 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 -- 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/2015372 Title: Add support for intel EMR cpu Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Released Bug description: SRU Justification [Impact] Intel has introduced support for their new Emerald Rapids CPU. This support is a nice feature to have in Jammy because it is an LTS release and enabling extra hardware adds to its usability. Usually backporting new features to existing kernels it's not a common practice. But these commits were easy to backport. Most of them were clean cherry picks. Some of them were already picked up from upstream stable releases, and some required manual intervention because Jammy did not have some commits applied but the actual changes were very minimal. More information about each commit is addressed inline. [Commits] 1. 9c252ecf3036: "platform/x86: intel-uncore-freq: add Emerald Rapids support" Adjusted the path to uncore-frequency.c In ce2645c458b5c83b0872ea9e39d2c3293445353a commit, this was moved to uncore-frequency dir 2. 5a8a05f165fb18d37526062419774d9088c2a9b9 "perf/x86/intel/cstate: Add Emerald Rapids" Small context adjustment in intel_cstates_match array because of missing SPR, RPL and MDL cpu models introduced in 528c9f1daf20d 3. 57512b57dcfaf63c52d8ad2fb35321328cde31b0 "perf/x86/rapl: Add support for Intel Emerald Rapids" Context adjustment due to missing - 80275ca9e525c "perf/x86/rapl: Use standard Energy Unit for SPR Dram RAPL domain" - 1ab28f17c "perf/x86/rapl: Add support for Intel AlderLake-N" - eff98a7421b3e "perf/x86/rapl: Add support for Intel Raptor Lake" - f52853a668bfe "perf/x86/rapl: Add support for Intel Meteor Lake" 4. 74528edfbc664f9d2c927c4e5a44f1285598ed0f clean cherry-pick 5. 61f9fdcdcd01f9a996b6db4e7092fcdfe8414ad5 clean cherry-pick 6. 93cac4150727dae0ee89f501dd75413b88eedec0 clean cherry-pick 7. 7adc6885259edd4ef5c9a7a62fd4270cf38fdbfb clean cherry-pick 8. e4b2bc6616e21 clean cherry-pick [Testing] Kernel was built on cbd and boot tested on a VM. TODO ask for help from intel. [Regression potential] Very low, these are minimal new features, which actually reuse a lot of the existing cpu structures/functions. The following changes since commit 8feeaa9039a290b978e7855ab82955cd9348fc13 "platform/x86: intel-uncore-freq: add Emerald Rapids support" are available in the Git repository at: git://git.launchpad.net/~~roxanan/ubuntu/+source/linux/+git/jammy lp2015372 for you to fetch changes up to commit 7d88565e6777082265b373733fd93eb3e0914e12 "EDAC/i10nm: Add Intel Emerald Rapids server support" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015372/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2013603] Re: Kernel livepatch ftrace graph fix
This bug is awaiting verification that the linux-aws/5.15.0-1038.43 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 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/2013603 Title: Kernel livepatch ftrace graph fix Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Bug description: [Impact] * Additional patch required to support Livepatch for s390x * Fixes Livepatch transition issues when using ftrace graph tracing [Test Case] * Compile test * Boot test * Test a Livepatch (patch to /proc/meminfo module) * Test Livepatch from ftrace graphed function (via https://github.com/SUSE/qa_test_klp/, klp_tc_10.sh) [Where things could go wrong] * Functionality already exists upstream, once kernel is boot and Livepatch tested - should have no regressions [Other info] * Additional required patch was identified (https://github.com/dynup/kpatch/commit/324a43714b1227b5688e22966a5ee4414c8861d1) due to ftrace graph livepatch transition issue (https://github.com/SUSE/qa_test_klp/issues/17). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2013603/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2013209] Re: expoline.o is packaged unconditionally for s390x
This bug is awaiting verification that the linux-aws/5.15.0-1038.43 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 -- 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/2013209 Title: expoline.o is packaged unconditionally for s390x Status in linux package in Ubuntu: Fix Released Status in linux-hwe-5.15 package in Ubuntu: New Status in linux-hwe-5.15 source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux source package in Lunar: Fix Released Bug description: https://bugs.launchpad.net/bugs/1639924 enabled CONFIG_EXPOLINE_EXTERN for s390x in Jammy. While this works as expected on Jammy, it won't work on some derivatives of it: for example focal:hwe-5.15. On Focal, this config can't be enabled due to the GCC version it comes with. CONFIG_EXPOLINE_EXTERN requires >= 110200 while Focal comes with 90400. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2013209/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2011926] Re: Revert "net/sched: taprio: make qdisc_leaf() see the per-netdev-queue pfifo child qdiscs"
This bug is awaiting verification that the linux-aws/5.15.0-1038.43
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
--
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/2011926
Title:
Revert "net/sched: taprio: make qdisc_leaf() see the per-netdev-queue
pfifo child qdiscs"
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Jammy:
Fix Released
Bug description:
Upstream commit: af7b29b1deaac6da3bb7637f0e263dfab7bfc7a3
Revert "net/sched: taprio: make qdisc_leaf() see the per-netdev-queue pfifo
child qdiscs"
taprio_attach() has this logic at the end, which should have been
removed with the blamed patch (which is now being reverted):
/* access to the child qdiscs is not needed in offload mode */
if (FULL_OFFLOAD_IS_ENABLED(q->flags)) {
kfree(q->qdiscs);
q->qdiscs = NULL;
}
because otherwise, we make use of q->qdiscs[] even after this array was
deallocated, namely in taprio_leaf(). Therefore, whenever one would try
to attach a valid child qdisc to a fully offloaded taprio root, one
would immediately dereference a NULL pointer.
$ tc qdisc replace dev eno0 handle 8001: parent root taprio \
num_tc 8 \
map 0 1 2 3 4 5 6 7 \
queues 1@0 1@1 1@2 1@3 1@4 1@5 1@6 1@7 \
max-sdu 0 0 0 0 0 200 0 0 \
base-time 200 \
sched-entry S 80 2 \
sched-entry S a0 2 \
sched-entry S 5f 6 \
flags 2
$ max_frame_size=1500
$ data_rate_kbps=2
$ port_transmit_rate_kbps=100
$ idleslope=$data_rate_kbps
$ sendslope=$(($idleslope - $port_transmit_rate_kbps))
$ locredit=$(($max_frame_size * $sendslope / $port_transmit_rate_kbps))
$ hicredit=$(($max_frame_size * $idleslope / $port_transmit_rate_kbps))
$ tc qdisc replace dev eno0 parent 8001:7 cbs \
idleslope $idleslope \
sendslope $sendslope \
hicredit $hicredit \
locredit $locredit \
offload 0
Unable to handle kernel NULL pointer dereference at virtual address
0030
pc : taprio_leaf+0x28/0x40
lr : qdisc_leaf+0x3c/0x60
Call trace:
taprio_leaf+0x28/0x40
tc_modify_qdisc+0xf0/0x72c
rtnetlink_rcv_msg+0x12c/0x390
netlink_rcv_skb+0x5c/0x130
rtnetlink_rcv+0x1c/0x2c
The solution is not as obvious as the problem. The code which deallocates
q->qdiscs[] is in fact copied and pasted from mqprio, which also
deallocates the array in mqprio_attach() and never uses it afterwards.
Therefore, the identical cleanup logic of priv->qdiscs[] that
mqprio_destroy() has is deceptive because it will never take place at
qdisc_destroy() time, but just at raw ops->destroy() time (otherwise
said, priv->qdiscs[] do not last for the entire lifetime of the mqprio
root), but rather, this is just the twisted way in which the Qdisc API
understands error path cleanup should be done (Qdisc_ops :: destroy() is
called even when Qdisc_ops :: init() never succeeded).
Side note, in fact this is also what the comment in mqprio_init()
says:
/* pre-allocate qdisc, attachment can't fail */
Or reworded, mqprio's priv->qdiscs[] scheme is only meant to serve as
data passing between Qdisc_ops :: init() and Qdisc_ops :: attach().
[ this comment was also copied and pasted into the initial taprio
commit, even though taprio_attach() came way later ]
The problem is that taprio also makes extensive use of the q->qdiscs[]
array in the software fast path (taprio_enqueue() and taprio_dequeue()),
but it does not keep a reference of its own on q->qdiscs[i] (you'd think
that since it creates these Qdiscs, it holds the reference, but nope,
this is not completely true).
To understand the difference between taprio_destroy() and mqprio_destroy()
one must look before commit 13511704f8d7 ("net: taprio offload: enforce
qdisc to netdev queue mapping"), because that just muddied the waters.
In the "original" taprio design, taprio always attached itself (the root
Qdisc) to all netdev TX queues, so that dev_qdisc_enqueue() would go
through taprio_enqueue().
It also called qdisc_refcount_inc() on itself for as many times as there
were netdev TX queues, in order to counter-balance what tc_get_qdisc()
does when destroying a Qdisc (simplified for bre
[Kernel-packages] [Bug 2011616] Re: Connection timeout due to conntrack limits
This bug is awaiting verification that the linux-aws/5.15.0-1038.43 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 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/2011616 Title: Connection timeout due to conntrack limits Status in linux package in Ubuntu: In Progress Status in linux-gcp package in Ubuntu: New Status in linux source package in Jammy: Fix Released Status in linux-gcp source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-gcp source package in Kinetic: Fix Released Status in linux source package in Lunar: In Progress Status in linux-gcp source package in Lunar: New Bug description: Customers of GKE 1.25 and 1.26 are affected by the conntrack performance issue that causes random connection timeouts. The fix has been committed to to the upstream's net git repo and to prodkernel and needs to be backported to Ubuntu versions with kernel 5.15. https://partnerissuetracker.corp.google.com/issues/272090522 Fix: https://git.kernel.org/pub/scm/linux/kernel/git/netfilter/nf.git/commit/?id=c77737b736ceb50fdf150434347dbd81ec76dbb1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2011616/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008157] Re: [SRU][Ubuntu 22.04.1]: Observed "Array Index out of bounds" Call Trace multiple times on Ubuntu 22.04.1 OS during boot
This bug is awaiting verification that the linux-aws/5.15.0-1038.43 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 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/2008157 Title: [SRU][Ubuntu 22.04.1]: Observed "Array Index out of bounds" Call Trace multiple times on Ubuntu 22.04.1 OS during boot Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: In Progress Bug description: SRU Justification: [Impact] When booted into Ubuntu 22.04.1 OS after installation, observed "Array Index out of bounds" Call Trace multiple times in dmesg. Call Trace is as follow: [ 6.125704] UBSAN: array-index-out-of-bounds in /build/linux-JjvoxS/linux-5.15.0/drivers/scsi/megaraid/megaraid_sas_fp.c:103:32 [ 6.125705] index 1 is out of range for type 'MR_LD_SPAN_MAP [1]' [ 6.125707] CPU: 0 PID: 18 Comm: kworker/0:1 Not tainted 5.15.0-53-generic #59-Ubuntu [ 6.125709] Hardware name: Dell Inc. , BIOS 11/08/2022 [ 6.125710] Workqueue: events work_for_cpu_fn [ 6.125716] Call Trace: [ 6.125718] [ 6.125720] show_stack+0x52/0x5c [ 6.125725] dump_stack_lvl+0x4a/0x63 [ 6.125731] dump_stack+0x10/0x16 [ 6.125732] ubsan_epilogue+0x9/0x49 [ 6.125734] __ubsan_handle_out_of_bounds.cold+0x44/0x49 [ 6.125736] ? MR_PopulateDrvRaidMap+0x194/0x580 [megaraid_sas] [ 6.125747] mr_update_load_balance_params+0xb9/0xc0 [megaraid_sas] [ 6.125753] MR_ValidateMapInfo+0x8d/0x290 [megaraid_sas] [ 6.125757] megasas_init_adapter_fusion+0x3ce/0x420 [megaraid_sas] [ 6.125762] ? megasas_setup_reply_map+0x49/0xac [megaraid_sas] [ 6.125768] megasas_init_fw.cold+0x87c/0x10c8 [megaraid_sas] [ 6.125774] megasas_probe_one+0x15c/0x4e0 [megaraid_sas] [ 6.125779] local_pci_probe+0x48/0x90 [ 6.125783] work_for_cpu_fn+0x17/0x30 [ 6.125785] process_one_work+0x228/0x3d0 [ 6.125786] worker_thread+0x223/0x420 [ 6.125787] ? process_one_work+0x3d0/0x3d0 [ 6.125788] kthread+0x127/0x150 [ 6.125790] ? set_kthread_struct+0x50/0x50 [ 6.125791] ret_from_fork+0x1f/0x30 [ 6.125796] [ 6.125796] Steps to reproduce: 1. Connect PERC H355 controller to the system 2. Create RAID1 using drives connected to PERC Controller 3. Install Ubuntu 22.04.1 on VD 4. Boot into OS after installation 5. Multiple Call Traces of "array-index-out-of-bounds" are seen Expected Behavior: OS should boot without this Call Trace [Fix] [PATCH v3 0/6] Replace one-element arrays with flexible-array members https://lore.kernel.org/linux-hardening/cover.1660592640.git.gustavo...@kernel.org/ 48658213 scsi: megaraid_sas: Use struct_size() in code related to struct MR_PD_CFG_SEQ_NUM_SYNC 41e83026 scsi: megaraid_sas: Use struct_size() in code related to struct MR_FW_RAID_MAP ee92366a scsi: megaraid_sas: Replace one-element array with flexible- array member in MR_PD_CFG_SEQ_NUM_SYNC eeb3bab7 scsi: megaraid_sas: Replace one-element array with flexible- array member in MR_DRV_RAID_MAP 204a29a1 scsi: megaraid_sas: Replace one-element array with flexible- array member in MR_FW_RAID_MAP_DYNAMIC ac23b92b scsi: megaraid_sas: Replace one-element array with flexible- array member in MR_FW_RAID_MAP [Test Plan] 1. Connect PERC H355 controller to the system 2. Create RAID1 using drives connected to PERC Controller 3. Install Ubuntu 22.04.1 on VD 4. Boot into OS after installation OS should boot without the Call Trace listed in the Impact field [Where problems could occur] [Other Info] https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/array_bounds_lp_2008157 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008157/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
This bug is awaiting verification that the linux-aws/5.15.0-1038.43
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
--
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:
Confirmed
Status in linux source package in Jammy:
Fix Released
Status in linux source package in Kinetic:
Fix Released
Status in linux source package in Lunar:
Confirmed
Bug description:
[Impact]
* Intel E810-family NICs cause system hangs when booting with bonding
enabled
* This happens due to the driver unplugging auxiliary devices
* The unplug event happens under RTNL lock context, which causes a deadlock
where the RDMA driver waits for the RNL lock to complete removal
[Test Plan]
* Users have reported that after setting up bonding on switch and server
side, the system will hang when starting network services
[Fix]
* The upstream patch defers unplugging/re-plugging of the auxiliary device,
so that it's not performed under the RTNL lock context.
* Fix was introduced by commit:
248401cb2c46 ice: avoid bonding causing auxiliary plug/unplug under
RTNL lock
[Regression Potential]
* Regressions would manifest in devices that support RDMA functionality and
have been added to a bond
* We should look out for auxiliary devices that haven't been properly
unplugged, or that cause further issues with
ice_plug_aux_dev()/ice_unplug_aux_dev()
[Original 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, 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
[Kernel-packages] [Bug 1937133] Re: devlink_port_split from ubuntu_kernel_selftests.net fails on hirsute (KeyError: 'flavour')
This bug is awaiting verification that the linux-aws/5.15.0-1038.43 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 -- 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/1937133 Title: devlink_port_split from ubuntu_kernel_selftests.net fails on hirsute (KeyError: 'flavour') Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Hirsute: Won't Fix Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux source package in Lunar: Fix Released Bug description: [Impact] On s390x LPAR instances, this test will fail with: # File "linux/tools/testing/selftests/net/devlink_port_split.py", line 64, in get_if_names # if ports[port]['flavour'] == 'physical': # KeyError: 'flavour' not ok 1 selftests: net: devlink_port_split.py # exit=1 This is because the mlx4 driver in use on this instance does not set attributes, therefore `devlink -j port show` command output does not contain this "flavour" key. [Fix] * 3de66d08d3 selftests: net: devlink_port_split.py: skip test if no suitable device available This patch can be cherry-picked into our J/K/L kernels. [Test] Run the patched devlink_port_split.py on s390x LPAR, and it won't fail with # KeyError: 'flavour' but marked as SKIP instead. [Where problems could occur] If this change is incorrect, it may affect the test result, however it's limited to testing tools, no actual impact to kernel functions. [Original Bug Report] Failing on hirsute/linux 5.11.0-26.28 host s2lp4 Not a regression as this is also failing on 5.11.0-24.25 17:16:32 DEBUG| [stdout] # selftests: net: devlink_port_split.py 17:16:32 DEBUG| [stdout] # Traceback (most recent call last): 17:16:32 DEBUG| [stdout] # File "/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py", line 283, in 17:16:32 DEBUG| [stdout] # main() 17:16:32 DEBUG| [stdout] # File "/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py", line 256, in main 17:16:32 DEBUG| [stdout] # ports = devlink_ports(dev) 17:16:32 DEBUG| [stdout] # File "/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py", line 70, in __init__ 17:16:32 DEBUG| [stdout] # self.if_names = devlink_ports.get_if_names(dev) 17:16:32 DEBUG| [stdout] # File "/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py", line 64, in get_if_names 17:16:32 DEBUG| [stdout] # if ports[port]['flavour'] == 'physical': 17:16:32 DEBUG| [stdout] # KeyError: 'flavour' 17:16:32 DEBUG| [stdout] not ok 44 selftests: net: devlink_port_split.py # exit=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1937133/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2013088] Re: kernel: fix __clear_user() inline assembly constraints
This bug is awaiting verification that the linux-aws/5.15.0-1038.43 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 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/2013088 Title: kernel: fix __clear_user() inline assembly constraints Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released 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 Status in linux source package in Lunar: Fix Released Bug description: SRU Justification: == [ Impact ] * In case clear_user() crosses two pages and faults on the second page the kernel may write lowcore contents to the first page, instead of clearing it. * The __clear_user() inline assembly misses earlyclobber constraint modifiers. Depending on compiler and compiler options this may lead to incorrect code which copies kernel lowcore contents to user space instead of clearing memory, in case clear_user() faults. [Fix] * For Kinetic and Jammy cherrypick of 89aba4c26fae 89aba4c26fae4e459f755a18912845c348ee48f3 "s390/uaccess: add missing earlyclobber annotations to __clear_user()" * For Focal and Bionic a backport of the above commit is needed: https://launchpadlibrarian.net/659551648/s390-uaccess.patch [ Test Plan ] * A test program in C is needed and used for testing. * The test will be done by IBM. [ Where problems could occur ] * The modification is limited to function 'long __clear_user'. * And there, just to one inline assembly constraints line. * This is usually difficult to trace. * A erroneous modification may lead to a wrong behavior in 'long __clear_user', * and maybe returning a wrong size (in uaccess.c). [ Other Info ] * This affects all Ubuntu releases in service, down to 18.04. * Since we are close to 23.04 kernel freeze, I submit a patch request for 23.04 separately, and submit the SRU request for the all other Ubuntu releases later. __ Description: kernel: fix __clear_user() inline assembly constraints Symptom: In case clear_user() crosses two pages and faults on the second page the kernel may write lowcore contents to the first page, instead of clearing it. Problem: The __clear_user() inline assembly misses earlyclobber constraint modifiers. Depending on compiler and compiler options this may lead to incorrect code which copies kernel lowcore contents to user space instead of clearing memory, in case clear_user() faults. Solution: Add missing earlyclobber constraint modifiers. Preventive:yes Upstream-ID: 89aba4c26fae4e459f755a18912845c348ee48f3 Affected Releases: 18.04 20.04 22.04 22.10 23.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2013088/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2018716] Re: zfs-dkms: support linux >= 6.3
This bug was fixed in the package zfs-linux - 2.1.99-0ubuntu4 --- zfs-linux (2.1.99-0ubuntu4) mantic; urgency=medium * Package master snapshot (zfs-2.1.99-1978-g4f583a827e) zfs-linux (2.1.99-0ubuntu3) mantic; urgency=medium * Fixup symbols for non-amd64 arches. * Remove all known zfs kernel modules in the smoke test. zfs-linux (2.1.99-0ubuntu2) mantic; urgency=medium * autopkgtest: skip on secureboot enabled machines. zfs-linux (2.1.99-0ubuntu1) mantic; urgency=medium * Package master snapshot (zfs-2.1.99-1955-gad0a554614) * Adds support for v6.3+ LP: #2018716 * Use native packaging without a tarball. * Lots of symbols dropped and changed: - however these are due to fvisibility=hidden - they should be internal-only - and not used externally - thus updating symbols without ABI bumps - fingers-crossed -- Dimitri John Ledkov Thu, 01 Jun 2023 16:13:59 +0100 ** Changed in: zfs-linux (Ubuntu Mantic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/2018716 Title: zfs-dkms: support linux >= 6.3 Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Mantic: Fix Released Bug description: [Impact] The current version of zfs-dkms available in lunar fails to build with kernels >= 6.3. [Test case] $ apt install zfs-dkms [Fix] Resync with zfs version in Debian (2.1.1) and apply the usual Ubuntu specific changes. [Regression potential] We may experience zfs regressions due to a new major version, especially on zfs volumes / filesystems created with the previous versions. However this goes in pair with the new major kernel version and we need to upgrade the version of zfs to properly support the new kernels >= 6.3. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2018716/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009136] Re: No HDMI audio under 5.19.0-35 & -37 (regression from -32)
@zzq4343, are you using jammy or kinetic? -- 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/2009136 Title: No HDMI audio under 5.19.0-35 & -37 (regression from -32) Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: Invalid Status in linux source package in Kinetic: Fix Released Bug description: [Impact] For amdgpu/i915, hdmi audio output device has disappeared. [Fix] The latest fix for the non-contiguous memalloc helper changed the allocation method for a non-IOMMU system to use only the fallback allocator. This should have worked, but it caused a problem sometimes when too many non-contiguous pages are allocated that can't be treated by HD-audio controller. As a quirk workaround, go back to the original strategy: use dma_alloc_noncontiguous() at first, and apply the fallback only when it fails, but only for non-IOMMU case [Test Case] 1. boot with kernel applied the patches. 2. check the cards in /proc/asound/cards. Get the hdmi cards. 0 [PCH ]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0xe232 irq 137 1 [HDMI ]: HDA-Intel - HDA ATI HDMI HDA ATI HDMI at 0xe226 irq 134 [Where problems could occur] Low, this is just workaround and may have a better solution in the future. [Misc] All patches has been landed on OEM-6.1 and lunar. ~~ CLARIFICATION: Just to avoid any confusion for those coming to this bug report; the "Jammy: invalid" status above does *not* mean that this bug doesn't affect jammy -- it does, and the kernel team is aware of this. All it reflects is that the fix has to go into the kinetic kernel package which will then flow into the kernel-hwe package implicitly. Currently known affected cards: * HD 7700 (comment 8) * R9 290 (comment 21) * RX 550 (LP: #2012141, and comment 27) * RX 570 (mine) * RX 580 (LP: #2009276, and comment 28) * WX 3200 (comment 29) * RX 6600 (LP: #2009542) * RX 6700 (LP: #2009275) [ Original Description ] After upgrading my Ubuntu jammy (22.04) desktop to the -35 release of the kernel, I found my HDMI audio output device had disappeared. Reverting to the -32 release caused it to appear again (hence why I'm filing the bug against the kernel rather than pulseaudio). I'm attaching the dmesg output from immediately after booting each kernel, but after a bit of trimming and diffing I *think* the following lines are the salient ones: input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input12 input: HDA ATI HDMI HDMI/DP,pcm=7 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input13 input: HDA ATI HDMI HDMI/DP,pcm=8 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input14 input: HDA ATI HDMI HDMI/DP,pcm=9 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input15 input: HDA ATI HDMI HDMI/DP,pcm=10 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input16 input: HDA ATI HDMI HDMI/DP,pcm=11 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input17 snd_hda_intel :2b:00.1: bound :2b:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu]) These lines appear in the dmesg of the -32 kernel, but not in the -35 kernel's log. Meanwhile, the following lines appear in the -35 kernel's log but not in the -32: hdaudio hdaudioC0D0: no AFG or MFG node found snd_hda_intel :2b:00.1: no codecs initialized I'll also attach the output of "pactl list" under each kernel (this shows the HDMI audio sink showing up under -32, but not -35) just in case that helps shed any light on things. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009136/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2021569] Re: [aarch64] Please help to enable CONFIG_REGULATOR_MT6359
** Description changed: Please help to enable CONFIG_REGULATOR_MT6359 for [aarch64] The CONFIG_REGULATOR_MT6359 option is required for MediaTek's MT8195/MT8390. This is the maintatory PMIC for MT8195/MT8390. It is currently disabled in the Mantic, Lunar. and Kinetic -generic kernel. While it is enabled in the arm-generic kernel: https://elixir.bootlin.com/linux/v5.19/source/arch/arm64/configs/defconfig#L658 https://elixir.bootlin.com/linux/latest/source/arch/arm64/configs/defconfig#L689 Please help to enable CONFIG_REGULATOR_MT6359 and related settings - CONFIG_REGULATOR_MT6359=y (or m) + CONFIG_REGULATOR_MT6359=y (MUST build in for supplying power for other peripherals) CONFIG_SND_SOC_MT6359=m CONFIG_SND_SOC_MT6359_ACCDET=m The same goes for Mantic, Lunar. Kinetic. Thanks Macpaul Lin -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/2021569 Title: [aarch64] Please help to enable CONFIG_REGULATOR_MT6359 Status in linux-meta package in Ubuntu: New Bug description: Please help to enable CONFIG_REGULATOR_MT6359 for [aarch64] The CONFIG_REGULATOR_MT6359 option is required for MediaTek's MT8195/MT8390. This is the maintatory PMIC for MT8195/MT8390. It is currently disabled in the Mantic, Lunar. and Kinetic -generic kernel. While it is enabled in the arm-generic kernel: https://elixir.bootlin.com/linux/v5.19/source/arch/arm64/configs/defconfig#L658 https://elixir.bootlin.com/linux/latest/source/arch/arm64/configs/defconfig#L689 Please help to enable CONFIG_REGULATOR_MT6359 and related settings CONFIG_REGULATOR_MT6359=y (MUST build in for supplying power for other peripherals) CONFIG_SND_SOC_MT6359=m CONFIG_SND_SOC_MT6359_ACCDET=m The same goes for Mantic, Lunar. Kinetic. Thanks Macpaul Lin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/2021569/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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-meta-raspi/5.15.0.1031.28)
All autopkgtests for the newly accepted linux-meta-raspi (5.15.0.1031.28) for jammy have finished running. The following regressions have been reported in tests triggered by the package: backport-iwlwifi-dkms/unknown (arm64) bbswitch/unknown (arm64) dpdk-kmods/unknown (arm64) evdi/unknown (arm64) fwts/unknown (arm64) gost-crypto/unknown (arm64) iptables-netflow/unknown (arm64) libvpoll-eventfd/unknown (arm64) lxc/unknown (arm64) nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.1 (armhf) nvidia-graphics-drivers-515/unknown (arm64) nvidia-graphics-drivers-525/unknown (arm64) rtl8812au/unknown (arm64) rtl8821ce/unknown (arm64) systemd/249.11-0ubuntu3.9 (arm64) v4l2loopback/unknown (arm64) wireguard/unknown (amd64, arm64) xtrx-dkms/unknown (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-meta-raspi [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 packaging 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 2020607] Re: ftracetest from selftests in linux ADT test failure with jammy/linux-intel-iotg (kernel NULL pointer dereference)
Found on J-realtime 5.15.0-1040.45 with node rizzo ** Attachment added: "j-realtime-ftrace-rizzo.log" https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2020607/+attachment/5677329/+files/j-realtime-ftrace-rizzo.log -- 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/2020607 Title: ftracetest from selftests in linux ADT test failure with jammy/linux- intel-iotg (kernel NULL pointer dereference) Status in ubuntu-kernel-tests: New Status in linux-intel-iotg package in Ubuntu: Invalid Status in linux-intel-iotg source package in Jammy: New Bug description: the failure only is seen on the machine rizzo. how to reproduce: 1. run net selftest in the kernel. 2. run ftracetest in the kernel, and then there is a highly chance that causes the kernel oops. issue could be seen on kernel 5.15.112-0515112 (mainline), 5.15.0-1030-intel-iotg, and 5.15.0-74-generic on the same machine. issue could not be reproduced on kernel 5.19.0-42-generic, 5.17.15-051715 (mainline), and 5.16.20-051620 (mainline). [13279.176639] BUG: kernel NULL pointer dereference, address: [13279.183712] #PF: supervisor instruction fetch in kernel mode [13279.189446] #PF: error_code(0x0010) - not-present page [13279.194654] PGD 0 P4D 0 [13279.197230] Oops: 0010 [#1] SMP PTI [13279.200767] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 5.15.0-74-generic #81-Ubuntu [13279.208431] Hardware name: Dell Inc. PowerEdge R310/05XKKK, BIOS 1.12.0 09/06/2013 [13279.216100] RIP: 0010:0x0 [13279.218767] Code: Unable to access opcode bytes at RIP 0xffd6. [13279.225721] RSP: 0018:9a1f80003e90 EFLAGS: 00010097 [13279.231013] RAX: RBX: 000231f0 RCX: 0004 [13279.238229] RDX: RSI: 0020 RDI: 8bfdc0074280 [13279.245449] RBP: 9a1f80003eb8 R08: 8bfdc0074280 R09: 0001 [13279.252673] R10: 0020 R11: R12: 8bfdc0074280 [13279.259900] R13: 0c13a1cab100 R14: 0004 R15: [13279.267124] FS: () GS:8bfef760() knlGS: [13279.275317] CS: 0010 DS: ES: CR0: 80050033 [13279.281140] CR2: ffd6 CR3: 4a01 CR4: 06f0 [13279.288366] Call Trace: [13279.290851] [13279.292902] tick_do_broadcast+0xa1/0xd0 [13279.296894] tick_handle_oneshot_broadcast+0x14d/0x200 [13279.302107] timer_interrupt+0x18/0x30 [13279.305914] __handle_irq_event_percpu+0x42/0x170 [13279.310689] ? timekeeping_advance+0x32a/0x470 [13279.315194] handle_irq_event+0x59/0xb0 [13279.319086] handle_edge_irq+0x8c/0x230 [13279.322976] __common_interrupt+0x52/0xe0 [13279.327045] common_interrupt+0x89/0xa0 [13279.330941] [13279.333079] [13279.335211] asm_common_interrupt+0x27/0x40 [13279.339461] RIP: 0010:cpuidle_enter_state+0xd9/0x620 [13279.344501] Code: 3d e4 e1 d8 4a e8 77 cb 67 ff 49 89 c7 0f 1f 44 00 00 31 ff e8 b8 d8 67 ff 80 7d d0 00 0f 85 61 01 00 00 fb 66 0f 1f 44 00 00 <45> 85 f6 0f 88 6d 01 00 00 4d 63 ee 49 83 fd 09 0f 87 e7 03 00 00 [13279.363476] RSP: 0018:b6603db8 EFLAGS: 0246 [13279.368768] RAX: RBX: 8bfef763b900 RCX: [13279.375984] RDX: 8bfdc01863c0 RSI: 0002 RDI: [13279.383203] RBP: b6603e08 R08: 0c13cc9b2925 R09: 000c3500 [13279.390423] R10: 0005 R11: 071c71c71c71c71c R12: b68d4b20 [13279.397646] R13: 0004 R14: 0004 R15: 0c13cc9b2925 [13279.404883] ? cpuidle_enter_state+0x24a/0x620 [13279.409389] cpuidle_enter+0x2e/0x50 [13279.413019] cpuidle_idle_call+0x142/0x1e0 [13279.417176] do_idle+0x83/0xf0 [13279.422843] cpu_startup_entry+0x20/0x30 [13279.429360] rest_init+0xd3/0x100 [13279.435396] ? acpi_enable_subsystem+0x21d/0x229 [13279.442594] arch_call_rest_init+0xe/0x23 [13279.449114] start_kernel+0x4a9/0x4ca [13279.455389] x86_64_start_reservations+0x24/0x2a [13279.462619] x86_64_start_kernel+0xfb/0x106 [13279.469328] secondary_startup_64_no_verify+0xc2/0xcb [13279.476844] [13279.481553] Modules linked in: br_netfilter tls act_mirred cls_matchall ip6_gre gre ip6_tunnel tunnel6 sch_ingress dummy ip6t_rpfilter mpls_gso mpls_iptunnel mpls_router ip_tunnel esp6 esp4 xfrm_user xfrm_algo l2tp_ip6 l2tp_eth l2tp_ip l2tp_netlink l2tp_core 8021q garp mrp ip6t_REJECT nf_reject_ipv6 ipt_REJECT nf_reject_ipv4 xt_tcpudp sch_etf sch_fq dccp_ipv6 dccp_ipv4 dccp vxlan ip6_udp_tunnel udp_tunnel bridge stp llc vrf nft_counter nft_chain_nat xt_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nft_compat nf_tables nfnetlink algif_hash af_alg veth ipmi_ssif intel_powerclamp coretemp kvm_intel kvm ipmi_
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-ibm/5.4.0.1051.77)
All autopkgtests for the newly accepted linux-meta-ibm (5.4.0.1051.77) for focal have finished running. The following regressions have been reported in tests triggered by the package: linux-ibm/5.4.0-1051.56 (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/focal/update_excuses.html#linux-meta-ibm [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 packaging 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 1786013] Autopkgtest regression report (linux-meta-aws/5.15.0.1038.37)
All autopkgtests for the newly accepted linux-meta-aws (5.15.0.1038.37) for jammy have finished running. The following regressions have been reported in tests triggered by the package: dm-writeboost/2.2.13-1ubuntu2 (amd64, arm64) dpdk-kmods/0~20220111+git-1ubuntu1~22.04.1 (amd64, arm64) rtl8812au/4.3.8.12175.20140902+dfsg-0ubuntu17~22.04.1 (amd64, arm64) systemd/249.11-0ubuntu3.9 (amd64, 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-meta-aws [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 packaging 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 1642368] Re: linux: Staging modules should be unsigned
** Changed in: linux (Ubuntu Trusty) Status: In Progress => Won't Fix -- 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/1642368 Title: linux: Staging modules should be unsigned Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux source package in Yakkety: Won't Fix Status in linux source package in Zesty: Fix Released Status in linux source package in Impish: Won't Fix Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Bug description: Modules under the drivers/staging hierarchy get little attention when it comes to vulnerabilities. It is possible that memory mapping tricks that expose kernel internals would go unnoticed. Therefore, do not sign staging modules so that they cannot be loaded in a secure boot environment. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1642368/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1767654] Re: [Intel Braswell/Cherryview] Cursor gets stuck on left side of the screen
** Changed in: linux Status: New => 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/1767654 Title: [Intel Braswell/Cherryview] Cursor gets stuck on left side of the screen Status in Linux: Fix Released Status in linux package in Ubuntu: Confirmed Bug description: When moving the cursor to the left side of the screen, it stops close to the edge. The cursor still moves over in the area but invisible until I move it out of the area. When it doesn't do this, glitching occurs on the screen where the cursor is until I log out. And on screen cast it shows the cursor going to the side of the screen and moving. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 28 09:49:51 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b1] (rev 21) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:2060] InstallationDate: Installed on 2018-04-27 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: \\boot\vmlinuz-4.15.0-20-generic root=UUID=c6f92850-287a-4747-ac0d-3af593994183 ro quiet splash vt.handoff=1 initrd=boot\initrd.img-4.15.0-20-generic SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/08/2017 dmi.bios.vendor: Intel Corp. dmi.bios.version: PYBSWCEL.86A.0062.2017.0308.1328 dmi.board.name: NUC5CPYB dmi.board.vendor: Intel Corporation dmi.board.version: H61145-408 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0062.2017.0308.1328:bd03/08/2017:svn:pn:pvr:rvnIntelCorporation:rnNUC5CPYB:rvrH61145-408:cvn:ct3:cvr: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1767654/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2022298] [NEW] package linux-nvidia-tools-common (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-intel-iotg-too
Public bug reported: i recieved this error while executing the install of the package ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-nvidia-tools-common (not installed) ProcVersionSignature: Ubuntu 5.19.0-42.43~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 AptOrdering: linux-nvidia-tools-common:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Jun 2 11:29:15 2023 DpkgTerminalLog: Preparing to unpack .../linux-nvidia-tools-common_5.15.0-1026.26_all.deb ... Unpacking linux-nvidia-tools-common (5.15.0-1026.26) ... [1mdpkg:[0m error processing archive /var/cache/apt/archives/linux-nvidia-tools-common_5.15.0-1026.26_all.deb (--unpack): trying to overwrite '/usr/bin/acpidbg', which is also in package linux-intel-iotg-tools-common 5.15.0-1030.35 ErrorMessage: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-intel-iotg-tools-common 5.15.0-1030.35 InstallationDate: Installed on 2023-04-18 (45 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.9 SourcePackage: linux-nvidia Title: package linux-nvidia-tools-common (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-intel-iotg-tools-common 5.15.0-1030.35 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-nvidia (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 linux-nvidia in Ubuntu. https://bugs.launchpad.net/bugs/2022298 Title: package linux-nvidia-tools-common (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-intel-iotg-tools-common 5.15.0-1030.35 Status in linux-nvidia package in Ubuntu: New Bug description: i recieved this error while executing the install of the package ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-nvidia-tools-common (not installed) ProcVersionSignature: Ubuntu 5.19.0-42.43~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 AptOrdering: linux-nvidia-tools-common:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Jun 2 11:29:15 2023 DpkgTerminalLog: Preparing to unpack .../linux-nvidia-tools-common_5.15.0-1026.26_all.deb ... Unpacking linux-nvidia-tools-common (5.15.0-1026.26) ... [1mdpkg:[0m error processing archive /var/cache/apt/archives/linux-nvidia-tools-common_5.15.0-1026.26_all.deb (--unpack): trying to overwrite '/usr/bin/acpidbg', which is also in package linux-intel-iotg-tools-common 5.15.0-1030.35 ErrorMessage: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-intel-iotg-tools-common 5.15.0-1030.35 InstallationDate: Installed on 2023-04-18 (45 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.9 SourcePackage: linux-nvidia Title: package linux-nvidia-tools-common (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-intel-iotg-tools-common 5.15.0-1030.35 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia/+bug/2022298/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2017332] Re: package linux-headers-6.2.0-20-generic (not installed) failed to install/upgrade: installed linux-headers-6.2.0-20-generic package post-installation script subproce
$ dkms remove 8812au/5.6.4.2_35491.20191025 --all -- 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/2017332 Title: package linux-headers-6.2.0-20-generic (not installed) failed to install/upgrade: installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 Status in linux package in Ubuntu: Invalid Bug description: I uninstalled kernel 6.2 because it is not working. ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-headers-6.2.0-20-generic (not installed) ProcVersionSignature: Ubuntu 5.15.0-70.77-generic 5.15.92 Uname: Linux 5.15.0-70-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: meda 3631 F wireplumber /dev/snd/controlC1: meda 3631 F wireplumber /dev/snd/seq:meda 3629 F pipewire CRDA: N/A CasperMD5CheckResult: unknown Date: Thu Apr 20 18:10:12 2023 ErrorMessage: installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 IwConfig: lono wireless extensions. enp4s0no wireless extensions. MachineType: Acer Aspire M5811 ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-70-generic root=UUID=118c3ae1-d7da-491e-bff7-c010d56ea4a7 ro recovery nomodeset dis_ucode_ldr PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.06-2ubuntu16 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux Title: package linux-headers-6.2.0-20-generic (not installed) failed to install/upgrade: installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to lunar on 2023-04-20 (1 days ago) dmi.bios.date: 03/23/2010 dmi.bios.release: 8.15 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P01-B1 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: H57M01 dmi.board.vendor: Acer dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP01-B1:bd03/23/2010:br8.15:svnAcer:pnAspireM5811:pvr:rvnAcer:rnH57M01:rvr:cvnAcer:ct3:cvr:skuToBeFilledByO.E.M.: dmi.product.family: Acer Desktop dmi.product.name: Aspire M5811 dmi.product.sku: To Be Filled By O.E.M. dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2017332/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2022098] Re: Severe NFS performance degradation after LP #2003053
** Changed in: linux-gke (Ubuntu Focal) Status: New => Fix Committed ** Changed in: linux-gke (Ubuntu Jammy) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gke in Ubuntu. https://bugs.launchpad.net/bugs/2022098 Title: Severe NFS performance degradation after LP #2003053 Status in linux-gke package in Ubuntu: New Status in linux-gke source package in Focal: Fix Committed Status in linux-gke source package in Jammy: Fix Committed Bug description: The fix to LP #2003053 has caused massively increased NFS server access in some use-cases, which caused severe performance degradation to the point of being unusable in some cases. The solution to this issue, at least temporarily and at least for linux-gke, is to make the new behaviour optional using the "nfs_fasc=1" module parameter. Without this parameter specified, (or specified as =0) will keep the old behaviour. Regresion potential: - Regression potential is considered low considering the scope of the change and is limited to NFS only. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gke/+bug/2022098/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2022061] Re: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: installed linux-headers-6.2.0-20-generic package post-installation script subprocess r
*** This bug is a duplicate of bug 2017332 *** https://bugs.launchpad.net/bugs/2017332 Building module: Cleaning build area... 'make' -j12 KVER=6.2.0-20-generic KSRC=/lib/modules/6.2.0-20-generic/build.(bad exit status: 2) ERROR (dkms apport): binary package for rtl8812au: 5.3.4 not found Error! Bad return status for module build on kernel: 6.2.0-20-generic (x86_64) Consult /var/lib/dkms/rtl8812au/5.3.4/build/make.log for more information. Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. ...fail! ** This bug has been marked a duplicate of bug 2017332 package linux-headers-6.2.0-20-generic (not installed) failed to install/upgrade: installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 -- 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/2022061 Title: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 Status in linux package in Ubuntu: Confirmed Bug description: this bug appeared after I tried to upgrade to 23.04 from 22.10, every time I tried to restart the computer, the computer ended up in kernel panic. I was not able to remove the extra package and instead I am starting the computer with an older version of kernel (Ubuntu 5.19.0-41.42-generic 5.19.17 as stated in the version.log). The information from the ubuntu-bug linux is therefore not too helpful as it only reports that I am running an unsupported kernel and I should try again to run the report with a new kernel which is not possible. I am using release23.04 The system was not able to to locate package pkgname. I expected the kernel to be upgraded with the new one 6.20.* and the computer run smoothly, instead, the computer ends up in kernel panic and I needed to start the machine with an older version of kernel. ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-headers-6.2.0-20-generic 6.2.0-20.20 ProcVersionSignature: Ubuntu 5.19.0-41.42-generic 5.19.17 Uname: Linux 5.19.0-41-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 AptOrdering: snapd:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: unknown Date: Thu Jun 1 07:56:17 2023 DpkgHistoryLog: Start-Date: 2023-06-01 07:55:39 Commandline: /usr/bin/unattended-upgrade Upgrade: snapd:amd64 (2.59.1+23.04ubuntu1, 2.59.1+23.04ubuntu1.1) ErrorMessage: installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-02-25 (1191 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. Precision 7920 Tower ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-41-generic root=UUID=380d0a7f-8500-4b5f-b8ba-80548f634c14 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. Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.06-2ubuntu16 RfKill: SourcePackage: linux Title: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to lunar on 2023-05-12 (19 days ago) dmi.bios.date: 07/29/2019 dmi.bios.release: 2.1 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.1.4 dmi.board.name: 060K5C dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.1.4:bd07/29/2019:br2.1:svnDellInc.:pnPrecision7920Tower:pvr:rvnDellInc.:rn060K5C:rvrA00:cvnDellInc.:ct3:cvr:sku073A: dmi.product.family: Precision dmi.product.name: Precision 7920 Tower dmi.product.sku: 073A dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2022061/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2022061] Re: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: installed linux-headers-6.2.0-20-generic package post-installation script subprocess r
*** This bug is a duplicate of bug 2017332 *** https://bugs.launchpad.net/bugs/2017332 $ dkms remove rtl8812au/5.3.4 --all -- 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/2022061 Title: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 Status in linux package in Ubuntu: Confirmed Bug description: this bug appeared after I tried to upgrade to 23.04 from 22.10, every time I tried to restart the computer, the computer ended up in kernel panic. I was not able to remove the extra package and instead I am starting the computer with an older version of kernel (Ubuntu 5.19.0-41.42-generic 5.19.17 as stated in the version.log). The information from the ubuntu-bug linux is therefore not too helpful as it only reports that I am running an unsupported kernel and I should try again to run the report with a new kernel which is not possible. I am using release23.04 The system was not able to to locate package pkgname. I expected the kernel to be upgraded with the new one 6.20.* and the computer run smoothly, instead, the computer ends up in kernel panic and I needed to start the machine with an older version of kernel. ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-headers-6.2.0-20-generic 6.2.0-20.20 ProcVersionSignature: Ubuntu 5.19.0-41.42-generic 5.19.17 Uname: Linux 5.19.0-41-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 AptOrdering: snapd:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: unknown Date: Thu Jun 1 07:56:17 2023 DpkgHistoryLog: Start-Date: 2023-06-01 07:55:39 Commandline: /usr/bin/unattended-upgrade Upgrade: snapd:amd64 (2.59.1+23.04ubuntu1, 2.59.1+23.04ubuntu1.1) ErrorMessage: installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-02-25 (1191 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. Precision 7920 Tower ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-41-generic root=UUID=380d0a7f-8500-4b5f-b8ba-80548f634c14 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. Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.06-2ubuntu16 RfKill: SourcePackage: linux Title: package linux-headers-6.2.0-20-generic 6.2.0-20.20 failed to install/upgrade: installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to lunar on 2023-05-12 (19 days ago) dmi.bios.date: 07/29/2019 dmi.bios.release: 2.1 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.1.4 dmi.board.name: 060K5C dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.1.4:bd07/29/2019:br2.1:svnDellInc.:pnPrecision7920Tower:pvr:rvnDellInc.:rn060K5C:rvrA00:cvnDellInc.:ct3:cvr:sku073A: dmi.product.family: Precision dmi.product.name: Precision 7920 Tower dmi.product.sku: 073A dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2022061/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2021830] Re: GVE: Performance improvement for "jumbo" frames
** Changed in: linux-gcp (Ubuntu Kinetic)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-gcp in Ubuntu.
https://bugs.launchpad.net/bugs/2021830
Title:
GVE: Performance improvement for "jumbo" frames
Status in linux-gcp package in Ubuntu:
New
Status in linux-gcp source package in Kinetic:
Fix Committed
Bug description:
This patch
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=82fd151d38d9fda714c5bb2e9e79ecd6bdc72da6
is a performance improvement fix for handling 9k frames on gvnic and
is being requested by GCP for the 5.19 kernel.
Testing:
- Boot tested with gvnic, tested basic networking functionality
Regression potential:
- Small regression potential - impact limited to the gvnic driver ("gve")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2021830/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
