[Kernel-packages] [Bug 2008186] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2008186 Title: amdgpu reset during firefox video Status in linux package in Ubuntu: Confirmed Bug description: My screen suddenly froze when watching a hardware-accelerated YouTube video in Firefox. The sound continued to play until my next step. I switched to TT1 to find out that the GPU reset in dmesg. I am happy that it didn't crash my whole machine like my computer with an older GPU, but the GPU shouldn't be crashing. I tried to do `kwin_wayland --replace`, but in addition to losing all my windows as that feature is missing in kwin, my second (right-side) monitor showed a trail of cursors (software cursors enabled) and was flickering when I opened a Konsole window unlike my left monitor. When I did `killall5`, the flickering stopped and I was back at lightdm. When I logged back in, my taskbar that I have on my right monitor was moved to my left one and I had to drag it back. # lsb_release -rd Description:Ubuntu 22.10 Release:22.10 # apt-cache policy linux-image-generic linux-image-generic: Installed: (none) Candidate: 5.19.0.31.28 Version table: 5.19.0.31.28 500 500 http://gpl.savoirfairelinux.net/pub/mirrors/ubuntu kinetic-updates/main amd64 Packages 500 http://gpl.savoirfairelinux.net/pub/mirrors/ubuntu kinetic-security/main amd64 Packages 5.19.0.21.21 500 500 http://gpl.savoirfairelinux.net/pub/mirrors/ubuntu kinetic/main amd64 Packages # version.log Attached by apport # lspci-vnvn.log Attached by apport # Expected behavior To be able to watch to videos without my GPU crashing. # Actual behavior The GPU crashes as described above and as logged in dmesg. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-31-generic 5.19.0-31.32 ProcVersionSignature: Ubuntu 5.19.0-31.32-generic 5.19.17 Uname: Linux 5.19.0-31-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: home 46003 F wireplumber /dev/snd/controlC0: home 46003 F wireplumber /dev/snd/seq:home 46001 F pipewire CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Feb 23 01:55:52 2023 InstallationDate: Installed on 2022-11-05 (110 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) IwConfig: lono wireless extensions. enp39s0 no wireless extensions. docker0 no wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7C37 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-31-generic root=/dev/mapper/vgubuntu-root ro quiet splash amdgpu.runpm=0 vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.19.0-31-generic N/A linux-backports-modules-5.19.0-31-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1.4 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/10/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: H.I0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X570-A PRO (MS-7C37) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 3.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 3.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrH.I0:bd08/10/2022:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C37:pvr3.0:rvnMicro-StarInternationalCo.,Ltd.:rnX570-APRO(MS-7C37):rvr3.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr3.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7C37 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 3.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008186/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008113] Re: Add firmware for amdgpu products with GC 11.01
** Tags added: kern-5797 -- 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/2008113 Title: Add firmware for amdgpu products with GC 11.01 Status in HWE Next: New Status in linux-firmware package in Ubuntu: In Progress Status in linux-firmware source package in Jammy: In Progress Status in linux-firmware source package in Lunar: In Progress Bug description: Firmware has been submitted upstream for a product that contains the IP blocks: DCN 3.1.4 GC 11.0.1 SDMA 6.0.1 PSP 13.0.4 VCN 4.0.2 Upstreamed commits: 5c11a374 amdgpu: Add VCN 4.0.2 firmware 5fe2d73c amdgpu: Add PSP 13.0.4 firmware a3332f8b amdgpu: Add SDMA 6.0.1 fimware 4535de67 amdgpu: Add GC 11.0.1 firmware 2e93e4c9 amdgpu: Add DCN 3.1.4 firmware c0a0bc23 amdgpu: Update GC 11.0.1 firmware To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2008113/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008188] [NEW] blacklist: Problem blacklisting hash
Public bug reported: When boot up the system from oem-6.1 kernel, some errors will printed in the console. Jan 04 05:28:09 Fenrir2-AMD-2 kernel: blacklist: Problem blacklisting hash (-13) Jan 04 05:28:09 Fenrir2-AMD-2 kernel: blacklist: Problem blacklisting hash (-13) Jan 04 05:28:09 Fenrir2-AMD-2 kernel: blacklist: Problem blacklisting hash (-13) Jan 04 05:28:09 Fenrir2-AMD-2 kernel: blacklist: Problem blacklisting hash (-13) Jan 04 05:28:09 Fenrir2-AMD-2 kernel: blacklist: Problem blacklisting hash (-13) Jan 04 05:28:09 Fenrir2-AMD-2 kernel: blacklist: Problem blacklisting hash (-13) ** Affects: linux-oem-6.1 (Ubuntu) Importance: Undecided Status: New ** Package changed: linux (Ubuntu) => linux-oem-6.1 (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/2008188 Title: blacklist: Problem blacklisting hash Status in linux-oem-6.1 package in Ubuntu: New Bug description: When boot up the system from oem-6.1 kernel, some errors will printed in the console. Jan 04 05:28:09 Fenrir2-AMD-2 kernel: blacklist: Problem blacklisting hash (-13) Jan 04 05:28:09 Fenrir2-AMD-2 kernel: blacklist: Problem blacklisting hash (-13) Jan 04 05:28:09 Fenrir2-AMD-2 kernel: blacklist: Problem blacklisting hash (-13) Jan 04 05:28:09 Fenrir2-AMD-2 kernel: blacklist: Problem blacklisting hash (-13) Jan 04 05:28:09 Fenrir2-AMD-2 kernel: blacklist: Problem blacklisting hash (-13) Jan 04 05:28:09 Fenrir2-AMD-2 kernel: blacklist: Problem blacklisting hash (-13) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.1/+bug/2008188/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008186] [NEW] amdgpu reset during firefox video
Public bug reported: My screen suddenly froze when watching a hardware-accelerated YouTube video in Firefox. The sound continued to play until my next step. I switched to TT1 to find out that the GPU reset in dmesg. I am happy that it didn't crash my whole machine like my computer with an older GPU, but the GPU shouldn't be crashing. I tried to do `kwin_wayland --replace`, but in addition to losing all my windows as that feature is missing in kwin, my second (right-side) monitor showed a trail of cursors (software cursors enabled) and was flickering when I opened a Konsole window unlike my left monitor. When I did `killall5`, the flickering stopped and I was back at lightdm. When I logged back in, my taskbar that I have on my right monitor was moved to my left one and I had to drag it back. # lsb_release -rd Description:Ubuntu 22.10 Release:22.10 # apt-cache policy linux-image-generic linux-image-generic: Installed: (none) Candidate: 5.19.0.31.28 Version table: 5.19.0.31.28 500 500 http://gpl.savoirfairelinux.net/pub/mirrors/ubuntu kinetic-updates/main amd64 Packages 500 http://gpl.savoirfairelinux.net/pub/mirrors/ubuntu kinetic-security/main amd64 Packages 5.19.0.21.21 500 500 http://gpl.savoirfairelinux.net/pub/mirrors/ubuntu kinetic/main amd64 Packages # version.log Attached by apport # lspci-vnvn.log Attached by apport # Expected behavior To be able to watch to videos without my GPU crashing. # Actual behavior The GPU crashes as described above and as logged in dmesg. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-31-generic 5.19.0-31.32 ProcVersionSignature: Ubuntu 5.19.0-31.32-generic 5.19.17 Uname: Linux 5.19.0-31-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: home 46003 F wireplumber /dev/snd/controlC0: home 46003 F wireplumber /dev/snd/seq:home 46001 F pipewire CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Feb 23 01:55:52 2023 InstallationDate: Installed on 2022-11-05 (110 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) IwConfig: lono wireless extensions. enp39s0 no wireless extensions. docker0 no wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7C37 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-31-generic root=/dev/mapper/vgubuntu-root ro quiet splash amdgpu.runpm=0 vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.19.0-31-generic N/A linux-backports-modules-5.19.0-31-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1.4 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/10/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: H.I0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X570-A PRO (MS-7C37) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 3.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 3.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrH.I0:bd08/10/2022:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C37:pvr3.0:rvnMicro-StarInternationalCo.,Ltd.:rnX570-APRO(MS-7C37):rvr3.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr3.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7C37 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 3.0 dmi.sys.vendor: Micro-Star International Co., Ltd. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic wayland-session -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2008186 Title: amdgpu reset during firefox video Status in linux package in Ubuntu: New Bug description: My screen suddenly froze when watching a hardware-accelerated YouTube video in Firefox. The sound continued to play until my next step. I switched to TT1 to find out that the GPU reset in dmesg. I am happy that it didn't crash my whole machine like my computer with an older GPU, but the GPU shouldn't be crashing. I tried to do `kwin_wayland --replace`, but in addition to losing all my windows as that feature is missing in kwin, my second (right-side) monitor showed a trail of cursors (software cursors enabled) and was flickering when I opened a Konsole window unlike my left monitor. When I did `killall5`, the flickering stopped and I was back at lightdm. When I logged back in, my taskbar that
[Kernel-packages] [Bug 2008113] Re: Add firmware for amdgpu products with GC 11.01
SRU: * https://lists.ubuntu.com/archives/kernel-team/2023-February/137279.html (jammy) * https://lists.ubuntu.com/archives/kernel-team/2023-February/137280.html (lunar) ** Changed in: linux-firmware (Ubuntu Lunar) Status: Confirmed => In Progress ** Changed in: linux-firmware (Ubuntu Jammy) Importance: Undecided => High ** Changed in: linux-firmware (Ubuntu Lunar) Importance: Undecided => High ** Changed in: linux-firmware (Ubuntu Jammy) Assignee: (unassigned) => You-Sheng Yang (vicamo) ** Changed in: linux-firmware (Ubuntu Lunar) Assignee: (unassigned) => You-Sheng Yang (vicamo) -- 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/2008113 Title: Add firmware for amdgpu products with GC 11.01 Status in HWE Next: New Status in linux-firmware package in Ubuntu: In Progress Status in linux-firmware source package in Jammy: In Progress Status in linux-firmware source package in Lunar: In Progress Bug description: Firmware has been submitted upstream for a product that contains the IP blocks: DCN 3.1.4 GC 11.0.1 SDMA 6.0.1 PSP 13.0.4 VCN 4.0.2 Upstreamed commits: 5c11a374 amdgpu: Add VCN 4.0.2 firmware 5fe2d73c amdgpu: Add PSP 13.0.4 firmware a3332f8b amdgpu: Add SDMA 6.0.1 fimware 4535de67 amdgpu: Add GC 11.0.1 firmware 2e93e4c9 amdgpu: Add DCN 3.1.4 firmware c0a0bc23 amdgpu: Update GC 11.0.1 firmware To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2008113/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-restricted-modules-gcp/5.19.0-1018.20)
All autopkgtests for the newly accepted linux-restricted-modules-gcp (5.19.0-1018.20) for kinetic have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-515/515.86.01-0ubuntu0.22.10.1 (amd64) nvidia-graphics-drivers-390/390.157-0ubuntu0.22.10.1 (i386) nvidia-graphics-drivers-515-server/515.86.01-0ubuntu0.22.10.1 (amd64) nvidia-graphics-drivers-470/470.161.03-0ubuntu0.22.10.1 (amd64) nvidia-graphics-drivers-525/525.85.05-0ubuntu0.22.10.1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/kinetic/update_excuses.html#linux-restricted-modules-gcp [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1988836] Autopkgtest regression report (linux-restricted-modules-gcp/5.19.0-1018.20)
All autopkgtests for the newly accepted linux-restricted-modules-gcp (5.19.0-1018.20) for kinetic have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-515/515.86.01-0ubuntu0.22.10.1 (amd64) nvidia-graphics-drivers-390/390.157-0ubuntu0.22.10.1 (i386) nvidia-graphics-drivers-515-server/515.86.01-0ubuntu0.22.10.1 (amd64) nvidia-graphics-drivers-470/470.161.03-0ubuntu0.22.10.1 (amd64) nvidia-graphics-drivers-525/525.85.05-0ubuntu0.22.10.1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/kinetic/update_excuses.html#linux-restricted-modules-gcp [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1988836 Title: LRMv7: Enable the open NVIDIA kernel modules Status in linux-restricted-modules package in Ubuntu: In Progress Status in nvidia-graphics-drivers-515 package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in linux-restricted-modules source package in Focal: In Progress Status in nvidia-graphics-drivers-515 source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Focal: Fix Committed Status in linux-restricted-modules source package in Jammy: In Progress Status in nvidia-graphics-drivers-515 source package in Jammy: Fix Released Status in ubuntu-drivers-common source package in Jammy: Fix Committed Bug description: [ Impact ] * The 515 series introduced open kernel modules for the NVIDIA driver. They come with an open source licence, and should be provided as an option for datacenter GPUs: https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/ Currently, this is only production-ready (and enabled) on datacenter GPUs. * We should enable signed modules for the 515-open drivers, giving users the option to try the drivers. * The ubuntu-drivers tool should set a lower priority for the -open flavour, so that we do not end up recommending it over the plain 515 flavour. [ Test Plan ] * [ubuntu-drivers-common]: "sudo ubuntu-drivers install (to make sure the driver is not installed by default)" * [nvidia driver] "sudo ubuntu-drivers install nvidia:515-open" to make sure that the driver can be installed manually. Please make sure that this installs the correct linux-restricted- modules. Note: support for GeForce and Workstation GPUs is alpha-quality, and is disabled by default. This means that desktop testing is not needed at the moment. [ Where problems could occur ] * This adds a new driver combination, which is not meant to be default, and is only enabled for a limited amount of devices (datacenter GPUs). * We need to be sure that the driver is not recommended over the other drivers. [ Other Info ] - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2000418] Re: Linux Image 5.15.0-56.62 (Jammy) crashes Surface Book 2
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2000418 Title: Linux Image 5.15.0-56.62 (Jammy) crashes Surface Book 2 Status in linux package in Ubuntu: Expired Bug description: Problem Version: linux (5.15.0-56.62) jammy; urgency=medium Good Version: linux (5.15.0-53.59) jammy; urgency=medium Laptop: Microsoft Surface Book 2 OS Used: Ubuntu 22.04 x86_64 Descripe: Ubuntu 22.04 ran well on Surface Book 2 until linux-image==5.15.0-53.59. Yesterday I upgrade the latest kernel 5.15.0-56.62 and then graphic driver is totally crashed. I have to fall back to use 5.15.0-53.59 instead. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2000418/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-restricted-modules-gcp-5.15/5.15.0-1030.37~20.04.1)
All autopkgtests for the newly accepted linux-restricted-modules-gcp-5.15 (5.15.0-1030.37~20.04.1) for focal have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-390/390.157-0ubuntu0.20.04.1 (i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-restricted-modules-gcp-5.15 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1988836] Autopkgtest regression report (linux-restricted-modules-gcp-5.15/5.15.0-1030.37~20.04.1)
All autopkgtests for the newly accepted linux-restricted-modules-gcp-5.15 (5.15.0-1030.37~20.04.1) for focal have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-390/390.157-0ubuntu0.20.04.1 (i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-restricted-modules-gcp-5.15 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1988836 Title: LRMv7: Enable the open NVIDIA kernel modules Status in linux-restricted-modules package in Ubuntu: In Progress Status in nvidia-graphics-drivers-515 package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in linux-restricted-modules source package in Focal: In Progress Status in nvidia-graphics-drivers-515 source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Focal: Fix Committed Status in linux-restricted-modules source package in Jammy: In Progress Status in nvidia-graphics-drivers-515 source package in Jammy: Fix Released Status in ubuntu-drivers-common source package in Jammy: Fix Committed Bug description: [ Impact ] * The 515 series introduced open kernel modules for the NVIDIA driver. They come with an open source licence, and should be provided as an option for datacenter GPUs: https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/ Currently, this is only production-ready (and enabled) on datacenter GPUs. * We should enable signed modules for the 515-open drivers, giving users the option to try the drivers. * The ubuntu-drivers tool should set a lower priority for the -open flavour, so that we do not end up recommending it over the plain 515 flavour. [ Test Plan ] * [ubuntu-drivers-common]: "sudo ubuntu-drivers install (to make sure the driver is not installed by default)" * [nvidia driver] "sudo ubuntu-drivers install nvidia:515-open" to make sure that the driver can be installed manually. Please make sure that this installs the correct linux-restricted- modules. Note: support for GeForce and Workstation GPUs is alpha-quality, and is disabled by default. This means that desktop testing is not needed at the moment. [ Where problems could occur ] * This adds a new driver combination, which is not meant to be default, and is only enabled for a limited amount of devices (datacenter GPUs). * We need to be sure that the driver is not recommended over the other drivers. [ Other Info ] - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1988346] Re: cm32181 module error blocking suspend
https://git.kernel.org/torvalds/c/ee3c5b644a0fdcfed27515a39fb2dd3a016704c1 ** Changed in: linux (Ubuntu) Assignee: Kai-Heng Feng (kaihengfeng) => (unassigned) -- 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/1988346 Title: cm32181 module error blocking suspend Status in linux package in Ubuntu: Confirmed Bug description: After updating to 22.04.1 (from 20.04) suspend gets interrupted and the system returns after a few seconds. journalctl output ``` Aug 31 19:59:32 nmurphy-laptop kernel: PM: suspend entry (deep) Aug 31 19:59:32 nmurphy-laptop kernel: Filesystems sync: 0.044 seconds Aug 31 19:59:37 nmurphy-laptop kernel: Freezing user space processes ... (elapsed 0.002 seconds) done. Aug 31 19:59:37 nmurphy-laptop kernel: OOM killer disabled. Aug 31 19:59:37 nmurphy-laptop kernel: Freezing remaining freezable tasks ... (elapsed 3.894 seconds) done. Aug 31 19:59:37 nmurphy-laptop kernel: printk: Suspending console(s) (use no_console_suspend to debug) Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache Aug 31 19:59:37 nmurphy-laptop kernel: PM: dpm_run_callback(): acpi_subsys_suspend+0x0/0x60 returns -121 Aug 31 19:59:37 nmurphy-laptop kernel: cm32181 i2c-CPLM3218:00: PM: failed to suspend: error -121 Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Stopping disk Aug 31 19:59:37 nmurphy-laptop kernel: PM: Some devices failed to suspend, or early wake event detected Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Starting disk Aug 31 19:59:37 nmurphy-laptop kernel: tpm tpm0: TPM is disabled/deactivated (0x6) Aug 31 19:59:37 nmurphy-laptop kernel: OOM killer enabled. Aug 31 19:59:37 nmurphy-laptop kernel: Restarting tasks ... done. Aug 31 19:59:37 nmurphy-laptop bluetoothd[1129]: Controller resume with wake event 0x0 Aug 31 19:59:37 nmurphy-laptop kernel: PM: suspend exit Aug 31 19:59:37 nmurphy-laptop kernel: PM: suspend entry (s2idle) Aug 31 19:59:37 nmurphy-laptop kernel: Filesystems sync: 0.051 seconds Aug 31 19:59:44 nmurphy-laptop kernel: Freezing user space processes ... (elapsed 0.005 seconds) done. Aug 31 19:59:44 nmurphy-laptop kernel: OOM killer disabled. Aug 31 19:59:44 nmurphy-laptop kernel: Freezing remaining freezable tasks ... Aug 31 19:59:44 nmurphy-laptop kernel: psmouse serio2: trackpoint: IBM TrackPoint firmware: 0x0e, buttons: 3/3 Aug 31 19:59:44 nmurphy-laptop kernel: input: TPPS/2 IBM TrackPoint as /devices/rmi4-00/rmi4-00.fn03/serio2/input/input196 Aug 31 19:59:44 nmurphy-laptop kernel: (elapsed 6.917 seconds) done. Aug 31 19:59:44 nmurphy-laptop kernel: printk: Suspending console(s) (use no_console_suspend to debug) Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache Aug 31 19:59:44 nmurphy-laptop kernel: PM: dpm_run_callback(): acpi_subsys_suspend+0x0/0x60 returns -121 Aug 31 19:59:44 nmurphy-laptop kernel: cm32181 i2c-CPLM3218:00: PM: failed to suspend: error -121 Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Stopping disk Aug 31 19:59:44 nmurphy-laptop kernel: PM: Some devices failed to suspend, or early wake event detected Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Starting disk Aug 31 19:59:44 nmurphy-laptop kernel: tpm tpm0: TPM is disabled/deactivated (0x6) Aug 31 19:59:44 nmurphy-laptop kernel: OOM killer enabled. Aug 31 19:59:44 nmurphy-laptop kernel: Restarting tasks ... done. Aug 31 19:59:44 nmurphy-laptop kernel: PM: suspend exit Aug 31 19:59:44 nmurphy-laptop systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully. Aug 31 19:59:44 nmurphy-laptop bluetoothd[1129]: Controller resume with wake event 0x0 Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65536]: Failed to put system to sleep. System resumed again: Remote I/O error Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]: /dev/sda: Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]: setting Advanced Power Management level to 0xfe (254) Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]: APM_level= 254 Aug 31 19:59:44 nmurphy-laptop NetworkManager[1131]: [1661972384.8203] audit: op="radio-control" arg="wwan-enabled:off" pid=65646 uid=0 result="success" Aug 31 19:59:44 nmurphy-laptop systemd[1]: systemd-suspend.service: Main process exited, code=exited, status=1/FAILURE Aug 31 19:59:44 nmurphy-laptop systemd[1]: systemd-suspend.service: Failed with result 'exit-code'. Aug 31 19:59:44 nmurphy-laptop systemd[1]: Failed to start System Suspend. Aug 31 19:59:44 nmurphy-laptop systemd[1]: Dependency failed for Suspend. Aug 31 19:59:44 nmurphy-laptop systemd[1]: suspend.target: Job suspend.target/start failed with result 'dependency'. Aug 31 19:59:44 nmurphy-laptop systemd[1]: Stopped target Sleep. Aug 31 19:59:44 nmurphy-laptop
[Kernel-packages] [Bug 2006914] Re: Raptor Lake S/P Enablement
** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy verification-testing-passed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-iotg in Ubuntu. https://bugs.launchpad.net/bugs/2006914 Title: Raptor Lake S/P Enablement Status in linux-intel-iotg package in Ubuntu: Invalid Status in linux-intel-iotg source package in Jammy: Fix Committed Bug description: [Summary] Raptor Lake S/P Enablement To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-intel-iotg/+bug/2006914/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1996609] Re: AX210 (8086:6020) WLAN init failed ucode -5 on 5.15 intel IoTG kernel
** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy verification-testing-passed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-iotg in Ubuntu. https://bugs.launchpad.net/bugs/1996609 Title: AX210 (8086:6020) WLAN init failed ucode -5 on 5.15 intel IoTG kernel Status in HWE Next: New Status in linux-intel-iotg package in Ubuntu: Invalid Status in linux-intel-iotg-5.15 package in Ubuntu: Invalid Status in linux-intel-iotg source package in Focal: Invalid Status in linux-intel-iotg-5.15 source package in Focal: New Status in linux-intel-iotg source package in Jammy: Fix Committed Status in linux-intel-iotg-5.15 source package in Jammy: Invalid Bug description: [Summary] AX210 (8086:6020) WLAN init failed ucode -5 on 5.15 Intel IoTG kernel. [Steps to reproduce] install 5.15 Intel IoTG kernel. [Expected result] WLAN works with no problem. [Actual result] Can't detect WLAN. [Failure rate] 100% The ucode version 66 would not be loaded successfully on this particular model with the folloing error messages: [ 13.231830] kernel: iwlwifi :02:00.0: Detected RF GF, rfid=0x10d000 [ 13.232964] kernel: iwlwifi :02:00.0: Microcode SW error detected. Restarting 0x0. [ 13.233061] kernel: iwlwifi :02:00.0: Start IWL Error Log Dump: [ 13.233062] kernel: iwlwifi :02:00.0: Transport status: 0x004A, valid: 6 [ 13.233064] kernel: iwlwifi :02:00.0: Loaded firmware version: 66.f1c864e0.0 ty-a0-gf-a0-66.ucode [ 13.233065] kernel: iwlwifi :02:00.0: 0x0071 | NMI_INTERRUPT_UMAC_FATAL [ 13.233066] kernel: iwlwifi :02:00.0: 0x002002F0 | trm_hw_status0 [ 13.233067] kernel: iwlwifi :02:00.0: 0x | trm_hw_status1 [ 13.233068] kernel: iwlwifi :02:00.0: 0x004DA722 | branchlink2 ... [ 14.094020] kernel: iwlwifi :02:00.0: Failed to run INIT ucode: -5 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1996609/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1971151] Re: [SRU][Ubuntu 22.04.1] mpi3mr: Add management application interface(BSG) support
** Description changed: SRU Justification: [Impact] Request to include below mpi3mr driver bug fix patches in Ubuntu 22.04.1(5.15 kernel). These patches got accepted by the upstream and please find the corresponding commit IDs as below: f304d35e5995 scsi: mpi3mr: Update driver version to 8.0.0.69.0 7dbd0dd8cde3 scsi: mpi3mr: Add support for NVMe passthrough 986d6bad2103 scsi: mpi3mr: Expose adapter state to sysfs 43ca11005098 scsi: mpi3mr: Add support for PEL commands 506bc1a0d6ba scsi: mpi3mr: Add support for MPT commands f3de4706c1e0 scsi: mpi3mr: Move data structures/definitions from MPI headers to uapi header f5e6d5a34376 scsi: mpi3mr: Add support for driver commands 4268fa751365 scsi: mpi3mr: Add bsg device support 1fcbe4c49039 scsi: mpi3mr: Fix kernel-doc 4094981db7b6 scsi: mpi3mr: Rework mrioc->bsg_device model to fix warnings 9feb5c4c3f95 scsi: mpi3mr: Add target device related sysfs attributes e51e76edddb1 scsi: mpi3mr: Add shost related sysfs attributes bc7896d31a92 scsi: mpi3mr: Return error if dma_alloc_coherent() fails a25eafd13e5f scsi: mpi3mr: Fix a NULL vs IS_ERR() bug in mpi3mr_bsg_init() 256bd4f23d9c scsi: mpi3mr: Return I/Os to an unrecoverable HBA with DID_ERROR 2dd8389f96d6 scsi: mpi3mr: Hidden drives not removed during soft reset 1aa529d40025 scsi: mpi3mr: Increase I/O timeout value to 60s - [Test Plan] 1. Install and boot kernel 2. Run basic I/O tests [Where problems could occur] Moderate to low regression risk for the kernel as most changes are in the driver [Other Info] - https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/mpi3mr_bsg_support + https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/mpi3mr_bsg_support_3 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1971151 Title: [SRU][Ubuntu 22.04.1] mpi3mr: Add management application interface(BSG) support Status in linux package in Ubuntu: In Progress Bug description: SRU Justification: [Impact] Request to include below mpi3mr driver bug fix patches in Ubuntu 22.04.1(5.15 kernel). These patches got accepted by the upstream and please find the corresponding commit IDs as below: f304d35e5995 scsi: mpi3mr: Update driver version to 8.0.0.69.0 7dbd0dd8cde3 scsi: mpi3mr: Add support for NVMe passthrough 986d6bad2103 scsi: mpi3mr: Expose adapter state to sysfs 43ca11005098 scsi: mpi3mr: Add support for PEL commands 506bc1a0d6ba scsi: mpi3mr: Add support for MPT commands f3de4706c1e0 scsi: mpi3mr: Move data structures/definitions from MPI headers to uapi header f5e6d5a34376 scsi: mpi3mr: Add support for driver commands 4268fa751365 scsi: mpi3mr: Add bsg device support 1fcbe4c49039 scsi: mpi3mr: Fix kernel-doc 4094981db7b6 scsi: mpi3mr: Rework mrioc->bsg_device model to fix warnings 9feb5c4c3f95 scsi: mpi3mr: Add target device related sysfs attributes e51e76edddb1 scsi: mpi3mr: Add shost related sysfs attributes bc7896d31a92 scsi: mpi3mr: Return error if dma_alloc_coherent() fails a25eafd13e5f scsi: mpi3mr: Fix a NULL vs IS_ERR() bug in mpi3mr_bsg_init() 256bd4f23d9c scsi: mpi3mr: Return I/Os to an unrecoverable HBA with DID_ERROR 2dd8389f96d6 scsi: mpi3mr: Hidden drives not removed during soft reset 1aa529d40025 scsi: mpi3mr: Increase I/O timeout value to 60s [Test Plan] 1. Install and boot kernel 2. Run basic I/O tests [Where problems could occur] Moderate to low regression risk for the kernel as most changes are in the driver [Other Info] https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/mpi3mr_bsg_support_3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971151/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008149] Re: Bluetooth Audio Broken After Suspend
** Also affects: pipewire (Ubuntu) Importance: Undecided Status: New ** Tags added: kinetic ** Tags added: a2dp suspend-resume -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2008149 Title: Bluetooth Audio Broken After Suspend Status in bluez package in Ubuntu: New Status in pipewire package in Ubuntu: New Bug description: Release: Description: Ubuntu 22.10 Release: 22.10 Package Version: isa~ apt-cache policy bluez bluez: Installed: 5.65-0ubuntu1 Candidate: 5.65-0ubuntu1 Version table: *** 5.65-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu kinetic/main amd64 Packages 100 /var/lib/dpkg/status Hardware: = Model: Apple Inc. MacBookPro9,2 isa~ lsusb | grep -i blue Bus 002 Device 009: ID 05ac:821d Apple, Inc. Bluetooth USB Host Controller Bus 002 Device 004: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth) Kmods: == bluetooth 827392 54 btrtl,btmtk,btintel,btbcm,bnep,btusb,rfcomm Symptom: Pausing sound output (with bluetooth device as sink) will often lead to a failed suspend / resume that leaves audio in an unusable state. Logs indicate that suspend fails, but it looks like the failure path is broken in some way that renders audio unusable when this occurs. This requires a reconnect to recover in all cases, and occasionally even a reboot is required. I have attached debug logs from `bluetooth.service`. I assume hci logs are not required in this case, but if they are please let me know. I can test proposed fixes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2008149/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008149] [NEW] Bluetooth Audio Broken After Suspend
Public bug reported: Release: Description:Ubuntu 22.10 Release:22.10 Package Version: isa~ apt-cache policy bluez bluez: Installed: 5.65-0ubuntu1 Candidate: 5.65-0ubuntu1 Version table: *** 5.65-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu kinetic/main amd64 Packages 100 /var/lib/dpkg/status Hardware: = Model: Apple Inc. MacBookPro9,2 isa~ lsusb | grep -i blue Bus 002 Device 009: ID 05ac:821d Apple, Inc. Bluetooth USB Host Controller Bus 002 Device 004: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth) Kmods: == bluetooth 827392 54 btrtl,btmtk,btintel,btbcm,bnep,btusb,rfcomm Symptom: Pausing sound output (with bluetooth device as sink) will often lead to a failed suspend / resume that leaves audio in an unusable state. Logs indicate that suspend fails, but it looks like the failure path is broken in some way that renders audio unusable when this occurs. This requires a reconnect to recover in all cases, and occasionally even a reboot is required. I have attached debug logs from `bluetooth.service`. I assume hci logs are not required in this case, but if they are please let me know. I can test proposed fixes. ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Attachment added: "debug mode logs" https://bugs.launchpad.net/bugs/2008149/+attachment/5649257/+files/bluetooth.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2008149 Title: Bluetooth Audio Broken After Suspend Status in bluez package in Ubuntu: New Bug description: Release: Description: Ubuntu 22.10 Release: 22.10 Package Version: isa~ apt-cache policy bluez bluez: Installed: 5.65-0ubuntu1 Candidate: 5.65-0ubuntu1 Version table: *** 5.65-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu kinetic/main amd64 Packages 100 /var/lib/dpkg/status Hardware: = Model: Apple Inc. MacBookPro9,2 isa~ lsusb | grep -i blue Bus 002 Device 009: ID 05ac:821d Apple, Inc. Bluetooth USB Host Controller Bus 002 Device 004: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth) Kmods: == bluetooth 827392 54 btrtl,btmtk,btintel,btbcm,bnep,btusb,rfcomm Symptom: Pausing sound output (with bluetooth device as sink) will often lead to a failed suspend / resume that leaves audio in an unusable state. Logs indicate that suspend fails, but it looks like the failure path is broken in some way that renders audio unusable when this occurs. This requires a reconnect to recover in all cases, and occasionally even a reboot is required. I have attached debug logs from `bluetooth.service`. I assume hci logs are not required in this case, but if they are please let me know. I can test proposed fixes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2008149/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2003816] Re: Regression in ext4 during online resize
This bug is awaiting verification that the linux-gke/5.15.0-1028.33 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-gke -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/2003816 Title: Regression in ext4 during online resize Status in linux package in Ubuntu: Invalid Status in linux-gcp package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-gcp source package in Jammy: Fix Committed Bug description: Issue resize2fs utility is used to resize the filesystem and is idempotent in nature. But in the 5.15 kernel, successive execution of resize2fs is returning error. Reproduction step (on AWS): Create an AWS instance with AMI ami-056a67ea1b8ffa0fc (Linux 5.15.0-1022-aws) in us-west-2 region and attach an EBS volume. Format and mount the disk - sudo mkfs.ext4 /dev/xvdb, sudo mkdir -p /mnt/ssd0, sudo mount /dev/xvdb /mnt/ssd0 Increase the size of EBS volume. Run sudo resize2fs /dev/xvdb multiple times. The first execution returns - $ sudo resize2fs /dev/xvdb resize2fs 1.45.5 (07-Jan-2020) Filesystem at /dev/xvdb is mounted on /mnt/ssd0; on-line resizing required old_desc_blocks = 2, new_desc_blocks = 3 The filesystem on /dev/xvdb is now 5242880 (4k) blocks long. The following execution returns - $ sudo resize2fs /dev/xvdb resize2fs 1.45.5 (07-Jan-2020) The filesystem is already 5242880 (4k) blocks long. Nothing to do! When you run the same step on the latest image ami-0a1d6d351894df6cc (Linux 5.15.0-1026-aws). The first execution returns - $ sudo resize2fs /dev/xvdb resize2fs 1.45.5 (07-Jan-2020) Filesystem at /dev/xvdb is mounted on /mnt/ssd0; on-line resizing required old_desc_blocks = 2, new_desc_blocks = 3 The filesystem on /dev/xvdb is now 5242880 (4k) blocks long. The following execution returns $ sudo resize2fs /dev/xvdb resize2fs 1.45.5 (07-Jan-2020) resize2fs: Superblock checksum does not match superblock while trying to open /dev/xvdb Couldn't find valid filesystem superblock. FIX: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=a408f33e895e455f16cf964cb5cd4979b658db7b To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2003816/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1987829] Re: LG Gram 12gen high CPU use when USB-C/TB is in use
Does rebooting from Windows (comment #5) temporarily fixes the issue for everyone? -- 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/1987829 Title: LG Gram 12gen high CPU use when USB-C/TB is in use Status in linux package in Ubuntu: Confirmed Status in linux package in Fedora: New Bug description: LG Gram laptop 17Z90Q with a Core i7-1260P CPU. Whenever an external monitor is connected to USB-C/Thunderbolt 4, average load goes above 3.0 and the machine is getting very hot. Output from top -H shows a lot of kworker CPU usage: top - 11:45:06 up 33 min, 2 users, load average: 3,30, 3,08, 2,79 Threads: 1442 total, 2 running, 1440 sleeping, 0 stopped, 0 zombie %Cpu(s): 0,1 us, 3,7 sy, 0,0 ni, 96,1 id, 0,0 wa, 0,0 hi, 0,1 si, 0,0 st MiB Mem : 15684,6 total, 8510,2 free, 2580,8 used, 4593,6 buff/cache MiB Swap: 3815,0 total, 3815,0 free, 0,0 used. 11326,9 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ WCHAN COMMAND 7766 root 20 0 0 0 0 R 19,8 0,0 0:56.05 worker_th+ kworker/0:2-events 196 root 20 0 0 0 0 D 15,8 0,0 1:18.12 ec_guard kworker/u32:2+USBC000:00-con0 10237 root 20 0 0 0 0 I 12,9 0,0 0:26.44 worker_th+ kworker/0:0-events 1027 root 20 0 0 0 0 I 6,6 0,0 0:43.30 worker_th+ kworker/1:3-events 10971 root 20 0 0 0 0 I 4,0 0,0 0:00.20 worker_th+ kworker/15:0-events 175 root 20 0 0 0 0 I 2,3 0,0 0:03.24 worker_th+ kworker/11:1-events 2410 root 20 0 0 0 0 I 1,7 0,0 0:05.49 worker_th+ kworker/9:3-events Perf shows a lot of time spent inside handle_irq_event/acpi_ev_gpe_detect/acpi_hw_gpe_read. Additionally, kernel log is getting spammed with these lines every 4 seconds (but also without any USB-C device attached): [ 223.514304] ACPI Error: No handler for Region [XIN1] (f2ad4f1f) [UserDefinedRegion] (20210730/evregion-130) [ 223.514323] ACPI Error: Region UserDefinedRegion (ID=143) has no handler (20210730/exfldio-261) [ 223.514337] Initialized Local Variables for Method [_TMP]: [ 223.514339] Local0: 21495082Integer 0034 [ 223.514349] No Arguments are initialized for method [_TMP] [ 223.514354] ACPI Error: Aborting method \_SB.PC00.LPCB.LGEC.SEN2._TMP due to previous error (AE_NOT_EXIST) (20210730/psparse-529) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-46-generic 5.15.0-46.49 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: me 1678 F pulseaudio /dev/snd/controlC1: me 1678 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass Date: Fri Aug 26 11:57:05 2022 InstallationDate: Installed on 2022-08-25 (1 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LG Electronics 17Z90Q-G.AA78N ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=e2f96916-a67c-432e-b687-730071271216 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/06/2022 dmi.bios.release: 0.1 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: A1ZG0380 X64 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 17Z90Q dmi.board.vendor: LG Electronics dmi.board.version: FAB1 dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LG Electronics dmi.chassis.version: 0.1 dmi.ec.firmware.release: 33.0 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrA1ZG0380X64:bd07/06/2022:br0.1:efr33.0:svnLGElectronics:pn17Z90Q-G.AA78N:pvr0.1:rvnLGElectronics:rn17Z90Q:rvrFAB1:cvnLGElectronics:ct10:cvr0.1:skuEVO: dmi.product.family: LG gram PC dmi.product.name: 17Z90Q-G.AA78N dmi.product.sku: EVO dmi.product.version: 0.1 dmi.sys.vendor: LG Electronics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987829/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe :
[Kernel-packages] [Bug 2006942] Re: With linux kernel 5.19.0-31 amd_pstate is not used, while with 5.19.0-29 and lower does
It gets disabled by commit ("cpufreq: amd-pstate: add amd-pstate driver
parameter for mode selection").
Use kernel parameter "amd_pstate=passive" to enable it once again.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
https://bugs.launchpad.net/bugs/2006942
Title:
With linux kernel 5.19.0-31 amd_pstate is not used, while with
5.19.0-29 and lower does
Status in linux package in Ubuntu:
Confirmed
Status in linux-signed package in Ubuntu:
Confirmed
Bug description:
After upgrading to 5.19.0-31 (two of my systems) CPU driver changes to
acpi-cpufreq. instead of amd_pstate.
This causes cpu to keep higher frequency and increased consumption.
```
root@zeus:/sys/devices/system/cpu/cpufreq/policy0# ls -l
total 0
-r--r--r-- 1 root root 4096 Feb 10 13:27 affected_cpus
-r--r--r-- 1 root root 4096 Feb 10 13:28 amd_pstate_highest_perf
-r--r--r-- 1 root root 4096 Feb 10 13:28 amd_pstate_lowest_nonlinear_freq
-r--r--r-- 1 root root 4096 Feb 10 13:28 amd_pstate_max_freq
-r--r--r-- 1 root root 4096 Feb 10 12:54 cpuinfo_max_freq
-r--r--r-- 1 root root 4096 Feb 10 13:27 cpuinfo_min_freq
-r--r--r-- 1 root root 4096 Feb 10 13:27 cpuinfo_transition_latency
-r--r--r-- 1 root root 4096 Feb 10 13:27 related_cpus
-r--r--r-- 1 root root 4096 Feb 10 12:54 scaling_available_governors
-r--r--r-- 1 root root 4096 Feb 10 13:27 scaling_cur_freq
-r--r--r-- 1 root root 4096 Feb 10 13:27 scaling_driver
-rw-r--r-- 1 root root 4096 Feb 10 12:54 scaling_governor
-rw-r--r-- 1 root root 4096 Feb 10 12:54 scaling_max_freq
-rw-r--r-- 1 root root 4096 Feb 10 12:54 scaling_min_freq
-rw-r--r-- 1 root root 4096 Feb 10 13:28 scaling_setspeed
root@zeus:/sys/devices/system/cpu/cpufreq/policy0#
```
with newer kernel also policy files for amd_pstate
Tried it on 2 Asus PN51-S1 systems with AMD Ryzen 7 5700U
I am currently staying at 5.19.0-29 as it is working better.
---
ProblemType: Bug
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k5.19.0-31-generic.
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1',
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p',
'/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0',
'/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CRDA: N/A
Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
CasperMD5CheckResult: pass
DistroRelease: Ubuntu 22.10
InstallationDate: Installed on 2022-11-18 (85 days ago)
InstallationMedia: Ubuntu-Server 22.10 "Kinetic Kudu" - Release amd64
(20221019)
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
MachineType: ASUSTeK COMPUTER INC. MINIPC PN51-S1
Package: linux-signed (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-31-generic
root=/dev/mapper/system-root ro
ProcVersionSignature: Ubuntu 5.19.0-31.32-generic 5.19.17
RelatedPackageVersions:
linux-restricted-modules-5.19.0-31-generic N/A
linux-backports-modules-5.19.0-31-generic N/A
linux-firmware 20220923.gitf09bebf3-0ubuntu1.3
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
Tags: kinetic uec-images
Uname: Linux 5.19.0-31-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
dmi.bios.date: 08/10/2022
dmi.bios.release: 1.12
dmi.bios.vendor: ASUSTeK COMPUTER INC.
dmi.bios.version: 0112
dmi.board.asset.tag: Default string
dmi.board.name: PN51-S1
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.:bvr0112:bd08/10/2022:br1.12:svnASUSTeKCOMPUTERINC.:pnMINIPCPN51-S1:pvr0112:rvnASUSTeKCOMPUTERINC.:rnPN51-S1:rvrTobefilledbyO.E.M.:cvnDefaultstring:ct35:cvrDefaultstring:sku:
dmi.product.family: Vivo PC
dmi.product.name: MINIPC PN51-S1
dmi.product.version: 0112
dmi.sys.vendor: ASUSTeK COMPUTER INC.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2006942/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to :
[Kernel-packages] [Bug 2007717] Re: Kernel linux-image-5.19.0-32 regression, compile speed down by 33%
Please try kernel parameter "amd_pstate=passive". -- 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/2007717 Title: Kernel linux-image-5.19.0-32 regression, compile speed down by 33% Status in linux package in Ubuntu: Incomplete Bug description: I just yesterday and the day before made some benchmark tests for a comparison between ext4 and zfs. I ran repeated builds of a large software package and it always came out to 45s. Now today I ran the same test a few times and it was always 60s. I noticed that today an update ran and that kernel 5.19.0-32 was installed. So just now I booted back to 5.15.0-60-generic:amd64 and ran the test again: back to 45s. I am running Ubuntu 22.04.1 LTS on a AMD Ryzen 3970X with 128GB RAM otherwise there is nothing very special going on. I ran the tests on ZFS and ext4, it makes no difference. To reproduce, I would think that compiling any decent sized software package one on 5.15 and then on 5.19 whould yield the same results. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-07-15 (217 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-32-generic root=UUID=c1b17af6-e10d-4836-a5d0-aa0c25802bca ro mitigations=off quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-32-generic N/A linux-backports-modules-5.19.0-32-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 Tags: wayland-session jammy Uname: Linux 5.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom davfs2 dip docker libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/01/2020 dmi.bios.release: 5.15 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.70 dmi.board.name: TRX40 Taichi 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.:bvrP1.70:bd06/01/2020:br5.15:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnTRX40Taichi: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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007717/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007717] Re: Kernel linux-image-5.19.0-32 regression, compile speed down by 33%
Maybe it shares the same root cause as LP: #2006942? -- 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/2007717 Title: Kernel linux-image-5.19.0-32 regression, compile speed down by 33% Status in linux package in Ubuntu: Incomplete Bug description: I just yesterday and the day before made some benchmark tests for a comparison between ext4 and zfs. I ran repeated builds of a large software package and it always came out to 45s. Now today I ran the same test a few times and it was always 60s. I noticed that today an update ran and that kernel 5.19.0-32 was installed. So just now I booted back to 5.15.0-60-generic:amd64 and ran the test again: back to 45s. I am running Ubuntu 22.04.1 LTS on a AMD Ryzen 3970X with 128GB RAM otherwise there is nothing very special going on. I ran the tests on ZFS and ext4, it makes no difference. To reproduce, I would think that compiling any decent sized software package one on 5.15 and then on 5.19 whould yield the same results. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-07-15 (217 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-32-generic root=UUID=c1b17af6-e10d-4836-a5d0-aa0c25802bca ro mitigations=off quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-32-generic N/A linux-backports-modules-5.19.0-32-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 Tags: wayland-session jammy Uname: Linux 5.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom davfs2 dip docker libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/01/2020 dmi.bios.release: 5.15 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.70 dmi.board.name: TRX40 Taichi 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.:bvrP1.70:bd06/01/2020:br5.15:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnTRX40Taichi: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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007717/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007717] Re: Kernel linux-image-5.19.0-32 regression, compile speed down by 33%
Does mainline kernel have the issue too? -- 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/2007717 Title: Kernel linux-image-5.19.0-32 regression, compile speed down by 33% Status in linux package in Ubuntu: Incomplete Bug description: I just yesterday and the day before made some benchmark tests for a comparison between ext4 and zfs. I ran repeated builds of a large software package and it always came out to 45s. Now today I ran the same test a few times and it was always 60s. I noticed that today an update ran and that kernel 5.19.0-32 was installed. So just now I booted back to 5.15.0-60-generic:amd64 and ran the test again: back to 45s. I am running Ubuntu 22.04.1 LTS on a AMD Ryzen 3970X with 128GB RAM otherwise there is nothing very special going on. I ran the tests on ZFS and ext4, it makes no difference. To reproduce, I would think that compiling any decent sized software package one on 5.15 and then on 5.19 whould yield the same results. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-07-15 (217 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-32-generic root=UUID=c1b17af6-e10d-4836-a5d0-aa0c25802bca ro mitigations=off quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-32-generic N/A linux-backports-modules-5.19.0-32-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 Tags: wayland-session jammy Uname: Linux 5.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom davfs2 dip docker libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/01/2020 dmi.bios.release: 5.15 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.70 dmi.board.name: TRX40 Taichi 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.:bvrP1.70:bd06/01/2020:br5.15:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnTRX40Taichi: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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007717/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1983297] Re: Additional fix for TGL + AUO panel flickering
Kernel version >= 5.16 don't need this quirk. ** Changed in: linux (Ubuntu Lunar) Status: Incomplete => Fix Released ** Changed in: linux (Ubuntu Kinetic) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1983297 Title: Additional fix for TGL + AUO panel flickering Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux source package in Kinetic: Fix Released Status in linux source package in Lunar: Fix Released Bug description: [Impact] "UBUNTU: SAUCE: drm/i915/display/psr: Fix flicker on TGL + AUO panel" alone used to fix the issue on the AUO panel. But the panel starts to flicker like crazy on top of the new stable commits. [Fix] Backport full fix for PSR2 selective fetch, but only enable it on TGL + specific AUO panel. The last three patches which enable PSR2 on ADL-P are dropped. [Test] Originally the backport regressed ADL + BOE panel, so this time we put extra effort to ensure those system are unaffected, while TGL + AUO panel is still fixed. [Where problems could occur] Most code changes only have functional impact when PSR2 selective fetch is enabled. Some of changes are under more general call path for hardware cursor rendering. Notes are added to describe the functional impact for each patch, so if regression really occurrs it's easier to spot the offending commit. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1983297/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007734] Re: Black screen on boot and tearing on resume on HP Envy x360
ADLP may be too new for 5.19. Please try some newer kernels. -- 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/2007734 Title: Black screen on boot and tearing on resume on HP Envy x360 Status in linux package in Ubuntu: Confirmed Bug description: I installed Ubuntu about 1 week ago on a new machine, after testing with a Live USB 22.10 that it was working reasonably well. While the live USB was working pretty well, including 3D acceleration, the installed system failed to display anything after the first mode setting. I was able to work around this first issue with: echo 'FRAMEBUFFER=y' | sudo tee /etc/initramfs-tools/conf.d/hp-envy-x360-quirk sudo update-initramfs -c -k all With this, the system starts correctly, with 3D acceleration. I noticed that, after enabling this option, the initrd image now contained i915 driver and firmware. However, just declaring "i915" /etc/initramfs-tools/modules did not appear to fix the issue. A second, possibly related issue, is that after resume, the screen was displaying random pixels of increasing intensity (tearing ?). I was able to work around this other issue with: echo 'GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i915.enable_psr=0 i915.enable_fbc=1"' | sudo tee /etc/default/grub.d/hp-envy-x360-quirk.cfg sudo update-grub With this second workaround in place, suspend/resumes has been working fine for at least the past couple of days. Let me know if this bug should be split into 2 dedicated bugs or if I can help with any test. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-31-generic 5.19.0-31.32 ProcVersionSignature: Ubuntu 5.19.0-31.32-generic 5.19.17 Uname: Linux 5.19.0-31-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jean-tiare 111982 F pipewire jean-tiare 111986 F wireplumber /dev/snd/pcmC0D0p: jean-tiare 111982 F...m pipewire /dev/snd/seq:jean-tiare 111982 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Feb 17 23:35:44 2023 InstallationDate: Installed on 2023-02-10 (6 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: HP HP ENVY x360 2-in-1 Laptop 15-ew0xxx ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-31-generic root=/dev/mapper/vgubuntu-root ro quiet splash i915.enable_psr=0 i915.enable_fbc=1 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.19.0-31-generic N/A linux-backports-modules-5.19.0-31-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/23/2022 dmi.bios.release: 15.13 dmi.bios.vendor: Insyde dmi.bios.version: F.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8A29 dmi.board.vendor: HP dmi.board.version: 22.41 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 22.41 dmi.modalias: dmi:bvnInsyde:bvrF.13:bd12/23/2022:br15.13:efr22.41:svnHP:pnHPENVYx3602-in-1Laptop15-ew0xxx:pvrType1ProductConfigId:rvnHP:rn8A29:rvr22.41:cvnHP:ct31:cvrChassisVersion:sku6R3F4EA#ABF: dmi.product.family: 103C_5335M8 HP ENVY dmi.product.name: HP ENVY x360 2-in-1 Laptop 15-ew0xxx dmi.product.sku: 6R3F4EA#ABF dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007734/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007769] Re: 7392:c611 Edimax Technology Co., Ltd Edimax Bluetooth Adapter is not currently supported by the installed kernel (5.15)
*** This bug is a duplicate of bug 2007772 *** https://bugs.launchpad.net/bugs/2007772 ** This bug has been marked a duplicate of bug 2007772 7392:c611 Edimax Technology Co., Ltd EdimaxBluetooth Adapter is not currently supported by the installed kernel (5.15) -- 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/2007769 Title: 7392:c611 Edimax Technology Co., Ltd EdimaxBluetooth Adapter is not currently supported by the installed kernel (5.15) Status in linux package in Ubuntu: Confirmed Bug description: Hi, I wanted to connect my bluetooth headset to my Ubuntu 22.04 LTS system. I purchased a Edimax usb bluetooth dongle (BT8500 with rtl8761b chipset) which has a ubuntu driver for a supportted kernal version of 2.6.32 – 5.3. BT USB CHIPS rtl8761bu_fw BTCOEX_20190327-0202 FW_VER= 0x999646b BT UART CHIPS rtl8761b_fw BTCOEX_20190327-0202 FW_VER= 0xd99646b systemctl status bluetooth.service ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled) Active: active (running) since Thu 2023-02-09 21:22:48 NZDT; 28min ago Docs: man:bluetoothd(8) Main PID: 1006 (bluetoothd) Status: "Running" Tasks: 1 (limit: 38335) Memory: 2.0M CPU: 133ms CGroup: /system.slice/bluetooth.service └─1006 /usr/lib/bluetooth/bluetoothd Feb 09 21:22:48 Edward bluetoothd[1006]: Starting SDP server Feb 09 21:22:48 Edward bluetoothd[1006]: Bluetooth management interface 1.21 initialized Feb 09 21:23:13 Edward bluetoothd[1006]: Endpoint registered: sender=:1.84 path=/MediaEndpoint/A2DPSink/sbc Feb 09 21:23:13 Edward bluetoothd[1006]: Endpoint registered: sender=:1.84 path=/MediaEndpoint/A2DPSource/sbc Feb 09 21:23:13 Edward bluetoothd[1006]: Endpoint registered: sender=:1.84 path=/MediaEndpoint/A2DPSink/sbc_xq_453 Feb 09 21:23:13 Edward bluetoothd[1006]: Endpoint registered: sender=:1.84 path=/MediaEndpoint/A2DPSource/sbc_xq_453 Feb 09 21:23:13 Edward bluetoothd[1006]: Endpoint registered: sender=:1.84 path=/MediaEndpoint/A2DPSink/sbc_xq_512 Feb 09 21:23:13 Edward bluetoothd[1006]: Endpoint registered: sender=:1.84 path=/MediaEndpoint/A2DPSource/sbc_xq_512 Feb 09 21:23:13 Edward bluetoothd[1006]: Endpoint registered: sender=:1.84 path=/MediaEndpoint/A2DPSink/sbc_xq_552 Feb 09 21:23:13 Edward bluetoothd[1006]: Endpoint registered: sender=:1.84 path=/MediaEndpoint/A2DPSource/sbc_xq_552 [86619.755586] rtk_btcoex: Close BTCOEX [86619.755592] rtk_btcoex: -x [86619.857321] rtk_btusb: btusb_open start [86619.857326] rtk_btusb: btusb_open hdev->promisc ==0 [86619.857329] rtk_btusb: download_patch start [86619.857331] rtk_btusb: chip type value: 0x74 systemctl status bluetooth.service 13/02 ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled) Active: active (running) since Sun 2023-02-12 22:01:25 NZDT; 22h ago Docs: man:bluetoothd(8) Main PID: 1008 (bluetoothd) Status: "Running" Tasks: 1 (limit: 38335) Memory: 2.2M CPU: 180ms CGroup: /system.slice/bluetooth.service └─1008 /usr/lib/bluetooth/bluetoothd Feb 13 19:39:54 Edward bluetoothd[1008]: Endpoint unregistered: sender=:1.84 path=/MediaEndpoint/A2DPSource/sbc_xq_552 Feb 13 20:11:52 Edward bluetoothd[1008]: Endpoint registered: sender=:1.84 path=/MediaEndpoint/A2DPSink/sbc Feb 13 20:11:52 Edward bluetoothd[1008]: Endpoint registered: sender=:1.84 path=/MediaEndpoint/A2DPSource/sbc Feb 13 20:11:52 Edward bluetoothd[1008]: Endpoint registered: sender=:1.84 path=/MediaEndpoint/A2DPSink/sbc_xq_453 Feb 13 20:11:52 Edward bluetoothd[1008]: Endpoint registered: sender=:1.84 path=/MediaEndpoint/A2DPSource/sbc_xq_453 Feb 13 20:11:52 Edward bluetoothd[1008]: Endpoint registered: sender=:1.84 path=/MediaEndpoint/A2DPSink/sbc_xq_512 Feb 13 20:11:52 Edward bluetoothd[1008]: Endpoint registered: sender=:1.84 path=/MediaEndpoint/A2DPSource/sbc_xq_512 Feb 13 20:11:52 Edward bluetoothd[1008]: Endpoint registered: sender=:1.84 path=/MediaEndpoint/A2DPSink/sbc_xq_552 Feb 13 20:11:52 Edward bluetoothd[1008]: Endpoint registered: sender=:1.84 path=/MediaEndpoint/A2DPSource/sbc_xq_552 Feb 13 20:11:52 Edward bluetoothd[1008]: src/adv_monitor.c:btd_adv_monitor_power_down() Unexpected NULL btd_adv_monitor_manager object upon power down systemctl status snap.bluez.bluez.service × snap.bluez.bluez.service - Service for snap application bluez.bluez Loaded: loaded (/etc/systemd/system/snap.bluez.bluez.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Wed 2023-02-08 19:28:26 NZDT; 20min
[Kernel-packages] [Bug 2007038] Re: 22.04 ib_mthca BUG: kernel NULL pointer, but had worked in 20.04
Please test latest mainline kernel: https://kernel.ubuntu.com/~kernel-ppa/mainline/v6.2/amd64/ Headers are not needed. ** Changed in: linux (Ubuntu) Status: Confirmed => 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/2007038 Title: 22.04 ib_mthca BUG: kernel NULL pointer, but had worked in 20.04 Status in linux package in Ubuntu: Incomplete Bug description: I run some x86_64 machines with Infiniband interfaces (Mellanox MT25204, ib_mthca driver + ib_ipoib for IP-over-IB). This had worked fine for years under Ubuntu 20.04.1 LTS and under RHEL6 before it. But as soon as I updated to 22.04.1 LTS -- with both its default 5.15.0-60-generic kernel and also 6.1.0-1006-oem (the latest packaged one I could find), the IB interface doesn't work. dmesg shows some UBSAN shift-out-of-bounds warnings in mthca modules, e.g. "shift exponent -25557 is negative". That's a bizarre number - maybe a hint of something uninitialized? The crippling symptom shows up within a second after that: a NULL dereference within the ib_mthca driver -- the "BUG: kernel NULL pointer dereference", in mthca_poll_one. The interface never sets its RUNNING flag (as shown by ifconfig). The rest of the system remains usable after the "BUG" message -- the ethernet, disk, etc. drivers and other functions work as expected. Attempting to unload the ib_mthca driver causes a kernel panic. Is there anything I should try? Should I build a kernel from source with debugging? I could try installing the 5.4.0 kernel from 20.04, but would rather use something that will continue to get security patches. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-60-generic 5.15.0-60.66 ProcVersionSignature: Ubuntu 5.15.0-60.66-generic 5.15.78 Uname: Linux 5.15.0-60-generic x86_64 AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Feb 12 14:12 seq crw-rw+ 1 root audio 116, 33 Feb 12 14:12 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass Date: Sun Feb 12 14:17:28 2023 InstallationDate: Installed on 2020-11-22 (812 days ago) InstallationMedia: Ubuntu-Server 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Supermicro X7DBR-8 PciMultimedia: ProcEnviron: TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-60-generic root=UUID=8624cf02-e743-4da6-9209-14ef2c2abd10 ro RelatedPackageVersions: linux-restricted-modules-5.15.0-60-generic N/A linux-backports-modules-5.15.0-60-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.9 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2023-02-10 (2 days ago) dmi.bios.date: 12/03/2007 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: X7DBR-8 dmi.board.vendor: Supermicro dmi.board.version: PCB Version dmi.chassis.type: 1 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd12/03/2007:svnSupermicro:pnX7DBR-8:pvr0123456789:rvnSupermicro:rnX7DBR-8:rvrPCBVersion:cvnSupermicro:ct1:cvr0123456789:sku: dmi.product.name: X7DBR-8 dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007038/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008136] Re: Add HW offloaded CT stats
** Description changed:
* Explain the bug(s)
When CT HW offload is enabled, the CT stats does not show the stats of the
offloaded flow.
- Ex: using
+ Ex: using
cat /proc/net/nf_conntrack, or conntrack -L
shows only the software CT stats, not the offloaded CT stats
* Brief explanation of fixes
Cherry-pick. No adaptation. First commit for SW, second commit of HW
offloaded rules.
ef803b3cf96a netfilter: flowtable: add counter support in HW offload
9312eabab4a6 netfilter: conntrack: add nf_ct_acct_add()
+
+ note: need to change a little due to cherry-pick conflict with
+ 24384e28586c netfilter: flowtable: Set offload timeouts according to proto
values
* How to test
Enable nf_conn_acct, enable HW offload using OVS or tc-flower, and check ct
stats.
ex:
ovs-vsctl get Open_vSwitch . other_config
{hw-offload="true"}
ovs-appctl dpctl/dump-flows type=offloaded
ovs-appctl dpctl/dump-conntrack
* What it could break.
Nothing.
--
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/2008136
Title:
Add HW offloaded CT stats
Status in linux-bluefield package in Ubuntu:
New
Bug description:
* Explain the bug(s)
When CT HW offload is enabled, the CT stats does not show the stats of the
offloaded flow.
Ex: using
cat /proc/net/nf_conntrack, or conntrack -L
shows only the software CT stats, not the offloaded CT stats
* Brief explanation of fixes
Cherry-pick. No adaptation. First commit for SW, second commit of HW
offloaded rules.
ef803b3cf96a netfilter: flowtable: add counter support in HW offload
9312eabab4a6 netfilter: conntrack: add nf_ct_acct_add()
note: need to change a little due to cherry-pick conflict with
24384e28586c netfilter: flowtable: Set offload timeouts according to proto
values
* How to test
Enable nf_conn_acct, enable HW offload using OVS or tc-flower, and check ct
stats.
ex:
ovs-vsctl get Open_vSwitch . other_config
{hw-offload="true"}
ovs-appctl dpctl/dump-flows type=offloaded
ovs-appctl dpctl/dump-conntrack
* What it could break.
Nothing.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2008136/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008136] [NEW] Add HW offloaded CT stats
Public bug reported:
* Explain the bug(s)
When CT HW offload is enabled, the CT stats does not show the stats of the
offloaded flow.
Ex: using
cat /proc/net/nf_conntrack, or conntrack -L
shows only the software CT stats, not the offloaded CT stats
* Brief explanation of fixes
Cherry-pick. No adaptation. First commit for SW, second commit of HW offloaded
rules.
ef803b3cf96a netfilter: flowtable: add counter support in HW offload
9312eabab4a6 netfilter: conntrack: add nf_ct_acct_add()
* How to test
Enable nf_conn_acct, enable HW offload using OVS or tc-flower, and check ct
stats.
ex:
ovs-vsctl get Open_vSwitch . other_config
{hw-offload="true"}
ovs-appctl dpctl/dump-flows type=offloaded
ovs-appctl dpctl/dump-conntrack
* What it could break.
Nothing.
** Affects: linux-bluefield (Ubuntu)
Importance: Undecided
Status: New
--
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/2008136
Title:
Add HW offloaded CT stats
Status in linux-bluefield package in Ubuntu:
New
Bug description:
* Explain the bug(s)
When CT HW offload is enabled, the CT stats does not show the stats of the
offloaded flow.
Ex: using
cat /proc/net/nf_conntrack, or conntrack -L
shows only the software CT stats, not the offloaded CT stats
* Brief explanation of fixes
Cherry-pick. No adaptation. First commit for SW, second commit of HW
offloaded rules.
ef803b3cf96a netfilter: flowtable: add counter support in HW offload
9312eabab4a6 netfilter: conntrack: add nf_ct_acct_add()
* How to test
Enable nf_conn_acct, enable HW offload using OVS or tc-flower, and check ct
stats.
ex:
ovs-vsctl get Open_vSwitch . other_config
{hw-offload="true"}
ovs-appctl dpctl/dump-flows type=offloaded
ovs-appctl dpctl/dump-conntrack
* What it could break.
Nothing.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2008136/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834085] Re: Bluetooth touchpad (Apple Magic Trackpad) disconnects every few minutes
I have the same issue with trackpad 1 and hp victus laptop running ubuntu 22.04.2 -- 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/1834085 Title: Bluetooth touchpad (Apple Magic Trackpad) disconnects every few minutes Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I recently got an Apple's Magic Trackpad. I paired it with Ubuntu 18.04.2 LTS and worked out of the box, no special drivers needed. However, I experience frequent disconnections that last a few seconds (5-15 seconds usually), which are quite annoying, as the cursor stops responding during that interval. The trackpad connects by itself after that period. That usually happens every 20-40 minutes. I use the onboard bluetooth device of my laptop. I also have, at the same time, two more bluetooth devices (keyboard and mouse) and they do not experience that issue, just the trackpad. On ocassion I use bluetooth headphones which work just fine. First of all: Using the command "bluetoothctl" I get the following every time I experience a disconnection: [CHG] Device F4:1B:A1:33:F9:8D Connected: no [CHG] Device F4:1B:A1:33:F9:8D Connected: yes Checking "dmesg" I can see more information: (if I am not mistaken, this shows 4 disconnections) [ 1609.070538] magicmouse 0005:05AC:030E.0007: unknown main item tag 0x0 [ 1609.070797] input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0007/input/input23 [ 1609.071460] magicmouse 0005:05AC:030E.0007: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 [ 1676.917377] NET: Registered protocol family 38 [ 1872.815348] magicmouse 0005:05AC:030E.0008: unknown main item tag 0x0 [ 1872.815559] input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0008/input/input24 [ 1872.816248] magicmouse 0005:05AC:030E.0008: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 [ 3101.682671] magicmouse 0005:05AC:030E.0009: unknown main item tag 0x0 [ 3101.683100] input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0009/input/input25 [ 3101.683673] magicmouse 0005:05AC:030E.0009: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 [ 3110.683360] magicmouse 0005:05AC:030E.000A: unknown main item tag 0x0 [ 3110.683929] input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:1024/0005:05AC:030E.000A/input/input26 [ 3110.684487] magicmouse 0005:05AC:030E.000A: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 And this is what journalctl -b shows at the moment of the disconnection/reconnection: de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) config/udev: removing device Apple Wireless Trackpad de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (**) Option "fd" "64" (1,63 m)˜ de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) event16 - Apple Wireless Trackpad: device removed de juny 13 21:37:49 TM1703 gnome-shell[5071]: g_array_unref: assertion 'array' failed de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) UnloadModule: "libinput" de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) systemd-logind: releasing fd for 13:80 de juny 13 21:37:49 TM1703 upowerd[1271]: unhandled action 'unbind' on /sys/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0008 de juny 13 21:37:50 TM1703 kernel: magicmouse 0005:05AC:030E.0009: unknown main item tag 0x0 de juny 13 21:37:50 TM1703 kernel: input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0009/input/input25 de juny 13 21:37:50 TM1703 kernel: magicmouse 0005:05AC:030E.0009: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) config/udev: Adding input device Apple Wireless Trackpad (/dev/input/mouse1) de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) No input driver specified, ignoring this device. de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) This device may have been added with another device file. de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) config/udev: Adding input device Apple Wireless Trackpad (/dev/input/event16) de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (**) Apple Wireless Trackpad: Applying InputClass "libinput touchpad catchall" de juny 13 21:37:50
[Kernel-packages] [Bug 2003995] Re: Update the 525 and 525-server NVIDIA driver series in Bionic, Focal, Jammy, and Kinetic
No regressions found for either 515-server or 525-server. Both were tested as DKMS and as LRMs using the generic kernel in all releases (lunar could not be installed with lrm). Jammy was also tested with the linux-nvidia kernel and LRMs. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/2003995 Title: Update the 525 and 525-server NVIDIA driver series in Bionic, Focal, Jammy, and Kinetic Status in fabric-manager-515 package in Ubuntu: Fix Released Status in fabric-manager-525 package in Ubuntu: Fix Released Status in libnvidia-nscq-515 package in Ubuntu: Fix Released Status in libnvidia-nscq-525 package in Ubuntu: Fix Released Status in linux-restricted-modules package in Ubuntu: New Status in linux-restricted-modules-hwe package in Ubuntu: New Status in nvidia-graphics-drivers-515-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: Fix Released Status in fabric-manager-515 source package in Bionic: Triaged Status in fabric-manager-525 source package in Bionic: Triaged Status in libnvidia-nscq-515 source package in Bionic: Triaged Status in libnvidia-nscq-525 source package in Bionic: Triaged Status in linux-restricted-modules source package in Bionic: New Status in linux-restricted-modules-hwe source package in Bionic: New Status in nvidia-graphics-drivers-515-server source package in Bionic: Triaged Status in nvidia-graphics-drivers-525 source package in Bionic: Triaged Status in nvidia-graphics-drivers-525-server source package in Bionic: Triaged Status in fabric-manager-515 source package in Focal: Triaged Status in fabric-manager-525 source package in Focal: Triaged Status in libnvidia-nscq-515 source package in Focal: Triaged Status in libnvidia-nscq-525 source package in Focal: Triaged Status in linux-restricted-modules source package in Focal: New Status in linux-restricted-modules-hwe source package in Focal: New Status in nvidia-graphics-drivers-515-server source package in Focal: Triaged Status in nvidia-graphics-drivers-525 source package in Focal: Triaged Status in nvidia-graphics-drivers-525-server source package in Focal: Triaged Status in fabric-manager-515 source package in Jammy: Triaged Status in fabric-manager-525 source package in Jammy: Triaged Status in libnvidia-nscq-515 source package in Jammy: Triaged Status in libnvidia-nscq-525 source package in Jammy: Triaged Status in linux-restricted-modules source package in Jammy: New Status in linux-restricted-modules-hwe source package in Jammy: New Status in nvidia-graphics-drivers-515-server source package in Jammy: Triaged Status in nvidia-graphics-drivers-525 source package in Jammy: Triaged Status in nvidia-graphics-drivers-525-server source package in Jammy: Triaged Status in fabric-manager-515 source package in Kinetic: Triaged Status in fabric-manager-525 source package in Kinetic: Triaged Status in libnvidia-nscq-515 source package in Kinetic: Triaged Status in libnvidia-nscq-525 source package in Kinetic: Triaged Status in linux-restricted-modules source package in Kinetic: New Status in linux-restricted-modules-hwe source package in Kinetic: New Status in nvidia-graphics-drivers-515-server source package in Kinetic: Triaged Status in nvidia-graphics-drivers-525 source package in Kinetic: Triaged Status in nvidia-graphics-drivers-525-server source package in Kinetic: Triaged Bug description: [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] 525 * New upstream release (LP: #2003995): - Improved the reliability of suspend and resume on UEFI systems when using certain display panels. - Fixed a bug that could cause VK_ERROR_DEVICE_LOST when using VK_MEMORY_ALLOCATE_DEVICE_ADDRESS_CAPTURE_REPLAY_BIT to allocate memory. - Disabled Fixed Rate Link (FRL) when using passive DisplayPort to HDMI dongles, which are incompatible
[Kernel-packages] [Bug 2008128] Re: Double fault in cpu_entry_area while resuming from suspend
Kernel 6.1.0-rc7 patched with a different patch: https://lore.kernel.org/lkml/20221129215008.7247-1-mat.jonc...@o2.pl/T/ ** Attachment added: "pstore_on_Linux_6.1.0-rc7unif10-1-g778bb35327f7.txt" https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.15/+bug/2008128/+attachment/5649216/+files/pstore_on_Linux_6.1.0-rc7unif10-1-g778bb35327f7.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2008128 Title: Double fault in cpu_entry_area while resuming from suspend Status in linux-signed-hwe-5.15 package in Ubuntu: New Bug description: Hello, On kernel 5.15.0-60-generic from Ubuntu, I had an occurrence of a double fault while resuming from suspend. I'm attaching logs from pstore. I run mostly upstream kernels. The same (or a similar) problem has happened to me a few times on rc releases of Linux 6.1, the first time in November 2022 on 6.1.0-rc5. It stopped happening since I have moved to rc releases of Linux 6.2. So I think that a similar bug was introduced in Linux 6.1 and fixed in Linux 6.2 and probably carried over with stable patches to Ubuntu's 5.15.0-60-generic. I was not able to reproduce this bug reliably on Linux 6.1 back then, and I did not report the problem to LKML (I'm sorry). In all occurrences (on Linux 5.15 and 6.1), the fault has happened at address 0xfe00b000, which according to https://www.kernel.org/doc/Documentation/x86/x86_64/mm.txt lies in the cpu_entry_area mapping, I think that it is in a guard page there. Every time, this has happened while resuming from suspend. Every time, there were some RCU functions present in the pstore stack traces. I have some patches in mainline Linux and I'm happy to assist in any troubleshooting. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.15.0-60-generic 5.15.0-60.66~20.04.1 ProcVersionSignature: Ubuntu 5.15.0-60.66~20.04.1-generic 5.15.78 Uname: Linux 5.15.0-60-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME-Classic:GNOME Date: Wed Feb 22 21:06:51 2023 InstallationDate: Installed on 2020-09-12 (892 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.15 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.15/+bug/2008128/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008128] Re: Double fault in cpu_entry_area while resuming from suspend
Pstore from Linux 6.1.0 with this Bluetooth patch: https://lore.kernel.org/linux- bluetooth/20221102175927.401091-2-brian@intel.com/ , which is probably unrelated. "unif9" is my kernel "local version" (CONFIG_LOCALVERSION) suffix that denotes the Kconfig I was using. ** Attachment added: "pstore_on_Linux_6.1.0-rc5unif9-1-g4b27c67b41bf.txt" https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.15/+bug/2008128/+attachment/5649215/+files/pstore_on_Linux_6.1.0-rc5unif9-1-g4b27c67b41bf.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2008128 Title: Double fault in cpu_entry_area while resuming from suspend Status in linux-signed-hwe-5.15 package in Ubuntu: New Bug description: Hello, On kernel 5.15.0-60-generic from Ubuntu, I had an occurrence of a double fault while resuming from suspend. I'm attaching logs from pstore. I run mostly upstream kernels. The same (or a similar) problem has happened to me a few times on rc releases of Linux 6.1, the first time in November 2022 on 6.1.0-rc5. It stopped happening since I have moved to rc releases of Linux 6.2. So I think that a similar bug was introduced in Linux 6.1 and fixed in Linux 6.2 and probably carried over with stable patches to Ubuntu's 5.15.0-60-generic. I was not able to reproduce this bug reliably on Linux 6.1 back then, and I did not report the problem to LKML (I'm sorry). In all occurrences (on Linux 5.15 and 6.1), the fault has happened at address 0xfe00b000, which according to https://www.kernel.org/doc/Documentation/x86/x86_64/mm.txt lies in the cpu_entry_area mapping, I think that it is in a guard page there. Every time, this has happened while resuming from suspend. Every time, there were some RCU functions present in the pstore stack traces. I have some patches in mainline Linux and I'm happy to assist in any troubleshooting. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.15.0-60-generic 5.15.0-60.66~20.04.1 ProcVersionSignature: Ubuntu 5.15.0-60.66~20.04.1-generic 5.15.78 Uname: Linux 5.15.0-60-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME-Classic:GNOME Date: Wed Feb 22 21:06:51 2023 InstallationDate: Installed on 2020-09-12 (892 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.15 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.15/+bug/2008128/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008128] Re: Double fault in cpu_entry_area while resuming from suspend
** Attachment added: "lspci -vvnn" https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.15/+bug/2008128/+attachment/5649204/+files/lspci_vvnn.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2008128 Title: Double fault in cpu_entry_area while resuming from suspend Status in linux-signed-hwe-5.15 package in Ubuntu: New Bug description: Hello, On kernel 5.15.0-60-generic from Ubuntu, I had an occurrence of a double fault while resuming from suspend. I'm attaching logs from pstore. I run mostly upstream kernels. The same (or a similar) problem has happened to me a few times on rc releases of Linux 6.1, the first time in November 2022 on 6.1.0-rc5. It stopped happening since I have moved to rc releases of Linux 6.2. So I think that a similar bug was introduced in Linux 6.1 and fixed in Linux 6.2 and probably carried over with stable patches to Ubuntu's 5.15.0-60-generic. I was not able to reproduce this bug reliably on Linux 6.1 back then, and I did not report the problem to LKML (I'm sorry). In all occurrences (on Linux 5.15 and 6.1), the fault has happened at address 0xfe00b000, which according to https://www.kernel.org/doc/Documentation/x86/x86_64/mm.txt lies in the cpu_entry_area mapping, I think that it is in a guard page there. Every time, this has happened while resuming from suspend. Every time, there were some RCU functions present in the pstore stack traces. I have some patches in mainline Linux and I'm happy to assist in any troubleshooting. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.15.0-60-generic 5.15.0-60.66~20.04.1 ProcVersionSignature: Ubuntu 5.15.0-60.66~20.04.1-generic 5.15.78 Uname: Linux 5.15.0-60-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME-Classic:GNOME Date: Wed Feb 22 21:06:51 2023 InstallationDate: Installed on 2020-09-12 (892 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.15 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.15/+bug/2008128/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008128] Re: Double fault in cpu_entry_area while resuming from suspend
Both pstore logs are from the same crash. They were obtained by concatenating the parts from systemd-pstore: cat $(ls /var/lib/systemd/pstore/167684323/dmesg-efi*001 -1 | tac) > pstore1_on_Linux_5.15.0-60.txt cat $(ls /var/lib/systemd/pstore/167684323/dmesg-efi*002 -1 | tac) > pstore2_on_Linux_5.15.0-60.txt ** Attachment added: "Pstore log no 2 from Ubuntu 5.15.0-60" https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.15/+bug/2008128/+attachment/5649202/+files/linux_5.15.0-60_pstore2.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2008128 Title: Double fault in cpu_entry_area while resuming from suspend Status in linux-signed-hwe-5.15 package in Ubuntu: New Bug description: Hello, On kernel 5.15.0-60-generic from Ubuntu, I had an occurrence of a double fault while resuming from suspend. I'm attaching logs from pstore. I run mostly upstream kernels. The same (or a similar) problem has happened to me a few times on rc releases of Linux 6.1, the first time in November 2022 on 6.1.0-rc5. It stopped happening since I have moved to rc releases of Linux 6.2. So I think that a similar bug was introduced in Linux 6.1 and fixed in Linux 6.2 and probably carried over with stable patches to Ubuntu's 5.15.0-60-generic. I was not able to reproduce this bug reliably on Linux 6.1 back then, and I did not report the problem to LKML (I'm sorry). In all occurrences (on Linux 5.15 and 6.1), the fault has happened at address 0xfe00b000, which according to https://www.kernel.org/doc/Documentation/x86/x86_64/mm.txt lies in the cpu_entry_area mapping, I think that it is in a guard page there. Every time, this has happened while resuming from suspend. Every time, there were some RCU functions present in the pstore stack traces. I have some patches in mainline Linux and I'm happy to assist in any troubleshooting. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.15.0-60-generic 5.15.0-60.66~20.04.1 ProcVersionSignature: Ubuntu 5.15.0-60.66~20.04.1-generic 5.15.78 Uname: Linux 5.15.0-60-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME-Classic:GNOME Date: Wed Feb 22 21:06:51 2023 InstallationDate: Installed on 2020-09-12 (892 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.15 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.15/+bug/2008128/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008128] Re: Double fault in cpu_entry_area while resuming from suspend
dmesg from before crash, obtained from "journalctl -k" ** Attachment added: "dmesg from Ubuntu 5.15.0-60" https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.15/+bug/2008128/+attachment/5649203/+files/linux_5.15.0-60_journalctl.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2008128 Title: Double fault in cpu_entry_area while resuming from suspend Status in linux-signed-hwe-5.15 package in Ubuntu: New Bug description: Hello, On kernel 5.15.0-60-generic from Ubuntu, I had an occurrence of a double fault while resuming from suspend. I'm attaching logs from pstore. I run mostly upstream kernels. The same (or a similar) problem has happened to me a few times on rc releases of Linux 6.1, the first time in November 2022 on 6.1.0-rc5. It stopped happening since I have moved to rc releases of Linux 6.2. So I think that a similar bug was introduced in Linux 6.1 and fixed in Linux 6.2 and probably carried over with stable patches to Ubuntu's 5.15.0-60-generic. I was not able to reproduce this bug reliably on Linux 6.1 back then, and I did not report the problem to LKML (I'm sorry). In all occurrences (on Linux 5.15 and 6.1), the fault has happened at address 0xfe00b000, which according to https://www.kernel.org/doc/Documentation/x86/x86_64/mm.txt lies in the cpu_entry_area mapping, I think that it is in a guard page there. Every time, this has happened while resuming from suspend. Every time, there were some RCU functions present in the pstore stack traces. I have some patches in mainline Linux and I'm happy to assist in any troubleshooting. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.15.0-60-generic 5.15.0-60.66~20.04.1 ProcVersionSignature: Ubuntu 5.15.0-60.66~20.04.1-generic 5.15.78 Uname: Linux 5.15.0-60-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME-Classic:GNOME Date: Wed Feb 22 21:06:51 2023 InstallationDate: Installed on 2020-09-12 (892 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.15 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.15/+bug/2008128/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008128] Re: Double fault in cpu_entry_area while resuming from suspend
-- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2008128 Title: Double fault in cpu_entry_area while resuming from suspend Status in linux-signed-hwe-5.15 package in Ubuntu: New Bug description: Hello, On kernel 5.15.0-60-generic from Ubuntu, I had an occurrence of a double fault while resuming from suspend. I'm attaching logs from pstore. I run mostly upstream kernels. The same (or a similar) problem has happened to me a few times on rc releases of Linux 6.1, the first time in November 2022 on 6.1.0-rc5. It stopped happening since I have moved to rc releases of Linux 6.2. So I think that a similar bug was introduced in Linux 6.1 and fixed in Linux 6.2 and probably carried over with stable patches to Ubuntu's 5.15.0-60-generic. I was not able to reproduce this bug reliably on Linux 6.1 back then, and I did not report the problem to LKML (I'm sorry). In all occurrences (on Linux 5.15 and 6.1), the fault has happened at address 0xfe00b000, which according to https://www.kernel.org/doc/Documentation/x86/x86_64/mm.txt lies in the cpu_entry_area mapping, I think that it is in a guard page there. Every time, this has happened while resuming from suspend. Every time, there were some RCU functions present in the pstore stack traces. I have some patches in mainline Linux and I'm happy to assist in any troubleshooting. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.15.0-60-generic 5.15.0-60.66~20.04.1 ProcVersionSignature: Ubuntu 5.15.0-60.66~20.04.1-generic 5.15.78 Uname: Linux 5.15.0-60-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME-Classic:GNOME Date: Wed Feb 22 21:06:51 2023 InstallationDate: Installed on 2020-09-12 (892 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.15 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.15/+bug/2008128/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008128] Re: Double fault in cpu_entry_area while resuming from suspend
** Attachment added: "Pstore log no 1 from Ubuntu 5.15.0-60" https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.15/+bug/2008128/+attachment/5649201/+files/linux_5.15.0-60_pstore1.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2008128 Title: Double fault in cpu_entry_area while resuming from suspend Status in linux-signed-hwe-5.15 package in Ubuntu: New Bug description: Hello, On kernel 5.15.0-60-generic from Ubuntu, I had an occurrence of a double fault while resuming from suspend. I'm attaching logs from pstore. I run mostly upstream kernels. The same (or a similar) problem has happened to me a few times on rc releases of Linux 6.1, the first time in November 2022 on 6.1.0-rc5. It stopped happening since I have moved to rc releases of Linux 6.2. So I think that a similar bug was introduced in Linux 6.1 and fixed in Linux 6.2 and probably carried over with stable patches to Ubuntu's 5.15.0-60-generic. I was not able to reproduce this bug reliably on Linux 6.1 back then, and I did not report the problem to LKML (I'm sorry). In all occurrences (on Linux 5.15 and 6.1), the fault has happened at address 0xfe00b000, which according to https://www.kernel.org/doc/Documentation/x86/x86_64/mm.txt lies in the cpu_entry_area mapping, I think that it is in a guard page there. Every time, this has happened while resuming from suspend. Every time, there were some RCU functions present in the pstore stack traces. I have some patches in mainline Linux and I'm happy to assist in any troubleshooting. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.15.0-60-generic 5.15.0-60.66~20.04.1 ProcVersionSignature: Ubuntu 5.15.0-60.66~20.04.1-generic 5.15.78 Uname: Linux 5.15.0-60-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME-Classic:GNOME Date: Wed Feb 22 21:06:51 2023 InstallationDate: Installed on 2020-09-12 (892 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.15 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.15/+bug/2008128/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008128] [NEW] Double fault in cpu_entry_area while resuming from suspend
Public bug reported: Hello, On kernel 5.15.0-60-generic from Ubuntu, I had an occurrence of a double fault while resuming from suspend. I'm attaching logs from pstore. I run mostly upstream kernels. The same (or a similar) problem has happened to me a few times on rc releases of Linux 6.1, the first time in November 2022 on 6.1.0-rc5. It stopped happening since I have moved to rc releases of Linux 6.2. So I think that a similar bug was introduced in Linux 6.1 and fixed in Linux 6.2 and probably carried over with stable patches to Ubuntu's 5.15.0-60-generic. I was not able to reproduce this bug reliably on Linux 6.1 back then, and I did not report the problem to LKML (I'm sorry). In all occurrences (on Linux 5.15 and 6.1), the fault has happened at address 0xfe00b000, which according to https://www.kernel.org/doc/Documentation/x86/x86_64/mm.txt lies in the cpu_entry_area mapping, I think that it is in a guard page there. Every time, this has happened while resuming from suspend. Every time, there were some RCU functions present in the pstore stack traces. I have some patches in mainline Linux and I'm happy to assist in any troubleshooting. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.15.0-60-generic 5.15.0-60.66~20.04.1 ProcVersionSignature: Ubuntu 5.15.0-60.66~20.04.1-generic 5.15.78 Uname: Linux 5.15.0-60-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME-Classic:GNOME Date: Wed Feb 22 21:06:51 2023 InstallationDate: Installed on 2020-09-12 (892 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.15 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.15 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "pstore logs" https://bugs.launchpad.net/bugs/2008128/+attachment/5649198/+files/linux_5.15.0-60_pstore1.txt ** Description changed: Hello, On kernel 5.15.0-60-generic from Ubuntu, I had an occurrence of a double fault while resuming from suspend. I'm attaching logs from pstore. I run mostly upstream kernels. The same (or a similar) problem has happened to me a few times on rc releases of Linux 6.1, the first time in November 2022 on 6.1.0-rc5. It stopped happening since I have moved to rc releases of Linux 6.2. So I think that a similar bug was introduced in Linux 6.1 and fixed in Linux 6.2 and probably carried over with stable patches to Ubuntu's 5.15.0-60-generic. I was not able to reproduce this bug reliably on Linux 6.1 back then, and I did not report the problem to LKML (I'm sorry). In all occurrences (on Linux 5.15 and 6.1), the fault has happened at address 0xfe00b000, which according to https://www.kernel.org/doc/Documentation/x86/x86_64/mm.txt lies in the cpu_entry_area mapping, I think that it is in a guard page there. - I have some patches in mainline Linux + I have some patches in mainline Linux and I'm happy to assist in any + troubleshooting. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.15.0-60-generic 5.15.0-60.66~20.04.1 ProcVersionSignature: Ubuntu 5.15.0-60.66~20.04.1-generic 5.15.78 Uname: Linux 5.15.0-60-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME-Classic:GNOME Date: Wed Feb 22 21:06:51 2023 InstallationDate: Installed on 2020-09-12 (892 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=pl_PL.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=pl_PL.UTF-8 + SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.15 UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: Hello, On kernel 5.15.0-60-generic from Ubuntu, I had an occurrence of a double fault while resuming from suspend. I'm attaching logs from pstore. I run mostly upstream kernels. The same (or a similar) problem has happened to me a few times on rc releases of Linux 6.1, the first time in November 2022 on 6.1.0-rc5. It stopped happening since I have moved to rc releases of Linux 6.2. So I think that a similar bug was introduced in Linux 6.1 and fixed in Linux 6.2 and probably carried over with stable patches to Ubuntu's 5.15.0-60-generic. I was not able to reproduce this bug reliably on Linux 6.1 back then, and I did not report the problem to LKML (I'm sorry). In all occurrences (on Linux 5.15 and 6.1), the fault has happened at address 0xfe00b000, which according to
[Kernel-packages] [Bug 1987829] Re: LG Gram 12gen high CPU use when USB-C/TB is in use
Confirm this bug in Clear Linux as well. -- 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/1987829 Title: LG Gram 12gen high CPU use when USB-C/TB is in use Status in linux package in Ubuntu: Confirmed Status in linux package in Fedora: New Bug description: LG Gram laptop 17Z90Q with a Core i7-1260P CPU. Whenever an external monitor is connected to USB-C/Thunderbolt 4, average load goes above 3.0 and the machine is getting very hot. Output from top -H shows a lot of kworker CPU usage: top - 11:45:06 up 33 min, 2 users, load average: 3,30, 3,08, 2,79 Threads: 1442 total, 2 running, 1440 sleeping, 0 stopped, 0 zombie %Cpu(s): 0,1 us, 3,7 sy, 0,0 ni, 96,1 id, 0,0 wa, 0,0 hi, 0,1 si, 0,0 st MiB Mem : 15684,6 total, 8510,2 free, 2580,8 used, 4593,6 buff/cache MiB Swap: 3815,0 total, 3815,0 free, 0,0 used. 11326,9 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ WCHAN COMMAND 7766 root 20 0 0 0 0 R 19,8 0,0 0:56.05 worker_th+ kworker/0:2-events 196 root 20 0 0 0 0 D 15,8 0,0 1:18.12 ec_guard kworker/u32:2+USBC000:00-con0 10237 root 20 0 0 0 0 I 12,9 0,0 0:26.44 worker_th+ kworker/0:0-events 1027 root 20 0 0 0 0 I 6,6 0,0 0:43.30 worker_th+ kworker/1:3-events 10971 root 20 0 0 0 0 I 4,0 0,0 0:00.20 worker_th+ kworker/15:0-events 175 root 20 0 0 0 0 I 2,3 0,0 0:03.24 worker_th+ kworker/11:1-events 2410 root 20 0 0 0 0 I 1,7 0,0 0:05.49 worker_th+ kworker/9:3-events Perf shows a lot of time spent inside handle_irq_event/acpi_ev_gpe_detect/acpi_hw_gpe_read. Additionally, kernel log is getting spammed with these lines every 4 seconds (but also without any USB-C device attached): [ 223.514304] ACPI Error: No handler for Region [XIN1] (f2ad4f1f) [UserDefinedRegion] (20210730/evregion-130) [ 223.514323] ACPI Error: Region UserDefinedRegion (ID=143) has no handler (20210730/exfldio-261) [ 223.514337] Initialized Local Variables for Method [_TMP]: [ 223.514339] Local0: 21495082Integer 0034 [ 223.514349] No Arguments are initialized for method [_TMP] [ 223.514354] ACPI Error: Aborting method \_SB.PC00.LPCB.LGEC.SEN2._TMP due to previous error (AE_NOT_EXIST) (20210730/psparse-529) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-46-generic 5.15.0-46.49 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: me 1678 F pulseaudio /dev/snd/controlC1: me 1678 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass Date: Fri Aug 26 11:57:05 2022 InstallationDate: Installed on 2022-08-25 (1 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LG Electronics 17Z90Q-G.AA78N ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=e2f96916-a67c-432e-b687-730071271216 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/06/2022 dmi.bios.release: 0.1 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: A1ZG0380 X64 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 17Z90Q dmi.board.vendor: LG Electronics dmi.board.version: FAB1 dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LG Electronics dmi.chassis.version: 0.1 dmi.ec.firmware.release: 33.0 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrA1ZG0380X64:bd07/06/2022:br0.1:efr33.0:svnLGElectronics:pn17Z90Q-G.AA78N:pvr0.1:rvnLGElectronics:rn17Z90Q:rvrFAB1:cvnLGElectronics:ct10:cvr0.1:skuEVO: dmi.product.family: LG gram PC dmi.product.name: 17Z90Q-G.AA78N dmi.product.sku: EVO dmi.product.version: 0.1 dmi.sys.vendor: LG Electronics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987829/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More
[Kernel-packages] [Bug 2008118] Status changed to Confirmed
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2008118
Title:
Freeze on resume from suspend (amdgpu errors)
Status in linux package in Ubuntu:
Confirmed
Bug description:
I'm running Kubuntu 22.04 LTS, fresh install. Most of the time, when
resuming from suspend-to-RAM, the system will freeze. Sometimes the
screen is all black, while other times it is showing the lock screen;
in both cases it's completely unresponsive.
The only way out is to force a reboot with the SYSRQ "REISUB" key
combo. I tried switching VT with Ctrl+Alt+F{1-7}, but it does not
respond.
From a quick look at the logs I can see that it shows a lot of red-
colored error lines from the kernel about amdgpu.
I didn't have this problem with other flavors (used Xubuntu and
Ubuntu, 22.04 and 22.10), so I guess it's a Kubuntu bug.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-60-generic 5.15.0-60.66
ProcVersionSignature: Ubuntu 5.15.0-60.66-generic 5.15.78
Uname: Linux 5.15.0-60-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: dsilva 1217 F pulseaudio
/dev/snd/controlC1: dsilva 1217 F pulseaudio
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: KDE
Date: Wed Feb 22 14:55:20 2023
InstallationDate: Installed on 2023-02-19 (2 days ago)
InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64
(20220809.1)
MachineType: Gigabyte Technology Co., Ltd. B460MDS3H
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-60-generic
root=UUID=5a8a2ff2-be5a-4aa5-ae8b-874e45080a04 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-5.15.0-60-generic N/A
linux-backports-modules-5.15.0-60-generic N/A
linux-firmware 20220329.git681281e4-0ubuntu3.10
RfKill:
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/23/2021
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F5
dmi.board.asset.tag: Default string
dmi.board.name: B460M DS3H
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: Default string
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd11/23/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnB460MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB460MDS3H:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
dmi.product.family: B460 MB
dmi.product.name: B460MDS3H
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/ubuntu/+source/linux/+bug/2008118/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008118] Re: Freeze on resume from suspend (amdgpu errors)
This contains the logs from the resume attempt that failed.
** Attachment added: "logs from the relevant boot (sudo journalctl -b -1)"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008118/+attachment/5649176/+files/journalctl.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/2008118
Title:
Freeze on resume from suspend (amdgpu errors)
Status in linux package in Ubuntu:
New
Bug description:
I'm running Kubuntu 22.04 LTS, fresh install. Most of the time, when
resuming from suspend-to-RAM, the system will freeze. Sometimes the
screen is all black, while other times it is showing the lock screen;
in both cases it's completely unresponsive.
The only way out is to force a reboot with the SYSRQ "REISUB" key
combo. I tried switching VT with Ctrl+Alt+F{1-7}, but it does not
respond.
From a quick look at the logs I can see that it shows a lot of red-
colored error lines from the kernel about amdgpu.
I didn't have this problem with other flavors (used Xubuntu and
Ubuntu, 22.04 and 22.10), so I guess it's a Kubuntu bug.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-60-generic 5.15.0-60.66
ProcVersionSignature: Ubuntu 5.15.0-60.66-generic 5.15.78
Uname: Linux 5.15.0-60-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: dsilva 1217 F pulseaudio
/dev/snd/controlC1: dsilva 1217 F pulseaudio
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: KDE
Date: Wed Feb 22 14:55:20 2023
InstallationDate: Installed on 2023-02-19 (2 days ago)
InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64
(20220809.1)
MachineType: Gigabyte Technology Co., Ltd. B460MDS3H
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-60-generic
root=UUID=5a8a2ff2-be5a-4aa5-ae8b-874e45080a04 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-5.15.0-60-generic N/A
linux-backports-modules-5.15.0-60-generic N/A
linux-firmware 20220329.git681281e4-0ubuntu3.10
RfKill:
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/23/2021
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F5
dmi.board.asset.tag: Default string
dmi.board.name: B460M DS3H
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: Default string
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd11/23/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnB460MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB460MDS3H:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
dmi.product.family: B460 MB
dmi.product.name: B460MDS3H
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/ubuntu/+source/linux/+bug/2008118/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008118] [NEW] Freeze on resume from suspend (amdgpu errors)
Public bug reported:
I'm running Kubuntu 22.04 LTS, fresh install. Most of the time, when
resuming from suspend-to-RAM, the system will freeze. Sometimes the
screen is all black, while other times it is showing the lock screen; in
both cases it's completely unresponsive.
The only way out is to force a reboot with the SYSRQ "REISUB" key combo.
I tried switching VT with Ctrl+Alt+F{1-7}, but it does not respond.
From a quick look at the logs I can see that it shows a lot of red-
colored error lines from the kernel about amdgpu.
I didn't have this problem with other flavors (used Xubuntu and Ubuntu,
22.04 and 22.10), so I guess it's a Kubuntu bug.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-60-generic 5.15.0-60.66
ProcVersionSignature: Ubuntu 5.15.0-60.66-generic 5.15.78
Uname: Linux 5.15.0-60-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: dsilva 1217 F pulseaudio
/dev/snd/controlC1: dsilva 1217 F pulseaudio
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: KDE
Date: Wed Feb 22 14:55:20 2023
InstallationDate: Installed on 2023-02-19 (2 days ago)
InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64
(20220809.1)
MachineType: Gigabyte Technology Co., Ltd. B460MDS3H
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-60-generic
root=UUID=5a8a2ff2-be5a-4aa5-ae8b-874e45080a04 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-5.15.0-60-generic N/A
linux-backports-modules-5.15.0-60-generic N/A
linux-firmware 20220329.git681281e4-0ubuntu3.10
RfKill:
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/23/2021
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F5
dmi.board.asset.tag: Default string
dmi.board.name: B460M DS3H
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: Default string
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd11/23/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnB460MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB460MDS3H:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
dmi.product.family: B460 MB
dmi.product.name: B460MDS3H
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug jammy
** Description changed:
I'm running Kubuntu 22.04 LTS, fresh install. Most of the time, when
- resuming from suspend, the system will freeze. Sometimes the screen is
- all black, while other times it is showing the lock screen; in both
- cases it's completely unresponsive.
+ resuming from suspend-to-RAM, the system will freeze. Sometimes the
+ screen is all black, while other times it is showing the lock screen; in
+ both cases it's completely unresponsive.
The only way out is to force a reboot with the SYSRQ "REISUB" key combo.
From a quick look at the logs I can see that it shows a lot of red-
colored error lines from the kernel about amdgpu.
I didn't have this problem with other flavors (used Xubuntu and Ubuntu,
22.04 and 22.10), so I guess it's a Kubuntu bug.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-60-generic 5.15.0-60.66
ProcVersionSignature: Ubuntu 5.15.0-60.66-generic 5.15.78
Uname: Linux 5.15.0-60-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
AudioDevicesInUse:
- USERPID ACCESS COMMAND
- /dev/snd/controlC0: dsilva 1217 F pulseaudio
- /dev/snd/controlC1: dsilva 1217 F pulseaudio
+ USERPID ACCESS COMMAND
+ /dev/snd/controlC0: dsilva 1217 F pulseaudio
+ /dev/snd/controlC1: dsilva 1217 F pulseaudio
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: KDE
Date: Wed Feb 22 14:55:20 2023
InstallationDate: Installed on 2023-02-19 (2 days ago)
InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64
(20220809.1)
MachineType: Gigabyte Technology Co., Ltd. B460MDS3H
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-60-generic
root=UUID=5a8a2ff2-be5a-4aa5-ae8b-874e45080a04 ro quiet splash vt.handoff=7
RelatedPackageVersions:
- linux-restricted-modules-5.15.0-60-generic N/A
- linux-backports-modules-5.15.0-60-generic N/A
- linux-firmware 20220329.git681281e4-0ubuntu3.10
+ linux-restricted-modules-5.15.0-60-generic N/A
+ linux-backports-modules-5.15.0-60-generic N/A
+ linux-firmware 20220329.git681281e4-0ubuntu3.10
RfKill:
- 0:
[Kernel-packages] [Bug 1943879] Re: NETDEV WATCHDOG: eno49 (ixgbe): transmit queue 34 timed out
Any update here? -- 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/1943879 Title: NETDEV WATCHDOG: eno49 (ixgbe): transmit queue 34 timed out Status in linux package in Ubuntu: Expired Bug description: I am running ubuntu Focal version with following kernel and NIC and noticed where strange error in kernel logs and my nic went down, does any one know about this? # uname -a Linux ostack-phx-comp-gen-1-27.v1v0x.net 5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020 x86_64 x86_64x # lspci | grep -i eth 06:00.0 Ethernet controller: Intel Corporation 82599 10 Gigabit Dual Port Backplane Connection (rev 01) 06:00.1 Ethernet controller: Intel Corporation 82599 10 Gigabit Dual Port Backplane Connection (rev 01) [Thu Sep 16 01:43:51 2021] [ cut here ] [Thu Sep 16 01:43:51 2021] NETDEV WATCHDOG: eno49 (ixgbe): transmit queue 34 timed out [Thu Sep 16 01:43:51 2021] WARNING: CPU: 11 PID: 0 at net/sched/sch_generic.c:447 dev_watchdog+0x258/0x260 [Thu Sep 16 01:43:51 2021] Modules linked in: nf_conntrack_netlink ebt_arp nft_compat nf_tables_set nft_meta_bridgel [Thu Sep 16 01:43:51 2021] ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_mi [Thu Sep 16 01:43:51 2021] CPU: 11 PID: 0 Comm: swapper/11 Not tainted 5.4.0-42-generic #46-Ubuntu [Thu Sep 16 01:43:51 2021] Hardware name: HP ProLiant BL460c Gen9, BIOS I36 02/17/2017 [Thu Sep 16 01:43:51 2021] RIP: 0010:dev_watchdog+0x258/0x260 [Thu Sep 16 01:43:51 2021] Code: 85 c0 75 e5 eb 9f 4c 89 ff c6 05 1f f5 e7 00 01 e8 8d bb fa ff 44 89 e9 4c 89 fe 47 [Thu Sep 16 01:43:51 2021] RSP: 0018:b92d466b4e30 EFLAGS: 00010286 [Thu Sep 16 01:43:51 2021] RAX: RBX: 9373ef57cec0 RCX: 083f [Thu Sep 16 01:43:51 2021] RDX: RSI: 00f6 RDI: 083f [Thu Sep 16 01:43:51 2021] RBP: b92d466b4e60 R08: 937bdf8d78c8 R09: 0004 [Thu Sep 16 01:43:51 2021] R10: R11: 0001 R12: 0040 [Thu Sep 16 01:43:51 2021] R13: 0022 R14: 9373ef580480 R15: 9373ef58 [Thu Sep 16 01:43:51 2021] FS: () GS:937bdf8c() knlGS: [Thu Sep 16 01:43:51 2021] CS: 0010 DS: ES: CR0: 80050033 [Thu Sep 16 01:43:51 2021] CR2: 7f3697ec19dc CR3: 00103ce0a001 CR4: 001626e0 [Thu Sep 16 01:43:51 2021] Call Trace: [Thu Sep 16 01:43:51 2021] [Thu Sep 16 01:43:51 2021] ? pfifo_fast_enqueue+0x150/0x150 [Thu Sep 16 01:43:51 2021] call_timer_fn+0x32/0x130 [Thu Sep 16 01:43:51 2021] __run_timers.part.0+0x180/0x280 [Thu Sep 16 01:43:51 2021] ? tick_sched_handle+0x33/0x60 [Thu Sep 16 01:43:51 2021] ? tick_sched_timer+0x3d/0x80 [Thu Sep 16 01:43:51 2021] ? ktime_get+0x3e/0xa0 [Thu Sep 16 01:43:51 2021] run_timer_softirq+0x2a/0x50 [Thu Sep 16 01:43:51 2021] __do_softirq+0xe1/0x2d6 [Thu Sep 16 01:43:51 2021] ? hrtimer_interrupt+0x13b/0x220 [Thu Sep 16 01:43:51 2021] irq_exit+0xae/0xb0 [Thu Sep 16 01:43:51 2021] smp_apic_timer_interrupt+0x7b/0x140 [Thu Sep 16 01:43:51 2021] apic_timer_interrupt+0xf/0x20 [Thu Sep 16 01:43:51 2021] [Thu Sep 16 01:43:51 2021] RIP: 0010:cpuidle_enter_state+0xc5/0x450 [Thu Sep 16 01:43:51 2021] Code: ff e8 bf 08 81 ff 80 7d c7 00 74 17 9c 58 0f 1f 44 00 00 f6 c4 02 0f 85 65 03 00 0d [Thu Sep 16 01:43:51 2021] RSP: 0018:b92d4634fe38 EFLAGS: 0246 ORIG_RAX: ff13 [Thu Sep 16 01:43:51 2021] RAX: 937bdf8ead00 RBX: 8d159c00 RCX: 001f [Thu Sep 16 01:43:51 2021] RDX: RSI: 3342629e RDI: [Thu Sep 16 01:43:51 2021] RBP: b92d4634fe78 R08: 0011dc129ea2a1f1 R09: 0011dc17357faf00 [Thu Sep 16 01:43:51 2021] R10: 937bdf8e9a00 R11: 937bdf8e99e0 R12: d9253fac20a8 [Thu Sep 16 01:43:51 2021] R13: 0004 R14: 0004 R15: d9253fac20a8 [Thu Sep 16 01:43:51 2021] ? cpuidle_enter_state+0xa1/0x450 [Thu Sep 16 01:43:51 2021] cpuidle_enter+0x2e/0x40 [Thu Sep 16 01:43:51 2021] call_cpuidle+0x23/0x40 [Thu Sep 16 01:43:51 2021] do_idle+0x1dd/0x270 [Thu Sep 16 01:43:51 2021] cpu_startup_entry+0x20/0x30 [Thu Sep 16 01:43:51 2021] start_secondary+0x167/0x1c0 [Thu Sep 16 01:43:51 2021] secondary_startup_64+0xa4/0xb0 [Thu Sep 16 01:43:51 2021] ---[ end trace cb80e9f61341ace0 ]--- [Thu Sep 16 01:43:51 2021] ixgbe :06:00.0 eno49: initiating reset due to tx timeout [Thu Sep 16 01:43:51 2021] ixgbe :06:00.0 eno49: Reset adapter [Thu Sep 16 01:43:51 2021] ixgbe :06:00.0 eno49: TXDCTL.ENABLE for one or more queues not cleared within the pod [Thu Sep 16 01:43:51 2021] ixgbe :06:00.0 eno49: NIC Link is Up 10 Gbps, Flow Control: RX/TX
[Kernel-packages] [Bug 2008113] Re: Add firmware for amdgpu products with GC 11.01
Also copied to https://launchpad.net/~vicamo/+archive/ubuntu/ppa-2008113 -- 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/2008113 Title: Add firmware for amdgpu products with GC 11.01 Status in HWE Next: New Status in linux-firmware package in Ubuntu: Confirmed Status in linux-firmware source package in Jammy: In Progress Status in linux-firmware source package in Lunar: Confirmed Bug description: Firmware has been submitted upstream for a product that contains the IP blocks: DCN 3.1.4 GC 11.0.1 SDMA 6.0.1 PSP 13.0.4 VCN 4.0.2 Upstreamed commits: 5c11a374 amdgpu: Add VCN 4.0.2 firmware 5fe2d73c amdgpu: Add PSP 13.0.4 firmware a3332f8b amdgpu: Add SDMA 6.0.1 fimware 4535de67 amdgpu: Add GC 11.0.1 firmware 2e93e4c9 amdgpu: Add DCN 3.1.4 firmware c0a0bc23 amdgpu: Update GC 11.0.1 firmware To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2008113/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008113] Re: Add firmware for amdgpu products with GC 11.01
Prebuilt PPA in https://launchpad.net/~canonical-hwe-team/+archive/ubuntu/linux-firmware-staging: * linux-firmware/jammy version 20220329.git681281e4-0ubuntu3.10+exp.63 * linux-firmware/lunar version Ubuntu-20230213.gitbf4115c1-0ubuntu1+exp.55 -- 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/2008113 Title: Add firmware for amdgpu products with GC 11.01 Status in HWE Next: New Status in linux-firmware package in Ubuntu: Confirmed Status in linux-firmware source package in Jammy: In Progress Status in linux-firmware source package in Lunar: Confirmed Bug description: Firmware has been submitted upstream for a product that contains the IP blocks: DCN 3.1.4 GC 11.0.1 SDMA 6.0.1 PSP 13.0.4 VCN 4.0.2 Upstreamed commits: 5c11a374 amdgpu: Add VCN 4.0.2 firmware 5fe2d73c amdgpu: Add PSP 13.0.4 firmware a3332f8b amdgpu: Add SDMA 6.0.1 fimware 4535de67 amdgpu: Add GC 11.0.1 firmware 2e93e4c9 amdgpu: Add DCN 3.1.4 firmware c0a0bc23 amdgpu: Update GC 11.0.1 firmware To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2008113/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007908] Re: [Possible Regression] powerpc/tm:tm-resched-dscr in ubuntu_kernel_selftests failed on P8
stress tested with 5.15.0-60-generic, there are 20 failures reported in 100 attempts. So it looks like a flaky test instead of a regression. I was too lucky to get multiple failures in a row. ** Attachment added: "stress-with-60.log" https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2007908/+attachment/5649156/+files/stress-with-60.log ** Summary changed: - [Possible Regression] powerpc/tm:tm-resched-dscr in ubuntu_kernel_selftests failed on P8 + powerpc/tm:tm-resched-dscr in ubuntu_kernel_selftests flaky on P8 node gulpin -- 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/2007908 Title: powerpc/tm:tm-resched-dscr in ubuntu_kernel_selftests flaky on P8 node gulpin Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Bug description: Issue found with Focal hwe-5.15.0-66.73~20.04.1 on Power8 node "gulpin". Test failed with: test: tm_resched_dscr tags: git_version:bfd31f0-dirty Binding to cpu 8 main test running as pid 2542 Check DSCR TM context switch: !! killing tm_resched_dscr !! child died by signal 15 failure: tm_resched_dscr Nothing interesting in dmesg / syslog: $ dmesg | tail [ 20.556968] IPv6: ADDRCONF(NETDEV_CHANGE): enP34p1s0f0: link becomes ready [ 20.572182] tg3 0022:01:00.2 enP34p1s0f2: Link is up at 1000 Mbps, full duplex [ 20.572187] tg3 0022:01:00.2 enP34p1s0f2: Flow control is off for TX and off for RX [ 20.572191] tg3 0022:01:00.2 enP34p1s0f2: EEE is disabled [ 20.572201] IPv6: ADDRCONF(NETDEV_CHANGE): enP34p1s0f2: link becomes ready [ 24.598633] kauditd_printk_skb: 19 callbacks suppressed [ 24.598640] audit: type=1400 audit(1676957767.768:31): apparmor="DENIED" operation="open" profile="/usr/sbin/ntpd" name="/snap/bin/" pid=2171 comm="ntpd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [ 27.682671] loop3: detected capacity change from 0 to 8 [ 28.618195] fbcon: Taking over console [ 28.747706] Console: switching to colour frame buffer device 128x48 This issue does not exist with 5.15.0-60.66~20.04.1 test: tm_resched_dscr tags: git_version:bfd31f0-dirty Binding to cpu 8 main test running as pid 28806 Check DSCR TM context switch: OK success: tm_resched_dscr We didn't catch this issue in Jammy 5.15 as Power8 was not supported there, and this test was skipped on the Power9 node that got tested with Jammy (looks like because of the lack of PPC_FEATURE2_HTM) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2007908/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008113] [NEW] Add firmware for amdgpu products with GC 11.01
Public bug reported: Firmware has been submitted upstream for a product that contains the IP blocks: DCN 3.1.4 GC 11.0.1 SDMA 6.0.1 PSP 13.0.4 VCN 4.0.2 Upstreamed commits: 5c11a374 amdgpu: Add VCN 4.0.2 firmware 5fe2d73c amdgpu: Add PSP 13.0.4 firmware a3332f8b amdgpu: Add SDMA 6.0.1 fimware 4535de67 amdgpu: Add GC 11.0.1 firmware 2e93e4c9 amdgpu: Add DCN 3.1.4 firmware c0a0bc23 amdgpu: Update GC 11.0.1 firmware ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux-firmware (Ubuntu Jammy) Importance: Undecided Status: In Progress ** Affects: linux-firmware (Ubuntu Lunar) Importance: Undecided Status: Confirmed ** Tags: amd oem-priority originate-from-2003863 ** Also affects: linux-firmware (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-firmware (Ubuntu Lunar) Importance: Undecided Status: New ** Changed in: linux-firmware (Ubuntu Lunar) Status: New => Confirmed ** Changed in: linux-firmware (Ubuntu Jammy) Status: New => In Progress ** Tags added: amd oem-priority originate-from-2003863 -- 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/2008113 Title: Add firmware for amdgpu products with GC 11.01 Status in HWE Next: New Status in linux-firmware package in Ubuntu: Confirmed Status in linux-firmware source package in Jammy: In Progress Status in linux-firmware source package in Lunar: Confirmed Bug description: Firmware has been submitted upstream for a product that contains the IP blocks: DCN 3.1.4 GC 11.0.1 SDMA 6.0.1 PSP 13.0.4 VCN 4.0.2 Upstreamed commits: 5c11a374 amdgpu: Add VCN 4.0.2 firmware 5fe2d73c amdgpu: Add PSP 13.0.4 firmware a3332f8b amdgpu: Add SDMA 6.0.1 fimware 4535de67 amdgpu: Add GC 11.0.1 firmware 2e93e4c9 amdgpu: Add DCN 3.1.4 firmware c0a0bc23 amdgpu: Update GC 11.0.1 firmware To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2008113/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008111] [NEW] mt9m114 webcam sensor power-up failed
Public bug reported: On my ASUS T100TAM (old Bay Trail 2-in-1 laptop) the webcam is the last non-working piece of hardware. The following dmesg snippet seems to suggest that the kernel needs a special config flag: [ 25.478178] atomisp_gmin_platform: module is from the staging directory, the quality is unknown, you have been warned. [ 25.478274] atomisp_gmin_platform: module verification failed: signature and/or required key missing - tainting kernel [ 25.508617] atomisp_mt9m114: module is from the staging directory, the quality is unknown, you have been warned. [ 25.649601] mt9m114 i2c-INT33F0:00: gmin: power management provided via Crystal Cove PMIC (i2c addr 0x6e) [ 25.649614] mt9m114 i2c-INT33F0:00: gmin_subdev_add: ACPI path is \_SB.I2C4.CAM0 [ 25.650170] mt9m114 i2c-INT33F0:00: Failed to find EFI variable INT33F0:00_ClkSrc [ 25.650176] mt9m114 i2c-INT33F0:00: ClkSrc: using default (1) [ 25.650508] mt9m114 i2c-INT33F0:00: Found DMI entry for 'INT33F0:00_CsiPort' [ 25.650812] mt9m114 i2c-INT33F0:00: Found DMI entry for 'INT33F0:00_CsiLanes' [ 25.650961] mt9m114 i2c-INT33F0:00: will handle gpio0 via ACPI [ 25.651048] mt9m114 i2c-INT33F0:00: will handle gpio1 via ACPI [ 25.651241] mt9m114 i2c-INT33F0:00: Failed to find EFI gmin variable gmin_V1P8GPIO [ 25.651247] mt9m114 i2c-INT33F0:00: V1P8GPIO: using default (-1) [ 25.651440] mt9m114 i2c-INT33F0:00: Failed to find EFI gmin variable gmin_V2P8GPIO [ 25.651445] mt9m114 i2c-INT33F0:00: V2P8GPIO: using default (-1) [ 25.651457] mt9m114 i2c-INT33F0:00: Will use CLK1 (pmc_plt_clk_1) [ 25.651472] intel_soc_pmic_exec_mipi_pmic_seq_element: Not implemented [ 25.651475] intel_soc_pmic_exec_mipi_pmic_seq_element: i2c-addr: 0x6e reg-addr 0x5d value 0x63 mask 0xff [ 25.651480] mt9m114 i2c-INT33F0:00: ACPI didn't mapped the OpRegion needed to access I2C address 0x6e. Need to compile the kernel using CONFIG_*_PMIC_OPREGION settings [ 25.651572] intel_soc_pmic_exec_mipi_pmic_seq_element: Not implemented [ 25.651575] intel_soc_pmic_exec_mipi_pmic_seq_element: i2c-addr: 0x6e reg-addr 0x5d value 0x62 mask 0xff [ 25.651579] mt9m114 i2c-INT33F0:00: ACPI didn't mapped the OpRegion needed to access I2C address 0x6e. Need to compile the kernel using CONFIG_*_PMIC_OPREGION settings [ 25.651659] mt9m114 i2c-INT33F0:00: sensor power-up failed [ 25.651691] INT33F0:00: mt9m114 power-up err Is this something that could be considered for the next kernels? Can I preview test it somehow? Keep in mind that this laptop is pretty slow... ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-32-generic 5.19.0-32.33~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Feb 22 10:56:28 2023 InstallationDate: Installed on 2023-02-12 (9 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) 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 wayland-session ** Attachment added: "Dmesg log" https://bugs.launchpad.net/bugs/2008111/+attachment/5649152/+files/dmesg.txt -- 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/2008111 Title: mt9m114 webcam sensor power-up failed Status in linux-signed-hwe-5.19 package in Ubuntu: New Bug description: On my ASUS T100TAM (old Bay Trail 2-in-1 laptop) the webcam is the last non-working piece of hardware. The following dmesg snippet seems to suggest that the kernel needs a special config flag: [ 25.478178] atomisp_gmin_platform: module is from the staging directory, the quality is unknown, you have been warned. [ 25.478274] atomisp_gmin_platform: module verification failed: signature and/or required key missing - tainting kernel [ 25.508617] atomisp_mt9m114: module is from the staging directory, the quality is unknown, you have been warned. [ 25.649601] mt9m114 i2c-INT33F0:00: gmin: power management provided via Crystal Cove PMIC (i2c addr 0x6e) [ 25.649614] mt9m114 i2c-INT33F0:00: gmin_subdev_add: ACPI path is \_SB.I2C4.CAM0 [ 25.650170] mt9m114 i2c-INT33F0:00: Failed to find EFI variable INT33F0:00_ClkSrc [ 25.650176] mt9m114 i2c-INT33F0:00: ClkSrc: using default (1) [ 25.650508] mt9m114 i2c-INT33F0:00: Found DMI entry for 'INT33F0:00_CsiPort' [ 25.650812] mt9m114 i2c-INT33F0:00: Found DMI entry for 'INT33F0:00_CsiLanes' [ 25.650961] mt9m114 i2c-INT33F0:00: will handle gpio0 via ACPI [ 25.651048] mt9m114 i2c-INT33F0:00: will handle gpio1 via ACPI [ 25.651241] mt9m114
Re: [Kernel-packages] [Bug 1981433] Re: [Asus Zenbook UX3402ZA] Sound doesn't work at all
yes, i saw, was added quirk to kernel in ALSA development 2023-02 for UM3402 and are some tweaks to make function it now last posts: https://ubuntuforums.org/showthread.php?t=2476921=3 [v1] ALSA: hda/realtek: Add quirk for ASUS UM3402 using CS35L41 (https://patchwork.kernel.org/project/alsa-devel/list/?series=719159)- - ---- 2023-02-06 Stefan Binding (https://patchwork.kernel.org/project/alsa-devel/list/?submitter=198213) New [v6,4/4] ASoC: dt-bindings: cirrus,cs35l41: Document CS35l41 shared boost (https://patchwork.kernel.org/project/alsa-devel/patch/20230222093244.938156-5-lucas.tan...@collabora.com/) Add CS35L41 shared boost feature (https://patchwork.kernel.org/project/alsa-devel/list/?series=724008) [v2,3/3] ALSA: hda: cs35l41: Enable Amp High Pass Filter (https://patchwork.kernel.org/project/alsa-devel/patch/20230213145008.1215849-4-sbind...@opensource.cirrus.com/) Fixes and Improvements for CS35L41 HDA (https://patchwork.kernel.org/project/alsa-devel/list/?series=721315)- - ---- 2023-02-13 Stefan Binding (https://patchwork.kernel.org/project/alsa-devel/list/?submitter=198213) -- Původní e-mail -- Od: Swastik Harish <1981...@bugs.launchpad.net> Komu: nikola.jan...@seznam.cz Datum: 22. 2. 2023 13:37:43 Předmět: Re: [Bug 1981433] Re: [Asus Zenbook UX3402ZA] Sound doesn't work at all "Is there any update/movement on this? Really need these speakers to work... On 08/02/23 09:38, Daniel van Vugt wrote: > The previous comment leads us to: > https://github.com/CirrusLogic/linux-firmware/issues/8 > > ** Tags added: kinetic > > ** Also affects: linux-firmware (Ubuntu) > Importance: Undecided > Status: New > > ** Bug watch added: github.com/CirrusLogic/linux-firmware/issues #8 > https://github.com/CirrusLogic/linux-firmware/issues/8 > > ** Also affects: linux-firmware via > https://github.com/CirrusLogic/linux-firmware/issues/8 > Importance: Unknown > Status: Unknown > > ** Also affects: firmware-sof (Ubuntu) > Importance: Undecided > Status: New > > ** No longer affects: firmware-sof (Ubuntu) > > ** Changed in: linux-firmware (Ubuntu) > Status: New => Confirmed > -- You received this bug notification because you are subscribed to a duplicate bug report (1994948). https://bugs.launchpad.net/bugs/1981433 Title: [Asus Zenbook UX3402ZA] Sound doesn't work at all Status in Linux Firmware: Unknown Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Confirmed Bug description: Sound/speakers don't work at all on Asus Zenbook 14 OLED and other similar models with Realtek ALC294. No solution works. Audio is not muted, tried adding snd-hda arguments - no dice. This has been reported numerous times, when will a fix finally be rolled out?! ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-41-generic 5.15.0-41.44 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: martin 1730 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Jul 12 13:57:05 2022 InstallationDate: Installed on 2022-07-12 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: ASUSTeK COMPUTER INC. Zenbook UX3402ZA_UX3402ZA ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic root=UUID=40c 924aa-99ad-4770-a66d-33d3359f6053 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-41-generic N/A linux-backports-modules-5.15.0-41-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2022 dmi.bios.release: 5.25 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: UX3402ZA.305 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX3402ZA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.5 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX3402ZA.305:bd 06/15/2022:br5.25:efr3.5:svnASUSTeKCOMPUTERINC.:pnZenbookUX3402ZA_UX3402ZA: pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX3402ZA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31: cvr1.0:sku: dmi.product.family: Zenbook dmi.product.name: Zenbook UX3402ZA_UX3402ZA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/linux-firmware/+bug/1981433/+subscriptions " -- You received this bug notification because you are a member of Kernel
[Kernel-packages] [Bug 1992513] Re: apt will not install nvidia-driver-470-server if nvidia-driver-450-server is installed and out of date
One should use ubuntu-drivers CLI or Additional Drivers GUI to install or switch nvidia graphics stacks from one major series to another. It ensures that correct matching pre-signed kernel drivers are installed together with the right userspace (with and without gui stacks, as needed). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470-server in Ubuntu. https://bugs.launchpad.net/bugs/1992513 Title: apt will not install nvidia-driver-470-server if nvidia- driver-450-server is installed and out of date Status in apt package in Ubuntu: Triaged Status in nvidia-graphics-drivers-450-server package in Ubuntu: New Status in nvidia-graphics-drivers-470-server package in Ubuntu: New Bug description: apt/jammy apt will refuse to install nvidia-driver-470-server if nvidia-driver-450-server is installed *and* out of date. I can reproduce this by disabling all but the jammy release pocket, installing the old n-d-450-s from there, and then enabling updates and trying to install n-v-470-s (where a new n-d-450-s is available): # libnvidia-gl-450-server has an update available root@dannf-apt-jammy:/var/cache# apt install --dry-run libnvidia-gl-470-server -o Debug::pkgProblemResolver=yes Reading package lists... Done Building dependency tree... Done Reading state information... Done 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: libnvidia-common-450-server : Conflicts: libnvidia-common libnvidia-common-470-server : Conflicts: libnvidia-common E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1992513/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1987829] Re: LG Gram 12gen high CPU use when USB-C/TB is in use
@kaihengfeng I gave latest mainline a try on my Fedora, installed through copr according to this doc: https://fedoraproject.org/wiki/Kernel_Vanilla_Repositories It's kernel 6.3 instead of 6.2, but I would assume it contains changes from 6.2. No luck, still same symptoms. # uname -a Linux lrob.local 6.3.0-0.rc0.20230222gt5b7c4cab.201.vanilla.fc37.x86_64 #1 SMP PREEMPT_DYNAMIC Wed Feb 22 05:16:05 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux At idle: # cat /proc/loadavg 2.66 3.05 2.87 3/2147 27819 Processes on top of CPU utilization: 1044 root 20 0 0 0 0 D 18.2 0.0 0:07.52 [kworker/u32:8+USBC000:00-con0] 19136 root 20 0 0 0 0 D 17.5 0.0 0:02.22 [kworker/0:0+events] 230 root 20 0 0 0 0 R 15.2 0.0 1:04.60 [kworker/0:3+kacpi_notify] Also the issue is now occurring even when the laptop's battery is 100% charged as it is currently. On a side note, a Thunderbolt docking station from Dell, which also charges the laptop, shows the exact same symptoms as the embedded charger. All the best. -- 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/1987829 Title: LG Gram 12gen high CPU use when USB-C/TB is in use Status in linux package in Ubuntu: Confirmed Status in linux package in Fedora: New Bug description: LG Gram laptop 17Z90Q with a Core i7-1260P CPU. Whenever an external monitor is connected to USB-C/Thunderbolt 4, average load goes above 3.0 and the machine is getting very hot. Output from top -H shows a lot of kworker CPU usage: top - 11:45:06 up 33 min, 2 users, load average: 3,30, 3,08, 2,79 Threads: 1442 total, 2 running, 1440 sleeping, 0 stopped, 0 zombie %Cpu(s): 0,1 us, 3,7 sy, 0,0 ni, 96,1 id, 0,0 wa, 0,0 hi, 0,1 si, 0,0 st MiB Mem : 15684,6 total, 8510,2 free, 2580,8 used, 4593,6 buff/cache MiB Swap: 3815,0 total, 3815,0 free, 0,0 used. 11326,9 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ WCHAN COMMAND 7766 root 20 0 0 0 0 R 19,8 0,0 0:56.05 worker_th+ kworker/0:2-events 196 root 20 0 0 0 0 D 15,8 0,0 1:18.12 ec_guard kworker/u32:2+USBC000:00-con0 10237 root 20 0 0 0 0 I 12,9 0,0 0:26.44 worker_th+ kworker/0:0-events 1027 root 20 0 0 0 0 I 6,6 0,0 0:43.30 worker_th+ kworker/1:3-events 10971 root 20 0 0 0 0 I 4,0 0,0 0:00.20 worker_th+ kworker/15:0-events 175 root 20 0 0 0 0 I 2,3 0,0 0:03.24 worker_th+ kworker/11:1-events 2410 root 20 0 0 0 0 I 1,7 0,0 0:05.49 worker_th+ kworker/9:3-events Perf shows a lot of time spent inside handle_irq_event/acpi_ev_gpe_detect/acpi_hw_gpe_read. Additionally, kernel log is getting spammed with these lines every 4 seconds (but also without any USB-C device attached): [ 223.514304] ACPI Error: No handler for Region [XIN1] (f2ad4f1f) [UserDefinedRegion] (20210730/evregion-130) [ 223.514323] ACPI Error: Region UserDefinedRegion (ID=143) has no handler (20210730/exfldio-261) [ 223.514337] Initialized Local Variables for Method [_TMP]: [ 223.514339] Local0: 21495082Integer 0034 [ 223.514349] No Arguments are initialized for method [_TMP] [ 223.514354] ACPI Error: Aborting method \_SB.PC00.LPCB.LGEC.SEN2._TMP due to previous error (AE_NOT_EXIST) (20210730/psparse-529) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-46-generic 5.15.0-46.49 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: me 1678 F pulseaudio /dev/snd/controlC1: me 1678 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass Date: Fri Aug 26 11:57:05 2022 InstallationDate: Installed on 2022-08-25 (1 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LG Electronics 17Z90Q-G.AA78N ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=e2f96916-a67c-432e-b687-730071271216 ro quiet splash vt.handoff=7 PulseList: Error:
[Kernel-packages] [Bug 2007798] Re: [Inspiron 7590, Realtek ALC3254, Speaker, Internal] fails after a while
** Changed in: linux (Ubuntu Jammy) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2007798 Title: [Inspiron 7590, Realtek ALC3254, Speaker, Internal] fails after a while Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Committed Bug description: == SRU Justification == [Impact] Audio playback becomes silent on some Intel SoF systems. [Fix] Revert offending commit. [Test] The speaker can always play sound after the commit gets reverted. [Where problems could occur] Audio on linux 5.15 has been working fine without the patch for a long time, so this only restore it to where it was. == Original Bug Report == [Summary] During the kernel SRU testing on focal-hwe, I found the audio output of some machines are broken. I've tested some of machine on Jammy using same kernel(5.15.0-66-generic) and haven't seen this happened. The volume bars in settings react to what sound is played correctly and device is detected as well. [Reproduce steps] 1. install focal 2. enable -proposed 3. run apt dist-upgrade. 4. reboot. 5. press fn keys to volume up then volume down or play a short youtube video. 6. after a while can't hear any sound from the speaker. [Failure rate] 10/10 [Additional info] If I run "sudo alsa force-reload" can make audio work again, but after a while it breaks again. These are machines that impacted by this bug: https://certification.canonical.com/hardware/202007-28045/ https://certification.canonical.com/hardware/201906-27109/ https://certification.canonical.com/hardware/201903-26881/ https://certification.canonical.com/hardware/202007-28047/ https://certification.canonical.com/hardware/202007-28055/ https://certification.canonical.com/hardware/202005-27899/ ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.15.0-66.73~20.04.1-generic 5.15.85 Uname: Linux 5.15.0-66-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1303 F pulseaudio CasperMD5CheckResult: skip Date: Sun Feb 19 21:24:59 2023 InstallationDate: Installed on 2020-08-03 (930 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_Card: Cannon Lake PCH cAVS - sof-hda-dsp Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: Feb 19 20:53:23 dell-inspiron-7591-nebula-n15a-c2-201903-26881 dbus-daemon[985]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.34' (uid=1000 pid=1303 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") Symptom_Type: Sound works for a while, then breaks Title: [Inspiron 7590, Realtek ALC3254, Speaker, Internal] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/06/2019 dmi.bios.release: 1.5 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd11/06/2019:br1.5:svnDellInc.:pnInspiron7590:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0922: dmi.product.family: Inspiron dmi.product.name: Inspiron 7590 dmi.product.sku: 0922 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007798/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2003130] Re: Jammy update: v5.15.81 upstream stable release
Reverted "ASoC: soc-pcm: Don't zero TDM masks in __soc_pcm_open()" because it introduced regressions (bug #2007798). -- 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/2003130 Title: Jammy update: v5.15.81 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.15.81 upstream stable release from git://git.kernel.org/ ASoC: fsl_sai: use local device pointer ASoC: fsl_asrc fsl_esai fsl_sai: allow CONFIG_PM=N serial: Add rs485_supported to uart_port serial: fsl_lpuart: Fill in rs485_supported tty: serial: fsl_lpuart: don't break the on-going transfer when global reset sctp: remove the unnecessary sinfo_stream check in sctp_prsctp_prune_unsent sctp: clear out_curr if all frag chunks of current msg are pruned cifs: introduce new helper for cifs_reconnect() cifs: split out dfs code from cifs_reconnect() cifs: support nested dfs links over reconnect cifs: Fix connections leak when tlink setup failed ata: libata-scsi: simplify __ata_scsi_queuecmd() ata: libata-core: do not issue non-internal commands once EH is pending drm/display: Don't assume dual mode adaptors support i2c sub-addressing nvme-pci: add NVME_QUIRK_BOGUS_NID for Micron Nitro nvme-pci: disable namespace identifiers for the MAXIO MAP1001 nvme-pci: disable write zeroes on various Kingston SSD nvme-pci: add NVME_QUIRK_BOGUS_NID for Netac NV7000 iio: ms5611: Simplify IO callback parameters iio: pressure: ms5611: fixed value compensation bug ceph: do not update snapshot context when there is no new snapshot ceph: avoid putting the realm twice when decoding snaps fails x86/sgx: Create utility to validate user provided offset and length x86/sgx: Add overflow check in sgx_validate_offset_length() binder: validate alloc->mm in ->mmap() handler ceph: Use kcalloc for allocating multiple elements ceph: fix NULL pointer dereference for req->r_session wifi: mac80211: fix memory free error when registering wiphy fail wifi: mac80211_hwsim: fix debugfs attribute ps with rc table support riscv: dts: sifive unleashed: Add PWM controlled LEDs audit: fix undefined behavior in bit shift for AUDIT_BIT wifi: airo: do not assign -1 to unsigned char wifi: mac80211: Fix ack frame idr leak when mesh has no route wifi: ath11k: Fix QCN9074 firmware boot on x86 spi: stm32: fix stm32_spi_prepare_mbr() that halves spi clk for every run selftests/bpf: Add verifier test for release_reference() Revert "net: macsec: report real_dev features when HW offloading is enabled" platform/x86: ideapad-laptop: Disable touchpad_switch platform/x86: touchscreen_dmi: Add info for the RCA Cambio W101 v2 2-in-1 platform/x86/intel/pmt: Sapphire Rapids PMT errata fix platform/x86/intel/hid: Add some ACPI device IDs scsi: ibmvfc: Avoid path failures during live migration scsi: scsi_debug: Make the READ CAPACITY response compliant with ZBC drm: panel-orientation-quirks: Add quirk for Acer Switch V 10 (SW5-017) block, bfq: fix null pointer dereference in bfq_bio_bfqg() arm64/syscall: Include asm/ptrace.h in syscall_wrapper header. nvmet: fix memory leak in nvmet_subsys_attr_model_store_locked Revert "drm/amdgpu: Revert "drm/amdgpu: getting fan speed pwm for vega10 properly"" ALSA: usb-audio: add quirk to fix Hamedal C20 disconnect issue RISC-V: vdso: Do not add missing symbols to version section in linker script MIPS: pic32: treat port as signed integer xfrm: fix "disable_policy" on ipv4 early demux xfrm: replay: Fix ESN wrap around for GSO af_key: Fix send_acquire race with pfkey_register ARM: dts: am335x-pcm-953: Define fixed regulators in root node ASoC: hdac_hda: fix hda pcm buffer overflow issue ASoC: sgtl5000: Reset the CHIP_CLK_CTRL reg on remove ASoC: soc-pcm: Don't zero TDM masks in __soc_pcm_open() x86/hyperv: Restore VP assist page after cpu offlining/onlining scsi: storvsc: Fix handling of srb_status and capacity change events ASoC: max98373: Add checks for devm_kcalloc regulator: core: fix kobject release warning and memory leak in regulator_register() spi: dw-dma: decrease reference count in dw_spi_dma_init_mfld() regulator: core: fix UAF in destroy_regulator() bus: sunxi-rsb: Remove the shutdown callback bus: sunxi-rsb: Support atomic transfers tee: optee: fix possible memory leak in
[Kernel-packages] [Bug 2008069] Re: IO stop running on NVME host when target is down
** Attachment added: "kern.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008069/+attachment/5649139/+files/kern.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/2008069 Title: IO stop running on NVME host when target is down Status in linux package in Ubuntu: Incomplete Bug description: Description: When running nvme with multipath enabled, it seems as host does not try to use another path. Steps to reproduce: Step 1: Install Ubuntu 22.04 LTS (ubuntu-22.04-live-server-amd64) on system. Step 2: Install nvme-cli package,currently installed version is nvme version 1.16 Step 3: Run IO on the nvme volume. step 4: Stop the service of the target controller. Expected Behavior: Upon stopping the service, host will try using another path for failed IO. from kernel log: Nov 11 08:58:10 localhost kernel: [88496.416058] sysfs: cannot create duplicate filename '/class/block/nvme0n1' Nov 11 08:58:10 localhost kernel: [88496.416062] CPU: 17 PID: 6358 Comm: kworker/u49:0 Kdump: loaded Tainted: GW 5.15.0-47-generic #51-Ubuntu Nov 11 08:58:10 localhost kernel: [88496.416067] Hardware name: Cisco Systems Inc UCSC-C240-M3S2/UCSC-C240-M3S2, BIOS C240M3.2.0.9a.0.113020152237 11/30/2015 Nov 11 08:58:10 localhost kernel: [88496.416069] Workqueue: nvme-wq nvme_scan_work [nvme_core] Nov 11 08:58:10 localhost kernel: [88496.416089] Call Trace: Nov 11 08:58:10 localhost kernel: [88496.416093] Nov 11 08:58:10 localhost kernel: [88496.416097] show_stack+0x52/0x5c Nov 11 08:58:10 localhost kernel: [88496.416107] dump_stack_lvl+0x4a/0x63 Nov 11 08:58:10 localhost kernel: [88496.416115] dump_stack+0x10/0x16 Nov 11 08:58:10 localhost kernel: [88496.416118] sysfs_warn_dup.cold+0x17/0x2b Nov 11 08:58:10 localhost kernel: [88496.416123] sysfs_do_create_link_sd+0xb7/0xd0 Nov 11 08:58:10 localhost kernel: [88496.416131] sysfs_create_link+0x21/0x40 Nov 11 08:58:10 localhost kernel: [88496.416135] device_add+0x2a3/0x7b0 Nov 11 08:58:10 localhost kernel: [88496.416141] ? dev_set_name+0x53/0x70 Nov 11 08:58:10 localhost kernel: [88496.416147] device_add_disk+0xfb/0x3c0 Nov 11 08:58:10 localhost kernel: [88496.416153] ? nvme_update_ns_info+0x14b/0x390 [nvme_core] Nov 11 08:58:10 localhost kernel: [88496.416162] nvme_alloc_ns+0x1ff/0x400 [nvme_core] Nov 11 08:58:10 localhost kernel: [88496.416172] nvme_validate_or_alloc_ns+0xcc/0x190 [nvme_core] Nov 11 08:58:10 localhost kernel: [88496.416181] nvme_scan_ns_list+0x109/0x390 [nvme_core] Nov 11 08:58:10 localhost kernel: [88496.416191] nvme_scan_work+0xd9/0x250 [nvme_core] Nov 11 08:58:10 localhost kernel: [88496.416200] process_one_work+0x22b/0x3d0 Nov 11 08:58:10 localhost kernel: [88496.416205] worker_thread+0x53/0x420 Nov 11 08:58:10 localhost kernel: [88496.416207] ? process_one_work+0x3d0/0x3d0 Nov 11 08:58:10 localhost kernel: [88496.416210] kthread+0x12a/0x150 Nov 11 08:58:10 localhost kernel: [88496.416214] ? set_kthread_struct+0x50/0x50 Nov 11 08:58:10 localhost kernel: [88496.416218] ret_from_fork+0x22/0x30 Nov 11 08:58:10 localhost kernel: [88496.416225] Nov 11 09:00:06 localhost kernel: [88612.227916] nvme nvme2: starting error recovery Nov 11 09:00:06 localhost kernel: [88612.228115] nvme nvme2: queue 4 socket state 11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008069/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007908] Re: [Possible Regression] powerpc/tm:tm-resched-dscr in ubuntu_kernel_selftests failed on P8
Here is the test output with -66. ** Attachment added: "stress-with-66.log" https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2007908/+attachment/5649138/+files/stress-with-66.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/2007908 Title: [Possible Regression] powerpc/tm:tm-resched-dscr in ubuntu_kernel_selftests failed on P8 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Bug description: Issue found with Focal hwe-5.15.0-66.73~20.04.1 on Power8 node "gulpin". Test failed with: test: tm_resched_dscr tags: git_version:bfd31f0-dirty Binding to cpu 8 main test running as pid 2542 Check DSCR TM context switch: !! killing tm_resched_dscr !! child died by signal 15 failure: tm_resched_dscr Nothing interesting in dmesg / syslog: $ dmesg | tail [ 20.556968] IPv6: ADDRCONF(NETDEV_CHANGE): enP34p1s0f0: link becomes ready [ 20.572182] tg3 0022:01:00.2 enP34p1s0f2: Link is up at 1000 Mbps, full duplex [ 20.572187] tg3 0022:01:00.2 enP34p1s0f2: Flow control is off for TX and off for RX [ 20.572191] tg3 0022:01:00.2 enP34p1s0f2: EEE is disabled [ 20.572201] IPv6: ADDRCONF(NETDEV_CHANGE): enP34p1s0f2: link becomes ready [ 24.598633] kauditd_printk_skb: 19 callbacks suppressed [ 24.598640] audit: type=1400 audit(1676957767.768:31): apparmor="DENIED" operation="open" profile="/usr/sbin/ntpd" name="/snap/bin/" pid=2171 comm="ntpd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [ 27.682671] loop3: detected capacity change from 0 to 8 [ 28.618195] fbcon: Taking over console [ 28.747706] Console: switching to colour frame buffer device 128x48 This issue does not exist with 5.15.0-60.66~20.04.1 test: tm_resched_dscr tags: git_version:bfd31f0-dirty Binding to cpu 8 main test running as pid 28806 Check DSCR TM context switch: OK success: tm_resched_dscr We didn't catch this issue in Jammy 5.15 as Power8 was not supported there, and this test was skipped on the Power9 node that got tested with Jammy (looks like because of the lack of PPC_FEATURE2_HTM) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2007908/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007908] Re: [Possible Regression] powerpc/tm:tm-resched-dscr in ubuntu_kernel_selftests failed on P8
stress tested with the following command on node gulpin with -66 shows this test is a bit flaky: failcnt=0 for i in `seq 1 100`; do time sudo ./tm-resched-dscr if [ $? -ne 0 ]; then let "failcnt=$failcnt+1" fi done echo $failcnt There are 27 failures in 100 attempts. Next is to stress test with -60 -- 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/2007908 Title: [Possible Regression] powerpc/tm:tm-resched-dscr in ubuntu_kernel_selftests failed on P8 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Bug description: Issue found with Focal hwe-5.15.0-66.73~20.04.1 on Power8 node "gulpin". Test failed with: test: tm_resched_dscr tags: git_version:bfd31f0-dirty Binding to cpu 8 main test running as pid 2542 Check DSCR TM context switch: !! killing tm_resched_dscr !! child died by signal 15 failure: tm_resched_dscr Nothing interesting in dmesg / syslog: $ dmesg | tail [ 20.556968] IPv6: ADDRCONF(NETDEV_CHANGE): enP34p1s0f0: link becomes ready [ 20.572182] tg3 0022:01:00.2 enP34p1s0f2: Link is up at 1000 Mbps, full duplex [ 20.572187] tg3 0022:01:00.2 enP34p1s0f2: Flow control is off for TX and off for RX [ 20.572191] tg3 0022:01:00.2 enP34p1s0f2: EEE is disabled [ 20.572201] IPv6: ADDRCONF(NETDEV_CHANGE): enP34p1s0f2: link becomes ready [ 24.598633] kauditd_printk_skb: 19 callbacks suppressed [ 24.598640] audit: type=1400 audit(1676957767.768:31): apparmor="DENIED" operation="open" profile="/usr/sbin/ntpd" name="/snap/bin/" pid=2171 comm="ntpd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [ 27.682671] loop3: detected capacity change from 0 to 8 [ 28.618195] fbcon: Taking over console [ 28.747706] Console: switching to colour frame buffer device 128x48 This issue does not exist with 5.15.0-60.66~20.04.1 test: tm_resched_dscr tags: git_version:bfd31f0-dirty Binding to cpu 8 main test running as pid 28806 Check DSCR TM context switch: OK success: tm_resched_dscr We didn't catch this issue in Jammy 5.15 as Power8 was not supported there, and this test was skipped on the Power9 node that got tested with Jammy (looks like because of the lack of PPC_FEATURE2_HTM) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2007908/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008084] Re: Linux image 5.19 cuts off the build date
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/2008084 Title: Linux image 5.19 cuts off the build date Status in linux package in Ubuntu: Confirmed Bug description: Hi, The output of uname -a is failing to show the full build date on Jammy 22.04.2 with kernel 5.19 as the string is too long. I believe there is some size limit that is being overrun when building the kernel. lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 22.04.2 LTS Release: 22.04 Codename: jammy uname -v #33~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Mon Jan 30 17:03:34 UTC 2 uname -a Linux kianp 5.19.0-32-generic #33~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Mon Jan 30 17:03:34 UTC 2 x86_64 x86_64 x86_64 GNU/Linux cat /proc/version Linux version 5.19.0-32-generic (buildd@lcy02-amd64-026) (x86_64-linux-gnu-gcc (Ubuntu 11.3.0-1ubuntu1~22.04) 11.3.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #33~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Mon Jan 30 17:03:34 UTC 2 cat /proc/version_signature Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 See above, the build date is missing the year (2023). On an older kernel the output of uname -v is much shorter which leads me to believe some buffer size limit is being hit. (Older Kernel): uname -v #66-Ubuntu SMP Fri Jan 20 14:29:49 UTC 2023 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008084/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008084] [NEW] Linux image 5.19 cuts off the build date
Public bug reported: Hi, The output of uname -a is failing to show the full build date on Jammy 22.04.2 with kernel 5.19 as the string is too long. I believe there is some size limit that is being overrun when building the kernel. lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 22.04.2 LTS Release:22.04 Codename: jammy uname -v #33~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Mon Jan 30 17:03:34 UTC 2 uname -a Linux kianp 5.19.0-32-generic #33~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Mon Jan 30 17:03:34 UTC 2 x86_64 x86_64 x86_64 GNU/Linux cat /proc/version Linux version 5.19.0-32-generic (buildd@lcy02-amd64-026) (x86_64-linux-gnu-gcc (Ubuntu 11.3.0-1ubuntu1~22.04) 11.3.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #33~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Mon Jan 30 17:03:34 UTC 2 cat /proc/version_signature Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 See above, the build date is missing the year (2023). On an older kernel the output of uname -v is much shorter which leads me to believe some buffer size limit is being hit. (Older Kernel): uname -v #66-Ubuntu SMP Fri Jan 20 14:29:49 UTC 2023 ** Affects: linux (Ubuntu) Importance: Undecided Status: 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/2008084 Title: Linux image 5.19 cuts off the build date Status in linux package in Ubuntu: Confirmed Bug description: Hi, The output of uname -a is failing to show the full build date on Jammy 22.04.2 with kernel 5.19 as the string is too long. I believe there is some size limit that is being overrun when building the kernel. lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 22.04.2 LTS Release: 22.04 Codename: jammy uname -v #33~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Mon Jan 30 17:03:34 UTC 2 uname -a Linux kianp 5.19.0-32-generic #33~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Mon Jan 30 17:03:34 UTC 2 x86_64 x86_64 x86_64 GNU/Linux cat /proc/version Linux version 5.19.0-32-generic (buildd@lcy02-amd64-026) (x86_64-linux-gnu-gcc (Ubuntu 11.3.0-1ubuntu1~22.04) 11.3.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #33~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Mon Jan 30 17:03:34 UTC 2 cat /proc/version_signature Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 See above, the build date is missing the year (2023). On an older kernel the output of uname -v is much shorter which leads me to believe some buffer size limit is being hit. (Older Kernel): uname -v #66-Ubuntu SMP Fri Jan 20 14:29:49 UTC 2023 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008084/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008069] Re: IO stop running on NVME host when target is down
** Description changed: - [ Impact ] - - Tab completion for the nvme command is completely broken in bash. - - [ Test Plan ] - - 1. Install nvme-cli package - 2. Open terminal - 3. type any nvme command and hit tab - - Tab completion should show entries like "list", "create-ns", etc. - - [ Where problems could occur ] - - The patch only changes the tab completion for nvme, but rebuilding nvme- - cli can reveal bugs on package upgrade, etc. - - [ Original report ] Description: When running nvme with multipath enabled, it seems as host does not try to use another path. Steps to reproduce: Step 1: Install Ubuntu 22.04 LTS (ubuntu-22.04-live-server-amd64) on system. Step 2: Install nvme-cli package,currently installed version is nvme version 1.16 - Step 3: Run IO on the nvme volume. + Step 3: Run IO on the nvme volume. step 4: Stop the service of the target controller. Expected Behavior: Upon stopping the service, host will try using another path for failed IO. from kernel log: Nov 11 08:58:10 localhost kernel: [88496.416058] sysfs: cannot create duplicate filename '/class/block/nvme0n1' Nov 11 08:58:10 localhost kernel: [88496.416062] CPU: 17 PID: 6358 Comm: kworker/u49:0 Kdump: loaded Tainted: GW 5.15.0-47-generic #51-Ubuntu Nov 11 08:58:10 localhost kernel: [88496.416067] Hardware name: Cisco Systems Inc UCSC-C240-M3S2/UCSC-C240-M3S2, BIOS C240M3.2.0.9a.0.113020152237 11/30/2015 Nov 11 08:58:10 localhost kernel: [88496.416069] Workqueue: nvme-wq nvme_scan_work [nvme_core] Nov 11 08:58:10 localhost kernel: [88496.416089] Call Trace: Nov 11 08:58:10 localhost kernel: [88496.416093] Nov 11 08:58:10 localhost kernel: [88496.416097] show_stack+0x52/0x5c Nov 11 08:58:10 localhost kernel: [88496.416107] dump_stack_lvl+0x4a/0x63 Nov 11 08:58:10 localhost kernel: [88496.416115] dump_stack+0x10/0x16 Nov 11 08:58:10 localhost kernel: [88496.416118] sysfs_warn_dup.cold+0x17/0x2b Nov 11 08:58:10 localhost kernel: [88496.416123] sysfs_do_create_link_sd+0xb7/0xd0 Nov 11 08:58:10 localhost kernel: [88496.416131] sysfs_create_link+0x21/0x40 Nov 11 08:58:10 localhost kernel: [88496.416135] device_add+0x2a3/0x7b0 Nov 11 08:58:10 localhost kernel: [88496.416141] ? dev_set_name+0x53/0x70 Nov 11 08:58:10 localhost kernel: [88496.416147] device_add_disk+0xfb/0x3c0 Nov 11 08:58:10 localhost kernel: [88496.416153] ? nvme_update_ns_info+0x14b/0x390 [nvme_core] Nov 11 08:58:10 localhost kernel: [88496.416162] nvme_alloc_ns+0x1ff/0x400 [nvme_core] Nov 11 08:58:10 localhost kernel: [88496.416172] nvme_validate_or_alloc_ns+0xcc/0x190 [nvme_core] Nov 11 08:58:10 localhost kernel: [88496.416181] nvme_scan_ns_list+0x109/0x390 [nvme_core] Nov 11 08:58:10 localhost kernel: [88496.416191] nvme_scan_work+0xd9/0x250 [nvme_core] Nov 11 08:58:10 localhost kernel: [88496.416200] process_one_work+0x22b/0x3d0 Nov 11 08:58:10 localhost kernel: [88496.416205] worker_thread+0x53/0x420 Nov 11 08:58:10 localhost kernel: [88496.416207] ? process_one_work+0x3d0/0x3d0 Nov 11 08:58:10 localhost kernel: [88496.416210] kthread+0x12a/0x150 Nov 11 08:58:10 localhost kernel: [88496.416214] ? set_kthread_struct+0x50/0x50 Nov 11 08:58:10 localhost kernel: [88496.416218] ret_from_fork+0x22/0x30 Nov 11 08:58:10 localhost kernel: [88496.416225] Nov 11 09:00:06 localhost kernel: [88612.227916] nvme nvme2: starting error recovery Nov 11 09:00:06 localhost kernel: [88612.228115] nvme nvme2: queue 4 socket state 11 -- 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/2008069 Title: IO stop running on NVME host when target is down Status in linux package in Ubuntu: Incomplete Bug description: Description: When running nvme with multipath enabled, it seems as host does not try to use another path. Steps to reproduce: Step 1: Install Ubuntu 22.04 LTS (ubuntu-22.04-live-server-amd64) on system. Step 2: Install nvme-cli package,currently installed version is nvme version 1.16 Step 3: Run IO on the nvme volume. step 4: Stop the service of the target controller. Expected Behavior: Upon stopping the service, host will try using another path for failed IO. from kernel log: Nov 11 08:58:10 localhost kernel: [88496.416058] sysfs: cannot create duplicate filename '/class/block/nvme0n1' Nov 11 08:58:10 localhost kernel: [88496.416062] CPU: 17 PID: 6358 Comm: kworker/u49:0 Kdump: loaded Tainted: GW 5.15.0-47-generic #51-Ubuntu Nov 11 08:58:10 localhost kernel: [88496.416067] Hardware name: Cisco Systems Inc UCSC-C240-M3S2/UCSC-C240-M3S2, BIOS C240M3.2.0.9a.0.113020152237 11/30/2015 Nov 11 08:58:10 localhost kernel: [88496.416069] Workqueue: nvme-wq nvme_scan_work [nvme_core] Nov 11 08:58:10 localhost kernel: [88496.416089] Call Trace: Nov 11 08:58:10 localhost
Re: [Kernel-packages] [Bug 1981433] Re: [Asus Zenbook UX3402ZA] Sound doesn't work at all
Is there any update/movement on this? Really need these speakers to work... On 08/02/23 09:38, Daniel van Vugt wrote: > The previous comment leads us to: > https://github.com/CirrusLogic/linux-firmware/issues/8 > > ** Tags added: kinetic > > ** Also affects: linux-firmware (Ubuntu) > Importance: Undecided > Status: New > > ** Bug watch added: github.com/CirrusLogic/linux-firmware/issues #8 > https://github.com/CirrusLogic/linux-firmware/issues/8 > > ** Also affects: linux-firmware via > https://github.com/CirrusLogic/linux-firmware/issues/8 > Importance: Unknown > Status: Unknown > > ** Also affects: firmware-sof (Ubuntu) > Importance: Undecided > Status: New > > ** No longer affects: firmware-sof (Ubuntu) > > ** Changed in: linux-firmware (Ubuntu) > Status: New => Confirmed > -- 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/1981433 Title: [Asus Zenbook UX3402ZA] Sound doesn't work at all Status in Linux Firmware: Unknown Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Confirmed Bug description: Sound/speakers don't work at all on Asus Zenbook 14 OLED and other similar models with Realtek ALC294. No solution works. Audio is not muted, tried adding snd-hda arguments - no dice. This has been reported numerous times, when will a fix finally be rolled out?! ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-41-generic 5.15.0-41.44 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: martin 1730 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Jul 12 13:57:05 2022 InstallationDate: Installed on 2022-07-12 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: ASUSTeK COMPUTER INC. Zenbook UX3402ZA_UX3402ZA ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic root=UUID=40c924aa-99ad-4770-a66d-33d3359f6053 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-41-generic N/A linux-backports-modules-5.15.0-41-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2022 dmi.bios.release: 5.25 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: UX3402ZA.305 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX3402ZA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.5 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX3402ZA.305:bd06/15/2022:br5.25:efr3.5:svnASUSTeKCOMPUTERINC.:pnZenbookUX3402ZA_UX3402ZA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX3402ZA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:sku: dmi.product.family: Zenbook dmi.product.name: Zenbook UX3402ZA_UX3402ZA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/linux-firmware/+bug/1981433/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007967] Re: [UBUNTU 22.04] PCIe Mensa card: Automatic recovery on second port fails - operator intervention required
After discussion with bug reporter, cancelling this and setting it to Invalid. ** Changed in: linux (Ubuntu) Status: New => Invalid ** Information type changed from Public to Private -- 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/2007967 Title: [UBUNTU 22.04] PCIe Mensa card: Automatic recovery on second port fails - operator intervention required Status in linux package in Ubuntu: Invalid Bug description: ---Problem Description--- During PCIe recovery on Mensa card second port fails recovery. First port recovers, second requires users to recover Physical function. ---Additional Hardware Info--- No additional setup, only PF are defined before inject. No traffic was running. ---uname output--- Linux t249sb1 5.15.0-60-generic #66-Ubuntu SMP Fri Jan 20 14:30:43 UTC 2023 s390x s390x s390x GNU/Linux Machine Type = 3932-AGZ ---Debugger--- A debugger is not configured ---Steps to Reproduce--- Inject error on the PBU attach to the mensa card. miep pbu 1800 etu_txe_eir store 0020_. Will cause AIB Data Bus UE ECC Error. Checking Linux distro, port 0 recover but port 1 is in unusable state. Stack trace output: no Oops output: no System Dump Info: The system is not configured to capture a system dump. *Additional Instructions for Schayne Bellrose/schayne.bellro...@ibm.com: -Post a private note with access information to the machine that the bug is occuring on. -Attach sysctl -a output output to the bug. [ 3135.702386] [ cut here ] [ 3135.702387] refcount_t: underflow; use-after-free. [ 3135.702409] WARNING: CPU: 10 PID: 0 at lib/refcount.c:28 refcount_warn_saturate+0x138/0x210 [ 3135.702416] Modules linked in: binfmt_misc s390_trng chsc_sch vfio_ccw eadm_sch zcrypt_cex4 mdev vfio_iommu_type1 vfio sch_fq_codel drm i2c_core drm_panel_orientation_quirks ip_tables x_tables btrfs blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 linear mlx5_ib ib_uverbs ib_core dm_service_time qeth_l2 bridge stp llc mlx5_core pkey zcrypt crc32_vx_s390 ghash_s390 prng chacha_s390 libchacha aes_s390 des_s390 libdes sha3_512_s390 sha3_256_s390 sha512_s390 sha256_s390 tls sha1_s390 sha_common mlxfw psample zfcp ptp qeth pps_core qdio scsi_transport_fc ccwgroup scsi_dh_emc scsi_dh_rdac scsi_dh_alua dm_multipath [ 3135.702459] CPU: 10 PID: 0 Comm: swapper/10 Not tainted 5.15.0-60-generic #66-Ubuntu [ 3135.702461] Hardware name: IBM 3932 AGZ Z06 (LPAR) [ 3135.702462] Krnl PSW : 0404c0018000 000269ab050c (refcount_warn_saturate+0x13c/0x210) [ 3135.702465]R:0 T:1 IO:0 EX:0 Key:0 M:1 W:0 P:0 AS:3 CC:0 PM:0 RI:0 EA:3 [ 3135.702468] Krnl GPRS: 8001 00070027 0026 00026a835560 [ 3135.702469]0380006fb710 0380006fb708 96b4c180 [ 3135.702470]0001 0401 96b4c200 00026a7c5578 [ 3135.702472]802f6c00 0001 000269ab0508 0380006fb930 [ 3135.702477] Krnl Code: 000269ab04fc: c020003b89f6 larl %r2,00026a2218e8 000269ab0502: c0e50021f267 brasl %r14,000269eee9d0 #000269ab0508: af00 mc 0,0 >000269ab050c: a7f4ffab brc 15,000269ab0462 000269ab0510: c0b00068a834 larl %r11,00026a7c5578 000269ab0516: 43a0b00a ic %r10,10(%r11) 000269ab051a: 42a0f0a7 stc %r10,167(%r15) 000269ab051e: 9501f0a7 cli 167(%r15),1 [ 3135.702488] Call Trace: [ 3135.702489] [<000269ab050c>] refcount_warn_saturate+0x13c/0x210 [ 3135.702492] ([<000269ab0508>] refcount_warn_saturate+0x138/0x210) [ 3135.702494] [<03ff80dd8930>] cmd_ent_put+0xf0/0x100 [mlx5_core] [ 3135.702598] [<03ff80dd9e52>] mlx5_cmd_comp_handler+0x382/0x590 [mlx5_core] [ 3135.702661] [<03ff80dda092>] cmd_comp_notifier+0x32/0x50 [mlx5_core] [ 3135.702723] [<0002694ea04e>] atomic_notifier_call_chain+0x4e/0x90 [ 3135.702727] [<03ff80de029c>] mlx5_eq_async_int+0x12c/0x320 [mlx5_core] [ 3135.702789] [<0002694ea04e>] atomic_notifier_call_chain+0x4e/0x90 [ 3135.702790] [<03ff80df3c4e>] irq_int_handler+0x2e/0x40 [mlx5_core] [ 3135.702850] [<00026953fb1c>] __handle_irq_event_percpu+0x6c/0x210 [ 3135.702853] [<00026953fcf0>] handle_irq_event_percpu+0x30/0x80 [ 3135.702854] [<000269545d28>] handle_percpu_irq+0x68/0x90 [ 3135.702857]
[Kernel-packages] [Bug 1993563] Re: support for same series backports versioning numbers
This bug is awaiting verification that the linux-realtime/5.15.0-1033.36 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-realtime -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1993563 Title: support for same series backports versioning numbers Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Bug description: packaging support for sameport versioning numbers Allow generating kernel packages, that use backports mechanism within the same series. For example linux-lowlatancy linux-riscv. Those kernels already have customized packaging to achieve the above, this is introducing standard support for this in the main kernels for jammy and kinetic series. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1993563/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1970074] Re: UBSAN: array-index-out-of-bounds in /build/linux-9H675w/linux-5.15.0/drivers/ata/libahci.c:968:41
This bug is awaiting verification that the linux-realtime/5.15.0-1033.36 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-realtime -- 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/1970074 Title: UBSAN: array-index-out-of-bounds in /build/linux-9H675w/linux-5.15.0/drivers/ata/libahci.c:968:41 Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: Fix Released Bug description: Something wrong with ata driver in dmesg found: [1.980693] kernel: [1.980699] kernel: fbcon: Taking over console [1.980703] kernel: UBSAN: array-index-out-of-bounds in /build/linux-9H675w/linux-5.15.0/drivers/ata/libahci.c:968:41 [1.980709] kernel: index 15 is out of range for type 'ahci_em_priv [8]' [1.980713] kernel: CPU: 0 PID: 209 Comm: scsi_eh_8 Not tainted 5.15.0-25-generic #25-Ubuntu [1.980716] kernel: Hardware name: System manufacturer System Product Name/P5Q3, BIOS 110206/11/2010 [1.980718] kernel: Call Trace: [1.980721] kernel: [1.980723] kernel: show_stack+0x52/0x58 [1.980729] kernel: dump_stack_lvl+0x4a/0x5f [1.980734] kernel: dump_stack+0x10/0x12 [1.980736] kernel: ubsan_epilogue+0x9/0x45 [1.980739] kernel: __ubsan_handle_out_of_bounds.cold+0x44/0x49 [1.980742] kernel: ahci_qc_issue+0x166/0x170 [libahci] [1.980748] kernel: ata_qc_issue+0x135/0x240 [1.980752] kernel: ata_exec_internal_sg+0x2c4/0x580 [1.980754] kernel: ? vprintk_default+0x1d/0x20 [1.980759] kernel: ata_exec_internal+0x67/0xa0 [1.980762] kernel: sata_pmp_read+0x8d/0xc0 [1.980765] kernel: sata_pmp_read_gscr+0x3c/0x90 [1.980768] kernel: sata_pmp_attach+0x8b/0x310 [1.980771] kernel: ata_eh_revalidate_and_attach+0x28c/0x4b0 [1.980775] kernel: ata_eh_recover+0x6b6/0xb30 [1.980778] kernel: ? ahci_do_hardreset+0x180/0x180 [libahci] [1.980783] kernel: ? ahci_stop_engine+0xb0/0xb0 [libahci] [1.980787] kernel: ? ahci_do_softreset+0x290/0x290 [libahci] [1.980792] kernel: ? trace_event_raw_event_ata_eh_link_autopsy_qc+0xe0/0xe0 [1.980795] kernel: sata_pmp_eh_recover.isra.0+0x214/0x560 [1.980799] kernel: sata_pmp_error_handler+0x23/0x40 [1.980802] kernel: ahci_error_handler+0x43/0x80 [libahci] [1.980806] kernel: ata_scsi_port_error_handler+0x2b1/0x600 [1.980810] kernel: ata_scsi_error+0x9c/0xd0 [1.980813] kernel: scsi_error_handler+0xa1/0x180 [1.980817] kernel: ? scsi_unjam_host+0x1c0/0x1c0 [1.980820] kernel: kthread+0x12a/0x150 [1.980823] kernel: ? set_kthread_struct+0x50/0x50 [1.980826] kernel: ret_from_fork+0x22/0x30 [1.980831] kernel: ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-25-generic 5.15.0-25.25 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eugene16798 F pulseaudio /dev/snd/pcmC0D0p: eugene16798 F...m pulseaudio /dev/snd/controlC1: eugene16798 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sun Apr 24 05:13:34 2022 HibernationDevice: RESUME=UUID=7e115b53-56a4-444f-bd93-6ad4f15c4a61 InstallationDate: Installed on 2019-04-13 (1106 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.1) IwConfig: lono wireless extensions. enp2s0no wireless extensions. virbr0no wireless extensions. MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE= PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=uk_UA.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.15.0-25-generic root=UUID=d87288b4-dbdd-4448-8088-4ebb6ed6cf33 ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-25-generic N/A linux-backports-modules-5.15.0-25-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to jammy
[Kernel-packages] [Bug 1989944] Re: [22.04/Jammy] Replace SAUCE AMD DP tunneling patch by upstream version
This bug is awaiting verification that the linux-realtime/5.15.0-1033.36 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-realtime -- 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/1989944 Title: [22.04/Jammy] Replace SAUCE AMD DP tunneling patch by upstream version Status in linux package in Ubuntu: Triaged Status in linux source package in Jammy: Fix Released Bug description: [SRU Justification] == Impact == We applied a set of patches early as the upstreaming got delayed. The patch now is in upstream linux. Since it differs somewhat from the patch we carry and in order to get potential security and other updates right, we want to replace the SAUCE patch by its upstream counterpart. == Fix == “UBUNTU: SAUCE: thunderbolt: Add DP out resource when DP tunnel is discovered.” to be replaced by: commit b60e31bf18a7064032dbcb73dcb5b58f8a00a110 linux-next “thunderbolt: Add DP OUT resource when DP tunnel is discovered” == Testcase == Attach external Monitor via Thunderbolt port (AMD GPU) (Reference: bug 1983143) == Regression Potential == Previously working external connections might no longer work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1989944/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1989990] Re: [SRU] Ubuntu 22.04 - NVMe TCP - Host fails to reconnect to target after link down/link up sequence
This bug is awaiting verification that the linux-realtime/5.15.0-1033.36 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-realtime -- 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/1989990 Title: [SRU] Ubuntu 22.04 - NVMe TCP - Host fails to reconnect to target after link down/link up sequence Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Bug description: [Impact] Ubuntu 22.04 host fails to reconnect successfully to the NVMe TCP target after link down event if the number of queues have changed post link down. [Fix] Following upstream patch set helps address the issue. 1. nvmet: Expose max queues to configfs https://git.infradead.org/nvme.git/commit/2c4282742d049e2a5ab874e2b359a2421b9377c2 2. nvme-tcp: Handle number of queue changes https://git.infradead.org/nvme.git/commit/516204e486a19d03962c2757ef49782e6c1cacf4 3. nvme-rdma: Handle number of queue changes https://git.infradead.org/nvme.git/commit/e800278c1dc97518eab1970f8f58a5aad52b0f86 The patch in Point 2 above helps address the failure to reconnect in NVMe TCP scenario. Also, following patch addresses error code parsing issue in the reconnect sequence. nvme-fabrics: parse nvme connect Linux error codes https://git.infradead.org/nvme.git/commit/ec9e96b5230148294c7abcaf3a4c592d3720b62d [Test Plan] 1. Boot into Ubuntu 22.04 kernel without fix. 2. Establish connection to NVMe TCP target. 3. Toggle NIC link and bring link up after 10 seconds. When the NIC link is down, on the target increase the number of queues assigned to the controller. 4. Observe that connection to target is lost and after link comes up, controller from host tries to re-establish connection. 5. With patch, reconnection succeeds with higher number of queues [Where problems could occur] Regression risk is low to medium. [Other Info] Test Kernel Source https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/lp_1989990_nvme_tcp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1989990/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1991951] Re: RCU stalls
This bug is awaiting verification that the linux-realtime/5.15.0-1033.36 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-realtime -- 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/1991951 Title: RCU stalls Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Released Bug description: our RCU Stall Timeouts are different to upstream defaults; with regular one 3x longer; and expedited one 1000x shorter. not sure why. Let's harmonize on 60 & 0, which is 60 for regular ones that are set on most architectures; and upstream default for the expedited ones. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991951/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1997200] Re: Mediatek WLAN RZ616(MT7922) SAR table control
This bug is awaiting verification that the linux-realtime/5.15.0-1033.36 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-realtime -- 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/1997200 Title: Mediatek WLAN RZ616(MT7922) SAR table control Status in HWE Next: In Progress Status in linux package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-firmware source package in Kinetic: Fix Released Status in linux-oem-5.17 source package in Kinetic: Invalid Bug description: [Impact] In order to make sure the amount of RF energy being absorbed by our bodies is safe according to the FCC’s guidelines, products must undergo and pass SAR testing. [Fix] Add ACPI SAR table control to pass the testing. [Test] the unit is 0.5dBm in following: Without the SAR table control: $ sudo cat /sys/kernel/debug/ieee80211/phy0/mt76/txpower_sku | grep -i user CCK (user) :N.AN.AN.AN.A OFDM (user) : 40 40 40 40 40 40 40 40 HT20 (user) : 40 40 40 40 40 40 40 40 HT40 (user) : 40 40 40 40 40 40 40 40 40 VHT20 (user): 40 40 40 40 40 40 40 40 40 40 0 0 VHT40 (user): 40 40 40 40 40 40 40 40 40 40 0 0 VHT80 (user): 40 40 40 40 40 40 40 40 40 40 0 0 VHT160 (user) : 40 40 40 40 40 40 40 40 40 40 0 0 HE26 (user) : 40 40 40 40 40 40 40 40 40 40 40 40 HE52 (user) : 40 40 40 40 40 40 40 40 40 40 40 40 HE106 (user): 40 40 40 40 40 40 40 40 40 40 40 40 HE242 (user): 40 40 40 40 40 40 40 40 40 40 40 40 HE484 (user): 40 40 40 40 40 40 40 40 40 40 40 40 HE996 (user): 40 40 40 40 40 40 40 40 40 40 40 40 HE996x2 (user) : 40 40 40 40 40 40 40 40 40 40 40 40 After enabled SAR table control: $ sudo cat /sys/kernel/debug/ieee80211/phy0/mt76/txpower_sku | grep -i user CCK (user) :N.AN.AN.AN.A OFDM (user) : 26 26 26 26 26 26 26 26 HT20 (user) : 26 26 26 26 26 26 26 26 HT40 (user) : 26 26 26 26 26 26 26 26 26 VHT20 (user): 26 26 26 26 26 26 26 26 26 26 0 0 VHT40 (user): 26 26 26 26 26 26 26 26 26 26 0 0 VHT80 (user): 26 26 26 26 26 26 26 26 26 26 0 0 VHT160 (user) : 26 26 26 26 26 26 26 26 26 26 0 0 HE26 (user) : 26 26 26 26 26 26 26 26 26 26 26 26 HE52 (user) : 26 26 26 26 26 26 26 26 26 26 26 26 HE106 (user): 26 26 26 26 26 26 26 26 26 26 26 26 HE242 (user): 26 26 26 26 26 26 26 26 26 26 26 26 HE484 (user): 26 26 26 26 26 26 26 26 26 26 26 26 HE996 (user): 26 26 26 26 26 26 26 26 26 26 26 26 HE996x2 (user) : 26 26 26 26 26 26 26 26 26 26 26 26 Also done stress test with iperf, all works fine. [Where problems could occur] It may break mt7922 driver.
[Kernel-packages] [Bug 1998106] Re: Fix AMD-PState driver for Genoa CPU
This bug is awaiting verification that the linux-realtime/5.15.0-1033.36 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-realtime -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1998106 Title: Fix AMD-PState driver for Genoa CPU Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-5.14 source package in Kinetic: Invalid Status in linux-oem-5.17 source package in Kinetic: Invalid Bug description: [Impact] During AMD Genoa development, the datacenter team identified performance regressions that were root caused in the amd-pstate driver. A first round of fixes already landed upstream (v6.1-rc7) in the amd-pstate driver, and should be backported to all the affected kernels. [Fix] Backport the upstream amd-pstate fixes: https://lore.kernel.org/linux- pm/20221117073541.3350600-1-perry.y...@amd.com/T/#m4616d857ca472937d1e1d31131ddc3261fa17b2a [Regression potential] Clean cherry-picks of already upstream (v6.1-rc7) fixes, impact a single driver (amd-pstate) and the new mode (passive) is disabled by default. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998106/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998115] Re: Fix iosm: WWAN cannot build the connection (DW5823e)
This bug is awaiting verification that the linux-realtime/5.15.0-1033.36 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-realtime -- 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/1998115 Title: Fix iosm: WWAN cannot build the connection (DW5823e) Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: [Impact] WWAN(DW5823e) can't build the connection successfully. [Fix] With INTEL_IOMMU disable config or by forcing intel_iommu=off from grub some of the features of IOSM driver like browsing, flashing & coredump collection is not working. When driver calls DMA API - dma_map_single() for tx transfers. It is resulting in dma mapping error. Set the device DMA addressing capabilities using dma_set_mask() and remove the INTEL_IOMMU dependency in kconfig so that driver follows the platform config either INTEL_IOMMU enable or disable. Because the generic jammy(5.15) doesn't contain NET_DEVLINK and RELAY CONFIGs yet on iosm module, the single patch is necessary for Jammy. [Test Case] 1. boot up with kernel applied the FIX. 2. check the status of wwan by "mmcli -m 0" Status| unlock retries: sim-pin (3) | state: ^[32mconnected^[0m |power state: on |access tech: lte | signal quality: 45% (recent) -- 3GPP | imei: ## | enabled locks: sim, fixed-dialing |operator id: 46692 | operator name: Chunghwa Telecom | registration: home | packet service state: attached |pco: | 0: (complete) [Where problems could occur] remove the dependency for intel_iommu, iosm would fit better on other platforms not only Intel. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1998115/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998883] Re: Micron NVME storage failure [1344, 5407]
This bug is awaiting verification that the linux-realtime/5.15.0-1033.36 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-realtime -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1998883 Title: Micron NVME storage failure [1344,5407] Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-5.17 source package in Kinetic: Invalid Bug description: [Impact] Micron NVME storage fails to init with below error messages [ 8.965698] nvme nvme1: Duplicate cntlid 0 with nvme0, subsys nqn.2014-08.org.nvmexpress:uuid:834ae34b-0ef0-8a48-ac5a-3006545c2b7f, rejecting [ 8.966111] nvme nvme1: Removing after probe failure status: -22 [Fix] The patch from v5.19 add a quirk for Micron NVME fixes this issue 41f38043f884 nvme: add a bogus subsystem NQN quirk for Micron MTFDKBA2T0TFH [Test] Verified with 5.17 OEM kernel on the reported machine. Didn't verify with 5.15 Jammy kernel, but confirmed the kernel could be compiled. [Where problems could occur] The impact should be low as it adds one device ID into a quirk. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1998883/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1999528] Re: [DEP-8] Run ADT regression suite for lowlatency kernels Jammy and later
This bug is awaiting verification that the linux-realtime/5.15.0-1033.36 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-realtime -- 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/1999528 Title: [DEP-8] Run ADT regression suite for lowlatency kernels Jammy and later Status in linux package in Ubuntu: Fix Committed Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Bug description: [SRU Justification] == Impact == Since we split the lowlatency kernel into its own source package the check in the regression test suite is missing a case and will not run, even though the kernel can be booted in a VM instance. == Fix == Add the missing case to the test script which is used by ADT testing. The test scripts are inherited from the primary/distro kernel. The fix should be made there instead of changing the lowlatency tree. == Test == Inspecting the ADT logs we should start to see tests executed instead of: autopkgtest [19:22:21]: test ubuntu-regression-suite: [- ubuntu-regression-suite is pointless, if one cannot boot the kernel == Regression Potential == There are a couple of flaky tests which will start to show up, rather than only successful runs (which should have been a suspicious thing). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1999528/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2002812] Re: Revoke & rotate to new signing key
This bug is awaiting verification that the linux-realtime/5.15.0-1033.36 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-realtime -- 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/2002812 Title: Revoke & rotate to new signing key Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Bug description: [ Impact ] * Revoke & rotate to new signing key * Update revocations, which match the next Ubuntu shim 15.7 revocations. Specifically - revoke certs that were previously protected with by-hash revocations, revoke lost/unused certificates. * Start using advantage2021v1 and ubuntu2022v1 signing keys. * This is a routine key rotation. [ Test Plan ] * Check that old shim/grub boot this kernel * Check that the upcomming future shim/grub can boot this kernel * Check that these kernels can do signed kexec into itself [ Where problems could occur ] * Kernels with this patch applied should be signed using ubuntu/4 pro/3 core/2 signing streams. [ Other Info ] * TPM PCR values and measurements will change when changing the signing key To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2002812/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008069] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 2008069 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2008069 Title: IO stop running on NVME host when target is down Status in linux package in Ubuntu: Incomplete Bug description: [ Impact ] Tab completion for the nvme command is completely broken in bash. [ Test Plan ] 1. Install nvme-cli package 2. Open terminal 3. type any nvme command and hit tab Tab completion should show entries like "list", "create-ns", etc. [ Where problems could occur ] The patch only changes the tab completion for nvme, but rebuilding nvme-cli can reveal bugs on package upgrade, etc. [ Original report ] Description: When running nvme with multipath enabled, it seems as host does not try to use another path. Steps to reproduce: Step 1: Install Ubuntu 22.04 LTS (ubuntu-22.04-live-server-amd64) on system. Step 2: Install nvme-cli package,currently installed version is nvme version 1.16 Step 3: Run IO on the nvme volume. step 4: Stop the service of the target controller. Expected Behavior: Upon stopping the service, host will try using another path for failed IO. from kernel log: Nov 11 08:58:10 localhost kernel: [88496.416058] sysfs: cannot create duplicate filename '/class/block/nvme0n1' Nov 11 08:58:10 localhost kernel: [88496.416062] CPU: 17 PID: 6358 Comm: kworker/u49:0 Kdump: loaded Tainted: GW 5.15.0-47-generic #51-Ubuntu Nov 11 08:58:10 localhost kernel: [88496.416067] Hardware name: Cisco Systems Inc UCSC-C240-M3S2/UCSC-C240-M3S2, BIOS C240M3.2.0.9a.0.113020152237 11/30/2015 Nov 11 08:58:10 localhost kernel: [88496.416069] Workqueue: nvme-wq nvme_scan_work [nvme_core] Nov 11 08:58:10 localhost kernel: [88496.416089] Call Trace: Nov 11 08:58:10 localhost kernel: [88496.416093] Nov 11 08:58:10 localhost kernel: [88496.416097] show_stack+0x52/0x5c Nov 11 08:58:10 localhost kernel: [88496.416107] dump_stack_lvl+0x4a/0x63 Nov 11 08:58:10 localhost kernel: [88496.416115] dump_stack+0x10/0x16 Nov 11 08:58:10 localhost kernel: [88496.416118] sysfs_warn_dup.cold+0x17/0x2b Nov 11 08:58:10 localhost kernel: [88496.416123] sysfs_do_create_link_sd+0xb7/0xd0 Nov 11 08:58:10 localhost kernel: [88496.416131] sysfs_create_link+0x21/0x40 Nov 11 08:58:10 localhost kernel: [88496.416135] device_add+0x2a3/0x7b0 Nov 11 08:58:10 localhost kernel: [88496.416141] ? dev_set_name+0x53/0x70 Nov 11 08:58:10 localhost kernel: [88496.416147] device_add_disk+0xfb/0x3c0 Nov 11 08:58:10 localhost kernel: [88496.416153] ? nvme_update_ns_info+0x14b/0x390 [nvme_core] Nov 11 08:58:10 localhost kernel: [88496.416162] nvme_alloc_ns+0x1ff/0x400 [nvme_core] Nov 11 08:58:10 localhost kernel: [88496.416172] nvme_validate_or_alloc_ns+0xcc/0x190 [nvme_core] Nov 11 08:58:10 localhost kernel: [88496.416181] nvme_scan_ns_list+0x109/0x390 [nvme_core] Nov 11 08:58:10 localhost kernel: [88496.416191] nvme_scan_work+0xd9/0x250 [nvme_core] Nov 11 08:58:10 localhost kernel: [88496.416200] process_one_work+0x22b/0x3d0 Nov 11 08:58:10 localhost kernel: [88496.416205] worker_thread+0x53/0x420 Nov 11 08:58:10 localhost kernel: [88496.416207] ? process_one_work+0x3d0/0x3d0 Nov 11 08:58:10 localhost kernel: [88496.416210] kthread+0x12a/0x150 Nov 11 08:58:10 localhost kernel: [88496.416214] ? set_kthread_struct+0x50/0x50 Nov 11 08:58:10 localhost kernel: [88496.416218] ret_from_fork+0x22/0x30 Nov 11 08:58:10 localhost kernel: [88496.416225] Nov 11 09:00:06 localhost kernel: [88612.227916] nvme nvme2: starting error recovery Nov 11 09:00:06 localhost kernel: [88612.228115] nvme nvme2: queue 4 socket state 11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008069/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008069] [NEW] IO stop running on NVME host when target is down
Public bug reported: [ Impact ] Tab completion for the nvme command is completely broken in bash. [ Test Plan ] 1. Install nvme-cli package 2. Open terminal 3. type any nvme command and hit tab Tab completion should show entries like "list", "create-ns", etc. [ Where problems could occur ] The patch only changes the tab completion for nvme, but rebuilding nvme- cli can reveal bugs on package upgrade, etc. [ Original report ] Description: When running nvme with multipath enabled, it seems as host does not try to use another path. Steps to reproduce: Step 1: Install Ubuntu 22.04 LTS (ubuntu-22.04-live-server-amd64) on system. Step 2: Install nvme-cli package,currently installed version is nvme version 1.16 Step 3: Run IO on the nvme volume. step 4: Stop the service of the target controller. Expected Behavior: Upon stopping the service, host will try using another path for failed IO. from kernel log: Nov 11 08:58:10 localhost kernel: [88496.416058] sysfs: cannot create duplicate filename '/class/block/nvme0n1' Nov 11 08:58:10 localhost kernel: [88496.416062] CPU: 17 PID: 6358 Comm: kworker/u49:0 Kdump: loaded Tainted: GW 5.15.0-47-generic #51-Ubuntu Nov 11 08:58:10 localhost kernel: [88496.416067] Hardware name: Cisco Systems Inc UCSC-C240-M3S2/UCSC-C240-M3S2, BIOS C240M3.2.0.9a.0.113020152237 11/30/2015 Nov 11 08:58:10 localhost kernel: [88496.416069] Workqueue: nvme-wq nvme_scan_work [nvme_core] Nov 11 08:58:10 localhost kernel: [88496.416089] Call Trace: Nov 11 08:58:10 localhost kernel: [88496.416093] Nov 11 08:58:10 localhost kernel: [88496.416097] show_stack+0x52/0x5c Nov 11 08:58:10 localhost kernel: [88496.416107] dump_stack_lvl+0x4a/0x63 Nov 11 08:58:10 localhost kernel: [88496.416115] dump_stack+0x10/0x16 Nov 11 08:58:10 localhost kernel: [88496.416118] sysfs_warn_dup.cold+0x17/0x2b Nov 11 08:58:10 localhost kernel: [88496.416123] sysfs_do_create_link_sd+0xb7/0xd0 Nov 11 08:58:10 localhost kernel: [88496.416131] sysfs_create_link+0x21/0x40 Nov 11 08:58:10 localhost kernel: [88496.416135] device_add+0x2a3/0x7b0 Nov 11 08:58:10 localhost kernel: [88496.416141] ? dev_set_name+0x53/0x70 Nov 11 08:58:10 localhost kernel: [88496.416147] device_add_disk+0xfb/0x3c0 Nov 11 08:58:10 localhost kernel: [88496.416153] ? nvme_update_ns_info+0x14b/0x390 [nvme_core] Nov 11 08:58:10 localhost kernel: [88496.416162] nvme_alloc_ns+0x1ff/0x400 [nvme_core] Nov 11 08:58:10 localhost kernel: [88496.416172] nvme_validate_or_alloc_ns+0xcc/0x190 [nvme_core] Nov 11 08:58:10 localhost kernel: [88496.416181] nvme_scan_ns_list+0x109/0x390 [nvme_core] Nov 11 08:58:10 localhost kernel: [88496.416191] nvme_scan_work+0xd9/0x250 [nvme_core] Nov 11 08:58:10 localhost kernel: [88496.416200] process_one_work+0x22b/0x3d0 Nov 11 08:58:10 localhost kernel: [88496.416205] worker_thread+0x53/0x420 Nov 11 08:58:10 localhost kernel: [88496.416207] ? process_one_work+0x3d0/0x3d0 Nov 11 08:58:10 localhost kernel: [88496.416210] kthread+0x12a/0x150 Nov 11 08:58:10 localhost kernel: [88496.416214] ? set_kthread_struct+0x50/0x50 Nov 11 08:58:10 localhost kernel: [88496.416218] ret_from_fork+0x22/0x30 Nov 11 08:58:10 localhost kernel: [88496.416225] Nov 11 09:00:06 localhost kernel: [88612.227916] nvme nvme2: starting error recovery Nov 11 09:00:06 localhost kernel: [88612.228115] nvme nvme2: queue 4 socket state 11 ** Affects: linux (Ubuntu) Importance: Undecided 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/2008069 Title: IO stop running on NVME host when target is down Status in linux package in Ubuntu: Incomplete Bug description: [ Impact ] Tab completion for the nvme command is completely broken in bash. [ Test Plan ] 1. Install nvme-cli package 2. Open terminal 3. type any nvme command and hit tab Tab completion should show entries like "list", "create-ns", etc. [ Where problems could occur ] The patch only changes the tab completion for nvme, but rebuilding nvme-cli can reveal bugs on package upgrade, etc. [ Original report ] Description: When running nvme with multipath enabled, it seems as host does not try to use another path. Steps to reproduce: Step 1: Install Ubuntu 22.04 LTS (ubuntu-22.04-live-server-amd64) on system. Step 2: Install nvme-cli package,currently installed version is nvme version 1.16 Step 3: Run IO on the nvme volume. step 4: Stop the service of the target controller. Expected Behavior: Upon stopping the service, host will try using another path for failed IO. from kernel log: Nov 11 08:58:10 localhost kernel: [88496.416058] sysfs: cannot create duplicate filename '/class/block/nvme0n1' Nov 11 08:58:10 localhost kernel: [88496.416062] CPU: 17 PID: 6358 Comm: kworker/u49:0 Kdump: loaded Tainted: GW 5.15.0-47-generic #51-Ubuntu
Re: [Kernel-packages] [Bug 1987829] Re: LG Gram 12gen high CPU use when USB-C/TB is in use
I am running LG Gram 16Z90Q (Intel I5) with PopOS and kernel 6.0.6 and I don't have this issue. Battery lasts half a day, it does not get hot whether plugged in or not. I had stability issues with Ubuntu, although I was running the newest release, not the LTS version and I did not have much time to dig into what is causing it. Then I figured System76 guys are building OS for laptops so maybe they already did the necessary tricks. And I fell in love with their tiling windows manager. The only things that do not work are fingerprint reader and the screen brightness buttons (they work with huge lag). śr., 22 lut 2023 o 01:55 Kai-Heng Feng <1987...@bugs.launchpad.net> napisał(a): > Please give latest mainline kernel a try: > https://kernel.ubuntu.com/~kernel-ppa/mainline/v6.2/amd64/ > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1987829 > > Title: > LG Gram 12gen high CPU use when USB-C/TB is in use > > Status in linux package in Ubuntu: > Confirmed > Status in linux package in Fedora: > New > > Bug description: > LG Gram laptop 17Z90Q with a Core i7-1260P CPU. > > Whenever an external monitor is connected to USB-C/Thunderbolt 4, > average load goes above 3.0 and the machine is getting very hot. > > Output from top -H shows a lot of kworker CPU usage: > > top - 11:45:06 up 33 min, 2 users, load average: 3,30, 3,08, 2,79 > Threads: 1442 total, 2 running, 1440 sleeping, 0 stopped, 0 zombie > %Cpu(s): 0,1 us, 3,7 sy, 0,0 ni, 96,1 id, 0,0 wa, 0,0 hi, 0,1 si, > 0,0 st > MiB Mem : 15684,6 total, 8510,2 free, 2580,8 used, 4593,6 > buff/cache > MiB Swap: 3815,0 total, 3815,0 free, 0,0 used. 11326,9 avail > Mem > > PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ > WCHAN COMMAND > 7766 root 20 0 0 0 0 R 19,8 0,0 0:56.05 > worker_th+ kworker/0:2-events > 196 root 20 0 0 0 0 D 15,8 0,0 1:18.12 > ec_guard kworker/u32:2+USBC000:00-con0 > 10237 root 20 0 0 0 0 I 12,9 0,0 0:26.44 > worker_th+ kworker/0:0-events > 1027 root 20 0 0 0 0 I 6,6 0,0 0:43.30 > worker_th+ kworker/1:3-events > 10971 root 20 0 0 0 0 I 4,0 0,0 0:00.20 > worker_th+ kworker/15:0-events > 175 root 20 0 0 0 0 I 2,3 0,0 0:03.24 > worker_th+ kworker/11:1-events > 2410 root 20 0 0 0 0 I 1,7 0,0 0:05.49 > worker_th+ kworker/9:3-events > > Perf shows a lot of time spent inside > handle_irq_event/acpi_ev_gpe_detect/acpi_hw_gpe_read. > > Additionally, kernel log is getting spammed with these lines every 4 > seconds (but also without any USB-C device attached): > > [ 223.514304] ACPI Error: No handler for Region [XIN1] > (f2ad4f1f) [UserDefinedRegion] (20210730/evregion-130) > [ 223.514323] ACPI Error: Region UserDefinedRegion (ID=143) has no > handler (20210730/exfldio-261) > > [ 223.514337] > Initialized Local Variables for Method [_TMP]: > [ 223.514339] Local0: 21495082Integer > 0034 > > [ 223.514349] No Arguments are initialized for method [_TMP] > > [ 223.514354] ACPI Error: Aborting method > \_SB.PC00.LPCB.LGEC.SEN2._TMP due to previous error (AE_NOT_EXIST) > (20210730/psparse-529) > > ProblemType: Bug > DistroRelease: Ubuntu 22.04 > Package: linux-image-5.15.0-46-generic 5.15.0-46.49 > ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 > Uname: Linux 5.15.0-46-generic x86_64 > ApportVersion: 2.20.11-0ubuntu82.1 > Architecture: amd64 > AudioDevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC0: me 1678 F pulseaudio >/dev/snd/controlC1: me 1678 F pulseaudio > CRDA: N/A > CasperMD5CheckResult: pass > Date: Fri Aug 26 11:57:05 2022 > InstallationDate: Installed on 2022-08-25 (1 days ago) > InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 > (20220809.1) > MachineType: LG Electronics 17Z90Q-G.AA78N > ProcFB: 0 i915drmfb > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic > root=UUID=e2f96916-a67c-432e-b687-730071271216 ro quiet splash vt.handoff=7 > PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No > PulseAudio daemon running, or not running as session daemon. > RelatedPackageVersions: >linux-restricted-modules-5.15.0-46-generic N/A >linux-backports-modules-5.15.0-46-generic N/A >linux-firmware > 20220329.git681281e4-0ubuntu3.4 > SourcePackage: linux > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 07/06/2022 > dmi.bios.release: 0.1 > dmi.bios.vendor: Phoenix Technologies Ltd. > dmi.bios.version: A1ZG0380 X64 > dmi.board.asset.tag: Base Board Asset Tag > dmi.board.name:
[Kernel-packages] [Bug 2007668] Re: Intel 12th gen: Noisy screen corruption during some cursor movement in 5.19 kernels
** Summary changed: - Noisy screen corruption during some cursor movement + Intel 12th gen: Noisy screen corruption during some cursor movement in 5.19 kernels ** Tags added: regression-release ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** 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/2007668 Title: Intel 12th gen: Noisy screen corruption during some cursor movement in 5.19 kernels Status in linux package in Ubuntu: Confirmed Bug description: This always happens when the cursor sweeps over a height range (approximately 960px ~ 990px from the top). Even when watching a video, the top of the screen sometimes glitches. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Feb 17 16:24:32 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Device [8086:46aa] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0b14] InstallationDate: Installed on 2022-08-13 (187 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Dell Inc. XPS 9315 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-32-generic root=UUID=3ba28059-7aea-46a5-bf4e-44dd0203b83d ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/04/2023 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.1 dmi.board.name: 02GGG1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.1:bd01/04/2023:br1.7:svnDellInc.:pnXPS9315:pvr:rvnDellInc.:rn02GGG1:rvrA00:cvnDellInc.:ct10:cvr:sku0B14: dmi.product.family: XPS dmi.product.name: XPS 9315 dmi.product.sku: 0B14 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007668/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007798] Re: [Inspiron 7590, Realtek ALC3254, Speaker, Internal] fails after a while
** Tags added: sru-20230130 -- 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/2007798 Title: [Inspiron 7590, Realtek ALC3254, Speaker, Internal] fails after a while Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Confirmed Bug description: == SRU Justification == [Impact] Audio playback becomes silent on some Intel SoF systems. [Fix] Revert offending commit. [Test] The speaker can always play sound after the commit gets reverted. [Where problems could occur] Audio on linux 5.15 has been working fine without the patch for a long time, so this only restore it to where it was. == Original Bug Report == [Summary] During the kernel SRU testing on focal-hwe, I found the audio output of some machines are broken. I've tested some of machine on Jammy using same kernel(5.15.0-66-generic) and haven't seen this happened. The volume bars in settings react to what sound is played correctly and device is detected as well. [Reproduce steps] 1. install focal 2. enable -proposed 3. run apt dist-upgrade. 4. reboot. 5. press fn keys to volume up then volume down or play a short youtube video. 6. after a while can't hear any sound from the speaker. [Failure rate] 10/10 [Additional info] If I run "sudo alsa force-reload" can make audio work again, but after a while it breaks again. These are machines that impacted by this bug: https://certification.canonical.com/hardware/202007-28045/ https://certification.canonical.com/hardware/201906-27109/ https://certification.canonical.com/hardware/201903-26881/ https://certification.canonical.com/hardware/202007-28047/ https://certification.canonical.com/hardware/202007-28055/ https://certification.canonical.com/hardware/202005-27899/ ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.15.0-66.73~20.04.1-generic 5.15.85 Uname: Linux 5.15.0-66-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1303 F pulseaudio CasperMD5CheckResult: skip Date: Sun Feb 19 21:24:59 2023 InstallationDate: Installed on 2020-08-03 (930 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_Card: Cannon Lake PCH cAVS - sof-hda-dsp Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: Feb 19 20:53:23 dell-inspiron-7591-nebula-n15a-c2-201903-26881 dbus-daemon[985]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.34' (uid=1000 pid=1303 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") Symptom_Type: Sound works for a while, then breaks Title: [Inspiron 7590, Realtek ALC3254, Speaker, Internal] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/06/2019 dmi.bios.release: 1.5 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd11/06/2019:br1.5:svnDellInc.:pnInspiron7590:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0922: dmi.product.family: Inspiron dmi.product.name: Inspiron 7590 dmi.product.sku: 0922 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007798/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008053] Re: Screen corruption and laggy mouse cursor in lower quarter of screen
*** This bug is a duplicate of bug 2007668 *** https://bugs.launchpad.net/bugs/2007668 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 2007668, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** This bug has been marked a duplicate of bug 2007668 Intel 12th gen: Noisy screen corruption during some cursor movement in 5.19 kernels -- 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/2008053 Title: Screen corruption and laggy mouse cursor in lower quarter of screen Status in linux package in Ubuntu: New Bug description: After a software upgrade yesterday, I see screen glitches and a "stumbling" mouse cursor whenever I move the mouse in the lower quarter of my laptop screen. When I have connected an external display, the external display doesn't show any issues, but the problem remains on the laptop screen. (This is my first bug report and I used the "ubuntu-bug" utility to collect the necessary data. I hope it is attached here somewhere.) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Feb 22 08:58:07 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.38, 5.15.0-58-generic, x86_64: installed virtualbox/6.1.38, 5.15.0-60-generic, x86_64: installed virtualbox/6.1.38, 5.19.0-32-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:46a8] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0b04] InstallationDate: Installed on 2022-11-30 (83 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Dell Inc. Latitude 5430 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-32-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/05/2022 dmi.bios.release: 1.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.1 dmi.board.name: 04X33N dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.1:bd09/05/2022:br1.6:svnDellInc.:pnLatitude5430:pvr:rvnDellInc.:rn04X33N:rvrA00:cvnDellInc.:ct10:cvr:sku0B04: dmi.product.family: Latitude dmi.product.name: Latitude 5430 dmi.product.sku: 0B04 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.5-0ubuntu0.1~22.04.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008053/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008053] [NEW] Screen corruption and laggy mouse cursor in lower quarter of screen
You have been subscribed to a public bug: After a software upgrade yesterday, I see screen glitches and a "stumbling" mouse cursor whenever I move the mouse in the lower quarter of my laptop screen. When I have connected an external display, the external display doesn't show any issues, but the problem remains on the laptop screen. (This is my first bug report and I used the "ubuntu-bug" utility to collect the necessary data. I hope it is attached here somewhere.) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Feb 22 08:58:07 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.38, 5.15.0-58-generic, x86_64: installed virtualbox/6.1.38, 5.15.0-60-generic, x86_64: installed virtualbox/6.1.38, 5.19.0-32-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:46a8] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0b04] InstallationDate: Installed on 2022-11-30 (83 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Dell Inc. Latitude 5430 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-32-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/05/2022 dmi.bios.release: 1.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.1 dmi.board.name: 04X33N dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.1:bd09/05/2022:br1.6:svnDellInc.:pnLatitude5430:pvr:rvnDellInc.:rn04X33N:rvrA00:cvnDellInc.:ct10:cvr:sku0B04: dmi.product.family: Latitude dmi.product.name: Latitude 5430 dmi.product.sku: 0B04 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.5-0ubuntu0.1~22.04.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug corruption jammy ubuntu wayland-session -- Screen corruption and laggy mouse cursor in lower quarter of screen https://bugs.launchpad.net/bugs/2008053 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007308] Re: linux-tools-common: bpftool wrapper causes build failure for xdp-tools
The attachment "xdp-tools_1.3.0-2ubuntu1.patch" seems to be a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.] ** Tags added: patch -- 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/2007308 Title: linux-tools-common: bpftool wrapper causes build failure for xdp-tools Status in launchpad-buildd: New Status in linux package in Ubuntu: Confirmed Status in xdp-tools package in Ubuntu: New Bug description: The linux-tools-common package appears to provide a shell script with a wrapper that will execute the actual bpftool binary located in a location like /usr/lib/linux-tools/6.1.0-14-generic/bpftool This causes problems for Lunar builds of xdp-tools on Launchpad [0] because there we appear to be running the build in a lunar container on host with a 5.4.0 kernel. Even if we were to install the linux-tools-6.1.0-14 package directly to get the real bpftool binary, the provided wrapper would be unhelpful. 0: https://launchpad.net/ubuntu/+source/xdp-tools/1.3.0-2 For completeness/process I collected artifacts below from a Lunar LXD container running on a Focal host with a 5.4.0 kernel. --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.24.0-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 23.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux-tools-common 6.1.0-14.14 PackageArchitecture: all PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-139-generic root=UUID=d7e84875-6ab0-4d9a-bd8c-8e452fa45621 ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 5.4.0-139.156-generic 5.4.224 RelatedPackageVersions: linux-restricted-modules-5.4.0-139-generic N/A linux-backports-modules-5.4.0-139-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: lunar uec-images package-from-proposed Uname: Linux 5.4.0-139-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-02-14 (0 days ago) UserGroups: N/A WifiSyslog: Feb 14 19:24:18 kind-flea udevadm[83]: kernel: Failed to write 'add' to '/sys/module/kernel/uevent': Permission denied _MarkForUpload: True acpidump: dmi.bios.date: 02/06/2015 dmi.bios.vendor: EFI Development Kit II / OVMF dmi.bios.version: 0.0.0 dmi.board.name: LXD dmi.board.vendor: Canonical Ltd. dmi.board.version: pc-q35-7.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-7.1 dmi.modalias: dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-7.1:rvnCanonicalLtd.:rnLXD:rvrpc-q35-7.1:cvnQEMU:ct1:cvrpc-q35-7.1: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-7.1 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad-buildd/+bug/2007308/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007718] Re: HWE-22.04 Kernel 5.19 breaks suspend/wake on newer AMD Ryzen 6000u
I can confirm this regression on LG Gram 17 with Intel CPU -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2007718 Title: HWE-22.04 Kernel 5.19 breaks suspend/wake on newer AMD Ryzen 6000u Status in linux-meta-hwe-5.19 package in Ubuntu: New Bug description: After 22.04 LTS upgraded the linux-generic-hwe kernel to 5.19.0.32 (from 5.15.0.60) suspend/wake up is broken on my laptop. The system refuses to wake up in about 50% of the cases, seemingly random. The only "solution" is a forced system power down. Reverting back to 5.15.0.60 resolves this issue immediately. I suspect some patch was not re-applied to 5.19, since there are many postings on Reddit (for instance) about sleep problems with newer AMD CPUs, but 5.15 was running beautifully. My machine is a Lenovo Thinkpad T14s AMD Gen 3, AMD 6850u CPU. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-5.19/+bug/2007718/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1987430] Re: Ubuntu 22.04 kernel 5.15.0-46-generic leaks kernel memory in kmalloc-2k slabs
hi Matthew, I did some investigation in 5.15.0-66-generic, lsm_multiple_contexts()return 0 that make audit_log_lsm() return without malloc memory thus avoiding memory leaks. audit_log_lsm() ->if (!lsm_multiple_contexts()) return; I haven't found out which commit change the behavior of lsm_multiple_contexts(). Jianlin -- 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/1987430 Title: Ubuntu 22.04 kernel 5.15.0-46-generic leaks kernel memory in kmalloc-2k slabs Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: In Progress Status in linux source package in Kinetic: In Progress Bug description: Since updating to kernel 5.15.0-46-generic (package version 5.15.0-46.49), all of our Ubuntu 22.04 LTS servers are leaking kernel memory; our first server with 8 GB of RAM just fatally OOMed, causing us to detect this. Inspection of OOM reports, /proc/meminfo, and /proc/slabinfo says that it's mostly going to unreclaimable kmalloc-2k slabs: Aug 23 12:51:11 cluster kernel: [361299.864757] Unreclaimable slab info: Aug 23 12:51:11 cluster kernel: [361299.864757] Name Used Total [...] Aug 23 12:51:11 cluster kernel: [361299.864924] kmalloc-2k 6676584KB6676596KB Most of our machines appear to be leaking slab memory at a rate of around 20 to 40 Mbytes/hour, with some machines leaking much faster; the champions are leaking kernel memory at 145 Mbytes/hour and 237 Mbytes/hour. We aren't running any proprietary kernel modules and our only unusual kernel configuration is that we've disabled AppArmor with 'apparmor=0' on the kernel command line. /proc/version_signature: Ubuntu 5.15.0-46.49-generic 5.15.39 Full kernel command line from the Dell R240 system that fatally OOMd: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=3165564f-a2dd-4b39-935b-114f3e23ff54 ro console=ttyS0,115200 console=tty0 apparmor=0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987430/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007308] Re: linux-tools-common: bpftool wrapper causes build failure for xdp-tools
** Patch added: "xdp-tools_1.3.0-2ubuntu1.patch" https://bugs.launchpad.net/ubuntu/+source/xdp-tools/+bug/2007308/+attachment/5649048/+files/xdp-tools_1.3.0-2ubuntu1.patch -- 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/2007308 Title: linux-tools-common: bpftool wrapper causes build failure for xdp-tools Status in launchpad-buildd: New Status in linux package in Ubuntu: Confirmed Status in xdp-tools package in Ubuntu: New Bug description: The linux-tools-common package appears to provide a shell script with a wrapper that will execute the actual bpftool binary located in a location like /usr/lib/linux-tools/6.1.0-14-generic/bpftool This causes problems for Lunar builds of xdp-tools on Launchpad [0] because there we appear to be running the build in a lunar container on host with a 5.4.0 kernel. Even if we were to install the linux-tools-6.1.0-14 package directly to get the real bpftool binary, the provided wrapper would be unhelpful. 0: https://launchpad.net/ubuntu/+source/xdp-tools/1.3.0-2 For completeness/process I collected artifacts below from a Lunar LXD container running on a Focal host with a 5.4.0 kernel. --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.24.0-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 23.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux-tools-common 6.1.0-14.14 PackageArchitecture: all PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-139-generic root=UUID=d7e84875-6ab0-4d9a-bd8c-8e452fa45621 ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 5.4.0-139.156-generic 5.4.224 RelatedPackageVersions: linux-restricted-modules-5.4.0-139-generic N/A linux-backports-modules-5.4.0-139-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: lunar uec-images package-from-proposed Uname: Linux 5.4.0-139-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-02-14 (0 days ago) UserGroups: N/A WifiSyslog: Feb 14 19:24:18 kind-flea udevadm[83]: kernel: Failed to write 'add' to '/sys/module/kernel/uevent': Permission denied _MarkForUpload: True acpidump: dmi.bios.date: 02/06/2015 dmi.bios.vendor: EFI Development Kit II / OVMF dmi.bios.version: 0.0.0 dmi.board.name: LXD dmi.board.vendor: Canonical Ltd. dmi.board.version: pc-q35-7.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-7.1 dmi.modalias: dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-7.1:rvnCanonicalLtd.:rnLXD:rvrpc-q35-7.1:cvnQEMU:ct1:cvrpc-q35-7.1: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-7.1 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad-buildd/+bug/2007308/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
