[Kernel-packages] [Bug 1961338] Re: Disable unprivileged BPF by default
This bug is awaiting verification that the linux-xilinx- zynqmp/5.4.0-1018.21 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification- done-focal'. If the problem still exists, change the tag 'verification- needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- 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/1961338 Title: Disable unprivileged BPF by default Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Bug description: [Impact] Unprivileged users have access to BPF, allowing them to execute code in the kernel under their control. Though restricted and verified, a lot of security issues have been uncovered over the years, indicating that it should be disabled by default in order to protect our users. Admins can reenable that access or give CAP_BPF to programs if needed. [Test case] A qa-regression-testing testcase has been added that checks for the ability to load BPF programs under different circumstances. [Potential regression] Users who rely on unprivileged BPF access will need to change the setting or give CAP_BPF to their programs. Also, sysctl and bpf code might be affected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1961338/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1982093] Re: Screen/display issue
[Expired for linux-oem-5.17 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux-oem-5.17 (Ubuntu) Status: Incomplete => Expired -- 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/1982093 Title: Screen/display issue Status in linux-oem-5.17 package in Ubuntu: Expired Bug description: After updates my laptop screen goes psychedelic when my cursor is near the bottom of my screen. I have a video of it but can't upload it. It happened first in Montreal when support updated my kernel, so they put me back on the previous kernel and it fixed it. But I did updates yesterday and since restarting it's happened again ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.17.0-1013-oem 5.17.0-1013.14 ProcVersionSignature: Ubuntu 5.17.0-1013.14-oem 5.17.15 Uname: Linux 5.17.0-1013-oem x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Jul 19 09:23:52 2022 InstallationDate: Installed on 2022-07-03 (15 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-oem-5.17 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: claire 2352 F pulseaudio /dev/snd/pcmC0D0p: claire 2352 F...m pulseaudio /dev/snd/pcmC0D6c: claire 2352 F...m pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-07-03 (15 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 21CBCTO1WW Package: linux-signed-oem-5.17 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.17.0-1013-oem root=UUID=d4f57971-5311-4b4a-aab5-ee87020fbbfe ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.17.0-1013.14-oem 5.17.15 RelatedPackageVersions: linux-restricted-modules-5.17.0-1013-oem N/A linux-backports-modules-5.17.0-1013-oem N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 Tags: jammy wayland-session Uname: Linux 5.17.0-1013-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/31/2022 dmi.bios.release: 1.25 dmi.bios.vendor: LENOVO dmi.bios.version: N3AET60W (1.25 ) dmi.board.asset.tag: Not Available dmi.board.name: 21CBCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0T76461 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrN3AET60W(1.25):bd05/31/2022:br1.25:efr1.13:svnLENOVO:pn21CBCTO1WW:pvrThinkPadX1CarbonGen10:rvnLENOVO:rn21CBCTO1WW:rvrSDK0T76461WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CB_BU_Think_FM_ThinkPadX1CarbonGen10: dmi.product.family: ThinkPad X1 Carbon Gen 10 dmi.product.name: 21CBCTO1WW dmi.product.sku: LENOVO_MT_21CB_BU_Think_FM_ThinkPad X1 Carbon Gen 10 dmi.product.version: ThinkPad X1 Carbon Gen 10 dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: claire 2352 F pulseaudio /dev/snd/pcmC1D0c: claire 2352 F...m pulseaudio /dev/snd/controlC0: claire 2352 F pulseaudio /dev/snd/pcmC0D0p: claire 2352 F...m pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-07-03 (15 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 21CBCTO1WW Package: linux-signed-oem-5.17 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.17.0-1013-oem root=UUID=d4f57971-5311-4b4a-aab5-ee87020fbbfe ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.17.0-1013.14-oem 5.17.15 RelatedPackageVersions: linux-restricted-modules-5.17.0-1013-oem N/A linux-backports-modules-5.17.0-1013-oem N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 Tags: jammy wayland-session Uname:
[Kernel-packages] [Bug 1982650] Re: screen flickering
[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/1982650 Title: screen flickering Status in linux package in Ubuntu: Expired Bug description: [Sat Jul 23 11:32:16 2022] i915 :00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun [Sat Jul 23 11:33:39 2022] i915 :00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-39-generic 5.15.0-39.42 ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35 Uname: Linux 5.15.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hari 1074 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Jul 23 11:44:21 2022 InstallationDate: Installed on 2021-02-24 (513 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Dell Inc. Inspiron 5559 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-39-generic root=UUID=e2bb84ca-dd6e-40ec-8b37-00f696fb958e ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-39-generic N/A linux-backports-modules-5.15.0-39-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-25 (89 days ago) dmi.bios.date: 09/07/2020 dmi.bios.release: 1.9 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.9.0 dmi.board.name: 04D1V1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.9.0:bd09/07/2020:br1.9:svnDellInc.:pnInspiron5559:pvr:rvnDellInc.:rn04D1V1:rvrA00:cvnDellInc.:ct10:cvr:sku06B2: dmi.product.family: Inspiron dmi.product.name: Inspiron 5559 dmi.product.sku: 06B2 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1982650/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1981390] Re: Mass Storage Gadget driver truncates device >2TB
** Tags added: verification-done-jammy
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1981390
Title:
Mass Storage Gadget driver truncates device >2TB
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Fix Released
Bug description:
[Impact]
I tried to use f_mass_storage to expose a 16TB hard drive attached to
Raspberry Pi to another computer.
On the remote computer the recognised drive has incorrect capacity and the
data is truncated.
After some debugging I noted the problem is caused by a bug in the
read capacity function of f_mass_storage in kernel version prior to
5.15, which had already been fixed upstream in mainline kernel since
v5.16
https://lore.kernel.org/all/20210914052728.23369-1-nikita.yo...@cogentembedded.com/
I tried the kernel from https://github.com/raspberrypi/linux version
rpi-5.16.y and confirmed that the problem is fixed at v5.16.
I wonder if the fix can be backported to the Ubuntu kernel.
Thank you very much!
Current kernel package version: linux-raspi (5.15.0-1011.13) jammy
Hardware: Raspberry Pi 4B
[Fix]
Backport commit bedbac5f66bf ("usb: gadget: storage: add support for
media larger than 2T")
[Test case]
See above.
[Where problems could occur]
Modifications are limited to the USB gadget mass storage driver, so
problems should only be seen on a client that uses this driver to
expose a USB drive to an attached USB host.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1981390/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-aws/5.15.0.1021.21)
All autopkgtests for the newly accepted linux-meta-aws (5.15.0.1021.21) for jammy have finished running. The following regressions have been reported in tests triggered by the package: lttng-modules/2.13.1-1ubuntu0.22.04.1 (arm64, amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#linux-meta-aws [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing 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 1961338] Re: Disable unprivileged BPF by default
This bug is awaiting verification that the linux-xilinx- zynqmp/5.4.0-1018.21 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification- done-focal'. If the problem still exists, change the tag 'verification- needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- 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/1961338 Title: Disable unprivileged BPF by default Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Bug description: [Impact] Unprivileged users have access to BPF, allowing them to execute code in the kernel under their control. Though restricted and verified, a lot of security issues have been uncovered over the years, indicating that it should be disabled by default in order to protect our users. Admins can reenable that access or give CAP_BPF to programs if needed. [Test case] A qa-regression-testing testcase has been added that checks for the ability to load BPF programs under different circumstances. [Potential regression] Users who rely on unprivileged BPF access will need to change the setting or give CAP_BPF to their programs. Also, sysctl and bpf code might be affected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1961338/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1981433] Re: [Asus Zenbook UX3402ZA] Sound doesn't work at all
Was audio working previously on this hardware and then stopped after a kernel (or other package) update? If so, we can try bisecting. Note also that the 5.15.0-41.44 kernel has been out for a while now. The most recent kernel is 5.15.0-48.54 so maybe that is worth trying 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/1981433 Title: [Asus Zenbook UX3402ZA] Sound doesn't work at all Status in linux 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/ubuntu/+source/linux/+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 1786013] Autopkgtest regression report (linux-meta-kvm/5.4.0.1076.73)
All autopkgtests for the newly accepted linux-meta-kvm (5.4.0.1076.73) for focal have finished running. The following regressions have been reported in tests triggered by the package: sl-modem/2.9.11~20110321-16ubuntu1 (amd64) evdi/1.9.1-1ubuntu4~20.04.2 (amd64) v4l2loopback/0.12.3-1ubuntu0.4 (amd64) dahdi-linux/1:2.11.1~dfsg-1ubuntu6.3 (amd64) virtualbox/6.1.38-dfsg-3~ubuntu1.20.04.1 (amd64) rtl8821ce/5.5.2.1-0ubuntu4~20.04.5 (amd64) oss4/4.2-build2010-5ubuntu6~20.04.3 (amd64) rtl8812au/4.3.8.12175.20140902+dfsg-0ubuntu13~20.04.4 (amd64) lttng-modules/2.12.5-1ubuntu2~20.04.3 (amd64) glibc/2.31-0ubuntu9.9 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-meta-kvm [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 1990700] 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 1990700 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/1990700 Title: Fibocom WWAN FM350-GL suspend error (notebook not suspend) Status in linux package in Ubuntu: Incomplete Bug description: Hi, I found a "little" problem with Fibocom WWAN FM350-GL 5G modem in module mtk_t7xx . Power management for this modem is bad. When the notebook goes to sleep/suspend, kernel module mtk_t7xx return an error: mtk_t7xx :58:00.0: [PM] SAP suspend error: -110 mtk_t7xx :58:00.0: PM: pci_pm_suspend(): t7xx_pci_pm_suspend+0x0/0x20 [mtk_t7xx] returns -110 mtk_t7xx :58:00.0: PM: dpm_run_callback(): pci_pm_suspend+0x0/0x1a0 returns -110 mtk_t7xx :58:00.0: PM: failed to suspend async: error -110 So power management failed to suspend: PM: Some devices failed to suspend, or early wake event detected And the notebook not suspend and wake up again. It must be this module, because if I remove the module first (modprobe -r), the laptop goes to sleep and wakes up normally. However, after reinserting the module, the modem no longer appears in the system. Expected state: sleep occurs when the device is put to sleep - including the modem. When you wake up, you will wake up, including activating the modem and logging into the operator's network. Description:Ubuntu 20.04.5 LTS Release:20.04 lspci -v: 58:00.0 Wireless controller [0d40]: MEDIATEK Corp. Device 4d75 (rev 01) Subsystem: Device 1cf8:3500 Flags: bus master, fast devsel, latency 0, IRQ 17 Memory at 601e80 (64-bit, prefetchable) [size=32K] Memory at 5e80 (64-bit, non-prefetchable) [size=8M] Memory at 601e00 (64-bit, prefetchable) [size=8M] Capabilities: [80] Express Endpoint, MSI 00 Capabilities: [d0] MSI-X: Enable+ Count=34 Masked- Capabilities: [e0] MSI: Enable- Count=1/32 Maskable+ 64bit+ Capabilities: [f8] Power Management version 3 Capabilities: [100] Vendor Specific Information: ID=1556 Rev=1 Len=008 Capabilities: [108] Latency Tolerance Reporting Capabilities: [110] L1 PM Substates Capabilities: [200] Advanced Error Reporting Capabilities: [300] Secondary PCI Express Kernel driver in use: mtk_t7xx Kernel modules: mtk_t7xx lshw: *-generic description: Wireless controller product: MEDIATEK Corp. vendor: MEDIATEK Corp. physical id: 0 bus info: pci@:58:00.0 version: 01 width: 64 bits clock: 33MHz capabilities: pciexpress msix msi pm bus_master cap_list configuration: driver=mtk_t7xx latency=0 resources: iomemory:600-5ff iomemory:600-5ff irq:17 memory:601e80-601e807fff memory:5e80-5eff memory:601e00-601e7f modinfo: modinfo mtk_t7xx filename: /lib/modules/5.19.10-051910-generic/kernel/drivers/net/wwan/t7xx/mtk_t7xx.ko license:GPL description:MediaTek PCIe 5G WWAN modem T7xx driver author: MediaTek Inc srcversion: 5FA53465EA0167231B632D4 alias: pci:v14C3d4D75sv*sd*bc*sc*i* depends: retpoline: Y intree: Y name: mtk_t7xx vermagic: 5.19.10-051910-generic SMP preempt mod_unload modversions sig_id: PKCS#7 signer: Build time autogenerated kernel key sig_key:7E:38:36:48:BB:F2:74:0E:30:57:1B:6E:64:90:57:55:30:C5:AF:45 sig_hashalgo: sha512 signature: 78:1B:C9:7F:DE:D2:BE:87:EA:17:94:14:C2:51:3E:2C:75:03:76:0F: 36:96:92:9B:88:48:B0:C8:73:E6:88:E4:A2:61:25:E9:16:E8:87:40: 45:99:CC:50:FD:21:B0:BB:11:0E:B5:8F:CC:5F:47:7A:5E:00:BF:7D: 77:50:A1:F5:00:24:DC:EF:E6:3E:A0:3B:0A:D7:2E:84:EC:FC:6B:4D: 9E:42:CD:A2:07:C3:D9:F8:6E:7B:76:12:7F:B9:9B:70:6A:22:3D:09: 4D:04:98:59:35:2A:95:D1:9A:B3:53:77:BE:E5:3E:50:51:18:D0:CE: 9A:DB:3B:0E:DA:4D:05:5D:D1:5F:4F:6B:DB:98:47:F3:32:25:D8:AD: 4E:CE:5F:3E:46:76:D9:F4:FA:28:F2:49:B3:3D:D1:5F:74:CF:69:39:
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-azure/5.4.0.1092.89)
All autopkgtests for the newly accepted linux-meta-azure (5.4.0.1092.89) for focal have finished running. The following regressions have been reported in tests triggered by the package: v4l2loopback/0.12.3-1ubuntu0.4 (amd64) dahdi-linux/1:2.11.1~dfsg-1ubuntu6.3 (amd64) systemd/245.4-4ubuntu3.18 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-meta-azure [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 1990700] [NEW] Fibocom WWAN FM350-GL suspend error (notebook not suspend)
Public bug reported: Hi, I found a "little" problem with Fibocom WWAN FM350-GL 5G modem in module mtk_t7xx . Power management for this modem is bad. When the notebook goes to sleep/suspend, kernel module mtk_t7xx return an error: mtk_t7xx :58:00.0: [PM] SAP suspend error: -110 mtk_t7xx :58:00.0: PM: pci_pm_suspend(): t7xx_pci_pm_suspend+0x0/0x20 [mtk_t7xx] returns -110 mtk_t7xx :58:00.0: PM: dpm_run_callback(): pci_pm_suspend+0x0/0x1a0 returns -110 mtk_t7xx :58:00.0: PM: failed to suspend async: error -110 So power management failed to suspend: PM: Some devices failed to suspend, or early wake event detected And the notebook not suspend and wake up again. It must be this module, because if I remove the module first (modprobe -r), the laptop goes to sleep and wakes up normally. However, after reinserting the module, the modem no longer appears in the system. Expected state: sleep occurs when the device is put to sleep - including the modem. When you wake up, you will wake up, including activating the modem and logging into the operator's network. Description:Ubuntu 20.04.5 LTS Release:20.04 lspci -v: 58:00.0 Wireless controller [0d40]: MEDIATEK Corp. Device 4d75 (rev 01) Subsystem: Device 1cf8:3500 Flags: bus master, fast devsel, latency 0, IRQ 17 Memory at 601e80 (64-bit, prefetchable) [size=32K] Memory at 5e80 (64-bit, non-prefetchable) [size=8M] Memory at 601e00 (64-bit, prefetchable) [size=8M] Capabilities: [80] Express Endpoint, MSI 00 Capabilities: [d0] MSI-X: Enable+ Count=34 Masked- Capabilities: [e0] MSI: Enable- Count=1/32 Maskable+ 64bit+ Capabilities: [f8] Power Management version 3 Capabilities: [100] Vendor Specific Information: ID=1556 Rev=1 Len=008 Capabilities: [108] Latency Tolerance Reporting Capabilities: [110] L1 PM Substates Capabilities: [200] Advanced Error Reporting Capabilities: [300] Secondary PCI Express Kernel driver in use: mtk_t7xx Kernel modules: mtk_t7xx lshw: *-generic description: Wireless controller product: MEDIATEK Corp. vendor: MEDIATEK Corp. physical id: 0 bus info: pci@:58:00.0 version: 01 width: 64 bits clock: 33MHz capabilities: pciexpress msix msi pm bus_master cap_list configuration: driver=mtk_t7xx latency=0 resources: iomemory:600-5ff iomemory:600-5ff irq:17 memory:601e80-601e807fff memory:5e80-5eff memory:601e00-601e7f modinfo: modinfo mtk_t7xx filename: /lib/modules/5.19.10-051910-generic/kernel/drivers/net/wwan/t7xx/mtk_t7xx.ko license:GPL description:MediaTek PCIe 5G WWAN modem T7xx driver author: MediaTek Inc srcversion: 5FA53465EA0167231B632D4 alias: pci:v14C3d4D75sv*sd*bc*sc*i* depends: retpoline: Y intree: Y name: mtk_t7xx vermagic: 5.19.10-051910-generic SMP preempt mod_unload modversions sig_id: PKCS#7 signer: Build time autogenerated kernel key sig_key:7E:38:36:48:BB:F2:74:0E:30:57:1B:6E:64:90:57:55:30:C5:AF:45 sig_hashalgo: sha512 signature: 78:1B:C9:7F:DE:D2:BE:87:EA:17:94:14:C2:51:3E:2C:75:03:76:0F: 36:96:92:9B:88:48:B0:C8:73:E6:88:E4:A2:61:25:E9:16:E8:87:40: 45:99:CC:50:FD:21:B0:BB:11:0E:B5:8F:CC:5F:47:7A:5E:00:BF:7D: 77:50:A1:F5:00:24:DC:EF:E6:3E:A0:3B:0A:D7:2E:84:EC:FC:6B:4D: 9E:42:CD:A2:07:C3:D9:F8:6E:7B:76:12:7F:B9:9B:70:6A:22:3D:09: 4D:04:98:59:35:2A:95:D1:9A:B3:53:77:BE:E5:3E:50:51:18:D0:CE: 9A:DB:3B:0E:DA:4D:05:5D:D1:5F:4F:6B:DB:98:47:F3:32:25:D8:AD: 4E:CE:5F:3E:46:76:D9:F4:FA:28:F2:49:B3:3D:D1:5F:74:CF:69:39: D2:B0:64:3D:41:FB:55:1F:AB:D3:76:65:54:C6:06:6E:F7:01:F2:F7: CE:CF:6C:76:17:1B:AD:41:69:29:FB:F8:6B:F9:74:3F:65:6B:C5:63: 98:76:D1:69:24:AA:7E:9D:D0:27:BF:AF:0B:C9:30:3C:1B:2A:AB:B9: 29:22:D5:6B:16:AB:22:43:16:A0:F6:94:EA:78:E7:54:5F:9B:2D:DA: 2E:9B:9F:81:E4:E0:B7:93:ED:9D:8F:79:19:1A:03:2C:00:C5:3A:99: A4:D0:14:6D:21:61:41:02:EC:8D:48:D5:13:0F:D7:AB:5E:B9:BF:17: FA:F3:8C:DE:62:A3:F1:5C:33:9C:FB:72:2F:BF:9F:BD:35:BC:F6:D4: DE:69:68:A7:80:FE:4C:ED:F8:02:97:66:CA:D0:7A:49:4A:A8:D5:C5: 67:48:31:42:F9:41:FB:1A:74:52:97:6D:28:A0:2B:03:DA:73:BF:27: 0E:84:45:33:40:2D:2F:A9:2C:0D:3A:A5:52:93:1B:E8:6D:27:CD:70: 7E:56:CF:0C:8E:C7:6C:E0:A7:16:2A:FF:95:C5:DE:B7:97:D5:FB:92: 28:EE:C6:98:1B:D7:06:A3:9D:26:31:09:1E:A8:09:D4:CF:0F:6C:4F: C5:EA:2E:BF:5E:02:02:54:15:A7:A7:86:07:B7:82:3B:C6:68:4A:2F:
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-ibm-5.4/5.4.0.1034.48)
All autopkgtests for the newly accepted linux-meta-ibm-5.4 (5.4.0.1034.48) for bionic have finished running. The following regressions have been reported in tests triggered by the package: systemd/237-3ubuntu10.56 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-meta-ibm-5.4 [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 1786013] Autopkgtest regression report (linux-meta-ibm/5.4.0.1034.63)
All autopkgtests for the newly accepted linux-meta-ibm (5.4.0.1034.63) for focal have finished running. The following regressions have been reported in tests triggered by the package: systemd/245.4-4ubuntu3.18 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-meta-ibm [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing 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 1983180]
Model Name: ASUS ZenBook13 UX325J BIOS Version: 311 CPU: Intel Core(TM) i7-10 65G7 CPU @ 1.30GHz GPU: Intel Iris(R) Plus Graphics OS: Ubuntu 22.04.1 LTS (GNU/Linux 5.15.0-48-generic x86_64) / Windows 11 I made 'sudo apt-get dist-upgrade' on 22-Sep-2022, followed by I lost an access to Ubuntu GUI. Everytime I try to login, following error message is shown and only tty access is available. -- Error message -- [ 0.076056] x86/cpu: SGX disabled by BIOS. [ 0.130860] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCIO.I2CO.TPDO], AE_NOT_FOUND (20210730/dswload2-162) [ 0.130868] ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20210730/psobject-220) [ 0.130895] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCIO.I2C1.TPL1], AE_NOT_FOUND (20210730/dswload2-162) [ 0.130898] ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20210730/psobject-220) [ 0.561376] pci :00:07.0: DPC: RP PI0 log size 0 is invalid [ 0.563606] pci :00:07.1: DPC: RP PI0 log size 0 is invalid /dev/nvme0n1p4: clean, 604301/22405120 files, 35951873/89599744 blocks [ 1.862340] mtd device must be supplied (device name is empty) [ 2.167925] mtd device must be supplied (device name is empty) [ 2.369446] mtd device must be supplied (device name is empty) [ 4.033184] ucsi_acpi USBC000:00: PPN init failed (-110) -- 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/1983180 Title: ACPI Error _CPC not found Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: just recently (I guess since the last update) I get a few ACPI error messages during start up. Those are also visible with dmesg: ... [0.713907] ACPI: AC: AC Adapter [AC] (on-line) [0.713978] input: Sleep Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input0 [0.714011] ACPI: button: Sleep Button [SLPB] [0.714040] input: Lid Switch as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input1 [0.714061] ACPI: button: Lid Switch [LID] [0.714087] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input2 [0.714105] ACPI: button: Power Button [PWRF] [0.714187] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330) [0.714199] No Local Variables are initialized for Method [_CPC] [0.714201] No Arguments are initialized for method [_CPC] [0.714203] ACPI Error: Aborting method \_SB.PR01._CPC due to previous error (AE_NOT_FOUND) (20210730/psparse-529) [0.714395] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330) [0.714404] No Local Variables are initialized for Method [_CPC] [0.714405] No Arguments are initialized for method [_CPC] [0.714407] ACPI Error: Aborting method \_SB.PR02._CPC due to previous error (AE_NOT_FOUND) (20210730/psparse-529) [0.714480] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330) [0.714488] No Local Variables are initialized for Method [_CPC] [0.714490] No Arguments are initialized for method [_CPC] [0.714492] ACPI Error: Aborting method \_SB.PR03._CPC due to previous error (AE_NOT_FOUND) (20210730/psparse-529) [0.714640] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330) [0.714651] No Local Variables are initialized for Method [_CPC] [0.714653] No Arguments are initialized for method [_CPC] [0.714655] ACPI Error: Aborting method \_SB.PR04._CPC due to previous error (AE_NOT_FOUND) (20210730/psparse-529) [0.714940] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330) [0.714952] No Local Variables are initialized for Method [_CPC] [0.714953] No Arguments are initialized for method [_CPC] [0.714955] ACPI Error: Aborting method \_SB.PR05._CPC due to previous error (AE_NOT_FOUND) (20210730/psparse-529) [0.715106] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330) [0.715118] No Local Variables are initialized for Method [_CPC] [0.715119] No Arguments are initialized for method [_CPC] [0.715121] ACPI Error: Aborting method \_SB.PR06._CPC due to previous error (AE_NOT_FOUND) (20210730/psparse-529) [0.715309] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330) [0.715321] No Local Variables are initialized for Method [_CPC] [0.715322] No Arguments are initialized for method [_CPC] [0.715324] ACPI Error: Aborting method \_SB.PR07._CPC due to previous error (AE_NOT_FOUND) (20210730/psparse-529) [0.715611] ACPI BIOS Error (bug): Could not resolve symbol
[Kernel-packages] [Bug 1990698] Re: Bionic update: upstream stable patchset 2022-09-23
** Description changed: - - SRU Justification - - Impact: -The upstream process for stable tree updates is quite similar -in scope to the Ubuntu SRU process, e.g., each patch has to -demonstrably fix a bug, and each patch is vetted by upstream -by originating either directly from a mainline/stable Linux tree or -a minimally backported form of that patch. The following upstream -stable patches should be included in the Ubuntu kernel: - -upstream stable patchset 2022-09-23 -from git://git.kernel.org/ + SRU Justification + + Impact: + The upstream process for stable tree updates is quite similar + in scope to the Ubuntu SRU process, e.g., each patch has to + demonstrably fix a bug, and each patch is vetted by upstream + by originating either directly from a mainline/stable Linux tree or + a minimally backported form of that patch. The following upstream + stable patches should be included in the Ubuntu kernel: + + upstream stable patchset 2022-09-23 + + Ported from the following upstream stable releases: + v4.14.291, v4.19.256 + + from git://git.kernel.org/ + + Bluetooth: L2CAP: Fix use-after-free caused by l2cap_chan_put + ntfs: fix use-after-free in ntfs_ucsncmp() + ARM: crypto: comment out gcc warning that breaks clang builds + mt7601u: add USB device ID for some versions of XiaoDu WiFi Dongle. + ACPI: video: Force backlight native for some TongFang devices + macintosh/adb: fix oob read in do_adb_query() function + Makefile: link with -z noexecstack --no-warn-rwx-segments + x86: link vdso and boot with -z noexecstack --no-warn-rwx-segments + ALSA: bcd2000: Fix a UAF bug on the error path of probing + add barriers to buffer_uptodate and set_buffer_uptodate + HID: wacom: Don't register pad_input for touch switch + KVM: SVM: Don't BUG if userspace injects an interrupt with GIF=0 + KVM: x86: Mark TSS busy during LTR emulation _after_ all fault checks + KVM: x86: Set error code to segment selector on LLDT/LTR non-canonical #GP + ALSA: hda/conexant: Add quirk for LENOVO 20149 Notebook model + ALSA: hda/cirrus - support for iMac 12,1 model + vfs: Check the truncate maximum size in inode_newsize_ok() + fs: Add missing umask strip in vfs_tmpfile + usbnet: Fix linkwatch use-after-free on disconnect + parisc: Fix device names in /proc/iomem + drm/nouveau: fix another off-by-one in nvbios_addr + drm/amdgpu: Check BO's requested pinning domains against its preferred_domains + iio: light: isl29028: Fix the warning in isl29028_remove() + fuse: limit nsec + md-raid10: fix KASAN warning + ia64, processor: fix -Wincompatible-pointer-types in ia64_get_irr() + PCI: Add defines for normal and subtractive PCI bridges + powerpc/fsl-pci: Fix Class Code of PCIe Root Port + powerpc/powernv: Avoid crashing if rng is NULL + MIPS: cpuinfo: Fix a warning for CONFIG_CPUMASK_OFFSTACK + USB: HCD: Fix URB giveback issue in tasklet function + netfilter: nf_tables: fix null deref due to zeroed list head + arm64: Do not forget syscall when starting a new thread. + arm64: fix oops in concurrently setting insn_emulation sysctls + ext2: Add more validity checks for inode counts + ARM: dts: imx6ul: add missing properties for sram + ARM: dts: imx6ul: fix qspi node compatible + ARM: OMAP2+: display: Fix refcount leak bug + ACPI: PM: save NVS memory for Lenovo G40-45 + ACPI: LPSS: Fix missing check in register_device_clock() + PM: hibernate: defer device probing when resuming from hibernation + selinux: Add boundary check in put_entry() + ARM: findbit: fix overflowing offset + ARM: bcm: Fix refcount leak in bcm_kona_smc_init + x86/pmem: Fix platform-device leak in error path + ARM: dts: ast2500-evb: fix board compatible + soc: fsl: guts: machine variable might be unset + cpufreq: zynq: Fix refcount leak in zynq_get_revision + ARM: dts: qcom: pm8841: add required thermal-sensor-cells + arm64: dts: qcom: msm8916: Fix typo in pronto remoteproc node + regulator: of: Fix refcount leak bug in of_get_regulation_constraints() + thermal/tools/tmon: Include pthread and time headers in tmon.h + dm: return early from dm_pr_call() if DM device is suspended + drm/radeon: fix potential buffer overflow in ni_set_mc_special_registers() + drm/mediatek: Add pull-down MIPI operation in mtk_dsi_poweroff function + i2c: Fix a potential use after free + wifi: iwlegacy: 4965: fix potential off-by-one overflow in il4965_rs_fill_link_cmd() + drm: bridge: adv7511: Add check for mipi_dsi_driver_register + media: hdpvr: fix error value returns in hdpvr_read + drm/vc4: dsi: Correct DSI divider calculations + drm/rockchip: vop: Don't crash for invalid duplicate_state() + drm/mediatek: dpi: Remove output format of YUV + drm: bridge: sii8620: fix possible off-by-one + media: platform: mtk-mdp: Fix mdp_ipi_comm structure alignment + tcp: make retransmitted SKB fit into the send window + selftests:
[Kernel-packages] [Bug 1981433] Re: [Asus Zenbook UX3402ZA] Sound doesn't work at all
On using linux-oem-5.17 kernel, no sound yet. But I got the following log in dmesg related to Cirrus driver, I assume. [ 11.845962] cs35l41_hda: probe of spi0-CSC3551:00-cs35l41-hda.0 failed with error -22 [ 11.846034] cs35l41_hda: probe of spi0-CSC3551:00-cs35l41-hda.1 failed with error -22 -- 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/1981433 Title: [Asus Zenbook UX3402ZA] Sound doesn't work at all Status in linux 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/ubuntu/+source/linux/+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 1786013] Autopkgtest regression report (linux-meta-azure-5.4/5.4.0.1092.69)
All autopkgtests for the newly accepted linux-meta-azure-5.4 (5.4.0.1092.69) for bionic have finished running. The following regressions have been reported in tests triggered by the package: lxc/3.0.3-0ubuntu1~18.04.1 (amd64) dahdi-linux/1:2.11.1~dfsg-1ubuntu4.2 (amd64) v4l2loopback/0.10.0-1ubuntu1.2 (arm64, amd64) kpatch/0.5.0-0ubuntu1.1 (amd64) asic0x/1.0.1-1 (arm64, 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/bionic/update_excuses.html#linux-meta-azure-5.4 [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 1990697] 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 1990697 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/1990697 Title: Crash on resume from sleep - 22.04, Thinkpad T14 (AMD) Gen 2 Status in linux package in Ubuntu: Incomplete Bug description: I'm seeing this 2-3 times per week. My system is configured with "Linux Suspend" in the BIOS (not the Windows/Modern setting). Furthermore, when plugged in, my system does not sleep. When I come up to my laptop after inactivity, the screens are dark (but as noted above, it is not suspended). If I click on a key and wait for both external monitors to light up, I can generally hit enter at that point, type my password and get in. If, however, I'm in a hurry or not thinking about it and just walk up to the machine, hit enter, type my password and hit enter a second time, I can generally reproduce the problem. The screen either goes to a backlit entirely black view, or (more commonly) a light grey (not the same color of grey as the Ubuntu login screen, much more white in the crashed state). The system is completely unresponsive and cannot be pinged or ssh'ed into from the outside. The only cure is to long-press the power button until it powers down, wait a moment and press it again to restart. Upon suggestions from the #Ubuntu mattermost channel, I ran: # journalctl -xe -b -1 That generated the following data: Sep 23 11:35:35 T14 kernel: RIP: 0010:update_config+0x11b/0x280 [amdgpu] Sep 23 11:35:35 T14 kernel: Code: 13 0f 00 00 41 0f b6 44 24 03 88 83 1e 0f 00 > Sep 23 11:35:35 T14 kernel: RSP: 0018:9b4743bab618 EFLAGS: 00010202 Sep 23 11:35:35 T14 kernel: RAX: RBX: 8a578653cf88 RCX: ff> Sep 23 11:35:35 T14 kernel: RDX: 8a578653dea0 RSI: 9b4743bab668 RDI: ff> Sep 23 11:35:35 T14 kernel: RBP: 9b4743bab658 R08: R09: 00> Sep 23 11:35:35 T14 kernel: R10: 5649 R11: 0010 R12: ff> Sep 23 11:35:35 T14 kernel: R13: 8a57a5eda000 R14: 0001 R15: ff> Sep 23 11:35:35 T14 kernel: FS: 7fb5f59a35c0() GS:8a5e4f04(000> Sep 23 11:35:35 T14 kernel: CS: 0010 DS: ES: CR0: 80050033 Sep 23 11:35:35 T14 kernel: CR2: CR3: 0001704d6000 CR4: 00> Sep 23 11:35:35 T14 kernel: PKRU: 5554 Sep 23 11:35:38 T14 kernel: input: PLT V5200 Series (AVRCP) as /devices/virtual> Sep 23 11:35:38 T14 pulseaudio[3488]: Battery Level: 90% Sep 23 11:35:38 T14 pulseaudio[3488]: Dock Status: undocked Sep 23 11:35:38 T14 systemd-logind[1832]: Watching system buttons on /dev/input> Sep 23 11:35:39 T14 bluetoothd[1809]: /org/bluez/hci0/dev_BC_F2_92_A0_AC_33/sep> Sep 23 11:35:39 T14 rtkit-daemon[2111]: Supervising 9 threads of 4 processes of> Sep 23 11:35:39 T14 rtkit-daemon[2111]: Successfully made thread 41544 of proce> Sep 23 11:35:39 T14 rtkit-daemon[2111]: Supervising 10 threads of 4 processes o> Sep 23 11:35:39 T14 pulseaudio[3488]: org.freedesktop.DBus.Properties.Get /org/> Sep 23 11:35:41 T14 audit[4797]: SECCOMP auid=1000 uid=1000 gid=1000 ses=3 subj> Sep 23 11:35:41 T14 kernel: audit: type=1326 audit(1663947341.195:578): auid=10> To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990697/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1990698] [NEW] Bionic update: upstream stable patchset 2022-09-23
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2022-09-23 from git://git.kernel.org/ ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1990698 Title: Bionic update: upstream stable patchset 2022-09-23 Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: New Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2022-09-23 from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990698/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1990697] [NEW] Crash on resume from sleep - 22.04, Thinkpad T14 (AMD) Gen 2
Public bug reported: I'm seeing this 2-3 times per week. My system is configured with "Linux Suspend" in the BIOS (not the Windows/Modern setting). Furthermore, when plugged in, my system does not sleep. When I come up to my laptop after inactivity, the screens are dark (but as noted above, it is not suspended). If I click on a key and wait for both external monitors to light up, I can generally hit enter at that point, type my password and get in. If, however, I'm in a hurry or not thinking about it and just walk up to the machine, hit enter, type my password and hit enter a second time, I can generally reproduce the problem. The screen either goes to a backlit entirely black view, or (more commonly) a light grey (not the same color of grey as the Ubuntu login screen, much more white in the crashed state). The system is completely unresponsive and cannot be pinged or ssh'ed into from the outside. The only cure is to long-press the power button until it powers down, wait a moment and press it again to restart. Upon suggestions from the #Ubuntu mattermost channel, I ran: # journalctl -xe -b -1 That generated the following data: Sep 23 11:35:35 T14 kernel: RIP: 0010:update_config+0x11b/0x280 [amdgpu] Sep 23 11:35:35 T14 kernel: Code: 13 0f 00 00 41 0f b6 44 24 03 88 83 1e 0f 00 > Sep 23 11:35:35 T14 kernel: RSP: 0018:9b4743bab618 EFLAGS: 00010202 Sep 23 11:35:35 T14 kernel: RAX: RBX: 8a578653cf88 RCX: ff> Sep 23 11:35:35 T14 kernel: RDX: 8a578653dea0 RSI: 9b4743bab668 RDI: ff> Sep 23 11:35:35 T14 kernel: RBP: 9b4743bab658 R08: R09: 00> Sep 23 11:35:35 T14 kernel: R10: 5649 R11: 0010 R12: ff> Sep 23 11:35:35 T14 kernel: R13: 8a57a5eda000 R14: 0001 R15: ff> Sep 23 11:35:35 T14 kernel: FS: 7fb5f59a35c0() GS:8a5e4f04(000> Sep 23 11:35:35 T14 kernel: CS: 0010 DS: ES: CR0: 80050033 Sep 23 11:35:35 T14 kernel: CR2: CR3: 0001704d6000 CR4: 00> Sep 23 11:35:35 T14 kernel: PKRU: 5554 Sep 23 11:35:38 T14 kernel: input: PLT V5200 Series (AVRCP) as /devices/virtual> Sep 23 11:35:38 T14 pulseaudio[3488]: Battery Level: 90% Sep 23 11:35:38 T14 pulseaudio[3488]: Dock Status: undocked Sep 23 11:35:38 T14 systemd-logind[1832]: Watching system buttons on /dev/input> Sep 23 11:35:39 T14 bluetoothd[1809]: /org/bluez/hci0/dev_BC_F2_92_A0_AC_33/sep> Sep 23 11:35:39 T14 rtkit-daemon[2111]: Supervising 9 threads of 4 processes of> Sep 23 11:35:39 T14 rtkit-daemon[2111]: Successfully made thread 41544 of proce> Sep 23 11:35:39 T14 rtkit-daemon[2111]: Supervising 10 threads of 4 processes o> Sep 23 11:35:39 T14 pulseaudio[3488]: org.freedesktop.DBus.Properties.Get /org/> Sep 23 11:35:41 T14 audit[4797]: SECCOMP auid=1000 uid=1000 gid=1000 ses=3 subj> Sep 23 11:35:41 T14 kernel: audit: type=1326 audit(1663947341.195:578): auid=10> ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1990697 Title: Crash on resume from sleep - 22.04, Thinkpad T14 (AMD) Gen 2 Status in linux package in Ubuntu: New Bug description: I'm seeing this 2-3 times per week. My system is configured with "Linux Suspend" in the BIOS (not the Windows/Modern setting). Furthermore, when plugged in, my system does not sleep. When I come up to my laptop after inactivity, the screens are dark (but as noted above, it is not suspended). If I click on a key and wait for both external monitors to light up, I can generally hit enter at that point, type my password and get in. If, however, I'm in a hurry or not thinking about it and just walk up to the machine, hit enter, type my password and hit enter a second time, I can generally reproduce the problem. The screen either goes to a backlit entirely black view, or (more commonly) a light grey (not the same color of grey as the Ubuntu login screen, much more white in the crashed state). The system is completely unresponsive and cannot be pinged or ssh'ed into from the outside. The only cure is to long-press the power button until it powers down, wait a moment and press it again to restart. Upon suggestions from the #Ubuntu mattermost channel, I ran: # journalctl -xe -b -1 That generated the following data: Sep 23 11:35:35 T14 kernel: RIP: 0010:update_config+0x11b/0x280 [amdgpu] Sep 23 11:35:35 T14 kernel: Code: 13 0f 00 00 41 0f b6 44 24 03 88 83 1e 0f 00 > Sep 23 11:35:35 T14 kernel: RSP: 0018:9b4743bab618 EFLAGS: 00010202 Sep 23 11:35:35 T14 kernel: RAX: RBX: 8a578653cf88 RCX: ff> Sep 23 11:35:35 T14 kernel: RDX: 8a578653dea0 RSI: 9b4743bab668 RDI: ff> Sep 23 11:35:35 T14 kernel: RBP: 9b4743bab658 R08: R09: 00> Sep 23 11:35:35 T14 kernel: R10:
[Kernel-packages] [Bug 1990690] Re: Users belonging to video group may trigger a deadlock WARN
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => Cengiz Can (cengizcan)
** Changed in: linux (Ubuntu)
Assignee: Cengiz Can (cengizcan) => (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/1990690
Title:
Users belonging to video group may trigger a deadlock WARN
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Bionic:
In Progress
Bug description:
[Impact]
One of the fixing commits for CVE-2021-33655, commit 159a96b199b4
("fbcon: Prevent that screen size is smaller than font size") introduced
a redundant lock_fb_info line into the ioctl flow in fbmem.c.
This line only exists in bionic tree.
Users belonging to video group may trigger a deadlock and potentially
lock the system.
WARNING: possible recursive locking detected
4.15.0-195-generic #206 Not tainted
refresh/1248 is trying to acquire lock:
(_info->lock){+.+.}, at: [<4c154cfe>] lock_fb_info+0x1d/0x40
but task is already holding lock:
(_info->lock){+.+.}, at: [<4c154cfe>] lock_fb_info+0x1d/0x40
other info that might help us debug this:
Possible unsafe locking scenario:
CPU0
lock(_info->lock);
lock(_info->lock);
*** DEADLOCK ***
May be due to missing lock nesting notation
2 locks held by refresh/1248:
#0: (console_lock){+.+.}, at: [<8000aa2b>] do_fb_ioctl+0x435/0x5e0
#1: (_info->lock){+.+.}, at: [<4c154cfe>] lock_fb_info+0x1d/0x40
stack backtrace:
CPU: 0 PID: 1248 Comm: refresh Not tainted 4.15.0-195-generic #206
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.15.0-1 04/01/2014
Call Trace:
dump_stack+0x98/0xd2
__lock_acquire+0x736/0x1480
? sched_clock_local+0x17/0x90
? sched_clock+0x9/0x10
? sched_clock_local+0x17/0x90
lock_acquire+0xa3/0x1e0
? lock_acquire+0xa3/0x1e0
? lock_fb_info+0x1d/0x40
? lock_fb_info+0x1d/0x40
__mutex_lock+0x65/0x970
? lock_fb_info+0x1d/0x40
? sched_clock_local+0x17/0x90
? lock_acquire+0xa3/0x1e0
mutex_lock_nested+0x1b/0x20
? mutex_lock_nested+0x1b/0x20
lock_fb_info+0x1d/0x40
do_fb_ioctl+0x57a/0x5e0
? __fd_install+0x5/0x250
fb_ioctl+0x33/0x40
? fb_ioctl+0x33/0x40
do_vfs_ioctl+0xa9/0x6d0
? putname+0x4c/0x60
? do_sys_open+0x13d/0x370
SyS_ioctl+0x79/0x90
do_syscall_64+0x7b/0x1e0
entry_SYSCALL_64_after_hwframe+0x46/0xbb
RIP: 0033:0x7f22acca7217
RSP: 002b:7ffe2a930b48 EFLAGS: 0213 ORIG_RAX: 0010
RAX: ffda RBX: RCX: 7f22acca7217
RDX: 7ffe2a930c30 RSI: 4601 RDI: 0003
RBP: 7ffe2a930d40 R08: R09:
R10: R11: 0213 R12: 5624ac8fc7c0
R13: 7ffe2a930e20 R14: R15:
[Test case]
Run a sample framebuffer userspace test to call FBIOPUT_VSCREENINFO
and verified with LOCKDEP.
[Potential regressions]
There are no new potential regressions.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990690/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1990690] [NEW] Users belonging to video group may trigger a deadlock WARN
Public bug reported:
[Impact]
One of the fixing commits for CVE-2021-33655, commit 159a96b199b4
("fbcon: Prevent that screen size is smaller than font size") introduced
a redundant lock_fb_info line into the ioctl flow in fbmem.c.
This line only exists in bionic tree.
Users belonging to video group may trigger a deadlock and potentially
lock the system.
WARNING: possible recursive locking detected
4.15.0-195-generic #206 Not tainted
refresh/1248 is trying to acquire lock:
(_info->lock){+.+.}, at: [<4c154cfe>] lock_fb_info+0x1d/0x40
but task is already holding lock:
(_info->lock){+.+.}, at: [<4c154cfe>] lock_fb_info+0x1d/0x40
other info that might help us debug this:
Possible unsafe locking scenario:
CPU0
lock(_info->lock);
lock(_info->lock);
*** DEADLOCK ***
May be due to missing lock nesting notation
2 locks held by refresh/1248:
#0: (console_lock){+.+.}, at: [<8000aa2b>] do_fb_ioctl+0x435/0x5e0
#1: (_info->lock){+.+.}, at: [<4c154cfe>] lock_fb_info+0x1d/0x40
stack backtrace:
CPU: 0 PID: 1248 Comm: refresh Not tainted 4.15.0-195-generic #206
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.15.0-1 04/01/2014
Call Trace:
dump_stack+0x98/0xd2
__lock_acquire+0x736/0x1480
? sched_clock_local+0x17/0x90
? sched_clock+0x9/0x10
? sched_clock_local+0x17/0x90
lock_acquire+0xa3/0x1e0
? lock_acquire+0xa3/0x1e0
? lock_fb_info+0x1d/0x40
? lock_fb_info+0x1d/0x40
__mutex_lock+0x65/0x970
? lock_fb_info+0x1d/0x40
? sched_clock_local+0x17/0x90
? lock_acquire+0xa3/0x1e0
mutex_lock_nested+0x1b/0x20
? mutex_lock_nested+0x1b/0x20
lock_fb_info+0x1d/0x40
do_fb_ioctl+0x57a/0x5e0
? __fd_install+0x5/0x250
fb_ioctl+0x33/0x40
? fb_ioctl+0x33/0x40
do_vfs_ioctl+0xa9/0x6d0
? putname+0x4c/0x60
? do_sys_open+0x13d/0x370
SyS_ioctl+0x79/0x90
do_syscall_64+0x7b/0x1e0
entry_SYSCALL_64_after_hwframe+0x46/0xbb
RIP: 0033:0x7f22acca7217
RSP: 002b:7ffe2a930b48 EFLAGS: 0213 ORIG_RAX: 0010
RAX: ffda RBX: RCX: 7f22acca7217
RDX: 7ffe2a930c30 RSI: 4601 RDI: 0003
RBP: 7ffe2a930d40 R08: R09:
R10: R11: 0213 R12: 5624ac8fc7c0
R13: 7ffe2a930e20 R14: R15:
[Test case]
Run a sample framebuffer userspace test to call FBIOPUT_VSCREENINFO
and verified with LOCKDEP.
[Potential regressions]
There are no new potential regressions.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Invalid
** Affects: linux (Ubuntu Bionic)
Importance: Medium
Assignee: Cengiz Can (cengizcan)
Status: In Progress
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Cengiz Can (cengizcan)
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Importance: Medium => Undecided
** Changed in: linux (Ubuntu Bionic)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: New => Invalid
** Changed in: linux (Ubuntu Bionic)
Status: New => In Progress
--
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/1990690
Title:
Users belonging to video group may trigger a deadlock WARN
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Bionic:
In Progress
Bug description:
[Impact]
One of the fixing commits for CVE-2021-33655, commit 159a96b199b4
("fbcon: Prevent that screen size is smaller than font size") introduced
a redundant lock_fb_info line into the ioctl flow in fbmem.c.
This line only exists in bionic tree.
Users belonging to video group may trigger a deadlock and potentially
lock the system.
WARNING: possible recursive locking detected
4.15.0-195-generic #206 Not tainted
refresh/1248 is trying to acquire lock:
(_info->lock){+.+.}, at: [<4c154cfe>] lock_fb_info+0x1d/0x40
but task is already holding lock:
(_info->lock){+.+.}, at: [<4c154cfe>] lock_fb_info+0x1d/0x40
other info that might help us debug this:
Possible unsafe locking scenario:
CPU0
lock(_info->lock);
lock(_info->lock);
*** DEADLOCK ***
May be due to missing lock nesting notation
2 locks held by refresh/1248:
#0: (console_lock){+.+.}, at: [<8000aa2b>] do_fb_ioctl+0x435/0x5e0
#1: (_info->lock){+.+.}, at: [<4c154cfe>] lock_fb_info+0x1d/0x40
stack backtrace:
CPU: 0 PID: 1248 Comm: refresh Not tainted 4.15.0-195-generic #206
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.15.0-1
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-bluefield/5.4.0.1047.46)
All autopkgtests for the newly accepted linux-meta-bluefield (5.4.0.1047.46) for focal have finished running. The following regressions have been reported in tests triggered by the package: mali-midgard/unknown (arm64) lxc/unknown (arm64) openrazer/unknown (arm64) nat-rtsp/unknown (arm64) langford/unknown (arm64) lime-forensics/unknown (arm64) gost-crypto/unknown (arm64) lttng-modules/unknown (arm64) dm-writeboost/unknown (arm64) linux-bluefield/unknown (arm64) west-chamber/unknown (arm64) dpdk/unknown (arm64) ddcci-driver-linux/unknown (arm64) iptables-netflow/unknown (arm64) openafs/unknown (arm64) adv-17v35x/unknown (arm64) zfs-linux/unknown (arm64) jool/unknown (arm64) glibc/unknown (arm64) wireguard-linux-compat/unknown (arm64) snapd/unknown (arm64) bbswitch/unknown (arm64) r8168/unknown (arm64) acpi-call/unknown (arm64) fwts/unknown (arm64) xtables-addons/unknown (arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-meta-bluefield [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
Re: [Kernel-packages] [Bug 1970672] Re: makedumpfile falls back to cp with "__vtop4_x86_64: Can't get a valid pmd_pte."
On Fri, Sep 23, 2022 at 11:15 AM Kellen Renshaw
<1970...@bugs.launchpad.net> wrote:
>
> I have put up a draft SRU exception page at
> https://wiki.ubuntu.com/MakedumpfileUpdates. Comments/edits are welcome.
> I am working on finding an appropriate place for test vmcores to be
> stored.
Awesome! Thanks for starting this. I made some edits already, but
here's some other things I'd recommend:
- Provide links under resources (it's a web page!)
- be more precise about what will be tested, ideally in a checklist
form. Make it clear enough that you could give the list to another
developer and they would run the same tests and get the same results.
- Testing other architectures should not be optional IMO. makedumpfile
has architecture specific knowledge. You could easily break one w/o
noticing on another.
- Mention the plan to filter a pool of saved dump files as a
regression test. That is key IMO.
- If you have the regression testing pool, I don't see any reason to
have to do the full kdump process everywhere. Just do that once (one
kernel, one arch) to make sure the kdump-tools<->makedumpfile
interface has been preserved. Testing the full crash dump process is
painful, but makedumpfile really is just used as a filter, and we can
test that easily.
-dann
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1970672
Title:
makedumpfile falls back to cp with "__vtop4_x86_64: Can't get a valid
pmd_pte."
Status in makedumpfile package in Ubuntu:
Confirmed
Bug description:
[Impact]
* On Focal with an HWE (>=5.12) kernel, makedumpfile can sometimes fail with
"__vtop4_x86_64: Can't get a valid pmd_pte."
* makedumpfile falls back to cp for the dump, resulting in extremely
large vmcores. This can impact both collection and analysis due to
lack of space for the resulting vmcore.
* This is fixed in upstream commit present in versions 1.7.0 and 1.7.1:
https://github.com/makedumpfile/makedumpfile/commit/646456862df8926ba10dd7330abf3bf0f887e1b6
commit 646456862df8926ba10dd7330abf3bf0f887e1b6
Author: Kazuhito Hagio
Date: Wed May 26 14:31:26 2021 +0900
[PATCH] Increase SECTION_MAP_LAST_BIT to 5
* Required for kernel 5.12
Kernel commit 1f90a3477df3 ("mm: teach pfn_to_online_page() about
ZONE_DEVICE section collisions") added a section flag
(SECTION_TAINT_ZONE_DEVICE) and causes makedumpfile an error on
some machines like this:
__vtop4_x86_64: Can't get a valid pmd_pte.
readmem: Can't convert a virtual address(e2bdc200) to physical
address.
readmem: type_addr: 0, addr:e2bdc200, size:32768
__exclude_unnecessary_pages: Can't read the buffer of struct page.
create_2nd_bitmap: Can't exclude unnecessary pages.
Increase SECTION_MAP_LAST_BIT to 5 to fix this. The bit had not
been used until the change, so we can just increase the value.
Signed-off-by: Kazuhito Hagio
[Test Plan]
* Confirm that makedumpfile works as expected by triggering a kdump.
* Confirm that the patched makedumpfile works as expected on a system
known to experience the issue.
* Confirm that the patched makedumpfile is able to work with a cp-
generated known affected vmcore to compress it. The unpatched version
fails.
[Where problems could occur]
* This change could adversely affect the collection/compression of
vmcores during a kdump situation resulting in fallback to cp.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1970672/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1988434] Re: azure: Set arm64 CONFIG_TRANSPARENT_HUGEPAGE_ALWAYS=n
This bug is awaiting verification that the linux-azure/5.4.0-1092.97 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- 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/1988434 Title: azure: Set arm64 CONFIG_TRANSPARENT_HUGEPAGE_ALWAYS=n Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Focal: Fix Committed Status in linux-azure source package in Jammy: Fix Released Status in linux-azure source package in Kinetic: Fix Released Bug description: SRU Justification [Impact] This request for all the ARM images Kernel have config updated . There is performance issues due to these config setting and after troubleshooting MSFT team found below two settings to update . Recommended CONFIG_TRANSPARENT_HUGEPAGE_ALWAYS=n CONFIG_TRANSPARENT_HUGEPAGE_MADVISE=y [Test Case] Microsoft tested [Where things could go wrong] Performance could decrease for some workloads. [Other Info] SF: #00343662 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1988434/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1990009] Re: Azure: Focal 5.4 kernel eBPF opensnoop does not display PATH
This bug is awaiting verification that the linux-azure/5.4.0-1092.97 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- 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/1990009 Title: Azure: Focal 5.4 kernel eBPF opensnoop does not display PATH Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Focal: Fix Committed Bug description: SRU Justification [Impact] The actual kernel used on AKS arm64 (i.e. 5.4.1089) suffers from a known problem [1]. As a consequence, opensnoop does not display PATH: # Run the following from Canonical:UbuntuServer:18_04-daily-lts-arm64:18.04.202208290 $ uname -a Linux francis-vm-arm64-ubuntu18vm 5.4.0-1089-azure #94~18.04.1-Ubuntu SMP Fri Aug 5 12:36:48 UTC 2022 aarch64 aarch64 aarch64 GNU/Linux $ lsb_release -rd Description: Ubuntu 18.04.6 LTS Release: 18.04 $ git clone --recurse-submodules https://github.com/iovisor/bcc Linux francis-vm-arm64-ubuntu18vm 5.4.0-1089-azure #94~18.04.1-Ubuntu SMP Fri Aug 5 12:36:48 UTC 2022 aarch64 aarch64 aarch64 GNU/Linux $ sudo sh -c 'apt update && apt install -qy clang-10 llvm-10 make gcc pkg-config libelf-dev libz-dev' ... $ cd bcc/libbpf-tools $ CLANG=clang-10 LLVM_STRIP=llvm-strip-10 make -j opensnoop ... BINARY opensnoop $ sudo ./opensnoop PID COMM FD ERR PATH 1672 python3 3 0 9746 opensnoop 20 0 1672 python3 3 0 1672 python3 3 0 1672 python3 -1 2 1672 python3 3 0 1 systemd 18 0 1672 python3 6 0 1672 python3 3 0 1672 python3 3 0 1672 python3 3 0 1672 python3 3 0 1672 python3 3 0 ^C As you can see, nothing is printed for the PATH while normal behavior prints the path of the opened file: $ uname -a Linux pwmachine 5.15.0-46-generic #49~20.04.1-Ubuntu SMP Thu Aug 4 19:15:44 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux $ sudo ./opensnoop PID COMM FD ERR PATH 2704 systemd 23 0 virtual 2704 systemd 22 0 misc 2704 systemd 23 0 fuse 2704 systemd 22 0 /sys/devices/virtual/misc/fuse/uevent 2704 systemd 22 0 /run/udev/data/c10:229 2704 systemd 22 0 /proc/2704/status 2704 systemd 22 0 /proc/2704/status 2704 systemd 22 0 /proc/2704/status ^C This bug was fixed in upstream patch [2] Sadly, this patch was not back ported, so it is not present in stable kernels. [Test plan] Follow the above instructions [Where things could go wrong] Unknown [Other Info] Original RFC at https://lists.ubuntu.com/archives/kernel- team/2022-September/133038.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1990009/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1970672] Re: makedumpfile falls back to cp with "__vtop4_x86_64: Can't get a valid pmd_pte."
I have put up a draft SRU exception page at
https://wiki.ubuntu.com/MakedumpfileUpdates. Comments/edits are welcome.
I am working on finding an appropriate place for test vmcores to be
stored.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1970672
Title:
makedumpfile falls back to cp with "__vtop4_x86_64: Can't get a valid
pmd_pte."
Status in makedumpfile package in Ubuntu:
Confirmed
Bug description:
[Impact]
* On Focal with an HWE (>=5.12) kernel, makedumpfile can sometimes fail with
"__vtop4_x86_64: Can't get a valid pmd_pte."
* makedumpfile falls back to cp for the dump, resulting in extremely
large vmcores. This can impact both collection and analysis due to
lack of space for the resulting vmcore.
* This is fixed in upstream commit present in versions 1.7.0 and 1.7.1:
https://github.com/makedumpfile/makedumpfile/commit/646456862df8926ba10dd7330abf3bf0f887e1b6
commit 646456862df8926ba10dd7330abf3bf0f887e1b6
Author: Kazuhito Hagio
Date: Wed May 26 14:31:26 2021 +0900
[PATCH] Increase SECTION_MAP_LAST_BIT to 5
* Required for kernel 5.12
Kernel commit 1f90a3477df3 ("mm: teach pfn_to_online_page() about
ZONE_DEVICE section collisions") added a section flag
(SECTION_TAINT_ZONE_DEVICE) and causes makedumpfile an error on
some machines like this:
__vtop4_x86_64: Can't get a valid pmd_pte.
readmem: Can't convert a virtual address(e2bdc200) to physical
address.
readmem: type_addr: 0, addr:e2bdc200, size:32768
__exclude_unnecessary_pages: Can't read the buffer of struct page.
create_2nd_bitmap: Can't exclude unnecessary pages.
Increase SECTION_MAP_LAST_BIT to 5 to fix this. The bit had not
been used until the change, so we can just increase the value.
Signed-off-by: Kazuhito Hagio
[Test Plan]
* Confirm that makedumpfile works as expected by triggering a kdump.
* Confirm that the patched makedumpfile works as expected on a system
known to experience the issue.
* Confirm that the patched makedumpfile is able to work with a cp-
generated known affected vmcore to compress it. The unpatched version
fails.
[Where problems could occur]
* This change could adversely affect the collection/compression of
vmcores during a kdump situation resulting in fallback to cp.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1970672/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1961338] Re: Disable unprivileged BPF by default
This bug is awaiting verification that the linux-xilinx- zynqmp/5.4.0-1018.21 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification- done-focal'. If the problem still exists, change the tag 'verification- needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- 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/1961338 Title: Disable unprivileged BPF by default Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Bug description: [Impact] Unprivileged users have access to BPF, allowing them to execute code in the kernel under their control. Though restricted and verified, a lot of security issues have been uncovered over the years, indicating that it should be disabled by default in order to protect our users. Admins can reenable that access or give CAP_BPF to programs if needed. [Test case] A qa-regression-testing testcase has been added that checks for the ability to load BPF programs under different circumstances. [Potential regression] Users who rely on unprivileged BPF access will need to change the setting or give CAP_BPF to their programs. Also, sysctl and bpf code might be affected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1961338/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1961338] Re: Disable unprivileged BPF by default
This bug is awaiting verification that the linux-xilinx- zynqmp/5.4.0-1018.21 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification- done-focal'. If the problem still exists, change the tag 'verification- needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- 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/1961338 Title: Disable unprivileged BPF by default Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Bug description: [Impact] Unprivileged users have access to BPF, allowing them to execute code in the kernel under their control. Though restricted and verified, a lot of security issues have been uncovered over the years, indicating that it should be disabled by default in order to protect our users. Admins can reenable that access or give CAP_BPF to programs if needed. [Test case] A qa-regression-testing testcase has been added that checks for the ability to load BPF programs under different circumstances. [Potential regression] Users who rely on unprivileged BPF access will need to change the setting or give CAP_BPF to their programs. Also, sysctl and bpf code might be affected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1961338/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1987670] Re: Add support for AMD PMF
** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1987670 Title: Add support for AMD PMF Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.0 source package in Jammy: Fix Committed Bug description: Some upcoming platforms support for AMD-PMF. This will enable ACPI platform profiles and some automatic transitions. The first 11 patches are queued up for 6.1 and also available in an immutable branch. https://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform- drivers-x86.git/log/?h=platform-drivers-x86-amd-pmf Can you please merge these to OEM-6.0? We will have 3-5 more patches targeted later as well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1987670/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1961338] Re: Disable unprivileged BPF by default
This bug is awaiting verification that the linux-xilinx- zynqmp/5.4.0-1018.21 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification- done-focal'. If the problem still exists, change the tag 'verification- needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- 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/1961338 Title: Disable unprivileged BPF by default Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Bug description: [Impact] Unprivileged users have access to BPF, allowing them to execute code in the kernel under their control. Though restricted and verified, a lot of security issues have been uncovered over the years, indicating that it should be disabled by default in order to protect our users. Admins can reenable that access or give CAP_BPF to programs if needed. [Test case] A qa-regression-testing testcase has been added that checks for the ability to load BPF programs under different circumstances. [Potential regression] Users who rely on unprivileged BPF access will need to change the setting or give CAP_BPF to their programs. Also, sysctl and bpf code might be affected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1961338/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1961338] Re: Disable unprivileged BPF by default
This bug is awaiting verification that the linux-xilinx- zynqmp/5.4.0-1018.21 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification- done-focal'. If the problem still exists, change the tag 'verification- needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- 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/1961338 Title: Disable unprivileged BPF by default Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Bug description: [Impact] Unprivileged users have access to BPF, allowing them to execute code in the kernel under their control. Though restricted and verified, a lot of security issues have been uncovered over the years, indicating that it should be disabled by default in order to protect our users. Admins can reenable that access or give CAP_BPF to programs if needed. [Test case] A qa-regression-testing testcase has been added that checks for the ability to load BPF programs under different circumstances. [Potential regression] Users who rely on unprivileged BPF access will need to change the setting or give CAP_BPF to their programs. Also, sysctl and bpf code might be affected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1961338/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1968155] Re: Multiple errors with DVD drive: ata1: SError: { PHYRdyChg CommWake 10B8B DevExch }
The problem was (partly) solved.
After asking for help in the linux kernel development mailing list Niklas
Cassel (one of the developers) wrote:
- The commit 1527f69204fe ("ata: ahci: Add Green Sardine vendor ID as
board_ahci_mobile") added the - PCI vendor and device id to the list of
supported AHCI controllers using the low power board
- version:
{ PCI_VDEVICE(AMD, 0x7901), board_ahci_low_power }, /* AMD Green
Sardine */
- Before the commit in question, your AHCI controller relied on this catch-all
entry:
/* Generic, PCI class code for AHCI */
{ PCI_ANY_ID, PCI_ANY_ID, PCI_ANY_ID, PCI_ANY_ID,
PCI_CLASS_STORAGE_SATA_AHCI, 0xff, board_ahci },
- which does not enable/allow any low power mode at all.
- Now, I do think that low power modes *should* work with this AHCI controller.
Most likely, it is - simply the optical drive that does not work well when the
HBA initiates a low power mode on the
- link.
.
.
.
- A way do disable lpm is to do:
$ ls -al /sys/class/scsi_host/host*
- Find your device in the list. My device is:
/sys/class/scsi_host/host13/
- Print the current lpm policy for your device:
$ cat /sys/class/scsi_host/host13/link_power_management_policy
med_power_with_dipm
- Anything other than "max_performance" means that you have (a varying degree)
of low power modes
- enabled.
$ sudo sh -c "echo max_performance >
/sys/class/scsi_host/host13/link_power_management_policy"
$ cat /sys/class/scsi_host/host13/link_power_management_policy
max_performance
- Try reading from the optical drive after ensuring that the policy is
"max_performance".
This solved the problem.
As the kernel parameter to disable lpm only works from kernel 5.18 onwards, I
had to find another way to force this setting, so I did:
$ apt install sysfsutils
and added in /etc/sysfs.conf the line:
class/scsi_host/host0/link_power_management_policy = max_performance
As long as I don't mess around with my hardware, the host number should stay
the same.
Of course, if anyone uses this method, he/she should find out his host number
for the controller of the optical drive in question and substitute it in the
hostnn part.
A definite solution will probably be a future patch in libata.
--
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/1968155
Title:
Multiple errors with DVD drive: ata1: SError: { PHYRdyChg CommWake
10B8B DevExch }
Status in linux package in Ubuntu:
Confirmed
Bug description:
Going from kernel version 5.4.0-99 to 5.4.0-100 my optical drive (Pioneer
BD-RW BDR-207M) became unusable. I include a selection of the errors, the
dmesg errors immediately after boot without trying to use the drive yet, the
system specs from system report, and the output of the inxi -Fdxxx commandin
the file attachment.txt.
Up to and including kernel 5.4.0-99 everything worked OK. Kernel 5.13.0-30
also works, from kernel 5.13.0-35 the same problem occurs. Might it be a
problem with atalib?
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: jaap 1928 F pulseaudio
/dev/snd/controlC1: jaap 1928 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: X-Cinnamon
DistroRelease: Linux Mint 20.3
InstallationDate: Installed on 2022-02-01 (64 days ago)
InstallationMedia: Linux Mint 20.3 "Una" - Release amd64 20220104
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
NonfreeKernelModules: nvidia_modeset nvidia
Package: linux (not installed)
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-100-generic
root=UUID=9d60bcb5-650d-484d-ae74-728526cd6db1 ro ipv6.disable=1
elevator=deadline quiet splash nomodeset
ProcVersionSignature: Ubuntu 5.4.0-100.113-generic 5.4.166
RelatedPackageVersions:
linux-restricted-modules-5.4.0-100-generic N/A
linux-backports-modules-5.4.0-100-generic N/A
linux-firmware 1.187.29
RfKill:
0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: yes
Tags: una
Uname: Linux 5.4.0-100-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip disk lpadmin plugdev sambashare sudo
systemd-timesync vboxusers
_MarkForUpload: True
dmi.bios.date: 12/01/2020
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P3.80
dmi.board.name: X570 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.:bvrP3.80:bd12/01/2020:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX570Taichi:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be
[Kernel-packages] [Bug 1987312] Re: IWLMEI may cause device down at resuming from s2idle
This bug is awaiting verification that the linux-oem-6.0/6.0.0-1004.4 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1987312 Title: IWLMEI may cause device down at resuming from s2idle Status in HWE Next: New Status in OEM Priority Project: New Status in backport-iwlwifi-dkms package in Ubuntu: Fix Released Status in linux package in Ubuntu: In Progress Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in backport-iwlwifi-dkms source package in Jammy: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Committed Status in backport-iwlwifi-dkms source package in Kinetic: Fix Released Status in linux source package in Kinetic: In Progress Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: [SRU Justification] [Impact] WiFi interfaces unsolicitedly down at resuming from s2idle. [Fix] Intel confirmed there is no CSME for WLAN POR for Linux. CSME for WLAN POR is only for Windows project design. Please remove or disable CONFIG_IWLMEI from Linux. [Test Case] Make sure iwlmei.ko is not built. [Where problems could occur] iwlmei was not enabled before 5.17 and was turned on automatically since then. This restores the state and shall not have impact on existing devices. == original bug report == Intel confirmed there is no CSME for WLAN POR for Linux. CSME for WLAN POR is only for Windows project design. Please remove or disable CONFIG_IWLMEI from Linux. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1987312/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1987670] Re: Add support for AMD PMF
This bug is awaiting verification that the linux-oem-6.0/6.0.0-1004.4 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1987670 Title: Add support for AMD PMF Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.0 source package in Jammy: Fix Committed Bug description: Some upcoming platforms support for AMD-PMF. This will enable ACPI platform profiles and some automatic transitions. The first 11 patches are queued up for 6.1 and also available in an immutable branch. https://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform- drivers-x86.git/log/?h=platform-drivers-x86-amd-pmf Can you please merge these to OEM-6.0? We will have 3-5 more patches targeted later as well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1987670/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1988120] Re: Support Intel TDX guest attestation driver
This bug is awaiting verification that the linux-oem-6.0/6.0.0-1004.4 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1988120 Title: Support Intel TDX guest attestation driver Status in linux package in Ubuntu: Fix Committed Status in linux source package in Kinetic: Fix Committed Bug description: [Impact] Intel has requested to support the TDX (trust domain extension) guest attestation driver interface. In a TDX guest "attestation" is used to verify the trustworthiness of a TD (trusted domain) before provisioning secrets to the TD (i.e, encrypted keys to mount an encrypted rootfs, etc.). During the TD boot the initial contents and configurations are recorded by the Intel TDX module in the build time measurement register (MRTD). At TD runtime, the Intel TDX module reuses the Intel SGX attestation infrastructure to provide support for attesting to these information. This driver is targeting 6.x upstream, so we need to backport the upstream patches as SAUCE patches to properly support this feature in 5.19. [Fix] Backport upstream TDX attestation driver. [Test case] Tests have been performed by Intel, a test-case is included in the patch set as a kernel selftest (called 'tdx'). TODO: consider to integrate this test in our testing infrastructure once this feature has been merged. [Regression potential] This feature is self-contained, it's only available on amd64 and it doesn't affect any other amd64 code. So we could only experience regressions on amd64 systems that are using the TDX feature. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1988120/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1989172] Re: mlxbf-pmc: error when reading unprogrammed events
This bug is awaiting verification that the linux-bluefield/5.4.0-1047.52 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- 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/1989172 Title: mlxbf-pmc: error when reading unprogrammed events Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Focal: Fix Committed Bug description: SRU Justification: [Impact] When the counters are not programmed to monitor any events, reading the "event" file results in the following error: cat: /sys/class/hwmon/hwmon0/smmu0/event0: Invalid argument This is misleading and instead needs to indicate that the counter is currently not enabled. [Fix] * First, skip the check for whether the counter is enabled when reading the event info. If the counter is not enabled, it should return 0, which is the default value when coming out of reset. * 0 is not a valid event in most blocks as per the respective event lists, so add a "Disable" event to all the event lists. [Test Case] Without the fix, reading any "event" file right after reset when the counters are not programmed should result in the following error: cat: /sys/class/hwmon/hwmon0/smmu0/event0: Invalid argumen With the fix, it should instead print: 0x0: DISABLE [Regression Potential] Can be considered minimal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1989172/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1989495] Re: mlxbf_gige: need to clear MDIO gateway lock after read
This bug is awaiting verification that the linux-bluefield/5.4.0-1047.52 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- 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/1989495 Title: mlxbf_gige: need to clear MDIO gateway lock after read Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Focal: Fix Committed Bug description: SRU Justification: [Impact] The BlueField-2 GIGE logic accesses the MDIO device via reads/writes to a gateway (GW) register. The MDIO GW lock is set after read. Make sure to always clear to indicate that the GW register is not being used. If the lock is mistakenly interpreted as ACTIVE, then subsequent MDIO accesses will be blocked and PHY device will be inaccessible. [Fix] For each MDIO read and write transaction, the last step should be to clear the MDIO GW lock. [Test Case] Boot the BlueField-2 platform Bring up the "oob_net0" interface via DHCP or static IP Ping and file transfer over "oob_net0" should work properly Bounce the "oob_net0" interface a few times and repeat tests [Regression Potential] * Low risk for causing a regression, tested well in our lab. [Other] * None To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1989495/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1980060] Re: Fix AMDGPU blank screen when Type-C DP alt is in use
This bug is awaiting verification that the linux-nvidia/5.15.0-1007.7 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1980060 Title: Fix AMDGPU blank screen when Type-C DP alt is in use 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: Won't Fix 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 Bug description: [Impact] When Type-C DP/HDMI is in use, s0ix resume renders both eDP and DP outputs blank. [Fix] Query the firmware to ensure the DP alt status. [Test] Suspend and resume the system, both eDP and Type-C DP/HDMI are working. [Where problems could occur] This fix only applies to certain AMD GFX with certain firmware version, so the scope is very limited. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1980060/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1980087] Re: Fix PSR flickers on Intel TGL laptops + AUO panel
This bug is awaiting verification that the linux-nvidia/5.15.0-1007.7 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1980087 Title: Fix PSR flickers on Intel TGL laptops + AUO panel 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: Won't Fix 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 Bug description: [Impact] Screen flickers on certain Intel TGL laptops + AUO panel. [Fix] Enable PSR2 selective fetch only for the specific case to minimize the regression risk. [Test] Screen flickers can no longer be observed on affected laptops. [Where problems could occur] The fix becomes very specific, so any other combination won't be affected at all. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1980087/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942999] Re: Fix invalid MAC address after hotplug tbt dock
This bug is awaiting verification that the linux-nvidia/5.15.0-1007.7 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1942999 Title: Fix invalid MAC address after hotplug tbt dock Status in HWE Next: Fix Released Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Hirsute: Won't Fix Status in linux source package in Impish: Fix Released Status in linux source package in Jammy: Fix Released Status in linux-oem-5.13 source package in Jammy: Invalid Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Bug description: SRU justification: [Impact] igc driver can not connect to network after re-plugin thunderbolt dock when MAC passthrough enabled in BIOS. [Fix] Wait for the MAC copy of BIOS when enabled MAC passthrough. Intel engineer wants a different solution and promise to discuss with firmware engineer. Due to the schedule, made this as a short term solution to fix the issue, and wait for the other fix from Intel. [Test] Verified on hardware, after hotplug the thunderbolt cable, Ethernet works fine. [Where problems could occur] It may break the igc driver. Intel still doesn't provide any solution about their approach. In the meantime, this patch is still the only fix. Re-submit it to Jammy, oem-5.17 and Unstable kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1942999/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1884232] Re: touchpad and touchscreen doesn't work at all on ACER Spin 5 (SP513-54N)
This bug is awaiting verification that the linux-nvidia/5.15.0-1007.7
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy' to 'verification-done-jammy'. If the
problem still exists, change the tag 'verification-needed-jammy' to
'verification-failed-jammy'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1884232
Title:
touchpad and touchscreen doesn't work at all on ACER Spin 5
(SP513-54N)
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Focal:
Won't Fix
Status in linux source package in Jammy:
Fix Released
Bug description:
[Impact]
E820 reserved retire memory window, and make other hot-added devices unable
to get the required memory window.
[Fix]
It only can be fixed by a list of quirk to mark those machines out, and
requires below commits from v5.19-rc1 and v5.19-rc3
a2b36ffbf5b6 x86/PCI: Revert "x86/PCI: Clip only host bridge windows for E820
regions"
d341838d776a x86/PCI: Disable E820 reserved region clipping via quirks
fa6dae5d8208 x86/PCI: Add kernel cmdline options to use/ignore E820 reserved
regions
4c5e242d3e93 x86/PCI: Clip only host bridge windows for E820 regions
31bf0f433325 x86: Log resource clipping for E820 regions
93d256cd3c1e x86/PCI: Eliminate remove_e820_regions() common subexpressions
[Test]
Verified by the bug reporter.
[Where problems could occur]
The 6 commits are all clean cherry-picked, and the sixth commit reverts the
third commit which are the 2 commits that do real functional changes.
a2b36ffbf5b6 ("x86/PCI: Revert \"x86/PCI: Clip only host bridge windows for
E820 regions\"")
4c5e242d3e93 ("x86/PCI: Clip only host bridge windows for E820 regions")
The fourth and and fifth commits introduce a new quirk to ignore E820
reserved regions and the quirk only affects the listed machines.
Drivers that operates E820 table may fail if we ignore the E820 regions, but
it should have no impact on the listed consumer PCs.
===
Touchpad is not working at all on ACER Spin 5 SP513-54N.
According to
https://wiki.ubuntu.com/DebuggingTouchpadDetection#In_case_your_Touchpad_doesn.27t_work_at_all_.28No_response_from_the_Touchpad.29
I am creating this kernel bug issue.
There are more issues, too, like touchscreen not working and Ubuntu
not installable - see here if interrested
https://askubuntu.com/questions/1251719/
I would like to run Ubuntu on this machine and I am willing to help
with any debug or kernel tweaking... Please let me know.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-26-generic 5.4.0-26.30
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ubuntu 4195 F pulseaudio
CasperMD5CheckResult: skip
CasperVersion: 1.445
CurrentDesktop: ubuntu:GNOME
Date: Fri Jun 19 10:44:58 2020
LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: Acer Spin SP513-54N
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
RelatedPackageVersions:
linux-restricted-modules-5.4.0-26-generic N/A
linux-backports-modules-5.4.0-26-generic N/A
linux-firmware1.187
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/21/2020
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.00
dmi.board.name: Caboom_IL
dmi.board.vendor: IL
dmi.board.version: V1.00
dmi.chassis.type: 31
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.00
dmi.modalias:
dmi:bvnInsydeCorp.:bvrV1.00:bd02/21/2020:svnAcer:pnSpinSP513-54N:pvrV1.00:rvnIL:rnCaboom_IL:rvrV1.00:cvnAcer:ct31:cvrV1.00:
dmi.product.family: Spin 5
dmi.product.name: Spin SP513-54N
dmi.product.sku:
dmi.product.version: V1.00
dmi.sys.vendor: Acer
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884232/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe :
[Kernel-packages] [Bug 1953613] Re: GPIO character device v1 API not enabled in kernel
This bug is awaiting verification that the linux-nvidia/5.15.0-1007.7 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-allwinner-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1953613 Title: GPIO character device v1 API not enabled in kernel Status in linux package in Ubuntu: Fix Released Status in linux-allwinner-5.17 package in Ubuntu: Invalid Status in linux-hwe-5.17 package in Ubuntu: Invalid Status in linux-starfive-5.17 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-allwinner-5.17 source package in Jammy: Fix Released Status in linux-hwe-5.17 source package in Jammy: Fix Committed Status in linux-starfive-5.17 source package in Jammy: Fix Released Bug description: [Impact] * The libgpiod2 library and gpiod tools shipped in Jammy don't work. * These tools are meant to replace the old sysfs interface and be a better and more efficient way to manipulate GPIOs from userspace. Unfortunately the latest release is still using v1 of the character device kernel API which is not enabled in Ubuntu kernels. * This is Kent Gibsons reply on the linux-gpio mailing list: On Tue, Jul 12, 2022 at 09:48:45AM +0200, Alexandre Ghiti wrote: > Hi, > > Ubuntu kernels do not enable GPIO_CDEV_V1 as it is deprecated, but the > libgpiod package that we ship is still based on the latest version > 1.6.3 which does not implement the API v2. So I'd like to update > libgpiod, do you have any recommendations about what branch/sha1 I > should use? Do you plan to make a release that implements the API v2? > Firstly, libgpiod is Bart's library so he is the authority, but this is my understanding... TLDR: You should keep GPIO_CDEV_V1 enabled. v1 is deprecated from a development perspective, so all new feature development will occur on v2, and new applications should target v2. Existing apps targetting v1, be that directly or via libgpiod v1.6.3, will require GPIO_CDEV_V1 until they migrate to v2. The mainline kernel will continue to support v1 while userspace transitions. libgpiod v2 is in active development, and should reach its first release shortly. Note that it is NOT a plugin replacement for v1. It has a different API, for similar reasons to why we had to switch in the kernel, so apps will need to be actively migrated. I wouldn't suggest making any effort to package libgpiod v2 until Bart makes an official release. Cheers, Kent. [Test Plan] * Run gpioinfo on a machine with exposed GPIOs and check that it lists the GPIOs and doesn't error with gpioinfo: error creating line iterator: Invalid argument [Where problems could occur] * There may be code and scripts that hasn't been tested with a working libgpiod2/gpiod tools and uncover latent bugs. [Other Info] Original bug text: The current versions of gpiod, libgpiod-dev and libgpiod2 (1.6.2-1) use version 1 of the GPIO character device API. However, they cannot work because the interface is disabled in the default kernel (tested with 5.13.19). After rebuilding the kernel with the option CONFIG_GPIO_CDEV_V1=y, the gpiod tools work as expected. Thanks to Marek Szuba, who reported the same bug for Gentoo (https://bugs.gentoo.org/807334), pointing me in the right direction. What I expect to happen: $ gpiodetect gpiochip0 [0-003c] (8 lines) $ gpioinfo gpiochip0 - 8 lines: line 0: unnamed unused output active-high line 1: unnamed unused output active-high line 2: unnamed unused output active-high line 3: unnamed unused output active-high line 4: unnamed unused output active-high line 5: unnamed unused output active-high line 6: unnamed unused input active-high line 7: unnamed unused input active-high $ gpioget gpiochip0 0 1 What actually happens: $ gpiodetect gpiochip0 [0-003c] (8 lines) $ gpioinfo gpioinfo: error creating line iterator: Invalid argument $ gpioget gpiochip0 0 gpioget: error reading GPIO values: Invalid argument $ cat /proc/version_signature Ubuntu 5.13.0-22.22-lowlatency 5.13.19 $ apt-cache policy libgpiod2 libgpiod2: Installed: 1.6.2-1 Candidate: 1.6.2-1
[Kernel-packages] [Bug 1966010] Re: Fix audio on Zbook Studio G9
This bug is awaiting verification that the linux-nvidia/5.15.0-1007.7 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1966010 Title: Fix audio on Zbook Studio G9 Status in HWE Next: Fix Released Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix 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 Bug description: [Impact] Cirrus Logic AMP still doesn't work on Zbook Studio G9. Moreoever, The audio mute LEDs stop working after the said SRU. [Fix] Correcly interpret the debounce time from ACPI to gpiolib, and apply the correct quirk for the audio mute LEDs. [Where problems could occur] It's possible that some hardwares rely on the "wrong" debounce time to work, however the fix is to increase the debounce time, so it's more forgiving than decreasing. The LED fix is only applied to one system, so it's specifi and won't cause too much trouble. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1966010/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1978915] Re: alsa/hda: mute led can't work on the lenovo machine with cs35l41 s-codec
This bug is awaiting verification that the linux-nvidia/5.15.0-1007.7 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1978915 Title: alsa/hda: mute led can't work on the lenovo machine with cs35l41 s-codec 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: Won't Fix 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 Bug description: The fix is already in the upstream kernel stable-v5.17, no need to send this patch to oem-5.17 and unstable kernels. [Impact] After we apply the cs35l41 s-codec patchset to the oem-5.14 and jammy kernels, the mute led can't work anymore. [Fix] Backport a patch from mainline kernel to fix this regression [Test] boot the patched kernel, press mute hotkey, the speaker is muted and the mute led is on, press the mute hotkey again, the speaker is unmuted and the mute led is off. [Where problems could occur] After merging this patch, it is possible to affect the machines which apply the ALC287_FIXUP_CS35L41_I2C_2, but the regression possibility is very low since hda_fixup_thinkpad_acpi() could check if the quirk is suitable for the running machine. And we did test, all machines could work well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1978915/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1981390] Re: Mass Storage Gadget driver truncates device >2TB
This bug is awaiting verification that the linux-nvidia/5.15.0-1007.7
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy' to 'verification-done-jammy'. If the
problem still exists, change the tag 'verification-needed-jammy' to
'verification-failed-jammy'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1981390
Title:
Mass Storage Gadget driver truncates device >2TB
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Fix Released
Bug description:
[Impact]
I tried to use f_mass_storage to expose a 16TB hard drive attached to
Raspberry Pi to another computer.
On the remote computer the recognised drive has incorrect capacity and the
data is truncated.
After some debugging I noted the problem is caused by a bug in the
read capacity function of f_mass_storage in kernel version prior to
5.15, which had already been fixed upstream in mainline kernel since
v5.16
https://lore.kernel.org/all/20210914052728.23369-1-nikita.yo...@cogentembedded.com/
I tried the kernel from https://github.com/raspberrypi/linux version
rpi-5.16.y and confirmed that the problem is fixed at v5.16.
I wonder if the fix can be backported to the Ubuntu kernel.
Thank you very much!
Current kernel package version: linux-raspi (5.15.0-1011.13) jammy
Hardware: Raspberry Pi 4B
[Fix]
Backport commit bedbac5f66bf ("usb: gadget: storage: add support for
media larger than 2T")
[Test case]
See above.
[Where problems could occur]
Modifications are limited to the USB gadget mass storage driver, so
problems should only be seen on a client that uses this driver to
expose a USB drive to an attached USB host.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1981390/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1981783]
Model Name: ASUS ZenBook13 UX325J BIOS Version: 311 CPU: Intel Core(TM) i7-10 65G7 CPU @ 1.30GHz GPU: Intel Iris(R) Plus Graphics OS: Ubuntu 22.04.1 LTS (GNU/Linux 5.15.0-48-generic x86_64) / Windows 11 I made 'sudo apt-get dist-upgrade' on 22-Sep-2022, followed by I lost an access to Ubuntu GUI. Everytime I try to login, following error message is shown and only tty access is available. -- Error message -- [ 0.076056] x86/cpu: SGX disabled by BIOS. [ 0.130860] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCIO.I2CO.TPDO], AE_NOT_FOUND (20210730/dswload2-162) [ 0.130868] ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20210730/psobject-220) [ 0.130895] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCIO.I2C1.TPL1], AE_NOT_FOUND (20210730/dswload2-162) [ 0.130898] ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20210730/psobject-220) [ 0.561376] pci :00:07.0: DPC: RP PI0 log size 0 is invalid [ 0.563606] pci :00:07.1: DPC: RP PI0 log size 0 is invalid /dev/nvme0n1p4: clean, 604301/22405120 files, 35951873/89599744 blocks [ 1.862340] mtd device must be supplied (device name is empty) [ 2.167925] mtd device must be supplied (device name is empty) [ 2.369446] mtd device must be supplied (device name is empty) [ 4.033184] ucsi_acpi USBC000:00: PPN init failed (-110) -- 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/1981783 Title: there is an ACPI error message every time it booting Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: there is the following message every time it boots [0.290526] ACPI BIOS Error (bug) : Could not resolve symbol [\_PR.CPU0._CPC]AE_NOT_FOUND (20210730/psargs-529) [0.290884] ACPI Error: Aborting method \_PR.CPU1._CPC due to previous error (AE_NOT_FOUND (20210730/psargs-529) [0.290526] ACPI BIOS Error (bug) : Could not resolve symbol [\_PR.CPU0._CPC]AE_NOT_FOUND (20210730/psargs-529) [0.290884] ACPI Error: Aborting method \_PR.CPU2._CPC due to previous error (AE_NOT_FOUND (20210730/psargs-529) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.38 ProcVersionSignature: Ubuntu 5.15.0-41.44~20.04.1-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Jul 15 11:15:30 2022 InstallationDate: Installed on 2022-04-21 (85 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1981783/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1983143] Re: AMD Rembrandt: DP tunneling fails with Thunderbolt monitors
This bug is awaiting verification that the linux-nvidia/5.15.0-1007.7 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1983143 Title: AMD Rembrandt: DP tunneling fails with Thunderbolt monitors Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Bug description: [Summary] No video output on Thunderbolt monitor. 1. Connect monitor to DUT directly 2. Connect monitor to DUT via Docking System can detect the monitor and able to change display mode but no output on the monitor [Steps to reproduce] 1. Boot to OS 2. Plug an external monitor via thunderbolt port [Expected result] Display on external monitor normally [Actual result] No vidoe ouput on external monitor [Failure rate] 3/3 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1983143/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1980925] Re: [SRU] bcache deadlock during read IO in writeback mode
This bug is awaiting verification that the linux-nvidia/5.15.0-1007.7 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1980925 Title: [SRU] bcache deadlock during read IO in writeback mode Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux source package in Jammy: Fix Released Bug description: SRU Justification: [Impact] When Random Read I/O is started with a test like - fio --name=read_iops --directory=/home/ubuntu/bcache_mount/ --size=16G --ioengine=libaio --direct=1 --verify=0 --bs=4K --iodepth=128 --rw=randread --randrepeat=0 or random read-writes with a test like, fio --filename=/home/ubuntu/bcache_mount/cachedfile --size=15GB --direct=1 --rw=randrw --bs=4k --ioengine=libaio --iodepth=128 --name=iops-test-job --randrepeat=0 traces are seen in the kernel log, [ 4473.699902] INFO: task bcache_writebac:1835 blocked for more than 120 seconds. [ 4474.050921] Not tainted 5.15.50-051550-generic #202206251445 [ 4474.350883] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 4474.731391] task:bcache_writebac state:D stack:0 pid: 1835 ppid: 2 flags:0x4000 [ 4474.731408] Call Trace: [ 4474.731411] [ 4474.731413] __schedule+0x23d/0x5a0 [ 4474.731433] schedule+0x4e/0xb0 [ 4474.731436] rwsem_down_write_slowpath+0x220/0x3d0 [ 4474.731441] down_write+0x43/0x50 [ 4474.731446] bch_writeback_thread+0x78/0x320 [bcache] [ 4474.731471] ? read_dirty_submit+0x70/0x70 [bcache] [ 4474.731487] kthread+0x12a/0x150 [ 4474.731491] ? set_kthread_struct+0x50/0x50 [ 4474.731494] ret_from_fork+0x22/0x30 [ 4474.731499] The bug exists till kernel 5.15.50-051550-generic The reproducer is pasted below: # uname -a Linux bronzor 5.15.50-051550-generic #202206251445 SMP Sat Jun 25 14:51:22 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux NAMEMAJ:MIN RM SIZE RO TYPE MOUNTPOINTS sdd 8:48 0 279.4G 0 disk └─sdd18:49 060G 0 part └─bcache0 252:0060G 0 disk /home/ubuntu/bcache_mount nvme0n1 259:00 372.6G 0 disk └─nvme0n1p1 259:2015G 0 part └─bcache0 252:0060G 0 disk /home/ubuntu/bcache_mount fio --name=read_iops --directory=/home/ubuntu/bcache_mount --size=12G --ioengine=libaio --direct=1 --verify=0 --bs=4K --iodepth=128 --rw=randread --group_reporting=1 read_iops: (g=0): rw=randread, bs=(R) 4096B-4096B, (W) 4096B-4096B, (T) 4096B-4096B, ioengine=libaio, iodepth=128 fio-3.28 Starting 1 process read_iops: Laying out IO file (1 file / 12288MiB) The test does not progress beyond a few minutes, and this trace is then seen in the kernel log, [ 4473.699902] INFO: task bcache_writebac:1835 blocked for more than 120 seconds. [ 4474.050921] Not tainted 5.15.50-051550-generic #202206251445 [ 4474.350883] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 4474.731391] task:bcache_writebac state:D stack:0 pid: 1835 ppid: 2 flags:0x4000 [ 4474.731408] Call Trace: [ 4474.731411] [ 4474.731413] __schedule+0x23d/0x5a0 [ 4474.731433] schedule+0x4e/0xb0 [ 4474.731436] rwsem_down_write_slowpath+0x220/0x3d0 [ 4474.731441] down_write+0x43/0x50 [ 4474.731446] bch_writeback_thread+0x78/0x320 [bcache] [ 4474.731471] ? read_dirty_submit+0x70/0x70 [bcache] [ 4474.731487] kthread+0x12a/0x150 [ 4474.731491] ? set_kthread_struct+0x50/0x50 [ 4474.731494] ret_from_fork+0x22/0x30 [ 4474.731499] [Fix] These 3 fixes are needed for the SRU. dea3560e5f31965165bcf34ecf0b47af28bfd155, 6445ec3df23f24677064a327dce437ef3e02dc6, dc60301fb408e06e0b718c0980cdd31d2b238bee I have built these fixes into kernel 5.15.0-39-generic (jammy) and tested to verify the problem is fixed. [Regression Potential] Regression potential should be minimal. I have not seen any potential drawbacks or harmful effects of this fix in my testing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1980925/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1983498] Re: Jammy: Add OVS Internal Port HW Offload to mlx5 driver
This bug is awaiting verification that the linux-nvidia/5.15.0-1007.7 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1983498 Title: Jammy: Add OVS Internal Port HW Offload to mlx5 driver Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Bug description: SRU Justification [Impact] A request has been made, originating from https://bugs.launchpad.net/bugs/1980730, to add support for OVS internal port offload for the mlx5 driver. This feature takes care of certain traffic workloads that are not currently being offloaded to the hardware. [Test Case] Tested by the requester. [Where things could go wrong] These changes could potentially introduce regressions in behavior of the mlx5 driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1983498/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1983640] Re: refactoring of overlayfs fix to properly support shiftfs
This bug is awaiting verification that the linux-nvidia/5.15.0-1007.7
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy' to 'verification-done-jammy'. If the
problem still exists, change the tag 'verification-needed-jammy' to
'verification-failed-jammy'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1983640
Title:
refactoring of overlayfs fix to properly support shiftfs
Status in linux package in Ubuntu:
Fix Committed
Status in linux-hwe-5.17 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Fix Released
Status in linux-hwe-5.17 source package in Jammy:
Fix Committed
Status in linux source package in Kinetic:
Fix Committed
Status in linux-hwe-5.17 source package in Kinetic:
Invalid
Bug description:
[Impact]
Starting with 5.13 we've incorrectly dropped the following sauce
patch:
UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened
from map_files
This patch is required to use overlayfs on top of shiftfs and without
this patch we may break containers that rely on shiftfs (using
zfs/ceph as storage pool w/ shiftfs enabled).
However, we made this patch dependent on AUFS, starting with Jammy
we're not enabling AUFS anymore, so this fix becomes a no-op.
So we need to re-introduce this fix with a bit of refactoring to not
depend on AUFS.
[Test case]
The following script can be used to trigger the issue:
#!/bin/bash
cat > test.py << EOF
import sys
f = open("/proc/self/maps")
for l in f.readlines():
if "python" not in l:
continue
print(l)
s = l.split()
start, end = s[0].split("-")
fname = s[-1]
print(start, end, fname)
break
else:
sys.exit(1)
test_file1 = open(fname)
test_file2 = open("/proc/self/map_files/%s-%s" % (start, end))
fdinfo1 = open("/proc/self/fdinfo/%d" % test_file1.fileno()).read()
fdinfo2 = open("/proc/self/fdinfo/%d" % test_file2.fileno()).read()
if fdinfo1 != fdinfo2:
print("FAIL")
print(test_file1)
print(fdinfo1)
print(test_file2)
print(fdinfo2)
sys.exit(1)
print("PASS")
EOF
sudo docker run -it --privileged --rm -v `pwd`:/mnt python python
/mnt/test.py
[Fix]
Import the right pieces from AUFS to properly support the fix and get
rid of the AUFS dependency across all our kernels and re-apply the
overlayfs fix without the AUFS dependency.
[Regression potential]
This patch is touching overlayfs, so we may see potential regressions
in overlayfs, especially when containers are used.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1983640/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1986798] Re: Remove unused variable from i915 psr
This bug is awaiting verification that the linux-nvidia/5.15.0-1007.7
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy' to 'verification-done-jammy'. If the
problem still exists, change the tag 'verification-needed-jammy' to
'verification-failed-jammy'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1986798
Title:
Remove unused variable from i915 psr
Status in linux package in Ubuntu:
Won't Fix
Status in linux source package in Jammy:
Fix Released
Bug description:
[Impact]
Compiler warns unused variable after commit 0c1d6921b07c ("UBUNTU:
SAUCE: drm/i915/display/psr: Reinstate fix for TGL + AUO panel flicker")
[Fix]
The variable is unused, remove it.
[Test]
Compiler no longer warns about it.
[Where problems could occur]
Nothing.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1986798/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1957026] Re: AMD Yellow Carp DMCUB fw update for s0i3 B0 fixes
This bug is awaiting verification that the linux-nvidia/5.15.0-1007.7 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1957026 Title: AMD Yellow Carp DMCUB fw update for s0i3 B0 fixes Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-firmware 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-firmware source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [SRU Justification] [Impact] On AMD Yellow Carp B0 platforms, S0i3 is still not working. [Fix] This denpends on a few fixes for kernel driver that are all either in v5.17-rc1 or in stable linux-5.1x.y, along with an already upstreamed dmcub firmware. [Test Case] On AMD RMT CRB board, 1. apply both kernel and firmware fixes 2. module blacklist amd_sfh as it's still under development, 3. trigger system suspend. Use power button to wake up the device. 4. check /sys/kernel/debug/amd_pmc/s0ix_stats, the values shall be non-zero On without any of above, the board may not cut device power during suspend, and/or fail to resume and leaving a blank screen, and/or s0ix stats remain all zeros. [Where problems could occur] On AMD RMT CRB board, Sensor Fusion Hub (amd_sfh) still doesn't support S0ix and has to be disabled. For the kernel side, the driver fixes addressed a few procedure errors that should be unlikely to introduce regressions; for the firmware side, also tested loading new firmware on unpatched kernels and there is no difference found yet. [Other Info] For kernel driver fixes, patches for both oem-5.14 and jammy are necessary; for firmware, that has been available in jammy branch but not yet released, so only Focal will be nominated. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1957026/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
This bug is awaiting verification that the linux-nvidia/5.15.0-1007.7 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/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 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 1989521] Re: Ubuntu 22.04.1 CPU soft lockup occurs repeatedly
Following this: https://askubuntu.com/questions/1264859/watchdog-bug-soft-lockup-cpu6-stuck-for-23s I attempted a BIOS update and verifying my swap was working properly. Also reseated my GPU and still no luck. -- 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/1989521 Title: Ubuntu 22.04.1 CPU soft lockup occurs repeatedly Status in linux package in Ubuntu: Confirmed Bug description: Hi all, Ubuntu server 22.04.1 is having issues freezing repeatedly with CPU softlocking. The issue seems to have started in the last week, all packages are up to date. I've updated to hwe kernel, rebooted several times, and it still happens. Hw info: 32G RAM, AMD 3600x CPU, Quadro RTX 4000 GPU. I caught the following in syslog : Sep 13 04:17:55 marcus-server kernel: [33687.436241] watchdog: BUG: soft lockup - CPU#2 stuck for 26s! [kworker/u64:17:154214] Sep 13 04:17:55 marcus-server kernel: [33687.436243] Modules linked in: tls xt_nat veth nf_conntrack_netlink xfrm_user xfrm_algo xt_addrtype br_netfilter xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp nft_compat nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nft_counter nf_tables nfnetlink overlay bridge stp llc nvidia_drm(PO) snd_hda_codec_realtek intel_rapl_msr intel_rapl_common nvidia_modeset(PO) snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec snd_hda_core snd_hwdep snd_pcm snd_seq_midi snd_seq_midi_event zfs(PO) edac_mce_amd nls_iso8859_1 snd_rawmidi kvm_amd zunicode(PO) nvidia(PO) snd_seq kvm zzstd(O) zlua(O) zavl(PO) snd_seq_device icp(PO) rapl wmi_bmof snd_timer zcommon(PO) k10temp ccp ucsi_ccg znvpair(PO) snd typec_ucsi typec spl(O) soundcore apex(OE) gasket(OE) mac_hid sch_fq_codel dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua nct6775 hwmon_vid ipmi_devi ntf ipmi_msghandler msr parport_pc ppdev lp Sep 13 04:17:55 marcus-server kernel: [33687.436279] parport ramoops reed_solomon pstore_blk pstore_zone mtd efi_pstore ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear nouveau mxm_wmi drm_ttm_helper ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops cec rc_core crct10dif_pclmul crc32_pclmul ghash_clmulni_intel drm aesni_intel video crypto_simd igb cryptd xhci_pci ahci dca i2c_piix4 i2c_nvidia_gpu arcmsr libahci xhci_pci_renesas i2c_algo_bit wmi Sep 13 04:17:55 marcus-server kernel: [33687.436302] CPU: 2 PID: 154214 Comm: kworker/u64:17 Tainted: P OE 5.15.0-47-generic #51-Ubuntu Sep 13 04:17:55 marcus-server kernel: [33687.436303] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./X570 Phantom Gaming 4, BIOS P4.20 08/02/2021 Sep 13 04:17:55 marcus-server kernel: [33687.436305] Workqueue: events_unbound async_run_entry_fn Sep 13 04:17:55 marcus-server kernel: [33687.436308] RIP: 0010:arcmsr_wait_firmware_ready+0xc1/0x140 [arcmsr] Sep 13 04:17:55 marcus-server kernel: [33687.436312] Code: e3 49 8b 94 24 48 08 00 00 b8 10 00 00 00 89 02 5b 41 5c 5d e9 b0 7b db e8 48 8b 47 50 4c 8d a0 bc 00 00 00 eb 0c 41 8b 04 24 <85> c0 0f 88 64 ff ff ff f6 83 81 00 00 00 01 75 eb bf 14 00 00 00 Sep 13 04:17:55 marcus-server kernel: [33687.436313] RSP: 0018:ade8d136fd10 EFLAGS: 0202 Sep 13 04:17:55 marcus-server kernel: [33687.436314] RAX: RBX: 96720a460870 RCX: ade8c12b0034 Sep 13 04:17:55 marcus-server kernel: [33687.436315] RDX: 000d RSI: 96721b53ef80 RDI: 96720a460870 Sep 13 04:17:55 marcus-server kernel: [33687.436315] RBP: ade8d136fd20 R08: R09: Sep 13 04:17:55 marcus-server kernel: [33687.436316] R10: 0284 R11: R12: ade8c12b00bc Sep 13 04:17:55 marcus-server kernel: [33687.436317] R13: 000d R14: 96720a46 R15: 96720a460870 Sep 13 04:17:55 marcus-server kernel: [33687.436318] FS: () GS:96791ea8() knlGS: Sep 13 04:17:55 marcus-server kernel: [33687.436319] CS: 0010 DS: ES: CR0: 80050033 Sep 13 04:17:55 marcus-server kernel: [33687.436320] CR2: CR3: 0007c8c1 CR4: 00350ee0 It happens pretty often too, but the system isn't overloaded, so I'm not sure what is causing it. Message from syslogd@marcus-server at Sep 14 02:16:11 ... kernel:[ 1276.914096] watchdog: BUG: soft lockup - CPU#8 stuck for 26s! [kworker/u64:28:252938] Message from syslogd@marcus-server at Sep 14 02:16:11 ... kernel:[ 1304.913956] watchdog: BUG: soft lockup - CPU#8 stuck for 52s! [kworker/u64:28:252938] Message from syslogd@marcus-server at Sep 14 02:37:47
[Kernel-packages] [Bug 1958770] Re: Aquantia GbE LAN driver causes UBSAN error during kernel boot
Present in 5.15.0-50-lowlatency . Continues the trend where tainted in the Generic version of the kernel, but not the lowlatency version. 9/22/22 1:41 PM kernel 9/22/22 1:41 PM kernel UBSAN: array-index-out-of-bounds in /build/linux-lowlatency-jwscnu/linux-lowlatency-5.15.0/drivers/net/ethernet/aquantia/atlantic/aq_nic.c:1262:48 9/22/22 1:41 PM kernel index 8 is out of range for type 'aq_vec_s *[8]' 9/22/22 1:41 PM kernel CPU: 22 PID: 2103 Comm: daemon-init Not tainted 5.15.0-50-lowlatency #56-Ubuntu 9/22/22 1:41 PM kernel Hardware name: To Be Filled By O.E.M. X570 Creator/X570 Creator, BIOS P3.72 05/17/2022 9/22/22 1:41 PM kernel Call Trace: 9/22/22 1:41 PM kernel 9/22/22 1:41 PM kernel show_stack+0x52/0x5c 9/22/22 1:41 PM kernel dump_stack_lvl+0x4a/0x63 9/22/22 1:41 PM kernel dump_stack+0x10/0x16 9/22/22 1:41 PM kernel ubsan_epilogue+0x9/0x49 9/22/22 1:41 PM kernel __ubsan_handle_out_of_bounds.cold+0x44/0x49 9/22/22 1:41 PM kernel ? dev_fetch_sw_netstats+0x48/0x90 9/22/22 1:41 PM kernel ? aq_vec_stop+0x72/0x80 [atlantic] 9/22/22 1:41 PM kernel aq_nic_stop+0x1b6/0x1c0 [atlantic] 9/22/22 1:41 PM kernel aq_ndev_set_features+0x143/0x1a0 [atlantic] 9/22/22 1:41 PM kernel __netdev_update_features+0x184/0x820 9/22/22 1:41 PM kernel dev_disable_lro+0x34/0x150 9/22/22 1:41 PM kernel devinet_sysctl_forward+0x1fb/0x230 9/22/22 1:41 PM kernel proc_sys_call_handler+0x161/0x2d0 9/22/22 1:41 PM kernel proc_sys_write+0x13/0x20 9/22/22 1:41 PM kernel new_sync_write+0x114/0x1a0 9/22/22 1:41 PM kernel vfs_write+0x1fb/0x290 9/22/22 1:41 PM kernel ksys_write+0x67/0xf0 9/22/22 1:41 PM kernel __x64_sys_write+0x19/0x20 9/22/22 1:41 PM kernel do_syscall_64+0x5c/0xc0 9/22/22 1:41 PM kernel entry_SYSCALL_64_after_hwframe+0x61/0xcb 9/22/22 1:41 PM kernel RIP: 0033:0x7f492a2f6a6f 9/22/22 1:41 PM kernel Code: 89 54 24 18 48 89 74 24 10 89 7c 24 08 e8 19 c0 f7 ff 48 8b 54 24 18 48 8b 74 24 10 41 89 c0 8b 7c 24 08 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 31 44 89 c7 48 89 44 24 08 e8 5c c0 f7 ff 48 9/22/22 1:41 PM kernel RSP: 002b:7f48fe7fb810 EFLAGS: 0293 ORIG_RAX: 0001 9/22/22 1:41 PM kernel RAX: ffda RBX: 0002 RCX: 7f492a2f6a6f 9/22/22 1:41 PM kernel RDX: 0002 RSI: 7f492ac7e5e5 RDI: 0013 9/22/22 1:41 PM kernel RBP: 7f492ac7e5e5 R08: R09: 0001 9/22/22 1:41 PM kernel R10: R11: 0293 R12: 0013 9/22/22 1:41 PM kernel R13: 0013 R14: R15: 7f48dc030970 9/22/22 1:41 PM kernel 9/22/22 1:41 PM kernel -- 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/1958770 Title: Aquantia GbE LAN driver causes UBSAN error during kernel boot Status in linux package in Ubuntu: Confirmed 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 Bug description: The undefined behaviour sanitiser picks up an array-index-out-of- bounds in the aquantia atlantic driver. The NIC is (I think) built into my gigabyte motherboard (https://www.gigabyte.com/uk/Motherboard/X399-AORUS-XTREME- rev-10/sp#sp). This wasn't an issue before I upgrading from 20.04 to 22.04 (or at least dmesg didn't previously complain). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-17-generic 5.15.0-17.17 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Jan 23 13:02:10 2022 InstallationDate: Installed on 2019-08-07 (899 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Gigabyte Technology Co., Ltd. X399 AORUS XTREME ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-17-generic root=UUID=08f6326a-30f9-4f23-bab7-72a48afad354 ro quiet splash resume=UUID=08f6326a-30f9-4f23-bab7-72a48afad354 resume_offset=34816 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-17-generic N/A linux-backports-modules-5.15.0-17-generic N/A linux-firmware 1.204 SourcePackage:
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-azure/5.15.0.1021.20)
All autopkgtests for the newly accepted linux-meta-azure (5.15.0.1021.20) for jammy have finished running. The following regressions have been reported in tests triggered by the package: digimend-dkms/10-4 (amd64, arm64) lttng-modules/2.13.1-1ubuntu0.22.04.1 (amd64, arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#linux-meta-azure [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 1990167] Re: cma alloc failure in large 5.15 arm instances
This bug is awaiting verification that the linux-azure/5.15.0-1021.26 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1990167 Title: cma alloc failure in large 5.15 arm instances Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Jammy: Fix Committed Status in linux-aws source package in Kinetic: Invalid Bug description: When launching large arm64 instances on the focal or jammy ami, cma allocation errors appear in the dmesg out: [0.063255] cma: cma_alloc: reserved: alloc failed, req-size: 4096 pages, ret: -12 As far as I can tell, this does not impact instance launch in a meaningful way, but I am unsure of the other implications of this. I was able to confirm that these messages are only present in 5.15, as they do not show up in the bionic image, and rolling back focal to linux-aws 5.4 avoids them as well. This was present in at least 2 instance types and only appears to pop up in large sizes (2x4 does not produce them, 64x124 (c6gn.16xlarge) does) This could be as simple as just disabling CMA in the linux-aws pkg, as it appears this is already the case in linux-azure(LP: #1949770). Attaching dmesg out to the report. # Replication + Launch a large arm64 instance (c6gn.16xlarge) + Observe the messages in kern.log / dmesg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1990167/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1990184] Re: Azure: Enable vPCI multi-MSI interrupts
This bug is awaiting verification that the linux-azure/5.15.0-1021.26 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1990184 Title: Azure: Enable vPCI multi-MSI interrupts Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Jammy: Fix Committed Bug description: SRU Justification [Impact] This is a 2nd attempt with this patch set. The first attempt [1] caused a regression. The Hyper-V vPCI driver (pci-hyperv) doesn't work with a PCIe devcie that supports multiple MSI interrupts (Note: MSI-X has been working fine). Recently Jeffrey Hugo made 4 patches to the vPCI driver so multiple-MSI can work now. Please consider picking up the 4 patches into the linux-azure kernels for Ubuntu LTS 18.04, 20.04 and 22.04: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=08e61e861a0e47e5e1a3fb78406afd6b0cea6b6d https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=455880dfe292a2bdd3b4ad6a107299fce610e64b https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b4b8ecc5bfbd4e77de1b2fd5c1dd3c655f1f https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=a2bad844a67b1c7740bda63e87453baf63c3a7f7 [1] https://bugs.launchpad.net/bugs/1981577 [Test Plan] Microsoft tested: " I tested the kernel and it worked as expected, i.e. we still have the multi-MSI capability and I no longer see the soft lockup issue with fio + NVMe + the L64s_v2 VM size." [Where things could go wrong] vPCI devices may no get interrupts [Other Info] SF: #00339521 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1990184/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1988797] Re: pcieport 0000:00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID)
** Tags added: originate-from-1976477 sutton -- 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/1988797 Title: pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected (Non- Fatal), type=Transaction Layer, (Requester ID) Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Confirmed Status in linux-oem-5.17 source package in Jammy: Fix Committed Status in linux-oem-6.0 source package in Jammy: Fix Committed Status in linux source package in Kinetic: Confirmed Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: My kernel log periodically bursts with: [10405.588287] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) [10405.593393] pcieport :00:1b.0: device [8086:7ac4] error status/mask=0010/4000 [10405.598564] pcieport :00:1b.0:[20] UnsupReq (First) [10405.603829] pcieport :00:1b.0: AER: TLP Header: 3400 0152 [10405.609563] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) [10405.614959] pcieport :00:1b.0: device [8086:7ac4] error status/mask=0010/4000 [10405.620296] pcieport :00:1b.0:[20] UnsupReq (First) [10405.625554] pcieport :00:1b.0: AER: TLP Header: 3400 0152 [10405.631180] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) [10405.636495] pcieport :00:1b.0: device [8086:7ac4] error status/mask=0010/4000 [10405.641867] pcieport :00:1b.0:[20] UnsupReq (First) [10405.647169] pcieport :00:1b.0: AER: TLP Header: 3400 0152 [10405.652919] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) [10405.658369] pcieport :00:1b.0: device [8086:7ac4] error status/mask=0010/4000 [10405.663803] pcieport :00:1b.0:[20] UnsupReq (First) [10405.669263] pcieport :00:1b.0: AER: TLP Header: 3400 0152 [10405.675130] pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) [10405.680699] pcieport :00:1b.0: device [8086:7ac4] error status/mask=0010/4000 [10405.686267] pcieport :00:1b.0:[20] UnsupReq (First) [10405.691759] pcieport :00:1b.0: AER: TLP Header: 3400 0152 This has happened even since I got the machine. It also happened with 5.15. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-15-generic 5.19.0-15.15 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dan2477 F wireplumber /dev/snd/seq:dan2474 F pipewire CRDA: N/A CasperMD5CheckResult: pass Date: Tue Sep 6 13:52:35 2022 InstallationDate: Installed on 2022-07-20 (47 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220718) MachineType: Intel(R) Client Systems NUC12DCMi7 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-15-generic root=UUID=a69020a6-a1dd-436c-b75a-be890a4063be ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.19.0-15-generic N/A linux-backports-modules-5.19.0-15-generic N/A linux-firmware 20220831.gitd3c92280-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/20/2021 dmi.bios.release: 5.24 dmi.bios.vendor: Intel Corp. dmi.bios.version: EDADL579.0046.2021.1220.2351 dmi.board.name: NUC12EDBi7 dmi.board.vendor: Intel Corporation dmi.board.version: M27908-302 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.ec.firmware.release: 3.7 dmi.modalias: dmi:bvnIntelCorp.:bvrEDADL579.0046.2021.1220.2351:bd12/20/2021:br5.24:efr3.7:svnIntel(R)ClientSystems:pnNUC12DCMi7:pvrM30143-302:rvnIntelCorporation:rnNUC12EDBi7:rvrM27908-302:cvnIntelCorporation:ct35:cvr2.0:skuRNUC12DCMi7: dmi.product.family: DC dmi.product.name: NUC12DCMi7 dmi.product.sku:
[Kernel-packages] [Bug 1989470] Re: BGP adjacency not established on linux-image-5.15.0-1019-aws
I have added a tcpdump to the github issue, if anybody wants to have a look. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1989470 Title: BGP adjacency not established on linux-image-5.15.0-1019-aws Status in linux-aws package in Ubuntu: New Bug description: We have a simple eBGP setup with a peer over IPsec using a VTI interface using frr (default BGP daemon in Ubuntu 22.04). Everything worked fine until we upgraded to the latest kernel available for our machine: linux-image-5.15.0-1019-aws. After that the adjacency would simply not come up. I have investigated for some time, and found no issues with the configuration (obviously, it was not modified since it was working fine) and also no other issues. There are no firewall rules on this machine. Also there is no issue with the IPsec and the VTI interface, traffic flows through it, the BGP neighbor is pingable etc. We have confirmed that downgrading to linux-image-5.15.0-1017-aws fixes the issue. According to tcpdump it seems like both ends initiate the connection, but then there are just a lot of TCP retransmissions and Duplicate ACKs after the OPEN messages. The other side sends a KEEPALIVE but FRR seems to be stuck getting it. Basically it looks like according to the tcpdump that after the initial exchange of messages the ACKs are not recognized properly by the kernel (?) and therefore continous retransmissions occur until the timer of BGP expires. Since other TCP applications (e.g. SSH) work fine I'm assuming this might be related to: - VTI interfaces - FRR itself To drive initiatives in parallel I have opened a bug at FRR as well: https://github.com/FRRouting/frr/issues/11943 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1989470/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1990587] Re: 13.3GB reserved by kernel sometimes on clean boot
** Package changed: ubuntu => linux-hwe-5.15 (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/1990587 Title: 13.3GB reserved by kernel sometimes on clean boot Status in linux-hwe-5.15 package in Ubuntu: New Bug description: Description:Ubuntu 22.04.1 LTS Release:22.04 Kernel: linux-image-5.15.0-48-generic Occasionally (twice today) a clean boot has left only 2GB of 16GB RAM usable. Looking at syslog - its clear the memory is being reserved for some reason by the kernel: Memory: 2558908K/16524372K available (16393K kernel code, 4377K rwdata, 10804K rodata, 3224K init, 6580K bss, 13965204K reserved, 0K cma-reserved) Usually the amount reserved is: Sep 22 11:35:57 pdlap01 kernel: [0.099454] Memory: 15926800K/16524372K available (16393K kernel code, 4377K rwdata, 10804K rodata, 3224K init, 6580K bss, 597312K reserved, 0K cma-reserved) Been using linux on this device for years - only noticed since 22.04.1. Both times today when it reserved 13GB - it was connected to the dell dock (dont know if that is relevant yet). No recent changes other than security updates - but I noticed it did this a month or so ago too - but hoped it was a one off. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.15/+bug/1990587/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1990587] [NEW] 13.3GB reserved by kernel sometimes on clean boot
You have been subscribed to a public bug: Description:Ubuntu 22.04.1 LTS Release:22.04 Kernel: linux-image-5.15.0-48-generic Occasionally (twice today) a clean boot has left only 2GB of 16GB RAM usable. Looking at syslog - its clear the memory is being reserved for some reason by the kernel: Memory: 2558908K/16524372K available (16393K kernel code, 4377K rwdata, 10804K rodata, 3224K init, 6580K bss, 13965204K reserved, 0K cma- reserved) Usually the amount reserved is: Sep 22 11:35:57 pdlap01 kernel: [0.099454] Memory: 15926800K/16524372K available (16393K kernel code, 4377K rwdata, 10804K rodata, 3224K init, 6580K bss, 597312K reserved, 0K cma-reserved) Been using linux on this device for years - only noticed since 22.04.1. Both times today when it reserved 13GB - it was connected to the dell dock (dont know if that is relevant yet). No recent changes other than security updates - but I noticed it did this a month or so ago too - but hoped it was a one off. ** Affects: linux-hwe-5.15 (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- 13.3GB reserved by kernel sometimes on clean boot https://bugs.launchpad.net/bugs/1990587 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.15 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 1990595] Re: Kernel Module usbserial not available on Jammy 22.04 (Raspi 4)
These modules are provided by linux-modules, not linux-modules-extra: $ dpkg -L linux-modules-5.15.0-1015-raspi | grep -E 'usbserial|ftdi' /lib/modules/5.15.0-1015-raspi/kernel/drivers/usb/serial/ftdi_sio.ko /lib/modules/5.15.0-1015-raspi/kernel/drivers/usb/serial/usbserial.ko ** Changed in: linux-raspi (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1990595 Title: Kernel Module usbserial not available on Jammy 22.04 (Raspi 4) Status in linux-raspi package in Ubuntu: Invalid Bug description: After installing a USB to Serial Adapter on a Raspberry Pi 4 running Ubuntu Server 22.04 LTS, no tty device is created under /dev/ttyUSB... dmesg: [3.793123] usb 1-1.2.1: New USB device found, idVendor=0403, idProduct=6001, bcdDevice= 6.00 [3.793142] usb 1-1.2.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [3.793149] usb 1-1.2.1: Product: FT232R USB UART [3.793155] usb 1-1.2.1: Manufacturer: FTDI [3.793160] usb 1-1.2.1: SerialNumber: A504D2PO The usbserial and ftdi_sio kernel modules are not included in the linux-modules-extra-5.15.0-1015-raspi package. dpkg-query -L linux-modules-extra-5.15.0-1015-raspi |grep -E 'usbserial|ftdio_sio' => NO OUTPUT lsb_release -rd: Description:Ubuntu 22.04.1 LTS Release:22.04 uname -a: Linux Host 5.15.0-1014-raspi #16-Ubuntu SMP PREEMPT Thu Aug 25 09:50:55 UTC 2022 aarch64 aarch64 aarch64 GNU/Linux For Reference: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1947723 Configuration from /boot/config-5.15.0-1014-raspi: grep USB_SERIAL /boot/config-5.15.0-1014-raspi CONFIG_USB_SERIAL=m <= set CONFIG_USB_SERIAL_GENERIC=y <= set CONFIG_USB_SERIAL_FTDI_SIO=m <= set Fix: According to the configuration, the modules should be built. Include the modules in the package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1990595/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1952674] Re: Kernel 5.13 fails to work with lots of hardware (HP Zbook)
I have a HP ZBook and 5.19 has not solved this for me. I cannot use my external monitor unless I revert back to 5.10, I have not attempted 5.13, but I don't think it matters that much, I would just like to use the up-to-date kernels if possible :) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1952674 Title: Kernel 5.13 fails to work with lots of hardware (HP Zbook) Status in linux-signed-hwe-5.13 package in Ubuntu: Confirmed Bug description: The Internal display does not work. External monitors connected via Thunderbolt down continue to work. The trackpad does not work. The keyboard does work. The Ethernet on the Thunderbolt dock does not work. Booting the 5.11 kernel allows everything to work. I'm not sure how useful the automatically-attached files are since I had to boot with 5.11 in order to get the network working. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-22-generic 5.13.0-22.22~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-41.45~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Nov 30 10:37:03 2021 InstallationDate: Installed on 2021-08-30 (91 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: linux-signed-hwe-5.13 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.13/+bug/1952674/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
