[Kernel-packages] [Bug 2022826] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/2022826/+attachment/5682470/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2022826 Title: Ethernet hangs Status in linux-firmware package in Ubuntu: New Bug description: I'm now getting my wired (i.e. Ethernet) connection hanging on trying to connect. I've tried switching ports (on the router) and using a different cable, but still the same. ifconfig shows for Ethernet: enp2s0: flags=4163 mtu 1500 ether 50:eb:f6:ef:a4:e6 txqueuelen 1000 (Ethernet) RX packets 2779 bytes 250524 (250.5 KB) RX errors 0 dropped 1 overruns 0 frame 0 TX packets 355 bytes 72171 (72.1 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 sudo lshw -C enp2s0 shows nothing lspci -nn shows for Ethernet: 02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller [10ec:8125] (rev 05) I found a web page: https://tutorialforlinux.com/2021/05...based-systems/ I followed the instructions and installed realtek-r8125-dkms package OK. On rebooting, I followed the instructed procedure (shown when installing the package) of creating a password and then entering it when requested on the reboot. But still same problem. Any ideas what to do? PS I've switched Wi-Fi on (though I'd prefer to use Ethernet, as my Wi-Fi is a little flaky due to walls) in order to post this question. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-firmware 20220329.git681281e4-0ubuntu3.13 ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Jun 3 07:29:15 2023 Dependencies: firmware-sof-signed 2.0-1ubuntu4.1 InstallationDate: Installed on 2022-08-21 (285 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: ASUSTeK COMPUTER INC. MINIPC PN50-E1 PackageArchitecture: all ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-43-generic root=UUID=1d99d177-09b2-43e7-b6c1-451d081353f8 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.19.0-43-generic N/A linux-backports-modules-5.19.0-43-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.13 SourcePackage: linux-firmware UpgradeStatus: Upgraded to jammy on 2022-10-06 (239 days ago) dmi.bios.date: 03/18/2021 dmi.bios.release: 4.5 dmi.bios.vendor: ASUSTeK COMPUTER INC. dmi.bios.version: 0405 dmi.board.asset.tag: Default string dmi.board.name: PN50-E1 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnASUSTeKCOMPUTERINC.:bvr0405:bd03/18/2021:br4.5:svnASUSTeKCOMPUTERINC.:pnMINIPCPN50-E1:pvr0405:rvnASUSTeKCOMPUTERINC.:rnPN50-E1:rvrTobefilledbyO.E.M.:cvnDefaultstring:ct35:cvrDefaultstring:sku: dmi.product.family: Vivo PC dmi.product.name: MINIPC PN50-E1 dmi.product.version: 0405 dmi.sys.vendor: ASUSTeK COMPUTER INC. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: john 1682 F pulseaudio /dev/snd/controlC2: john 1682 F pulseaudio /dev/snd/controlC1: john 1682 F pulseaudio /dev/snd/controlC0: john 1682 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Dependencies: firmware-sof-signed 2.0-1ubuntu4.1 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-06-15 (12 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) MachineType: Micro Computer (HK) Tech Limited MC560 Package: linux-firmware 20220329.git681281e4-0ubuntu3.13 PackageArchitecture: all ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-45-generic root=UUID=ef5c33e1-311f-4fd6-ae66-aa6877e464df ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-45.46~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-45-generic N/A linux-backports-modules-5.19.0-45-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.13 Tags: wayland-session jammy Uname: Linux 5.19.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/07/2022 dmi.bios.release: 5.19 dmi.bios.vendor:
[Kernel-packages] [Bug 2022826] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/2022826/+attachment/5682469/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2022826 Title: Ethernet hangs Status in linux-firmware package in Ubuntu: New Bug description: I'm now getting my wired (i.e. Ethernet) connection hanging on trying to connect. I've tried switching ports (on the router) and using a different cable, but still the same. ifconfig shows for Ethernet: enp2s0: flags=4163 mtu 1500 ether 50:eb:f6:ef:a4:e6 txqueuelen 1000 (Ethernet) RX packets 2779 bytes 250524 (250.5 KB) RX errors 0 dropped 1 overruns 0 frame 0 TX packets 355 bytes 72171 (72.1 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 sudo lshw -C enp2s0 shows nothing lspci -nn shows for Ethernet: 02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller [10ec:8125] (rev 05) I found a web page: https://tutorialforlinux.com/2021/05...based-systems/ I followed the instructions and installed realtek-r8125-dkms package OK. On rebooting, I followed the instructed procedure (shown when installing the package) of creating a password and then entering it when requested on the reboot. But still same problem. Any ideas what to do? PS I've switched Wi-Fi on (though I'd prefer to use Ethernet, as my Wi-Fi is a little flaky due to walls) in order to post this question. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-firmware 20220329.git681281e4-0ubuntu3.13 ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Jun 3 07:29:15 2023 Dependencies: firmware-sof-signed 2.0-1ubuntu4.1 InstallationDate: Installed on 2022-08-21 (285 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: ASUSTeK COMPUTER INC. MINIPC PN50-E1 PackageArchitecture: all ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-43-generic root=UUID=1d99d177-09b2-43e7-b6c1-451d081353f8 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.19.0-43-generic N/A linux-backports-modules-5.19.0-43-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.13 SourcePackage: linux-firmware UpgradeStatus: Upgraded to jammy on 2022-10-06 (239 days ago) dmi.bios.date: 03/18/2021 dmi.bios.release: 4.5 dmi.bios.vendor: ASUSTeK COMPUTER INC. dmi.bios.version: 0405 dmi.board.asset.tag: Default string dmi.board.name: PN50-E1 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnASUSTeKCOMPUTERINC.:bvr0405:bd03/18/2021:br4.5:svnASUSTeKCOMPUTERINC.:pnMINIPCPN50-E1:pvr0405:rvnASUSTeKCOMPUTERINC.:rnPN50-E1:rvrTobefilledbyO.E.M.:cvnDefaultstring:ct35:cvrDefaultstring:sku: dmi.product.family: Vivo PC dmi.product.name: MINIPC PN50-E1 dmi.product.version: 0405 dmi.sys.vendor: ASUSTeK COMPUTER INC. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: john 1682 F pulseaudio /dev/snd/controlC2: john 1682 F pulseaudio /dev/snd/controlC1: john 1682 F pulseaudio /dev/snd/controlC0: john 1682 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Dependencies: firmware-sof-signed 2.0-1ubuntu4.1 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-06-15 (12 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) MachineType: Micro Computer (HK) Tech Limited MC560 Package: linux-firmware 20220329.git681281e4-0ubuntu3.13 PackageArchitecture: all ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-45-generic root=UUID=ef5c33e1-311f-4fd6-ae66-aa6877e464df ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-45.46~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-45-generic N/A linux-backports-modules-5.19.0-45-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.13 Tags: wayland-session jammy Uname: Linux 5.19.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/07/2022 dmi.bios.release: 5.19 dmi.bios.vendor: American
[Kernel-packages] [Bug 2022826] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/2022826/+attachment/5682468/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2022826 Title: Ethernet hangs Status in linux-firmware package in Ubuntu: New Bug description: I'm now getting my wired (i.e. Ethernet) connection hanging on trying to connect. I've tried switching ports (on the router) and using a different cable, but still the same. ifconfig shows for Ethernet: enp2s0: flags=4163 mtu 1500 ether 50:eb:f6:ef:a4:e6 txqueuelen 1000 (Ethernet) RX packets 2779 bytes 250524 (250.5 KB) RX errors 0 dropped 1 overruns 0 frame 0 TX packets 355 bytes 72171 (72.1 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 sudo lshw -C enp2s0 shows nothing lspci -nn shows for Ethernet: 02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller [10ec:8125] (rev 05) I found a web page: https://tutorialforlinux.com/2021/05...based-systems/ I followed the instructions and installed realtek-r8125-dkms package OK. On rebooting, I followed the instructed procedure (shown when installing the package) of creating a password and then entering it when requested on the reboot. But still same problem. Any ideas what to do? PS I've switched Wi-Fi on (though I'd prefer to use Ethernet, as my Wi-Fi is a little flaky due to walls) in order to post this question. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-firmware 20220329.git681281e4-0ubuntu3.13 ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Jun 3 07:29:15 2023 Dependencies: firmware-sof-signed 2.0-1ubuntu4.1 InstallationDate: Installed on 2022-08-21 (285 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: ASUSTeK COMPUTER INC. MINIPC PN50-E1 PackageArchitecture: all ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-43-generic root=UUID=1d99d177-09b2-43e7-b6c1-451d081353f8 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.19.0-43-generic N/A linux-backports-modules-5.19.0-43-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.13 SourcePackage: linux-firmware UpgradeStatus: Upgraded to jammy on 2022-10-06 (239 days ago) dmi.bios.date: 03/18/2021 dmi.bios.release: 4.5 dmi.bios.vendor: ASUSTeK COMPUTER INC. dmi.bios.version: 0405 dmi.board.asset.tag: Default string dmi.board.name: PN50-E1 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnASUSTeKCOMPUTERINC.:bvr0405:bd03/18/2021:br4.5:svnASUSTeKCOMPUTERINC.:pnMINIPCPN50-E1:pvr0405:rvnASUSTeKCOMPUTERINC.:rnPN50-E1:rvrTobefilledbyO.E.M.:cvnDefaultstring:ct35:cvrDefaultstring:sku: dmi.product.family: Vivo PC dmi.product.name: MINIPC PN50-E1 dmi.product.version: 0405 dmi.sys.vendor: ASUSTeK COMPUTER INC. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: john 1682 F pulseaudio /dev/snd/controlC2: john 1682 F pulseaudio /dev/snd/controlC1: john 1682 F pulseaudio /dev/snd/controlC0: john 1682 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Dependencies: firmware-sof-signed 2.0-1ubuntu4.1 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-06-15 (12 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) MachineType: Micro Computer (HK) Tech Limited MC560 Package: linux-firmware 20220329.git681281e4-0ubuntu3.13 PackageArchitecture: all ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-45-generic root=UUID=ef5c33e1-311f-4fd6-ae66-aa6877e464df ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-45.46~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-45-generic N/A linux-backports-modules-5.19.0-45-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.13 Tags: wayland-session jammy Uname: Linux 5.19.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/07/2022 dmi.bios.release: 5.19 dmi.bios.vendor: American
[Kernel-packages] [Bug 2022826] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/2022826/+attachment/5682467/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2022826 Title: Ethernet hangs Status in linux-firmware package in Ubuntu: New Bug description: I'm now getting my wired (i.e. Ethernet) connection hanging on trying to connect. I've tried switching ports (on the router) and using a different cable, but still the same. ifconfig shows for Ethernet: enp2s0: flags=4163 mtu 1500 ether 50:eb:f6:ef:a4:e6 txqueuelen 1000 (Ethernet) RX packets 2779 bytes 250524 (250.5 KB) RX errors 0 dropped 1 overruns 0 frame 0 TX packets 355 bytes 72171 (72.1 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 sudo lshw -C enp2s0 shows nothing lspci -nn shows for Ethernet: 02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller [10ec:8125] (rev 05) I found a web page: https://tutorialforlinux.com/2021/05...based-systems/ I followed the instructions and installed realtek-r8125-dkms package OK. On rebooting, I followed the instructed procedure (shown when installing the package) of creating a password and then entering it when requested on the reboot. But still same problem. Any ideas what to do? PS I've switched Wi-Fi on (though I'd prefer to use Ethernet, as my Wi-Fi is a little flaky due to walls) in order to post this question. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-firmware 20220329.git681281e4-0ubuntu3.13 ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Jun 3 07:29:15 2023 Dependencies: firmware-sof-signed 2.0-1ubuntu4.1 InstallationDate: Installed on 2022-08-21 (285 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: ASUSTeK COMPUTER INC. MINIPC PN50-E1 PackageArchitecture: all ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-43-generic root=UUID=1d99d177-09b2-43e7-b6c1-451d081353f8 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.19.0-43-generic N/A linux-backports-modules-5.19.0-43-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.13 SourcePackage: linux-firmware UpgradeStatus: Upgraded to jammy on 2022-10-06 (239 days ago) dmi.bios.date: 03/18/2021 dmi.bios.release: 4.5 dmi.bios.vendor: ASUSTeK COMPUTER INC. dmi.bios.version: 0405 dmi.board.asset.tag: Default string dmi.board.name: PN50-E1 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnASUSTeKCOMPUTERINC.:bvr0405:bd03/18/2021:br4.5:svnASUSTeKCOMPUTERINC.:pnMINIPCPN50-E1:pvr0405:rvnASUSTeKCOMPUTERINC.:rnPN50-E1:rvrTobefilledbyO.E.M.:cvnDefaultstring:ct35:cvrDefaultstring:sku: dmi.product.family: Vivo PC dmi.product.name: MINIPC PN50-E1 dmi.product.version: 0405 dmi.sys.vendor: ASUSTeK COMPUTER INC. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: john 1682 F pulseaudio /dev/snd/controlC2: john 1682 F pulseaudio /dev/snd/controlC1: john 1682 F pulseaudio /dev/snd/controlC0: john 1682 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Dependencies: firmware-sof-signed 2.0-1ubuntu4.1 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-06-15 (12 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) MachineType: Micro Computer (HK) Tech Limited MC560 Package: linux-firmware 20220329.git681281e4-0ubuntu3.13 PackageArchitecture: all ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-45-generic root=UUID=ef5c33e1-311f-4fd6-ae66-aa6877e464df ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-45.46~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-45-generic N/A linux-backports-modules-5.19.0-45-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.13 Tags: wayland-session jammy Uname: Linux 5.19.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/07/2022 dmi.bios.release: 5.19 dmi.bios.vendor:
[Kernel-packages] [Bug 2022826] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/2022826/+attachment/5682471/+files/acpidump.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2022826 Title: Ethernet hangs Status in linux-firmware package in Ubuntu: New Bug description: I'm now getting my wired (i.e. Ethernet) connection hanging on trying to connect. I've tried switching ports (on the router) and using a different cable, but still the same. ifconfig shows for Ethernet: enp2s0: flags=4163 mtu 1500 ether 50:eb:f6:ef:a4:e6 txqueuelen 1000 (Ethernet) RX packets 2779 bytes 250524 (250.5 KB) RX errors 0 dropped 1 overruns 0 frame 0 TX packets 355 bytes 72171 (72.1 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 sudo lshw -C enp2s0 shows nothing lspci -nn shows for Ethernet: 02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller [10ec:8125] (rev 05) I found a web page: https://tutorialforlinux.com/2021/05...based-systems/ I followed the instructions and installed realtek-r8125-dkms package OK. On rebooting, I followed the instructed procedure (shown when installing the package) of creating a password and then entering it when requested on the reboot. But still same problem. Any ideas what to do? PS I've switched Wi-Fi on (though I'd prefer to use Ethernet, as my Wi-Fi is a little flaky due to walls) in order to post this question. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-firmware 20220329.git681281e4-0ubuntu3.13 ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Jun 3 07:29:15 2023 Dependencies: firmware-sof-signed 2.0-1ubuntu4.1 InstallationDate: Installed on 2022-08-21 (285 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: ASUSTeK COMPUTER INC. MINIPC PN50-E1 PackageArchitecture: all ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-43-generic root=UUID=1d99d177-09b2-43e7-b6c1-451d081353f8 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.19.0-43-generic N/A linux-backports-modules-5.19.0-43-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.13 SourcePackage: linux-firmware UpgradeStatus: Upgraded to jammy on 2022-10-06 (239 days ago) dmi.bios.date: 03/18/2021 dmi.bios.release: 4.5 dmi.bios.vendor: ASUSTeK COMPUTER INC. dmi.bios.version: 0405 dmi.board.asset.tag: Default string dmi.board.name: PN50-E1 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnASUSTeKCOMPUTERINC.:bvr0405:bd03/18/2021:br4.5:svnASUSTeKCOMPUTERINC.:pnMINIPCPN50-E1:pvr0405:rvnASUSTeKCOMPUTERINC.:rnPN50-E1:rvrTobefilledbyO.E.M.:cvnDefaultstring:ct35:cvrDefaultstring:sku: dmi.product.family: Vivo PC dmi.product.name: MINIPC PN50-E1 dmi.product.version: 0405 dmi.sys.vendor: ASUSTeK COMPUTER INC. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: john 1682 F pulseaudio /dev/snd/controlC2: john 1682 F pulseaudio /dev/snd/controlC1: john 1682 F pulseaudio /dev/snd/controlC0: john 1682 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Dependencies: firmware-sof-signed 2.0-1ubuntu4.1 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-06-15 (12 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) MachineType: Micro Computer (HK) Tech Limited MC560 Package: linux-firmware 20220329.git681281e4-0ubuntu3.13 PackageArchitecture: all ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-45-generic root=UUID=ef5c33e1-311f-4fd6-ae66-aa6877e464df ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-45.46~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-45-generic N/A linux-backports-modules-5.19.0-45-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.13 Tags: wayland-session jammy Uname: Linux 5.19.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/07/2022 dmi.bios.release: 5.19 dmi.bios.vendor: American
[Kernel-packages] [Bug 2022826] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/2022826/+attachment/5682466/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2022826 Title: Ethernet hangs Status in linux-firmware package in Ubuntu: New Bug description: I'm now getting my wired (i.e. Ethernet) connection hanging on trying to connect. I've tried switching ports (on the router) and using a different cable, but still the same. ifconfig shows for Ethernet: enp2s0: flags=4163 mtu 1500 ether 50:eb:f6:ef:a4:e6 txqueuelen 1000 (Ethernet) RX packets 2779 bytes 250524 (250.5 KB) RX errors 0 dropped 1 overruns 0 frame 0 TX packets 355 bytes 72171 (72.1 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 sudo lshw -C enp2s0 shows nothing lspci -nn shows for Ethernet: 02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller [10ec:8125] (rev 05) I found a web page: https://tutorialforlinux.com/2021/05...based-systems/ I followed the instructions and installed realtek-r8125-dkms package OK. On rebooting, I followed the instructed procedure (shown when installing the package) of creating a password and then entering it when requested on the reboot. But still same problem. Any ideas what to do? PS I've switched Wi-Fi on (though I'd prefer to use Ethernet, as my Wi-Fi is a little flaky due to walls) in order to post this question. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-firmware 20220329.git681281e4-0ubuntu3.13 ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Jun 3 07:29:15 2023 Dependencies: firmware-sof-signed 2.0-1ubuntu4.1 InstallationDate: Installed on 2022-08-21 (285 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: ASUSTeK COMPUTER INC. MINIPC PN50-E1 PackageArchitecture: all ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-43-generic root=UUID=1d99d177-09b2-43e7-b6c1-451d081353f8 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.19.0-43-generic N/A linux-backports-modules-5.19.0-43-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.13 SourcePackage: linux-firmware UpgradeStatus: Upgraded to jammy on 2022-10-06 (239 days ago) dmi.bios.date: 03/18/2021 dmi.bios.release: 4.5 dmi.bios.vendor: ASUSTeK COMPUTER INC. dmi.bios.version: 0405 dmi.board.asset.tag: Default string dmi.board.name: PN50-E1 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnASUSTeKCOMPUTERINC.:bvr0405:bd03/18/2021:br4.5:svnASUSTeKCOMPUTERINC.:pnMINIPCPN50-E1:pvr0405:rvnASUSTeKCOMPUTERINC.:rnPN50-E1:rvrTobefilledbyO.E.M.:cvnDefaultstring:ct35:cvrDefaultstring:sku: dmi.product.family: Vivo PC dmi.product.name: MINIPC PN50-E1 dmi.product.version: 0405 dmi.sys.vendor: ASUSTeK COMPUTER INC. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: john 1682 F pulseaudio /dev/snd/controlC2: john 1682 F pulseaudio /dev/snd/controlC1: john 1682 F pulseaudio /dev/snd/controlC0: john 1682 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Dependencies: firmware-sof-signed 2.0-1ubuntu4.1 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-06-15 (12 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) MachineType: Micro Computer (HK) Tech Limited MC560 Package: linux-firmware 20220329.git681281e4-0ubuntu3.13 PackageArchitecture: all ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-45-generic root=UUID=ef5c33e1-311f-4fd6-ae66-aa6877e464df ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-45.46~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-45-generic N/A linux-backports-modules-5.19.0-45-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.13 Tags: wayland-session jammy Uname: Linux 5.19.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/07/2022 dmi.bios.release: 5.19 dmi.bios.vendor:
[Kernel-packages] [Bug 2022826] Re: Ethernet hangs
Running 'apport-collect 2022826' as other similar bugs show that it was requested by kernel devs. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2022826 Title: Ethernet hangs Status in linux-firmware package in Ubuntu: New Bug description: I'm now getting my wired (i.e. Ethernet) connection hanging on trying to connect. I've tried switching ports (on the router) and using a different cable, but still the same. ifconfig shows for Ethernet: enp2s0: flags=4163 mtu 1500 ether 50:eb:f6:ef:a4:e6 txqueuelen 1000 (Ethernet) RX packets 2779 bytes 250524 (250.5 KB) RX errors 0 dropped 1 overruns 0 frame 0 TX packets 355 bytes 72171 (72.1 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 sudo lshw -C enp2s0 shows nothing lspci -nn shows for Ethernet: 02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller [10ec:8125] (rev 05) I found a web page: https://tutorialforlinux.com/2021/05...based-systems/ I followed the instructions and installed realtek-r8125-dkms package OK. On rebooting, I followed the instructed procedure (shown when installing the package) of creating a password and then entering it when requested on the reboot. But still same problem. Any ideas what to do? PS I've switched Wi-Fi on (though I'd prefer to use Ethernet, as my Wi-Fi is a little flaky due to walls) in order to post this question. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-firmware 20220329.git681281e4-0ubuntu3.13 ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Jun 3 07:29:15 2023 Dependencies: firmware-sof-signed 2.0-1ubuntu4.1 InstallationDate: Installed on 2022-08-21 (285 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: ASUSTeK COMPUTER INC. MINIPC PN50-E1 PackageArchitecture: all ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-43-generic root=UUID=1d99d177-09b2-43e7-b6c1-451d081353f8 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.19.0-43-generic N/A linux-backports-modules-5.19.0-43-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.13 SourcePackage: linux-firmware UpgradeStatus: Upgraded to jammy on 2022-10-06 (239 days ago) dmi.bios.date: 03/18/2021 dmi.bios.release: 4.5 dmi.bios.vendor: ASUSTeK COMPUTER INC. dmi.bios.version: 0405 dmi.board.asset.tag: Default string dmi.board.name: PN50-E1 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnASUSTeKCOMPUTERINC.:bvr0405:bd03/18/2021:br4.5:svnASUSTeKCOMPUTERINC.:pnMINIPCPN50-E1:pvr0405:rvnASUSTeKCOMPUTERINC.:rnPN50-E1:rvrTobefilledbyO.E.M.:cvnDefaultstring:ct35:cvrDefaultstring:sku: dmi.product.family: Vivo PC dmi.product.name: MINIPC PN50-E1 dmi.product.version: 0405 dmi.sys.vendor: ASUSTeK COMPUTER INC. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: john 1682 F pulseaudio /dev/snd/controlC2: john 1682 F pulseaudio /dev/snd/controlC1: john 1682 F pulseaudio /dev/snd/controlC0: john 1682 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Dependencies: firmware-sof-signed 2.0-1ubuntu4.1 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-06-15 (12 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) MachineType: Micro Computer (HK) Tech Limited MC560 Package: linux-firmware 20220329.git681281e4-0ubuntu3.13 PackageArchitecture: all ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-45-generic root=UUID=ef5c33e1-311f-4fd6-ae66-aa6877e464df ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-45.46~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-45-generic N/A linux-backports-modules-5.19.0-45-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.13 Tags: wayland-session jammy Uname: Linux 5.19.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/07/2022 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC.
[Kernel-packages] [Bug 2022826] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/2022826/+attachment/5682465/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2022826 Title: Ethernet hangs Status in linux-firmware package in Ubuntu: New Bug description: I'm now getting my wired (i.e. Ethernet) connection hanging on trying to connect. I've tried switching ports (on the router) and using a different cable, but still the same. ifconfig shows for Ethernet: enp2s0: flags=4163 mtu 1500 ether 50:eb:f6:ef:a4:e6 txqueuelen 1000 (Ethernet) RX packets 2779 bytes 250524 (250.5 KB) RX errors 0 dropped 1 overruns 0 frame 0 TX packets 355 bytes 72171 (72.1 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 sudo lshw -C enp2s0 shows nothing lspci -nn shows for Ethernet: 02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller [10ec:8125] (rev 05) I found a web page: https://tutorialforlinux.com/2021/05...based-systems/ I followed the instructions and installed realtek-r8125-dkms package OK. On rebooting, I followed the instructed procedure (shown when installing the package) of creating a password and then entering it when requested on the reboot. But still same problem. Any ideas what to do? PS I've switched Wi-Fi on (though I'd prefer to use Ethernet, as my Wi-Fi is a little flaky due to walls) in order to post this question. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-firmware 20220329.git681281e4-0ubuntu3.13 ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Jun 3 07:29:15 2023 Dependencies: firmware-sof-signed 2.0-1ubuntu4.1 InstallationDate: Installed on 2022-08-21 (285 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: ASUSTeK COMPUTER INC. MINIPC PN50-E1 PackageArchitecture: all ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-43-generic root=UUID=1d99d177-09b2-43e7-b6c1-451d081353f8 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.19.0-43-generic N/A linux-backports-modules-5.19.0-43-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.13 SourcePackage: linux-firmware UpgradeStatus: Upgraded to jammy on 2022-10-06 (239 days ago) dmi.bios.date: 03/18/2021 dmi.bios.release: 4.5 dmi.bios.vendor: ASUSTeK COMPUTER INC. dmi.bios.version: 0405 dmi.board.asset.tag: Default string dmi.board.name: PN50-E1 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnASUSTeKCOMPUTERINC.:bvr0405:bd03/18/2021:br4.5:svnASUSTeKCOMPUTERINC.:pnMINIPCPN50-E1:pvr0405:rvnASUSTeKCOMPUTERINC.:rnPN50-E1:rvrTobefilledbyO.E.M.:cvnDefaultstring:ct35:cvrDefaultstring:sku: dmi.product.family: Vivo PC dmi.product.name: MINIPC PN50-E1 dmi.product.version: 0405 dmi.sys.vendor: ASUSTeK COMPUTER INC. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: john 1682 F pulseaudio /dev/snd/controlC2: john 1682 F pulseaudio /dev/snd/controlC1: john 1682 F pulseaudio /dev/snd/controlC0: john 1682 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Dependencies: firmware-sof-signed 2.0-1ubuntu4.1 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-06-15 (12 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) MachineType: Micro Computer (HK) Tech Limited MC560 Package: linux-firmware 20220329.git681281e4-0ubuntu3.13 PackageArchitecture: all ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-45-generic root=UUID=ef5c33e1-311f-4fd6-ae66-aa6877e464df ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-45.46~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-45-generic N/A linux-backports-modules-5.19.0-45-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.13 Tags: wayland-session jammy Uname: Linux 5.19.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/07/2022 dmi.bios.release: 5.19
[Kernel-packages] [Bug 2022826] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/2022826/+attachment/5682461/+files/PaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2022826 Title: Ethernet hangs Status in linux-firmware package in Ubuntu: New Bug description: I'm now getting my wired (i.e. Ethernet) connection hanging on trying to connect. I've tried switching ports (on the router) and using a different cable, but still the same. ifconfig shows for Ethernet: enp2s0: flags=4163 mtu 1500 ether 50:eb:f6:ef:a4:e6 txqueuelen 1000 (Ethernet) RX packets 2779 bytes 250524 (250.5 KB) RX errors 0 dropped 1 overruns 0 frame 0 TX packets 355 bytes 72171 (72.1 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 sudo lshw -C enp2s0 shows nothing lspci -nn shows for Ethernet: 02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller [10ec:8125] (rev 05) I found a web page: https://tutorialforlinux.com/2021/05...based-systems/ I followed the instructions and installed realtek-r8125-dkms package OK. On rebooting, I followed the instructed procedure (shown when installing the package) of creating a password and then entering it when requested on the reboot. But still same problem. Any ideas what to do? PS I've switched Wi-Fi on (though I'd prefer to use Ethernet, as my Wi-Fi is a little flaky due to walls) in order to post this question. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-firmware 20220329.git681281e4-0ubuntu3.13 ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Jun 3 07:29:15 2023 Dependencies: firmware-sof-signed 2.0-1ubuntu4.1 InstallationDate: Installed on 2022-08-21 (285 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: ASUSTeK COMPUTER INC. MINIPC PN50-E1 PackageArchitecture: all ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-43-generic root=UUID=1d99d177-09b2-43e7-b6c1-451d081353f8 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.19.0-43-generic N/A linux-backports-modules-5.19.0-43-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.13 SourcePackage: linux-firmware UpgradeStatus: Upgraded to jammy on 2022-10-06 (239 days ago) dmi.bios.date: 03/18/2021 dmi.bios.release: 4.5 dmi.bios.vendor: ASUSTeK COMPUTER INC. dmi.bios.version: 0405 dmi.board.asset.tag: Default string dmi.board.name: PN50-E1 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnASUSTeKCOMPUTERINC.:bvr0405:bd03/18/2021:br4.5:svnASUSTeKCOMPUTERINC.:pnMINIPCPN50-E1:pvr0405:rvnASUSTeKCOMPUTERINC.:rnPN50-E1:rvrTobefilledbyO.E.M.:cvnDefaultstring:ct35:cvrDefaultstring:sku: dmi.product.family: Vivo PC dmi.product.name: MINIPC PN50-E1 dmi.product.version: 0405 dmi.sys.vendor: ASUSTeK COMPUTER INC. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: john 1682 F pulseaudio /dev/snd/controlC2: john 1682 F pulseaudio /dev/snd/controlC1: john 1682 F pulseaudio /dev/snd/controlC0: john 1682 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Dependencies: firmware-sof-signed 2.0-1ubuntu4.1 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-06-15 (12 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) MachineType: Micro Computer (HK) Tech Limited MC560 Package: linux-firmware 20220329.git681281e4-0ubuntu3.13 PackageArchitecture: all ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-45-generic root=UUID=ef5c33e1-311f-4fd6-ae66-aa6877e464df ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-45.46~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-45-generic N/A linux-backports-modules-5.19.0-45-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.13 Tags: wayland-session jammy Uname: Linux 5.19.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/07/2022 dmi.bios.release: 5.19 dmi.bios.vendor: American
[Kernel-packages] [Bug 2022826] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/2022826/+attachment/5682463/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2022826 Title: Ethernet hangs Status in linux-firmware package in Ubuntu: New Bug description: I'm now getting my wired (i.e. Ethernet) connection hanging on trying to connect. I've tried switching ports (on the router) and using a different cable, but still the same. ifconfig shows for Ethernet: enp2s0: flags=4163 mtu 1500 ether 50:eb:f6:ef:a4:e6 txqueuelen 1000 (Ethernet) RX packets 2779 bytes 250524 (250.5 KB) RX errors 0 dropped 1 overruns 0 frame 0 TX packets 355 bytes 72171 (72.1 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 sudo lshw -C enp2s0 shows nothing lspci -nn shows for Ethernet: 02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller [10ec:8125] (rev 05) I found a web page: https://tutorialforlinux.com/2021/05...based-systems/ I followed the instructions and installed realtek-r8125-dkms package OK. On rebooting, I followed the instructed procedure (shown when installing the package) of creating a password and then entering it when requested on the reboot. But still same problem. Any ideas what to do? PS I've switched Wi-Fi on (though I'd prefer to use Ethernet, as my Wi-Fi is a little flaky due to walls) in order to post this question. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-firmware 20220329.git681281e4-0ubuntu3.13 ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Jun 3 07:29:15 2023 Dependencies: firmware-sof-signed 2.0-1ubuntu4.1 InstallationDate: Installed on 2022-08-21 (285 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: ASUSTeK COMPUTER INC. MINIPC PN50-E1 PackageArchitecture: all ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-43-generic root=UUID=1d99d177-09b2-43e7-b6c1-451d081353f8 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.19.0-43-generic N/A linux-backports-modules-5.19.0-43-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.13 SourcePackage: linux-firmware UpgradeStatus: Upgraded to jammy on 2022-10-06 (239 days ago) dmi.bios.date: 03/18/2021 dmi.bios.release: 4.5 dmi.bios.vendor: ASUSTeK COMPUTER INC. dmi.bios.version: 0405 dmi.board.asset.tag: Default string dmi.board.name: PN50-E1 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnASUSTeKCOMPUTERINC.:bvr0405:bd03/18/2021:br4.5:svnASUSTeKCOMPUTERINC.:pnMINIPCPN50-E1:pvr0405:rvnASUSTeKCOMPUTERINC.:rnPN50-E1:rvrTobefilledbyO.E.M.:cvnDefaultstring:ct35:cvrDefaultstring:sku: dmi.product.family: Vivo PC dmi.product.name: MINIPC PN50-E1 dmi.product.version: 0405 dmi.sys.vendor: ASUSTeK COMPUTER INC. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: john 1682 F pulseaudio /dev/snd/controlC2: john 1682 F pulseaudio /dev/snd/controlC1: john 1682 F pulseaudio /dev/snd/controlC0: john 1682 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Dependencies: firmware-sof-signed 2.0-1ubuntu4.1 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-06-15 (12 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) MachineType: Micro Computer (HK) Tech Limited MC560 Package: linux-firmware 20220329.git681281e4-0ubuntu3.13 PackageArchitecture: all ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-45-generic root=UUID=ef5c33e1-311f-4fd6-ae66-aa6877e464df ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-45.46~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-45-generic N/A linux-backports-modules-5.19.0-45-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.13 Tags: wayland-session jammy Uname: Linux 5.19.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/07/2022 dmi.bios.release: 5.19
[Kernel-packages] [Bug 2022826] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/2022826/+attachment/5682464/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2022826 Title: Ethernet hangs Status in linux-firmware package in Ubuntu: New Bug description: I'm now getting my wired (i.e. Ethernet) connection hanging on trying to connect. I've tried switching ports (on the router) and using a different cable, but still the same. ifconfig shows for Ethernet: enp2s0: flags=4163 mtu 1500 ether 50:eb:f6:ef:a4:e6 txqueuelen 1000 (Ethernet) RX packets 2779 bytes 250524 (250.5 KB) RX errors 0 dropped 1 overruns 0 frame 0 TX packets 355 bytes 72171 (72.1 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 sudo lshw -C enp2s0 shows nothing lspci -nn shows for Ethernet: 02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller [10ec:8125] (rev 05) I found a web page: https://tutorialforlinux.com/2021/05...based-systems/ I followed the instructions and installed realtek-r8125-dkms package OK. On rebooting, I followed the instructed procedure (shown when installing the package) of creating a password and then entering it when requested on the reboot. But still same problem. Any ideas what to do? PS I've switched Wi-Fi on (though I'd prefer to use Ethernet, as my Wi-Fi is a little flaky due to walls) in order to post this question. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-firmware 20220329.git681281e4-0ubuntu3.13 ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Jun 3 07:29:15 2023 Dependencies: firmware-sof-signed 2.0-1ubuntu4.1 InstallationDate: Installed on 2022-08-21 (285 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: ASUSTeK COMPUTER INC. MINIPC PN50-E1 PackageArchitecture: all ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-43-generic root=UUID=1d99d177-09b2-43e7-b6c1-451d081353f8 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.19.0-43-generic N/A linux-backports-modules-5.19.0-43-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.13 SourcePackage: linux-firmware UpgradeStatus: Upgraded to jammy on 2022-10-06 (239 days ago) dmi.bios.date: 03/18/2021 dmi.bios.release: 4.5 dmi.bios.vendor: ASUSTeK COMPUTER INC. dmi.bios.version: 0405 dmi.board.asset.tag: Default string dmi.board.name: PN50-E1 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnASUSTeKCOMPUTERINC.:bvr0405:bd03/18/2021:br4.5:svnASUSTeKCOMPUTERINC.:pnMINIPCPN50-E1:pvr0405:rvnASUSTeKCOMPUTERINC.:rnPN50-E1:rvrTobefilledbyO.E.M.:cvnDefaultstring:ct35:cvrDefaultstring:sku: dmi.product.family: Vivo PC dmi.product.name: MINIPC PN50-E1 dmi.product.version: 0405 dmi.sys.vendor: ASUSTeK COMPUTER INC. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: john 1682 F pulseaudio /dev/snd/controlC2: john 1682 F pulseaudio /dev/snd/controlC1: john 1682 F pulseaudio /dev/snd/controlC0: john 1682 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Dependencies: firmware-sof-signed 2.0-1ubuntu4.1 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-06-15 (12 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) MachineType: Micro Computer (HK) Tech Limited MC560 Package: linux-firmware 20220329.git681281e4-0ubuntu3.13 PackageArchitecture: all ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-45-generic root=UUID=ef5c33e1-311f-4fd6-ae66-aa6877e464df ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-45.46~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-45-generic N/A linux-backports-modules-5.19.0-45-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.13 Tags: wayland-session jammy Uname: Linux 5.19.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/07/2022 dmi.bios.release: 5.19 dmi.bios.vendor:
[Kernel-packages] [Bug 2022826] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/2022826/+attachment/5682462/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2022826 Title: Ethernet hangs Status in linux-firmware package in Ubuntu: New Bug description: I'm now getting my wired (i.e. Ethernet) connection hanging on trying to connect. I've tried switching ports (on the router) and using a different cable, but still the same. ifconfig shows for Ethernet: enp2s0: flags=4163 mtu 1500 ether 50:eb:f6:ef:a4:e6 txqueuelen 1000 (Ethernet) RX packets 2779 bytes 250524 (250.5 KB) RX errors 0 dropped 1 overruns 0 frame 0 TX packets 355 bytes 72171 (72.1 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 sudo lshw -C enp2s0 shows nothing lspci -nn shows for Ethernet: 02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller [10ec:8125] (rev 05) I found a web page: https://tutorialforlinux.com/2021/05...based-systems/ I followed the instructions and installed realtek-r8125-dkms package OK. On rebooting, I followed the instructed procedure (shown when installing the package) of creating a password and then entering it when requested on the reboot. But still same problem. Any ideas what to do? PS I've switched Wi-Fi on (though I'd prefer to use Ethernet, as my Wi-Fi is a little flaky due to walls) in order to post this question. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-firmware 20220329.git681281e4-0ubuntu3.13 ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Jun 3 07:29:15 2023 Dependencies: firmware-sof-signed 2.0-1ubuntu4.1 InstallationDate: Installed on 2022-08-21 (285 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: ASUSTeK COMPUTER INC. MINIPC PN50-E1 PackageArchitecture: all ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-43-generic root=UUID=1d99d177-09b2-43e7-b6c1-451d081353f8 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.19.0-43-generic N/A linux-backports-modules-5.19.0-43-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.13 SourcePackage: linux-firmware UpgradeStatus: Upgraded to jammy on 2022-10-06 (239 days ago) dmi.bios.date: 03/18/2021 dmi.bios.release: 4.5 dmi.bios.vendor: ASUSTeK COMPUTER INC. dmi.bios.version: 0405 dmi.board.asset.tag: Default string dmi.board.name: PN50-E1 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnASUSTeKCOMPUTERINC.:bvr0405:bd03/18/2021:br4.5:svnASUSTeKCOMPUTERINC.:pnMINIPCPN50-E1:pvr0405:rvnASUSTeKCOMPUTERINC.:rnPN50-E1:rvrTobefilledbyO.E.M.:cvnDefaultstring:ct35:cvrDefaultstring:sku: dmi.product.family: Vivo PC dmi.product.name: MINIPC PN50-E1 dmi.product.version: 0405 dmi.sys.vendor: ASUSTeK COMPUTER INC. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: john 1682 F pulseaudio /dev/snd/controlC2: john 1682 F pulseaudio /dev/snd/controlC1: john 1682 F pulseaudio /dev/snd/controlC0: john 1682 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Dependencies: firmware-sof-signed 2.0-1ubuntu4.1 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-06-15 (12 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) MachineType: Micro Computer (HK) Tech Limited MC560 Package: linux-firmware 20220329.git681281e4-0ubuntu3.13 PackageArchitecture: all ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-45-generic root=UUID=ef5c33e1-311f-4fd6-ae66-aa6877e464df ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-45.46~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-45-generic N/A linux-backports-modules-5.19.0-45-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.13 Tags: wayland-session jammy Uname: Linux 5.19.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/07/2022 dmi.bios.release: 5.19 dmi.bios.vendor:
[Kernel-packages] [Bug 2022826] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/2022826/+attachment/5682460/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2022826 Title: Ethernet hangs Status in linux-firmware package in Ubuntu: New Bug description: I'm now getting my wired (i.e. Ethernet) connection hanging on trying to connect. I've tried switching ports (on the router) and using a different cable, but still the same. ifconfig shows for Ethernet: enp2s0: flags=4163 mtu 1500 ether 50:eb:f6:ef:a4:e6 txqueuelen 1000 (Ethernet) RX packets 2779 bytes 250524 (250.5 KB) RX errors 0 dropped 1 overruns 0 frame 0 TX packets 355 bytes 72171 (72.1 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 sudo lshw -C enp2s0 shows nothing lspci -nn shows for Ethernet: 02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller [10ec:8125] (rev 05) I found a web page: https://tutorialforlinux.com/2021/05...based-systems/ I followed the instructions and installed realtek-r8125-dkms package OK. On rebooting, I followed the instructed procedure (shown when installing the package) of creating a password and then entering it when requested on the reboot. But still same problem. Any ideas what to do? PS I've switched Wi-Fi on (though I'd prefer to use Ethernet, as my Wi-Fi is a little flaky due to walls) in order to post this question. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-firmware 20220329.git681281e4-0ubuntu3.13 ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Jun 3 07:29:15 2023 Dependencies: firmware-sof-signed 2.0-1ubuntu4.1 InstallationDate: Installed on 2022-08-21 (285 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: ASUSTeK COMPUTER INC. MINIPC PN50-E1 PackageArchitecture: all ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-43-generic root=UUID=1d99d177-09b2-43e7-b6c1-451d081353f8 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.19.0-43-generic N/A linux-backports-modules-5.19.0-43-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.13 SourcePackage: linux-firmware UpgradeStatus: Upgraded to jammy on 2022-10-06 (239 days ago) dmi.bios.date: 03/18/2021 dmi.bios.release: 4.5 dmi.bios.vendor: ASUSTeK COMPUTER INC. dmi.bios.version: 0405 dmi.board.asset.tag: Default string dmi.board.name: PN50-E1 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnASUSTeKCOMPUTERINC.:bvr0405:bd03/18/2021:br4.5:svnASUSTeKCOMPUTERINC.:pnMINIPCPN50-E1:pvr0405:rvnASUSTeKCOMPUTERINC.:rnPN50-E1:rvrTobefilledbyO.E.M.:cvnDefaultstring:ct35:cvrDefaultstring:sku: dmi.product.family: Vivo PC dmi.product.name: MINIPC PN50-E1 dmi.product.version: 0405 dmi.sys.vendor: ASUSTeK COMPUTER INC. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: john 1682 F pulseaudio /dev/snd/controlC2: john 1682 F pulseaudio /dev/snd/controlC1: john 1682 F pulseaudio /dev/snd/controlC0: john 1682 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Dependencies: firmware-sof-signed 2.0-1ubuntu4.1 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-06-15 (12 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) MachineType: Micro Computer (HK) Tech Limited MC560 Package: linux-firmware 20220329.git681281e4-0ubuntu3.13 PackageArchitecture: all ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-45-generic root=UUID=ef5c33e1-311f-4fd6-ae66-aa6877e464df ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-45.46~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-45-generic N/A linux-backports-modules-5.19.0-45-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.13 Tags: wayland-session jammy Uname: Linux 5.19.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/07/2022 dmi.bios.release: 5.19 dmi.bios.vendor: American
[Kernel-packages] [Bug 2022826] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/2022826/+attachment/5682459/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2022826 Title: Ethernet hangs Status in linux-firmware package in Ubuntu: New Bug description: I'm now getting my wired (i.e. Ethernet) connection hanging on trying to connect. I've tried switching ports (on the router) and using a different cable, but still the same. ifconfig shows for Ethernet: enp2s0: flags=4163 mtu 1500 ether 50:eb:f6:ef:a4:e6 txqueuelen 1000 (Ethernet) RX packets 2779 bytes 250524 (250.5 KB) RX errors 0 dropped 1 overruns 0 frame 0 TX packets 355 bytes 72171 (72.1 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 sudo lshw -C enp2s0 shows nothing lspci -nn shows for Ethernet: 02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller [10ec:8125] (rev 05) I found a web page: https://tutorialforlinux.com/2021/05...based-systems/ I followed the instructions and installed realtek-r8125-dkms package OK. On rebooting, I followed the instructed procedure (shown when installing the package) of creating a password and then entering it when requested on the reboot. But still same problem. Any ideas what to do? PS I've switched Wi-Fi on (though I'd prefer to use Ethernet, as my Wi-Fi is a little flaky due to walls) in order to post this question. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-firmware 20220329.git681281e4-0ubuntu3.13 ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Jun 3 07:29:15 2023 Dependencies: firmware-sof-signed 2.0-1ubuntu4.1 InstallationDate: Installed on 2022-08-21 (285 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: ASUSTeK COMPUTER INC. MINIPC PN50-E1 PackageArchitecture: all ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-43-generic root=UUID=1d99d177-09b2-43e7-b6c1-451d081353f8 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.19.0-43-generic N/A linux-backports-modules-5.19.0-43-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.13 SourcePackage: linux-firmware UpgradeStatus: Upgraded to jammy on 2022-10-06 (239 days ago) dmi.bios.date: 03/18/2021 dmi.bios.release: 4.5 dmi.bios.vendor: ASUSTeK COMPUTER INC. dmi.bios.version: 0405 dmi.board.asset.tag: Default string dmi.board.name: PN50-E1 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnASUSTeKCOMPUTERINC.:bvr0405:bd03/18/2021:br4.5:svnASUSTeKCOMPUTERINC.:pnMINIPCPN50-E1:pvr0405:rvnASUSTeKCOMPUTERINC.:rnPN50-E1:rvrTobefilledbyO.E.M.:cvnDefaultstring:ct35:cvrDefaultstring:sku: dmi.product.family: Vivo PC dmi.product.name: MINIPC PN50-E1 dmi.product.version: 0405 dmi.sys.vendor: ASUSTeK COMPUTER INC. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: john 1682 F pulseaudio /dev/snd/controlC2: john 1682 F pulseaudio /dev/snd/controlC1: john 1682 F pulseaudio /dev/snd/controlC0: john 1682 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Dependencies: firmware-sof-signed 2.0-1ubuntu4.1 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-06-15 (12 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) MachineType: Micro Computer (HK) Tech Limited MC560 Package: linux-firmware 20220329.git681281e4-0ubuntu3.13 PackageArchitecture: all ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-45-generic root=UUID=ef5c33e1-311f-4fd6-ae66-aa6877e464df ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-45.46~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-45-generic N/A linux-backports-modules-5.19.0-45-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.13 Tags: wayland-session jammy Uname: Linux 5.19.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/07/2022 dmi.bios.release: 5.19 dmi.bios.vendor: American
[Kernel-packages] [Bug 2022826] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/2022826/+attachment/5682456/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2022826 Title: Ethernet hangs Status in linux-firmware package in Ubuntu: New Bug description: I'm now getting my wired (i.e. Ethernet) connection hanging on trying to connect. I've tried switching ports (on the router) and using a different cable, but still the same. ifconfig shows for Ethernet: enp2s0: flags=4163 mtu 1500 ether 50:eb:f6:ef:a4:e6 txqueuelen 1000 (Ethernet) RX packets 2779 bytes 250524 (250.5 KB) RX errors 0 dropped 1 overruns 0 frame 0 TX packets 355 bytes 72171 (72.1 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 sudo lshw -C enp2s0 shows nothing lspci -nn shows for Ethernet: 02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller [10ec:8125] (rev 05) I found a web page: https://tutorialforlinux.com/2021/05...based-systems/ I followed the instructions and installed realtek-r8125-dkms package OK. On rebooting, I followed the instructed procedure (shown when installing the package) of creating a password and then entering it when requested on the reboot. But still same problem. Any ideas what to do? PS I've switched Wi-Fi on (though I'd prefer to use Ethernet, as my Wi-Fi is a little flaky due to walls) in order to post this question. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-firmware 20220329.git681281e4-0ubuntu3.13 ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Jun 3 07:29:15 2023 Dependencies: firmware-sof-signed 2.0-1ubuntu4.1 InstallationDate: Installed on 2022-08-21 (285 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: ASUSTeK COMPUTER INC. MINIPC PN50-E1 PackageArchitecture: all ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-43-generic root=UUID=1d99d177-09b2-43e7-b6c1-451d081353f8 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.19.0-43-generic N/A linux-backports-modules-5.19.0-43-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.13 SourcePackage: linux-firmware UpgradeStatus: Upgraded to jammy on 2022-10-06 (239 days ago) dmi.bios.date: 03/18/2021 dmi.bios.release: 4.5 dmi.bios.vendor: ASUSTeK COMPUTER INC. dmi.bios.version: 0405 dmi.board.asset.tag: Default string dmi.board.name: PN50-E1 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnASUSTeKCOMPUTERINC.:bvr0405:bd03/18/2021:br4.5:svnASUSTeKCOMPUTERINC.:pnMINIPCPN50-E1:pvr0405:rvnASUSTeKCOMPUTERINC.:rnPN50-E1:rvrTobefilledbyO.E.M.:cvnDefaultstring:ct35:cvrDefaultstring:sku: dmi.product.family: Vivo PC dmi.product.name: MINIPC PN50-E1 dmi.product.version: 0405 dmi.sys.vendor: ASUSTeK COMPUTER INC. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: john 1682 F pulseaudio /dev/snd/controlC2: john 1682 F pulseaudio /dev/snd/controlC1: john 1682 F pulseaudio /dev/snd/controlC0: john 1682 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Dependencies: firmware-sof-signed 2.0-1ubuntu4.1 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-06-15 (12 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) MachineType: Micro Computer (HK) Tech Limited MC560 Package: linux-firmware 20220329.git681281e4-0ubuntu3.13 PackageArchitecture: all ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-45-generic root=UUID=ef5c33e1-311f-4fd6-ae66-aa6877e464df ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-45.46~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-45-generic N/A linux-backports-modules-5.19.0-45-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.13 Tags: wayland-session jammy Uname: Linux 5.19.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/07/2022 dmi.bios.release: 5.19 dmi.bios.vendor: American
[Kernel-packages] [Bug 2022826] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/2022826/+attachment/5682458/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2022826 Title: Ethernet hangs Status in linux-firmware package in Ubuntu: New Bug description: I'm now getting my wired (i.e. Ethernet) connection hanging on trying to connect. I've tried switching ports (on the router) and using a different cable, but still the same. ifconfig shows for Ethernet: enp2s0: flags=4163 mtu 1500 ether 50:eb:f6:ef:a4:e6 txqueuelen 1000 (Ethernet) RX packets 2779 bytes 250524 (250.5 KB) RX errors 0 dropped 1 overruns 0 frame 0 TX packets 355 bytes 72171 (72.1 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 sudo lshw -C enp2s0 shows nothing lspci -nn shows for Ethernet: 02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller [10ec:8125] (rev 05) I found a web page: https://tutorialforlinux.com/2021/05...based-systems/ I followed the instructions and installed realtek-r8125-dkms package OK. On rebooting, I followed the instructed procedure (shown when installing the package) of creating a password and then entering it when requested on the reboot. But still same problem. Any ideas what to do? PS I've switched Wi-Fi on (though I'd prefer to use Ethernet, as my Wi-Fi is a little flaky due to walls) in order to post this question. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-firmware 20220329.git681281e4-0ubuntu3.13 ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Jun 3 07:29:15 2023 Dependencies: firmware-sof-signed 2.0-1ubuntu4.1 InstallationDate: Installed on 2022-08-21 (285 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: ASUSTeK COMPUTER INC. MINIPC PN50-E1 PackageArchitecture: all ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-43-generic root=UUID=1d99d177-09b2-43e7-b6c1-451d081353f8 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.19.0-43-generic N/A linux-backports-modules-5.19.0-43-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.13 SourcePackage: linux-firmware UpgradeStatus: Upgraded to jammy on 2022-10-06 (239 days ago) dmi.bios.date: 03/18/2021 dmi.bios.release: 4.5 dmi.bios.vendor: ASUSTeK COMPUTER INC. dmi.bios.version: 0405 dmi.board.asset.tag: Default string dmi.board.name: PN50-E1 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnASUSTeKCOMPUTERINC.:bvr0405:bd03/18/2021:br4.5:svnASUSTeKCOMPUTERINC.:pnMINIPCPN50-E1:pvr0405:rvnASUSTeKCOMPUTERINC.:rnPN50-E1:rvrTobefilledbyO.E.M.:cvnDefaultstring:ct35:cvrDefaultstring:sku: dmi.product.family: Vivo PC dmi.product.name: MINIPC PN50-E1 dmi.product.version: 0405 dmi.sys.vendor: ASUSTeK COMPUTER INC. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: john 1682 F pulseaudio /dev/snd/controlC2: john 1682 F pulseaudio /dev/snd/controlC1: john 1682 F pulseaudio /dev/snd/controlC0: john 1682 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Dependencies: firmware-sof-signed 2.0-1ubuntu4.1 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-06-15 (12 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) MachineType: Micro Computer (HK) Tech Limited MC560 Package: linux-firmware 20220329.git681281e4-0ubuntu3.13 PackageArchitecture: all ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-45-generic root=UUID=ef5c33e1-311f-4fd6-ae66-aa6877e464df ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-45.46~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-45-generic N/A linux-backports-modules-5.19.0-45-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.13 Tags: wayland-session jammy Uname: Linux 5.19.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/07/2022 dmi.bios.release: 5.19 dmi.bios.vendor: American
[Kernel-packages] [Bug 2022826] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/2022826/+attachment/5682457/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2022826 Title: Ethernet hangs Status in linux-firmware package in Ubuntu: New Bug description: I'm now getting my wired (i.e. Ethernet) connection hanging on trying to connect. I've tried switching ports (on the router) and using a different cable, but still the same. ifconfig shows for Ethernet: enp2s0: flags=4163 mtu 1500 ether 50:eb:f6:ef:a4:e6 txqueuelen 1000 (Ethernet) RX packets 2779 bytes 250524 (250.5 KB) RX errors 0 dropped 1 overruns 0 frame 0 TX packets 355 bytes 72171 (72.1 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 sudo lshw -C enp2s0 shows nothing lspci -nn shows for Ethernet: 02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller [10ec:8125] (rev 05) I found a web page: https://tutorialforlinux.com/2021/05...based-systems/ I followed the instructions and installed realtek-r8125-dkms package OK. On rebooting, I followed the instructed procedure (shown when installing the package) of creating a password and then entering it when requested on the reboot. But still same problem. Any ideas what to do? PS I've switched Wi-Fi on (though I'd prefer to use Ethernet, as my Wi-Fi is a little flaky due to walls) in order to post this question. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-firmware 20220329.git681281e4-0ubuntu3.13 ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Jun 3 07:29:15 2023 Dependencies: firmware-sof-signed 2.0-1ubuntu4.1 InstallationDate: Installed on 2022-08-21 (285 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: ASUSTeK COMPUTER INC. MINIPC PN50-E1 PackageArchitecture: all ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-43-generic root=UUID=1d99d177-09b2-43e7-b6c1-451d081353f8 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.19.0-43-generic N/A linux-backports-modules-5.19.0-43-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.13 SourcePackage: linux-firmware UpgradeStatus: Upgraded to jammy on 2022-10-06 (239 days ago) dmi.bios.date: 03/18/2021 dmi.bios.release: 4.5 dmi.bios.vendor: ASUSTeK COMPUTER INC. dmi.bios.version: 0405 dmi.board.asset.tag: Default string dmi.board.name: PN50-E1 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnASUSTeKCOMPUTERINC.:bvr0405:bd03/18/2021:br4.5:svnASUSTeKCOMPUTERINC.:pnMINIPCPN50-E1:pvr0405:rvnASUSTeKCOMPUTERINC.:rnPN50-E1:rvrTobefilledbyO.E.M.:cvnDefaultstring:ct35:cvrDefaultstring:sku: dmi.product.family: Vivo PC dmi.product.name: MINIPC PN50-E1 dmi.product.version: 0405 dmi.sys.vendor: ASUSTeK COMPUTER INC. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: john 1682 F pulseaudio /dev/snd/controlC2: john 1682 F pulseaudio /dev/snd/controlC1: john 1682 F pulseaudio /dev/snd/controlC0: john 1682 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Dependencies: firmware-sof-signed 2.0-1ubuntu4.1 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-06-15 (12 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) MachineType: Micro Computer (HK) Tech Limited MC560 Package: linux-firmware 20220329.git681281e4-0ubuntu3.13 PackageArchitecture: all ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-45-generic root=UUID=ef5c33e1-311f-4fd6-ae66-aa6877e464df ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-45.46~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-45-generic N/A linux-backports-modules-5.19.0-45-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.13 Tags: wayland-session jammy Uname: Linux 5.19.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/07/2022 dmi.bios.release: 5.19 dmi.bios.vendor: American
[Kernel-packages] [Bug 2022826] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/2022826/+attachment/5682455/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2022826 Title: Ethernet hangs Status in linux-firmware package in Ubuntu: New Bug description: I'm now getting my wired (i.e. Ethernet) connection hanging on trying to connect. I've tried switching ports (on the router) and using a different cable, but still the same. ifconfig shows for Ethernet: enp2s0: flags=4163 mtu 1500 ether 50:eb:f6:ef:a4:e6 txqueuelen 1000 (Ethernet) RX packets 2779 bytes 250524 (250.5 KB) RX errors 0 dropped 1 overruns 0 frame 0 TX packets 355 bytes 72171 (72.1 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 sudo lshw -C enp2s0 shows nothing lspci -nn shows for Ethernet: 02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller [10ec:8125] (rev 05) I found a web page: https://tutorialforlinux.com/2021/05...based-systems/ I followed the instructions and installed realtek-r8125-dkms package OK. On rebooting, I followed the instructed procedure (shown when installing the package) of creating a password and then entering it when requested on the reboot. But still same problem. Any ideas what to do? PS I've switched Wi-Fi on (though I'd prefer to use Ethernet, as my Wi-Fi is a little flaky due to walls) in order to post this question. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-firmware 20220329.git681281e4-0ubuntu3.13 ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Jun 3 07:29:15 2023 Dependencies: firmware-sof-signed 2.0-1ubuntu4.1 InstallationDate: Installed on 2022-08-21 (285 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: ASUSTeK COMPUTER INC. MINIPC PN50-E1 PackageArchitecture: all ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-43-generic root=UUID=1d99d177-09b2-43e7-b6c1-451d081353f8 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.19.0-43-generic N/A linux-backports-modules-5.19.0-43-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.13 SourcePackage: linux-firmware UpgradeStatus: Upgraded to jammy on 2022-10-06 (239 days ago) dmi.bios.date: 03/18/2021 dmi.bios.release: 4.5 dmi.bios.vendor: ASUSTeK COMPUTER INC. dmi.bios.version: 0405 dmi.board.asset.tag: Default string dmi.board.name: PN50-E1 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnASUSTeKCOMPUTERINC.:bvr0405:bd03/18/2021:br4.5:svnASUSTeKCOMPUTERINC.:pnMINIPCPN50-E1:pvr0405:rvnASUSTeKCOMPUTERINC.:rnPN50-E1:rvrTobefilledbyO.E.M.:cvnDefaultstring:ct35:cvrDefaultstring:sku: dmi.product.family: Vivo PC dmi.product.name: MINIPC PN50-E1 dmi.product.version: 0405 dmi.sys.vendor: ASUSTeK COMPUTER INC. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: john 1682 F pulseaudio /dev/snd/controlC2: john 1682 F pulseaudio /dev/snd/controlC1: john 1682 F pulseaudio /dev/snd/controlC0: john 1682 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Dependencies: firmware-sof-signed 2.0-1ubuntu4.1 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-06-15 (12 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) MachineType: Micro Computer (HK) Tech Limited MC560 Package: linux-firmware 20220329.git681281e4-0ubuntu3.13 PackageArchitecture: all ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-45-generic root=UUID=ef5c33e1-311f-4fd6-ae66-aa6877e464df ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-45.46~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-45-generic N/A linux-backports-modules-5.19.0-45-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.13 Tags: wayland-session jammy Uname: Linux 5.19.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/07/2022 dmi.bios.release: 5.19 dmi.bios.vendor: American
[Kernel-packages] [Bug 2022826] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/2022826/+attachment/5682454/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2022826 Title: Ethernet hangs Status in linux-firmware package in Ubuntu: New Bug description: I'm now getting my wired (i.e. Ethernet) connection hanging on trying to connect. I've tried switching ports (on the router) and using a different cable, but still the same. ifconfig shows for Ethernet: enp2s0: flags=4163 mtu 1500 ether 50:eb:f6:ef:a4:e6 txqueuelen 1000 (Ethernet) RX packets 2779 bytes 250524 (250.5 KB) RX errors 0 dropped 1 overruns 0 frame 0 TX packets 355 bytes 72171 (72.1 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 sudo lshw -C enp2s0 shows nothing lspci -nn shows for Ethernet: 02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller [10ec:8125] (rev 05) I found a web page: https://tutorialforlinux.com/2021/05...based-systems/ I followed the instructions and installed realtek-r8125-dkms package OK. On rebooting, I followed the instructed procedure (shown when installing the package) of creating a password and then entering it when requested on the reboot. But still same problem. Any ideas what to do? PS I've switched Wi-Fi on (though I'd prefer to use Ethernet, as my Wi-Fi is a little flaky due to walls) in order to post this question. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-firmware 20220329.git681281e4-0ubuntu3.13 ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Jun 3 07:29:15 2023 Dependencies: firmware-sof-signed 2.0-1ubuntu4.1 InstallationDate: Installed on 2022-08-21 (285 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: ASUSTeK COMPUTER INC. MINIPC PN50-E1 PackageArchitecture: all ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-43-generic root=UUID=1d99d177-09b2-43e7-b6c1-451d081353f8 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.19.0-43-generic N/A linux-backports-modules-5.19.0-43-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.13 SourcePackage: linux-firmware UpgradeStatus: Upgraded to jammy on 2022-10-06 (239 days ago) dmi.bios.date: 03/18/2021 dmi.bios.release: 4.5 dmi.bios.vendor: ASUSTeK COMPUTER INC. dmi.bios.version: 0405 dmi.board.asset.tag: Default string dmi.board.name: PN50-E1 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnASUSTeKCOMPUTERINC.:bvr0405:bd03/18/2021:br4.5:svnASUSTeKCOMPUTERINC.:pnMINIPCPN50-E1:pvr0405:rvnASUSTeKCOMPUTERINC.:rnPN50-E1:rvrTobefilledbyO.E.M.:cvnDefaultstring:ct35:cvrDefaultstring:sku: dmi.product.family: Vivo PC dmi.product.name: MINIPC PN50-E1 dmi.product.version: 0405 dmi.sys.vendor: ASUSTeK COMPUTER INC. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: john 1682 F pulseaudio /dev/snd/controlC2: john 1682 F pulseaudio /dev/snd/controlC1: john 1682 F pulseaudio /dev/snd/controlC0: john 1682 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Dependencies: firmware-sof-signed 2.0-1ubuntu4.1 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-06-15 (12 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) MachineType: Micro Computer (HK) Tech Limited MC560 Package: linux-firmware 20220329.git681281e4-0ubuntu3.13 PackageArchitecture: all ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-45-generic root=UUID=ef5c33e1-311f-4fd6-ae66-aa6877e464df ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-45.46~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-45-generic N/A linux-backports-modules-5.19.0-45-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.13 Tags: wayland-session jammy Uname: Linux 5.19.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/07/2022 dmi.bios.release: 5.19 dmi.bios.vendor:
[Kernel-packages] [Bug 2022826] Re: Ethernet hangs
apport information ** Tags added: apport-collected ** Description changed: I'm now getting my wired (i.e. Ethernet) connection hanging on trying to connect. I've tried switching ports (on the router) and using a different cable, but still the same. ifconfig shows for Ethernet: enp2s0: flags=4163 mtu 1500 ether 50:eb:f6:ef:a4:e6 txqueuelen 1000 (Ethernet) RX packets 2779 bytes 250524 (250.5 KB) RX errors 0 dropped 1 overruns 0 frame 0 TX packets 355 bytes 72171 (72.1 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 sudo lshw -C enp2s0 shows nothing lspci -nn shows for Ethernet: 02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller [10ec:8125] (rev 05) I found a web page: https://tutorialforlinux.com/2021/05...based-systems/ I followed the instructions and installed realtek-r8125-dkms package OK. On rebooting, I followed the instructed procedure (shown when installing the package) of creating a password and then entering it when requested on the reboot. But still same problem. Any ideas what to do? PS I've switched Wi-Fi on (though I'd prefer to use Ethernet, as my Wi-Fi is a little flaky due to walls) in order to post this question. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-firmware 20220329.git681281e4-0ubuntu3.13 ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Jun 3 07:29:15 2023 Dependencies: firmware-sof-signed 2.0-1ubuntu4.1 InstallationDate: Installed on 2022-08-21 (285 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: ASUSTeK COMPUTER INC. MINIPC PN50-E1 PackageArchitecture: all ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-43-generic root=UUID=1d99d177-09b2-43e7-b6c1-451d081353f8 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.19.0-43-generic N/A linux-backports-modules-5.19.0-43-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.13 SourcePackage: linux-firmware UpgradeStatus: Upgraded to jammy on 2022-10-06 (239 days ago) dmi.bios.date: 03/18/2021 dmi.bios.release: 4.5 dmi.bios.vendor: ASUSTeK COMPUTER INC. dmi.bios.version: 0405 dmi.board.asset.tag: Default string dmi.board.name: PN50-E1 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnASUSTeKCOMPUTERINC.:bvr0405:bd03/18/2021:br4.5:svnASUSTeKCOMPUTERINC.:pnMINIPCPN50-E1:pvr0405:rvnASUSTeKCOMPUTERINC.:rnPN50-E1:rvrTobefilledbyO.E.M.:cvnDefaultstring:ct35:cvrDefaultstring:sku: dmi.product.family: Vivo PC dmi.product.name: MINIPC PN50-E1 dmi.product.version: 0405 dmi.sys.vendor: ASUSTeK COMPUTER INC. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu82.5 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC3: john 1682 F pulseaudio + /dev/snd/controlC2: john 1682 F pulseaudio + /dev/snd/controlC1: john 1682 F pulseaudio + /dev/snd/controlC0: john 1682 F pulseaudio + CRDA: N/A + CasperMD5CheckResult: pass + CurrentDesktop: ubuntu:GNOME + Dependencies: firmware-sof-signed 2.0-1ubuntu4.1 + DistroRelease: Ubuntu 22.04 + InstallationDate: Installed on 2023-06-15 (12 days ago) + InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) + MachineType: Micro Computer (HK) Tech Limited MC560 + Package: linux-firmware 20220329.git681281e4-0ubuntu3.13 + PackageArchitecture: all + ProcFB: 0 amdgpudrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-45-generic root=UUID=ef5c33e1-311f-4fd6-ae66-aa6877e464df ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 5.19.0-45.46~22.04.1-generic 5.19.17 + RelatedPackageVersions: + linux-restricted-modules-5.19.0-45-generic N/A + linux-backports-modules-5.19.0-45-generic N/A + linux-firmware 20220329.git681281e4-0ubuntu3.13 + Tags: wayland-session jammy + Uname: Linux 5.19.0-45-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 11/07/2022 + dmi.bios.release: 5.19 + dmi.bios.vendor: American Megatrends International, LLC. + dmi.bios.version: 5.05 + dmi.board.asset.tag: Default string + dmi.board.name: F6CQW + dmi.board.vendor: Shenzhen Meigao Electronic Equipment Co.,Ltd + dmi.board.version: Default string + dmi.chassis.asset.tag: Default string + dmi.chassis.type: 3 + dmi.chassis.vendor: Default string +
[Kernel-packages] [Bug 2025120] Re: 6.3.0-7-generic can't boot on Intel NUC 12 Extreme
And 6.3.0-7 is working again today. So this is indeed an intermittent crash. ** Summary changed: - 6.3.0-7-generic can't boot on Intel NUC 12 Extreme + Crash in ucsi_acpi_async_write [ucsi_acpi] occasionally prevents booting -- 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/2025120 Title: Crash in ucsi_acpi_async_write [ucsi_acpi] occasionally prevents booting Status in linux package in Ubuntu: New Bug description: 6.3.0-7-generic can't boot on Intel NUC 12 Extreme Weirdly this only started today. Yesterday the same kernel would boot. Looks like it keeps crashing in ucsi_acpi/typec_ucsi but I can't tell if that is fatal. Booting with 6.2.0-21-generic still works. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2025120/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1810546] Re: AMDGPU VMC page fault with Athlon 200GE APU
I'm getting same on new AMD Ryzen 3270U with Ubuntu 22.04. -- 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/1810546 Title: AMDGPU VMC page fault with Athlon 200GE APU Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: System - AMD Athlon 200GE - Gigabyte GA-B450M-S2H board - latest F2c Firmware - Ubuntu 18.04.1 LTS Reproducible with kernels - linux-image-generic-hwe-18.04 version 4.18.0.13.63 - linux-image-unsigned-4.20.0-042000rc4-generic_4.20.0-042000rc4.201812030528_amd64.deb --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2016-08-15 (872 days ago) InstallationMedia: Mythbuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Package: linux (not installed) Tags: bionic Uname: Linux 4.20.0-042000rc4-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to bionic on 2019-01-03 (1 days ago) UserGroups: _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mythfe 2175 F mythfrontend.re mythfe 2181 F pulseaudio /dev/snd/pcmC0D3p: mythfe 2175 F...m mythfrontend.re DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=/dev/mythnew/swap InstallationDate: Installed on 2016-08-15 (872 days ago) InstallationMedia: Mythbuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Gigabyte Technology Co., Ltd. B450M S2H Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-13-generic root=/dev/mapper/mythnew-myth_root ro verbose ProcVersionSignature: Ubuntu 4.18.0-13.14~18.04.1-generic 4.18.17 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.18.0-13-generic N/A linux-backports-modules-4.18.0-13-generic N/A linux-firmware 1.173.2 RfKill: Tags: bionic Uname: Linux 4.18.0-13-generic x86_64 UpgradeStatus: Upgraded to bionic on 2019-01-03 (1 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 12/04/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2c dmi.board.asset.tag: Default string dmi.board.name: B450M S2H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2c:bd12/04/2018:svnGigabyteTechnologyCo.,Ltd.:pnB450MS2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MS2H:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: B450M S2H dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1810546/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2019264] Re: net/sched: act_ct: offload UDP NEW connections
** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2019264 Title: net/sched: act_ct: offload UDP NEW connections Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Jammy: Fix Committed Bug description: * Explain the bug(s) UDP single sided connections aren't offloaded. * brief explanation of fixes Add support for to offload single sided UDP connections by offloading only one side, and offloading the second side when/if it comes. * How to test Create OVS bridge with 2 devices mlx5 rep devices. Enable HW offload and configure regular connection tracking OpenFlow rules: e.g: ovs-ofctl del-flows br-ovs ovs-ofctl add-flow br-ovs arp,actions=normal ovs-ofctl add-flow br-ovs "table=0, ip,ct_state=-trk actions=ct(table=1)" ovs-ofctl add-flow br-ovs "table=1, ip,ct_state=+trk+new actions=ct(commit),normal" ovs-ofctl add-flow br-ovs "table=1, ip,ct_state=+trk+est, actions=normal" Run a UDP single sided connection, e.g iperf without a server: on mlx5 VF2 iperf -t 1 -c -u -b 10pps Optional: In different terminal, while traffic is running, check for offload: tcpdump -nnepi udp and see no iperf udp packets. Dump conntrack with relevant ip: cat /proc/net/nf_conntrack | grep -i | grep "\[UNREPLIED\]" | grep -q "\[OFFLOAD\]" If tuple appears, tuple was offloaded, yet unreplied. * What it could break. Single sided udp connections aren't offloaded. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2019264/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2024432] Re: net/sched: act_ct: Fix promotion of offloaded unreplied tuple
** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2024432 Title: net/sched: act_ct: Fix promotion of offloaded unreplied tuple Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Jammy: Fix Committed Bug description: * Explain the bug(s) Currently UNREPLIED and UNASSURED connections are added to the nf flow table. This causes the following connection packets to be processed by the flow table which then skips conntrack_in(), and thus such the connections will remain UNREPLIED and UNASSURED even if reply traffic is then seen. Even still, the unoffloaded reply packets are the ones triggering hardware update from new to established state, and if there aren't any to triger an update and/or previous update was missed, hardware can get out of sync with sw and still mark packets as new. * brief explanation of fixes 1) Not skipping conntrack_in() for UNASSURED packets, but still refresh for hardware, as before the cited patch. 2) Try and force a refresh by reply-direction packets that update the hardware rules from new to established state. 3) Remove any bidirectional flows that didn't failed to update in hardware for re-insertion as bidirectional once any new packet arrives. * How to test Create OVS bridge with 2 devices mlx5 rep devices. Enable HW offload and configure regular connection tracking OpenFlow rules: e.g: ovs-ofctl del-flows br-ovs ovs-ofctl add-flow br-ovs arp,actions=normal ovs-ofctl add-flow br-ovs "table=0, ip,ct_state=-trk actions=ct(table=1)" ovs-ofctl add-flow br-ovs "table=1, ip,ct_state=+trk+new actions=ct(commit),normal" ovs-ofctl add-flow br-ovs "table=1, ip,ct_state=+trk+est, actions=normal" Run a UDP single sided connection, e.g iperf without a server: on mlx5 VF2 iperf -t 1 -c -u -b 10pps Optional: In different terminal, while traffic is running, check for offload: tcpdump -nnepi udp and see no iperf udp packets. Dump conntrack with relevant ip: cat /proc/net/nf_conntrack | grep -i | grep "\[UNREPLIED\]" | grep -q "\[OFFLOAD\]" If tuple appears, tuple was offloaded, yet unreplied. * What it could break. The connections remain UNREPLIED and UNASSURED even if reply traffic is seen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2024432/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2025192] Re: broken installation while mirror syncing new kernel packages
Ditto. Looks like 2 packages are unavailable: linux-modules-extra-5.15.0-76-generic linux-modules-5.15.0-76-generic = sudo apt install --download-only linux-modules-extra-5.15.0-76-generic Reading package lists... Done Building dependency tree... Done Reading state information... Done Package linux-modules-extra-5.15.0-76-generic is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source E: Package 'linux-modules-extra-5.15.0-76-generic' has no installation candidate = = sudo apt install --download-only linux-modules-5.15.0-76-generic Reading package lists... Done Building dependency tree... Done Reading state information... Done Package linux-modules-5.15.0-76-generic is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source E: Package 'linux-modules-5.15.0-76-generic' has no installation candidate = -- 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/2025192 Title: broken installation while mirror syncing new kernel packages Status in linux-meta package in Ubuntu: Confirmed Bug description: A new kernel package for jammy was released 3 hours ago. It is probably being synced to mirrors right now. It can be seen at https://launchpad.net/ubuntu/+source/linux-meta: 5.15.0.76.74 updates (main) 3 hours ago A little before that, I was deploying 10 Jammy machines in maas, without any problem. After that, I started having all 10 machines fail deployment. The reason is that curtin will fail package updates (complete log attached). This is the important part: ==8<--- Running command ['unshare', '--fork', '--pid', '--', 'chroot', '/tmp/tmp_24ek5y0/target', 'eatmydata', 'apt-get', '--quiet', '--assume-yes', '--option=Dpkg::options::=--force-unsafe-io', '--option=Dpkg::Options::=--force-confold', 'install', 'linux-generic'] with allowed return codes [0] (capture=False) Reading package lists... Building dependency tree... Reading state information... Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: linux-headers-generic : Depends: linux-headers-5.15.0-76-generic but it is not installable linux-image-generic : Depends: linux-image-5.15.0-76-generic but it is not going to be installed Depends: linux-modules-extra-5.15.0-76-generic but it is not installable Recommends: thermald but it is not going to be installed E: Unable to correct problems, you have held broken packages. ==8<--- The repository being used is "http://archive.ubuntu.com/ubuntu jammy/main" It may be the case that there is still a partial mirror there, but it should not break and instead just use the latest available version while the new one is not completely avalable. I'm not sure this is only valid for linux kernel packages (maybe this is a general problem with any package) but I'm opening to linux-meta since it happened with linux in this case. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/2025192/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2020062] Re: No HDMI/DP audio output on dock(Nvidia GPU)
** Tags removed: verification-needed-lunar
** Tags added: verification-done-lunar
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2020062
Title:
No HDMI/DP audio output on dock(Nvidia GPU)
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-6.0 package in Ubuntu:
Invalid
Status in linux-oem-6.1 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
In Progress
Status in linux-oem-6.0 source package in Jammy:
Fix Released
Status in linux-oem-6.1 source package in Jammy:
Fix Released
Status in linux source package in Lunar:
Fix Committed
Status in linux-oem-6.0 source package in Lunar:
Invalid
Status in linux-oem-6.1 source package in Lunar:
Invalid
Status in linux source package in Mantic:
In Progress
Status in linux-oem-6.0 source package in Mantic:
Invalid
Status in linux-oem-6.1 source package in Mantic:
Invalid
Bug description:
[Impact]
When the machine is docked with an external monitor, it is able to output
display, but the HDMI/DP audio output option is lost in DGFF Hybrid
Discrete/Discrete mode(Nvidia GPU).
[Fix]
Nvidia provides a patch to fix it
https://patchwork.kernel.org/project/alsa-devel/patch/20230517090736.15088-1-nmah...@nvidia.com/
in 6.4-rc3
dc4f2ccaeddd ALSA: hda: Add NVIDIA codec IDs a3 through a7 to patch table
[Test]
Verified on the target machine.
{Where problems could occur]
The patch just adds IDs, and won't lead to any regression.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2020062/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2025192] Re: broken installation while mirror syncing new kernel packages
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-meta (Ubuntu) Status: New => Confirmed -- 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/2025192 Title: broken installation while mirror syncing new kernel packages Status in linux-meta package in Ubuntu: Confirmed Bug description: A new kernel package for jammy was released 3 hours ago. It is probably being synced to mirrors right now. It can be seen at https://launchpad.net/ubuntu/+source/linux-meta: 5.15.0.76.74 updates (main) 3 hours ago A little before that, I was deploying 10 Jammy machines in maas, without any problem. After that, I started having all 10 machines fail deployment. The reason is that curtin will fail package updates (complete log attached). This is the important part: ==8<--- Running command ['unshare', '--fork', '--pid', '--', 'chroot', '/tmp/tmp_24ek5y0/target', 'eatmydata', 'apt-get', '--quiet', '--assume-yes', '--option=Dpkg::options::=--force-unsafe-io', '--option=Dpkg::Options::=--force-confold', 'install', 'linux-generic'] with allowed return codes [0] (capture=False) Reading package lists... Building dependency tree... Reading state information... Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: linux-headers-generic : Depends: linux-headers-5.15.0-76-generic but it is not installable linux-image-generic : Depends: linux-image-5.15.0-76-generic but it is not going to be installed Depends: linux-modules-extra-5.15.0-76-generic but it is not installable Recommends: thermald but it is not going to be installed E: Unable to correct problems, you have held broken packages. ==8<--- The repository being used is "http://archive.ubuntu.com/ubuntu jammy/main" It may be the case that there is still a partial mirror there, but it should not break and instead just use the latest available version while the new one is not completely avalable. I'm not sure this is only valid for linux kernel packages (maybe this is a general problem with any package) but I'm opening to linux-meta since it happened with linux in this case. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/2025192/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2025198] [NEW] Lenevo Ideapad Slim - Ubuntu slow, Lost of internet, Main display not clean resolution
Public bug reported: Since I installed Ubuntu 22.04 my laptop is slow I lose my internet connection intermittently. The main display resolution is not clean. The image rendering seems diluted and unclear, especially at the edges of the screen. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-45-generic 5.19.0-45.46~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-45.46~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-45-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Jun 27 20:33:17 2023 InstallationDate: Installed on 2023-06-21 (6 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.19 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- 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/2025198 Title: Lenevo Ideapad Slim - Ubuntu slow, Lost of internet, Main display not clean resolution Status in linux-signed-hwe-5.19 package in Ubuntu: New Bug description: Since I installed Ubuntu 22.04 my laptop is slow I lose my internet connection intermittently. The main display resolution is not clean. The image rendering seems diluted and unclear, especially at the edges of the screen. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-45-generic 5.19.0-45.46~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-45.46~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-45-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Jun 27 20:33:17 2023 InstallationDate: Installed on 2023-06-21 (6 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) SourcePackage: linux-signed-hwe-5.19 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/2025198/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2023638] Re: Various backlight issues with the 6.0/6.1 kernel
** Description changed: [Impact] There are some new patches for new method to decide which backlight driver should be registered introduced since 6.1. And we backport some of them to 6.0-oem kernel which are not enough to solved all backlight issues. 1. dell_laptop created a non-working backlight driver before nvidia is loaded, that leads to the system can't adjust the display brightness. 2. acpi_backlight0 sometimes will be generated together with intel_backlight. [Fix] - Below 2 commits from v6.3-rc6 prevent the acpi_backlight from being registered automatically + Below 2 commits from v6.3-rc6 prevent the acpi_backlight from being registered automatically(which have been included into ubuntu kernels through stable update) e506731c8f35 ACPI: video: Make acpi_backlight=video work independent from GPU driver 78dfc9d1d1ab ACPI: video: Add auto_detect arg to __acpi_video_get_backlight_type() Below patch prevents platform driver(dell_laptop) from creating backlight driver after win8. + aa8a950a5d6b ACPI: video: Stop trying to use vendor backlight control on laptops from after ~2012 https://patchwork.kernel.org/project/linux-acpi/patch/20230608091258.7963-1-hdego...@redhat.com/ [Test] Verified on the dell platform which reports this issue. [Where problems could occur] The assumption of the not-yet-upstreamed commit regarding backlight control is that, after Windows 8, all laptop backlights are controlled either by ACPI or the native graphics driver. It impacts the laptops that do not follow the assumption and will lead to broken backlight interface. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/2023638 Title: Various backlight issues with the 6.0/6.1 kernel Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.0 source package in Jammy: Fix Committed Status in linux-oem-6.1 source package in Jammy: In Progress Status in linux 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: In Progress Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: In Progress Status in linux-oem-6.0 source package in Mantic: Invalid Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: [Impact] There are some new patches for new method to decide which backlight driver should be registered introduced since 6.1. And we backport some of them to 6.0-oem kernel which are not enough to solved all backlight issues. 1. dell_laptop created a non-working backlight driver before nvidia is loaded, that leads to the system can't adjust the display brightness. 2. acpi_backlight0 sometimes will be generated together with intel_backlight. [Fix] Below 2 commits from v6.3-rc6 prevent the acpi_backlight from being registered automatically(which have been included into ubuntu kernels through stable update) e506731c8f35 ACPI: video: Make acpi_backlight=video work independent from GPU driver 78dfc9d1d1ab ACPI: video: Add auto_detect arg to __acpi_video_get_backlight_type() Below patch prevents platform driver(dell_laptop) from creating backlight driver after win8. aa8a950a5d6b ACPI: video: Stop trying to use vendor backlight control on laptops from after ~2012 https://patchwork.kernel.org/project/linux-acpi/patch/20230608091258.7963-1-hdego...@redhat.com/ [Test] Verified on the dell platform which reports this issue. [Where problems could occur] The assumption of the not-yet-upstreamed commit regarding backlight control is that, after Windows 8, all laptop backlights are controlled either by ACPI or the native graphics driver. It impacts the laptops that do not follow the assumption and will lead to broken backlight interface. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2023638/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2025195] Re: HDMI output with More than one child device for port B in VBT error
** Patch added: "0001-UBUNTU-SAUCE-drm-i915-quirks-Add-multiple-VBT-quirk-.patch" https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.1/+bug/2025195/+attachment/5682421/+files/0001-UBUNTU-SAUCE-drm-i915-quirks-Add-multiple-VBT-quirk-.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2025195 Title: HDMI output with More than one child device for port B in VBT error Status in HWE Next: New Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.1 source package in Jammy: In Progress Bug description: [Impact] The HDMI monitor doesn't work, no events while plug/unplug then cable. [Fix] From the bug report[1], skip the return workaround the issue, so I created the DMI quirk to list affected platforms. Intel is submitting patches[2][3] to fix the issue, but it requires to backport huge drm structure changes, too. As there is no regression found with this workaround, it's safer to use the DMI quirk to handle this issue, and wait Intel's fix[2][3] to be available in v6.5 kernel. 1. https://gitlab.freedesktop.org/drm/intel/-/issues/7709 2. https://patchwork.freedesktop.org/series/117641/ 3. https://patchwork.freedesktop.org/series/114200/ [Test] Verified by me, FE, and ODM. [Where problems could occur] I have no idea what might happen, so only make the workaround avaiable on the listed platforms. So far, no regressions have been observed with plug/unplug, switch modes, reboot, and suspend tests. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2025195/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2025195] [NEW] HDMI output with More than one child device for port B in VBT error
Public bug reported: [Impact] The HDMI monitor doesn't work, no events while plug/unplug then cable. [Fix] >From the bug report[1], skip the return workaround the issue, so I created the >DMI quirk to list affected platforms. Intel is submitting patches[2][3] to fix the issue, but it requires to backport huge drm structure changes, too. As there is no regression found with this workaround, it's safer to use the DMI quirk to handle this issue, and wait Intel's fix[2][3] to be available in v6.5 kernel. 1. https://gitlab.freedesktop.org/drm/intel/-/issues/7709 2. https://patchwork.freedesktop.org/series/117641/ 3. https://patchwork.freedesktop.org/series/114200/ [Test] Verified by me, FE, and ODM. [Where problems could occur] I have no idea what might happen, so only make the workaround avaiable on the listed platforms. So far, no regressions have been observed with plug/unplug, switch modes, reboot, and suspend tests. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux-oem-6.1 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-oem-6.1 (Ubuntu Jammy) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Tags: oem-priority originate-from-2000703 stella ** Also affects: linux-oem-6.1 (Ubuntu Jammy) Importance: Undecided Status: New ** Tags added: oem-priority originate-from-2000703 stella ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux-oem-6.1 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2025195 Title: HDMI output with More than one child device for port B in VBT error Status in HWE Next: New Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.1 source package in Jammy: In Progress Bug description: [Impact] The HDMI monitor doesn't work, no events while plug/unplug then cable. [Fix] From the bug report[1], skip the return workaround the issue, so I created the DMI quirk to list affected platforms. Intel is submitting patches[2][3] to fix the issue, but it requires to backport huge drm structure changes, too. As there is no regression found with this workaround, it's safer to use the DMI quirk to handle this issue, and wait Intel's fix[2][3] to be available in v6.5 kernel. 1. https://gitlab.freedesktop.org/drm/intel/-/issues/7709 2. https://patchwork.freedesktop.org/series/117641/ 3. https://patchwork.freedesktop.org/series/114200/ [Test] Verified by me, FE, and ODM. [Where problems could occur] I have no idea what might happen, so only make the workaround avaiable on the listed platforms. So far, no regressions have been observed with plug/unplug, switch modes, reboot, and suspend tests. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2025195/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2025192] [NEW] broken installation while mirror syncing new kernel packages
Public bug reported: A new kernel package for jammy was released 3 hours ago. It is probably being synced to mirrors right now. It can be seen at https://launchpad.net/ubuntu/+source/linux-meta: 5.15.0.76.74 updates (main) 3 hours ago A little before that, I was deploying 10 Jammy machines in maas, without any problem. After that, I started having all 10 machines fail deployment. The reason is that curtin will fail package updates (complete log attached). This is the important part: ==8<--- Running command ['unshare', '--fork', '--pid', '--', 'chroot', '/tmp/tmp_24ek5y0/target', 'eatmydata', 'apt-get', '--quiet', '--assume-yes', '--option=Dpkg::options::=--force-unsafe-io', '--option=Dpkg::Options::=--force-confold', 'install', 'linux-generic'] with allowed return codes [0] (capture=False) Reading package lists... Building dependency tree... Reading state information... Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: linux-headers-generic : Depends: linux-headers-5.15.0-76-generic but it is not installable linux-image-generic : Depends: linux-image-5.15.0-76-generic but it is not going to be installed Depends: linux-modules-extra-5.15.0-76-generic but it is not installable Recommends: thermald but it is not going to be installed E: Unable to correct problems, you have held broken packages. ==8<--- The repository being used is "http://archive.ubuntu.com/ubuntu jammy/main" It may be the case that there is still a partial mirror there, but it should not break and instead just use the latest available version while the new one is not completely avalable. I'm not sure this is only valid for linux kernel packages (maybe this is a general problem with any package) but I'm opening to linux-meta since it happened with linux in this case. ** Affects: linux-meta (Ubuntu) Importance: Undecided Status: New -- 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/2025192 Title: broken installation while mirror syncing new kernel packages Status in linux-meta package in Ubuntu: New Bug description: A new kernel package for jammy was released 3 hours ago. It is probably being synced to mirrors right now. It can be seen at https://launchpad.net/ubuntu/+source/linux-meta: 5.15.0.76.74 updates (main) 3 hours ago A little before that, I was deploying 10 Jammy machines in maas, without any problem. After that, I started having all 10 machines fail deployment. The reason is that curtin will fail package updates (complete log attached). This is the important part: ==8<--- Running command ['unshare', '--fork', '--pid', '--', 'chroot', '/tmp/tmp_24ek5y0/target', 'eatmydata', 'apt-get', '--quiet', '--assume-yes', '--option=Dpkg::options::=--force-unsafe-io', '--option=Dpkg::Options::=--force-confold', 'install', 'linux-generic'] with allowed return codes [0] (capture=False) Reading package lists... Building dependency tree... Reading state information... Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: linux-headers-generic : Depends: linux-headers-5.15.0-76-generic but it is not installable linux-image-generic : Depends: linux-image-5.15.0-76-generic but it is not going to be installed Depends: linux-modules-extra-5.15.0-76-generic but it is not installable Recommends: thermald but it is not going to be installed E: Unable to correct problems, you have held broken packages. ==8<--- The repository being used is "http://archive.ubuntu.com/ubuntu jammy/main" It may be the case that there is still a partial mirror there, but it should not break and instead just use the latest available version while the new one is not completely avalable. I'm not sure this is only valid for linux kernel packages (maybe this is a general problem with any package) but I'm opening to linux-meta since
[Kernel-packages] [Bug 2025192] Re: broken installation while mirror syncing new kernel packages
** Attachment added: "ob76-node3.maas-installation-output-2023-06-27.log" https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/2025192/+attachment/5682415/+files/ob76-node3.maas-installation-output-2023-06-27.log -- 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/2025192 Title: broken installation while mirror syncing new kernel packages Status in linux-meta package in Ubuntu: New Bug description: A new kernel package for jammy was released 3 hours ago. It is probably being synced to mirrors right now. It can be seen at https://launchpad.net/ubuntu/+source/linux-meta: 5.15.0.76.74 updates (main) 3 hours ago A little before that, I was deploying 10 Jammy machines in maas, without any problem. After that, I started having all 10 machines fail deployment. The reason is that curtin will fail package updates (complete log attached). This is the important part: ==8<--- Running command ['unshare', '--fork', '--pid', '--', 'chroot', '/tmp/tmp_24ek5y0/target', 'eatmydata', 'apt-get', '--quiet', '--assume-yes', '--option=Dpkg::options::=--force-unsafe-io', '--option=Dpkg::Options::=--force-confold', 'install', 'linux-generic'] with allowed return codes [0] (capture=False) Reading package lists... Building dependency tree... Reading state information... Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: linux-headers-generic : Depends: linux-headers-5.15.0-76-generic but it is not installable linux-image-generic : Depends: linux-image-5.15.0-76-generic but it is not going to be installed Depends: linux-modules-extra-5.15.0-76-generic but it is not installable Recommends: thermald but it is not going to be installed E: Unable to correct problems, you have held broken packages. ==8<--- The repository being used is "http://archive.ubuntu.com/ubuntu jammy/main" It may be the case that there is still a partial mirror there, but it should not break and instead just use the latest available version while the new one is not completely avalable. I'm not sure this is only valid for linux kernel packages (maybe this is a general problem with any package) but I'm opening to linux-meta since it happened with linux in this case. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/2025192/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2025185] Re: package linux-headers-6.2.0-23-generic 6.2.0-23.23 failed to install/upgrade: installed linux-headers-6.2.0-23-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/2025185 Title: package linux-headers-6.2.0-23-generic 6.2.0-23.23 failed to install/upgrade: installed linux-headers-6.2.0-23-generic package post-installation script subprocess returned error exit status 1 Status in linux package in Ubuntu: New Bug description: error happened while updating software ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-headers-6.2.0-23-generic 6.2.0-23.23 ProcVersionSignature: Ubuntu 5.19.0-40.41~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-40-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lucky 2205 F wireplumber /dev/snd/controlC0: lucky 2205 F wireplumber /dev/snd/seq:lucky 2202 F pipewire CasperMD5CheckResult: unknown Date: Tue Jun 27 18:53:31 2023 ErrorMessage: installed linux-headers-6.2.0-23-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2023-04-07 (81 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: Dell Inc. Inspiron 15-5578 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-40-generic root=UUID=645f930b-ccc1-4d48-b320-ec2e259f546a ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.06-2ubuntu16 SourcePackage: linux Title: package linux-headers-6.2.0-23-generic 6.2.0-23.23 failed to install/upgrade: installed linux-headers-6.2.0-23-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to lunar on 2023-04-07 (81 days ago) dmi.bios.date: 01/18/2019 dmi.bios.release: 1.27 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.27.0 dmi.board.name: 0D4XFH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.27.0:bd01/18/2019:br1.27:svnDellInc.:pnInspiron15-5578:pvr:rvnDellInc.:rn0D4XFH:rvrA00:cvnDellInc.:ct9:cvr:sku0742: dmi.product.family: Inspiron dmi.product.name: Inspiron 15-5578 dmi.product.sku: 0742 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2025185/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2025185] [NEW] package linux-headers-6.2.0-23-generic 6.2.0-23.23 failed to install/upgrade: installed linux-headers-6.2.0-23-generic package post-installation script subprocess
Public bug reported: error happened while updating software ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-headers-6.2.0-23-generic 6.2.0-23.23 ProcVersionSignature: Ubuntu 5.19.0-40.41~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-40-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lucky 2205 F wireplumber /dev/snd/controlC0: lucky 2205 F wireplumber /dev/snd/seq:lucky 2202 F pipewire CasperMD5CheckResult: unknown Date: Tue Jun 27 18:53:31 2023 ErrorMessage: installed linux-headers-6.2.0-23-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2023-04-07 (81 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: Dell Inc. Inspiron 15-5578 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-40-generic root=UUID=645f930b-ccc1-4d48-b320-ec2e259f546a ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.06-2ubuntu16 SourcePackage: linux Title: package linux-headers-6.2.0-23-generic 6.2.0-23.23 failed to install/upgrade: installed linux-headers-6.2.0-23-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to lunar on 2023-04-07 (81 days ago) dmi.bios.date: 01/18/2019 dmi.bios.release: 1.27 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.27.0 dmi.board.name: 0D4XFH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.27.0:bd01/18/2019:br1.27:svnDellInc.:pnInspiron15-5578:pvr:rvnDellInc.:rn0D4XFH:rvrA00:cvnDellInc.:ct9:cvr:sku0742: dmi.product.family: Inspiron dmi.product.name: Inspiron 15-5578 dmi.product.sku: 0742 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package lunar -- 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/2025185 Title: package linux-headers-6.2.0-23-generic 6.2.0-23.23 failed to install/upgrade: installed linux-headers-6.2.0-23-generic package post-installation script subprocess returned error exit status 1 Status in linux package in Ubuntu: New Bug description: error happened while updating software ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-headers-6.2.0-23-generic 6.2.0-23.23 ProcVersionSignature: Ubuntu 5.19.0-40.41~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-40-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lucky 2205 F wireplumber /dev/snd/controlC0: lucky 2205 F wireplumber /dev/snd/seq:lucky 2202 F pipewire CasperMD5CheckResult: unknown Date: Tue Jun 27 18:53:31 2023 ErrorMessage: installed linux-headers-6.2.0-23-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2023-04-07 (81 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: Dell Inc. Inspiron 15-5578 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-40-generic root=UUID=645f930b-ccc1-4d48-b320-ec2e259f546a ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.06-2ubuntu16 SourcePackage: linux Title: package linux-headers-6.2.0-23-generic 6.2.0-23.23 failed to install/upgrade: installed linux-headers-6.2.0-23-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to lunar on 2023-04-07 (81 days ago) dmi.bios.date: 01/18/2019 dmi.bios.release: 1.27 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.27.0 dmi.board.name: 0D4XFH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.27.0:bd01/18/2019:br1.27:svnDellInc.:pnInspiron15-5578:pvr:rvnDellInc.:rn0D4XFH:rvrA00:cvnDellInc.:ct9:cvr:sku0742: dmi.product.family: Inspiron dmi.product.name: Inspiron 15-5578 dmi.product.sku: 0742 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2025185/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
[Kernel-packages] [Bug 2025183] Re: Kinetic update: upstream stable patchset 2023-06-27
** Description changed: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2023-06-27 + + Ported from the following upstream stable releases: + v5.15.109, v6.1.26 + v5.15.110, v6.1.27 + from git://git.kernel.org/ ARM: dts: rockchip: fix a typo error for rk3288 spdif node arm64: dts: qcom: ipq8074-hk01: enable QMP device, not the PHY node arm64: dts: meson-g12-common: specify full DMC range arm64: dts: imx8mm-evk: correct pmic clock source netfilter: br_netfilter: fix recent physdev match breakage regulator: fan53555: Explicitly include bits header regulator: fan53555: Fix wrong TCS_SLEW_MASK virtio_net: bugfix overflow inside xdp_linearize_page() sfc: Split STATE_READY in to STATE_NET_DOWN and STATE_NET_UP. sfc: Fix use-after-free due to selftest_work netfilter: nf_tables: fix ifdef to also consider nf_tables=m i40e: fix accessing vsi->active_filters without holding lock i40e: fix i40e_setup_misc_vector() error handling netfilter: nf_tables: validate catch-all set elements netfilter: nf_tables: tighten netlink attribute requirements for catch-all elements bnxt_en: Do not initialize PTP on older P3/P4 chips mlxfw: fix null-ptr-deref in mlxfw_mfa2_tlv_next() bonding: Fix memory leak when changing bond type to Ethernet net: rpl: fix rpl header size calculation mlxsw: pci: Fix possible crash during initialization spi: spi-rockchip: Fix missing unwind goto in rockchip_sfc_probe() bpf: Fix incorrect verifier pruning due to missing register precision taints e1000e: Disable TSO on i219-LM card to increase speed f2fs: Fix f2fs_truncate_partial_nodes ftrace event platform/x86 (gigabyte-wmi): Add support for A320M-S2H V2 selftests: sigaltstack: fix -Wuninitialized scsi: megaraid_sas: Fix fw_crash_buffer_show() scsi: core: Improve scsi_vpd_inquiry() checks net: dsa: b53: mmap: add phy ops s390/ptrace: fix PTRACE_GET_LAST_BREAK error handling nvme-tcp: fix a possible UAF when failing to allocate an io queue xen/netback: use same error messages for same errors platform/x86: gigabyte-wmi: add support for X570S AORUS ELITE iio: light: tsl2772: fix reading proximity-diodes from device tree nilfs2: initialize unused bytes in segment summary blocks memstick: fix memory leak if card device is never registered kernel/sys.c: fix and improve control flow in __sys_setres[ug]id() mmc: sdhci_am654: Set HIGH_SPEED_ENA for SDR12 and SDR25 drm/i915: Fix fast wake AUX sync len mm/khugepaged: check again on anon uffd-wp during isolation mm: page_alloc: skip regions with hugetlbfs pages when allocating 1G pages sched/fair: Detect capacity inversion sched/fair: Consider capacity inversion in util_fits_cpu() sched/uclamp: Fix a uninitialized variable warnings sched/fair: Fixes for capacity inversion detection MIPS: Define RUNTIME_DISCARD_EXIT in LD script purgatory: fix disabling debug info fuse: always revalidate rename target dentry udp: Call inet6_destroy_sock() in setsockopt(IPV6_ADDRFORM). tcp/udp: Call inet6_destroy_sock() in IPv6 sk->sk_destruct(). inet6: Remove inet6_destroy_sock() in sk->sk_prot->destroy(). dccp: Call inet6_destroy_sock() via sk->sk_destruct(). sctp: Call inet6_destroy_sock() via sk->sk_destruct(). pwm: meson: Explicitly set .polarity in .get_state() iio: adc: at91-sama5d2_adc: fix an error code in at91_adc_allocate_trigger() mm/page_alloc: fix potential deadlock on zonelist_update_seq seqlock ASoC: fsl_asrc_dma: fix potential null-ptr-deref ASN.1: Fix check for strdup() success soc: sifive: l2_cache: fix missing iounmap() in error path in sifive_l2_init() soc: sifive: l2_cache: fix missing free_irq() in error path in sifive_l2_init() soc: sifive: l2_cache: fix missing of_node_put() in sifive_l2_init() arm64: dts: rockchip: Lower sd speed on rk3566-soquartz arm64: dts: qcom: ipq8074-hk10: enable QMP device, not the PHY node arm64: dts: imx8mm-verdin: correct off-on-delay arm64: dts: imx8mp-verdin: correct off-on-delay netfilter: nf_tables: Modify nla_memdup's flag to GFP_KERNEL_ACCOUNT net: bridge: switchdev: don't notify FDB entries with "master dynamic" drm/amdgpu/vcn: Disable indirect SRAM on Vangogh broken BIOSes iio: dac: ad5755: Add missing fwnode_handle_put() tools/mm/page_owner_sort.c: fix TGID output when cull=tg is used writeback, cgroup: fix null-ptr-deref write in bdi_split_work_to_wbs drm/rockchip: vop2: fix suspend/resume
[Kernel-packages] [Bug 2025183] [NEW] Kinetic update: upstream stable patchset 2023-06-27
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2023-06-27 from git://git.kernel.org/ ARM: dts: rockchip: fix a typo error for rk3288 spdif node arm64: dts: qcom: ipq8074-hk01: enable QMP device, not the PHY node arm64: dts: meson-g12-common: specify full DMC range arm64: dts: imx8mm-evk: correct pmic clock source netfilter: br_netfilter: fix recent physdev match breakage regulator: fan53555: Explicitly include bits header regulator: fan53555: Fix wrong TCS_SLEW_MASK virtio_net: bugfix overflow inside xdp_linearize_page() sfc: Split STATE_READY in to STATE_NET_DOWN and STATE_NET_UP. sfc: Fix use-after-free due to selftest_work netfilter: nf_tables: fix ifdef to also consider nf_tables=m i40e: fix accessing vsi->active_filters without holding lock i40e: fix i40e_setup_misc_vector() error handling netfilter: nf_tables: validate catch-all set elements netfilter: nf_tables: tighten netlink attribute requirements for catch-all elements bnxt_en: Do not initialize PTP on older P3/P4 chips mlxfw: fix null-ptr-deref in mlxfw_mfa2_tlv_next() bonding: Fix memory leak when changing bond type to Ethernet net: rpl: fix rpl header size calculation mlxsw: pci: Fix possible crash during initialization spi: spi-rockchip: Fix missing unwind goto in rockchip_sfc_probe() bpf: Fix incorrect verifier pruning due to missing register precision taints e1000e: Disable TSO on i219-LM card to increase speed f2fs: Fix f2fs_truncate_partial_nodes ftrace event platform/x86 (gigabyte-wmi): Add support for A320M-S2H V2 selftests: sigaltstack: fix -Wuninitialized scsi: megaraid_sas: Fix fw_crash_buffer_show() scsi: core: Improve scsi_vpd_inquiry() checks net: dsa: b53: mmap: add phy ops s390/ptrace: fix PTRACE_GET_LAST_BREAK error handling nvme-tcp: fix a possible UAF when failing to allocate an io queue xen/netback: use same error messages for same errors platform/x86: gigabyte-wmi: add support for X570S AORUS ELITE iio: light: tsl2772: fix reading proximity-diodes from device tree nilfs2: initialize unused bytes in segment summary blocks memstick: fix memory leak if card device is never registered kernel/sys.c: fix and improve control flow in __sys_setres[ug]id() mmc: sdhci_am654: Set HIGH_SPEED_ENA for SDR12 and SDR25 drm/i915: Fix fast wake AUX sync len mm/khugepaged: check again on anon uffd-wp during isolation mm: page_alloc: skip regions with hugetlbfs pages when allocating 1G pages sched/fair: Detect capacity inversion sched/fair: Consider capacity inversion in util_fits_cpu() sched/uclamp: Fix a uninitialized variable warnings sched/fair: Fixes for capacity inversion detection MIPS: Define RUNTIME_DISCARD_EXIT in LD script purgatory: fix disabling debug info fuse: always revalidate rename target dentry udp: Call inet6_destroy_sock() in setsockopt(IPV6_ADDRFORM). tcp/udp: Call inet6_destroy_sock() in IPv6 sk->sk_destruct(). inet6: Remove inet6_destroy_sock() in sk->sk_prot->destroy(). dccp: Call inet6_destroy_sock() via sk->sk_destruct(). sctp: Call inet6_destroy_sock() via sk->sk_destruct(). pwm: meson: Explicitly set .polarity in .get_state() iio: adc: at91-sama5d2_adc: fix an error code in at91_adc_allocate_trigger() mm/page_alloc: fix potential deadlock on zonelist_update_seq seqlock ASoC: fsl_asrc_dma: fix potential null-ptr-deref ASN.1: Fix check for strdup() success soc: sifive: l2_cache: fix missing iounmap() in error path in sifive_l2_init() soc: sifive: l2_cache: fix missing free_irq() in error path in sifive_l2_init() soc: sifive: l2_cache: fix missing of_node_put() in sifive_l2_init() arm64: dts: rockchip: Lower sd speed on rk3566-soquartz arm64: dts: qcom: ipq8074-hk10: enable QMP device, not the PHY node arm64: dts: imx8mm-verdin: correct off-on-delay arm64: dts: imx8mp-verdin: correct off-on-delay netfilter: nf_tables: Modify nla_memdup's flag to GFP_KERNEL_ACCOUNT net: bridge: switchdev: don't notify FDB entries with "master dynamic" drm/amdgpu/vcn: Disable indirect SRAM on Vangogh broken BIOSes iio: dac: ad5755: Add missing fwnode_handle_put() tools/mm/page_owner_sort.c: fix TGID output when cull=tg is used writeback, cgroup: fix null-ptr-deref write in bdi_split_work_to_wbs drm/rockchip: vop2: fix suspend/resume mm/userfaultfd: fix uffd-wp handling for THP migration entries mm/huge_memory.c: warn with pr_warn_ratelimited instead of VM_WARN_ON_ONCE_FOLIO KVM: arm64: Fix buffer overflow in kvm_arm_set_fw_reg() fpga: bridge: properly initialize bridge device before populating children ASoC: fsl_sai: Fix pins setting for i.MX8QM platform UBUNTU: Upstream stable to
[Kernel-packages] [Bug 1997178] Re: Black screen after wake from S3 suspend on Nvidia proprietary driver redux
Worth noting that Windows 10 on this same desktop has never had an issue with sleep and wake - this is a Linux-specific issue. -- 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/1997178 Title: Black screen after wake from S3 suspend on Nvidia proprietary driver redux Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-515 package in Ubuntu: New Bug description: When resuming from suspend in Ubuntu 22.04 with proprietary Nvidia driver 515, screen is black, and never changes after 10 minutes of waiting. However journalctl shows activity after wake (see attached log excerpt, where wake occurs around Nov 20 10:28:37 with black screen, followed by forced REISUB reboot a couple minutes later when screen failed to update). This makes me think the issue is around Nvidia driver <-> Linux kernel communication. I [previously reported](https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987134) similar black screen after wake behavior that seemed resolve with a Linux kernel update, but subsequent Linux kernel and Nvidia driver updates steadily regressed back to the previous behavior. The most recent kernel update from a few days ago (5.15.0-53-generic) never wakes from suspend (so far out of 5 trials). Previous few kernels where regression was first noticed it was 50/50 odds of successful wake, so most recent kernel is a noticeable regression. Important note: most recent kernel (5.15.0-53) upgrade freezed system mid-upgrade (first time this has happened to me on Linux in at least 5 years!). Damaged GRUB and Nvidia DKMS, requiring reinstallation of GRUB, the kernel, Nvidia drivers, and a GRUB update (in that order). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-53.59-generic 5.15.64 Uname: Linux 5.15.0-53-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..0d.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 515.65.01 Wed Jul 20 14:00:58 UTC 2022 GCC version: gcc version 11.3.0 (Ubuntu 11.3.0-1ubuntu1~22.04) ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Nov 20 11:20:45 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: nvidia/515.65.01, 5.15.0-53-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Several times a week GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Within the last week or two GraphicsCard: NVIDIA Corporation GM204 [GeForce GTX 970] [10de:13c2] (rev a1) (prog-if 00 [VGA controller]) Subsystem: PNY GM204 [GeForce GTX 970] [196e:1131] InstallationDate: Installed on 2022-08-17 (95 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-53-generic root=UUID=70074436-a9a5-4212-9b57-7600a7dc6843 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/29/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P4.70 dmi.board.name: X470 Taichi Ultimate dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP4.70:bd03/29/2021:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX470TaichiUltimate:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx:
[Kernel-packages] [Bug 1997178] Re: Black screen after wake from S3 suspend on Nvidia proprietary driver redux
Upgraded to a Nvidia RTX 4090, and initially sleep seemed to work for a few weeks. After the last few kernel updates, sleep again is frequently (but not always) failing to wake, sometimes resulting in a hang at a black screen (responsive to Alt+Print+REISUB), sometimes in a automatic reboot after a couple minutes. Attaching excerpt from systemd which covers the sleep, though it does not seem to record anything related to attempted wake before the force reboot. Oddly systemd is treating it as a single boot even though the system force rebooted. ** Attachment added: "systemd log of forced reboot after wake from sleep" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-515/+bug/1997178/+attachment/5682375/+files/rtx_4090_sleep_cannot_wake.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/1997178 Title: Black screen after wake from S3 suspend on Nvidia proprietary driver redux Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-515 package in Ubuntu: New Bug description: When resuming from suspend in Ubuntu 22.04 with proprietary Nvidia driver 515, screen is black, and never changes after 10 minutes of waiting. However journalctl shows activity after wake (see attached log excerpt, where wake occurs around Nov 20 10:28:37 with black screen, followed by forced REISUB reboot a couple minutes later when screen failed to update). This makes me think the issue is around Nvidia driver <-> Linux kernel communication. I [previously reported](https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987134) similar black screen after wake behavior that seemed resolve with a Linux kernel update, but subsequent Linux kernel and Nvidia driver updates steadily regressed back to the previous behavior. The most recent kernel update from a few days ago (5.15.0-53-generic) never wakes from suspend (so far out of 5 trials). Previous few kernels where regression was first noticed it was 50/50 odds of successful wake, so most recent kernel is a noticeable regression. Important note: most recent kernel (5.15.0-53) upgrade freezed system mid-upgrade (first time this has happened to me on Linux in at least 5 years!). Damaged GRUB and Nvidia DKMS, requiring reinstallation of GRUB, the kernel, Nvidia drivers, and a GRUB update (in that order). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-53.59-generic 5.15.64 Uname: Linux 5.15.0-53-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..0d.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 515.65.01 Wed Jul 20 14:00:58 UTC 2022 GCC version: gcc version 11.3.0 (Ubuntu 11.3.0-1ubuntu1~22.04) ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Nov 20 11:20:45 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: nvidia/515.65.01, 5.15.0-53-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Several times a week GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Within the last week or two GraphicsCard: NVIDIA Corporation GM204 [GeForce GTX 970] [10de:13c2] (rev a1) (prog-if 00 [VGA controller]) Subsystem: PNY GM204 [GeForce GTX 970] [196e:1131] InstallationDate: Installed on 2022-08-17 (95 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-53-generic root=UUID=70074436-a9a5-4212-9b57-7600a7dc6843 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/29/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P4.70 dmi.board.name: X470 Taichi Ultimate dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be
[Kernel-packages] [Bug 2024675] Re: NVIDIA CVE-2023-25515, CVE-2023-25516
Automated testing of the DKMS drivers, (450-server, 470-server,
525-server, 470, 525 and 535) has completed across bionic, focal, jammy,
kinetic and lunar. This was performed with:
* Deploy host with gpgpu
* Install latest `linux-generic` kernel
* Install driver from ppa using `nvidia-driver-${DRIVER_NUMBER}` package
* Reboot
* Install cuda
* Execute select cuda samples
* Verify nvidia-smi output matches the expected DRIVER_NUMBER and version.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu.
https://bugs.launchpad.net/bugs/2024675
Title:
NVIDIA CVE-2023-25515, CVE-2023-25516
Status in fabric-manager-450 package in Ubuntu:
In Progress
Status in fabric-manager-470 package in Ubuntu:
Triaged
Status in fabric-manager-525 package in Ubuntu:
Triaged
Status in libnvidia-nscq-450 package in Ubuntu:
Triaged
Status in libnvidia-nscq-470 package in Ubuntu:
Triaged
Status in libnvidia-nscq-525 package in Ubuntu:
Triaged
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
Triaged
Status in nvidia-graphics-drivers-470 package in Ubuntu:
Triaged
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
Triaged
Status in nvidia-graphics-drivers-525 package in Ubuntu:
Triaged
Status in nvidia-graphics-drivers-525-server package in Ubuntu:
Triaged
Status in nvidia-graphics-drivers-530 package in Ubuntu:
Triaged
Status in fabric-manager-450 source package in Focal:
New
Status in fabric-manager-470 source package in Focal:
New
Status in fabric-manager-525 source package in Focal:
New
Status in libnvidia-nscq-450 source package in Focal:
New
Status in libnvidia-nscq-470 source package in Focal:
New
Status in libnvidia-nscq-525 source package in Focal:
New
Status in nvidia-graphics-drivers-450-server source package in Focal:
New
Status in nvidia-graphics-drivers-470 source package in Focal:
New
Status in nvidia-graphics-drivers-470-server source package in Focal:
New
Status in nvidia-graphics-drivers-525 source package in Focal:
New
Status in nvidia-graphics-drivers-525-server source package in Focal:
New
Status in nvidia-graphics-drivers-530 source package in Focal:
New
Status in fabric-manager-450 source package in Jammy:
New
Status in fabric-manager-470 source package in Jammy:
New
Status in fabric-manager-525 source package in Jammy:
New
Status in libnvidia-nscq-450 source package in Jammy:
New
Status in libnvidia-nscq-470 source package in Jammy:
New
Status in libnvidia-nscq-525 source package in Jammy:
New
Status in nvidia-graphics-drivers-450-server source package in Jammy:
New
Status in nvidia-graphics-drivers-470 source package in Jammy:
New
Status in nvidia-graphics-drivers-470-server source package in Jammy:
New
Status in nvidia-graphics-drivers-525 source package in Jammy:
New
Status in nvidia-graphics-drivers-525-server source package in Jammy:
New
Status in nvidia-graphics-drivers-530 source package in Jammy:
New
Status in fabric-manager-450 source package in Kinetic:
New
Status in fabric-manager-470 source package in Kinetic:
New
Status in fabric-manager-525 source package in Kinetic:
New
Status in libnvidia-nscq-450 source package in Kinetic:
New
Status in libnvidia-nscq-470 source package in Kinetic:
New
Status in libnvidia-nscq-525 source package in Kinetic:
New
Status in nvidia-graphics-drivers-450-server source package in Kinetic:
New
Status in nvidia-graphics-drivers-470 source package in Kinetic:
New
Status in nvidia-graphics-drivers-470-server source package in Kinetic:
New
Status in nvidia-graphics-drivers-525 source package in Kinetic:
New
Status in nvidia-graphics-drivers-525-server source package in Kinetic:
New
Status in nvidia-graphics-drivers-530 source package in Kinetic:
New
Status in fabric-manager-450 source package in Lunar:
New
Status in fabric-manager-470 source package in Lunar:
New
Status in fabric-manager-525 source package in Lunar:
New
Status in libnvidia-nscq-450 source package in Lunar:
New
Status in libnvidia-nscq-470 source package in Lunar:
New
Status in libnvidia-nscq-525 source package in Lunar:
New
Status in nvidia-graphics-drivers-450-server source package in Lunar:
New
Status in nvidia-graphics-drivers-470 source package in Lunar:
New
Status in nvidia-graphics-drivers-470-server source package in Lunar:
New
Status in nvidia-graphics-drivers-525 source package in Lunar:
New
Status in nvidia-graphics-drivers-525-server source package in Lunar:
New
Status in nvidia-graphics-drivers-530 source package in Lunar:
New
Bug description:
CVE-2023-25516, CVE-2023-25516
https://nvidia.custhelp.com/app/answers/detail/a_id/5468
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fabric-manager-450/+bug/2024675/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to :
[Kernel-packages] [Bug 2012571] Re: net/sched: cls_api: Support hardware miss to tc action
This bug is awaiting verification that the linux- bluefield/5.15.0-1019.21 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-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: verification-needed-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2012571 Title: net/sched: cls_api: Support hardware miss to tc action Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Focal: Fix Released Status in linux-bluefield source package in Jammy: Fix Committed Bug description: * Explain the bug(s) Currently tc miss interface only supports resuming from a specific tc chain. If a packet modification is done before a missable action such as CT and there is a miss in CT after it, this may cause a miss match when resuming re-executing the same chain in software, and wrong packet count. This use case for example is a stateless (static) nat. * brief explanation of fixes Add support for missing to a specific action instance, and support of per action hardware stats to update what was actually done in hardware. * How to test Create OVS bridge with 2 devices mlx5 rep devices. Enable HW offload and configure regular connection tracking OpenFlow rules with packet modification before the CT action (such as statless nat): e.g: ovs-ofctl del-flows br-ovs ovs-ofctl add-flow br-ovs arp,actions=normal ovs-ofctl add-flow br-ovs "in_port=1,table=0, ip,ct_state=-trk actions=mod_nw_dst=1.1.1.2,ct(table=1)" ovs-ofctl add-flow br-ovs "in_port=1,table=1, ip,ct_state=+trk+new actions=ct(commit),output:2" ovs-ofctl add-flow br-ovs "in_port=1,table=1, ip,ct_state=+trk+est, actions=output:2" ovs-ofctl add-flow br-ovs "in_port=2,table=0, ip,ct_state=-trk actions=ct(table=1)" ovs-ofctl add-flow br-ovs "in_port=2,table=1, ip,ct_state=+trk+est, actions=mod_nw_src=1.1.1.2,output:1" Config VF1 ip 1.1.1.1, VF2 ip 1.1.1.2 For VF2, add route and static neighbour to floating (router) ip 5.5.5.5 Then run a TCP connection, e.g: on mlx5 VF1 iperf -s #(which will listen on 1.1.1.2) on mlx5 VF2 iperf -c 5.5.5.5 -t 10#(this creates a packet from 1.1.1.1 -> 5.5.5.5, and nat will change this to 1.1.1.1->1.1.1.2) Optional: In different terminal, while traffic is running, check for offload: tcpdump -nnepi tcp and see no iperf tcp packets. Dump conntrack with relevant ip: cat /proc/net/nf_conntrack | grep -i 1.1.1.1 See tuples were offloaded: ipv4 2 tcp 6 src= 1.1.1.1 dst=1.1.1.2 sport=56394 dport=5001 packets=2 bytes=112 src=1.1.1.2 dst=1.1.1.1 sport=5001 dport=56394 packets=1777 bytes=665340 [HW_OFFLOAD] mark=0 zone=0 use=3 * What it could break. offload for modifications + ct and tc packet count. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2012571/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2015293] Re: netfilter: ctnetlink: Support offloaded conntrack entry deletion
This bug is awaiting verification that the linux- bluefield/5.15.0-1019.21 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-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: verification-needed-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2015293 Title: netfilter: ctnetlink: Support offloaded conntrack entry deletion Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Focal: Fix Released Status in linux-bluefield source package in Jammy: Fix Committed Bug description: * Explain the bug(s) conntrack -D or conntrack -F doesn't delete offloaded tuples. * brief explanation of fixes Add support for to delete offloaded tuples via netlink interface and userspace conntrack utility. * How to test Create OVS bridge with 2 devices mlx5 rep devices. Enable HW offload and configure regular connection tracking OpenFlow rules: e.g: ovs-ofctl del-flows br-ovs ovs-ofctl add-flow br-ovs arp,actions=normal ovs-ofctl add-flow br-ovs "table=0, ip,ct_state=-trk actions=ct(table=1)" ovs-ofctl add-flow br-ovs "table=1, ip,ct_state=+trk+new actions=ct(commit),normal" ovs-ofctl add-flow br-ovs "table=1, ip,ct_state=+trk+est, actions=normal" Run a UDP connection, e.g: on mlx5 VF1 iperf -s -u on mlx5 VF2 iperf -c -u -t 10 Optional: In different terminal, while traffic is running, check for offload: tcpdump -nnepi udp and see no iperf udp packets. Dump conntrack with relevant ip: cat /proc/net/nf_conntrack | grep -i See tuples were offloaded: ipv4 2 udp 17 src=1.1.1.2 dst=1.1.1.3 sport=56394 dport=5001 packets=2 bytes=112 src=1.1.1.3 dst=1.1.1.2 sport=5001 dport=56394 packets=1777 bytes=665340 [HW_OFFLOAD] mark=0 zone=0 use=3 Flush the tuples: conntrack -F Verify tuples are deleted: cat /proc/net/nf_conntrack | grep -i Before fix, the above tuple shows again, after fix, it's deleted, and shows nothing. * What it could break. Conntrack -F / -D not working on offloaded tuples. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2015293/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2021749] Re: mlxbf-tmfifo: robust fix to drop over-sized packet or no Rx descriptors
This bug is awaiting verification that the linux- bluefield/5.15.0-1019.21 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-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: verification-needed-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2021749 Title: mlxbf-tmfifo: robust fix to drop over-sized packet or no Rx descriptors Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Focal: Fix Committed Status in linux-bluefield source package in Jammy: Fix Committed Bug description: SRU Justification: [Impact] This change is needed to avoid potential tmfifo console stuck when network interface is down or receiving oversized packets. [Fix] Drop the Rx packets in the above cases. Since tmfifo is shared resource for both console and networking. Dropping such network packets can continue to process the fifo and avoid console stuck. [Test Case] Same functionality and testing as on BlueField-1/2/3. No functionality change. Add negative tests: 1. 'ifconfig tmfifo_net0 down' on ARM side during traffic, then verify rshim console doesn't stuck. 2. Config MTU to 4000 on rshim host and send oversized packet with command 'ping 192.168.100.2 -s 2000". It shouldn't cause any stuck. [Regression Potential] Same behavior from user perspective. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2021749/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2020606] Re: net: openvswitch: fix race on port output
This bug is awaiting verification that the linux-
bluefield/5.15.0-1019.21 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-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: verification-needed-jammy
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-bluefield in Ubuntu.
https://bugs.launchpad.net/bugs/2020606
Title:
net: openvswitch: fix race on port output
Status in linux-bluefield package in Ubuntu:
Invalid
Status in linux-bluefield source package in Focal:
Fix Committed
Status in linux-bluefield source package in Jammy:
Fix Committed
Bug description:
fix race on port output
* Explain the bug(s)
there is a race condition on port output
* brief explanation of fixes
We found that upstream linux has the same issue and fix
commit 066b86787fa3d97b7aefb5ac0a99a22dad2d15f8
Author: Felix Huettner
Date: Wed Apr 5 07:53:41 2023 +
net: openvswitch: fix race on port output
assume the following setup on a single machine:
1. An openvswitch instance with one bridge and default flows
2. two network namespaces "server" and "client"
3. two ovs interfaces "server" and "client" on the bridge
4. for each ovs interface a veth pair with a matching name and 32 rx and
tx queues
5. move the ends of the veth pairs to the respective network namespaces
6. assign ip addresses to each of the veth ends in the namespaces (needs
to be the same subnet)
7. start some http server on the server network namespace
8. test if a client in the client namespace can reach the http server
...
Fixes: 7f8a436eaa2c ("openvswitch: Add conntrack action")
Co-developed-by: Luca Czesla
Signed-off-by: Luca Czesla
Signed-off-by: Felix Huettner
Reviewed-by: Eric Dumazet
Reviewed-by: Simon Horman
Link: https://lore.kernel.org/r/ZC0pBXBAgh7c76CA@kernel-bug-kernel-bug
Signed-off-by: Jakub Kicinski
* How to test
After configuring QoS on BF-3:
Disable all priorities
Set priorities [0, 0, 0, 0, 0, 0, 0, 0]
Remove all policies
Remove all traffic classes
Add policy (policy_name=ND_traffic, traffic_type=RDMA, priority=5,
port=2, dscp=None)
Add policy (policy_name=TCP_traffic, traffic_type=TCP, priority=4,
port=26000, dscp=None)
Add traffic class two prio TC with prio_list=[5, 4], min_bw=76, algorithm=ETS
Enable QOS on adapter SLOT 5 Port 1
Restart driver (detach VFs -> restart with devcon -> attach VFs)
BF-3 sometimes stops responding. need to run it multiple times!
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2020606/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2024432] Re: net/sched: act_ct: Fix promotion of offloaded unreplied tuple
This bug is awaiting verification that the linux- bluefield/5.15.0-1019.21 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-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: verification-needed-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2024432 Title: net/sched: act_ct: Fix promotion of offloaded unreplied tuple Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Jammy: Fix Committed Bug description: * Explain the bug(s) Currently UNREPLIED and UNASSURED connections are added to the nf flow table. This causes the following connection packets to be processed by the flow table which then skips conntrack_in(), and thus such the connections will remain UNREPLIED and UNASSURED even if reply traffic is then seen. Even still, the unoffloaded reply packets are the ones triggering hardware update from new to established state, and if there aren't any to triger an update and/or previous update was missed, hardware can get out of sync with sw and still mark packets as new. * brief explanation of fixes 1) Not skipping conntrack_in() for UNASSURED packets, but still refresh for hardware, as before the cited patch. 2) Try and force a refresh by reply-direction packets that update the hardware rules from new to established state. 3) Remove any bidirectional flows that didn't failed to update in hardware for re-insertion as bidirectional once any new packet arrives. * How to test Create OVS bridge with 2 devices mlx5 rep devices. Enable HW offload and configure regular connection tracking OpenFlow rules: e.g: ovs-ofctl del-flows br-ovs ovs-ofctl add-flow br-ovs arp,actions=normal ovs-ofctl add-flow br-ovs "table=0, ip,ct_state=-trk actions=ct(table=1)" ovs-ofctl add-flow br-ovs "table=1, ip,ct_state=+trk+new actions=ct(commit),normal" ovs-ofctl add-flow br-ovs "table=1, ip,ct_state=+trk+est, actions=normal" Run a UDP single sided connection, e.g iperf without a server: on mlx5 VF2 iperf -t 1 -c -u -b 10pps Optional: In different terminal, while traffic is running, check for offload: tcpdump -nnepi udp and see no iperf udp packets. Dump conntrack with relevant ip: cat /proc/net/nf_conntrack | grep -i | grep "\[UNREPLIED\]" | grep -q "\[OFFLOAD\]" If tuple appears, tuple was offloaded, yet unreplied. * What it could break. The connections remain UNREPLIED and UNASSURED even if reply traffic is seen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2024432/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1995606] Re: Upgrade thermald to 2.5.1 for Jammy (22.04)
** Patch added: "thermald_jammy_2.4.9-1ubuntu0.3.v2.debdiff" https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1995606/+attachment/5682352/+files/thermald_jammy_2.4.9-1ubuntu0.3.v2.debdiff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1995606 Title: Upgrade thermald to 2.5.1 for Jammy (22.04) Status in OEM Priority Project: New Status in thermald package in Ubuntu: New Status in thermald source package in Jammy: Incomplete Bug description: [Justification] The purpose of this bug is that prevent the regression in the future. The automatic test scripts are better for the future SRU and is still on the planning. [Test case] For these CPU series, RPL/ADL/TGL/CML/CFL/KBL, the following tests will be run on machines in the CI lab: 1. Run stress-ng, and observe the temperature/frequency/power with s-tui - Temperatures should stay just below trip values - Power/performance profiles should stay roughly the same between old thermald and new thermald (unless specifically expected eg: to fix premature/insufficient throttling) 2. check if thermald could read rules from /dev/acpi_thermal_rel and generate the xml file on /etc/thermald/ correctly. - this depends on if acpi_thermal_rel exist. - if the machine suppots acpi_thermal_rel, the "thermal-conf.xml.auto" could be landed in etc/thermald/. - if not, the user-defined xml could be created, then jump to (3). - run thermald with --loglevel=debug, and compare the log with xml.auto file. check if the configuration could be parsed correctly. 3. check if theramd-conf.xml and thermal-cpu-cdev-order.xml can be loaded correctly. - run thermald with --loglevel=debug, and compare the log with xml files. - if parsed correctly, the configurations from XML files would appear in the log. 4. Run unit tests, the scripts are under test folder, using emul_temp to simulate the High temperatue and check thermald would throttle CPU through the related cooling device. - rapl.sh - intel_pstate.sh - powerclamp.sh - processor.sh 5. check if the power/frequency would be throttled once the temperature reach the trip-points of thermal zone. 6. check if system would be throttled even the temperature is under the trip-points. [ Where problems could occur ] since the PL1 min/max is introduced, there may have some cases that don't check the minimum of PL1 then make PL1 to smaller and smaller and throttle the CPU. this may cause machines run like the old behavior that doesn't have PL1 min/max. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1995606/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2022370] Re: mlxbf-gige: Fix kernel panic at shutdown
This bug is awaiting verification that the linux- bluefield/5.15.0-1019.21 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-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: verification-needed-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2022370 Title: mlxbf-gige: Fix kernel panic at shutdown Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Focal: Fix Committed Status in linux-bluefield source package in Jammy: Fix Committed Bug description: SRU Justification: [Impact] We occasionally see a race condition (once every 350 reboots) where napi is still running (mlxbf_gige_poll) while a shutdown has been initiated through "reboot". Since mlxbf_gige_poll is still running, it tries to access a NULL pointer and as a result causes a kernel panic. [Fix] The fix is to explicitly disable napi and dequeue it during shutdown. mlxbf_gige_remove already calls: unregister_netdev->unregister_netdevice->unregister_netdev_queue-> rollback_registered->rollback_registered_many->dev_close_many-> __dev_close_many->ndo_stop->mlxbf_gige_stop which stops napi So use mlxbf_gige_remove in place of the existing shutdown logic. [Test Case] * Issue at least 1000 reboots from linux and make sure there is no panic caused by the mlxbf-gige driver. [Regression Potential] * since this issue is hard to reproduce, it hasn't been tested thoroughly yet. so it needs several reboot loops to validate it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2022370/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2019264] Re: net/sched: act_ct: offload UDP NEW connections
This bug is awaiting verification that the linux- bluefield/5.15.0-1019.21 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-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: verification-needed-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2019264 Title: net/sched: act_ct: offload UDP NEW connections Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Jammy: Fix Committed Bug description: * Explain the bug(s) UDP single sided connections aren't offloaded. * brief explanation of fixes Add support for to offload single sided UDP connections by offloading only one side, and offloading the second side when/if it comes. * How to test Create OVS bridge with 2 devices mlx5 rep devices. Enable HW offload and configure regular connection tracking OpenFlow rules: e.g: ovs-ofctl del-flows br-ovs ovs-ofctl add-flow br-ovs arp,actions=normal ovs-ofctl add-flow br-ovs "table=0, ip,ct_state=-trk actions=ct(table=1)" ovs-ofctl add-flow br-ovs "table=1, ip,ct_state=+trk+new actions=ct(commit),normal" ovs-ofctl add-flow br-ovs "table=1, ip,ct_state=+trk+est, actions=normal" Run a UDP single sided connection, e.g iperf without a server: on mlx5 VF2 iperf -t 1 -c -u -b 10pps Optional: In different terminal, while traffic is running, check for offload: tcpdump -nnepi udp and see no iperf udp packets. Dump conntrack with relevant ip: cat /proc/net/nf_conntrack | grep -i | grep "\[UNREPLIED\]" | grep -q "\[OFFLOAD\]" If tuple appears, tuple was offloaded, yet unreplied. * What it could break. Single sided udp connections aren't offloaded. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2019264/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2016039] Re: mlxbf-tmfifo: fix potential race
This bug is awaiting verification that the linux- bluefield/5.15.0-1019.21 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-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: verification-needed-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2016039 Title: mlxbf-tmfifo: fix potential race Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Focal: In Progress Status in linux-bluefield source package in Jammy: Fix Committed Bug description: SRU Justification: [Impact] This change is needed to avoid potential race of accessing the 'vq' pointer [Fix] The fix adds memory barrier for the is_ready flag and the 'vq' pointer access in mlxbf_tmfifo_virtio_find_vqs(), so updated in vq will be visible before accessing this pointer. [Test Case] Same functionality and testing as on BlueField-1/2/2. No functionality change. [Regression Potential] Same behavior from user perspective. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2016039/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2024675] Re: NVIDIA CVE-2023-25515, CVE-2023-25516
** Also affects: nvidia-graphics-drivers-450-server (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: fabric-manager-450 (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: libnvidia-nscq-450 (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-470 (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-470-server (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: libnvidia-nscq-470 (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: fabric-manager-470 (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-525 (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-525-server (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: fabric-manager-525 (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: libnvidia-nscq-525 (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-530 (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-450-server (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: fabric-manager-450 (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: libnvidia-nscq-450 (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-470 (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-470-server (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: libnvidia-nscq-470 (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: fabric-manager-470 (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-525 (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-525-server (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: fabric-manager-525 (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: libnvidia-nscq-525 (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-530 (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-450-server (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: fabric-manager-450 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: libnvidia-nscq-450 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-470 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-470-server (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: libnvidia-nscq-470 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: fabric-manager-470 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-525 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-525-server (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: fabric-manager-525 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: libnvidia-nscq-525 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-530 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-450-server (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: fabric-manager-450 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: libnvidia-nscq-450 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-470 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-470-server (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: libnvidia-nscq-470 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: fabric-manager-470 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-525 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-525-server (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: fabric-manager-525 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: libnvidia-nscq-525 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-530 (Ubuntu Jammy) Importance: Undecided Status: New ** Information type changed from Private Security to Public
[Kernel-packages] [Bug 2025097] Re: uvcvideo issue with ubuntu 22.04 & 5.15.0.75 kernel
** Package changed: ubuntu => linux (Ubuntu) -- 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/2025097 Title: uvcvideo issue with ubuntu 22.04 & 5.15.0.75 kernel Status in linux package in Ubuntu: New Bug description: Using ubuntu 22.04 latest patches as at 27 June 2023, the USB 2 HD webcam fails to be recognised properly by the driver resulting in Cheese only giving lowest 160 x120 mono resolution. The USB Camera is being recognised properly as a USB device with expected features. Rebooting to 5.15.0.73 removes the issue. Same camera in Ubuntu 20.04.6 using same 5.15.0.75 kernel works fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2025097/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2020685] Re: System either hang with black screen or rebooted on entering suspend on AMD Ryzen 9 PRO 7940HS w/ Radeon 780M Graphics
verified linux-oem-6.1/jammy version 6.1.0-1015.15, linux/lunar version 6.2.0-25.25. ** Tags removed: verification-needed-jammy verification-needed-lunar ** Tags added: verification-done-jammy verification-done-lunar -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/2020685 Title: System either hang with black screen or rebooted on entering suspend on AMD Ryzen 9 PRO 7940HS w/ Radeon 780M Graphics Status in HWE Next: New Status in linux package in Ubuntu: Fix Released 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 Jammy: Invalid Status in linux-oem-6.0 source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in linux source package in Kinetic: Won't Fix 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 Committed Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: Fix Released Status in linux-oem-6.0 source package in Mantic: Invalid Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: [SRU Justfication] [Impact] On AMD Phoenix platforms, system may hang, or reboot while resuming from suspend. [Fix] Two patches in v6.4-rc3 for amdgpu. The first one is pulled for dependency. [Test Case] $ checkbox-cli run com.canonical.certification::suspend/suspend_advanced_auto $ checkbox-cli run com.canonical.certification::stress/s2idle_pm-graph_30 $ checkbox-cli run com.canonical.certification::power-management/suspend_30_cycles_with_reboots [Where problems could occur] The fix is to safely guard register access as it should be. No potential problem identified so far. [Other Info] This should affects v6.1 or above as which AMD Phoenix are supported, and has been included in mantic-6.3 through stable-6.3.4 and in oem-6.1 through stable-6.1.30, leaving lunar-6.2 unfixed only. == original bug report == To reproduce: ``` $ checkbox-cli run com.canonical.certification::suspend/suspend_advanced_auto # or $ checkbox-cli run com.canonical.certification::stress/s2idle_pm-graph_30 ``` Proposed fixes from AMD: * https://github.com/torvalds/linux/commit/5591a051b86be170a84943698ab140342602ff7b * https://github.com/torvalds/linux/commit/d5aa417808cf14c052ca042920b3c6b9f1dc6aa4 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1277 F pulseaudio /dev/snd/controlC1: ubuntu 1277 F pulseaudio CasperMD5CheckMismatches: ./preseed/project.cfg CasperMD5CheckResult: fail DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-jammy-amd64-20230421-366 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-04-21 (38 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - pc-stella-jammy-amd64-20230421-366 MachineType: HP HP ZBook Power 15.6 inch G10 A Mobile Workstation PC Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.1.0-1014-oem root=UUID=73c6b0d7-9459-43d9-b80d-40c2edef6621 ro automatic-oem-config quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.1.0-1014.14-oem 6.1.29 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.1.0-1014-oem N/A linux-backports-modules-6.1.0-1014-oem N/A linux-firmware 20220329.git681281e4-0ubuntu3.13 Tags: jammy Uname: Linux 6.1.0-1014-oem x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 05/08/2023 dmi.bios.release: 30.1 dmi.bios.vendor: HP dmi.bios.version: V85 Ver. 00.30.01 dmi.board.name: 8B95 dmi.board.vendor: HP dmi.board.version: KBC Version 59.1E.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 89.30 dmi.modalias: dmi:bvnHP:bvrV85Ver.00.30.01:bd05/08/2023:br30.1:efr89.30:svnHP:pnHPZBookPower15.6inchG10AMobileWorkstationPC:pvr:rvnHP:rn8B95:rvrKBCVersion59.1E.00:cvnHP:ct10:cvr:skuXW6SKU2#ABA: dmi.product.family: 103C_5336AN HP ZBook dmi.product.name: HP ZBook Power 15.6 inch G10 A Mobile Workstation PC dmi.product.sku: XW6SKU2#ABA
[Kernel-packages] [Bug 2023307] Re: System hang at reading amdgpu sysfs attribute psp_vbflash
verified linux-oem-6.1/6.1.0-1015.15. ** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/2023307 Title: System hang at reading amdgpu sysfs attribute psp_vbflash Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: New Status in linux source package in Jammy: Invalid Status in linux-oem-6.0 source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in linux source package in Kinetic: In Progress 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: In Progress Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: In Progress Status in linux-oem-6.0 source package in Mantic: Invalid Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: [Summary] 1. System hang on starting checkbox test. 2. Hang on collecting device information during start Auto and Stress test. 3. This issue exist on GPU with W7500 & W7600. [Steps to reproduce] 1. Boot into OS 2. Start Auto test or Stress test(checkbox-cli run com.canonical.certification::sysfs_attachment) AMD proposed fix in https://lore.kernel.org/amd-gfx/20230607065259.48516-1-mario.limoncie...@amd.com/T/#mc5c38f31129f23e498d669734cafe96474a8f8ba . --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: u 1442 F pulseaudio /dev/snd/controlC0: u 1442 F pulseaudio CasperMD5CheckResult: pass DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-jammy-amd64-20220504-33+jellyfish-tynamo+X81 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-05-16 (23 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - somerville-jammy-amd64-20220504-33 IwConfig: lono wireless extensions. enp5s0f0 no wireless extensions. enp4s0no wireless extensions. MachineType: Dell Inc. Precision 7875 Tower Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.1.0-1014-oem root=UUID=e9463c30-0a89-4838-a9fa-3296791ccd2a ro log_buf_len=64M quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.1.0-1014.14-oem 6.1.29 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.1.0-1014-oem N/A linux-backports-modules-6.1.0-1014-oem N/A linux-firmware 20220329.git681281e4-0ubuntu3.13 RfKill: Tags: jammy Uname: Linux 6.1.0-1014-oem x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 05/10/2023 dmi.bios.release: 0.4 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.4.28 dmi.board.vendor: Dell Inc. dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 0.18 dmi.modalias: dmi:bvnDellInc.:bvr0.4.28:bd05/10/2023:br0.4:efr0.18:svnDellInc.:pnPrecision7875Tower:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct3:cvr:sku0C61: dmi.product.family: Precision dmi.product.name: Precision 7875 Tower dmi.product.sku: 0C61 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2023307/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2021449] Re: ALSA: hda/realtek: Enable headset onLenovo M70/M90
** Changed in: linux (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2021449 Title: ALSA: hda/realtek: Enable headset onLenovo M70/M90 Status in OEM Priority Project: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Committed Bug description: [Impact] The headset couldn't work on M70/M90 Gen4 on 6.1.0-oem kernel and 5.19 generic kernel. Lenovo M70/M90 Gen4 are equipped with ALC897, and they need ALC897_FIXUP_HEADSET_MIC_PIN quirk to make its headset mic work. The previous quirk for M70/M90 is for Gen3. [Fix] cherry picked from commit 4ca110cab46561cd74a2acd9b447435acb4bec5f [Test] After applying the patch, the os works fine with the headset mic on 6.1.0-oem. [Where problems could occur] It's just a quirk for sound/pci/hda/patch_realtek.c, the risk is low. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2021449/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2023650] Re: Add microphone support of the front headphone port on P3 Tower
** Also affects: linux (Ubuntu Mantic) Importance: Undecided Status: In Progress ** Also affects: linux-oem-6.1 (Ubuntu Mantic) Importance: Undecided Status: Invalid ** Changed in: linux (Ubuntu Mantic) Assignee: (unassigned) => AaronMa (mapengyu) ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Assignee: (unassigned) => AaronMa (mapengyu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2023650 Title: Add microphone support of the front headphone port on P3 Tower Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in linux source package in Kinetic: Fix Committed Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: Fix Committed Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: In Progress Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: [Impact] The 3.5mm headphone port in front panel cannot detect the microphone. [Fix] Add quirk for headset mic pin on P3 Tower. [Test] Tested with alsa audio, mic works fine. [Where problems could occur] Low risk to add specific hardware ID. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2023650/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2023197] Re: Fix speaker volume too low on HP G10 laptops
** Changed in: linux-oem-6.1 (Ubuntu Jammy) Assignee: (unassigned) => Chris Chiu (mschiu77) ** Also affects: linux (Ubuntu Mantic) Importance: Undecided Status: Incomplete ** Also affects: linux-oem-6.1 (Ubuntu Mantic) Importance: Undecided Status: Invalid ** Changed in: linux (Ubuntu Mantic) Assignee: (unassigned) => Chris Chiu (mschiu77) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2023197 Title: Fix speaker volume too low on HP G10 laptops Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Incomplete Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in linux source package in Mantic: Incomplete Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: [ Impact ] HP G10 laptops need the quirk ALC245_FIXUP_CS35L41_SPI_4_HP_GPIO_LED to enable all amplifiers to output audio with expected level. [ Test Plan ] * Power up the HP G10 series laptops and adjust the output volume to MAX * Verify speaker output volume by ears. [ Where problems could occur ] * The quirk is for Cirrus codec on particular HP series laptops. * The risk of regression should only impact particular models To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2023197/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2023201] Re: Add support of Smart Amplifier IC ALC1319D on Intel platforms
** Changed in: linux-oem-6.1 (Ubuntu Jammy) Assignee: (unassigned) => Chris Chiu (mschiu77) ** Also affects: linux (Ubuntu Mantic) Importance: Undecided Status: Incomplete ** Also affects: linux-oem-6.1 (Ubuntu Mantic) Importance: Undecided Status: Invalid ** Changed in: linux (Ubuntu Mantic) Assignee: (unassigned) => Chris Chiu (mschiu77) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2023201 Title: Add support of Smart Amplifier IC ALC1319D on Intel platforms Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Incomplete Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in linux source package in Mantic: Incomplete Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: [Impact] Speaker is not functional on some Dell machines of Intel RPL platforms [Fix] Here's the patch submitted by Intel. https://patchwork.kernel.org/project/alsa-devel/patch/20230602202225.249209-16-pierre-louis.boss...@linux.intel.com/ [Test Case] 1. Power on the machine and open the audio settings 2. Verify it's not `Dummy Output` shown on the Audio output option [Where problems could occur] Only affect specific Intel RPL platforms. The risk of regression is low. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2023201/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2023220] Re: Some INVLPG implementations can leave Global translations unflushed when PCIDs are enabled
** Tags removed: verification-needed-lunar ** Tags added: verification-done-lunar ** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy verification-done-kinetic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2023220 Title: Some INVLPG implementations can leave Global translations unflushed when PCIDs are enabled Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Trusty: Incomplete Status in linux-oem-6.1 source package in Trusty: Invalid Status in linux source package in Xenial: Incomplete Status in linux-oem-6.1 source package in Xenial: Invalid Status in linux source package in Bionic: Incomplete Status in linux-oem-6.1 source package in Bionic: Invalid Status in linux source package in Focal: Fix Committed Status in linux-oem-6.1 source package in Focal: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in linux source package in Kinetic: Fix Committed Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: Fix Committed Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: Fix Released Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: [Impact] When PCIDs are enabled on Alder Lake and Raptor Lake, INVLPG will not flush the global TLB entries. This can lead to info leak or undefined behavior. [Mitigation] Boot with nopcid on affected systems. [Test case] There is no particular test case. [Potential regressions] This affects performance on the affected systems. TLB behavior could also be affected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2023220/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2023577] Re: cls_flower: off-by-one in fl_set_geneve_opt
** Tags removed: verification-needed-lunar ** Tags added: verification-done-lunar ** Tags added: verification-done-kinetic ** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2023577 Title: cls_flower: off-by-one in fl_set_geneve_opt Status in linux package in Ubuntu: Incomplete Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Kinetic: Fix Committed Status in linux source package in Lunar: Fix Committed Bug description: [Impact] An unprivileged user may cause an out-of-bounds write by setting up geneve options on the flower classifier. [Test case] https://seclists.org/oss-sec/2023/q2/219 [Potential regression] Users setting up geneve options on the flower tc classifier can be affected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2023577/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811254] Re: HP ProBook 470 G5, LED's in Hotkeys f5, f8 and f11 without function
Already in Bionic through stable update: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1837664 ** Changed in: linux (Ubuntu Bionic) Status: In Progress => 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/1811254 Title: HP ProBook 470 G5, LED's in Hotkeys f5, f8 and f11 without function Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Bug description: Notebook: HP ProBook 470 G5 (3KZ03EA) Distro: Linux Mint 19.1 Tessa Desktop: Cinnamon 4.0.8 Kernel: 4.15.0-43-generic x86_64 bits: 64 The functions of all hotkeys are given, but the LED's in the [f5] Speaker-mute, [f8] Micro-mute and [f11] Wireless on/off Buttons do not show the status. Disturbing is also the LED in [f11] permanently lit. This is my first bug report to launchpad and I ask for leniency and troubleshooting support. I created 12 logs, unfortunately the upload did not work at once: acpi_listen.txt apt-cache-policy dmesg.log lsb_release lsinput.log lspci-vnvn.log rfkill_list.txt udev-db.txt version.log xev keypress test.txt xkbcomp.txt xkbmap.txt Previous attempts: My on-board search for other HP ProBook Hotkey LED-issues led me to this bug report: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705586 but the solution to the file: /etc/modprobe.d/alsa-base.conf to supplement the entry: options snd-hda-intel mode = mute-led-gpio did not lead to the solution here. Presumably, the failure results from a different ubuntu-version and/or a another kernel. Information: This problem was previously discussed on linuxmintusers.de: https://www.linuxmintusers.de/index.php?topic=51737.msg710376#msg710376 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811254/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2024599] Re: linux-image-5.15.0-1032-realtime locks up under scheduler test load
And also occurs in Ubuntu Mantic with 6.3.0-7-generic -- 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/2024599 Title: linux-image-5.15.0-1032-realtime locks up under scheduler test load Status in apparmor package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in apparmor source package in Jammy: New Status in linux source package in Jammy: Incomplete Status in apparmor source package in Kinetic: New Status in linux source package in Kinetic: New Status in apparmor source package in Lunar: New Status in linux source package in Lunar: New Status in apparmor source package in Mantic: New Status in linux source package in Mantic: Incomplete Bug description: lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 22.04.2 LTS Release: 22.04 Codename: jammy uname -a Linux jammie-amd64-efi 5.15.0-1032-realtime #35-Ubuntu SMP PREEMPT_RT Tue Jan 24 11:45:03 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux free totalusedfree shared buff/cache available Mem: 4013888 200984 34390121204 373892 3744628 Swap:4014076 0 4014076 Running in a kvm-qemu, 8 cpus, cpu Intel Core Processor (Skylake, IBRS): how to reproduce issue: git clone https://github.com/ColinIanKing/stress-ng sudo apt-get update sudo apt-get build-dep stress-ng sudo apt-get install libeigen3-dev libmpfr-dev libkmod-dev libxxhash-dev libglvnd-dev libgbm-dev cd stress-ng make clean make -j 8 sudo ./stress-ng --class scheduler --all 1 -v --vmstat 1 -t 30m ..wait for all the stressors to get invoked, system becomes unresponsive, can't ^C stress-ng, can't swap consoles on the VM, appears to be hard locked. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2024599/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2025152] [NEW] kernel NULL pointer dereference on displayport connection loss
Public bug reported: I run this laptop with two external screens, using displayport daisy chaining, connected over USB-C. This crash happens when the daisy- chained screen loses connection. Here's a trace from the syslog: 2023-06-27T14:03:46.539822+02:00 parahippus kernel: [518130.334914] [drm] DM_MST: stopping TM on aconnector: b0b244c1 [id: 90] 2023-06-27T14:03:47.315820+02:00 parahippus kernel: [518131.110966] [drm] DP Alt mode state on HPD: 1 2023-06-27T14:03:47.439805+02:00 parahippus kernel: [518131.235885] [drm] DM_MST: starting TM on aconnector: b0b244c1 [id: 90] 2023-06-27T14:03:50.898600+02:00 parahippus kernel: [518132.646219] BUG: kernel NULL pointer dereference, address: 0008 2023-06-27T14:03:50.898614+02:00 parahippus kernel: [518132.646229] #PF: supervisor read access in kernel mode 2023-06-27T14:03:50.898616+02:00 parahippus kernel: [518132.646234] #PF: error_code(0x) - not-present page 2023-06-27T14:03:50.898619+02:00 parahippus kernel: [518132.646238] PGD 0 P4D 0 2023-06-27T14:03:50.898621+02:00 parahippus kernel: [518132.646244] Oops: [#1] PREEMPT SMP NOPTI 2023-06-27T14:03:50.898623+02:00 parahippus kernel: [518132.646250] CPU: 0 PID: 1130 Comm: Xorg Tainted: G OE 6.2.0-23-generic #23-Ubuntu 2023-06-27T14:03:50.898625+02:00 parahippus kernel: [518132.646256] Hardware name: TUXEDO TUXEDO Aura 15 Gen1/NL5xRU, BIOS 1.07.11RTR2 01/30/2023 2023-06-27T14:03:50.898627+02:00 parahippus kernel: [518132.646260] RIP: 0010:drm_dp_add_payload_part2+0xfe/0x130 [drm_display_helper] 2023-06-27T14:03:50.898629+02:00 parahippus kernel: [518132.646297] Code: e8 37 7e 2c f0 44 89 f0 5b 41 5c 41 5d 41 5e 5d 31 d2 31 c9 31 f6 31 ff 45 31 c0 45 31 c9 e9 b9 c2 8b f0 48 8b 80 58 05 00 00 <48> 8b 76 08 4c 8b 40 60 48 85 f6 74 04 48 8b 76 08 48 c7 c1 08 87 2023-06-27T14:03:50.898630+02:00 parahippus kernel: [518132.646302] RSP: 0018:b8250307b5b8 EFLAGS: 00010246 2023-06-27T14:03:50.898632+02:00 parahippus kernel: [518132.646307] RAX: 900132cf6000 RBX: 900132cf6000 RCX: 2023-06-27T14:03:50.898633+02:00 parahippus kernel: [518132.646311] RDX: 90013937e980 RSI: RDI: 900022a8a568 2023-06-27T14:03:50.898635+02:00 parahippus kernel: [518132.646314] RBP: b8250307b5d8 R08: R09: 2023-06-27T14:03:50.898637+02:00 parahippus kernel: [518132.646317] R10: R11: R12: 0001 2023-06-27T14:03:50.898638+02:00 parahippus kernel: [518132.646320] R13: 900022a8a000 R14: 900021bb48a0 R15: 0006 2023-06-27T14:03:50.898639+02:00 parahippus kernel: [518132.646324] FS: 7f26efa1ca80() GS:9006ef60() knlGS: 2023-06-27T14:03:50.898641+02:00 parahippus kernel: [518132.646328] CS: 0010 DS: ES: CR0: 80050033 2023-06-27T14:03:50.898642+02:00 parahippus kernel: [518132.646332] CR2: 0008 CR3: 00010e9a6000 CR4: 00350ef0 2023-06-27T14:03:50.898644+02:00 parahippus kernel: [518132.646336] Call Trace: 2023-06-27T14:03:50.898645+02:00 parahippus kernel: [518132.646339] 2023-06-27T14:03:50.898646+02:00 parahippus kernel: [518132.646346] dm_helpers_dp_mst_send_payload_allocation+0x90/0xd0 [amdgpu] 2023-06-27T14:03:50.898647+02:00 parahippus kernel: [518132.647146] dc_link_allocate_mst_payload+0x1a9/0x360 [amdgpu] 2023-06-27T14:03:50.898648+02:00 parahippus kernel: [518132.647911] core_link_enable_stream+0x5fc/0x650 [amdgpu] 2023-06-27T14:03:50.898650+02:00 parahippus kernel: [518132.647995] apply_single_controller_ctx_to_hw+0x416/0x4c0 [amdgpu] 2023-06-27T14:03:50.898651+02:00 parahippus kernel: [518132.647995] dce110_apply_ctx_to_hw+0x1f1/0x360 [amdgpu] 2023-06-27T14:03:50.898653+02:00 parahippus kernel: [518132.647995] ? dcn10_wait_for_mpcc_disconnect+0x51/0x220 [amdgpu] 2023-06-27T14:03:50.898654+02:00 parahippus kernel: [518132.647995] ? dcn20_prepare_bandwidth+0xc7/0x1c0 [amdgpu] 2023-06-27T14:03:50.898655+02:00 parahippus kernel: [518132.647995] dc_commit_state_no_check+0x313/0xd20 [amdgpu] 2023-06-27T14:03:50.898657+02:00 parahippus kernel: [518132.647995] dc_commit_state+0x127/0x160 [amdgpu] 2023-06-27T14:03:50.898658+02:00 parahippus kernel: [518132.647995] amdgpu_dm_atomic_commit_tail+0x60b/0x13e0 [amdgpu] 2023-06-27T14:03:50.898659+02:00 parahippus kernel: [518132.647995] ? dcn21_fast_validate_bw+0x4c4/0x6f0 [amdgpu] 2023-06-27T14:03:50.898661+02:00 parahippus kernel: [518132.647995] ? __kmem_cache_alloc_node+0x19d/0x340 2023-06-27T14:03:50.898662+02:00 parahippus kernel: [518132.647995] ? dcn21_validate_bandwidth_fp+0x15f/0x380 [amdgpu] 2023-06-27T14:03:50.898664+02:00 parahippus kernel: [518132.647995] ? kfree+0x78/0x120 2023-06-27T14:03:50.898665+02:00 parahippus kernel: [518132.647995] ? dcn21_validate_bandwidth_fp+0x15f/0x380 [amdgpu] 2023-06-27T14:03:50.898667+02:00 parahippus kernel: [518132.647995]
[Kernel-packages] [Bug 2025134] Re: Revert variable symbol length modversion in all the jammy kernels
** Also affects: linux-aws-6.2 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-aws-6.2 (Ubuntu)
Status: New => Confirmed
** Changed in: linux-aws-6.2 (Ubuntu)
Importance: Undecided => Medium
** Also affects: linux-azure-6.2 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-azure-6.2 (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux-azure-6.2 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.2 in Ubuntu.
https://bugs.launchpad.net/bugs/2025134
Title:
Revert variable symbol length modversion in all the jammy kernels
Status in linux-aws-6.2 package in Ubuntu:
Confirmed
Status in linux-azure-6.2 package in Ubuntu:
Confirmed
Status in linux-hwe-6.2 package in Ubuntu:
Fix Committed
Status in linux-lowlatency-hwe-6.2 package in Ubuntu:
Fix Committed
Bug description:
[Impact]
In order to support Rust in the kernel starting with Lunar we had to
apply the following UBUNTU SAUCE patch:
27c4fe11712c ("UBUNTU: SAUCE: modpost: support arbitrary symbol
length in modversion")
This patch can potentially introduce a user-space regression, because it
alters how the module names are stored in the modversion_info area.
Realistically it doesn't break anything, since this area is used only by the
kmod tools (and they've been verified to work fine also with this change
applied).
However, to be 100% that we don't introduce regressions it is safer to
simply revert this patch, considering that we don't provide kernel
Rust support in Jammy and without Rust this patch doesn't provide any
benefit.
[Fix]
In order to fix this we need to explicitly revert the patch in all the
Jammy kernels that are derived from any Lunar kernel.
To do so, after `cranky rebase`, run:
git revert -s 27c4fe11712c
The comment for the revert should report something like this:
```
Revert "UBUNTU: SAUCE: modpost: support arbitrary symbol length in
modversion"
This patch is required by Rust and it can potentially break user-space.
It is safer to revert this in all the kernel backported to old releases.
```
[Regression potential]
This revert is not very critical, realistically even with the variable
modversions patch applied we won't regress any known tool, however we
don't to risk to introduce potential user-space ABI changes. Fixing
this requires a slightly different action, respect to our usual
workflow, so if some kernels are shipped with the variable modversion
patch (for any reason), we may experience regressions with kmod-
related tools (e.g., scripts that are using modinfo, modprobe and
similar or custom tools that are parsing .ko sections directly).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-aws-6.2/+bug/2025134/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2000947] Re: UVC Quanta 0408:4035 camera PROBLEM
@Giuliano Lotta (giuliano69) Its will happen if we reinstall again so I buy the USB WEBCAM -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2000947 Title: UVC Quanta 0408:4035 camera PROBLEM Status in linux package in Ubuntu: Confirmed Bug description: I bought a Acer Nitro 5 AN517-55 with Quanta ACER HD User Facing', USB 0408:4035. The camera is reported to have problems by many users: https://linux-hardware.org/?id=usb:0408-4035 The uvc camera Quanta 0408:4035 does not work with ubuntu 22,04. the camera is “recongized” but fails installation. My console commands report similar info to other users: https://unix.stackexchange.com/questions/723504/integrated-camera-not-detected-working-on-acer-nitro-5-an515-58 PROPOSED SOLUTION I got in contact with laurent.pinch...@ideasonboard.com and with riba...@chromium.org , and subscribed to https://www.linuxtv.org/lists. And me...@vger.kernel.org mailinglist. Laurent proposed me a fix and I modified the 5,15 uvc_driver.c version, and loaded it on github https://github.com/Giuliano69/uvc_driver-for-Quanta-HD-User- Facing-0x0408-0x4035-/blob/main/uvc_driver.c I offered to test the fix, so I tried to compile the module with the new source. COMPILING PROBLEMS I’m running **Ubuntu 22.04.1 LTS, with kernel giuliano@Astra2A:/usr/src$ cat /proc/version_signature Ubuntu 5.15.0-56.62-generic 5.15.64 BUT the linux-source that I found installed seems to be different tgiuliano@Astra2A:/usr/src$ ls -al linux-so* lrwxrwxrwx 1 root root 47 nov 22 16:08 linux-source-5.15.0.tar.bz2 -> linux-source-5.15.0/linux-source-5.15.0.tar.bz2 I expanded the tar file, configured the IDE and compiled without error any errors… I manually copied the uvcvideo.ko in /lib/modules/5.15.0-56- sudo cp…... then tryed to intall the new uvcvideo.ko module sudo rmmod uvcvideo && sudo modprobe uvcvideo BUT… IT FAILS giuliano@Astra2A:~$ sudo rmmod uvcvideo && sudo modprobe uvcvideo modprobe: ERROR: could not insert 'uvcvideo': Exec format error and dmesg shows [25961.151982] usbcore: registered new interface driver uvcvideo [26323.125534] usbcore: deregistering interface driver uvcvideo [26323.189294] uvcvideo: disagrees about version of symbol module_layout These are the TWO modinfo from the old and new uvcvideo modules https://pastebin.com/tSj8Exm6 Basically OLD module: vermagic: 5.15.0-56-generic SMP mod_unload modversions NEW module: vermagic: 5.15.64 SMP mod_unload modversions -kindly ASK HOW can FORCE the uvcdriver.c to match mi kernel version ? Have I got OTHER ways to make the kernel module I’m compiling, match my running system ? I would like to test the module so to confirm the patch and let it enter the kernel main stream... BR Giuliano PS btw…. to allow Eclipse to compile the kernel, I had to pass this commands scripts/config --disable CONFIG_SYSTEM_REVOCATION_KEYS scripts/config --disable SYSTEM_REVOCATION_KEYS scripts/config --disable SYSTEM_TRUSTED_KEYS hope that this does not affect the module layout & checking --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: giuliano 2142 F pulseaudio /dev/snd/pcmC1D0p: giuliano 2142 F...m pulseaudio /dev/snd/controlC0: giuliano 2142 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-11-03 (66 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Acer Nitro AN517-55 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-57-generic root=UUID=f07e25f9-07e7-4a29-a15e-f481aa0ee0f2 ro rootflags=subvol=@ quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-57.63-generic 5.15.74 RelatedPackageVersions: linux-restricted-modules-5.15.0-57-generic N/A linux-backports-modules-5.15.0-57-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.9 Tags: jammy Uname: Linux 5.15.0-57-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 04/20/2022 dmi.bios.release: 1.6 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.06 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Ignis_ADH dmi.board.vendor: ADL dmi.board.version: V1.06 dmi.chassis.type: 10 dmi.chassis.vendor: Acer
[Kernel-packages] [Bug 2019011] Comment bridged from LTC Bugzilla
--- Comment From boris.m...@de.ibm.com 2023-06-27 07:04 EDT--- Sorry for the premature closing of this bug. Reopening this item as the fix needs to be released in Focal LTS by Canonical first, before we can close. -- 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/2019011 Title: [UBUNTU 20.04] [HPS] Kernel panic with "refcount_t: underflow" in mlx5 driver Status in Ubuntu on IBM z Systems: New Status in linux package in Ubuntu: New Status in linux source package in Focal: In Progress Bug description: ---Problem Description--- Kernel panic with "refcount_t: underflow" in kernel log Contact Information = rijo...@ibm.com, vineeth.vija...@ibm.com ---uname output--- 5.4.0-128-generic Machine Type = s390x ---System Hang--- Kernel panic and stack-trace as below ---Debugger--- A debugger is not configured Stack trace output: [Sat Apr 8 17:52:21 UTC 2023] Call Trace: [Sat Apr 8 17:52:21 UTC 2023] ([<002a5939a286>] refcount_warn_saturate+0xce/0x140) [Sat Apr 8 17:52:21 UTC 2023] [<03ff805f861e>] cmd_ent_put+0xe6/0xf8 [mlx5_core] [Sat Apr 8 17:52:21 UTC 2023] [<03ff805f9b6a>] mlx5_cmd_comp_handler+0x102/0x4f0 [mlx5_core] [Sat Apr 8 17:52:21 UTC 2023] [<03ff805f9f8a>] cmd_comp_notifier+0x32/0x48 [mlx5_core] [Sat Apr 8 17:52:21 UTC 2023] [<002a58ecf0c6>] notifier_call_chain+0x4e/0xa0 [Sat Apr 8 17:52:21 UTC 2023] [<002a58ecf17e>] atomic_notifier_call_chain+0x2e/0x40 [Sat Apr 8 17:52:21 UTC 2023] [<03ff805fe4fc>] mlx5_eq_async_int+0x13c/0x200 [mlx5_core] [Sat Apr 8 17:52:21 UTC 2023] [<002a58ecf0c6>] notifier_call_chain+0x4e/0xa0 [Sat Apr 8 17:52:21 UTC 2023] [<002a58ecf17e>] atomic_notifier_call_chain+0x2e/0x40 [Sat Apr 8 17:52:21 UTC 2023] [<03ff8061318e>] mlx5_irq_int_handler+0x2e/0x48 [mlx5_core] [Sat Apr 8 17:52:21 UTC 2023] [<002a58f1455a>] __handle_irq_event_percpu+0x6a/0x250 [Sat Apr 8 17:52:21 UTC 2023] [<002a58f14770>] handle_irq_event_percpu+0x30/0x78 [Sat Apr 8 17:52:21 UTC 2023] [<002a58f1a0c8>] handle_percpu_irq+0x68/0xa0 [Sat Apr 8 17:52:21 UTC 2023] [<002a58f134d2>] generic_handle_irq+0x3a/0x60 [Sat Apr 8 17:52:21 UTC 2023] [<002a58e960ce>] zpci_floating_irq_handler+0xe6/0x1b8 [Sat Apr 8 17:52:21 UTC 2023] [<002a594f54a6>] do_airq_interrupt+0x96/0x130 [Sat Apr 8 17:52:21 UTC 2023] [<002a58f1455a>] __handle_irq_event_percpu+0x6a/0x250 [Sat Apr 8 17:52:21 UTC 2023] [<002a58f14770>] handle_irq_event_percpu+0x30/0x78 [Sat Apr 8 17:52:21 UTC 2023] [<002a58f1a0c8>] handle_percpu_irq+0x68/0xa0 [Sat Apr 8 17:52:21 UTC 2023] [<002a58f134d2>] generic_handle_irq+0x3a/0x60 [Sat Apr 8 17:52:21 UTC 2023] [<002a58e30e42>] do_IRQ+0x7a/0xb0 [Sat Apr 8 17:52:21 UTC 2023] [<002a5972a408>] io_int_handler+0x12c/0x294 [Sat Apr 8 17:52:21 UTC 2023] [<002a58e2752e>] enabled_wait+0x46/0xd8 [Sat Apr 8 17:52:21 UTC 2023] ([<002a58e2752e>] enabled_wait+0x46/0xd8) [Sat Apr 8 17:52:21 UTC 2023] [<002a58e278aa>] arch_cpu_idle+0x2a/0x40 [Sat Apr 8 17:52:21 UTC 2023] [<002a58ee1536>] do_idle+0xee/0x1b0 [Sat Apr 8 17:52:21 UTC 2023] [<002a58ee17a6>] cpu_startup_entry+0x36/0x40 [Sat Apr 8 17:52:21 UTC 2023] [<002a58e3ab38>] smp_init_secondary+0xc8/0xe8 [Sat Apr 8 17:52:21 UTC 2023] [<002a58e3a770>] smp_start_secondary+0x88/0x90 [Sat Apr 8 17:52:21 UTC 2023] [<002a5972a09c>] kernel_thread_starter+0x0/0x10 [Sat Apr 8 17:52:21 UTC 2023] Last Breaking-Event-Address: [Sat Apr 8 17:52:21 UTC 2023] [<002a5939a286>] refcount_warn_saturate+0xce/0x140 [Sat Apr 8 17:52:21 UTC 2023] ---[ end trace 6ec6f9c6f666ca2d ]--- [Sat Apr 8 17:52:21 UTC 2023] specification exception: 0006 ilc:3 [#1] SMP [Sat Apr 8 17:52:21 UTC 2023] Modules linked in: sysdigcloud_probe(OE) vhost_net vhost macvtap macvlan tap rpcsec_gss_krb5 auth_rpcgss nfsv3 nfs_acl nfs lockd grace fscache ebtable_broute binfmt_misc nbd veth xt_statistic ipt_REJECT nf_reject_ipv4 ip_vs_sh ip_vs_wrr ip_vs_rr ip_vs iptable_mangle ip6table_mangle ip6table_nat xt_mark sunrpc lcs ctcm fsm zfcp scsi_transport_fc dasd_fba_mod dasd_eckd_mod dasd_mod nf_log_ipv6 nf_log_ipv4 nf_log_common xt_LOG xt_limit xt_tcpudp xt_multiport xt_set ip_set_hash_net ip_set_hash_ip ip_set tcp_diag inet_diag xt_comment xt_nat act_gact sch_multiq act_mirred act_pedit act_tunnel_key cls_flower act_police cls_u32 vxlan ip6_udp_tunnel udp_tunnel dummy sch_ingress mlx5_ib ib_uverbs ib_core mlx5_core tls mlxfw ptp pps_core xt_MASQUERADE iptable_nat xt_addrtype xt_conntrack br_netfilter bridge stp llc aufs ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter bpfilter xfrm_user xfrm4_tunnel tunnel4 ipcomp xfrm_ipcomp esp4 ah4 af_key xfr m_algo
[Kernel-packages] [Bug 2019011] Comment bridged from LTC Bugzilla
--- Comment From boris.m...@de.ibm.com 2023-06-27 06:45 EDT--- The cloud team did some testing with the fixed Focal -gt version. The problem did not appear anymore, therefore I think we can close this bugzilla / LP item. Thanks to everybody for your work. ==> Changing the status to: CLOSED -- 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/2019011 Title: [UBUNTU 20.04] [HPS] Kernel panic with "refcount_t: underflow" in mlx5 driver Status in Ubuntu on IBM z Systems: New Status in linux package in Ubuntu: New Status in linux source package in Focal: In Progress Bug description: ---Problem Description--- Kernel panic with "refcount_t: underflow" in kernel log Contact Information = rijo...@ibm.com, vineeth.vija...@ibm.com ---uname output--- 5.4.0-128-generic Machine Type = s390x ---System Hang--- Kernel panic and stack-trace as below ---Debugger--- A debugger is not configured Stack trace output: [Sat Apr 8 17:52:21 UTC 2023] Call Trace: [Sat Apr 8 17:52:21 UTC 2023] ([<002a5939a286>] refcount_warn_saturate+0xce/0x140) [Sat Apr 8 17:52:21 UTC 2023] [<03ff805f861e>] cmd_ent_put+0xe6/0xf8 [mlx5_core] [Sat Apr 8 17:52:21 UTC 2023] [<03ff805f9b6a>] mlx5_cmd_comp_handler+0x102/0x4f0 [mlx5_core] [Sat Apr 8 17:52:21 UTC 2023] [<03ff805f9f8a>] cmd_comp_notifier+0x32/0x48 [mlx5_core] [Sat Apr 8 17:52:21 UTC 2023] [<002a58ecf0c6>] notifier_call_chain+0x4e/0xa0 [Sat Apr 8 17:52:21 UTC 2023] [<002a58ecf17e>] atomic_notifier_call_chain+0x2e/0x40 [Sat Apr 8 17:52:21 UTC 2023] [<03ff805fe4fc>] mlx5_eq_async_int+0x13c/0x200 [mlx5_core] [Sat Apr 8 17:52:21 UTC 2023] [<002a58ecf0c6>] notifier_call_chain+0x4e/0xa0 [Sat Apr 8 17:52:21 UTC 2023] [<002a58ecf17e>] atomic_notifier_call_chain+0x2e/0x40 [Sat Apr 8 17:52:21 UTC 2023] [<03ff8061318e>] mlx5_irq_int_handler+0x2e/0x48 [mlx5_core] [Sat Apr 8 17:52:21 UTC 2023] [<002a58f1455a>] __handle_irq_event_percpu+0x6a/0x250 [Sat Apr 8 17:52:21 UTC 2023] [<002a58f14770>] handle_irq_event_percpu+0x30/0x78 [Sat Apr 8 17:52:21 UTC 2023] [<002a58f1a0c8>] handle_percpu_irq+0x68/0xa0 [Sat Apr 8 17:52:21 UTC 2023] [<002a58f134d2>] generic_handle_irq+0x3a/0x60 [Sat Apr 8 17:52:21 UTC 2023] [<002a58e960ce>] zpci_floating_irq_handler+0xe6/0x1b8 [Sat Apr 8 17:52:21 UTC 2023] [<002a594f54a6>] do_airq_interrupt+0x96/0x130 [Sat Apr 8 17:52:21 UTC 2023] [<002a58f1455a>] __handle_irq_event_percpu+0x6a/0x250 [Sat Apr 8 17:52:21 UTC 2023] [<002a58f14770>] handle_irq_event_percpu+0x30/0x78 [Sat Apr 8 17:52:21 UTC 2023] [<002a58f1a0c8>] handle_percpu_irq+0x68/0xa0 [Sat Apr 8 17:52:21 UTC 2023] [<002a58f134d2>] generic_handle_irq+0x3a/0x60 [Sat Apr 8 17:52:21 UTC 2023] [<002a58e30e42>] do_IRQ+0x7a/0xb0 [Sat Apr 8 17:52:21 UTC 2023] [<002a5972a408>] io_int_handler+0x12c/0x294 [Sat Apr 8 17:52:21 UTC 2023] [<002a58e2752e>] enabled_wait+0x46/0xd8 [Sat Apr 8 17:52:21 UTC 2023] ([<002a58e2752e>] enabled_wait+0x46/0xd8) [Sat Apr 8 17:52:21 UTC 2023] [<002a58e278aa>] arch_cpu_idle+0x2a/0x40 [Sat Apr 8 17:52:21 UTC 2023] [<002a58ee1536>] do_idle+0xee/0x1b0 [Sat Apr 8 17:52:21 UTC 2023] [<002a58ee17a6>] cpu_startup_entry+0x36/0x40 [Sat Apr 8 17:52:21 UTC 2023] [<002a58e3ab38>] smp_init_secondary+0xc8/0xe8 [Sat Apr 8 17:52:21 UTC 2023] [<002a58e3a770>] smp_start_secondary+0x88/0x90 [Sat Apr 8 17:52:21 UTC 2023] [<002a5972a09c>] kernel_thread_starter+0x0/0x10 [Sat Apr 8 17:52:21 UTC 2023] Last Breaking-Event-Address: [Sat Apr 8 17:52:21 UTC 2023] [<002a5939a286>] refcount_warn_saturate+0xce/0x140 [Sat Apr 8 17:52:21 UTC 2023] ---[ end trace 6ec6f9c6f666ca2d ]--- [Sat Apr 8 17:52:21 UTC 2023] specification exception: 0006 ilc:3 [#1] SMP [Sat Apr 8 17:52:21 UTC 2023] Modules linked in: sysdigcloud_probe(OE) vhost_net vhost macvtap macvlan tap rpcsec_gss_krb5 auth_rpcgss nfsv3 nfs_acl nfs lockd grace fscache ebtable_broute binfmt_misc nbd veth xt_statistic ipt_REJECT nf_reject_ipv4 ip_vs_sh ip_vs_wrr ip_vs_rr ip_vs iptable_mangle ip6table_mangle ip6table_nat xt_mark sunrpc lcs ctcm fsm zfcp scsi_transport_fc dasd_fba_mod dasd_eckd_mod dasd_mod nf_log_ipv6 nf_log_ipv4 nf_log_common xt_LOG xt_limit xt_tcpudp xt_multiport xt_set ip_set_hash_net ip_set_hash_ip ip_set tcp_diag inet_diag xt_comment xt_nat act_gact sch_multiq act_mirred act_pedit act_tunnel_key cls_flower act_police cls_u32 vxlan ip6_udp_tunnel udp_tunnel dummy sch_ingress mlx5_ib ib_uverbs ib_core mlx5_core tls mlxfw ptp pps_core xt_MASQUERADE iptable_nat xt_addrtype xt_conntrack br_netfilter bridge stp llc aufs ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter bpfilter
[Kernel-packages] [Bug 2020279] Re: Kernel warning after upgrade to 4.15.0.211.194
** Tags added: verification-done-bionic -- 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: Confirmed Status in linux source package in Bionic: Fix Committed 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 esolr kernel: [ 18.787923] __netif_receive_skb_core+0x432/0xb80 May 21 19:09:59 esolr kernel: [
[Kernel-packages] [Bug 2022826] Re: Ethernet hangs
A Realtek Ethernet Controller was on my old PC and it is on my new MinisForum MC560 PC and it is on my old Lenovo laptop. My old PC had an Intel AX200 wireless interface; my old Lenovo laptop has a Realtek wireless interface; my new PC has a MEDIATEK wireless interface. So there seems to be nothing in common between the problem PCs (old PC & new PC) which the Lenovo laptop has, except that the problem PCs are AMD Ryzen processors and the Lenovo laptop is a Pentium 1 processor! My new PC doesn't even have WireGuard on it whereas my old PC had WireGuard on it, as I've decided to use a Raspberry Pi model 4 B for that. Here is network details for new PC: john@Desktop:~$ sudo lshw -C network *-network description: Ethernet interface product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:01:00.0 logical name: eno1 version: 15 serial: 58:47:ca:70:a0:ea size: 100Mbit/s capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=5.19.0-45-generic duplex=full firmware=rtl8168h-2_0.0.2 02/26/15 latency=0 link=yes multicast=yes port=twisted pair speed=100Mbit/s resources: irq:24 ioport:f000(size=256) memory:fcf04000-fcf04fff memory:fcf0-fcf03fff *-network description: Wireless interface product: MEDIATEK Corp. vendor: MEDIATEK Corp. physical id: 0 bus info: pci@:02:00.0 logical name: wlp2s0 version: 00 serial: 10:6f:d9:cf:d1:69 width: 64 bits clock: 33MHz capabilities: pciexpress msi pm bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=mt7921e driverversion=5.19.0-45-generic firmware=01-20220209150915 ip=192.168.1.110 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: irq:67 memory:e030-e03f memory:e040-e0403fff memory:e0404000-e0404fff john@Desktop:~$ ifconfig eno1: flags=4163 mtu 1500 ether 58:47:ca:70:a0:ea txqueuelen 1000 (Ethernet) RX packets 79903 bytes 6374933 (6.3 MB) RX errors 0 dropped 35 overruns 0 frame 0 TX packets 3769 bytes 871473 (871.4 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 lo: flags=73 mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10 loop txqueuelen 1000 (Local Loopback) RX packets 28449 bytes 3223428 (3.2 MB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 28449 bytes 3223428 (3.2 MB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 wlp2s0: flags=4163 mtu 1500 inet 192.168.1.110 netmask 255.255.255.0 broadcast 192.168.1.255 inet6 fe80::d63e:3edb:8f82:6f7f prefixlen 64 scopeid 0x20 ether 10:6f:d9:cf:d1:69 txqueuelen 1000 (Ethernet) RX packets 2172914 bytes 1928088175 (1.9 GB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 666334 bytes 168574947 (168.5 MB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2022826 Title: Ethernet hangs Status in linux-firmware package in Ubuntu: New Bug description: I'm now getting my wired (i.e. Ethernet) connection hanging on trying to connect. I've tried switching ports (on the router) and using a different cable, but still the same. ifconfig shows for Ethernet: enp2s0: flags=4163 mtu 1500 ether 50:eb:f6:ef:a4:e6 txqueuelen 1000 (Ethernet) RX packets 2779 bytes 250524 (250.5 KB) RX errors 0 dropped 1 overruns 0 frame 0 TX packets 355 bytes 72171 (72.1 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 sudo lshw -C enp2s0 shows nothing lspci -nn shows for Ethernet: 02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller [10ec:8125] (rev 05) I found a web page: https://tutorialforlinux.com/2021/05...based-systems/ I followed the instructions and installed realtek-r8125-dkms package OK. On rebooting, I followed the instructed procedure (shown when installing the package) of creating a password and then entering it when requested on the reboot. But still same problem. Any ideas what to do? PS I've switched Wi-Fi on (though I'd prefer to use Ethernet, as my Wi-Fi is a little flaky due to walls) in order to post this question. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-firmware 20220329.git681281e4-0ubuntu3.13 ProcVersionSignature: Ubuntu
[Kernel-packages] [Bug 1918085] Re: Package linux-crashdump in 20.04 configures kernel cmdline crashkernel incorrectly causing lock-up on kernel dump
Yeah, 22.04. sudo dmesg | grep 'command line' [0.045410] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.19.0-45-generic root=UUID=xxx ro crashkernel=512M-:192M [0.045459] Unknown kernel command line parameters "BOOT_IMAGE=/boot/vmlinuz-5.19.0-45-generic", will be passed to user space. -- 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/1918085 Title: Package linux-crashdump in 20.04 configures kernel cmdline crashkernel incorrectly causing lock-up on kernel dump Status in linux-meta package in Ubuntu: Confirmed Bug description: Package linux-crashdump in 20.04 configures kernel cmdline crashkernel incorrectly causing lock-up on kernel dump. It is very simple to replicate. I was testing using QEmu virtualisation software, where I had QEmu running a 20.04 install within another 20.04 install. Within the virtualisation install, simply install the package "linux-crashdump": $ sudo apt install linux-crashdump Answering Yes and Yes to the two questions asked: || Configuring kexec-tools || | | | | | If you choose this option, a system reboot will trigger a restart into a | | kernel loaded by kexec instead of going through the full system boot | | loader process. | | | | Should kexec-tools handle reboots (sysvinit only)?| | | | | | | |---| || Configuring kdump-tools || | | | | | If you choose this option, the kdump-tools mechanism will be enabled. A | | reboot is still required in order to enable the crashkernel kernel| | parameter.| | | | Should kdump-tools be enabled be default? | | | | | | | |---| Check the kernel command-line Grub configured by package install: $ cat /proc/cmdline BOOT_IMAGE=/vmlinuz-5.4.0-66-lowlatency root=/dev/mapper/rootlvm-rootpart ro crashkernel=512M-:192M As you can see "crashkernel=512M-:192M" is definitely a syntax error. Furthermore, when I test with this default configuration by forcing a crash: Enable dump then reboot testing with the following command: sudo sysctl -w kernel.sysrq=1 Once this is done, you must become root, as just using sudo will not be sufficient. As the root user, you will have to issue the command echo c > /proc/sysrq-trigger. Once the "echo c > /proc/sysrq-trigger" command is issued as root, the virtual host being tested locks-up at 100% CPU indefinitely. Forcing shutdown and reboot shows no crash file in /var/crash folder however I can only see files "kexec_cmd" and "kdump_lock". To manually fix this issue I changed to "crashkernel=512M-:192M" to "crashkernel=384M-:512M" by editing (i.e. make the small number/larger number order correct): $ sudo vim /etc/default/grub.d/kdump-tools.cfg GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=384M-:512M" After reboot and retest of the forced crash commands, the kdump works and all the needed files are present after self-reboot: $ ls /var/crash/ 202103081345 kdump_lock kexec_cmd linux-image-5.4.0-66-lowlatency-202103081345.crash $ ls /var/crash/202103081345/ dmesg.202103081345 dump.202103081345 In summary the problem is that the default kernel command-line configured by default "crashkernel=512M-:192M" is faulty in some way or other and causes the kernel to lock-up at 100% CPU indefinitely when kdump is triggered. This can be manually fixed giving a workaround but future user will suffer until the default installation configuration is fixed. To manage notifications about this bug go to:
[Kernel-packages] [Bug 2006797] Re: MT7922 firmware not working
Reproduced on ASUS G14 Laptop (model number GA402NV). Ubuntu 23.04 6.2.0-23-generic `dmesg | grep mt7` gives the following - ``` [ 14.665322] mt7921e :03:00.0: ASIC revision: 79220010 [ 17.955295] mt7921e :03:00.0: Message 0010 (seq 1) timeout [ 17.955309] mt7921e :03:00.0: Failed to get patch semaphore [ 21.287296] mt7921e :03:00.0: Message 0010 (seq 2) timeout [ 21.287325] mt7921e :03:00.0: Failed to get patch semaphore [ 24.611295] mt7921e :03:00.0: Message 0010 (seq 3) timeout [ 24.611309] mt7921e :03:00.0: Failed to get patch semaphore [ 27.939637] mt7921e :03:00.0: Message 0010 (seq 4) timeout [ 27.939653] mt7921e :03:00.0: Failed to get patch semaphore [ 31.267262] mt7921e :03:00.0: Message 0010 (seq 5) timeout [ 31.267268] mt7921e :03:00.0: Failed to get patch semaphore [ 34.599284] mt7921e :03:00.0: Message 0010 (seq 6) timeout [ 34.599294] mt7921e :03:00.0: Failed to get patch semaphore [ 37.923354] mt7921e :03:00.0: Message 0010 (seq 7) timeout [ 37.923371] mt7921e :03:00.0: Failed to get patch semaphore [ 41.251277] mt7921e :03:00.0: Message 0010 (seq 8) timeout [ 41.251289] mt7921e :03:00.0: Failed to get patch semaphore [ 44.579666] mt7921e :03:00.0: Message 0010 (seq 9) timeout [ 44.579681] mt7921e :03:00.0: Failed to get patch semaphore [ 47.907627] mt7921e :03:00.0: Message 0010 (seq 10) timeout [ 47.907641] mt7921e :03:00.0: Failed to get patch semaphore [ 47.989282] mt7921e :03:00.0: hardware init failed ``` Occasionally after a reboot I instead see the following: ``` [ 19.143835] mt7921e :03:00.0: driver own failed [ 19.143886] mt7921e: probe of :03:00.0 failed with error -5 ``` Have tried all suggested workarounds including disconnecting the battery, no change. -- 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/2006797 Title: MT7922 firmware not working Status in linux package in Ubuntu: Confirmed Bug description: Hey I have a "ASUS ROG Strix B650-A Gaming WIFI" (https://rog.asus.com/motherboards/rog-strix/rog-strix-b650-a-gaming- wifi-model/) Motherboard and the WiFi/Bluetooth is not working. On windows, the module is working fine. Using "Kubuntu 22.10" with Kernel "5.19.0-35-generic" lshw -class network: *-network description: Network controller product: MT7922 802.11ax PCI Express Wireless Network Adapter vendor: MEDIATEK Corp. physical id: 0 bus info: pci@:0b:00.0 version: 00 width: 64 bits clock: 33MHz capabilities: pciexpress msi pm bus_master cap_list configuration: driver=mt7921e latency=0 resources: iomemory:fc0-fbf irq:119 memory:fc3030-fc303f memory:fc50-fc507fff #dmesg | grep mt7921e [ 17.001057] mt7921e :0b:00.0: enabling device ( -> 0002) [ 17.001199] mt7921e :0b:00.0: ASIC revision: 79220010 [ 20.247369] mt7921e :0b:00.0: Message 0004008a (seq 1) timeout [ 23.575534] mt7921e :0b:00.0: Message 0004008a (seq 2) timeout [ 26.907372] mt7921e :0b:00.0: Message 0004008a (seq 3) timeout [ 30.231376] mt7921e :0b:00.0: Message 0004008a (seq 4) timeout [ 33.559704] mt7921e :0b:00.0: Message 0004008a (seq 5) timeout [ 36.887365] mt7921e :0b:00.0: Message 0004008a (seq 6) timeout [ 40.215367] mt7921e :0b:00.0: Message 0004008a (seq 7) timeout [ 43.543670] mt7921e :0b:00.0: Message 0004008a (seq 8) timeout [ 46.871378] mt7921e :0b:00.0: Message 0004008a (seq 9) timeout [ 50.199714] mt7921e :0b:00.0: Message 0004008a (seq 10) timeout [ 50.280219] mt7921e :0b:00.0: hardware init failed ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-35-generic 5.19.0-35.36 ProcVersionSignature: Ubuntu 5.19.0-35.36-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Fri Feb 10 03:33:02 2023 InstallationDate: Installed on 2023-02-09 (0 days ago) InstallationMedia: Kubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: ASUS System Product Name ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-35-generic root=/dev/mapper/vgkubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.19.0-35-generic N/A linux-backports-modules-5.19.0-35-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1.4 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/21/2022
[Kernel-packages] [Bug 2025134] Re: Revert variable symbol length modversion in all the jammy kernels
** Changed in: linux-hwe-6.2 (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux-lowlatency-hwe-6.2 (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.2 in Ubuntu.
https://bugs.launchpad.net/bugs/2025134
Title:
Revert variable symbol length modversion in all the jammy kernels
Status in linux-hwe-6.2 package in Ubuntu:
Fix Committed
Status in linux-lowlatency-hwe-6.2 package in Ubuntu:
Fix Committed
Bug description:
[Impact]
In order to support Rust in the kernel starting with Lunar we had to
apply the following UBUNTU SAUCE patch:
27c4fe11712c ("UBUNTU: SAUCE: modpost: support arbitrary symbol
length in modversion")
This patch can potentially introduce a user-space regression, because it
alters how the module names are stored in the modversion_info area.
Realistically it doesn't break anything, since this area is used only by the
kmod tools (and they've been verified to work fine also with this change
applied).
However, to be 100% that we don't introduce regressions it is safer to
simply revert this patch, considering that we don't provide kernel
Rust support in Jammy and without Rust this patch doesn't provide any
benefit.
[Fix]
In order to fix this we need to explicitly revert the patch in all the
Jammy kernels that are derived from any Lunar kernel.
To do so, after `cranky rebase`, run:
git revert -s 27c4fe11712c
The comment for the revert should report something like this:
```
Revert "UBUNTU: SAUCE: modpost: support arbitrary symbol length in
modversion"
This patch is required by Rust and it can potentially break user-space.
It is safer to revert this in all the kernel backported to old releases.
```
[Regression potential]
This revert is not very critical, realistically even with the variable
modversions patch applied we won't regress any known tool, however we
don't to risk to introduce potential user-space ABI changes. Fixing
this requires a slightly different action, respect to our usual
workflow, so if some kernels are shipped with the variable modversion
patch (for any reason), we may experience regressions with kmod-
related tools (e.g., scripts that are using modinfo, modprobe and
similar or custom tools that are parsing .ko sections directly).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.2/+bug/2025134/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2025134] Re: Revert variable symbol length modversion in all the jammy kernels
** Also affects: linux-hwe-6.2 (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: linux (Ubuntu)
** No longer affects: linux (Ubuntu Jammy)
** Changed in: linux-hwe-6.2 (Ubuntu Jammy)
Status: New => Fix Committed
** Also affects: linux-lowlatency-hwe-6.2 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-lowlatency-hwe-6.2 (Ubuntu)
Status: New => Fix Committed
** No longer affects: linux-hwe-6.2 (Ubuntu Jammy)
** Changed in: linux-hwe-6.2 (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.2 in Ubuntu.
https://bugs.launchpad.net/bugs/2025134
Title:
Revert variable symbol length modversion in all the jammy kernels
Status in linux-hwe-6.2 package in Ubuntu:
Fix Committed
Status in linux-lowlatency-hwe-6.2 package in Ubuntu:
Fix Committed
Bug description:
[Impact]
In order to support Rust in the kernel starting with Lunar we had to
apply the following UBUNTU SAUCE patch:
27c4fe11712c ("UBUNTU: SAUCE: modpost: support arbitrary symbol
length in modversion")
This patch can potentially introduce a user-space regression, because it
alters how the module names are stored in the modversion_info area.
Realistically it doesn't break anything, since this area is used only by the
kmod tools (and they've been verified to work fine also with this change
applied).
However, to be 100% that we don't introduce regressions it is safer to
simply revert this patch, considering that we don't provide kernel
Rust support in Jammy and without Rust this patch doesn't provide any
benefit.
[Fix]
In order to fix this we need to explicitly revert the patch in all the
Jammy kernels that are derived from any Lunar kernel.
To do so, after `cranky rebase`, run:
git revert -s 27c4fe11712c
The comment for the revert should report something like this:
```
Revert "UBUNTU: SAUCE: modpost: support arbitrary symbol length in
modversion"
This patch is required by Rust and it can potentially break user-space.
It is safer to revert this in all the kernel backported to old releases.
```
[Regression potential]
This revert is not very critical, realistically even with the variable
modversions patch applied we won't regress any known tool, however we
don't to risk to introduce potential user-space ABI changes. Fixing
this requires a slightly different action, respect to our usual
workflow, so if some kernels are shipped with the variable modversion
patch (for any reason), we may experience regressions with kmod-
related tools (e.g., scripts that are using modinfo, modprobe and
similar or custom tools that are parsing .ko sections directly).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.2/+bug/2025134/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2025134] [NEW] Revert variable symbol length modversion in all the jammy kernels
Public bug reported:
[Impact]
In order to support Rust in the kernel starting with Lunar we had to
apply the following UBUNTU SAUCE patch:
27c4fe11712c ("UBUNTU: SAUCE: modpost: support arbitrary symbol length
in modversion")
This patch can potentially introduce a user-space regression, because it alters
how the module names are stored in the modversion_info area. Realistically it
doesn't break anything, since this area is used only by the kmod tools (and
they've been verified to work fine also with this change applied).
However, to be 100% that we don't introduce regressions it is safer to
simply revert this patch, considering that we don't provide kernel Rust
support in Jammy and without Rust this patch doesn't provide any
benefit.
[Fix]
In order to fix this we need to explicitly revert the patch in all the
Jammy kernels that are derived from any Lunar kernel.
To do so, after `cranky rebase`, run:
git revert -s 27c4fe11712c
The comment for the revert should report something like this:
```
Revert "UBUNTU: SAUCE: modpost: support arbitrary symbol length in
modversion"
This patch is required by Rust and it can potentially break user-space.
It is safer to revert this in all the kernel backported to old releases.
```
[Regression potential]
This revert is not very critical, realistically even with the variable
modversions patch applied we won't regress any known tool, however we
don't to risk to introduce potential user-space ABI changes. Fixing this
requires a slightly different action, respect to our usual workflow, so
if some kernels are shipped with the variable modversion patch (for any
reason), we may experience regressions with kmod-related tools (e.g.,
scripts that are using modinfo, modprobe and similar or custom tools
that are parsing .ko sections directly).
** Affects: linux-hwe-6.2 (Ubuntu)
Importance: Undecided
Status: Fix Committed
** Affects: linux-lowlatency-hwe-6.2 (Ubuntu)
Importance: Undecided
Status: Fix Committed
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2025134
Title:
Revert variable symbol length modversion in all the jammy kernels
Status in linux-hwe-6.2 package in Ubuntu:
Fix Committed
Status in linux-lowlatency-hwe-6.2 package in Ubuntu:
Fix Committed
Bug description:
[Impact]
In order to support Rust in the kernel starting with Lunar we had to
apply the following UBUNTU SAUCE patch:
27c4fe11712c ("UBUNTU: SAUCE: modpost: support arbitrary symbol
length in modversion")
This patch can potentially introduce a user-space regression, because it
alters how the module names are stored in the modversion_info area.
Realistically it doesn't break anything, since this area is used only by the
kmod tools (and they've been verified to work fine also with this change
applied).
However, to be 100% that we don't introduce regressions it is safer to
simply revert this patch, considering that we don't provide kernel
Rust support in Jammy and without Rust this patch doesn't provide any
benefit.
[Fix]
In order to fix this we need to explicitly revert the patch in all the
Jammy kernels that are derived from any Lunar kernel.
To do so, after `cranky rebase`, run:
git revert -s 27c4fe11712c
The comment for the revert should report something like this:
```
Revert "UBUNTU: SAUCE: modpost: support arbitrary symbol length in
modversion"
This patch is required by Rust and it can potentially break user-space.
It is safer to revert this in all the kernel backported to old releases.
```
[Regression potential]
This revert is not very critical, realistically even with the variable
modversions patch applied we won't regress any known tool, however we
don't to risk to introduce potential user-space ABI changes. Fixing
this requires a slightly different action, respect to our usual
workflow, so if some kernels are shipped with the variable modversion
patch (for any reason), we may experience regressions with kmod-
related tools (e.g., scripts that are using modinfo, modprobe and
similar or custom tools that are parsing .ko sections directly).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.2/+bug/2025134/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2021605] Re: introduce do_lib_rust=true|false to enable/disable linux-lib-rust package
** Changed in: linux (Ubuntu Mantic) Status: Incomplete => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/2021605 Title: introduce do_lib_rust=true|false to enable/disable linux-lib-rust package Status in linux package in Ubuntu: Fix Committed Status in linux-aws package in Ubuntu: New Status in linux source package in Lunar: Fix Committed Status in linux-aws source package in Lunar: Fix Released Status in linux source package in Mantic: Fix Committed Status in linux-aws source package in Mantic: New Bug description: [Impact] Provide a variable do_lib_rust=true|false in the kernel build system to selectively enable the Rust packaging (linux-lib-rust) with specific kernels and specific architectures. Right now Rust should be enabled only in lunar and mantic and only on amd64. [Test case] Build the kernel producing all the debs. [Fix] Introduce a do_lib_rust=true variable that will be defined only in debian.master/rules.d/amd64.mk for now. [Regression potential] Kernels may need to set this variables if they want to enable the Rust support. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2021605/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2024599] Re: linux-image-5.15.0-1032-realtime locks up under scheduler test load
5.15.0.75 works fine, no problem, 5.19.0-45 kernel crashes, so issue introduced between 5.15 and 5.19 ** Also affects: apparmor (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: apparmor (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: apparmor (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Mantic) Importance: Low Status: 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/2024599 Title: linux-image-5.15.0-1032-realtime locks up under scheduler test load Status in apparmor package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in apparmor source package in Jammy: New Status in linux source package in Jammy: Incomplete Status in apparmor source package in Kinetic: New Status in linux source package in Kinetic: New Status in apparmor source package in Lunar: New Status in linux source package in Lunar: New Status in apparmor source package in Mantic: New Status in linux source package in Mantic: Incomplete Bug description: lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 22.04.2 LTS Release: 22.04 Codename: jammy uname -a Linux jammie-amd64-efi 5.15.0-1032-realtime #35-Ubuntu SMP PREEMPT_RT Tue Jan 24 11:45:03 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux free totalusedfree shared buff/cache available Mem: 4013888 200984 34390121204 373892 3744628 Swap:4014076 0 4014076 Running in a kvm-qemu, 8 cpus, cpu Intel Core Processor (Skylake, IBRS): how to reproduce issue: git clone https://github.com/ColinIanKing/stress-ng sudo apt-get update sudo apt-get build-dep stress-ng sudo apt-get install libeigen3-dev libmpfr-dev libkmod-dev libxxhash-dev libglvnd-dev libgbm-dev cd stress-ng make clean make -j 8 sudo ./stress-ng --class scheduler --all 1 -v --vmstat 1 -t 30m ..wait for all the stressors to get invoked, system becomes unresponsive, can't ^C stress-ng, can't swap consoles on the VM, appears to be hard locked. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2024599/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2024599] Re: linux-image-5.15.0-1032-realtime locks up under scheduler test load
And with 5.19.0-45-generic: sudo ./stress-ng --apparmor 1 --klog-check [sudo] password for cking: stress-ng: info: [1179] defaulting to a 86400 second (1 day, 0.00 secs) run per stressor stress-ng: info: [1179] dispatching hogs: 1 apparmor stress-ng: info: [1180] klog-check: kernel cmdline: 'BOOT_IMAGE=/vmlinuz-5.19.0-45-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro' stress-ng: error: [1180] klog-check: error: [93.527396] 'AppArmor DFA next/check upper bounds error' stress-ng: error: [1180] klog-check: error: [93.827976] 'AppArmor DFA state with invalid match flags' stress-ng: error: [1180] klog-check: error: [93.991395] 'AppArmor DFA next/check upper bounds error' stress-ng: error: [1180] klog-check: error: [93.992189] 'AppArmor DFA next/check upper bounds error' stress-ng: error: [1180] klog-check: error: [94.007400] 'AppArmor DFA state with invalid match flags' stress-ng: error: [1180] klog-check: error: [94.059345] 'AppArmor DFA state with invalid match flags' stress-ng: error: [1180] klog-check: error: [94.104414] 'AppArmor DFA next/check upper bounds error' stress-ng: error: [1180] klog-check: alert: [94.128617] 'BUG: kernel NULL pointer dereference, address: 0130' stress-ng: error: [1180] klog-check: alert: [94.128644] '#PF: supervisor read access in kernel mode' stress-ng: error: [1180] klog-check: alert: [94.128659] '#PF: error_code(0x) - not-present page' stress-ng: info: [1180] klog-check: warning: [94.128685] 'Oops: [#1] PREEMPT SMP PTI' stress-ng: info: [1180] klog-check: warning: [94.128698] 'CPU: 7 PID: 1185 Comm: stress-ng-appar Not tainted 5.19.0-45-generic #46-Ubuntu' stress-ng: info: [1180] klog-check: warning: [94.128722] 'Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.0-debian-1.16.0-5 04/01/2014' stress-ng: info: [1180] klog-check: warning: [94.128745] 'RIP: 0010:aa_unpack+0x11f/0x530' stress-ng: info: [1180] klog-check: warning: [94.128762] 'Code: 00 48 85 c0 0f 84 15 04 00 00 48 8d 75 a8 48 8d 7d b0 4c 8b 7d c0 e8 80 ec ff ff 48 89 c3 48 3d 00 f0 ff ff 0f 87 00 02 00 00 <4c> 8b b0 30 01 00 00 4d 85 f6 0f 84 38 01 00 00 49 8b 86 c8 00 00' stress-ng: info: [1180] klog-check: warning: [94.128807] 'RSP: 0018:b1fdc0f57ce0 EFLAGS: 00010207' stress-ng: info: [1180] klog-check: warning: [94.129378] 'RAX: RBX: RCX: ' stress-ng: info: [1180] klog-check: warning: [94.129928] 'RDX: RSI: RDI: ' stress-ng: info: [1180] klog-check: warning: [94.130443] 'RBP: b1fdc0f57d40 R08: R09: ' stress-ng: info: [1180] klog-check: warning: [94.131056] 'R10: R11: R12: b1fdc0f57da8' stress-ng: info: [1180] klog-check: warning: [94.131572] 'R13: b1fdc0f57da0 R14: 9da384835962 R15: 9da384820010' stress-ng: info: [1180] klog-check: warning: [94.132090] 'FS: 7fa65a059740() GS:9da3fbdc() knlGS:' stress-ng: info: [1180] klog-check: warning: [94.132652] 'CS: 0010 DS: ES: CR0: 80050033' stress-ng: info: [1180] klog-check: warning: [94.133206] 'CR2: 0130 CR3: 00010d432006 CR4: 00370ee0' stress-ng: info: [1180] klog-check: warning: [94.133739] 'DR0: DR1: DR2: ' stress-ng: info: [1180] klog-check: warning: [94.134282] 'DR3: DR6: fffe0ff0 DR7: 0400' stress-ng: info: [1180] klog-check: warning: [94.134868] 'Call Trace:' stress-ng: info: [1180] klog-check: warning: [94.135388] ' ' stress-ng: info: [1180] klog-check: warning: [94.135933] ' aa_replace_profiles+0xa1/0x10b0' stress-ng: info: [1180] klog-check: warning: [94.136471] ' ? check_heap_object+0x29/0x1e0' stress-ng: info: [1180] klog-check: warning: [94.137018] ' ? __check_object_size.part.0+0x4c/0xf0' stress-ng: info: [1180] klog-check: warning: [94.137528] ' policy_update+0xd0/0x170' stress-ng: info: [1180] klog-check: warning: [94.138061] ' profile_replace+0xb9/0x150' stress-ng: info: [1180] klog-check: warning: [94.138612] ' vfs_write+0xb7/0x290' stress-ng: info: [1180] klog-check: warning: [94.139124] ' ksys_write+0x73/0x100' stress-ng: info: [1180] klog-check: warning: [94.139616] ' __x64_sys_write+0x19/0x30' stress-ng: info: [1180] klog-check: warning: [94.140104] ' do_syscall_64+0x58/0x90' stress-ng: info: [1180] klog-check: warning: [94.140651] ' ? syscall_exit_to_user_mode+0x29/0x50' stress-ng: info: [1180] klog-check: warning: [94.141130] ' ? do_syscall_64+0x67/0x90' stress-ng: info: [1180] klog-check: warning: [94.141630] ' ? do_syscall_64+0x67/0x90' stress-ng: info: [1180] klog-check: warning: [94.142117] ' ? do_syscall_64+0x67/0x90' stress-ng: info: [1180] klog-check: warning: [94.142627] ' entry_SYSCALL_64_after_hwframe+0x63/0xcd' stress-ng: info: [1180] klog-check: warning:
[Kernel-packages] [Bug 2024599] Re: linux-image-5.15.0-1032-realtime locks up under scheduler test load
On 6.2.0-21-generic I also get: sudo ./stress-ng --apparmor 1 --klog-check stress-ng: error: [1083] klog-check: alert: [66.442338] 'BUG: kernel NULL pointer dereference, address: 0030' stress-ng: error: [1083] klog-check: alert: [66.442538] '#PF: supervisor read access in kernel mode' stress-ng: error: [1083] klog-check: alert: [66.442718] '#PF: error_code(0x) - not-present page' stress-ng: info: [1083] klog-check: warning: [66.443080] 'Oops: [#1] PREEMPT SMP PTI' stress-ng: info: [1083] klog-check: warning: [66.443256] 'CPU: 3 PID: 1088 Comm: stress-ng-appar Not tainted 6.2.0-21-generic #21-Ubuntu' stress-ng: info: [1083] klog-check: warning: [66.443438] 'Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.0-debian-1.16.0-5 04/01/2014' stress-ng: info: [1083] klog-check: warning: [66.443628] 'RIP: 0010:aafs_create.constprop.0+0x7f/0x130' stress-ng: info: [1083] klog-check: warning: [66.443819] 'Code: 4c 63 e0 48 83 c4 18 4c 89 e0 5b 41 5c 41 5d 41 5e 41 5f 5d 31 d2 31 c9 31 f6 31 ff 45 31 c0 45 31 c9 45 31 d2 c3 cc cc cc cc <4d> 8b 55 30 4d 8d ba a0 00 00 00 4c 89 55 c0 4c 89 ff e8 8a 59 a1' stress-ng: info: [1083] klog-check: warning: [66.444227] 'RSP: 0018:beb940907bd8 EFLAGS: 00010246' stress-ng: info: [1083] klog-check: warning: [66.33] 'RAX: RBX: 41ed RCX: ' stress-ng: info: [1083] klog-check: warning: [66.444646] 'RDX: RSI: RDI: ' stress-ng: info: [1083] klog-check: warning: [66.444862] 'RBP: beb940907c18 R08: R09: ' stress-ng: info: [1083] klog-check: warning: [66.445074] 'R10: R11: R12: 93db8b18' stress-ng: info: [1083] klog-check: warning: [66.445291] 'R13: R14: R15: ' stress-ng: info: [1083] klog-check: warning: [66.445503] 'FS: 7f60f5c07740() GS:9578bbcc() knlGS:' stress-ng: info: [1083] klog-check: warning: [66.445721] 'CS: 0010 DS: ES: CR0: 80050033' stress-ng: info: [1083] klog-check: warning: [66.445939] 'CR2: 0030 CR3: 000124ffa004 CR4: 00370ee0' stress-ng: info: [1083] klog-check: warning: [66.446163] 'DR0: DR1: DR2: ' stress-ng: info: [1083] klog-check: warning: [66.446387] 'DR3: DR6: fffe0ff0 DR7: 0400' stress-ng: info: [1083] klog-check: warning: [66.446608] 'Call Trace:' stress-ng: info: [1083] klog-check: warning: [66.446829] ' ' stress-ng: info: [1083] klog-check: warning: [66.447059] ' __aafs_profile_mkdir+0x3d6/0x480' stress-ng: info: [1083] klog-check: warning: [66.447290] ' aa_replace_profiles+0x862/0x1270' stress-ng: info: [1083] klog-check: warning: [66.447518] ' policy_update+0xe0/0x180' stress-ng: info: [1083] klog-check: warning: [66.447750] ' profile_replace+0xb9/0x150' stress-ng: info: [1083] klog-check: warning: [66.447981] ' vfs_write+0xc8/0x410' stress-ng: info: [1083] klog-check: warning: [66.448213] ' ? kmem_cache_free+0x1e/0x3b0' stress-ng: info: [1083] klog-check: warning: [66.448442] ' ksys_write+0x73/0x100' stress-ng: info: [1083] klog-check: warning: [66.448670] ' __x64_sys_write+0x19/0x30' stress-ng: info: [1083] klog-check: warning: [66.448892] ' do_syscall_64+0x58/0x90' stress-ng: info: [1083] klog-check: warning: [66.449115] ' ? do_syscall_64+0x67/0x90' stress-ng: info: [1083] klog-check: warning: [66.449337] ' ? do_syscall_64+0x67/0x90' stress-ng: info: [1083] klog-check: warning: [66.449551] ' ? exit_to_user_mode_loop+0xe0/0x130' stress-ng: info: [1083] klog-check: warning: [66.449775] ' ? exit_to_user_mode_prepare+0x30/0xb0' stress-ng: info: [1083] klog-check: warning: [66.449996] ' ? syscall_exit_to_user_mode+0x29/0x50' stress-ng: info: [1083] klog-check: warning: [66.450220] ' ? do_syscall_64+0x67/0x90' stress-ng: info: [1083] klog-check: warning: [66.450449] ' ? exit_to_user_mode_prepare+0x30/0xb0' stress-ng: info: [1083] klog-check: warning: [66.450681] ' ? syscall_exit_to_user_mode+0x29/0x50' stress-ng: info: [1083] klog-check: warning: [66.450915] ' ? do_syscall_64+0x67/0x90' stress-ng: info: [1083] klog-check: warning: [66.451151] ' ? do_syscall_64+0x67/0x90' stress-ng: info: [1083] klog-check: warning: [66.451384] ' entry_SYSCALL_64_after_hwframe+0x72/0xdc' stress-ng: info: [1083] klog-check: warning: [66.451614] 'RIP: 0033:0x7f60f5b0b9e4' stress-ng: info: [1083] klog-check: warning: [66.451848] 'Code: 15 39 a4 0e 00 f7 d8 64 89 02 48 c7 c0 ff ff ff ff eb b7 0f 1f 00 f3 0f 1e fa 80 3d fd 2b 0f 00 00 74 13 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 54 c3 0f 1f 00 48 83 ec 28 48 89 54 24 18 48' stress-ng: info: [1083] klog-check: warning: [66.452341] 'RSP: 002b:7ffdaa28bfb8 EFLAGS: 0202 ORIG_RAX: 0001' stress-ng: info:
[Kernel-packages] [Bug 2025124] [NEW] PC frequently fails to wake from suspend with kernel 5.4
Public bug reported: Ever since upgrading from Bionic to Focal, my machine frequently (multiple times per week) fails to wake up from suspend with the default 5.4 kernel (linux-image-generic). When booting the 4.15 kernel from Bionic that I still have installed (linux-image-4.15.0-46-generic), suspend and wake-up works reliably again. The symptoms of the failure to wake up are that the machine powers up (fans, LEDs), but the screen stays black. Num lock LED on the keyboard is ON and cannot be toggled. The Machine cannot be pinged. After hard-resetting the machine, the last entry in journalctl from the previous boot is "kernel: PM: suspend entry (deep)". ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-generic 5.4.0.152.149 ProcVersionSignature: Ubuntu 5.4.0-152.169-generic 5.4.235 Uname: Linux 5.4.0-152-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: christian 2130 F pulseaudio /dev/snd/controlC1: christian 2130 F pulseaudio /dev/snd/controlC0: christian 2130 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Tue Jun 27 09:02:07 2023 InstallationDate: Installed on 2014-09-16 (3205 days ago) InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release amd64 (20140807.1) MachineType: Gigabyte Technology Co., Ltd. H97M-D3H ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-152-generic root=UUID=ef54dd1e-0d88-4541-a64c-71f83163f2f2 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-152-generic N/A linux-backports-modules-5.4.0-152-generic N/A linux-firmware 1.187.39 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to focal on 2023-04-03 (84 days ago) dmi.bios.date: 06/03/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F3 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H97M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF3:bd06/03/2014:svnGigabyteTechnologyCo.,Ltd.:pnH97M-D3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH97M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: H97M-D3H dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "Output from dmidecode" https://bugs.launchpad.net/bugs/2025124/+attachment/5682174/+files/dmi.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/2025124 Title: PC frequently fails to wake from suspend with kernel 5.4 Status in linux package in Ubuntu: New Bug description: Ever since upgrading from Bionic to Focal, my machine frequently (multiple times per week) fails to wake up from suspend with the default 5.4 kernel (linux-image-generic). When booting the 4.15 kernel from Bionic that I still have installed (linux-image-4.15.0-46-generic), suspend and wake-up works reliably again. The symptoms of the failure to wake up are that the machine powers up (fans, LEDs), but the screen stays black. Num lock LED on the keyboard is ON and cannot be toggled. The Machine cannot be pinged. After hard-resetting the machine, the last entry in journalctl from the previous boot is "kernel: PM: suspend entry (deep)". ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-generic 5.4.0.152.149 ProcVersionSignature: Ubuntu 5.4.0-152.169-generic 5.4.235 Uname: Linux 5.4.0-152-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: christian 2130 F pulseaudio /dev/snd/controlC1: christian 2130 F pulseaudio /dev/snd/controlC0: christian 2130 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Tue Jun 27 09:02:07 2023 InstallationDate: Installed on 2014-09-16 (3205 days ago) InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release amd64 (20140807.1) MachineType: Gigabyte Technology Co., Ltd. H97M-D3H ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-152-generic root=UUID=ef54dd1e-0d88-4541-a64c-71f83163f2f2 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-152-generic N/A linux-backports-modules-5.4.0-152-generic N/A linux-firmware 1.187.39 RfKill: SourcePackage:
[Kernel-packages] [Bug 1995606] Re: Upgrade thermald to 2.5.1 for Jammy (22.04)
@Raof * Replied 1st, please check Ref. https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/2018275/comments/2 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1995606 Title: Upgrade thermald to 2.5.1 for Jammy (22.04) Status in OEM Priority Project: New Status in thermald package in Ubuntu: New Status in thermald source package in Jammy: Incomplete Bug description: [Justification] The purpose of this bug is that prevent the regression in the future. The automatic test scripts are better for the future SRU and is still on the planning. [Test case] For these CPU series, RPL/ADL/TGL/CML/CFL/KBL, the following tests will be run on machines in the CI lab: 1. Run stress-ng, and observe the temperature/frequency/power with s-tui - Temperatures should stay just below trip values - Power/performance profiles should stay roughly the same between old thermald and new thermald (unless specifically expected eg: to fix premature/insufficient throttling) 2. check if thermald could read rules from /dev/acpi_thermal_rel and generate the xml file on /etc/thermald/ correctly. - this depends on if acpi_thermal_rel exist. - if the machine suppots acpi_thermal_rel, the "thermal-conf.xml.auto" could be landed in etc/thermald/. - if not, the user-defined xml could be created, then jump to (3). - run thermald with --loglevel=debug, and compare the log with xml.auto file. check if the configuration could be parsed correctly. 3. check if theramd-conf.xml and thermal-cpu-cdev-order.xml can be loaded correctly. - run thermald with --loglevel=debug, and compare the log with xml files. - if parsed correctly, the configurations from XML files would appear in the log. 4. Run unit tests, the scripts are under test folder, using emul_temp to simulate the High temperatue and check thermald would throttle CPU through the related cooling device. - rapl.sh - intel_pstate.sh - powerclamp.sh - processor.sh 5. check if the power/frequency would be throttled once the temperature reach the trip-points of thermal zone. 6. check if system would be throttled even the temperature is under the trip-points. [ Where problems could occur ] since the PL1 min/max is introduced, there may have some cases that don't check the minimum of PL1 then make PL1 to smaller and smaller and throttle the CPU. this may cause machines run like the old behavior that doesn't have PL1 min/max. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1995606/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2021532] Re: Ubuntu 23.04 does not suspend laptop on lid close
*** This bug is a duplicate of bug 2018773 *** https://bugs.launchpad.net/bugs/2018773 Status changed to 'Confirmed' because the bug affects multiple users. ** 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/2021532 Title: Ubuntu 23.04 does not suspend laptop on lid close Status in linux package in Ubuntu: Confirmed Bug description: Intentional duplicate of 2018773, added so that I can upload logs --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: reece 2919 F pipewire reece 2934 F wireplumber /dev/snd/seq:reece 2919 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2023-02-13 (105 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: Dell Inc. XPS 13 9310 Package: linux (not installed) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=416f513d-23cf-40bf-b8d8-05f7b27d0436 ro quiet splash 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 Tags: wayland-session lunar Uname: Linux 6.2.0-20-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-05-16 (13 days ago) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/12/2023 dmi.bios.release: 3.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 3.15.0 dmi.board.name: 0DMPXV dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr3.15.0:bd04/12/2023:br3.15:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn0DMPXV:rvrA02:cvnDellInc.:ct10:cvr:sku0991: dmi.product.family: XPS dmi.product.name: XPS 13 9310 dmi.product.sku: 0991 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2021532/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2025120] Re: 6.3.0-7-generic can't boot on Intel NUC 12 Extreme
Jun 27 13:56:27 dragon kernel: Workqueue: events_long ucsi_init_work [typec_ucsi] Jun 27 13:56:27 dragon kernel: RIP: 0010:ucsi_acpi_async_write+0x31/0x60 [ucsi_acpi] Jun 27 13:56:27 dragon kernel: Code: 89 e5 41 56 49 89 ce 41 55 49 89 d5 41 54 53 89 f3 e8 83 2b fe ff 4c 89 f2 4c 89 ee 89 df 48 03 78 10 49 89 c4 e8 1f 34 c7 d1 <49> 8b 45 00 4c 89 e7 be 01 00 00 00 49 89 44 24 50 e8 c9 fc ff ff Jun 27 13:56:27 dragon kernel: RSP: 0018:b347c0683d78 EFLAGS: 00010282 Jun 27 13:56:27 dragon kernel: RAX: b347c0185002 RBX: 0002 RCX: Jun 27 13:56:27 dragon kernel: RDX: RSI: RDI: b347c0185002 Jun 27 13:56:27 dragon kernel: RBP: b347c0683d98 R08: R09: Jun 27 13:56:27 dragon kernel: R10: R11: R12: 9c370214a7a8 Jun 27 13:56:27 dragon kernel: R13: R14: R15: 9c37010c1db8 Jun 27 13:56:27 dragon kernel: FS: () GS:9c3e8d28() knlGS: Jun 27 13:56:27 dragon kernel: CS: 0010 DS: ES: CR0: 80050033 Jun 27 13:56:27 dragon kernel: CR2: CR3: 00052e83a000 CR4: 00750ee0 Jun 27 13:56:27 dragon kernel: PKRU: 5554 Jun 27 13:56:27 dragon kernel: Call Trace: Jun 27 13:56:27 dragon kernel: Jun 27 13:56:27 dragon kernel: ? show_regs+0x6d/0x80 Jun 27 13:56:27 dragon kernel: ? __die+0x24/0x80 Jun 27 13:56:27 dragon kernel: ? page_fault_oops+0x99/0x1b0 Jun 27 13:56:27 dragon kernel: ? do_user_addr_fault+0x335/0x720 Jun 27 13:56:27 dragon kernel: ? acpi_evaluate_object+0x1e7/0x470 Jun 27 13:56:27 dragon kernel: ? exc_page_fault+0x80/0x1b0 Jun 27 13:56:27 dragon kernel: ? asm_exc_page_fault+0x27/0x30 Jun 27 13:56:27 dragon kernel: ? ucsi_acpi_async_write+0x31/0x60 [ucsi_acpi] Jun 27 13:56:27 dragon kernel: ? ucsi_acpi_async_write+0x31/0x60 [ucsi_acpi] Jun 27 13:56:27 dragon kernel: ucsi_exec_command+0xdf/0x100 [typec_ucsi] Jun 27 13:56:27 dragon kernel: ucsi_send_command+0x4b/0xf0 [typec_ucsi] Jun 27 13:56:27 dragon kernel: ucsi_init+0x33/0x270 [typec_ucsi] Jun 27 13:56:27 dragon kernel: ucsi_init_work+0x18/0x80 [typec_ucsi] Jun 27 13:56:27 dragon kernel: process_one_work+0x222/0x430 Jun 27 13:56:27 dragon kernel: worker_thread+0x50/0x3f0 Jun 27 13:56:27 dragon kernel: ? __pfx_worker_thread+0x10/0x10 Jun 27 13:56:27 dragon kernel: kthread+0xe6/0x110 Jun 27 13:56:27 dragon kernel: ? __pfx_kthread+0x10/0x10 Jun 27 13:56:27 dragon kernel: ret_from_fork+0x29/0x50 Jun 27 13:56:27 dragon kernel: Jun 27 13:56:27 dragon kernel: Modules linked in: nvme ucsi_acpi atlantic crc32_pclmul thunderbolt nvme_core spi_intel_pci typec_ucsi i2c_i801 ahci macsec spi_intel i2c_smbus nvme_common xhci_pci typec libahci xhci_pci_renesas video wmi pinctrl_alderlake Jun 27 13:56:27 dragon kernel: CR2: Jun 27 13:56:27 dragon kernel: ---[ end trace ]--- -- 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/2025120 Title: 6.3.0-7-generic can't boot on Intel NUC 12 Extreme Status in linux package in Ubuntu: New Bug description: 6.3.0-7-generic can't boot on Intel NUC 12 Extreme Weirdly this only started today. Yesterday the same kernel would boot. Looks like it keeps crashing in ucsi_acpi/typec_ucsi but I can't tell if that is fatal. Booting with 6.2.0-21-generic still works. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2025120/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2025120] Re: 6.3.0-7-generic can't boot on Intel NUC 12 Extreme
** Attachment added: "prevboot3.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2025120/+attachment/5682169/+files/prevboot3.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/2025120 Title: 6.3.0-7-generic can't boot on Intel NUC 12 Extreme Status in linux package in Ubuntu: New Bug description: 6.3.0-7-generic can't boot on Intel NUC 12 Extreme Weirdly this only started today. Yesterday the same kernel would boot. Looks like it keeps crashing in ucsi_acpi/typec_ucsi but I can't tell if that is fatal. Booting with 6.2.0-21-generic still works. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2025120/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2025120] Re: 6.3.0-7-generic can't boot on Intel NUC 12 Extreme
** Attachment added: "prevboot2.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2025120/+attachment/5682168/+files/prevboot2.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/2025120 Title: 6.3.0-7-generic can't boot on Intel NUC 12 Extreme Status in linux package in Ubuntu: New Bug description: 6.3.0-7-generic can't boot on Intel NUC 12 Extreme Weirdly this only started today. Yesterday the same kernel would boot. Looks like it keeps crashing in ucsi_acpi/typec_ucsi but I can't tell if that is fatal. Booting with 6.2.0-21-generic still works. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2025120/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2025120] [NEW] 6.3.0-7-generic can't boot on Intel NUC 12 Extreme
Public bug reported: 6.3.0-7-generic can't boot on Intel NUC 12 Extreme Weirdly this only started today. Yesterday the same kernel would boot. Looks like it keeps crashing in ucsi_acpi/typec_ucsi but I can't tell if that is fatal. Booting with 6.2.0-21-generic still works. ** Affects: linux (Ubuntu) Importance: High Status: New ** Tags: mantic regression ** Attachment added: "prevboot1.txt" https://bugs.launchpad.net/bugs/2025120/+attachment/5682167/+files/prevboot1.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/2025120 Title: 6.3.0-7-generic can't boot on Intel NUC 12 Extreme Status in linux package in Ubuntu: New Bug description: 6.3.0-7-generic can't boot on Intel NUC 12 Extreme Weirdly this only started today. Yesterday the same kernel would boot. Looks like it keeps crashing in ucsi_acpi/typec_ucsi but I can't tell if that is fatal. Booting with 6.2.0-21-generic still works. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2025120/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1972140] Re: UBSAN: array-index-out-of-bounds in /build/linux-HMZHpV/linux-5.15.0/drivers/net/wireless/ath/ath5k/base.c:1695:20
Update: The disconnection problems are unrelated to this ticket and can be fixed with the iommu=pt kernel parameter. The device seems to work without problems despite the UBSAN warnings. -- 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/1972140 Title: UBSAN: array-index-out-of-bounds in /build/linux- HMZHpV/linux-5.15.0/drivers/net/wireless/ath/ath5k/base.c:1695:20 Status in linux package in Ubuntu: Confirmed Bug description: [114914.279420] [114914.279431] UBSAN: array-index-out-of-bounds in /build/linux-HMZHpV/linux-5.15.0/drivers/net/wireless/ath/ath5k/base.c:1695:20 [114914.279436] index 4 is out of range for type 'ieee80211_tx_rate [4]' [114914.279440] CPU: 1 PID: 0 Comm: swapper/1 Tainted: P IOE 5.15.0-27-generic #28-Ubuntu [114914.279445] Hardware name: Dell Inc. Precision WorkStation T7500 /0D881F, BIOS A18 10/15/2018 [114914.279448] Call Trace: [114914.279451] [114914.279455] show_stack+0x52/0x58 [114914.279465] dump_stack_lvl+0x4a/0x5f [114914.279475] dump_stack+0x10/0x12 [114914.279478] ubsan_epilogue+0x9/0x45 [114914.279482] __ubsan_handle_out_of_bounds.cold+0x44/0x49 [114914.279487] ? iommu_dma_unmap_page+0x4a/0x50 [114914.279492] ath5k_tx_frame_completed.constprop.0+0x279/0x2c0 [ath5k] [114914.279507] ath5k_tx_processq+0xb1/0x1c0 [ath5k] [114914.279519] ath5k_tasklet_tx+0x7b/0xf0 [ath5k] [114914.279531] tasklet_action_common.constprop.0+0xc0/0xf0 [114914.279539] tasklet_action+0x22/0x30 [114914.279543] __do_softirq+0xd9/0x2e3 [114914.279550] irq_exit_rcu+0x8c/0xb0 [114914.279554] common_interrupt+0x8a/0xa0 [114914.279560] [114914.279562] [114914.279563] asm_common_interrupt+0x1e/0x40 [114914.279568] RIP: 0010:cpuidle_enter_state+0xd9/0x620 [114914.279574] Code: 3d 14 5b be 67 e8 d7 ad 6c ff 49 89 c7 0f 1f 44 00 00 31 ff e8 28 ba 6c ff 80 7d d0 00 0f 85 5d 01 00 00 fb 66 0f 1f 44 00 00 <45> 85 f6 0f 88 69 01 00 00 4d 63 ee 49 83 fd 09 0f 87 e3 03 00 00 [114914.279577] RSP: 0018:adc58009be28 EFLAGS: 0292 [114914.279582] RAX: RBX: cdc57ee79f00 RCX: 0020 [114914.279584] RDX: 02c71492 RSI: 3d66 RDI: 99807a40 [114914.279587] RBP: adc58009be78 R08: R09: 000c3500 [114914.279589] R10: 0005 R11: 071c71c71c71c71c R12: 99ad3580 [114914.279592] R13: 0004 R14: 0004 R15: 688390cd49d1 [114914.279597] ? cpuidle_enter_state+0x246/0x620 [114914.279601] cpuidle_enter+0x2e/0x40 [114914.279605] cpuidle_idle_call+0x13e/0x1e0 [114914.279610] do_idle+0x83/0xf0 [114914.279614] cpu_startup_entry+0x20/0x30 [114914.279617] start_secondary+0x12a/0x180 [114914.279622] secondary_startup_64_no_verify+0xc2/0xcb [114914.279630] [114914.279632] ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-27-generic 5.15.0-27.28 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: js1 17869 F pulseaudio /dev/snd/controlC1: js1 17869 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: LXQt Date: Sun May 8 23:36:44 2022 InstallationDate: Installed on 2020-02-02 (826 days ago) InstallationMedia: Lubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017.1) MachineType: Dell Inc. Precision WorkStation T7500 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=93fc02c6-baa4-4282-96d7-ea5ad53b0c78 ro ipv6.disable=1 splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/15/2018 dmi.bios.release: 0.0 dmi.bios.vendor: Dell Inc. dmi.bios.version: A18 dmi.board.name: 0D881F dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA18:bd10/15/2018:br0.0:svnDellInc.:pnPrecisionWorkStationT7500:pvr:rvnDellInc.:rn0D881F:rvrA05:cvnDellInc.:ct7:cvr:sku: dmi.product.name: Precision WorkStation T7500 dmi.sys.vendor: Dell Inc. To manage notifications
[Kernel-packages] [Bug 2024965] Re: 6.3.0-7 freezes early at startup on Dell Latitude E6530
** Tags added: mantic regression-release ** Tags removed: regression-release ** Tags added: regression ** Changed in: linux (Ubuntu) Importance: Undecided => High -- 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/2024965 Title: 6.3.0-7 freezes early at startup on Dell Latitude E6530 Status in linux package in Ubuntu: New Bug description: When starting the laptop with kernel 6.3.0-7 on Mantic Minotaur, the system freezes early in the boot process even before the GRUB background image gets replaced. Trying to boot the rescue system and resuming hangs at a white non- blinking underscore cursor in the upper left corner. Booting into the system with the earlier 6.2.0-21 works without any issues. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2024965/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
