[Kernel-packages] [Bug 2008217] Re: Unsolicited wake from suspend with bluetooth connected (Intel AX211)
** Tags added: kern-5809 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2008217 Title: Unsolicited wake from suspend with bluetooth connected (Intel AX211) Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: In Progress Status in linux-firmware source package in Lunar: Fix Released Bug description: [Summary] The system will auto wake from suspend with bluetooth connected. Note: 1. BT headset, BT Keyboard and BT mouse all can duplicate 2. RTL 8852BE & Intel AX201 cannot duplicate [Steps to reproduce] 1. Install dell-bto-jammy-jellyfish-quilladin-X72-20230216-17.iso 2. Boot to OS 3. Pair the bluetooth headset device. 4. Enter suspend. [Expected result] The system will not auto wake when the bluetooth device is connected. [Actual result] The system will auto wake from suspend with bluetooth connected. [Failure rate] 3/10 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2008217/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008224] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/2008224/+attachment/5649732/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2008224 Title: Intel MIPI Camera does not work on Ubuntu 22.04.02 Status in linux package in Ubuntu: Incomplete Status in v4l2-relayd package in Ubuntu: Invalid Status in linux source package in Jammy: Confirmed Status in v4l2-relayd source package in Jammy: Invalid Bug description: Install Ubuntu 22.04.02 daily build (2023-02-23), the camera does not work with Google Meet and any sort of camera application. [steps] 1. boot into OS 2. check kernel log [rate] 1/3 [kernel] [ 3.169297] intel-ipu6 intel-ipu: enabling device ( -> 0002) [ 3.169665] intel-ipu6 intel-ipu: Device 0x465d (rev: 0x1) [ 3.169682] intel-ipu6 intel-ipu: physical base address 0x603e00 [ 3.169683] intel-ipu6 intel-ipu: mapped as: 0xd0bf5156 [ 3.169729] intel-ipu6 intel-ipu: Unable to set secure mode [ 3.169730] intel-ipu6 intel-ipu: IPU in non-secure mode [ 3.169731] intel-ipu6 intel-ipu: IPU secure touch = 0x0 [ 3.169731] intel-ipu6 intel-ipu: IPU camera mask = 0xff [ 3.170713] intel-ipu6 intel-ipu: Skip ipc reset for non-secure mode [ 3.170714] intel-ipu6 intel-ipu: IPC reset done [ 3.170715] intel-ipu6 intel-ipu: cpd file name: intel/ipu6ep_fw.bin [ 3.171885] intel-ipu6 intel-ipu: FW version: 20220510 [ 3.174214] intel-ipu6 intel-ipu: IPU6-v3 driver version 1.0 [ 3.218000] intel-ipu6-psys intel-ipu6-psys0: pkg_dir entry count:8 [ 3.218094] intel-ipu6-psys intel-ipu6-psys0: psys probe minor: 0 [ 12.433762] vsc_ace spi-INTC1094:00-5db76cf6-0a68-4ed6-9b78-0361635e2447: recv firmware id [ 17.721699] vsc_ace spi-INTC1094:00-5db76cf6-0a68-4ed6-9b78-0361635e2447: command 19 response timeout [ 17.721725] ipu own camera failed [ 17.829513] ov01a10 i2c-OVTI01A0:00: Acquire VSC failed [ 17.829987] ov01a10: probe of i2c-OVTI01A0:00 failed with error -110 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: v4l2-relayd 0.1.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Feb 23 05:16:46 2023 InstallationDate: Installed on 2023-02-23 (0 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: v4l2-relayd UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.modprobe.d.v4l2-relayd.conf: options v4l2loopback exclusive_caps=1 card_label="Intel MIPI Camera" mtime.conffile..etc.modprobe.d.v4l2-relayd.conf: 2023-02-23T03:30:34.242686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008224/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008224] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/2008224/+attachment/5649731/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2008224 Title: Intel MIPI Camera does not work on Ubuntu 22.04.02 Status in linux package in Ubuntu: Incomplete Status in v4l2-relayd package in Ubuntu: Invalid Status in linux source package in Jammy: Confirmed Status in v4l2-relayd source package in Jammy: Invalid Bug description: Install Ubuntu 22.04.02 daily build (2023-02-23), the camera does not work with Google Meet and any sort of camera application. [steps] 1. boot into OS 2. check kernel log [rate] 1/3 [kernel] [ 3.169297] intel-ipu6 intel-ipu: enabling device ( -> 0002) [ 3.169665] intel-ipu6 intel-ipu: Device 0x465d (rev: 0x1) [ 3.169682] intel-ipu6 intel-ipu: physical base address 0x603e00 [ 3.169683] intel-ipu6 intel-ipu: mapped as: 0xd0bf5156 [ 3.169729] intel-ipu6 intel-ipu: Unable to set secure mode [ 3.169730] intel-ipu6 intel-ipu: IPU in non-secure mode [ 3.169731] intel-ipu6 intel-ipu: IPU secure touch = 0x0 [ 3.169731] intel-ipu6 intel-ipu: IPU camera mask = 0xff [ 3.170713] intel-ipu6 intel-ipu: Skip ipc reset for non-secure mode [ 3.170714] intel-ipu6 intel-ipu: IPC reset done [ 3.170715] intel-ipu6 intel-ipu: cpd file name: intel/ipu6ep_fw.bin [ 3.171885] intel-ipu6 intel-ipu: FW version: 20220510 [ 3.174214] intel-ipu6 intel-ipu: IPU6-v3 driver version 1.0 [ 3.218000] intel-ipu6-psys intel-ipu6-psys0: pkg_dir entry count:8 [ 3.218094] intel-ipu6-psys intel-ipu6-psys0: psys probe minor: 0 [ 12.433762] vsc_ace spi-INTC1094:00-5db76cf6-0a68-4ed6-9b78-0361635e2447: recv firmware id [ 17.721699] vsc_ace spi-INTC1094:00-5db76cf6-0a68-4ed6-9b78-0361635e2447: command 19 response timeout [ 17.721725] ipu own camera failed [ 17.829513] ov01a10 i2c-OVTI01A0:00: Acquire VSC failed [ 17.829987] ov01a10: probe of i2c-OVTI01A0:00 failed with error -110 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: v4l2-relayd 0.1.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Feb 23 05:16:46 2023 InstallationDate: Installed on 2023-02-23 (0 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: v4l2-relayd UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.modprobe.d.v4l2-relayd.conf: options v4l2loopback exclusive_caps=1 card_label="Intel MIPI Camera" mtime.conffile..etc.modprobe.d.v4l2-relayd.conf: 2023-02-23T03:30:34.242686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008224/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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-lowlatency-hwe-5.19/5.19.0.1018.19~22.04.6)
All autopkgtests for the newly accepted linux-meta-lowlatency-hwe-5.19 (5.19.0.1018.19~22.04.6) for jammy have finished running. The following regressions have been reported in tests triggered by the package: glibc/2.35-0ubuntu3.1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#linux-meta-lowlatency-hwe-5.19 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008224] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/2008224/+attachment/5649734/+files/acpidump.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2008224 Title: Intel MIPI Camera does not work on Ubuntu 22.04.02 Status in linux package in Ubuntu: Incomplete Status in v4l2-relayd package in Ubuntu: Invalid Status in linux source package in Jammy: Confirmed Status in v4l2-relayd source package in Jammy: Invalid Bug description: Install Ubuntu 22.04.02 daily build (2023-02-23), the camera does not work with Google Meet and any sort of camera application. [steps] 1. boot into OS 2. check kernel log [rate] 1/3 [kernel] [ 3.169297] intel-ipu6 intel-ipu: enabling device ( -> 0002) [ 3.169665] intel-ipu6 intel-ipu: Device 0x465d (rev: 0x1) [ 3.169682] intel-ipu6 intel-ipu: physical base address 0x603e00 [ 3.169683] intel-ipu6 intel-ipu: mapped as: 0xd0bf5156 [ 3.169729] intel-ipu6 intel-ipu: Unable to set secure mode [ 3.169730] intel-ipu6 intel-ipu: IPU in non-secure mode [ 3.169731] intel-ipu6 intel-ipu: IPU secure touch = 0x0 [ 3.169731] intel-ipu6 intel-ipu: IPU camera mask = 0xff [ 3.170713] intel-ipu6 intel-ipu: Skip ipc reset for non-secure mode [ 3.170714] intel-ipu6 intel-ipu: IPC reset done [ 3.170715] intel-ipu6 intel-ipu: cpd file name: intel/ipu6ep_fw.bin [ 3.171885] intel-ipu6 intel-ipu: FW version: 20220510 [ 3.174214] intel-ipu6 intel-ipu: IPU6-v3 driver version 1.0 [ 3.218000] intel-ipu6-psys intel-ipu6-psys0: pkg_dir entry count:8 [ 3.218094] intel-ipu6-psys intel-ipu6-psys0: psys probe minor: 0 [ 12.433762] vsc_ace spi-INTC1094:00-5db76cf6-0a68-4ed6-9b78-0361635e2447: recv firmware id [ 17.721699] vsc_ace spi-INTC1094:00-5db76cf6-0a68-4ed6-9b78-0361635e2447: command 19 response timeout [ 17.721725] ipu own camera failed [ 17.829513] ov01a10 i2c-OVTI01A0:00: Acquire VSC failed [ 17.829987] ov01a10: probe of i2c-OVTI01A0:00 failed with error -110 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: v4l2-relayd 0.1.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Feb 23 05:16:46 2023 InstallationDate: Installed on 2023-02-23 (0 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: v4l2-relayd UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.modprobe.d.v4l2-relayd.conf: options v4l2loopback exclusive_caps=1 card_label="Intel MIPI Camera" mtime.conffile..etc.modprobe.d.v4l2-relayd.conf: 2023-02-23T03:30:34.242686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008224/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008224] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/2008224/+attachment/5649733/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2008224 Title: Intel MIPI Camera does not work on Ubuntu 22.04.02 Status in linux package in Ubuntu: Incomplete Status in v4l2-relayd package in Ubuntu: Invalid Status in linux source package in Jammy: Confirmed Status in v4l2-relayd source package in Jammy: Invalid Bug description: Install Ubuntu 22.04.02 daily build (2023-02-23), the camera does not work with Google Meet and any sort of camera application. [steps] 1. boot into OS 2. check kernel log [rate] 1/3 [kernel] [ 3.169297] intel-ipu6 intel-ipu: enabling device ( -> 0002) [ 3.169665] intel-ipu6 intel-ipu: Device 0x465d (rev: 0x1) [ 3.169682] intel-ipu6 intel-ipu: physical base address 0x603e00 [ 3.169683] intel-ipu6 intel-ipu: mapped as: 0xd0bf5156 [ 3.169729] intel-ipu6 intel-ipu: Unable to set secure mode [ 3.169730] intel-ipu6 intel-ipu: IPU in non-secure mode [ 3.169731] intel-ipu6 intel-ipu: IPU secure touch = 0x0 [ 3.169731] intel-ipu6 intel-ipu: IPU camera mask = 0xff [ 3.170713] intel-ipu6 intel-ipu: Skip ipc reset for non-secure mode [ 3.170714] intel-ipu6 intel-ipu: IPC reset done [ 3.170715] intel-ipu6 intel-ipu: cpd file name: intel/ipu6ep_fw.bin [ 3.171885] intel-ipu6 intel-ipu: FW version: 20220510 [ 3.174214] intel-ipu6 intel-ipu: IPU6-v3 driver version 1.0 [ 3.218000] intel-ipu6-psys intel-ipu6-psys0: pkg_dir entry count:8 [ 3.218094] intel-ipu6-psys intel-ipu6-psys0: psys probe minor: 0 [ 12.433762] vsc_ace spi-INTC1094:00-5db76cf6-0a68-4ed6-9b78-0361635e2447: recv firmware id [ 17.721699] vsc_ace spi-INTC1094:00-5db76cf6-0a68-4ed6-9b78-0361635e2447: command 19 response timeout [ 17.721725] ipu own camera failed [ 17.829513] ov01a10 i2c-OVTI01A0:00: Acquire VSC failed [ 17.829987] ov01a10: probe of i2c-OVTI01A0:00 failed with error -110 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: v4l2-relayd 0.1.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Feb 23 05:16:46 2023 InstallationDate: Installed on 2023-02-23 (0 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: v4l2-relayd UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.modprobe.d.v4l2-relayd.conf: options v4l2loopback exclusive_caps=1 card_label="Intel MIPI Camera" mtime.conffile..etc.modprobe.d.v4l2-relayd.conf: 2023-02-23T03:30:34.242686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008224/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008224] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/2008224/+attachment/5649729/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2008224 Title: Intel MIPI Camera does not work on Ubuntu 22.04.02 Status in linux package in Ubuntu: Incomplete Status in v4l2-relayd package in Ubuntu: Invalid Status in linux source package in Jammy: Confirmed Status in v4l2-relayd source package in Jammy: Invalid Bug description: Install Ubuntu 22.04.02 daily build (2023-02-23), the camera does not work with Google Meet and any sort of camera application. [steps] 1. boot into OS 2. check kernel log [rate] 1/3 [kernel] [ 3.169297] intel-ipu6 intel-ipu: enabling device ( -> 0002) [ 3.169665] intel-ipu6 intel-ipu: Device 0x465d (rev: 0x1) [ 3.169682] intel-ipu6 intel-ipu: physical base address 0x603e00 [ 3.169683] intel-ipu6 intel-ipu: mapped as: 0xd0bf5156 [ 3.169729] intel-ipu6 intel-ipu: Unable to set secure mode [ 3.169730] intel-ipu6 intel-ipu: IPU in non-secure mode [ 3.169731] intel-ipu6 intel-ipu: IPU secure touch = 0x0 [ 3.169731] intel-ipu6 intel-ipu: IPU camera mask = 0xff [ 3.170713] intel-ipu6 intel-ipu: Skip ipc reset for non-secure mode [ 3.170714] intel-ipu6 intel-ipu: IPC reset done [ 3.170715] intel-ipu6 intel-ipu: cpd file name: intel/ipu6ep_fw.bin [ 3.171885] intel-ipu6 intel-ipu: FW version: 20220510 [ 3.174214] intel-ipu6 intel-ipu: IPU6-v3 driver version 1.0 [ 3.218000] intel-ipu6-psys intel-ipu6-psys0: pkg_dir entry count:8 [ 3.218094] intel-ipu6-psys intel-ipu6-psys0: psys probe minor: 0 [ 12.433762] vsc_ace spi-INTC1094:00-5db76cf6-0a68-4ed6-9b78-0361635e2447: recv firmware id [ 17.721699] vsc_ace spi-INTC1094:00-5db76cf6-0a68-4ed6-9b78-0361635e2447: command 19 response timeout [ 17.721725] ipu own camera failed [ 17.829513] ov01a10 i2c-OVTI01A0:00: Acquire VSC failed [ 17.829987] ov01a10: probe of i2c-OVTI01A0:00 failed with error -110 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: v4l2-relayd 0.1.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Feb 23 05:16:46 2023 InstallationDate: Installed on 2023-02-23 (0 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: v4l2-relayd UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.modprobe.d.v4l2-relayd.conf: options v4l2loopback exclusive_caps=1 card_label="Intel MIPI Camera" mtime.conffile..etc.modprobe.d.v4l2-relayd.conf: 2023-02-23T03:30:34.242686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008224/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008224] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/2008224/+attachment/5649730/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2008224 Title: Intel MIPI Camera does not work on Ubuntu 22.04.02 Status in linux package in Ubuntu: Incomplete Status in v4l2-relayd package in Ubuntu: Invalid Status in linux source package in Jammy: Confirmed Status in v4l2-relayd source package in Jammy: Invalid Bug description: Install Ubuntu 22.04.02 daily build (2023-02-23), the camera does not work with Google Meet and any sort of camera application. [steps] 1. boot into OS 2. check kernel log [rate] 1/3 [kernel] [ 3.169297] intel-ipu6 intel-ipu: enabling device ( -> 0002) [ 3.169665] intel-ipu6 intel-ipu: Device 0x465d (rev: 0x1) [ 3.169682] intel-ipu6 intel-ipu: physical base address 0x603e00 [ 3.169683] intel-ipu6 intel-ipu: mapped as: 0xd0bf5156 [ 3.169729] intel-ipu6 intel-ipu: Unable to set secure mode [ 3.169730] intel-ipu6 intel-ipu: IPU in non-secure mode [ 3.169731] intel-ipu6 intel-ipu: IPU secure touch = 0x0 [ 3.169731] intel-ipu6 intel-ipu: IPU camera mask = 0xff [ 3.170713] intel-ipu6 intel-ipu: Skip ipc reset for non-secure mode [ 3.170714] intel-ipu6 intel-ipu: IPC reset done [ 3.170715] intel-ipu6 intel-ipu: cpd file name: intel/ipu6ep_fw.bin [ 3.171885] intel-ipu6 intel-ipu: FW version: 20220510 [ 3.174214] intel-ipu6 intel-ipu: IPU6-v3 driver version 1.0 [ 3.218000] intel-ipu6-psys intel-ipu6-psys0: pkg_dir entry count:8 [ 3.218094] intel-ipu6-psys intel-ipu6-psys0: psys probe minor: 0 [ 12.433762] vsc_ace spi-INTC1094:00-5db76cf6-0a68-4ed6-9b78-0361635e2447: recv firmware id [ 17.721699] vsc_ace spi-INTC1094:00-5db76cf6-0a68-4ed6-9b78-0361635e2447: command 19 response timeout [ 17.721725] ipu own camera failed [ 17.829513] ov01a10 i2c-OVTI01A0:00: Acquire VSC failed [ 17.829987] ov01a10: probe of i2c-OVTI01A0:00 failed with error -110 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: v4l2-relayd 0.1.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Feb 23 05:16:46 2023 InstallationDate: Installed on 2023-02-23 (0 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: v4l2-relayd UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.modprobe.d.v4l2-relayd.conf: options v4l2loopback exclusive_caps=1 card_label="Intel MIPI Camera" mtime.conffile..etc.modprobe.d.v4l2-relayd.conf: 2023-02-23T03:30:34.242686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008224/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008224] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/2008224/+attachment/5649728/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2008224 Title: Intel MIPI Camera does not work on Ubuntu 22.04.02 Status in linux package in Ubuntu: Incomplete Status in v4l2-relayd package in Ubuntu: Invalid Status in linux source package in Jammy: Confirmed Status in v4l2-relayd source package in Jammy: Invalid Bug description: Install Ubuntu 22.04.02 daily build (2023-02-23), the camera does not work with Google Meet and any sort of camera application. [steps] 1. boot into OS 2. check kernel log [rate] 1/3 [kernel] [ 3.169297] intel-ipu6 intel-ipu: enabling device ( -> 0002) [ 3.169665] intel-ipu6 intel-ipu: Device 0x465d (rev: 0x1) [ 3.169682] intel-ipu6 intel-ipu: physical base address 0x603e00 [ 3.169683] intel-ipu6 intel-ipu: mapped as: 0xd0bf5156 [ 3.169729] intel-ipu6 intel-ipu: Unable to set secure mode [ 3.169730] intel-ipu6 intel-ipu: IPU in non-secure mode [ 3.169731] intel-ipu6 intel-ipu: IPU secure touch = 0x0 [ 3.169731] intel-ipu6 intel-ipu: IPU camera mask = 0xff [ 3.170713] intel-ipu6 intel-ipu: Skip ipc reset for non-secure mode [ 3.170714] intel-ipu6 intel-ipu: IPC reset done [ 3.170715] intel-ipu6 intel-ipu: cpd file name: intel/ipu6ep_fw.bin [ 3.171885] intel-ipu6 intel-ipu: FW version: 20220510 [ 3.174214] intel-ipu6 intel-ipu: IPU6-v3 driver version 1.0 [ 3.218000] intel-ipu6-psys intel-ipu6-psys0: pkg_dir entry count:8 [ 3.218094] intel-ipu6-psys intel-ipu6-psys0: psys probe minor: 0 [ 12.433762] vsc_ace spi-INTC1094:00-5db76cf6-0a68-4ed6-9b78-0361635e2447: recv firmware id [ 17.721699] vsc_ace spi-INTC1094:00-5db76cf6-0a68-4ed6-9b78-0361635e2447: command 19 response timeout [ 17.721725] ipu own camera failed [ 17.829513] ov01a10 i2c-OVTI01A0:00: Acquire VSC failed [ 17.829987] ov01a10: probe of i2c-OVTI01A0:00 failed with error -110 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: v4l2-relayd 0.1.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Feb 23 05:16:46 2023 InstallationDate: Installed on 2023-02-23 (0 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: v4l2-relayd UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.modprobe.d.v4l2-relayd.conf: options v4l2loopback exclusive_caps=1 card_label="Intel MIPI Camera" mtime.conffile..etc.modprobe.d.v4l2-relayd.conf: 2023-02-23T03:30:34.242686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008224/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008224] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/2008224/+attachment/5649727/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2008224 Title: Intel MIPI Camera does not work on Ubuntu 22.04.02 Status in linux package in Ubuntu: Incomplete Status in v4l2-relayd package in Ubuntu: Invalid Status in linux source package in Jammy: Confirmed Status in v4l2-relayd source package in Jammy: Invalid Bug description: Install Ubuntu 22.04.02 daily build (2023-02-23), the camera does not work with Google Meet and any sort of camera application. [steps] 1. boot into OS 2. check kernel log [rate] 1/3 [kernel] [ 3.169297] intel-ipu6 intel-ipu: enabling device ( -> 0002) [ 3.169665] intel-ipu6 intel-ipu: Device 0x465d (rev: 0x1) [ 3.169682] intel-ipu6 intel-ipu: physical base address 0x603e00 [ 3.169683] intel-ipu6 intel-ipu: mapped as: 0xd0bf5156 [ 3.169729] intel-ipu6 intel-ipu: Unable to set secure mode [ 3.169730] intel-ipu6 intel-ipu: IPU in non-secure mode [ 3.169731] intel-ipu6 intel-ipu: IPU secure touch = 0x0 [ 3.169731] intel-ipu6 intel-ipu: IPU camera mask = 0xff [ 3.170713] intel-ipu6 intel-ipu: Skip ipc reset for non-secure mode [ 3.170714] intel-ipu6 intel-ipu: IPC reset done [ 3.170715] intel-ipu6 intel-ipu: cpd file name: intel/ipu6ep_fw.bin [ 3.171885] intel-ipu6 intel-ipu: FW version: 20220510 [ 3.174214] intel-ipu6 intel-ipu: IPU6-v3 driver version 1.0 [ 3.218000] intel-ipu6-psys intel-ipu6-psys0: pkg_dir entry count:8 [ 3.218094] intel-ipu6-psys intel-ipu6-psys0: psys probe minor: 0 [ 12.433762] vsc_ace spi-INTC1094:00-5db76cf6-0a68-4ed6-9b78-0361635e2447: recv firmware id [ 17.721699] vsc_ace spi-INTC1094:00-5db76cf6-0a68-4ed6-9b78-0361635e2447: command 19 response timeout [ 17.721725] ipu own camera failed [ 17.829513] ov01a10 i2c-OVTI01A0:00: Acquire VSC failed [ 17.829987] ov01a10: probe of i2c-OVTI01A0:00 failed with error -110 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: v4l2-relayd 0.1.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Feb 23 05:16:46 2023 InstallationDate: Installed on 2023-02-23 (0 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: v4l2-relayd UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.modprobe.d.v4l2-relayd.conf: options v4l2loopback exclusive_caps=1 card_label="Intel MIPI Camera" mtime.conffile..etc.modprobe.d.v4l2-relayd.conf: 2023-02-23T03:30:34.242686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008224/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008224] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/2008224/+attachment/5649725/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2008224 Title: Intel MIPI Camera does not work on Ubuntu 22.04.02 Status in linux package in Ubuntu: Incomplete Status in v4l2-relayd package in Ubuntu: Invalid Status in linux source package in Jammy: Confirmed Status in v4l2-relayd source package in Jammy: Invalid Bug description: Install Ubuntu 22.04.02 daily build (2023-02-23), the camera does not work with Google Meet and any sort of camera application. [steps] 1. boot into OS 2. check kernel log [rate] 1/3 [kernel] [ 3.169297] intel-ipu6 intel-ipu: enabling device ( -> 0002) [ 3.169665] intel-ipu6 intel-ipu: Device 0x465d (rev: 0x1) [ 3.169682] intel-ipu6 intel-ipu: physical base address 0x603e00 [ 3.169683] intel-ipu6 intel-ipu: mapped as: 0xd0bf5156 [ 3.169729] intel-ipu6 intel-ipu: Unable to set secure mode [ 3.169730] intel-ipu6 intel-ipu: IPU in non-secure mode [ 3.169731] intel-ipu6 intel-ipu: IPU secure touch = 0x0 [ 3.169731] intel-ipu6 intel-ipu: IPU camera mask = 0xff [ 3.170713] intel-ipu6 intel-ipu: Skip ipc reset for non-secure mode [ 3.170714] intel-ipu6 intel-ipu: IPC reset done [ 3.170715] intel-ipu6 intel-ipu: cpd file name: intel/ipu6ep_fw.bin [ 3.171885] intel-ipu6 intel-ipu: FW version: 20220510 [ 3.174214] intel-ipu6 intel-ipu: IPU6-v3 driver version 1.0 [ 3.218000] intel-ipu6-psys intel-ipu6-psys0: pkg_dir entry count:8 [ 3.218094] intel-ipu6-psys intel-ipu6-psys0: psys probe minor: 0 [ 12.433762] vsc_ace spi-INTC1094:00-5db76cf6-0a68-4ed6-9b78-0361635e2447: recv firmware id [ 17.721699] vsc_ace spi-INTC1094:00-5db76cf6-0a68-4ed6-9b78-0361635e2447: command 19 response timeout [ 17.721725] ipu own camera failed [ 17.829513] ov01a10 i2c-OVTI01A0:00: Acquire VSC failed [ 17.829987] ov01a10: probe of i2c-OVTI01A0:00 failed with error -110 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: v4l2-relayd 0.1.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Feb 23 05:16:46 2023 InstallationDate: Installed on 2023-02-23 (0 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: v4l2-relayd UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.modprobe.d.v4l2-relayd.conf: options v4l2loopback exclusive_caps=1 card_label="Intel MIPI Camera" mtime.conffile..etc.modprobe.d.v4l2-relayd.conf: 2023-02-23T03:30:34.242686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008224/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008224] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/2008224/+attachment/5649722/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2008224 Title: Intel MIPI Camera does not work on Ubuntu 22.04.02 Status in linux package in Ubuntu: Incomplete Status in v4l2-relayd package in Ubuntu: Invalid Status in linux source package in Jammy: Confirmed Status in v4l2-relayd source package in Jammy: Invalid Bug description: Install Ubuntu 22.04.02 daily build (2023-02-23), the camera does not work with Google Meet and any sort of camera application. [steps] 1. boot into OS 2. check kernel log [rate] 1/3 [kernel] [ 3.169297] intel-ipu6 intel-ipu: enabling device ( -> 0002) [ 3.169665] intel-ipu6 intel-ipu: Device 0x465d (rev: 0x1) [ 3.169682] intel-ipu6 intel-ipu: physical base address 0x603e00 [ 3.169683] intel-ipu6 intel-ipu: mapped as: 0xd0bf5156 [ 3.169729] intel-ipu6 intel-ipu: Unable to set secure mode [ 3.169730] intel-ipu6 intel-ipu: IPU in non-secure mode [ 3.169731] intel-ipu6 intel-ipu: IPU secure touch = 0x0 [ 3.169731] intel-ipu6 intel-ipu: IPU camera mask = 0xff [ 3.170713] intel-ipu6 intel-ipu: Skip ipc reset for non-secure mode [ 3.170714] intel-ipu6 intel-ipu: IPC reset done [ 3.170715] intel-ipu6 intel-ipu: cpd file name: intel/ipu6ep_fw.bin [ 3.171885] intel-ipu6 intel-ipu: FW version: 20220510 [ 3.174214] intel-ipu6 intel-ipu: IPU6-v3 driver version 1.0 [ 3.218000] intel-ipu6-psys intel-ipu6-psys0: pkg_dir entry count:8 [ 3.218094] intel-ipu6-psys intel-ipu6-psys0: psys probe minor: 0 [ 12.433762] vsc_ace spi-INTC1094:00-5db76cf6-0a68-4ed6-9b78-0361635e2447: recv firmware id [ 17.721699] vsc_ace spi-INTC1094:00-5db76cf6-0a68-4ed6-9b78-0361635e2447: command 19 response timeout [ 17.721725] ipu own camera failed [ 17.829513] ov01a10 i2c-OVTI01A0:00: Acquire VSC failed [ 17.829987] ov01a10: probe of i2c-OVTI01A0:00 failed with error -110 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: v4l2-relayd 0.1.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Feb 23 05:16:46 2023 InstallationDate: Installed on 2023-02-23 (0 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: v4l2-relayd UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.modprobe.d.v4l2-relayd.conf: options v4l2loopback exclusive_caps=1 card_label="Intel MIPI Camera" mtime.conffile..etc.modprobe.d.v4l2-relayd.conf: 2023-02-23T03:30:34.242686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008224/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008224] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/2008224/+attachment/5649720/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2008224 Title: Intel MIPI Camera does not work on Ubuntu 22.04.02 Status in linux package in Ubuntu: Incomplete Status in v4l2-relayd package in Ubuntu: Invalid Status in linux source package in Jammy: Confirmed Status in v4l2-relayd source package in Jammy: Invalid Bug description: Install Ubuntu 22.04.02 daily build (2023-02-23), the camera does not work with Google Meet and any sort of camera application. [steps] 1. boot into OS 2. check kernel log [rate] 1/3 [kernel] [ 3.169297] intel-ipu6 intel-ipu: enabling device ( -> 0002) [ 3.169665] intel-ipu6 intel-ipu: Device 0x465d (rev: 0x1) [ 3.169682] intel-ipu6 intel-ipu: physical base address 0x603e00 [ 3.169683] intel-ipu6 intel-ipu: mapped as: 0xd0bf5156 [ 3.169729] intel-ipu6 intel-ipu: Unable to set secure mode [ 3.169730] intel-ipu6 intel-ipu: IPU in non-secure mode [ 3.169731] intel-ipu6 intel-ipu: IPU secure touch = 0x0 [ 3.169731] intel-ipu6 intel-ipu: IPU camera mask = 0xff [ 3.170713] intel-ipu6 intel-ipu: Skip ipc reset for non-secure mode [ 3.170714] intel-ipu6 intel-ipu: IPC reset done [ 3.170715] intel-ipu6 intel-ipu: cpd file name: intel/ipu6ep_fw.bin [ 3.171885] intel-ipu6 intel-ipu: FW version: 20220510 [ 3.174214] intel-ipu6 intel-ipu: IPU6-v3 driver version 1.0 [ 3.218000] intel-ipu6-psys intel-ipu6-psys0: pkg_dir entry count:8 [ 3.218094] intel-ipu6-psys intel-ipu6-psys0: psys probe minor: 0 [ 12.433762] vsc_ace spi-INTC1094:00-5db76cf6-0a68-4ed6-9b78-0361635e2447: recv firmware id [ 17.721699] vsc_ace spi-INTC1094:00-5db76cf6-0a68-4ed6-9b78-0361635e2447: command 19 response timeout [ 17.721725] ipu own camera failed [ 17.829513] ov01a10 i2c-OVTI01A0:00: Acquire VSC failed [ 17.829987] ov01a10: probe of i2c-OVTI01A0:00 failed with error -110 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: v4l2-relayd 0.1.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Feb 23 05:16:46 2023 InstallationDate: Installed on 2023-02-23 (0 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: v4l2-relayd UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.modprobe.d.v4l2-relayd.conf: options v4l2loopback exclusive_caps=1 card_label="Intel MIPI Camera" mtime.conffile..etc.modprobe.d.v4l2-relayd.conf: 2023-02-23T03:30:34.242686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008224/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008224] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/2008224/+attachment/5649724/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2008224 Title: Intel MIPI Camera does not work on Ubuntu 22.04.02 Status in linux package in Ubuntu: Incomplete Status in v4l2-relayd package in Ubuntu: Invalid Status in linux source package in Jammy: Confirmed Status in v4l2-relayd source package in Jammy: Invalid Bug description: Install Ubuntu 22.04.02 daily build (2023-02-23), the camera does not work with Google Meet and any sort of camera application. [steps] 1. boot into OS 2. check kernel log [rate] 1/3 [kernel] [ 3.169297] intel-ipu6 intel-ipu: enabling device ( -> 0002) [ 3.169665] intel-ipu6 intel-ipu: Device 0x465d (rev: 0x1) [ 3.169682] intel-ipu6 intel-ipu: physical base address 0x603e00 [ 3.169683] intel-ipu6 intel-ipu: mapped as: 0xd0bf5156 [ 3.169729] intel-ipu6 intel-ipu: Unable to set secure mode [ 3.169730] intel-ipu6 intel-ipu: IPU in non-secure mode [ 3.169731] intel-ipu6 intel-ipu: IPU secure touch = 0x0 [ 3.169731] intel-ipu6 intel-ipu: IPU camera mask = 0xff [ 3.170713] intel-ipu6 intel-ipu: Skip ipc reset for non-secure mode [ 3.170714] intel-ipu6 intel-ipu: IPC reset done [ 3.170715] intel-ipu6 intel-ipu: cpd file name: intel/ipu6ep_fw.bin [ 3.171885] intel-ipu6 intel-ipu: FW version: 20220510 [ 3.174214] intel-ipu6 intel-ipu: IPU6-v3 driver version 1.0 [ 3.218000] intel-ipu6-psys intel-ipu6-psys0: pkg_dir entry count:8 [ 3.218094] intel-ipu6-psys intel-ipu6-psys0: psys probe minor: 0 [ 12.433762] vsc_ace spi-INTC1094:00-5db76cf6-0a68-4ed6-9b78-0361635e2447: recv firmware id [ 17.721699] vsc_ace spi-INTC1094:00-5db76cf6-0a68-4ed6-9b78-0361635e2447: command 19 response timeout [ 17.721725] ipu own camera failed [ 17.829513] ov01a10 i2c-OVTI01A0:00: Acquire VSC failed [ 17.829987] ov01a10: probe of i2c-OVTI01A0:00 failed with error -110 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: v4l2-relayd 0.1.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Feb 23 05:16:46 2023 InstallationDate: Installed on 2023-02-23 (0 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: v4l2-relayd UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.modprobe.d.v4l2-relayd.conf: options v4l2loopback exclusive_caps=1 card_label="Intel MIPI Camera" mtime.conffile..etc.modprobe.d.v4l2-relayd.conf: 2023-02-23T03:30:34.242686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008224/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008224] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/2008224/+attachment/5649721/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2008224 Title: Intel MIPI Camera does not work on Ubuntu 22.04.02 Status in linux package in Ubuntu: Incomplete Status in v4l2-relayd package in Ubuntu: Invalid Status in linux source package in Jammy: Confirmed Status in v4l2-relayd source package in Jammy: Invalid Bug description: Install Ubuntu 22.04.02 daily build (2023-02-23), the camera does not work with Google Meet and any sort of camera application. [steps] 1. boot into OS 2. check kernel log [rate] 1/3 [kernel] [ 3.169297] intel-ipu6 intel-ipu: enabling device ( -> 0002) [ 3.169665] intel-ipu6 intel-ipu: Device 0x465d (rev: 0x1) [ 3.169682] intel-ipu6 intel-ipu: physical base address 0x603e00 [ 3.169683] intel-ipu6 intel-ipu: mapped as: 0xd0bf5156 [ 3.169729] intel-ipu6 intel-ipu: Unable to set secure mode [ 3.169730] intel-ipu6 intel-ipu: IPU in non-secure mode [ 3.169731] intel-ipu6 intel-ipu: IPU secure touch = 0x0 [ 3.169731] intel-ipu6 intel-ipu: IPU camera mask = 0xff [ 3.170713] intel-ipu6 intel-ipu: Skip ipc reset for non-secure mode [ 3.170714] intel-ipu6 intel-ipu: IPC reset done [ 3.170715] intel-ipu6 intel-ipu: cpd file name: intel/ipu6ep_fw.bin [ 3.171885] intel-ipu6 intel-ipu: FW version: 20220510 [ 3.174214] intel-ipu6 intel-ipu: IPU6-v3 driver version 1.0 [ 3.218000] intel-ipu6-psys intel-ipu6-psys0: pkg_dir entry count:8 [ 3.218094] intel-ipu6-psys intel-ipu6-psys0: psys probe minor: 0 [ 12.433762] vsc_ace spi-INTC1094:00-5db76cf6-0a68-4ed6-9b78-0361635e2447: recv firmware id [ 17.721699] vsc_ace spi-INTC1094:00-5db76cf6-0a68-4ed6-9b78-0361635e2447: command 19 response timeout [ 17.721725] ipu own camera failed [ 17.829513] ov01a10 i2c-OVTI01A0:00: Acquire VSC failed [ 17.829987] ov01a10: probe of i2c-OVTI01A0:00 failed with error -110 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: v4l2-relayd 0.1.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Feb 23 05:16:46 2023 InstallationDate: Installed on 2023-02-23 (0 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: v4l2-relayd UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.modprobe.d.v4l2-relayd.conf: options v4l2loopback exclusive_caps=1 card_label="Intel MIPI Camera" mtime.conffile..etc.modprobe.d.v4l2-relayd.conf: 2023-02-23T03:30:34.242686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008224/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008224] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/2008224/+attachment/5649723/+files/PaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2008224 Title: Intel MIPI Camera does not work on Ubuntu 22.04.02 Status in linux package in Ubuntu: Incomplete Status in v4l2-relayd package in Ubuntu: Invalid Status in linux source package in Jammy: Confirmed Status in v4l2-relayd source package in Jammy: Invalid Bug description: Install Ubuntu 22.04.02 daily build (2023-02-23), the camera does not work with Google Meet and any sort of camera application. [steps] 1. boot into OS 2. check kernel log [rate] 1/3 [kernel] [ 3.169297] intel-ipu6 intel-ipu: enabling device ( -> 0002) [ 3.169665] intel-ipu6 intel-ipu: Device 0x465d (rev: 0x1) [ 3.169682] intel-ipu6 intel-ipu: physical base address 0x603e00 [ 3.169683] intel-ipu6 intel-ipu: mapped as: 0xd0bf5156 [ 3.169729] intel-ipu6 intel-ipu: Unable to set secure mode [ 3.169730] intel-ipu6 intel-ipu: IPU in non-secure mode [ 3.169731] intel-ipu6 intel-ipu: IPU secure touch = 0x0 [ 3.169731] intel-ipu6 intel-ipu: IPU camera mask = 0xff [ 3.170713] intel-ipu6 intel-ipu: Skip ipc reset for non-secure mode [ 3.170714] intel-ipu6 intel-ipu: IPC reset done [ 3.170715] intel-ipu6 intel-ipu: cpd file name: intel/ipu6ep_fw.bin [ 3.171885] intel-ipu6 intel-ipu: FW version: 20220510 [ 3.174214] intel-ipu6 intel-ipu: IPU6-v3 driver version 1.0 [ 3.218000] intel-ipu6-psys intel-ipu6-psys0: pkg_dir entry count:8 [ 3.218094] intel-ipu6-psys intel-ipu6-psys0: psys probe minor: 0 [ 12.433762] vsc_ace spi-INTC1094:00-5db76cf6-0a68-4ed6-9b78-0361635e2447: recv firmware id [ 17.721699] vsc_ace spi-INTC1094:00-5db76cf6-0a68-4ed6-9b78-0361635e2447: command 19 response timeout [ 17.721725] ipu own camera failed [ 17.829513] ov01a10 i2c-OVTI01A0:00: Acquire VSC failed [ 17.829987] ov01a10: probe of i2c-OVTI01A0:00 failed with error -110 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: v4l2-relayd 0.1.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Feb 23 05:16:46 2023 InstallationDate: Installed on 2023-02-23 (0 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: v4l2-relayd UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.modprobe.d.v4l2-relayd.conf: options v4l2loopback exclusive_caps=1 card_label="Intel MIPI Camera" mtime.conffile..etc.modprobe.d.v4l2-relayd.conf: 2023-02-23T03:30:34.242686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008224/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008224] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/2008224/+attachment/5649719/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2008224 Title: Intel MIPI Camera does not work on Ubuntu 22.04.02 Status in linux package in Ubuntu: Incomplete Status in v4l2-relayd package in Ubuntu: Invalid Status in linux source package in Jammy: Confirmed Status in v4l2-relayd source package in Jammy: Invalid Bug description: Install Ubuntu 22.04.02 daily build (2023-02-23), the camera does not work with Google Meet and any sort of camera application. [steps] 1. boot into OS 2. check kernel log [rate] 1/3 [kernel] [ 3.169297] intel-ipu6 intel-ipu: enabling device ( -> 0002) [ 3.169665] intel-ipu6 intel-ipu: Device 0x465d (rev: 0x1) [ 3.169682] intel-ipu6 intel-ipu: physical base address 0x603e00 [ 3.169683] intel-ipu6 intel-ipu: mapped as: 0xd0bf5156 [ 3.169729] intel-ipu6 intel-ipu: Unable to set secure mode [ 3.169730] intel-ipu6 intel-ipu: IPU in non-secure mode [ 3.169731] intel-ipu6 intel-ipu: IPU secure touch = 0x0 [ 3.169731] intel-ipu6 intel-ipu: IPU camera mask = 0xff [ 3.170713] intel-ipu6 intel-ipu: Skip ipc reset for non-secure mode [ 3.170714] intel-ipu6 intel-ipu: IPC reset done [ 3.170715] intel-ipu6 intel-ipu: cpd file name: intel/ipu6ep_fw.bin [ 3.171885] intel-ipu6 intel-ipu: FW version: 20220510 [ 3.174214] intel-ipu6 intel-ipu: IPU6-v3 driver version 1.0 [ 3.218000] intel-ipu6-psys intel-ipu6-psys0: pkg_dir entry count:8 [ 3.218094] intel-ipu6-psys intel-ipu6-psys0: psys probe minor: 0 [ 12.433762] vsc_ace spi-INTC1094:00-5db76cf6-0a68-4ed6-9b78-0361635e2447: recv firmware id [ 17.721699] vsc_ace spi-INTC1094:00-5db76cf6-0a68-4ed6-9b78-0361635e2447: command 19 response timeout [ 17.721725] ipu own camera failed [ 17.829513] ov01a10 i2c-OVTI01A0:00: Acquire VSC failed [ 17.829987] ov01a10: probe of i2c-OVTI01A0:00 failed with error -110 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: v4l2-relayd 0.1.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Feb 23 05:16:46 2023 InstallationDate: Installed on 2023-02-23 (0 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: v4l2-relayd UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.modprobe.d.v4l2-relayd.conf: options v4l2loopback exclusive_caps=1 card_label="Intel MIPI Camera" mtime.conffile..etc.modprobe.d.v4l2-relayd.conf: 2023-02-23T03:30:34.242686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008224/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008224] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/2008224/+attachment/5649718/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2008224 Title: Intel MIPI Camera does not work on Ubuntu 22.04.02 Status in linux package in Ubuntu: Incomplete Status in v4l2-relayd package in Ubuntu: Invalid Status in linux source package in Jammy: Confirmed Status in v4l2-relayd source package in Jammy: Invalid Bug description: Install Ubuntu 22.04.02 daily build (2023-02-23), the camera does not work with Google Meet and any sort of camera application. [steps] 1. boot into OS 2. check kernel log [rate] 1/3 [kernel] [ 3.169297] intel-ipu6 intel-ipu: enabling device ( -> 0002) [ 3.169665] intel-ipu6 intel-ipu: Device 0x465d (rev: 0x1) [ 3.169682] intel-ipu6 intel-ipu: physical base address 0x603e00 [ 3.169683] intel-ipu6 intel-ipu: mapped as: 0xd0bf5156 [ 3.169729] intel-ipu6 intel-ipu: Unable to set secure mode [ 3.169730] intel-ipu6 intel-ipu: IPU in non-secure mode [ 3.169731] intel-ipu6 intel-ipu: IPU secure touch = 0x0 [ 3.169731] intel-ipu6 intel-ipu: IPU camera mask = 0xff [ 3.170713] intel-ipu6 intel-ipu: Skip ipc reset for non-secure mode [ 3.170714] intel-ipu6 intel-ipu: IPC reset done [ 3.170715] intel-ipu6 intel-ipu: cpd file name: intel/ipu6ep_fw.bin [ 3.171885] intel-ipu6 intel-ipu: FW version: 20220510 [ 3.174214] intel-ipu6 intel-ipu: IPU6-v3 driver version 1.0 [ 3.218000] intel-ipu6-psys intel-ipu6-psys0: pkg_dir entry count:8 [ 3.218094] intel-ipu6-psys intel-ipu6-psys0: psys probe minor: 0 [ 12.433762] vsc_ace spi-INTC1094:00-5db76cf6-0a68-4ed6-9b78-0361635e2447: recv firmware id [ 17.721699] vsc_ace spi-INTC1094:00-5db76cf6-0a68-4ed6-9b78-0361635e2447: command 19 response timeout [ 17.721725] ipu own camera failed [ 17.829513] ov01a10 i2c-OVTI01A0:00: Acquire VSC failed [ 17.829987] ov01a10: probe of i2c-OVTI01A0:00 failed with error -110 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: v4l2-relayd 0.1.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Feb 23 05:16:46 2023 InstallationDate: Installed on 2023-02-23 (0 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: v4l2-relayd UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.modprobe.d.v4l2-relayd.conf: options v4l2loopback exclusive_caps=1 card_label="Intel MIPI Camera" mtime.conffile..etc.modprobe.d.v4l2-relayd.conf: 2023-02-23T03:30:34.242686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008224/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008224] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/2008224/+attachment/5649716/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2008224 Title: Intel MIPI Camera does not work on Ubuntu 22.04.02 Status in linux package in Ubuntu: Incomplete Status in v4l2-relayd package in Ubuntu: Invalid Status in linux source package in Jammy: Confirmed Status in v4l2-relayd source package in Jammy: Invalid Bug description: Install Ubuntu 22.04.02 daily build (2023-02-23), the camera does not work with Google Meet and any sort of camera application. [steps] 1. boot into OS 2. check kernel log [rate] 1/3 [kernel] [ 3.169297] intel-ipu6 intel-ipu: enabling device ( -> 0002) [ 3.169665] intel-ipu6 intel-ipu: Device 0x465d (rev: 0x1) [ 3.169682] intel-ipu6 intel-ipu: physical base address 0x603e00 [ 3.169683] intel-ipu6 intel-ipu: mapped as: 0xd0bf5156 [ 3.169729] intel-ipu6 intel-ipu: Unable to set secure mode [ 3.169730] intel-ipu6 intel-ipu: IPU in non-secure mode [ 3.169731] intel-ipu6 intel-ipu: IPU secure touch = 0x0 [ 3.169731] intel-ipu6 intel-ipu: IPU camera mask = 0xff [ 3.170713] intel-ipu6 intel-ipu: Skip ipc reset for non-secure mode [ 3.170714] intel-ipu6 intel-ipu: IPC reset done [ 3.170715] intel-ipu6 intel-ipu: cpd file name: intel/ipu6ep_fw.bin [ 3.171885] intel-ipu6 intel-ipu: FW version: 20220510 [ 3.174214] intel-ipu6 intel-ipu: IPU6-v3 driver version 1.0 [ 3.218000] intel-ipu6-psys intel-ipu6-psys0: pkg_dir entry count:8 [ 3.218094] intel-ipu6-psys intel-ipu6-psys0: psys probe minor: 0 [ 12.433762] vsc_ace spi-INTC1094:00-5db76cf6-0a68-4ed6-9b78-0361635e2447: recv firmware id [ 17.721699] vsc_ace spi-INTC1094:00-5db76cf6-0a68-4ed6-9b78-0361635e2447: command 19 response timeout [ 17.721725] ipu own camera failed [ 17.829513] ov01a10 i2c-OVTI01A0:00: Acquire VSC failed [ 17.829987] ov01a10: probe of i2c-OVTI01A0:00 failed with error -110 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: v4l2-relayd 0.1.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Feb 23 05:16:46 2023 InstallationDate: Installed on 2023-02-23 (0 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: v4l2-relayd UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.modprobe.d.v4l2-relayd.conf: options v4l2loopback exclusive_caps=1 card_label="Intel MIPI Camera" mtime.conffile..etc.modprobe.d.v4l2-relayd.conf: 2023-02-23T03:30:34.242686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008224/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008224] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/2008224/+attachment/5649717/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2008224 Title: Intel MIPI Camera does not work on Ubuntu 22.04.02 Status in linux package in Ubuntu: Incomplete Status in v4l2-relayd package in Ubuntu: Invalid Status in linux source package in Jammy: Confirmed Status in v4l2-relayd source package in Jammy: Invalid Bug description: Install Ubuntu 22.04.02 daily build (2023-02-23), the camera does not work with Google Meet and any sort of camera application. [steps] 1. boot into OS 2. check kernel log [rate] 1/3 [kernel] [ 3.169297] intel-ipu6 intel-ipu: enabling device ( -> 0002) [ 3.169665] intel-ipu6 intel-ipu: Device 0x465d (rev: 0x1) [ 3.169682] intel-ipu6 intel-ipu: physical base address 0x603e00 [ 3.169683] intel-ipu6 intel-ipu: mapped as: 0xd0bf5156 [ 3.169729] intel-ipu6 intel-ipu: Unable to set secure mode [ 3.169730] intel-ipu6 intel-ipu: IPU in non-secure mode [ 3.169731] intel-ipu6 intel-ipu: IPU secure touch = 0x0 [ 3.169731] intel-ipu6 intel-ipu: IPU camera mask = 0xff [ 3.170713] intel-ipu6 intel-ipu: Skip ipc reset for non-secure mode [ 3.170714] intel-ipu6 intel-ipu: IPC reset done [ 3.170715] intel-ipu6 intel-ipu: cpd file name: intel/ipu6ep_fw.bin [ 3.171885] intel-ipu6 intel-ipu: FW version: 20220510 [ 3.174214] intel-ipu6 intel-ipu: IPU6-v3 driver version 1.0 [ 3.218000] intel-ipu6-psys intel-ipu6-psys0: pkg_dir entry count:8 [ 3.218094] intel-ipu6-psys intel-ipu6-psys0: psys probe minor: 0 [ 12.433762] vsc_ace spi-INTC1094:00-5db76cf6-0a68-4ed6-9b78-0361635e2447: recv firmware id [ 17.721699] vsc_ace spi-INTC1094:00-5db76cf6-0a68-4ed6-9b78-0361635e2447: command 19 response timeout [ 17.721725] ipu own camera failed [ 17.829513] ov01a10 i2c-OVTI01A0:00: Acquire VSC failed [ 17.829987] ov01a10: probe of i2c-OVTI01A0:00 failed with error -110 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: v4l2-relayd 0.1.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Feb 23 05:16:46 2023 InstallationDate: Installed on 2023-02-23 (0 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: v4l2-relayd UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.modprobe.d.v4l2-relayd.conf: options v4l2loopback exclusive_caps=1 card_label="Intel MIPI Camera" mtime.conffile..etc.modprobe.d.v4l2-relayd.conf: 2023-02-23T03:30:34.242686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008224/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008224] AlsaInfo.txt
apport information ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/2008224/+attachment/5649715/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2008224 Title: Intel MIPI Camera does not work on Ubuntu 22.04.02 Status in linux package in Ubuntu: Incomplete Status in v4l2-relayd package in Ubuntu: Invalid Status in linux source package in Jammy: Confirmed Status in v4l2-relayd source package in Jammy: Invalid Bug description: Install Ubuntu 22.04.02 daily build (2023-02-23), the camera does not work with Google Meet and any sort of camera application. [steps] 1. boot into OS 2. check kernel log [rate] 1/3 [kernel] [ 3.169297] intel-ipu6 intel-ipu: enabling device ( -> 0002) [ 3.169665] intel-ipu6 intel-ipu: Device 0x465d (rev: 0x1) [ 3.169682] intel-ipu6 intel-ipu: physical base address 0x603e00 [ 3.169683] intel-ipu6 intel-ipu: mapped as: 0xd0bf5156 [ 3.169729] intel-ipu6 intel-ipu: Unable to set secure mode [ 3.169730] intel-ipu6 intel-ipu: IPU in non-secure mode [ 3.169731] intel-ipu6 intel-ipu: IPU secure touch = 0x0 [ 3.169731] intel-ipu6 intel-ipu: IPU camera mask = 0xff [ 3.170713] intel-ipu6 intel-ipu: Skip ipc reset for non-secure mode [ 3.170714] intel-ipu6 intel-ipu: IPC reset done [ 3.170715] intel-ipu6 intel-ipu: cpd file name: intel/ipu6ep_fw.bin [ 3.171885] intel-ipu6 intel-ipu: FW version: 20220510 [ 3.174214] intel-ipu6 intel-ipu: IPU6-v3 driver version 1.0 [ 3.218000] intel-ipu6-psys intel-ipu6-psys0: pkg_dir entry count:8 [ 3.218094] intel-ipu6-psys intel-ipu6-psys0: psys probe minor: 0 [ 12.433762] vsc_ace spi-INTC1094:00-5db76cf6-0a68-4ed6-9b78-0361635e2447: recv firmware id [ 17.721699] vsc_ace spi-INTC1094:00-5db76cf6-0a68-4ed6-9b78-0361635e2447: command 19 response timeout [ 17.721725] ipu own camera failed [ 17.829513] ov01a10 i2c-OVTI01A0:00: Acquire VSC failed [ 17.829987] ov01a10: probe of i2c-OVTI01A0:00 failed with error -110 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: v4l2-relayd 0.1.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Feb 23 05:16:46 2023 InstallationDate: Installed on 2023-02-23 (0 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: v4l2-relayd UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.modprobe.d.v4l2-relayd.conf: options v4l2loopback exclusive_caps=1 card_label="Intel MIPI Camera" mtime.conffile..etc.modprobe.d.v4l2-relayd.conf: 2023-02-23T03:30:34.242686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008224/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008224] Re: Intel MIPI Camera does not work on Ubuntu 22.04.02
ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1692 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-02-24 (0 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) MachineType: Dell Inc. XPS 9320 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-32-generic root=UUID=4747e171-2f31-4d0f-a7d2-ddac842c6a91 ro quiet splash i915.enable_psr2_sel_fetch=0 vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-32-generic N/A linux-backports-modules-5.19.0-32-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 Tags: jammy wayland-session wayland-session Uname: Linux 5.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/06/2023 dmi.bios.release: 2.0 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.0.0 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.0.0:bd02/06/2023:br2.0:svnDellInc.:pnXPS9320:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0AF3: dmi.product.family: XPS dmi.product.name: XPS 9320 dmi.product.sku: 0AF3 dmi.sys.vendor: Dell Inc. ** Tags added: apport-collected -- 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/2008224 Title: Intel MIPI Camera does not work on Ubuntu 22.04.02 Status in linux package in Ubuntu: Incomplete Status in v4l2-relayd package in Ubuntu: Invalid Status in linux source package in Jammy: Confirmed Status in v4l2-relayd source package in Jammy: Invalid Bug description: Install Ubuntu 22.04.02 daily build (2023-02-23), the camera does not work with Google Meet and any sort of camera application. [steps] 1. boot into OS 2. check kernel log [rate] 1/3 [kernel] [ 3.169297] intel-ipu6 intel-ipu: enabling device ( -> 0002) [ 3.169665] intel-ipu6 intel-ipu: Device 0x465d (rev: 0x1) [ 3.169682] intel-ipu6 intel-ipu: physical base address 0x603e00 [ 3.169683] intel-ipu6 intel-ipu: mapped as: 0xd0bf5156 [ 3.169729] intel-ipu6 intel-ipu: Unable to set secure mode [ 3.169730] intel-ipu6 intel-ipu: IPU in non-secure mode [ 3.169731] intel-ipu6 intel-ipu: IPU secure touch = 0x0 [ 3.169731] intel-ipu6 intel-ipu: IPU camera mask = 0xff [ 3.170713] intel-ipu6 intel-ipu: Skip ipc reset for non-secure mode [ 3.170714] intel-ipu6 intel-ipu: IPC reset done [ 3.170715] intel-ipu6 intel-ipu: cpd file name: intel/ipu6ep_fw.bin [ 3.171885] intel-ipu6 intel-ipu: FW version: 20220510 [ 3.174214] intel-ipu6 intel-ipu: IPU6-v3 driver version 1.0 [ 3.218000] intel-ipu6-psys intel-ipu6-psys0: pkg_dir entry count:8 [ 3.218094] intel-ipu6-psys intel-ipu6-psys0: psys probe minor: 0 [ 12.433762] vsc_ace spi-INTC1094:00-5db76cf6-0a68-4ed6-9b78-0361635e2447: recv firmware id [ 17.721699] vsc_ace spi-INTC1094:00-5db76cf6-0a68-4ed6-9b78-0361635e2447: command 19 response timeout [ 17.721725] ipu own camera failed [ 17.829513] ov01a10 i2c-OVTI01A0:00: Acquire VSC failed [ 17.829987] ov01a10: probe of i2c-OVTI01A0:00 failed with error -110 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: v4l2-relayd 0.1.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Feb 23 05:16:46 2023 InstallationDate: Installed on 2023-02-23 (0 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: v4l2-relayd UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.modprobe.d.v4l2-relayd.conf: options v4l2loopback exclusive_caps=1 card_label="Intel MIPI Camera" mtime.conffile..etc.modprobe.d.v4l2-relayd.conf: 2023-02-23T03:30:34.242686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008224/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1981658] Re: BUG: kernel NULL pointer dereference, address: 0000000000000008
Is anybody knows the steps to reproduce this issue? We are also facing the same below TB in our testbed and we are planning to take the patch mentioned in comment #15. Even though we are using this kernel from long time and seen this issue on very few nodes. Appreciate your help in this regard. Feb 22 22:20:47 maglev-master-192-168-70-10 kernel: [14501.026015] TCP: request_sock_TCP: Possible SYN flooding on port 8033. Sending cookies. Check SNMP counters. Feb 22 22:20:47 maglev-master-192-168-70-10 kernel: [14501.027529] BUG: kernel NULL pointer dereference, address: 0008 Feb 22 22:20:47 maglev-master-192-168-70-10 kernel: [14501.035339] #PF: supervisor read access in kernel mode Feb 22 22:20:47 maglev-master-192-168-70-10 kernel: [14501.041083] #PF: error_code(0x) - not-present page Feb 22 22:20:47 maglev-master-192-168-70-10 kernel: [14501.046838] PGD 0 P4D 0 Feb 22 22:20:47 maglev-master-192-168-70-10 kernel: [14501.049670] Oops: [#1] SMP NOPTI Feb 22 22:20:47 maglev-master-192-168-70-10 kernel: [14501.053764] CPU: 36 PID: 230 Comm: ksoftirqd/36 Not tainted 5.4.0-122-generic #138~18.04.1 Feb 22 22:20:47 maglev-master-192-168-70-10 kernel: [14501.063007] Hardware name: Cisco Systems Inc DN2-HW-APL-L/UCSC-C220-M5SX, BIOS C220M5.4.1.3i.0.0713210713 07/13/2021 Feb 22 22:20:47 maglev-master-192-168-70-10 kernel: [14501.074770] RIP: 0010:tcp_create_openreq_child+0x2e1/0x3e0 Feb 22 22:20:47 maglev-master-192-168-70-10 kernel: [14501.080907] Code: 08 00 00 41 8b 84 24 18 01 00 00 48 c7 83 80 08 00 00 00 00 00 00 4c 89 e6 4c 89 ef 89 83 c4 05 00 00 49 8b 84 24 f8 00 00 00 <48> 8b 40 08 e8 96 b8 41 00 48 85 c0 0f b7 83 68 05 00 00 74 0a 83 Feb 22 22:20:47 maglev-master-192-168-70-10 kernel: [14501.101919] RSP: 0018:97b88d207a28 EFLAGS: 00010246 Feb 22 22:20:47 maglev-master-192-168-70-10 kernel: [14501.107764] RAX: RBX: 8abb9d1bc600 RCX: 0007 Feb 22 22:20:47 maglev-master-192-168-70-10 kernel: [14501.115745] RDX: 0020 RSI: 8abb3c6e1560 RDI: 8acdef1b9180 Feb 22 22:20:47 maglev-master-192-168-70-10 kernel: [14501.123722] RBP: 97b88d207a48 R08: R09: 8aacffc07800 Feb 22 22:20:47 maglev-master-192-168-70-10 kernel: [14501.131699] R10: 0514 R11: 97b88d207b0f R12: 8abb3c6e1560 Feb 22 22:20:47 maglev-master-192-168-70-10 kernel: [14501.139678] R13: 8acdef1b9180 R14: 8abdfc1a7500 R15: 8adc75529ec0 Feb 22 22:20:47 maglev-master-192-168-70-10 kernel: [14501.147655] FS: () GS:8adcff00() knlGS: Feb 22 22:20:47 maglev-master-192-168-70-10 kernel: [14501.156705] CS: 0010 DS: ES: CR0: 80050033 Feb 22 22:20:47 maglev-master-192-168-70-10 kernel: [14501.163144] CR2: 0008 CR3: 00594ea0a005 CR4: 007606e0 Feb 22 22:20:47 maglev-master-192-168-70-10 kernel: [14501.171120] DR0: DR1: DR2: Feb 22 22:20:47 maglev-master-192-168-70-10 kernel: [14501.179099] DR3: DR6: fffe0ff0 DR7: 0400 Feb 22 22:20:47 maglev-master-192-168-70-10 kernel: [14501.187076] PKRU: 5554 Feb 22 22:20:47 maglev-master-192-168-70-10 kernel: [14501.190101] Call Trace: Feb 22 22:20:47 maglev-master-192-168-70-10 kernel: [14501.192841] tcp_v4_syn_recv_sock+0x5a/0x3d0 Feb 22 22:20:47 maglev-master-192-168-70-10 kernel: [14501.197616] tcp_get_cookie_sock+0x48/0x140 Feb 22 22:20:47 maglev-master-192-168-70-10 kernel: [14501.202284] cookie_v4_check+0x561/0x660 Feb 22 22:20:47 maglev-master-192-168-70-10 kernel: [14501.206672] tcp_v4_do_rcv+0x1a0/0x1d0 Feb 22 22:20:47 maglev-master-192-168-70-10 kernel: [14501.210864] tcp_v4_rcv+0xa86/0xad0 Feb 22 22:20:47 maglev-master-192-168-70-10 kernel: [14501.214766] ip_protocol_deliver_rcu+0x31/0x1b0 Feb 22 22:20:47 maglev-master-192-168-70-10 kernel: [14501.219831] ip_local_deliver_finish+0x48/0x50 Feb 22 22:20:47 maglev-master-192-168-70-10 kernel: [14501.224807] ip_local_deliver+0x7e/0xe0 Feb 22 22:20:47 maglev-master-192-168-70-10 kernel: [14501.229095] ? ip_protocol_deliver_rcu+0x1b0/0x1b0 Feb 22 22:20:47 maglev-master-192-168-70-10 kernel: [14501.234456] ip_rcv_finish+0x84/0xa0 Feb 22 22:20:47 maglev-master-192-168-70-10 kernel: [14501.238453] ip_rcv+0xbc/0xd0 Feb 22 22:20:47 maglev-master-192-168-70-10 kernel: [14501.241773] __netif_receive_skb_one_core+0x86/0xa0 Feb 22 22:20:47 maglev-master-192-168-70-10 kernel: [14501.247226] __netif_receive_skb+0x18/0x60 Feb 22 22:20:47 maglev-master-192-168-70-10 kernel: [14501.251806] process_backlog+0xa9/0x170 Feb 22 22:20:47 maglev-master-192-168-70-10 kernel: [14501.256093] net_rx_action+0x140/0x3e0 Feb 22 22:20:47 maglev-master-192-168-70-10 kernel: [14501.260287] ? __switch_to_asm+0x34/0x70 Feb 22 22:20:47 maglev-master-192-168-70-10 kernel: [14501.264664] __do_softirq+0xe4/0x2da Feb 22 22:20:47
[Kernel-packages] [Bug 2008224] Re: Intel MIPI Camera does not work on Ubuntu 22.04.02
The BIOS on TRBA-DVT2-C1_202112-29801 is 1.11.0 -- 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/2008224 Title: Intel MIPI Camera does not work on Ubuntu 22.04.02 Status in linux package in Ubuntu: Incomplete Status in v4l2-relayd package in Ubuntu: Invalid Status in linux source package in Jammy: Confirmed Status in v4l2-relayd source package in Jammy: Invalid Bug description: Install Ubuntu 22.04.02 daily build (2023-02-23), the camera does not work with Google Meet and any sort of camera application. [steps] 1. boot into OS 2. check kernel log [rate] 1/3 [kernel] [ 3.169297] intel-ipu6 intel-ipu: enabling device ( -> 0002) [ 3.169665] intel-ipu6 intel-ipu: Device 0x465d (rev: 0x1) [ 3.169682] intel-ipu6 intel-ipu: physical base address 0x603e00 [ 3.169683] intel-ipu6 intel-ipu: mapped as: 0xd0bf5156 [ 3.169729] intel-ipu6 intel-ipu: Unable to set secure mode [ 3.169730] intel-ipu6 intel-ipu: IPU in non-secure mode [ 3.169731] intel-ipu6 intel-ipu: IPU secure touch = 0x0 [ 3.169731] intel-ipu6 intel-ipu: IPU camera mask = 0xff [ 3.170713] intel-ipu6 intel-ipu: Skip ipc reset for non-secure mode [ 3.170714] intel-ipu6 intel-ipu: IPC reset done [ 3.170715] intel-ipu6 intel-ipu: cpd file name: intel/ipu6ep_fw.bin [ 3.171885] intel-ipu6 intel-ipu: FW version: 20220510 [ 3.174214] intel-ipu6 intel-ipu: IPU6-v3 driver version 1.0 [ 3.218000] intel-ipu6-psys intel-ipu6-psys0: pkg_dir entry count:8 [ 3.218094] intel-ipu6-psys intel-ipu6-psys0: psys probe minor: 0 [ 12.433762] vsc_ace spi-INTC1094:00-5db76cf6-0a68-4ed6-9b78-0361635e2447: recv firmware id [ 17.721699] vsc_ace spi-INTC1094:00-5db76cf6-0a68-4ed6-9b78-0361635e2447: command 19 response timeout [ 17.721725] ipu own camera failed [ 17.829513] ov01a10 i2c-OVTI01A0:00: Acquire VSC failed [ 17.829987] ov01a10: probe of i2c-OVTI01A0:00 failed with error -110 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: v4l2-relayd 0.1.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Feb 23 05:16:46 2023 InstallationDate: Installed on 2023-02-23 (0 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: v4l2-relayd UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.modprobe.d.v4l2-relayd.conf: options v4l2loopback exclusive_caps=1 card_label="Intel MIPI Camera" mtime.conffile..etc.modprobe.d.v4l2-relayd.conf: 2023-02-23T03:30:34.242686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008224/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008224] Re: Intel MIPI Camera does not work on Ubuntu 22.04.02
I tried on TRBA-DVT2-C1_202112-29801 with warm boot 10 times, the kernel does not report error. MIPI camera works well from webcamtests.com. I'll try to run a stress test to perform 100 times warm boot to see what will happen. -- 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/2008224 Title: Intel MIPI Camera does not work on Ubuntu 22.04.02 Status in linux package in Ubuntu: Incomplete Status in v4l2-relayd package in Ubuntu: Invalid Status in linux source package in Jammy: Confirmed Status in v4l2-relayd source package in Jammy: Invalid Bug description: Install Ubuntu 22.04.02 daily build (2023-02-23), the camera does not work with Google Meet and any sort of camera application. [steps] 1. boot into OS 2. check kernel log [rate] 1/3 [kernel] [ 3.169297] intel-ipu6 intel-ipu: enabling device ( -> 0002) [ 3.169665] intel-ipu6 intel-ipu: Device 0x465d (rev: 0x1) [ 3.169682] intel-ipu6 intel-ipu: physical base address 0x603e00 [ 3.169683] intel-ipu6 intel-ipu: mapped as: 0xd0bf5156 [ 3.169729] intel-ipu6 intel-ipu: Unable to set secure mode [ 3.169730] intel-ipu6 intel-ipu: IPU in non-secure mode [ 3.169731] intel-ipu6 intel-ipu: IPU secure touch = 0x0 [ 3.169731] intel-ipu6 intel-ipu: IPU camera mask = 0xff [ 3.170713] intel-ipu6 intel-ipu: Skip ipc reset for non-secure mode [ 3.170714] intel-ipu6 intel-ipu: IPC reset done [ 3.170715] intel-ipu6 intel-ipu: cpd file name: intel/ipu6ep_fw.bin [ 3.171885] intel-ipu6 intel-ipu: FW version: 20220510 [ 3.174214] intel-ipu6 intel-ipu: IPU6-v3 driver version 1.0 [ 3.218000] intel-ipu6-psys intel-ipu6-psys0: pkg_dir entry count:8 [ 3.218094] intel-ipu6-psys intel-ipu6-psys0: psys probe minor: 0 [ 12.433762] vsc_ace spi-INTC1094:00-5db76cf6-0a68-4ed6-9b78-0361635e2447: recv firmware id [ 17.721699] vsc_ace spi-INTC1094:00-5db76cf6-0a68-4ed6-9b78-0361635e2447: command 19 response timeout [ 17.721725] ipu own camera failed [ 17.829513] ov01a10 i2c-OVTI01A0:00: Acquire VSC failed [ 17.829987] ov01a10: probe of i2c-OVTI01A0:00 failed with error -110 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: v4l2-relayd 0.1.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Feb 23 05:16:46 2023 InstallationDate: Installed on 2023-02-23 (0 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: v4l2-relayd UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.modprobe.d.v4l2-relayd.conf: options v4l2loopback exclusive_caps=1 card_label="Intel MIPI Camera" mtime.conffile..etc.modprobe.d.v4l2-relayd.conf: 2023-02-23T03:30:34.242686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008224/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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-hwe-5.15/5.15.0.67.74~20.04.28)
All autopkgtests for the newly accepted linux-meta-hwe-5.15 (5.15.0.67.74~20.04.28) for focal have finished running. The following regressions have been reported in tests triggered by the package: 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-hwe-5.15 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1871015] Re: test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed (Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL])
Hints removed, closing this bug. ** Changed in: ubuntu-kernel-tests Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1871015 Title: test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed (Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL]) Status in ubuntu-kernel-tests: 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 Bionic: Invalid Status in linux-oem-5.14 source package in Bionic: Invalid Status in linux 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-oem-5.14 source package in Hirsute: Invalid Status in linux source package in Impish: Fix Released Status in linux-oem-5.14 source package in Impish: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux source package in Kinetic: Fix Released Status in linux-oem-5.14 source package in Kinetic: Invalid Bug description: [Impact] test_vxlan_under_vrf.sh in the net category of ubuntu_kernel_selftests will fail on 5.13 kernel with: # selftests: net: test_vxlan_under_vrf.sh # Checking HV connectivity [ OK ] # Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL] not ok 1 selftests: net: test_vxlan_under_vrf.sh # exit=1 Note that this test is not failing on F-oem-5.14 but it's better to have corresponding patches applied to reduce the maintenance cost in the future. [Fix] * e7e4785f selftests: net: test_vxlan_under_vrf: fix HV connectivity test * b50d3b46 selftests: test_vxlan_under_vrf: Fix broken test case Only F-5.4, I-5.13 and F-oem-5.14 need these patches. First patch (e7e4785f): - Can be cherry-picked to F-5.4 / Impish 5.13 - Can be cherry-picked to F-oem-5.14. Second patch (b50d3b46): - Can be cherry-picked to F-5.4 / Impish 5.13 (-C2 is required while applying it due to our SAUCE patches) - F-oem-5.14 has already got this one applied. The reason why we need the second patch is that after the first one got applied, we will see another failure, which we made it an expected failure (XFAIL) with SAUCE patches: Check VM connectivity through VXLAN (underlay in a VRF) [XFAIL] [Test] With the patched test_vxlan_under_vrf.sh test, it can pass on Impish 5.13 and F-oem-5.14 without any issue: Checking HV connectivity [ OK ] Check VM connectivity through VXLAN (underlay in the default VRF) [ OK ] Check VM connectivity through VXLAN (underlay in a VRF) [ OK ] [Where problems could occur] Change limit to test cases, should not have any real impact to any kernel functions. But if these fixes are incorrect we will see failures in our regression-testing report. The worst scenario is getting false-negative results. v2: Update cover-letter content and target in patch title to make it easier to read. [Original Bug Report] Issue found with GCP 5.3.0-1017.18~18.04.1 # selftests: net: test_vxlan_under_vrf.sh # Checking HV connectivity [ OK ] # Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL] not ok 25 selftests: net: test_vxlan_under_vrf.sh # exit=1 The failure is different from bug 1837348 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1871015/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2004235] Re: mlxbf-pmc counters not functional for llt_miss block
** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2004235 Title: mlxbf-pmc counters not functional for llt_miss block Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Focal: Fix Committed Status in linux-bluefield source package in Jammy: Fix Committed Bug description: SRU Justification: [Impact] Currently, the driver uses fixed offsets for the control and data registers in the performance counter module. However, this is not correct since the module is not uniform in all HW blocks, and in this case, the llt_miss block is different from the rest. [Fix] The number of counters present in each block is not fixed, and hence the offsets for the control and data registers should also be calculated accordingly. [Test Case] Without the fix, writing 1 to the llt_miss "enable" file will not result in any of the counters incrementing. With the fix, the counters should increment even with the default event settings. [Regression Potential] Can be considered minimal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2004235/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007516] Re: XPS 9320 screen flicker on UHD panel 3840x2400
** Changed in: linux-oem-6.1 (Ubuntu Jammy) Assignee: Kai-Heng Feng (kaihengfeng) => (unassigned) ** Changed in: linux (Ubuntu Kinetic) Assignee: Kai-Heng Feng (kaihengfeng) => (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2007516 Title: XPS 9320 screen flicker on UHD panel 3840x2400 Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Confirmed Status in linux source package in Kinetic: Confirmed Status in linux-oem-6.1 source package in Kinetic: Invalid Bug description: The screen flicker after ubuntu jammy upgrade kernel to 5.19. The enable_psr2_sel_fetch was disabled in 5.15 kernel but enabled in 5.19 kernel. I try to add "options i915 enable_psr2_sel_fetch=0" to modprobe config can omit the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2007516/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007516] Re: XPS 9320 screen flicker on UHD panel 3840x2400
** Tags added: regression-update -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2007516 Title: XPS 9320 screen flicker on UHD panel 3840x2400 Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Confirmed Status in linux source package in Kinetic: Confirmed Status in linux-oem-6.1 source package in Kinetic: Invalid Bug description: The screen flicker after ubuntu jammy upgrade kernel to 5.19. The enable_psr2_sel_fetch was disabled in 5.15 kernel but enabled in 5.19 kernel. I try to add "options i915 enable_psr2_sel_fetch=0" to modprobe config can omit the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2007516/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007516] Re: XPS 9320 screen flicker on UHD panel 3840x2400
** Changed in: linux-oem-6.1 (Ubuntu Jammy) Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2007516 Title: XPS 9320 screen flicker on UHD panel 3840x2400 Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Confirmed Status in linux source package in Kinetic: Confirmed Status in linux-oem-6.1 source package in Kinetic: Invalid Bug description: The screen flicker after ubuntu jammy upgrade kernel to 5.19. The enable_psr2_sel_fetch was disabled in 5.15 kernel but enabled in 5.19 kernel. I try to add "options i915 enable_psr2_sel_fetch=0" to modprobe config can omit the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2007516/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007516] Re: XPS 9320 screen flicker on UHD panel 3840x2400
** Changed in: linux (Ubuntu Kinetic) Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2007516 Title: XPS 9320 screen flicker on UHD panel 3840x2400 Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Confirmed Status in linux source package in Kinetic: Confirmed Status in linux-oem-6.1 source package in Kinetic: Invalid Bug description: The screen flicker after ubuntu jammy upgrade kernel to 5.19. The enable_psr2_sel_fetch was disabled in 5.15 kernel but enabled in 5.19 kernel. I try to add "options i915 enable_psr2_sel_fetch=0" to modprobe config can omit the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2007516/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007516] Re: XPS 9320 screen flicker on UHD panel 3840x2400
** Tags added: ubuntu-certified -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2007516 Title: XPS 9320 screen flicker on UHD panel 3840x2400 Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Confirmed Status in linux source package in Kinetic: Confirmed Status in linux-oem-6.1 source package in Kinetic: Invalid Bug description: The screen flicker after ubuntu jammy upgrade kernel to 5.19. The enable_psr2_sel_fetch was disabled in 5.15 kernel but enabled in 5.19 kernel. I try to add "options i915 enable_psr2_sel_fetch=0" to modprobe config can omit the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2007516/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008224] Re: Intel MIPI Camera does not work on Ubuntu 22.04.02
BIOS on TRBA-DVT2-C5_202112-29763 is 2.0.0 ** Description changed: Install Ubuntu 22.04.02 daily build (2023-02-23), the camera does not work with Google Meet and any sort of camera application. + + [steps] + 1. boot into OS + 2. check kernel log + + [rate] + 1/3 + + [kernel] + [ 3.169297] intel-ipu6 intel-ipu: enabling device ( -> 0002) + [ 3.169665] intel-ipu6 intel-ipu: Device 0x465d (rev: 0x1) + [ 3.169682] intel-ipu6 intel-ipu: physical base address 0x603e00 + [ 3.169683] intel-ipu6 intel-ipu: mapped as: 0xd0bf5156 + [ 3.169729] intel-ipu6 intel-ipu: Unable to set secure mode + [ 3.169730] intel-ipu6 intel-ipu: IPU in non-secure mode + [ 3.169731] intel-ipu6 intel-ipu: IPU secure touch = 0x0 + [ 3.169731] intel-ipu6 intel-ipu: IPU camera mask = 0xff + [ 3.170713] intel-ipu6 intel-ipu: Skip ipc reset for non-secure mode + [ 3.170714] intel-ipu6 intel-ipu: IPC reset done + [ 3.170715] intel-ipu6 intel-ipu: cpd file name: intel/ipu6ep_fw.bin + [ 3.171885] intel-ipu6 intel-ipu: FW version: 20220510 + [ 3.174214] intel-ipu6 intel-ipu: IPU6-v3 driver version 1.0 + [ 3.218000] intel-ipu6-psys intel-ipu6-psys0: pkg_dir entry count:8 + [ 3.218094] intel-ipu6-psys intel-ipu6-psys0: psys probe minor: 0 + [ 12.433762] vsc_ace spi-INTC1094:00-5db76cf6-0a68-4ed6-9b78-0361635e2447: recv firmware id + [ 17.721699] vsc_ace spi-INTC1094:00-5db76cf6-0a68-4ed6-9b78-0361635e2447: command 19 response timeout + [ 17.721725] ipu own camera failed + [ 17.829513] ov01a10 i2c-OVTI01A0:00: Acquire VSC failed + [ 17.829987] ov01a10: probe of i2c-OVTI01A0:00 failed with error -110 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: v4l2-relayd 0.1.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Feb 23 05:16:46 2023 InstallationDate: Installed on 2023-02-23 (0 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: v4l2-relayd UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.modprobe.d.v4l2-relayd.conf: options v4l2loopback exclusive_caps=1 card_label="Intel MIPI Camera" mtime.conffile..etc.modprobe.d.v4l2-relayd.conf: 2023-02-23T03:30:34.242686 -- 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/2008224 Title: Intel MIPI Camera does not work on Ubuntu 22.04.02 Status in linux package in Ubuntu: Incomplete Status in v4l2-relayd package in Ubuntu: Invalid Status in linux source package in Jammy: Confirmed Status in v4l2-relayd source package in Jammy: Invalid Bug description: Install Ubuntu 22.04.02 daily build (2023-02-23), the camera does not work with Google Meet and any sort of camera application. [steps] 1. boot into OS 2. check kernel log [rate] 1/3 [kernel] [ 3.169297] intel-ipu6 intel-ipu: enabling device ( -> 0002) [ 3.169665] intel-ipu6 intel-ipu: Device 0x465d (rev: 0x1) [ 3.169682] intel-ipu6 intel-ipu: physical base address 0x603e00 [ 3.169683] intel-ipu6 intel-ipu: mapped as: 0xd0bf5156 [ 3.169729] intel-ipu6 intel-ipu: Unable to set secure mode [ 3.169730] intel-ipu6 intel-ipu: IPU in non-secure mode [ 3.169731] intel-ipu6 intel-ipu: IPU secure touch = 0x0 [ 3.169731] intel-ipu6 intel-ipu: IPU camera mask = 0xff [ 3.170713] intel-ipu6 intel-ipu: Skip ipc reset for non-secure mode [ 3.170714] intel-ipu6 intel-ipu: IPC reset done [ 3.170715] intel-ipu6 intel-ipu: cpd file name: intel/ipu6ep_fw.bin [ 3.171885] intel-ipu6 intel-ipu: FW version: 20220510 [ 3.174214] intel-ipu6 intel-ipu: IPU6-v3 driver version 1.0 [ 3.218000] intel-ipu6-psys intel-ipu6-psys0: pkg_dir entry count:8 [ 3.218094] intel-ipu6-psys intel-ipu6-psys0: psys probe minor: 0 [ 12.433762] vsc_ace spi-INTC1094:00-5db76cf6-0a68-4ed6-9b78-0361635e2447: recv firmware id [ 17.721699] vsc_ace spi-INTC1094:00-5db76cf6-0a68-4ed6-9b78-0361635e2447: command 19 response timeout [ 17.721725] ipu own camera failed [ 17.829513] ov01a10 i2c-OVTI01A0:00: Acquire VSC failed [ 17.829987] ov01a10: probe of i2c-OVTI01A0:00 failed with error -110 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: v4l2-relayd 0.1.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Feb 23 05:16:46 2023 InstallationDate: Installed on 2023-02-23 (0 day
[Kernel-packages] [Bug 2008224] 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 2008224 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/2008224 Title: Intel MIPI Camera does not work on Ubuntu 22.04.02 Status in linux package in Ubuntu: Incomplete Status in v4l2-relayd package in Ubuntu: Invalid Status in linux source package in Jammy: Confirmed Status in v4l2-relayd source package in Jammy: Invalid Bug description: Install Ubuntu 22.04.02 daily build (2023-02-23), the camera does not work with Google Meet and any sort of camera application. [steps] 1. boot into OS 2. check kernel log [rate] 1/3 [kernel] [ 3.169297] intel-ipu6 intel-ipu: enabling device ( -> 0002) [ 3.169665] intel-ipu6 intel-ipu: Device 0x465d (rev: 0x1) [ 3.169682] intel-ipu6 intel-ipu: physical base address 0x603e00 [ 3.169683] intel-ipu6 intel-ipu: mapped as: 0xd0bf5156 [ 3.169729] intel-ipu6 intel-ipu: Unable to set secure mode [ 3.169730] intel-ipu6 intel-ipu: IPU in non-secure mode [ 3.169731] intel-ipu6 intel-ipu: IPU secure touch = 0x0 [ 3.169731] intel-ipu6 intel-ipu: IPU camera mask = 0xff [ 3.170713] intel-ipu6 intel-ipu: Skip ipc reset for non-secure mode [ 3.170714] intel-ipu6 intel-ipu: IPC reset done [ 3.170715] intel-ipu6 intel-ipu: cpd file name: intel/ipu6ep_fw.bin [ 3.171885] intel-ipu6 intel-ipu: FW version: 20220510 [ 3.174214] intel-ipu6 intel-ipu: IPU6-v3 driver version 1.0 [ 3.218000] intel-ipu6-psys intel-ipu6-psys0: pkg_dir entry count:8 [ 3.218094] intel-ipu6-psys intel-ipu6-psys0: psys probe minor: 0 [ 12.433762] vsc_ace spi-INTC1094:00-5db76cf6-0a68-4ed6-9b78-0361635e2447: recv firmware id [ 17.721699] vsc_ace spi-INTC1094:00-5db76cf6-0a68-4ed6-9b78-0361635e2447: command 19 response timeout [ 17.721725] ipu own camera failed [ 17.829513] ov01a10 i2c-OVTI01A0:00: Acquire VSC failed [ 17.829987] ov01a10: probe of i2c-OVTI01A0:00 failed with error -110 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: v4l2-relayd 0.1.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Feb 23 05:16:46 2023 InstallationDate: Installed on 2023-02-23 (0 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: v4l2-relayd UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.modprobe.d.v4l2-relayd.conf: options v4l2loopback exclusive_caps=1 card_label="Intel MIPI Camera" mtime.conffile..etc.modprobe.d.v4l2-relayd.conf: 2023-02-23T03:30:34.242686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008224/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008224] Re: Intel MIPI Camera does not work on Ubuntu 22.04.02
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: v4l2-relayd (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: v4l2-relayd (Ubuntu Jammy) Status: New => Invalid ** Changed in: v4l2-relayd (Ubuntu) Status: New => Invalid ** Changed in: linux (Ubuntu Jammy) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2008224 Title: Intel MIPI Camera does not work on Ubuntu 22.04.02 Status in linux package in Ubuntu: Incomplete Status in v4l2-relayd package in Ubuntu: Invalid Status in linux source package in Jammy: Confirmed Status in v4l2-relayd source package in Jammy: Invalid Bug description: Install Ubuntu 22.04.02 daily build (2023-02-23), the camera does not work with Google Meet and any sort of camera application. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: v4l2-relayd 0.1.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Feb 23 05:16:46 2023 InstallationDate: Installed on 2023-02-23 (0 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: v4l2-relayd UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.modprobe.d.v4l2-relayd.conf: options v4l2loopback exclusive_caps=1 card_label="Intel MIPI Camera" mtime.conffile..etc.modprobe.d.v4l2-relayd.conf: 2023-02-23T03:30:34.242686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008224/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-restricted-modules-lowlatency-hwe-5.19/5.19.0-1018.19~22.04.1+1)
All autopkgtests for the newly accepted linux-restricted-modules-lowlatency-hwe-5.19 (5.19.0-1018.19~22.04.1+1) for jammy have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.1 (i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#linux-restricted-modules-lowlatency- hwe-5.19 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1988836] Autopkgtest regression report (linux-restricted-modules-lowlatency-hwe-5.19/5.19.0-1018.19~22.04.1+1)
All autopkgtests for the newly accepted linux-restricted-modules-lowlatency-hwe-5.19 (5.19.0-1018.19~22.04.1+1) for jammy have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.1 (i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#linux-restricted-modules-lowlatency- hwe-5.19 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1988836 Title: LRMv7: Enable the open NVIDIA kernel modules Status in linux-restricted-modules package in Ubuntu: In Progress Status in nvidia-graphics-drivers-515 package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in linux-restricted-modules source package in Focal: In Progress Status in nvidia-graphics-drivers-515 source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Focal: Fix Committed Status in linux-restricted-modules source package in Jammy: In Progress Status in nvidia-graphics-drivers-515 source package in Jammy: Fix Released Status in ubuntu-drivers-common source package in Jammy: Fix Committed Bug description: [ Impact ] * The 515 series introduced open kernel modules for the NVIDIA driver. They come with an open source licence, and should be provided as an option for datacenter GPUs: https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/ Currently, this is only production-ready (and enabled) on datacenter GPUs. * We should enable signed modules for the 515-open drivers, giving users the option to try the drivers. * The ubuntu-drivers tool should set a lower priority for the -open flavour, so that we do not end up recommending it over the plain 515 flavour. [ Test Plan ] * [ubuntu-drivers-common]: "sudo ubuntu-drivers install (to make sure the driver is not installed by default)" * [nvidia driver] "sudo ubuntu-drivers install nvidia:515-open" to make sure that the driver can be installed manually. Please make sure that this installs the correct linux-restricted- modules. Note: support for GeForce and Workstation GPUs is alpha-quality, and is disabled by default. This means that desktop testing is not needed at the moment. [ Where problems could occur ] * This adds a new driver combination, which is not meant to be default, and is only enabled for a limited amount of devices (datacenter GPUs). * We need to be sure that the driver is not recommended over the other drivers. [ Other Info ] - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2003995] Re: Update the 525 and 525-server NVIDIA driver series in Bionic, Focal, Jammy, and Kinetic
This bug was fixed in the package nvidia-graphics-drivers-525 - 525.85.05-0ubuntu1 --- nvidia-graphics-drivers-525 (525.85.05-0ubuntu1) lunar; urgency=medium * New upstream release (LP: #2003995): - Improved the reliability of suspend and resume on UEFI systems when using certain display panels. - Fixed a bug that could cause VK_ERROR_DEVICE_LOST when using VK_MEMORY_ALLOCATE_DEVICE_ADDRESS_CAPTURE_REPLAY_BIT to allocate memory. - Disabled Fixed Rate Link (FRL) when using passive DisplayPort to HDMI dongles, which are incompatible with FRL. * debian/templates/control.in: - Add Conflicts, Replaces, Provides up to libcuda-11.7-1. -- Alberto Milone Wed, 01 Feb 2023 11:31:00 + ** Changed in: nvidia-graphics-drivers-525 (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/2003995 Title: Update the 525 and 525-server NVIDIA driver series in Bionic, Focal, Jammy, and Kinetic Status in fabric-manager-515 package in Ubuntu: Fix Released Status in fabric-manager-525 package in Ubuntu: Fix Released Status in libnvidia-nscq-515 package in Ubuntu: Fix Released Status in libnvidia-nscq-525 package in Ubuntu: Fix Released Status in linux-restricted-modules package in Ubuntu: New Status in linux-restricted-modules-hwe package in Ubuntu: New Status in nvidia-graphics-drivers-515-server package in Ubuntu: Triaged Status in nvidia-graphics-drivers-525 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-525-server package in Ubuntu: Fix Released Status in fabric-manager-515 source package in Bionic: Triaged Status in fabric-manager-525 source package in Bionic: Triaged Status in libnvidia-nscq-515 source package in Bionic: Triaged Status in libnvidia-nscq-525 source package in Bionic: Triaged Status in linux-restricted-modules source package in Bionic: New Status in linux-restricted-modules-hwe source package in Bionic: New Status in nvidia-graphics-drivers-515-server source package in Bionic: Triaged Status in nvidia-graphics-drivers-525 source package in Bionic: Triaged Status in nvidia-graphics-drivers-525-server source package in Bionic: Triaged Status in fabric-manager-515 source package in Focal: Triaged Status in fabric-manager-525 source package in Focal: Triaged Status in libnvidia-nscq-515 source package in Focal: Triaged Status in libnvidia-nscq-525 source package in Focal: Triaged Status in linux-restricted-modules source package in Focal: New Status in linux-restricted-modules-hwe source package in Focal: New Status in nvidia-graphics-drivers-515-server source package in Focal: Triaged Status in nvidia-graphics-drivers-525 source package in Focal: Triaged Status in nvidia-graphics-drivers-525-server source package in Focal: Triaged Status in fabric-manager-515 source package in Jammy: Triaged Status in fabric-manager-525 source package in Jammy: Triaged Status in libnvidia-nscq-515 source package in Jammy: Triaged Status in libnvidia-nscq-525 source package in Jammy: Triaged Status in linux-restricted-modules source package in Jammy: New Status in linux-restricted-modules-hwe source package in Jammy: New Status in nvidia-graphics-drivers-515-server source package in Jammy: Triaged Status in nvidia-graphics-drivers-525 source package in Jammy: Triaged Status in nvidia-graphics-drivers-525-server source package in Jammy: Triaged Status in fabric-manager-515 source package in Kinetic: Triaged Status in fabric-manager-525 source package in Kinetic: Triaged Status in libnvidia-nscq-515 source package in Kinetic: Triaged Status in libnvidia-nscq-525 source package in Kinetic: Triaged Status in linux-restricted-modules source package in Kinetic: New Status in linux-restricted-modules-hwe source package in Kinetic: New Status in nvidia-graphics-drivers-515-server source package in Kinetic: Triaged Status in nvidia-graphics-drivers-525 source package in Kinetic: Triaged Status in nvidia-graphics-drivers-525-server source package in Kinetic: Triaged Bug description: [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta/5.15.0.67.65)
All autopkgtests for the newly accepted linux-meta (5.15.0.67.65) for jammy have finished running. The following regressions have been reported in tests triggered by the package: glibc/2.35-0ubuntu3.1 (amd64) casper/1.470.2 (amd64) systemd/249.11-0ubuntu3.6 (s390x) initramfs-tools/0.140ubuntu13.1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#linux-meta [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 1980848] Re: arc_summary doesn't work with HWE kernel 5.15
Seeing this issue also. $ lsb_release -rd Description:Ubuntu 20.04.5 LTS Release:20.04 $ uname -a Linux alvincura-desktop2 5.15.0-60-generic #66~20.04.1-Ubuntu SMP Wed Jan 25 09:41:30 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux $ sudo apt-cache policy zfsutils-linux zfsutils-linux: Installed: 0.8.3-1ubuntu12.14 Candidate: 0.8.3-1ubuntu12.14 Version table: *** 0.8.3-1ubuntu12.14 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 0.8.3-1ubuntu12 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages $ sudo arc_summary -s arc Traceback (most recent call last): File "/usr/sbin/arc_summary", line 875, in main() File "/usr/sbin/arc_summary", line 826, in main kstats = get_kstats() File "/usr/sbin/arc_summary", line 259, in get_kstats with open(PROC_PATH+section, 'r') as proc_location: FileNotFoundError: [Errno 2] No such file or directory: '/proc/spl/kstat/zfs/xuio_stats' -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1980848 Title: arc_summary doesn't work with HWE kernel 5.15 Status in zfs-linux package in Ubuntu: Confirmed Bug description: # Issue description `arc_summary` no longer works with kernel 5.15. It used to work with previous kernel like 5.13. # Steps to reproduce 1) setup 20.04 with HWE kernel 5.15 2) install `zfsutils-linux` 3) run `arc_summary` $ arc_summary Traceback (most recent call last): File "/usr/sbin/arc_summary", line 875, in main() File "/usr/sbin/arc_summary", line 826, in main kstats = get_kstats() File "/usr/sbin/arc_summary", line 259, in get_kstats with open(PROC_PATH+section, 'r') as proc_location: FileNotFoundError: [Errno 2] No such file or directory: '/proc/spl/kstat/zfs/xuio_stats' Indeed, the xuio_stats file isn't there anymore: $ ll /proc/spl/kstat/zfs/ total 0 dr-xr-xr-x 21 root root 0 Jul 6 10:49 ./ dr-xr-xr-x 4 root root 0 Jul 6 10:49 ../ -rw-r--r-- 1 root root 0 Jul 6 10:49 abdstats -rw-r--r-- 1 root root 0 Jul 6 10:49 arcstats dr-xr-xr-x 20 root root 0 Jul 6 10:49 data/ -rw--- 1 root root 0 Jul 6 10:49 dbgmsg -rw--- 1 root root 0 Jul 6 10:49 dbufs -rw-r--r-- 1 root root 0 Jul 6 10:49 dbufstats dr-xr-xr-x 70 root root 0 Jul 6 10:49 default/ -rw-r--r-- 1 root root 0 Jul 6 10:49 dmu_tx -rw-r--r-- 1 root root 0 Jul 6 10:49 dnodestats -rw-r--r-- 1 root root 0 Jul 6 10:49 fletcher_4_bench -rw-r--r-- 1 root root 0 Jul 6 10:49 fm -rw-r--r-- 1 root root 0 Jul 6 10:49 import_progress -rw-r--r-- 1 root root 0 Jul 6 10:49 metaslab_stats -rw-r--r-- 1 root root 0 Jul 6 10:49 vdev_cache_stats -rw-r--r-- 1 root root 0 Jul 6 10:49 vdev_mirror_stats -rw-r--r-- 1 root root 0 Jul 6 10:49 vdev_raidz_bench -rw-r--r-- 1 root root 0 Jul 6 10:49 zfetchstats -rw-r--r-- 1 root root 0 Jul 6 10:49 zil -rw-r--r-- 1 root root 0 Jul 6 10:49 zstd # Workaround This (naive) patch sidesteps the problem: $ diff -Naur /usr/sbin/arc_summary.old /usr/sbin/arc_summary --- /usr/sbin/arc_summary.old 2022-07-06 10:59:50.752833101 -0400 +++ /usr/sbin/arc_summary 2022-07-06 10:59:22.449113169 -0400 @@ -255,6 +255,8 @@ secs = SECTION_PATHS.values() for section in secs: +if not os.path.exists(PROC_PATH+section): +continue with open(PROC_PATH+section, 'r') as proc_location: lines = [line for line in proc_location] # Additional information $ lsb_release -rd Description: Ubuntu 20.04.4 LTS Release: 20.04 $ uname -r 5.15.0-41-generic $ apt-cache policy zfsutils-linux linux-image-generic-hwe-20.04 zfsutils-linux: Installed: 0.8.3-1ubuntu12.14 Candidate: 0.8.3-1ubuntu12.14 Version table: *** 0.8.3-1ubuntu12.14 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 0.8.3-1ubuntu12.9 500 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 0.8.3-1ubuntu12 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages linux-image-generic-hwe-20.04: Installed: 5.15.0.41.44~20.04.13 Candidate: 5.15.0.41.44~20.04.13 Version table: *** 5.15.0.41.44~20.04.13 400 400 http://us.archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages 100 /var/lib/dpkg/status 5.13.0.52.59~20.04.31 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 5.4.0.26.32 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages To
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-lowlatency-hwe-5.15/5.15.0.67.74~20.04.25)
All autopkgtests for the newly accepted linux-meta-lowlatency-hwe-5.15 (5.15.0.67.74~20.04.25) for focal have finished running. The following regressions have been reported in tests triggered by the package: glibc/2.31-0ubuntu9.9 (amd64) linux-lowlatency-hwe-5.15/5.15.0-67.74~20.04.1 (arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-meta-lowlatency-hwe-5.15 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008434] [NEW] NBS cleanup required in lunar-proposed
Public bug reported: NBS cleanup in lunar-proposed on i386 and armhf old binaries left on i386: libcuda1-384, libnvidia-cfg1-390, nvidia-384, nvidia-384-dev, nvidia-compute-utils-390, nvidia-dkms-390, nvidia-driver-390, nvidia-headless-390, nvidia-headless-no-dkms-390, nvidia-kernel-common-390, nvidia-kernel-source-390, nvidia-utils-390, xserver-xorg-video-nvidia-390 (from 390.157-0ubuntu2) missing build on armhf: libcuda1-384, libnvidia-cfg1-390, libnvidia-compute-390, libnvidia-fbc1-390, libnvidia-gl-390, libnvidia-ifr1-390, nvidia-384, nvidia-384-dev, nvidia-compute-utils-390, nvidia-dkms-390, nvidia-driver-390, nvidia-headless-390, nvidia-headless-no-dkms-390, nvidia-kernel-common-390, nvidia-kernel-source-390, nvidia-utils-390, xserver-xorg-video-nvidia-390 (from 390.157-0ubuntu2) arch:armhf not built yet, autopkgtest delayed there please remove these binaries, as they will no longer be built on 32bit arches. ** Affects: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided Status: Triaged ** Tags: update-excuse -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/2008434 Title: NBS cleanup required in lunar-proposed Status in nvidia-graphics-drivers-390 package in Ubuntu: Triaged Bug description: NBS cleanup in lunar-proposed on i386 and armhf old binaries left on i386: libcuda1-384, libnvidia-cfg1-390, nvidia-384, nvidia-384-dev, nvidia-compute-utils-390, nvidia-dkms-390, nvidia-driver-390, nvidia-headless-390, nvidia-headless-no-dkms-390, nvidia-kernel-common-390, nvidia-kernel-source-390, nvidia-utils-390, xserver-xorg-video-nvidia-390 (from 390.157-0ubuntu2) missing build on armhf: libcuda1-384, libnvidia-cfg1-390, libnvidia-compute-390, libnvidia-fbc1-390, libnvidia-gl-390, libnvidia-ifr1-390, nvidia-384, nvidia-384-dev, nvidia-compute-utils-390, nvidia-dkms-390, nvidia-driver-390, nvidia-headless-390, nvidia-headless-no-dkms-390, nvidia-kernel-common-390, nvidia-kernel-source-390, nvidia-utils-390, xserver-xorg-video-nvidia-390 (from 390.157-0ubuntu2) arch:armhf not built yet, autopkgtest delayed there please remove these binaries, as they will no longer be built on 32bit arches. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2008434/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008118] Re: Freeze on resume from suspend (amdgpu errors)
** Tags added: kubuntu
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2008118
Title:
Freeze on resume from suspend (amdgpu errors)
Status in linux package in Ubuntu:
Confirmed
Bug description:
I'm running Kubuntu 22.04 LTS, fresh install. Most of the time, when
resuming from suspend-to-RAM, the system will freeze. Sometimes the
screen is all black, while other times it is showing the lock screen;
in both cases it's completely unresponsive.
The only way out is to force a reboot with the SYSRQ "REISUB" key
combo. I tried switching VT with Ctrl+Alt+F{1-7}, but it does not
respond.
From a quick look at the logs I can see that it shows a lot of red-
colored error lines from the kernel about amdgpu.
I didn't have this problem with other flavors (used Xubuntu and
Ubuntu, 22.04 and 22.10), so I guess it's a Kubuntu bug.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-60-generic 5.15.0-60.66
ProcVersionSignature: Ubuntu 5.15.0-60.66-generic 5.15.78
Uname: Linux 5.15.0-60-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: dsilva 1217 F pulseaudio
/dev/snd/controlC1: dsilva 1217 F pulseaudio
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: KDE
Date: Wed Feb 22 14:55:20 2023
InstallationDate: Installed on 2023-02-19 (2 days ago)
InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64
(20220809.1)
MachineType: Gigabyte Technology Co., Ltd. B460MDS3H
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-60-generic
root=UUID=5a8a2ff2-be5a-4aa5-ae8b-874e45080a04 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-5.15.0-60-generic N/A
linux-backports-modules-5.15.0-60-generic N/A
linux-firmware 20220329.git681281e4-0ubuntu3.10
RfKill:
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/23/2021
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F5
dmi.board.asset.tag: Default string
dmi.board.name: B460M DS3H
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: Default string
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd11/23/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnB460MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB460MDS3H:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
dmi.product.family: B460 MB
dmi.product.name: B460MDS3H
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008118/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2004645] Re: mmc: sdhci-of-dwcmshc: add the missing device table IDs for acpi
I searched a little bit and still got errors even with the correct link (I think)... Reading package lists... Done E: The repository 'http://archive.ubuntu.com/ubuntu/dists/jammy-proposed restricted Release' does not have a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. -- 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/2004645 Title: mmc: sdhci-of-dwcmshc: add the missing device table IDs for acpi Status in linux-bluefield package in Ubuntu: New Status in linux-bluefield source package in Jammy: Fix Committed Bug description: SRU Justification: [Impact] This change is needed so the sdhci-of-dwcmshc driver can be loaded automatically when built ad kernel module. [Fix] add the missing device table IDs for acpi [Test Case] Build sdhci-of-dwcmshc as kernel module, use modinfo command to make sure the output contains 'acpi*:MLNXBF30:*'. [Regression Potential] No changes to driver funtionality. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2004645/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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-gke-5.15/5.15.0.1028.33~20.04.1)
All autopkgtests for the newly accepted linux-meta-gke-5.15 (5.15.0.1028.33~20.04.1) for focal have finished running. The following regressions have been reported in tests triggered by the package: linux-gke-5.15/5.15.0-1028.33~20.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/focal/update_excuses.html#linux-meta-gke-5.15 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-restricted-modules-lowlatency-hwe-5.19/5.19.0-1018.19~22.04.1)
All autopkgtests for the newly accepted linux-restricted-modules-lowlatency-hwe-5.19 (5.19.0-1018.19~22.04.1) for jammy have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.1 (i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#linux-restricted-modules-lowlatency- hwe-5.19 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1988836] Autopkgtest regression report (linux-restricted-modules-lowlatency-hwe-5.19/5.19.0-1018.19~22.04.1)
All autopkgtests for the newly accepted linux-restricted-modules-lowlatency-hwe-5.19 (5.19.0-1018.19~22.04.1) for jammy have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.1 (i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#linux-restricted-modules-lowlatency- hwe-5.19 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1988836 Title: LRMv7: Enable the open NVIDIA kernel modules Status in linux-restricted-modules package in Ubuntu: In Progress Status in nvidia-graphics-drivers-515 package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in linux-restricted-modules source package in Focal: In Progress Status in nvidia-graphics-drivers-515 source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Focal: Fix Committed Status in linux-restricted-modules source package in Jammy: In Progress Status in nvidia-graphics-drivers-515 source package in Jammy: Fix Released Status in ubuntu-drivers-common source package in Jammy: Fix Committed Bug description: [ Impact ] * The 515 series introduced open kernel modules for the NVIDIA driver. They come with an open source licence, and should be provided as an option for datacenter GPUs: https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/ Currently, this is only production-ready (and enabled) on datacenter GPUs. * We should enable signed modules for the 515-open drivers, giving users the option to try the drivers. * The ubuntu-drivers tool should set a lower priority for the -open flavour, so that we do not end up recommending it over the plain 515 flavour. [ Test Plan ] * [ubuntu-drivers-common]: "sudo ubuntu-drivers install (to make sure the driver is not installed by default)" * [nvidia driver] "sudo ubuntu-drivers install nvidia:515-open" to make sure that the driver can be installed manually. Please make sure that this installs the correct linux-restricted- modules. Note: support for GeForce and Workstation GPUs is alpha-quality, and is disabled by default. This means that desktop testing is not needed at the moment. [ Where problems could occur ] * This adds a new driver combination, which is not meant to be default, and is only enabled for a limited amount of devices (datacenter GPUs). * We need to be sure that the driver is not recommended over the other drivers. [ Other Info ] - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2004645] Re: mmc: sdhci-of-dwcmshc: add the missing device table IDs for acpi
Any suggestion how to upgrade the -propose? I followed the instruction but got failure when running "apt update" Fetched 270 kB in 2s (116 kB/s) Reading package lists... Done E: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/jammy-proposed/main/binary-arm64/Packages 404 Not Found [IP: 185.125.190.36 80] E: Some index files failed to download. They have been ignored, or old ones used instead. -- 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/2004645 Title: mmc: sdhci-of-dwcmshc: add the missing device table IDs for acpi Status in linux-bluefield package in Ubuntu: New Status in linux-bluefield source package in Jammy: Fix Committed Bug description: SRU Justification: [Impact] This change is needed so the sdhci-of-dwcmshc driver can be loaded automatically when built ad kernel module. [Fix] add the missing device table IDs for acpi [Test Case] Build sdhci-of-dwcmshc as kernel module, use modinfo command to make sure the output contains 'acpi*:MLNXBF30:*'. [Regression Potential] No changes to driver funtionality. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2004645/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1814234] Re: rtcpie in timers from ubuntu_kernel_selftests randomly failing
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1814234 Title: rtcpie in timers from ubuntu_kernel_selftests randomly failing Status in ubuntu-kernel-tests: Invalid Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: In Progress Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Kinetic: Fix Committed Status in linux source package in Lunar: Fix Committed Bug description: Node: Standard_D11_v2 Kernel: 4.18.0-1008.8~18.04.1 selftests: timers: rtcpie Periodic IRQ rate is 1024Hz. Counting 20 interrupts at: 2Hz: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 4Hz: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 8Hz: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 16Hz:1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 32Hz:1 2 3 4 5 6 7 PIE delta error: 0.034667 should be close to 0.031250 181. 01/30 20:08:46 DEBUG| utils:0153| [stdout] not ok 1..9 selftests: timers: rtcpie [FAIL] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1814234/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1987430] Re: Ubuntu 22.04 kernel 5.15.0-46-generic leaks kernel memory in kmalloc-2k slabs
I am able to reproduce this issue on 5.15.0-52-generic. However, it
seems to be hidden in 5.15.0-53-generic by this commit:
39cce16cfeed UBUNTU: SAUCE: LSM: Change Landlock from LSMBLOB_NEEDED to
LSMBLOB_NOT_NEEDED
Applying this commit on its own on top of 5.15.0-52-generic stops the
memory leak in the test case described by Matthew in #8. This is
coincidental, since now with apparmor=0 no lsmblob slots are assigned.
Thus as JianlinLv mentions in #12, lsm_multiple_contexts() will return
false, and audit_log_lsm() will exit before any memory is allocated.
Before this commit, landlock was assigned 3 lsmblob slots that did not use the
task_getsecid_obj hook (from dmesg with lsm.debug=1):
[0.155733] LSM: landlock assigned lsmblob slot 0
[0.155733] LSM: landlock assigned lsmblob slot 1
[0.155733] LSM: landlock assigned lsmblob slot 2
Thus, before 5.15.0-53, lsm_multiple_contexts() would return true and
there would be no early exit before memory allocation. With apparmor
disabled, the only LSM modules registered to use lsmblob slots would be
ones that did not implement the task_getsecid_subj hook, so the
localblob variable would not get set by anyone. Hence, there would be
this other early exit (post-allocation) in audit_log_lsm()...
if (blob == NULL) {
security_task_getsecid_subj(current, );
if (!lsmblob_is_set())
return;
...
}
... which is one of the two locations addressed by the patch.
The above commit introduced in 5.15.0-53 does not fix the underlying
problem, but the underlying problem is resolved by JianlinLv's patch.
The patch has received its two ACKs on the SRU mailing list and is
pending application.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1987430
Title:
Ubuntu 22.04 kernel 5.15.0-46-generic leaks kernel memory in
kmalloc-2k slabs
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Jammy:
In Progress
Status in linux source package in Kinetic:
In Progress
Bug description:
Since updating to kernel 5.15.0-46-generic (package version
5.15.0-46.49), all of our Ubuntu 22.04 LTS servers are leaking kernel
memory; our first server with 8 GB of RAM just fatally OOMed, causing
us to detect this. Inspection of OOM reports, /proc/meminfo, and
/proc/slabinfo says that it's mostly going to unreclaimable kmalloc-2k
slabs:
Aug 23 12:51:11 cluster kernel: [361299.864757] Unreclaimable slab
info:
Aug 23 12:51:11 cluster kernel: [361299.864757] Name
Used Total
[...]
Aug 23 12:51:11 cluster kernel: [361299.864924] kmalloc-2k
6676584KB6676596KB
Most of our machines appear to be leaking slab memory at a rate of
around 20 to 40 Mbytes/hour, with some machines leaking much faster;
the champions are leaking kernel memory at 145 Mbytes/hour and 237
Mbytes/hour.
We aren't running any proprietary kernel modules and our only unusual
kernel configuration is that we've disabled AppArmor with 'apparmor=0'
on the kernel command line.
/proc/version_signature:
Ubuntu 5.15.0-46.49-generic 5.15.39
Full kernel command line from the Dell R240 system that fatally OOMd:
BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic
root=UUID=3165564f-a2dd-4b39-935b-114f3e23ff54 ro console=ttyS0,115200
console=tty0 apparmor=0
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987430/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-lowlatency/5.15.0.67.72)
All autopkgtests for the newly accepted linux-meta-lowlatency (5.15.0.67.72) for jammy have finished running. The following regressions have been reported in tests triggered by the package: glibc/2.35-0ubuntu3.1 (amd64) linux-lowlatency/5.15.0-67.74 (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-lowlatency [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 2007718] Re: HWE-22.04 Kernel 5.19 breaks suspend/wake on newer AMD Ryzen 6000u
For completeness: Apport data ** Attachment added: "Apport data" https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-5.19/+bug/2007718/+attachment/5649649/+files/apport.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2007718 Title: HWE-22.04 Kernel 5.19 breaks suspend/wake on newer AMD Ryzen 6000u Status in linux-meta-hwe-5.19 package in Ubuntu: Confirmed Bug description: After 22.04 LTS upgraded the linux-generic-hwe kernel to 5.19.0.32 (from 5.15.0.60) suspend/wake up is broken on my laptop. The system refuses to wake up in about 50% of the cases, seemingly random. The only "solution" is a forced system power down. Reverting back to 5.15.0.60 resolves this issue immediately. I suspect some patch was not re-applied to 5.19, since there are many postings on Reddit (for instance) about sleep problems with newer AMD CPUs, but 5.15 was running beautifully. My machine is a Lenovo Thinkpad T14s AMD Gen 3, AMD 6850u CPU. UPDATE: See attached log. This may not be a case of the laptop failing to resume, but a case of the laptop not suspending properly! What happened was the following. When packing in my things, I closed the laptop and put it in my bag. At home I picked it up again, and immediately noticed how unusually hot it was. The laptop didn't resume properly on opening the lid, but was frozen as before. So this might actually be a case of the laptop FAILING TO SUSPEND properly, instead of failing to wake up. UPDATE: I just noticed the battery was down to the low 40% from at least 80%. Given the temperature on opening the laption I suspect the CPU has been working hard during "sleep time". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-5.19/+bug/2007718/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-restricted-modules-hwe-5.15/5.15.0-67.74~20.04.1)
All autopkgtests for the newly accepted linux-restricted-modules-hwe-5.15 (5.15.0-67.74~20.04.1) for focal have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-390/390.157-0ubuntu0.20.04.1 (i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-restricted-modules-hwe-5.15 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1988836] Autopkgtest regression report (linux-restricted-modules-hwe-5.15/5.15.0-67.74~20.04.1)
All autopkgtests for the newly accepted linux-restricted-modules-hwe-5.15 (5.15.0-67.74~20.04.1) for focal have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-390/390.157-0ubuntu0.20.04.1 (i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-restricted-modules-hwe-5.15 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1988836 Title: LRMv7: Enable the open NVIDIA kernel modules Status in linux-restricted-modules package in Ubuntu: In Progress Status in nvidia-graphics-drivers-515 package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in linux-restricted-modules source package in Focal: In Progress Status in nvidia-graphics-drivers-515 source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Focal: Fix Committed Status in linux-restricted-modules source package in Jammy: In Progress Status in nvidia-graphics-drivers-515 source package in Jammy: Fix Released Status in ubuntu-drivers-common source package in Jammy: Fix Committed Bug description: [ Impact ] * The 515 series introduced open kernel modules for the NVIDIA driver. They come with an open source licence, and should be provided as an option for datacenter GPUs: https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/ Currently, this is only production-ready (and enabled) on datacenter GPUs. * We should enable signed modules for the 515-open drivers, giving users the option to try the drivers. * The ubuntu-drivers tool should set a lower priority for the -open flavour, so that we do not end up recommending it over the plain 515 flavour. [ Test Plan ] * [ubuntu-drivers-common]: "sudo ubuntu-drivers install (to make sure the driver is not installed by default)" * [nvidia driver] "sudo ubuntu-drivers install nvidia:515-open" to make sure that the driver can be installed manually. Please make sure that this installs the correct linux-restricted- modules. Note: support for GeForce and Workstation GPUs is alpha-quality, and is disabled by default. This means that desktop testing is not needed at the moment. [ Where problems could occur ] * This adds a new driver combination, which is not meant to be default, and is only enabled for a limited amount of devices (datacenter GPUs). * We need to be sure that the driver is not recommended over the other drivers. [ Other Info ] - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007734] Re: Black screen on boot and tearing on resume on HP Envy x360
Sorry, it took me some time to realize that "adlp" might be firmware related. In the kernel log, I have the following lines: > sudo dmesg | grep adlp > [2.429107] i915 :00:02.0: [drm] Finished loading DMC firmware > i915/adlp_dmc_ver2_16.bin (v2.16) > [2.557289] i915 :00:02.0: [drm] GuC firmware i915/adlp_guc_70.1.1.bin > version 70.1 These look to match the latest versions available here: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/tree/i915. I also gave a try to Linux 6.2: * The "FRAMEBUFFER=y" hack on the initramfs no longer seems needed. Interestingly, it does not see need on 5.19 anymore either for me :/ * The "i915.enable_psr=0 i915.enable_fbc=1" flags are still needed to avoid tearing. Without these, the tearing also appears after the initial modeset, in addition to sleep exit. With 5.19, the initial modeset yields to a plain black screen. Not sure if this is an improvment :) Thanks for having a look ! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2007734 Title: Black screen on boot and tearing on resume on HP Envy x360 Status in linux package in Ubuntu: Confirmed Bug description: I installed Ubuntu about 1 week ago on a new machine, after testing with a Live USB 22.10 that it was working reasonably well. While the live USB was working pretty well, including 3D acceleration, the installed system failed to display anything after the first mode setting. I was able to work around this first issue with: echo 'FRAMEBUFFER=y' | sudo tee /etc/initramfs-tools/conf.d/hp-envy-x360-quirk sudo update-initramfs -c -k all With this, the system starts correctly, with 3D acceleration. I noticed that, after enabling this option, the initrd image now contained i915 driver and firmware. However, just declaring "i915" /etc/initramfs-tools/modules did not appear to fix the issue. A second, possibly related issue, is that after resume, the screen was displaying random pixels of increasing intensity (tearing ?). I was able to work around this other issue with: echo 'GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i915.enable_psr=0 i915.enable_fbc=1"' | sudo tee /etc/default/grub.d/hp-envy-x360-quirk.cfg sudo update-grub With this second workaround in place, suspend/resumes has been working fine for at least the past couple of days. Let me know if this bug should be split into 2 dedicated bugs or if I can help with any test. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-31-generic 5.19.0-31.32 ProcVersionSignature: Ubuntu 5.19.0-31.32-generic 5.19.17 Uname: Linux 5.19.0-31-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jean-tiare 111982 F pipewire jean-tiare 111986 F wireplumber /dev/snd/pcmC0D0p: jean-tiare 111982 F...m pipewire /dev/snd/seq:jean-tiare 111982 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Feb 17 23:35:44 2023 InstallationDate: Installed on 2023-02-10 (6 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: HP HP ENVY x360 2-in-1 Laptop 15-ew0xxx ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-31-generic root=/dev/mapper/vgubuntu-root ro quiet splash i915.enable_psr=0 i915.enable_fbc=1 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.19.0-31-generic N/A linux-backports-modules-5.19.0-31-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/23/2022 dmi.bios.release: 15.13 dmi.bios.vendor: Insyde dmi.bios.version: F.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8A29 dmi.board.vendor: HP dmi.board.version: 22.41 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 22.41 dmi.modalias: dmi:bvnInsyde:bvrF.13:bd12/23/2022:br15.13:efr22.41:svnHP:pnHPENVYx3602-in-1Laptop15-ew0xxx:pvrType1ProductConfigId:rvnHP:rn8A29:rvr22.41:cvnHP:ct31:cvrChassisVersion:sku6R3F4EA#ABF: dmi.product.family: 103C_5335M8 HP ENVY dmi.product.name: HP ENVY x360 2-in-1 Laptop 15-ew0xxx dmi.product.sku: 6R3F4EA#ABF dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007734/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 2003161] Re: Fix speaker mute hotkey doesn't work on Dell G16 series
** Changed in: linux (Ubuntu Lunar) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Kinetic) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/2003161 Title: Fix speaker mute hotkey doesn't work on Dell G16 series Status in HWE Next: New Status in HWE Next lunar series: Invalid Status in linux package in Ubuntu: Fix Committed Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Committed Status in linux-oem-6.0 source package in Kinetic: New Status in linux-oem-6.1 source package in Kinetic: New Status in linux source package in Lunar: Fix Committed Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] Speaker mute and Mic mute hotkey no function on the G16. [Fix] speaker mute event is sent by EC then dell-wmi can't recognize it. Add a new keymap for KEY_MUTE. Send for OEM kernels first then will SRU for generic kernel once the patch is merged. [Test Case] 1. boot-up with the kernel applied the fix. 2. Play video/audio. 3. Press the speak-mute hotkey 4. can't hear any sounds. [Where problems could occur] Low, only add a keymap the affect would be very limited. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2003161/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2000709] Re: net:cmsg_ipv6.sh from ubuntu_kernel_selftests failed with K-5.19
** Changed in: linux (Ubuntu Kinetic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2000709 Title: net:cmsg_ipv6.sh from ubuntu_kernel_selftests failed with K-5.19 Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Kinetic: Fix Committed Bug description: Issue found with 5.19.0-28.29 Running 'make run_tests -C net TEST_PROGS=cmsg_ipv6.sh TEST_GEN_PROGS='' TEST_CUSTOM_PROGS=''' make: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net' make --no-builtin-rules ARCH=x86 -C ../../../.. headers_install make[1]: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux' INSTALL ./usr/include make[1]: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux' TAP version 13 1..1 # selftests: net: cmsg_ipv6.sh # Case TCLASS UDP setsock - packet data returned 1, expected 0 # Case TCLASS ICMP setsock - packet data returned 1, expected 0 # Case TCLASS RAW setsock - packet data returned 1, expected 0 # Case TCLASS UDP cmsg - packet data returned 1, expected 0 # Case TCLASS ICMP cmsg - packet data returned 1, expected 0 # Case TCLASS RAW cmsg - packet data returned 1, expected 0 # Case TCLASS UDP both - packet data returned 1, expected 0 # Case TCLASS ICMP both - packet data returned 1, expected 0 # Case TCLASS RAW both - packet data returned 1, expected 0 # Case TCLASS UDP diff - packet data returned 1, expected 0 # Case TCLASS ICMP diff - packet data returned 1, expected 0 # Case TCLASS RAW diff - packet data returned 1, expected 0 # Case HOPLIMIT UDP setsock - packet data returned 1, expected 0 # Case HOPLIMIT ICMP setsock - packet data returned 1, expected 0 # Case HOPLIMIT RAW setsock - packet data returned 1, expected 0 # Case HOPLIMIT UDP cmsg - packet data returned 1, expected 0 # Case HOPLIMIT ICMP cmsg - packet data returned 1, expected 0 # Case HOPLIMIT RAW cmsg - packet data returned 1, expected 0 # Case HOPLIMIT UDP both - packet data returned 1, expected 0 # Case HOPLIMIT ICMP both - packet data returned 1, expected 0 # Case HOPLIMIT RAW both - packet data returned 1, expected 0 # Case HOPLIMIT UDP diff - packet data returned 1, expected 0 # Case HOPLIMIT ICMP diff - packet data returned 1, expected 0 # Case HOPLIMIT RAW diff - packet data returned 1, expected 0 # FAIL - 24/93 cases failed not ok 1 selftests: net: cmsg_ipv6.sh # exit=1 This is not a regression as the net test build was blocked with bug 1993155 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2000709/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2004132] Re: btrfs/154: rename fails with EOVERFLOW when calculating item size during item key collision
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2004132 Title: btrfs/154: rename fails with EOVERFLOW when calculating item size during item key collision Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Bug description: BugLink: https://bugs.launchpad.net/bugs/2004132 [Impact] xfstests btrfs/154 fails on both Bionic and Focal, leading to a kernel oops and the btrfs volume being forced readonly. In btrfs, item key collision is allowed for some item types, namely dir item and inode references. When inserting items into the btree, there are two objects, the btrfs_item and the item data. These objects must fit within the btree nodesize. When a hash collision occurs, and we call btrfs_search_slot() to place the objects in the tree, when btrfs_search_slot() reaches the leaf node, a check is performed to see if we need to split the leaf. The check is incorrect, returning that we need to split the leaf, since it thinks that both btrfs_item and the item data need to be inserted, when in reality, the item can be merged with the existing one and no new btrfs_item will be inserted. split_leaf() will return EOVERFLOW from following code: if (extend && data_size + btrfs_item_size_nr(l, slot) + sizeof(struct btrfs_item) > BTRFS_LEAF_DATA_SIZE(fs_info)) return -EOVERFLOW; In the rename case, btrfs_check_dir_item_collision() is called early stages of treewalking, and correctly calculates the needed size, taking into account that a hash collision has occurred. data_size = sizeof(*di) + name_len; if (data_size + btrfs_item_size_nr(leaf, slot) + sizeof(struct btrfs_item) > BTRFS_LEAF_DATA_SIZE(root->fs_info)) The two sizes reported from btrfs_check_dir_item_collision() and btrfs_search_slot() are different, and rename fails due to split_leaf() returning -EOVERFLOW, leading to transaction abort and forcing the volume readonly. Kernel oops: BTRFS: Transaction aborted (error -75) WARNING: CPU: 0 PID: 2921 at /build/linux-fTmV3T/linux-4.15.0/fs/btrfs/inode.c:10217 btrfs_rename+0xcf1/0xdf0 [btrfs] CPU: 0 PID: 2921 Comm: python3 Not tainted 4.15.0-202-generic #213-Ubuntu RIP: 0010:btrfs_rename+0xcf1/0xdf0 [btrfs] RSP: 0018:9e6f4183fd20 EFLAGS: 00010282 RAX: RBX: 91a493f27b98 RCX: 0006 RDX: 0007 RSI: 0096 RDI: 91a4bfc1b4d0 RBP: 9e6f4183fdc0 R08: 02b4 R09: 0004 R10: R11: 0001 R12: 0236 R13: 91a493f56518 R14: 91a4b6b57b40 R15: 91a493f27b98 FS: 7f6041081740() GS:91a4bfc0() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 7f6040fe84c8 CR3: 00015c8ca005 CR4: 00760ef0 PKRU: 5554 Call Trace: btrfs_rename2+0x1d/0x30 [btrfs] vfs_rename+0x46e/0x960 SyS_rename+0x362/0x3c0 do_syscall_64+0x73/0x130 entry_SYSCALL_64_after_hwframe+0x41/0xa6 Code: 0f ba a8 d0 cd 00 00 02 72 2b 41 83 f8 fb 0f 84 d9 00 00 00 44 89 c6 48 c7 c7 68 43 4b c0 44 89 55 80 44 89 45 98 e8 8f 5c a6 d0 <0f> 0b 44 8b 45 98 44 8b 55 80 44 89 55 80 44 89 c1 44 89 45 98 ---[ end trace 9c6b87a19f4436f3 ]--- BTRFS: error (device vdd) in btrfs_rename:10217: errno=-75 unknown BTRFS info (device vdd): forced readonly [Testcase] Start a fresh Bionic or Focal VM. Attach two scratch disks, I used standard virtio disks with 3gb of storage each. These disks are /dev/vdc and /dev/vdd. Compile xfstests: $ sudo apt-get install acl attr automake bc dbench dump e2fsprogs fio gawk \ gcc git indent libacl1-dev libaio-dev libcap-dev libgdbm-dev libtool \ libtool-bin libuuid1 lvm2 make psmisc python3 quota sed \ uuid-dev uuid-runtime xfsprogs linux-headers-$(uname -r) sqlite3 make $ sudo apt-get install f2fs-tools ocfs2-tools udftools xfsdump \ xfslibs-dev $ git clone git://git.kernel.org/pub/scm/fs/xfs/xfstests-dev.git $ cd xfstests-dev $ make $ sudo su # mkdir /test # mkdir /scratch # mkfs.btrfs -f /dev/vdc # cat << EOF >> ./local.config export TEST_DEV=/dev/vdc export TEST_DIR=/test export SCRATCH_DEV=/dev/vdd export SCRATCH_MNT=/scratch EOF # ./check btrfs/154 btrfs/154 _check_dmesg: something found in dmesg (see /home/ubuntu/xfstests-dev/results//btrfs/154.dmesg) - output mismatch (see /home/ubuntu/xfstests-dev/results//btrfs/154.out.bad) --- tests/btrfs/154.out 2023-01-28 02:53:03.566450703 + +++
[Kernel-packages] [Bug 1990700] Re: Fibocom WWAN FM350-GL suspend error (notebook not suspend)
About the 5G support: nm-applet reports LTE, but it does work on 5G. I just got 400+ Mbps yesterday when testing, which obviously is not LTE. Might just be a naming issue there. The sleep issue persists however, latest tests with 6.1.12 are the same as before. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/1990700 Title: Fibocom WWAN FM350-GL suspend error (notebook not suspend) Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux source package in Lunar: Fix Released Status in linux-oem-6.0 source package in Lunar: Invalid Bug description: [SRU Justification] [Impact] Fibocom WWAN FM350-GL equipped platform fails to suspend. [Fix] Full t7xx driver is still under development and some of them have already accepted and merged in mainline kernel. The following commits are once in the mainline and are reverted in v6.0: d20ef656f994 net: wwan: t7xx: Add AP CLDMA 007f26f0d68e net: wwan: t7xx: Infrastructure for early port configuration 140424d90165 net: wwan: t7xx: PCIe reset rescan 87dae9e70bf7 net: wwan: t7xx: Enable devlink based fw flashing and coredump collection The first patch implemented the other AP-CLDMA, and with that applied, platforms in question may suspend and resume normally as every bits are in position. However, while these patches had been reverted for another revision that is still being worked on by the hardware vendor, a minimum, sauced patch is created to work-around this first to meet project schedules, and will be reverted and superseded with a final, mainline landing revision. [Test Case] Trigger suspend and there should be no more suspend errors from t7xx: mtk_t7xx :58:00.0: [PM] SAP suspend error: -110 mtk_t7xx :58:00.0: PM: pci_pm_suspend(): t7xx_pci_pm_suspend+0x0/0x20 [mtk_t7xx] returns -110 mtk_t7xx :58:00.0: PM: dpm_run_callback(): pci_pm_suspend+0x0/0x1a0 returns -110 mtk_t7xx :58:00.0: PM: failed to suspend async: error -110 [Where problems could occur] The t7xx driver is still incomplete and we're staging aforementioned 4 patches in internal experimental kernels for development use. [Other Info] This affects Kinetic and above, so only Unstable, Kinetic and OEM-6.0 are nominated for fix. == original bug report == Hi, I found a "little" problem with Fibocom WWAN FM350-GL 5G modem in module mtk_t7xx . Power management for this modem is bad. When the notebook goes to sleep/suspend, kernel module mtk_t7xx return an error: mtk_t7xx :58:00.0: [PM] SAP suspend error: -110 mtk_t7xx :58:00.0: PM: pci_pm_suspend(): t7xx_pci_pm_suspend+0x0/0x20 [mtk_t7xx] returns -110 mtk_t7xx :58:00.0: PM: dpm_run_callback(): pci_pm_suspend+0x0/0x1a0 returns -110 mtk_t7xx :58:00.0: PM: failed to suspend async: error -110 So power management failed to suspend: PM: Some devices failed to suspend, or early wake event detected And the notebook not suspend and wake up again. It must be this module, because if I remove the module first (modprobe -r), the laptop goes to sleep and wakes up normally. However, after reinserting the module, the modem no longer appears in the system. Expected state: sleep occurs when the device is put to sleep - including the modem. When you wake up, you will wake up, including activating the modem and logging into the operator's network. Description:Ubuntu 20.04.5 LTS Release:20.04 lspci -v: 58:00.0 Wireless controller [0d40]: MEDIATEK Corp. Device 4d75 (rev 01) Subsystem: Device 1cf8:3500 Flags: bus master, fast devsel, latency 0, IRQ 17 Memory at 601e80 (64-bit, prefetchable) [size=32K] Memory at 5e80 (64-bit, non-prefetchable) [size=8M] Memory at 601e00 (64-bit, prefetchable) [size=8M] Capabilities: [80] Express Endpoint, MSI 00 Capabilities: [d0] MSI-X: Enable+ Count=34 Masked- Capabilities: [e0] MSI: Enable- Count=1/32 Maskable+ 64bit+ Capabilities: [f8] Power 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
[Kernel-packages] [Bug 2007718] Re: HWE-22.04 Kernel 5.19 breaks suspend/wake on newer AMD Ryzen 6000u
This also affects at least some older Ryzens too. I have a 5800u that is affected by this bug. As mentioned, the previous 5.15 kernel still suspends and resumes reliably. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2007718 Title: HWE-22.04 Kernel 5.19 breaks suspend/wake on newer AMD Ryzen 6000u Status in linux-meta-hwe-5.19 package in Ubuntu: Confirmed Bug description: After 22.04 LTS upgraded the linux-generic-hwe kernel to 5.19.0.32 (from 5.15.0.60) suspend/wake up is broken on my laptop. The system refuses to wake up in about 50% of the cases, seemingly random. The only "solution" is a forced system power down. Reverting back to 5.15.0.60 resolves this issue immediately. I suspect some patch was not re-applied to 5.19, since there are many postings on Reddit (for instance) about sleep problems with newer AMD CPUs, but 5.15 was running beautifully. My machine is a Lenovo Thinkpad T14s AMD Gen 3, AMD 6850u CPU. UPDATE: See attached log. This may not be a case of the laptop failing to resume, but a case of the laptop not suspending properly! What happened was the following. When packing in my things, I closed the laptop and put it in my bag. At home I picked it up again, and immediately noticed how unusually hot it was. The laptop didn't resume properly on opening the lid, but was frozen as before. So this might actually be a case of the laptop FAILING TO SUSPEND properly, instead of failing to wake up. UPDATE: I just noticed the battery was down to the low 40% from at least 80%. Given the temperature on opening the laption I suspect the CPU has been working hard during "sleep time". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-5.19/+bug/2007718/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007718] Re: HWE-22.04 Kernel 5.19 breaks suspend/wake on newer AMD Ryzen 6000u
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-meta-hwe-5.19 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2007718 Title: HWE-22.04 Kernel 5.19 breaks suspend/wake on newer AMD Ryzen 6000u Status in linux-meta-hwe-5.19 package in Ubuntu: Confirmed Bug description: After 22.04 LTS upgraded the linux-generic-hwe kernel to 5.19.0.32 (from 5.15.0.60) suspend/wake up is broken on my laptop. The system refuses to wake up in about 50% of the cases, seemingly random. The only "solution" is a forced system power down. Reverting back to 5.15.0.60 resolves this issue immediately. I suspect some patch was not re-applied to 5.19, since there are many postings on Reddit (for instance) about sleep problems with newer AMD CPUs, but 5.15 was running beautifully. My machine is a Lenovo Thinkpad T14s AMD Gen 3, AMD 6850u CPU. UPDATE: See attached log. This may not be a case of the laptop failing to resume, but a case of the laptop not suspending properly! What happened was the following. When packing in my things, I closed the laptop and put it in my bag. At home I picked it up again, and immediately noticed how unusually hot it was. The laptop didn't resume properly on opening the lid, but was frozen as before. So this might actually be a case of the laptop FAILING TO SUSPEND properly, instead of failing to wake up. UPDATE: I just noticed the battery was down to the low 40% from at least 80%. Given the temperature on opening the laption I suspect the CPU has been working hard during "sleep time". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-5.19/+bug/2007718/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958918] Re: dependency on crda obsolete according to Debian
** Also affects: linux-aws-5.19 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-aws-5.19 (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux-aws-5.19 (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-aws-5.19 (Ubuntu Jammy) Assignee: (unassigned) => Tim Gardner (timg-tpi) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lowlatency in Ubuntu. https://bugs.launchpad.net/bugs/1958918 Title: dependency on crda obsolete according to Debian Status in crda package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-aws package in Ubuntu: Fix Released Status in linux-aws-5.19 package in Ubuntu: New Status in linux-azure package in Ubuntu: Fix Released Status in linux-gcp package in Ubuntu: Fix Released Status in linux-lowlatency package in Ubuntu: Fix Released Status in linux-oracle package in Ubuntu: Fix Released Status in linux-raspi package in Ubuntu: Fix Released Status in wireless-regdb package in Ubuntu: New Status in crda source package in Jammy: Fix Released Status in linux source package in Jammy: Fix Released Status in linux-aws source package in Jammy: Fix Released Status in linux-aws-5.19 source package in Jammy: In Progress Status in linux-azure source package in Jammy: Fix Released Status in linux-gcp source package in Jammy: Fix Released Status in linux-lowlatency source package in Jammy: Fix Released Status in linux-oracle source package in Jammy: Fix Released Status in linux-raspi source package in Jammy: Fix Released Status in wireless-regdb source package in Jammy: New Status in crda package in Debian: Fix Released Bug description: Debian has just removed the crda package from the archive, stating that it is obsolete with current kernels: https://bugs.debian.org/1003903 We need someone to determine if this is accurate for Ubuntu as well, and if so, update the kernel packaging to not depend on crda anymore so it can be removed. wireless-regdb should stop shipping /lib/crda files which only removed crda package used to use. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crda/+bug/1958918/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-restricted-modules-lowlatency/5.15.0-67.74)
All autopkgtests for the newly accepted linux-restricted-modules-lowlatency (5.15.0-67.74) for jammy have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.1 (i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#linux-restricted-modules-lowlatency [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-restricted-modules-lowlatency-hwe-5.15/5.15.0-67.74~20.04.1)
All autopkgtests for the newly accepted linux-restricted-modules-lowlatency-hwe-5.15 (5.15.0-67.74~20.04.1) for focal have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-525/525.85.05-0ubuntu0.20.04.1 (amd64) nvidia-graphics-drivers-390/390.157-0ubuntu0.20.04.1 (i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-restricted-modules-lowlatency- hwe-5.15 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1988836] Autopkgtest regression report (linux-restricted-modules-lowlatency/5.15.0-67.74)
All autopkgtests for the newly accepted linux-restricted-modules-lowlatency (5.15.0-67.74) for jammy have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.1 (i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#linux-restricted-modules-lowlatency [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1988836 Title: LRMv7: Enable the open NVIDIA kernel modules Status in linux-restricted-modules package in Ubuntu: In Progress Status in nvidia-graphics-drivers-515 package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in linux-restricted-modules source package in Focal: In Progress Status in nvidia-graphics-drivers-515 source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Focal: Fix Committed Status in linux-restricted-modules source package in Jammy: In Progress Status in nvidia-graphics-drivers-515 source package in Jammy: Fix Released Status in ubuntu-drivers-common source package in Jammy: Fix Committed Bug description: [ Impact ] * The 515 series introduced open kernel modules for the NVIDIA driver. They come with an open source licence, and should be provided as an option for datacenter GPUs: https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/ Currently, this is only production-ready (and enabled) on datacenter GPUs. * We should enable signed modules for the 515-open drivers, giving users the option to try the drivers. * The ubuntu-drivers tool should set a lower priority for the -open flavour, so that we do not end up recommending it over the plain 515 flavour. [ Test Plan ] * [ubuntu-drivers-common]: "sudo ubuntu-drivers install (to make sure the driver is not installed by default)" * [nvidia driver] "sudo ubuntu-drivers install nvidia:515-open" to make sure that the driver can be installed manually. Please make sure that this installs the correct linux-restricted- modules. Note: support for GeForce and Workstation GPUs is alpha-quality, and is disabled by default. This means that desktop testing is not needed at the moment. [ Where problems could occur ] * This adds a new driver combination, which is not meant to be default, and is only enabled for a limited amount of devices (datacenter GPUs). * We need to be sure that the driver is not recommended over the other drivers. [ Other Info ] - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1988836] Autopkgtest regression report (linux-restricted-modules-lowlatency-hwe-5.15/5.15.0-67.74~20.04.1)
All autopkgtests for the newly accepted linux-restricted-modules-lowlatency-hwe-5.15 (5.15.0-67.74~20.04.1) for focal have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-525/525.85.05-0ubuntu0.20.04.1 (amd64) nvidia-graphics-drivers-390/390.157-0ubuntu0.20.04.1 (i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-restricted-modules-lowlatency- hwe-5.15 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1988836 Title: LRMv7: Enable the open NVIDIA kernel modules Status in linux-restricted-modules package in Ubuntu: In Progress Status in nvidia-graphics-drivers-515 package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in linux-restricted-modules source package in Focal: In Progress Status in nvidia-graphics-drivers-515 source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Focal: Fix Committed Status in linux-restricted-modules source package in Jammy: In Progress Status in nvidia-graphics-drivers-515 source package in Jammy: Fix Released Status in ubuntu-drivers-common source package in Jammy: Fix Committed Bug description: [ Impact ] * The 515 series introduced open kernel modules for the NVIDIA driver. They come with an open source licence, and should be provided as an option for datacenter GPUs: https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/ Currently, this is only production-ready (and enabled) on datacenter GPUs. * We should enable signed modules for the 515-open drivers, giving users the option to try the drivers. * The ubuntu-drivers tool should set a lower priority for the -open flavour, so that we do not end up recommending it over the plain 515 flavour. [ Test Plan ] * [ubuntu-drivers-common]: "sudo ubuntu-drivers install (to make sure the driver is not installed by default)" * [nvidia driver] "sudo ubuntu-drivers install nvidia:515-open" to make sure that the driver can be installed manually. Please make sure that this installs the correct linux-restricted- modules. Note: support for GeForce and Workstation GPUs is alpha-quality, and is disabled by default. This means that desktop testing is not needed at the moment. [ Where problems could occur ] * This adds a new driver combination, which is not meant to be default, and is only enabled for a limited amount of devices (datacenter GPUs). * We need to be sure that the driver is not recommended over the other drivers. [ Other Info ] - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007718] Re: HWE-22.04 Kernel 5.19 breaks suspend/wake on newer AMD Ryzen 6000u
** Description changed: After 22.04 LTS upgraded the linux-generic-hwe kernel to 5.19.0.32 (from 5.15.0.60) suspend/wake up is broken on my laptop. The system refuses to wake up in about 50% of the cases, seemingly random. The only "solution" is a forced system power down. Reverting back to 5.15.0.60 resolves this issue immediately. I suspect some patch was not re-applied to 5.19, since there are many postings on Reddit (for instance) about sleep problems with newer AMD CPUs, but 5.15 was running beautifully. My machine is a Lenovo Thinkpad T14s AMD Gen 3, AMD 6850u CPU. UPDATE: See attached log. This may not be a case of the laptop failing to resume, but a case of the laptop not suspending properly! What happened was the following. When packing in my things, I closed the laptop and put it in my bag. At home I picked it up again, and immediately noticed how unusually hot it was. The laptop didn't resume properly on opening the lid, but was frozen as before. So this might actually be a case of the laptop FAILING TO SUSPEND properly, instead of failing to wake up. + + UPDATE: + + I just noticed the battery was down to the low 40% from at least 80%. + Given the temperature on opening the laption I suspect the CPU has been + working hard during "sleep time". -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2007718 Title: HWE-22.04 Kernel 5.19 breaks suspend/wake on newer AMD Ryzen 6000u Status in linux-meta-hwe-5.19 package in Ubuntu: New Bug description: After 22.04 LTS upgraded the linux-generic-hwe kernel to 5.19.0.32 (from 5.15.0.60) suspend/wake up is broken on my laptop. The system refuses to wake up in about 50% of the cases, seemingly random. The only "solution" is a forced system power down. Reverting back to 5.15.0.60 resolves this issue immediately. I suspect some patch was not re-applied to 5.19, since there are many postings on Reddit (for instance) about sleep problems with newer AMD CPUs, but 5.15 was running beautifully. My machine is a Lenovo Thinkpad T14s AMD Gen 3, AMD 6850u CPU. UPDATE: See attached log. This may not be a case of the laptop failing to resume, but a case of the laptop not suspending properly! What happened was the following. When packing in my things, I closed the laptop and put it in my bag. At home I picked it up again, and immediately noticed how unusually hot it was. The laptop didn't resume properly on opening the lid, but was frozen as before. So this might actually be a case of the laptop FAILING TO SUSPEND properly, instead of failing to wake up. UPDATE: I just noticed the battery was down to the low 40% from at least 80%. Given the temperature on opening the laption I suspect the CPU has been working hard during "sleep time". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-5.19/+bug/2007718/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007718] Re: HWE-22.04 Kernel 5.19 breaks suspend/wake on newer AMD Ryzen 6000u
** Description changed: After 22.04 LTS upgraded the linux-generic-hwe kernel to 5.19.0.32 (from 5.15.0.60) suspend/wake up is broken on my laptop. The system refuses to wake up in about 50% of the cases, seemingly random. The only "solution" is a forced system power down. Reverting back to 5.15.0.60 resolves this issue immediately. I suspect some patch was not re-applied to 5.19, since there are many postings on Reddit (for instance) about sleep problems with newer AMD CPUs, but 5.15 was running beautifully. My machine is a Lenovo Thinkpad T14s AMD Gen 3, AMD 6850u CPU. + + UPDATE: + + See attached log. This may not be a case of the laptop failing to + resume, but a case of the laptop not suspending properly! + + What happened was the following. When packing in my things, I closed + the laptop and put it in my bag. At home I picked it up again, and + immediately noticed how unusually hot it was. The laptop didn't resume + properly on opening the lid, but was frozen as before. + + So this might actually be a case of the laptop FAILING TO SUSPEND + properly, instead of failing to wake up. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2007718 Title: HWE-22.04 Kernel 5.19 breaks suspend/wake on newer AMD Ryzen 6000u Status in linux-meta-hwe-5.19 package in Ubuntu: New Bug description: After 22.04 LTS upgraded the linux-generic-hwe kernel to 5.19.0.32 (from 5.15.0.60) suspend/wake up is broken on my laptop. The system refuses to wake up in about 50% of the cases, seemingly random. The only "solution" is a forced system power down. Reverting back to 5.15.0.60 resolves this issue immediately. I suspect some patch was not re-applied to 5.19, since there are many postings on Reddit (for instance) about sleep problems with newer AMD CPUs, but 5.15 was running beautifully. My machine is a Lenovo Thinkpad T14s AMD Gen 3, AMD 6850u CPU. UPDATE: See attached log. This may not be a case of the laptop failing to resume, but a case of the laptop not suspending properly! What happened was the following. When packing in my things, I closed the laptop and put it in my bag. At home I picked it up again, and immediately noticed how unusually hot it was. The laptop didn't resume properly on opening the lid, but was frozen as before. So this might actually be a case of the laptop FAILING TO SUSPEND properly, instead of failing to wake up. UPDATE: I just noticed the battery was down to the low 40% from at least 80%. Given the temperature on opening the laption I suspect the CPU has been working hard during "sleep time". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-5.19/+bug/2007718/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008136] Re: netfilter: flowtable: add counter support in HW offload
** Also affects: linux-bluefield (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-bluefield (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux-bluefield (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-bluefield (Ubuntu Focal) Assignee: (unassigned) => William Tu (wtu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2008136 Title: netfilter: flowtable: add counter support in HW offload Status in linux-bluefield package in Ubuntu: New Status in linux-bluefield source package in Focal: In Progress Bug description: * Explain the bug(s) While conntrack tuples are offloaded to hardware and conntrack packet accounting is enabled, offloaded packets aren't counted. * Brief explanation of fixes Cherry-pick. No adaptation. First commit for SW, second commit of HW offloaded rules. ef803b3cf96a netfilter: flowtable: add counter support in HW offload 9312eabab4a6 netfilter: conntrack: add nf_ct_acct_add() note: need to change a little due to cherry-pick conflict with 24384e28586c netfilter: flowtable: Set offload timeouts according to proto values * How to test Create OVS bridge with 2 devices mlx5 rep devices. Enable HW offload and configure regular connection tracking OpenFlow rules: e.g: ovs-ofctl del-flows br-ovs ovs-ofctl add-flow br-ovs arp,actions=normal ovs-ofctl add-flow br-ovs "table=0, ip,ct_state=-trk actions=ct(table=1)" ovs-ofctl add-flow br-ovs "table=1, ip,ct_state=+trk+new actions=ct(commit),normal" ovs-ofctl add-flow br-ovs "table=1, ip,ct_state=+trk+est, actions=normal" Run a TCP connection, e.g: on mlx5 VF1 iperf -s on mlx5 VF2 iperf -c -t 10 Optional: In different terminal, while traffic is running, check for offload: tcpdump -nnepi tcp and see no iperf tcp packets. Dump conntrack with relevant ip: cat /proc/net/nf_conntrack | grep -i See counters (packets=.*) advancing while tuples were offloaded: ipv4 2 tcp 6 src=1.1.1.2 dst=1.1.1.3 sport=56394 dport=5001 packets=2 bytes=112 src=1.1.1.3 dst=1.1.1.2 sport=5001 dport=56394 packets=1777 bytes=665340 [HW_OFFLOAD] mark=0 zone=0 use=3 * What it could break. Nothing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2008136/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1991676] Re: Package grub-efi-arm64-signed 1.173.2~18.04.1+2.04-1ubuntu47.4 from bionic-proposed fails to install/upgrade (grub-install: error: efibootmgr: not found.)
This issue has been worked around in the autopkgtest environment with the following change: https://code.launchpad.net/~ubuntu- release/autopkgtest/+git/development/+merge/437822 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1991676 Title: Package grub-efi-arm64-signed 1.173.2~18.04.1+2.04-1ubuntu47.4 from bionic-proposed fails to install/upgrade (grub-install: error: efibootmgr: not found.) Status in ubuntu-kernel-tests: New Status in grub2-signed package in Ubuntu: Invalid Status in linux-hwe-5.4 package in Ubuntu: Confirmed Status in grub2-signed source package in Bionic: Triaged Status in linux-hwe-5.4 source package in Bionic: Confirmed Bug description: The ADT tests for arm64 kernels in Bionic are failing during the setup phase with the following errors: Setting up grub-efi-arm64-signed (1.173.2~18.04.1+2.04-1ubuntu47.4) ... Installing for arm64-efi platform. grub-install: error: efibootmgr: not found. dpkg: error processing package grub-efi-arm64-signed (--configure): installed grub-efi-arm64-signed package post-installation script subprocess returned error exit status 1 Setting up libx11-6:arm64 (2:1.6.4-3ubuntu0.5) ... Processing triggers for man-db (2.8.3-2ubuntu0.1) ... Processing triggers for libc-bin (2.27-3ubuntu1.6) ... Errors were encountered while processing: grub-efi-arm64-signed E: Sub-process /usr/bin/dpkg returned an error code (1) blame: badpkg: testbed setup commands failed with status 100 autopkgtest [15:12:03]: ERROR: erroneous package: testbed setup commands failed with status 100 ADT test log: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/arm64/l/linux-hwe-5.4/20220930_151219_13ac3@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1991676/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007718] Re: HWE-22.04 Kernel 5.19 breaks suspend/wake on newer AMD Ryzen 6000u
kern.log attached, suspend on line 59124 ** Attachment added: "kern.log" https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-5.19/+bug/2007718/+attachment/5649624/+files/kern.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2007718 Title: HWE-22.04 Kernel 5.19 breaks suspend/wake on newer AMD Ryzen 6000u Status in linux-meta-hwe-5.19 package in Ubuntu: New Bug description: After 22.04 LTS upgraded the linux-generic-hwe kernel to 5.19.0.32 (from 5.15.0.60) suspend/wake up is broken on my laptop. The system refuses to wake up in about 50% of the cases, seemingly random. The only "solution" is a forced system power down. Reverting back to 5.15.0.60 resolves this issue immediately. I suspect some patch was not re-applied to 5.19, since there are many postings on Reddit (for instance) about sleep problems with newer AMD CPUs, but 5.15 was running beautifully. My machine is a Lenovo Thinkpad T14s AMD Gen 3, AMD 6850u CPU. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-5.19/+bug/2007718/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2006994] Re: Ubuntu 22.10 and Dell Latitude 7390 – screen does not turn back on after waking up from sleep
I have exactly the same problem on my Dell Latitude 7390. I also try it with Debian Bullseye and I reproduce this problem. No problem on the original Microsoft Windows installation. -- 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/2006994 Title: Ubuntu 22.10 and Dell Latitude 7390 – screen does not turn back on after waking up from sleep Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 22.10 and Dell Latitude 7390 – screen does not turn back on after waking up from sleep Scenario: Fresh and clean Ubuntu 22.10 install on Latitude 7390, requiring nomodeset kernel boot option to be added in GRUB at boot time when booting from USB stick. This can be achieved by following instructions from here: https://www.dell.com/support/kbdoc/en-uk/000123893/manual- nomodeset-kernel-boot-line-option-for-linux-booting Then, nomodeset needs to be permanently added to /etc/default/grub Followed instructions from https://askubuntu.com/questions/38780/how-do-i-set-nomodeset-after-ive-already-installed-ubuntu If nomodeset is not added, Dell Latitude 7390 will freeze at one point or another, either before reaching the Gnome desktop, either little after. This is the case with both, installing Ubuntu 22.10 from Live USB and running Ubuntu 22.10 after install the install (and having the USB stick disconnected). The issue after having Ubuntu 22.10 installed on Dell Latitude 7390 and having nomodeset permanently added to GRUB for each boot is: If by chance the system goes into sleep, after waking up, there is a totally pitch-black screen; nothing shows up, no screen backlight either. However, caps-lock works and I am able to log in to the system via ssh and can see the system is up an running well. I can even issue a request to send the system to sleep by “sudo systemctl suspend” and then wake the the system up several times without loosing ssh access, however, the screen will remain pitch-black. Other tries to troubleshoot and see if the system can be brought back with a working display (while nomodeset kernel option is being used): 1. sudo systemctl suspend -i >>> this will result in an unusable system after waking up, again, with a pitch-black screen; moreover, the caps-lock would not work, the keyboard backlight won’t work, ssh won’t work; I need a hard reset to get the system back up. 2. start the system in single user mode by inserting “single” in GRUB at boot time; >>> the system will be unusable after waking up, same as in try 1. 3. after a normal boot into the GNOME desktop with kernel nomodeset option and investigating the dmesg for any acpi, no error could be found. Tried to read up on other possible solutions, while stumbled upon the ubuntu wiki page below: https://wiki.ubuntu.com/UnderstandingSuspend Unfortunately, to not much help so far. Other notes: N1. All the above were done by having the latest BIOS v1.30.0 N2. This laptop came with Windows 10 Pro which works fine: goes into suspend and wakes up fine, with working screen and display. N3. Dell Latitude 7390 was released on 15 Feb 2018 ( source: https://www.laptoparena.net/dell/notebook-dell-latitude-7390-n025l739013emea-black-12984 ) and the user manual states it has support for Ubuntu. Therefore, other older and major Ubuntu versions were given a try, along with a new version of Fedora: N3.1 – Ubuntu 22.04 N3.2 – Ubuntu 18.04.6 N3.3 – Ubuntu 16.04.7 N3.4 – Fedora-Workstation-Live-x86_64-37-1.7 Each of the above will freeze at one point or another if nomodeset is not used, except the Ubuntu 18.04.6 and Ubuntu 16.04.7 which will run well and install well from the USB Live stick and will also run fine after the install, until the system goes into sleep, after which, when the system is awake, the screen is black and will have nothing displayed. Any advice will be appreciated. Thank you! ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-31-generic 5.19.0-31.32 ProcVersionSignature: Ubuntu 5.19.0-31.32-generic 5.19.17 Uname: Linux 5.19.0-31-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tuser 2832 F wireplumber /dev/snd/seq:tuser 2829 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Feb 11 13:37:59 2023 InstallationDate: Installed on 2023-01-15 (27 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 0bda:5650 Realtek Semiconductor Corp. Integrated Webcam_HD Bus 001 Device 004: ID 0a5c:5832
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-restricted-modules/5.15.0-67.74)
All autopkgtests for the newly accepted linux-restricted-modules (5.15.0-67.74) for jammy have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.1 (i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#linux-restricted-modules [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1988836] Autopkgtest regression report (linux-restricted-modules/5.15.0-67.74)
All autopkgtests for the newly accepted linux-restricted-modules (5.15.0-67.74) for jammy have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.1 (i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#linux-restricted-modules [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1988836 Title: LRMv7: Enable the open NVIDIA kernel modules Status in linux-restricted-modules package in Ubuntu: In Progress Status in nvidia-graphics-drivers-515 package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in linux-restricted-modules source package in Focal: In Progress Status in nvidia-graphics-drivers-515 source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Focal: Fix Committed Status in linux-restricted-modules source package in Jammy: In Progress Status in nvidia-graphics-drivers-515 source package in Jammy: Fix Released Status in ubuntu-drivers-common source package in Jammy: Fix Committed Bug description: [ Impact ] * The 515 series introduced open kernel modules for the NVIDIA driver. They come with an open source licence, and should be provided as an option for datacenter GPUs: https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/ Currently, this is only production-ready (and enabled) on datacenter GPUs. * We should enable signed modules for the 515-open drivers, giving users the option to try the drivers. * The ubuntu-drivers tool should set a lower priority for the -open flavour, so that we do not end up recommending it over the plain 515 flavour. [ Test Plan ] * [ubuntu-drivers-common]: "sudo ubuntu-drivers install (to make sure the driver is not installed by default)" * [nvidia driver] "sudo ubuntu-drivers install nvidia:515-open" to make sure that the driver can be installed manually. Please make sure that this installs the correct linux-restricted- modules. Note: support for GeForce and Workstation GPUs is alpha-quality, and is disabled by default. This means that desktop testing is not needed at the moment. [ Where problems could occur ] * This adds a new driver combination, which is not meant to be default, and is only enabled for a limited amount of devices (datacenter GPUs). * We need to be sure that the driver is not recommended over the other drivers. [ Other Info ] - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008157] Re: [SRU][Ubuntu 22.04.1]: Observed "Array Index out of bounds" Call Trace multiple times on Ubuntu 22.04.1 OS during boot
** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2008157 Title: [SRU][Ubuntu 22.04.1]: Observed "Array Index out of bounds" Call Trace multiple times on Ubuntu 22.04.1 OS during boot Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: In Progress Bug description: SRU Justification: [Impact] When booted into Ubuntu 22.04.1 OS after installation, observed "Array Index out of bounds" Call Trace multiple times in dmesg. Call Trace is as follow: [ 6.125704] UBSAN: array-index-out-of-bounds in /build/linux-JjvoxS/linux-5.15.0/drivers/scsi/megaraid/megaraid_sas_fp.c:103:32 [ 6.125705] index 1 is out of range for type 'MR_LD_SPAN_MAP [1]' [ 6.125707] CPU: 0 PID: 18 Comm: kworker/0:1 Not tainted 5.15.0-53-generic #59-Ubuntu [ 6.125709] Hardware name: Dell Inc. , BIOS 11/08/2022 [ 6.125710] Workqueue: events work_for_cpu_fn [ 6.125716] Call Trace: [ 6.125718] [ 6.125720] show_stack+0x52/0x5c [ 6.125725] dump_stack_lvl+0x4a/0x63 [ 6.125731] dump_stack+0x10/0x16 [ 6.125732] ubsan_epilogue+0x9/0x49 [ 6.125734] __ubsan_handle_out_of_bounds.cold+0x44/0x49 [ 6.125736] ? MR_PopulateDrvRaidMap+0x194/0x580 [megaraid_sas] [ 6.125747] mr_update_load_balance_params+0xb9/0xc0 [megaraid_sas] [ 6.125753] MR_ValidateMapInfo+0x8d/0x290 [megaraid_sas] [ 6.125757] megasas_init_adapter_fusion+0x3ce/0x420 [megaraid_sas] [ 6.125762] ? megasas_setup_reply_map+0x49/0xac [megaraid_sas] [ 6.125768] megasas_init_fw.cold+0x87c/0x10c8 [megaraid_sas] [ 6.125774] megasas_probe_one+0x15c/0x4e0 [megaraid_sas] [ 6.125779] local_pci_probe+0x48/0x90 [ 6.125783] work_for_cpu_fn+0x17/0x30 [ 6.125785] process_one_work+0x228/0x3d0 [ 6.125786] worker_thread+0x223/0x420 [ 6.125787] ? process_one_work+0x3d0/0x3d0 [ 6.125788] kthread+0x127/0x150 [ 6.125790] ? set_kthread_struct+0x50/0x50 [ 6.125791] ret_from_fork+0x1f/0x30 [ 6.125796] [ 6.125796] Steps to reproduce: 1. Connect PERC H355 controller to the system 2. Create RAID1 using drives connected to PERC Controller 3. Install Ubuntu 22.04.1 on VD 4. Boot into OS after installation 5. Multiple Call Traces of "array-index-out-of-bounds" are seen Expected Behavior: OS should boot without this Call Trace [Fix] [PATCH v3 0/6] Replace one-element arrays with flexible-array members https://lore.kernel.org/linux-hardening/cover.1660592640.git.gustavo...@kernel.org/ 48658213 scsi: megaraid_sas: Use struct_size() in code related to struct MR_PD_CFG_SEQ_NUM_SYNC 41e83026 scsi: megaraid_sas: Use struct_size() in code related to struct MR_FW_RAID_MAP ee92366a scsi: megaraid_sas: Replace one-element array with flexible- array member in MR_PD_CFG_SEQ_NUM_SYNC eeb3bab7 scsi: megaraid_sas: Replace one-element array with flexible- array member in MR_DRV_RAID_MAP 204a29a1 scsi: megaraid_sas: Replace one-element array with flexible- array member in MR_FW_RAID_MAP_DYNAMIC ac23b92b scsi: megaraid_sas: Replace one-element array with flexible- array member in MR_FW_RAID_MAP [Test Plan] 1. Connect PERC H355 controller to the system 2. Create RAID1 using drives connected to PERC Controller 3. Install Ubuntu 22.04.1 on VD 4. Boot into OS after installation OS should boot without the Call Trace listed in the Impact field [Where problems could occur] [Other Info] https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/array_bounds_lp_2008157 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008157/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2004235] Re: mlxbf-pmc counters not functional for llt_miss block
This bug is awaiting verification that the linux- bluefield/5.15.0-1013.15 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-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2004235 Title: mlxbf-pmc counters not functional for llt_miss block Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Focal: Fix Committed Status in linux-bluefield source package in Jammy: Fix Committed Bug description: SRU Justification: [Impact] Currently, the driver uses fixed offsets for the control and data registers in the performance counter module. However, this is not correct since the module is not uniform in all HW blocks, and in this case, the llt_miss block is different from the rest. [Fix] The number of counters present in each block is not fixed, and hence the offsets for the control and data registers should also be calculated accordingly. [Test Case] Without the fix, writing 1 to the llt_miss "enable" file will not result in any of the counters incrementing. With the fix, the counters should increment even with the default event settings. [Regression Potential] Can be considered minimal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2004235/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2004645] Re: mmc: sdhci-of-dwcmshc: add the missing device table IDs for acpi
This bug is awaiting verification that the linux- bluefield/5.15.0-1013.15 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-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2004645 Title: mmc: sdhci-of-dwcmshc: add the missing device table IDs for acpi Status in linux-bluefield package in Ubuntu: New Status in linux-bluefield source package in Jammy: Fix Committed Bug description: SRU Justification: [Impact] This change is needed so the sdhci-of-dwcmshc driver can be loaded automatically when built ad kernel module. [Fix] add the missing device table IDs for acpi [Test Case] Build sdhci-of-dwcmshc as kernel module, use modinfo command to make sure the output contains 'acpi*:MLNXBF30:*'. [Regression Potential] No changes to driver funtionality. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2004645/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008084] Re: Linux image 5.19 cuts off the build date
Yes the version there in /proc/version is from uname -v. The version field in utsname is 64 characters fixed width. This leads to truncation with the longer version on the backport and the very long flags. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2008084 Title: Linux image 5.19 cuts off the build date Status in linux package in Ubuntu: Confirmed Bug description: Hi, The output of uname -a is failing to show the full build date on Jammy 22.04.2 with kernel 5.19 as the string is too long. I believe there is some size limit that is being overrun when building the kernel. lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 22.04.2 LTS Release: 22.04 Codename: jammy uname -v #33~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Mon Jan 30 17:03:34 UTC 2 uname -a Linux kianp 5.19.0-32-generic #33~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Mon Jan 30 17:03:34 UTC 2 x86_64 x86_64 x86_64 GNU/Linux cat /proc/version Linux version 5.19.0-32-generic (buildd@lcy02-amd64-026) (x86_64-linux-gnu-gcc (Ubuntu 11.3.0-1ubuntu1~22.04) 11.3.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #33~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Mon Jan 30 17:03:34 UTC 2 cat /proc/version_signature Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 See above, the build date is missing the year (2023). On an older kernel the output of uname -v is much shorter which leads me to believe some buffer size limit is being hit. (Older Kernel): uname -v #66-Ubuntu SMP Fri Jan 20 14:29:49 UTC 2023 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008084/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008136] Re: Add HW offloaded CT stats
** Description changed:
* Explain the bug(s)
When CT HW offload is enabled, the CT stats does not show the stats of the
offloaded flow.
Ex: using
cat /proc/net/nf_conntrack, or conntrack -L
shows only the software CT stats, not the offloaded CT stats
* Brief explanation of fixes
Cherry-pick. No adaptation. First commit for SW, second commit of HW
offloaded rules.
ef803b3cf96a netfilter: flowtable: add counter support in HW offload
9312eabab4a6 netfilter: conntrack: add nf_ct_acct_add()
note: need to change a little due to cherry-pick conflict with
24384e28586c netfilter: flowtable: Set offload timeouts according to proto
values
* How to test
+ Create OVS bridge with 2 devices mlx5 rep devices.
+ Enable HW offload and configure regular connection tracking OpenFlow rules:
- Enable nf_conn_acct, enable HW offload using OVS or tc-flower, and check ct
stats.
- ex:
- ovs-vsctl get Open_vSwitch . other_config
- {hw-offload="true"}
- ovs-appctl dpctl/dump-flows type=offloaded
- ovs-appctl dpctl/dump-conntrack
+ e.g:
+ ovs-ofctl del-flows br-ovs
+ ovs-ofctl add-flow br-ovs arp,actions=normal
+ ovs-ofctl add-flow br-ovs "table=0, ip,ct_state=-trk actions=ct(table=1)"
+ ovs-ofctl add-flow br-ovs "table=1, ip,ct_state=+trk+new
actions=ct(commit),normal"
+ ovs-ofctl add-flow br-ovs "table=1, ip,ct_state=+trk+est, actions=normal"
+
+ Run a TCP connection, e.g:
+ on mlx5 VF1 iperf -s
+ on mlx5 VF2 iperf -c -t 10
+
+ Optional: In different terminal, while traffic is running, check for offload:
+ tcpdump -nnepi tcp
+
+ and see no iperf tcp packets.
+ Dump conntrack with relevant ip:
+ cat /proc/net/nf_conntrack | grep -i
+
+ See counters (packets=.*) advancing while tuples were offloaded:
+ ipv4 2 tcp 6 src=1.1.1.2 dst=1.1.1.3 sport=56394 dport=5001
packets=2 bytes=112 src=1.1.1.3 dst=1.1.1.2 sport=5001 dport=56394 packets=1777
bytes=665340 [HW_OFFLOAD] mark=0 zone=0 use=3
+
+
* What it could break.
Nothing.
** Summary changed:
- Add HW offloaded CT stats
+ netfilter: flowtable: add counter support in HW offload
** Description changed:
* Explain the bug(s)
- When CT HW offload is enabled, the CT stats does not show the stats of the
offloaded flow.
- Ex: using
- cat /proc/net/nf_conntrack, or conntrack -L
- shows only the software CT stats, not the offloaded CT stats
+ While conntrack tuples are offloaded to hardware and conntrack packet
+ accounting is enabled, offloaded packets aren't counted.
* Brief explanation of fixes
Cherry-pick. No adaptation. First commit for SW, second commit of HW
offloaded rules.
ef803b3cf96a netfilter: flowtable: add counter support in HW offload
9312eabab4a6 netfilter: conntrack: add nf_ct_acct_add()
note: need to change a little due to cherry-pick conflict with
24384e28586c netfilter: flowtable: Set offload timeouts according to proto
values
* How to test
Create OVS bridge with 2 devices mlx5 rep devices.
Enable HW offload and configure regular connection tracking OpenFlow rules:
e.g:
- ovs-ofctl del-flows br-ovs
- ovs-ofctl add-flow br-ovs arp,actions=normal
- ovs-ofctl add-flow br-ovs "table=0, ip,ct_state=-trk actions=ct(table=1)"
- ovs-ofctl add-flow br-ovs "table=1, ip,ct_state=+trk+new
actions=ct(commit),normal"
- ovs-ofctl add-flow br-ovs "table=1, ip,ct_state=+trk+est, actions=normal"
-
+ ovs-ofctl del-flows br-ovs
+ ovs-ofctl add-flow br-ovs arp,actions=normal
+ ovs-ofctl add-flow br-ovs "table=0, ip,ct_state=-trk actions=ct(table=1)"
+ ovs-ofctl add-flow br-ovs "table=1, ip,ct_state=+trk+new
actions=ct(commit),normal"
+ ovs-ofctl add-flow br-ovs "table=1, ip,ct_state=+trk+est, actions=normal"
Run a TCP connection, e.g:
on mlx5 VF1 iperf -s
- on mlx5 VF2 iperf -c -t 10
+ on mlx5 VF2 iperf -c -t 10
Optional: In different terminal, while traffic is running, check for offload:
tcpdump -nnepi tcp
and see no iperf tcp packets.
Dump conntrack with relevant ip:
cat /proc/net/nf_conntrack | grep -i
See counters (packets=.*) advancing while tuples were offloaded:
ipv4 2 tcp 6 src=1.1.1.2 dst=1.1.1.3 sport=56394 dport=5001
packets=2 bytes=112 src=1.1.1.3 dst=1.1.1.2 sport=5001 dport=56394 packets=1777
bytes=665340 [HW_OFFLOAD] mark=0 zone=0 use=3
-
* What it could break.
Nothing.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-bluefield in Ubuntu.
https://bugs.launchpad.net/bugs/2008136
Title:
netfilter: flowtable: add counter support in HW offload
Status in linux-bluefield package in Ubuntu:
New
Bug description:
* Explain the bug(s)
While conntrack tuples are offloaded to hardware and conntrack packet
accounting is enabled, offloaded packets aren't counted.
* Brief explanation of fixes
Cherry-pick. No adaptation. First commit for SW, second commit of HW
offloaded
[Kernel-packages] [Bug 2008157] [NEW] [SRU][Ubuntu 22.04.1]: Observed "Array Index out of bounds" Call Trace multiple times on Ubuntu 22.04.1 OS during boot
You have been subscribed to a public bug: SRU Justification: [Impact] When booted into Ubuntu 22.04.1 OS after installation, observed "Array Index out of bounds" Call Trace multiple times in dmesg. Call Trace is as follow: [ 6.125704] UBSAN: array-index-out-of-bounds in /build/linux-JjvoxS/linux-5.15.0/drivers/scsi/megaraid/megaraid_sas_fp.c:103:32 [ 6.125705] index 1 is out of range for type 'MR_LD_SPAN_MAP [1]' [ 6.125707] CPU: 0 PID: 18 Comm: kworker/0:1 Not tainted 5.15.0-53-generic #59-Ubuntu [ 6.125709] Hardware name: Dell Inc. , BIOS 11/08/2022 [ 6.125710] Workqueue: events work_for_cpu_fn [ 6.125716] Call Trace: [ 6.125718] [ 6.125720] show_stack+0x52/0x5c [ 6.125725] dump_stack_lvl+0x4a/0x63 [ 6.125731] dump_stack+0x10/0x16 [ 6.125732] ubsan_epilogue+0x9/0x49 [ 6.125734] __ubsan_handle_out_of_bounds.cold+0x44/0x49 [ 6.125736] ? MR_PopulateDrvRaidMap+0x194/0x580 [megaraid_sas] [ 6.125747] mr_update_load_balance_params+0xb9/0xc0 [megaraid_sas] [ 6.125753] MR_ValidateMapInfo+0x8d/0x290 [megaraid_sas] [ 6.125757] megasas_init_adapter_fusion+0x3ce/0x420 [megaraid_sas] [ 6.125762] ? megasas_setup_reply_map+0x49/0xac [megaraid_sas] [ 6.125768] megasas_init_fw.cold+0x87c/0x10c8 [megaraid_sas] [ 6.125774] megasas_probe_one+0x15c/0x4e0 [megaraid_sas] [ 6.125779] local_pci_probe+0x48/0x90 [ 6.125783] work_for_cpu_fn+0x17/0x30 [ 6.125785] process_one_work+0x228/0x3d0 [ 6.125786] worker_thread+0x223/0x420 [ 6.125787] ? process_one_work+0x3d0/0x3d0 [ 6.125788] kthread+0x127/0x150 [ 6.125790] ? set_kthread_struct+0x50/0x50 [ 6.125791] ret_from_fork+0x1f/0x30 [ 6.125796] [ 6.125796] Steps to reproduce: 1. Connect PERC H355 controller to the system 2. Create RAID1 using drives connected to PERC Controller 3. Install Ubuntu 22.04.1 on VD 4. Boot into OS after installation 5. Multiple Call Traces of "array-index-out-of-bounds" are seen Expected Behavior: OS should boot without this Call Trace [Fix] [PATCH v3 0/6] Replace one-element arrays with flexible-array members https://lore.kernel.org/linux-hardening/cover.1660592640.git.gustavo...@kernel.org/ 48658213 scsi: megaraid_sas: Use struct_size() in code related to struct MR_PD_CFG_SEQ_NUM_SYNC 41e83026 scsi: megaraid_sas: Use struct_size() in code related to struct MR_FW_RAID_MAP ee92366a scsi: megaraid_sas: Replace one-element array with flexible- array member in MR_PD_CFG_SEQ_NUM_SYNC eeb3bab7 scsi: megaraid_sas: Replace one-element array with flexible- array member in MR_DRV_RAID_MAP 204a29a1 scsi: megaraid_sas: Replace one-element array with flexible- array member in MR_FW_RAID_MAP_DYNAMIC ac23b92b scsi: megaraid_sas: Replace one-element array with flexible- array member in MR_FW_RAID_MAP [Test Plan] 1. Connect PERC H355 controller to the system 2. Create RAID1 using drives connected to PERC Controller 3. Install Ubuntu 22.04.1 on VD 4. Boot into OS after installation OS should boot without the Call Trace listed in the Impact field [Where problems could occur] [Other Info] https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/array_bounds_lp_2008157 ** Affects: linux (Ubuntu) Importance: Medium Assignee: Michael Reed (mreed8855) Status: In Progress ** Affects: linux (Ubuntu Jammy) Importance: Medium Assignee: Michael Reed (mreed8855) Status: In Progress ** Tags: bot-comment -- [SRU][Ubuntu 22.04.1]: Observed "Array Index out of bounds" Call Trace multiple times on Ubuntu 22.04.1 OS during boot https://bugs.launchpad.net/bugs/2008157 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008269] Re: dkms prevents installing vendored-in dkms packages
** Tags added: lunar regression-release ** Changed in: dkms (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/2008269 Title: dkms prevents installing vendored-in dkms packages Status in dkms package in Ubuntu: Fix Committed Bug description: [ Impact ] * In kinetic, installing kernel which vendors a dkms module from the archive allows to still install the same dkms module from the archive, in an inactive package: $ sudo apt install linux-virtual zfs-dkms ... zstd.ko: Running module version sanity check. Error! Module version 1.4.5a-2.1.5-1ubuntu6 for zzstd.ko is not newer than what is already found in kernel 5.19.0-35-generic (1.4.5a-2.1.5-1ubuntu6). You may override by specifying --force. depmod... Processing triggers for libc-bin (2.36-0ubuntu2) ... $ echo $? 0 $ sudo dkms status zfs/2.1.5, 5.19.0-35-generic, x86_64: installed (WARNING! Diff between built and installed module!) If the user wishes to use dkms built module for whatever reason, one can then call dkms install --force after apt completes. Whereas in lunar, such apt installation fails, resulting in broken apt packages, and inability to specify `dkms install --force` zzstd.ko: Running module version sanity check. Module version 1.4.5a-2.1.7-1ubuntu1 for zzstd.ko exactly matches what is already found in kernel 6.1.0-14-generic. DKMS will not replace this module. You may override by specifying --force. Error! Installation aborted. dpkg: error processing package zfs-dkms (--configure): installed zfs-dkms package post-installation script subprocess returned error exit status 6 Processing triggers for libc-bin (2.36-0ubuntu4) ... Errors were encountered while processing: zfs-dkms E: Sub-process /usr/local/libexec/mk-sbuild/dpkg returned an error code (1) This breaks existing Ubuntu workflows that allow keeping dkms module installed, and get it upgraded on older kernel abis, if and when desired. [ Test Plan ] * Install zfs-dkms and linux-virtual that vendors the identical version zfs-dkms [ Where problems could occur ] * This looks like upstream regression [ Other Info ] * this is making kernels unmigratable in lunar. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/2008269/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2004644] Re: Incompatible jbd2 format between kernel and lttng-modules
version 2.10.8-1ubuntu2~18.04.5 tested on bionic 5.4.0-144.161~18.04.1 works fine https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/amd64/l/lttng-modules/20230223_150053_15e8f@/log.gz -- 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/2004644 Title: Incompatible jbd2 format between kernel and lttng-modules Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Incomplete Status in lttng-modules package in Ubuntu: Fix Committed Status in lttng-modules source package in Bionic: In Progress Status in linux source package in Focal: Incomplete Status in lttng-modules source package in Focal: Fix Committed Status in linux source package in Jammy: Incomplete Status in lttng-modules source package in Jammy: Fix Committed Status in linux source package in Kinetic: Incomplete Status in lttng-modules source package in Kinetic: Fix Committed Status in linux source package in Lunar: Incomplete Status in lttng-modules source package in Lunar: Fix Committed Bug description: [SRU Justification] Impact: Upstream stable added a change in the format of jbd2 in 5.4.229, 5.15.87, 6.1.3. This is incompatible with the current changes in the lttng-module for bionic-5.4 backports, focal, jammy, and kinetic. Focal and bionic updates are needed for the current sru kernel release (2023.01.30). Both adt and rt fail during compilation of the module. Jammy and kinetic updates are not needed for this cycle because patches from upstream stable are not applied yet but it will be needed for the next release(s). Correct changes are already in lttng-modules:master and in 2.13.8-1 version. Fix(es): 1. focal and bionic: Picking 4 patches from upstream lttng-modules which handle the changed interface as well as add the required code to enable that change for other versions as well: LTTNG_KERNEL_RANGE(5,4,229, 5,5,0) LTTNG_KERNEL_RANGE(5,10,163, 5,11,0) LTTNG_KERNEL_RANGE(5,15,87, 5,16,0) LTTNG_KERNEL_RANGE(6,0,18, 6,1,0) LTTNG_KERNEL_RANGE(6,1,4, 6,2,0) 2. Jammy and kinetic: backport 2.13.8-1 Tescase(s) for focal: 1. lttng-smoke-test fail to compile with the error from below. 2. adt lttng-module fail to compile with same error Regression potential: We may notice new failures in ubuntu_lttng_smoke_test once this will compile and run. But it was tested locally and results were good, so probablity is very very low. 760 21:14:39 DEBUG| [stdout] In file included from /var/lib/dkms/lttng-modules/2.12.5/build/probes/../probes/define_trace.h:87, 761 21:14:39 DEBUG| [stdout] from /var/lib/dkms/lttng-modules/2.12.5/build/probes/../instrumentation/events/lttng-module/jbd2.h:177, 762 21:14:39 DEBUG| [stdout] from /var/lib/dkms/lttng-modules/2.12.5/build/probes/lttng-probe-jbd2.c:29: 763 21:14:39 DEBUG| [stdout] /var/lib/dkms/lttng-modules/2.12.5/build/probes/../probes/lttng-tracepoint-event-impl.h:131:6: error: conflicting types for ‘trace_jbd2_run_stats’ 764 21:14:39 DEBUG| [stdout] 131 | void trace_##_name(_proto); 765 21:14:39 DEBUG| [stdout] | ^~ 766 21:14:39 DEBUG| [stdout] /var/lib/dkms/lttng-modules/2.12.5/build/probes/../probes/lttng-tracepoint-event-impl.h:43:2: note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP’ 767 21:14:39 DEBUG| [stdout] 43 | LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP(map, name, map, PARAMS(proto), PARAMS(args)) 768 21:14:39 DEBUG| [stdout] | ^~~ 769 21:14:39 DEBUG| [stdout] /var/lib/dkms/lttng-modules/2.12.5/build/probes/../probes/lttng-tracepoint-event-impl.h:85:2: note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_MAP’ 770 21:14:39 DEBUG| [stdout] 85 | LTTNG_TRACEPOINT_EVENT_MAP(name, name, \ 771 21:14:39 DEBUG| [stdout] | ^~ 772 21:14:39 DEBUG| [stdout] /var/lib/dkms/lttng-modules/2.12.5/build/probes/../instrumentation/events/lttng-module/jbd2.h:104:1: note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT’ 773 21:14:39 DEBUG| [stdout] 104 | LTTNG_TRACEPOINT_EVENT(jbd2_run_stats, 774 21:14:39 DEBUG| [stdout] | ^~ 775 21:14:39 DEBUG| [stdout] In file included from ./include/trace/events/jbd2.h:9, 776 21:14:39 DEBUG| [stdout] from /var/lib/dkms/lttng-modules/2.12.5/build/probes/lttng-probe-jbd2.c:18: 777 21:14:39 DEBUG| [stdout] ./include/linux/tracepoint.h:243:21: note: previous definition of ‘trace_jbd2_run_stats’ was here 778 21:14:39 DEBUG| [stdout] 243 | static inline void trace_##name(proto) \ 779 21:14:39 DEBUG| [stdout] | ^~ 780 21:14:39 DEBUG| [stdout] ./include/linux/tracepoint.h:406:2: note: in expansion of macro ‘__DECLARE_TRACE’ 781 21:14:39 DEBUG| [stdout] 406 | __DECLARE_TRACE(name, PARAMS(proto),
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-restricted-modules-hwe-5.15/5.15.0-66.73~20.04.1)
All autopkgtests for the newly accepted linux-restricted-modules-hwe-5.15 (5.15.0-66.73~20.04.1) for focal have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-390/390.157-0ubuntu0.20.04.1 (i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-restricted-modules-hwe-5.15 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1988836] Autopkgtest regression report (linux-restricted-modules-hwe-5.15/5.15.0-66.73~20.04.1)
All autopkgtests for the newly accepted linux-restricted-modules-hwe-5.15 (5.15.0-66.73~20.04.1) for focal have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-390/390.157-0ubuntu0.20.04.1 (i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-restricted-modules-hwe-5.15 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1988836 Title: LRMv7: Enable the open NVIDIA kernel modules Status in linux-restricted-modules package in Ubuntu: In Progress Status in nvidia-graphics-drivers-515 package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in linux-restricted-modules source package in Focal: In Progress Status in nvidia-graphics-drivers-515 source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Focal: Fix Committed Status in linux-restricted-modules source package in Jammy: In Progress Status in nvidia-graphics-drivers-515 source package in Jammy: Fix Released Status in ubuntu-drivers-common source package in Jammy: Fix Committed Bug description: [ Impact ] * The 515 series introduced open kernel modules for the NVIDIA driver. They come with an open source licence, and should be provided as an option for datacenter GPUs: https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/ Currently, this is only production-ready (and enabled) on datacenter GPUs. * We should enable signed modules for the 515-open drivers, giving users the option to try the drivers. * The ubuntu-drivers tool should set a lower priority for the -open flavour, so that we do not end up recommending it over the plain 515 flavour. [ Test Plan ] * [ubuntu-drivers-common]: "sudo ubuntu-drivers install (to make sure the driver is not installed by default)" * [nvidia driver] "sudo ubuntu-drivers install nvidia:515-open" to make sure that the driver can be installed manually. Please make sure that this installs the correct linux-restricted- modules. Note: support for GeForce and Workstation GPUs is alpha-quality, and is disabled by default. This means that desktop testing is not needed at the moment. [ Where problems could occur ] * This adds a new driver combination, which is not meant to be default, and is only enabled for a limited amount of devices (datacenter GPUs). * We need to be sure that the driver is not recommended over the other drivers. [ Other Info ] - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2004645] Re: mmc: sdhci-of-dwcmshc: add the missing device table IDs for acpi
** Tags added: verification-needed-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2004645 Title: mmc: sdhci-of-dwcmshc: add the missing device table IDs for acpi Status in linux-bluefield package in Ubuntu: New Status in linux-bluefield source package in Jammy: Fix Committed Bug description: SRU Justification: [Impact] This change is needed so the sdhci-of-dwcmshc driver can be loaded automatically when built ad kernel module. [Fix] add the missing device table IDs for acpi [Test Case] Build sdhci-of-dwcmshc as kernel module, use modinfo command to make sure the output contains 'acpi*:MLNXBF30:*'. [Regression Potential] No changes to driver funtionality. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2004645/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2004235] Re: mlxbf-pmc counters not functional for llt_miss block
** Tags added: verification-needed-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2004235 Title: mlxbf-pmc counters not functional for llt_miss block Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Focal: Fix Committed Status in linux-bluefield source package in Jammy: Fix Committed Bug description: SRU Justification: [Impact] Currently, the driver uses fixed offsets for the control and data registers in the performance counter module. However, this is not correct since the module is not uniform in all HW blocks, and in this case, the llt_miss block is different from the rest. [Fix] The number of counters present in each block is not fixed, and hence the offsets for the control and data registers should also be calculated accordingly. [Test Case] Without the fix, writing 1 to the llt_miss "enable" file will not result in any of the counters incrementing. With the fix, the counters should increment even with the default event settings. [Regression Potential] Can be considered minimal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2004235/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1991676] Re: Package grub-efi-arm64-signed 1.173.2~18.04.1+2.04-1ubuntu47.4 from bionic-proposed fails to install/upgrade (grub-install: error: efibootmgr: not found.)
I just bumped into this on a new linux-hwe-5.4 version: Setting up grub-efi-arm64-signed (1.187.3~18.04.1+2.06-2ubuntu14.1) ... Installing for arm64-efi platform. grub-install: error: efibootmgr: not found. ref.: https://autopkgtest.ubuntu.com/results/autopkgtest- bionic/bionic/arm64/l/lttng-modules/20230223_161020_a9d08@/log.gz Do we have any progress on it? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1991676 Title: Package grub-efi-arm64-signed 1.173.2~18.04.1+2.04-1ubuntu47.4 from bionic-proposed fails to install/upgrade (grub-install: error: efibootmgr: not found.) Status in ubuntu-kernel-tests: New Status in grub2-signed package in Ubuntu: Invalid Status in linux-hwe-5.4 package in Ubuntu: Confirmed Status in grub2-signed source package in Bionic: Triaged Status in linux-hwe-5.4 source package in Bionic: Confirmed Bug description: The ADT tests for arm64 kernels in Bionic are failing during the setup phase with the following errors: Setting up grub-efi-arm64-signed (1.173.2~18.04.1+2.04-1ubuntu47.4) ... Installing for arm64-efi platform. grub-install: error: efibootmgr: not found. dpkg: error processing package grub-efi-arm64-signed (--configure): installed grub-efi-arm64-signed package post-installation script subprocess returned error exit status 1 Setting up libx11-6:arm64 (2:1.6.4-3ubuntu0.5) ... Processing triggers for man-db (2.8.3-2ubuntu0.1) ... Processing triggers for libc-bin (2.27-3ubuntu1.6) ... Errors were encountered while processing: grub-efi-arm64-signed E: Sub-process /usr/bin/dpkg returned an error code (1) blame: badpkg: testbed setup commands failed with status 100 autopkgtest [15:12:03]: ERROR: erroneous package: testbed setup commands failed with status 100 ADT test log: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/arm64/l/linux-hwe-5.4/20220930_151219_13ac3@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1991676/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008245] Re: zfs-dkms: support linux 6.2
** Tags added: patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/2008245 Title: zfs-dkms: support linux 6.2 Status in zfs-linux package in Ubuntu: New Status in zfs-linux source package in Lunar: New Bug description: [Impact] The current version of zfs-dkms available in lunar fails to build with kernels >= 6.2, reporting the following configure error: configure: error: *** None of the expected "iops->get_acl()" interfaces were detected. *** This may be because your kernel version is newer than what is *** supported, or you are using a patched custom kernel with *** incompatible modifications. *** *** ZFS Version: zfs-2.1.7-1ubuntu1 *** Compatible Kernels: 3.10 - 6.0 [Test case] $ apt install zfs-dkms [Fix] Resync with zfs version in Debian (2.1.9) and apply the usual Ubuntu specific changes. [Regression potential] We may experience zfs regressions due to a new major version, especially on zfs volumes / filesystems created with the previous versions. However this goes in pair with the new major kernel version and we need to upgrade the version of zfs to properly support the new kernel 6.2. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2008245/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1971151] Re: [SRU][Ubuntu 22.04.1] mpi3mr: Add management application interface(BSG) support
** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => Michael Reed (mreed8855) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1971151 Title: [SRU][Ubuntu 22.04.1] mpi3mr: Add management application interface(BSG) support Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: In Progress Bug description: SRU Justification: [Impact] Request to include below mpi3mr driver bug fix patches in Ubuntu 22.04.1(5.15 kernel). These patches got accepted by the upstream and please find the corresponding commit IDs as below: f304d35e5995 scsi: mpi3mr: Update driver version to 8.0.0.69.0 7dbd0dd8cde3 scsi: mpi3mr: Add support for NVMe passthrough 986d6bad2103 scsi: mpi3mr: Expose adapter state to sysfs 43ca11005098 scsi: mpi3mr: Add support for PEL commands 506bc1a0d6ba scsi: mpi3mr: Add support for MPT commands f3de4706c1e0 scsi: mpi3mr: Move data structures/definitions from MPI headers to uapi header f5e6d5a34376 scsi: mpi3mr: Add support for driver commands 4268fa751365 scsi: mpi3mr: Add bsg device support 1fcbe4c49039 scsi: mpi3mr: Fix kernel-doc 4094981db7b6 scsi: mpi3mr: Rework mrioc->bsg_device model to fix warnings 9feb5c4c3f95 scsi: mpi3mr: Add target device related sysfs attributes e51e76edddb1 scsi: mpi3mr: Add shost related sysfs attributes bc7896d31a92 scsi: mpi3mr: Return error if dma_alloc_coherent() fails a25eafd13e5f scsi: mpi3mr: Fix a NULL vs IS_ERR() bug in mpi3mr_bsg_init() 256bd4f23d9c scsi: mpi3mr: Return I/Os to an unrecoverable HBA with DID_ERROR 2dd8389f96d6 scsi: mpi3mr: Hidden drives not removed during soft reset 1aa529d40025 scsi: mpi3mr: Increase I/O timeout value to 60s [Test Plan] 1. Install and boot kernel 2. Run basic I/O tests [Where problems could occur] Moderate to low regression risk for the kernel as most changes are in the driver [Other Info] https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/mpi3mr_bsg_support_3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971151/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1933090] Re: systemd/245.4-4ubuntu3.6 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1
** Merge proposal linked:
https://code.launchpad.net/~enr0n/ubuntu/+source/systemd/+git/systemd/+merge/437809
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.15 in Ubuntu.
https://bugs.launchpad.net/bugs/1933090
Title:
systemd/245.4-4ubuntu3.6 ADT test failure with linux-
hwe-5.11/5.11.0-20.21~20.04.1
Status in linux-hwe-5.11 package in Ubuntu:
Won't Fix
Status in linux-hwe-5.15 package in Ubuntu:
Invalid
Status in systemd package in Ubuntu:
Fix Released
Status in linux-hwe-5.11 source package in Focal:
Won't Fix
Status in linux-hwe-5.15 source package in Focal:
Invalid
Status in systemd source package in Focal:
Triaged
Bug description:
[SRU Impact]
Sysctl was removed from 5.5 kernels. In src/test/test-seccomp.c,
test_protect_syscall
sysctl is called with the expectation the error result is EFAULT and not
ENOSYS.
This affects autotests for all focal-5.15 linux kernels (hwe, azure, gcp,
oem, gke, oracle).
[Fix]
Assertion checks if either EFAULT or ENOSYS is returned. This way it will
work for focal-5.4 kernels and focal-5.15 kernels.
[Test to reproduce the issue]
1. Create a vm and install one of the focal-5.15 kernels (i.e
5.15.0-1029.35~20.04.1 linux-oracle-5.15).
2. Run the autotests for upstream and/or root-unittests:
autopkgtest --test-name=upstream systemd -- qemu
[Test to verify the fix]
1. Same as above
2. Apply the fix in your local repo and run the tests using your local repo
autopkgtest --test-name=upstream -- qemu
[Where problems could occur]
This is not gonna affect end users since it is a change in the test only.
It may impact autotests, but it's a very low probability.
[Original Description]
This is a scripted bug report about ADT failures while running systemd
tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. Whether this
is caused by the dep8 tests of the tested source or the kernel has yet
to be determined.
Testing failed on:
amd64:
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/s/systemd/20210611_220645_bf5b6@/log.gz
armhf:
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/armhf/s/systemd/20210617_124738_5b554@/log.gz
ppc64el:
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/s/systemd/20210611_235629_92856@/log.gz
s390x:
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/s390x/s/systemd/20210611_214456_6427f@/log.gz
In arm64, ppc64el and s390x, 'root-unittests' fails with:
/* test_protect_sysctl */
Assertion 'errno == EFAULT' failed at src/test/test-seccomp.c:311, function
test_protect_sysctl(). A
borting.
sysctlseccomp terminated by signal ABRT.
Assertion 'wait_for_terminate_and_check("sysctlseccomp", pid, WAIT_LOG) ==
EXIT_SUCCESS' failed at s
rc/test/test-seccomp.c:324, function test_protect_sysctl(). Aborting.
FAIL: test-seccomp (code: 134)
In amd64, 'upstream' also fails on 'TEST-24-UNIT-TESTS', which
apparently is caused by the same 'test-seccomp.c:311' assertion
failure.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1933090/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943879] Re: NETDEV WATCHDOG: eno49 (ixgbe): transmit queue 34 timed out
Please test latest mainline kernel: https://kernel.ubuntu.com/~kernel-ppa/mainline/v6.2/amd64/ Headers are not needed. ** Changed in: linux (Ubuntu) Status: Expired => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1943879 Title: NETDEV WATCHDOG: eno49 (ixgbe): transmit queue 34 timed out Status in linux package in Ubuntu: Confirmed Bug description: I am running ubuntu Focal version with following kernel and NIC and noticed where strange error in kernel logs and my nic went down, does any one know about this? # uname -a Linux ostack-phx-comp-gen-1-27.v1v0x.net 5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020 x86_64 x86_64x # lspci | grep -i eth 06:00.0 Ethernet controller: Intel Corporation 82599 10 Gigabit Dual Port Backplane Connection (rev 01) 06:00.1 Ethernet controller: Intel Corporation 82599 10 Gigabit Dual Port Backplane Connection (rev 01) [Thu Sep 16 01:43:51 2021] [ cut here ] [Thu Sep 16 01:43:51 2021] NETDEV WATCHDOG: eno49 (ixgbe): transmit queue 34 timed out [Thu Sep 16 01:43:51 2021] WARNING: CPU: 11 PID: 0 at net/sched/sch_generic.c:447 dev_watchdog+0x258/0x260 [Thu Sep 16 01:43:51 2021] Modules linked in: nf_conntrack_netlink ebt_arp nft_compat nf_tables_set nft_meta_bridgel [Thu Sep 16 01:43:51 2021] ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_mi [Thu Sep 16 01:43:51 2021] CPU: 11 PID: 0 Comm: swapper/11 Not tainted 5.4.0-42-generic #46-Ubuntu [Thu Sep 16 01:43:51 2021] Hardware name: HP ProLiant BL460c Gen9, BIOS I36 02/17/2017 [Thu Sep 16 01:43:51 2021] RIP: 0010:dev_watchdog+0x258/0x260 [Thu Sep 16 01:43:51 2021] Code: 85 c0 75 e5 eb 9f 4c 89 ff c6 05 1f f5 e7 00 01 e8 8d bb fa ff 44 89 e9 4c 89 fe 47 [Thu Sep 16 01:43:51 2021] RSP: 0018:b92d466b4e30 EFLAGS: 00010286 [Thu Sep 16 01:43:51 2021] RAX: RBX: 9373ef57cec0 RCX: 083f [Thu Sep 16 01:43:51 2021] RDX: RSI: 00f6 RDI: 083f [Thu Sep 16 01:43:51 2021] RBP: b92d466b4e60 R08: 937bdf8d78c8 R09: 0004 [Thu Sep 16 01:43:51 2021] R10: R11: 0001 R12: 0040 [Thu Sep 16 01:43:51 2021] R13: 0022 R14: 9373ef580480 R15: 9373ef58 [Thu Sep 16 01:43:51 2021] FS: () GS:937bdf8c() knlGS: [Thu Sep 16 01:43:51 2021] CS: 0010 DS: ES: CR0: 80050033 [Thu Sep 16 01:43:51 2021] CR2: 7f3697ec19dc CR3: 00103ce0a001 CR4: 001626e0 [Thu Sep 16 01:43:51 2021] Call Trace: [Thu Sep 16 01:43:51 2021] [Thu Sep 16 01:43:51 2021] ? pfifo_fast_enqueue+0x150/0x150 [Thu Sep 16 01:43:51 2021] call_timer_fn+0x32/0x130 [Thu Sep 16 01:43:51 2021] __run_timers.part.0+0x180/0x280 [Thu Sep 16 01:43:51 2021] ? tick_sched_handle+0x33/0x60 [Thu Sep 16 01:43:51 2021] ? tick_sched_timer+0x3d/0x80 [Thu Sep 16 01:43:51 2021] ? ktime_get+0x3e/0xa0 [Thu Sep 16 01:43:51 2021] run_timer_softirq+0x2a/0x50 [Thu Sep 16 01:43:51 2021] __do_softirq+0xe1/0x2d6 [Thu Sep 16 01:43:51 2021] ? hrtimer_interrupt+0x13b/0x220 [Thu Sep 16 01:43:51 2021] irq_exit+0xae/0xb0 [Thu Sep 16 01:43:51 2021] smp_apic_timer_interrupt+0x7b/0x140 [Thu Sep 16 01:43:51 2021] apic_timer_interrupt+0xf/0x20 [Thu Sep 16 01:43:51 2021] [Thu Sep 16 01:43:51 2021] RIP: 0010:cpuidle_enter_state+0xc5/0x450 [Thu Sep 16 01:43:51 2021] Code: ff e8 bf 08 81 ff 80 7d c7 00 74 17 9c 58 0f 1f 44 00 00 f6 c4 02 0f 85 65 03 00 0d [Thu Sep 16 01:43:51 2021] RSP: 0018:b92d4634fe38 EFLAGS: 0246 ORIG_RAX: ff13 [Thu Sep 16 01:43:51 2021] RAX: 937bdf8ead00 RBX: 8d159c00 RCX: 001f [Thu Sep 16 01:43:51 2021] RDX: RSI: 3342629e RDI: [Thu Sep 16 01:43:51 2021] RBP: b92d4634fe78 R08: 0011dc129ea2a1f1 R09: 0011dc17357faf00 [Thu Sep 16 01:43:51 2021] R10: 937bdf8e9a00 R11: 937bdf8e99e0 R12: d9253fac20a8 [Thu Sep 16 01:43:51 2021] R13: 0004 R14: 0004 R15: d9253fac20a8 [Thu Sep 16 01:43:51 2021] ? cpuidle_enter_state+0xa1/0x450 [Thu Sep 16 01:43:51 2021] cpuidle_enter+0x2e/0x40 [Thu Sep 16 01:43:51 2021] call_cpuidle+0x23/0x40 [Thu Sep 16 01:43:51 2021] do_idle+0x1dd/0x270 [Thu Sep 16 01:43:51 2021] cpu_startup_entry+0x20/0x30 [Thu Sep 16 01:43:51 2021] start_secondary+0x167/0x1c0 [Thu Sep 16 01:43:51 2021] secondary_startup_64+0xa4/0xb0 [Thu Sep 16 01:43:51 2021] ---[ end trace cb80e9f61341ace0 ]--- [Thu Sep 16 01:43:51 2021] ixgbe :06:00.0 eno49: initiating reset due to tx timeout [Thu Sep 16 01:43:51 2021] ixgbe :06:00.0 eno49: Reset adapter [Thu Sep 16 01:43:51 2021] ixgbe :06:00.0
[Kernel-packages] [Bug 2008269] [NEW] dkms prevents installing vendored-in dkms packages
Public bug reported: [ Impact ] * In kinetic, installing kernel which vendors a dkms module from the archive allows to still install the same dkms module from the archive, in an inactive package: $ sudo apt install linux-virtual zfs-dkms ... zstd.ko: Running module version sanity check. Error! Module version 1.4.5a-2.1.5-1ubuntu6 for zzstd.ko is not newer than what is already found in kernel 5.19.0-35-generic (1.4.5a-2.1.5-1ubuntu6). You may override by specifying --force. depmod... Processing triggers for libc-bin (2.36-0ubuntu2) ... $ echo $? 0 $ sudo dkms status zfs/2.1.5, 5.19.0-35-generic, x86_64: installed (WARNING! Diff between built and installed module!) If the user wishes to use dkms built module for whatever reason, one can then call dkms install --force after apt completes. Whereas in lunar, such apt installation fails, resulting in broken apt packages, and inability to specify `dkms install --force` zzstd.ko: Running module version sanity check. Module version 1.4.5a-2.1.7-1ubuntu1 for zzstd.ko exactly matches what is already found in kernel 6.1.0-14-generic. DKMS will not replace this module. You may override by specifying --force. Error! Installation aborted. dpkg: error processing package zfs-dkms (--configure): installed zfs-dkms package post-installation script subprocess returned error exit status 6 Processing triggers for libc-bin (2.36-0ubuntu4) ... Errors were encountered while processing: zfs-dkms E: Sub-process /usr/local/libexec/mk-sbuild/dpkg returned an error code (1) This breaks existing Ubuntu workflows that allow keeping dkms module installed, and get it upgraded on older kernel abis, if and when desired. [ Test Plan ] * Install zfs-dkms and linux-virtual that vendors the identical version zfs-dkms [ Where problems could occur ] * This looks like upstream regression [ Other Info ] * this is making kernels unmigratable in lunar. ** Affects: dkms (Ubuntu) Importance: Critical Status: Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/2008269 Title: dkms prevents installing vendored-in dkms packages Status in dkms package in Ubuntu: Triaged Bug description: [ Impact ] * In kinetic, installing kernel which vendors a dkms module from the archive allows to still install the same dkms module from the archive, in an inactive package: $ sudo apt install linux-virtual zfs-dkms ... zstd.ko: Running module version sanity check. Error! Module version 1.4.5a-2.1.5-1ubuntu6 for zzstd.ko is not newer than what is already found in kernel 5.19.0-35-generic (1.4.5a-2.1.5-1ubuntu6). You may override by specifying --force. depmod... Processing triggers for libc-bin (2.36-0ubuntu2) ... $ echo $? 0 $ sudo dkms status zfs/2.1.5, 5.19.0-35-generic, x86_64: installed (WARNING! Diff between built and installed module!) If the user wishes to use dkms built module for whatever reason, one can then call dkms install --force after apt completes. Whereas in lunar, such apt installation fails, resulting in broken apt packages, and inability to specify `dkms install --force` zzstd.ko: Running module version sanity check. Module version 1.4.5a-2.1.7-1ubuntu1 for zzstd.ko exactly matches what is already found in kernel 6.1.0-14-generic. DKMS will not replace this module. You may override by specifying --force. Error! Installation aborted. dpkg: error processing package zfs-dkms (--configure): installed zfs-dkms package post-installation script subprocess returned error exit status 6 Processing triggers for libc-bin (2.36-0ubuntu4) ... Errors were encountered while processing: zfs-dkms E: Sub-process /usr/local/libexec/mk-sbuild/dpkg returned an error code (1) This breaks existing Ubuntu workflows that allow keeping dkms module installed, and get it upgraded on older kernel abis, if and when desired. [ Test Plan ] * Install zfs-dkms and linux-virtual that vendors the identical version zfs-dkms [ Where problems could occur ] * This looks like upstream regression [ Other Info ] * this is making kernels unmigratable in lunar. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/2008269/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008268] [NEW] Check abi compatiblity between Lunar and Jammy
Public bug reported: Check abi compatiblity between Lunar and Jammy ** Affects: zfs-linux (Ubuntu) Importance: Undecided Assignee: Dimitri John Ledkov (xnox) Status: New ** Changed in: zfs-linux (Ubuntu) Assignee: (unassigned) => Dimitri John Ledkov (xnox) ** Changed in: zfs-linux (Ubuntu) Milestone: None => ubuntu-23.04-beta -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/2008268 Title: Check abi compatiblity between Lunar and Jammy Status in zfs-linux package in Ubuntu: New Bug description: Check abi compatiblity between Lunar and Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2008268/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2004493] Re: dmidecode support for SMBIOS SPEC 3.5 for type 9 EDSFF enumeration
Hi Craig, You can e.g., either download/install/remove the package from Kinetic in Jammy (its deps work on Jammy) or copy the DMI tables into a Kinetic container. Option 1) Kinetic package on Jammy $ wget https://launchpad.net/ubuntu/+archive/primary/+files/dmidecode_3.4-1_amd64.deb $ sudo apt install ./dmidecode_3.4-1_amd64.deb $ sudo dmidecode $ sudo apt install --allow-downgrades dmidecode/jammy-updates Option 2) Copy DMI tables to Kinetic container $ sudo tar cf dmi-tables.tar /sys/firmware/dmi/tables/ $ lxc launch ubuntu:kinetic kinetic $ lxc file push dmi-tables.tar kinetic/tmp/ $ lxc shell kinetic # cd /tmp # tar xf dmi-tables.tar # mount --bind /tmp/sys/firmware/dmi/tables/ /sys/firmware/dmi/tables/ # dmidecode # umount /sys/firmware/dmi/tables/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dmidecode in Ubuntu. https://bugs.launchpad.net/bugs/2004493 Title: dmidecode support for SMBIOS SPEC 3.5 for type 9 EDSFF enumeration Status in dmidecode package in Ubuntu: Incomplete Bug description: For EDSFF slot type changes no longer indicate the PCIe Generation supported nor do they indicate the full formfactor. To accomodate this severa sections have been added in the spec as follows 7.10.10 System Slots — Slot Information , 7.10.11 System Slots —Slot Physical Width , 7.10.12 System Slots — Slot Pitch , 7.10.13 System Slots — Slot Height. Currently they do no show up in the dmidecode 3.3 / Jammy Untested on Kinetic. This is related to a previous bug as well. https://bugs.launchpad.net/ubuntu/+source/dmidecode/+bug/1986852 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dmidecode/+bug/2004493/+subscriptions -- Mailing list: https://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 2004534] Re: Lenovo IdeaPad 3 15ABA7 never wakes from sleep
And to fill you up, the problem with hibernation/suspend/sleep is with all dstros i installed on my lenovo ideapad 3. I suppose something in the HW<->SW still is not fixed with Linux. Wish you luck Ubuntu team. You have the most elaborated user friendly Linux! 90/100, but still many fixes to work on... On Tue, Feb 14, 2023 at 9:55 AM mahavishnu wrote: > OK, i disabled all suspend and dim of the screen. no sleep at all. > after 10-12h the when i started to work with the system suddenly the > cursor of the mouse became square and couldn't start anything neither with > kbd or the nouse, nor i could reboot or shut down. > the only exit is the power button. > Any ideas? > > On Mon, Feb 13, 2023 at 10:50 AM Daniel van Vugt < > 2004...@bugs.launchpad.net> wrote: > >> Also, comment #numbers can be found on this page: >> https://launchpad.net/bugs/2004534 >> >> That's probably easier to follow than email. >> >> -- >> You received this bug notification because you are subscribed to the bug >> report. >> https://bugs.launchpad.net/bugs/2004534 >> >> Title: >> Lenovo IdeaPad 3 15ABA7 never wakes from sleep >> >> Status in linux package in Ubuntu: >> Confirmed >> >> Bug description: >>- on locked screen: the keyboard blocks after a while and I cannot >> login anymore; >>- on unlocked screen: >>= apps do not start (failed to start); >>= no icon pictures on desktop; >>= no wallpaper anymore (black background); >> >> ProblemType: Bug >> DistroRelease: Ubuntu 22.04 >> Package: xorg 1:7.7+23ubuntu2 >> ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 >> Uname: Linux 5.15.0-58-generic x86_64 >> ApportVersion: 2.20.11-0ubuntu82.3 >> Architecture: amd64 >> BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' >> CasperMD5CheckResult: pass >> CompositorRunning: None >> CurrentDesktop: ubuntu:GNOME >> Date: Thu Feb 2 07:15:13 2023 >> DistUpgraded: Fresh install >> DistroCodename: jammy >> DistroVariant: ubuntu >> ExtraDebuggingInterest: Yes, including running git bisection searches >> GraphicsCard: >>Advanced Micro Devices, Inc. [AMD/ATI] Barcelo [1002:15e7] (rev c2) >> (prog-if 00 [VGA controller]) >> Subsystem: Lenovo Device [17aa:3801] >> InstallationDate: Installed on 2023-02-01 (1 days ago) >> InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 >> (20220809.1) >> MachineType: LENOVO 82RN >> ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic >> root=UUID=b63af605-bd2f-4b16-8bb4-1cc9bb85554c ro quiet splash vt.handoff=7 >> SourcePackage: xorg >> Symptom: display >> UpgradeStatus: No upgrade log present (probably fresh install) >> dmi.bios.date: 08/04/2022 >> dmi.bios.release: 1.38 >> dmi.bios.vendor: LENOVO >> dmi.bios.version: JTCN38WW >> dmi.board.asset.tag: No Asset Tag >> dmi.board.name: LNVNB161216 >> dmi.board.vendor: LENOVO >> dmi.board.version: NO DPK >> dmi.chassis.asset.tag: No Asset Tag >> dmi.chassis.type: 10 >> dmi.chassis.vendor: LENOVO >> dmi.chassis.version: IdeaPad 3 15ABA7 >> dmi.ec.firmware.release: 1.38 >> dmi.modalias: >> dmi:bvnLENOVO:bvrJTCN38WW:bd08/04/2022:br1.38:efr1.38:svnLENOVO:pn82RN:pvrIdeaPad315ABA7:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrIdeaPad315ABA7:skuLENOVO_MT_82RN_BU_idea_FM_IdeaPad315ABA7: >> dmi.product.family: IdeaPad 3 15ABA7 >> dmi.product.name: 82RN >> dmi.product.sku: LENOVO_MT_82RN_BU_idea_FM_IdeaPad 3 15ABA7 >> dmi.product.version: IdeaPad 3 15ABA7 >> dmi.sys.vendor: LENOVO >> version.compiz: compiz N/A >> version.libdrm2: libdrm2 2.4.110-1ubuntu1 >> version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 >> version.libgl1-mesa-glx: libgl1-mesa-glx N/A >> version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.5 >> version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A >> version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 >> version.xserver-xorg-video-intel: xserver-xorg-video-intel >> 2:2.99.917+git20210115-1 >> version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau >> 1:1.0.17-2build1 >> >> To manage notifications about this bug go to: >> >> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2004534/+subscriptions >> >> -- 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/2004534 Title: Lenovo IdeaPad 3 15ABA7 never wakes from sleep Status in linux package in Ubuntu: Confirmed Bug description: - on locked screen: the keyboard blocks after a while and I cannot login anymore; - on unlocked screen: = apps do not start (failed to start); = no icon pictures on desktop; = no wallpaper anymore (black background); ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-gcp/5.19.0.1018.15)
All autopkgtests for the newly accepted linux-meta-gcp (5.19.0.1018.15) for kinetic have finished running. The following regressions have been reported in tests triggered by the package: glibc/2.36-0ubuntu4 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/kinetic/update_excuses.html#linux-meta-gcp [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2006797] Re: MT7922 firmware not working
I searched for the Internet and some Anons suggested resetting the Network-Adapter by disconnecting them from power. (i.E.: https://unix.stackexchange.com/a/723829 ) So, I executed the following steps: 1. Removing the Motherboard from ANY power source (even took the battery off) 2. pressed power button several times to unload capacitors 3. waited ~5 mins and connected power cable and inserted battery - Then, after booting into the system, the network was not loaded at all. 4. opened the shell and executed `$ sudo modprobe mt7921e` - Everything was working now. I am using/restarting my PC daily and there was only on occurrence where the WLAN was not working, a second `$ sudo modprobe mt7921e` fixed it. Strangely enough, I loaded the mod before I did the power surge, so I only can narrow it down to that step. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2006797 Title: MT7922 firmware not working Status in linux package in Ubuntu: Confirmed Bug description: Hey I have a "ASUS ROG Strix B650-A Gaming WIFI" (https://rog.asus.com/motherboards/rog-strix/rog-strix-b650-a-gaming- wifi-model/) Motherboard and the WiFi/Bluetooth is not working. On windows, the module is working fine. Using "Kubuntu 22.10" with Kernel "5.19.0-35-generic" lshw -class network: *-network description: Network controller product: MT7922 802.11ax PCI Express Wireless Network Adapter vendor: MEDIATEK Corp. physical id: 0 bus info: pci@:0b:00.0 version: 00 width: 64 bits clock: 33MHz capabilities: pciexpress msi pm bus_master cap_list configuration: driver=mt7921e latency=0 resources: iomemory:fc0-fbf irq:119 memory:fc3030-fc303f memory:fc50-fc507fff #dmesg | grep mt7921e [ 17.001057] mt7921e :0b:00.0: enabling device ( -> 0002) [ 17.001199] mt7921e :0b:00.0: ASIC revision: 79220010 [ 20.247369] mt7921e :0b:00.0: Message 0004008a (seq 1) timeout [ 23.575534] mt7921e :0b:00.0: Message 0004008a (seq 2) timeout [ 26.907372] mt7921e :0b:00.0: Message 0004008a (seq 3) timeout [ 30.231376] mt7921e :0b:00.0: Message 0004008a (seq 4) timeout [ 33.559704] mt7921e :0b:00.0: Message 0004008a (seq 5) timeout [ 36.887365] mt7921e :0b:00.0: Message 0004008a (seq 6) timeout [ 40.215367] mt7921e :0b:00.0: Message 0004008a (seq 7) timeout [ 43.543670] mt7921e :0b:00.0: Message 0004008a (seq 8) timeout [ 46.871378] mt7921e :0b:00.0: Message 0004008a (seq 9) timeout [ 50.199714] mt7921e :0b:00.0: Message 0004008a (seq 10) timeout [ 50.280219] mt7921e :0b:00.0: hardware init failed ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-35-generic 5.19.0-35.36 ProcVersionSignature: Ubuntu 5.19.0-35.36-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Fri Feb 10 03:33:02 2023 InstallationDate: Installed on 2023-02-09 (0 days ago) InstallationMedia: Kubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: ASUS System Product Name ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-35-generic root=/dev/mapper/vgkubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.19.0-35-generic N/A linux-backports-modules-5.19.0-35-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1.4 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/21/2022 dmi.bios.release: 8.23 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0823 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX B650-A GAMING WIFI dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0823:bd11/21/2022:br8.23:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB650-AGAMINGWIFI:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2006797/+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 1987829] Re: LG Gram 12gen high CPU use when USB-C/TB is in use
I would gladly answer #20 @kaihengfeng but I don't have nor want Windows on this professional machine used for sysadmin work. Since this appears to be a global kernel issue and I didn't find it on the Linux kernel Bugzilla, I have forwarded the issue: https://bugzilla.kernel.org/show_bug.cgi?id=217076 I'm unsure if this is necessary, but if not, there isn't much harm, and if necessary, well now it's done. All the best ** Bug watch added: Linux Kernel Bug Tracker #217076 https://bugzilla.kernel.org/show_bug.cgi?id=217076 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1987829 Title: LG Gram 12gen high CPU use when USB-C/TB is in use Status in linux package in Ubuntu: Confirmed Status in linux package in Fedora: New Bug description: LG Gram laptop 17Z90Q with a Core i7-1260P CPU. Whenever an external monitor is connected to USB-C/Thunderbolt 4, average load goes above 3.0 and the machine is getting very hot. Output from top -H shows a lot of kworker CPU usage: top - 11:45:06 up 33 min, 2 users, load average: 3,30, 3,08, 2,79 Threads: 1442 total, 2 running, 1440 sleeping, 0 stopped, 0 zombie %Cpu(s): 0,1 us, 3,7 sy, 0,0 ni, 96,1 id, 0,0 wa, 0,0 hi, 0,1 si, 0,0 st MiB Mem : 15684,6 total, 8510,2 free, 2580,8 used, 4593,6 buff/cache MiB Swap: 3815,0 total, 3815,0 free, 0,0 used. 11326,9 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ WCHAN COMMAND 7766 root 20 0 0 0 0 R 19,8 0,0 0:56.05 worker_th+ kworker/0:2-events 196 root 20 0 0 0 0 D 15,8 0,0 1:18.12 ec_guard kworker/u32:2+USBC000:00-con0 10237 root 20 0 0 0 0 I 12,9 0,0 0:26.44 worker_th+ kworker/0:0-events 1027 root 20 0 0 0 0 I 6,6 0,0 0:43.30 worker_th+ kworker/1:3-events 10971 root 20 0 0 0 0 I 4,0 0,0 0:00.20 worker_th+ kworker/15:0-events 175 root 20 0 0 0 0 I 2,3 0,0 0:03.24 worker_th+ kworker/11:1-events 2410 root 20 0 0 0 0 I 1,7 0,0 0:05.49 worker_th+ kworker/9:3-events Perf shows a lot of time spent inside handle_irq_event/acpi_ev_gpe_detect/acpi_hw_gpe_read. Additionally, kernel log is getting spammed with these lines every 4 seconds (but also without any USB-C device attached): [ 223.514304] ACPI Error: No handler for Region [XIN1] (f2ad4f1f) [UserDefinedRegion] (20210730/evregion-130) [ 223.514323] ACPI Error: Region UserDefinedRegion (ID=143) has no handler (20210730/exfldio-261) [ 223.514337] Initialized Local Variables for Method [_TMP]: [ 223.514339] Local0: 21495082Integer 0034 [ 223.514349] No Arguments are initialized for method [_TMP] [ 223.514354] ACPI Error: Aborting method \_SB.PC00.LPCB.LGEC.SEN2._TMP due to previous error (AE_NOT_EXIST) (20210730/psparse-529) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-46-generic 5.15.0-46.49 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: me 1678 F pulseaudio /dev/snd/controlC1: me 1678 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass Date: Fri Aug 26 11:57:05 2022 InstallationDate: Installed on 2022-08-25 (1 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LG Electronics 17Z90Q-G.AA78N ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=e2f96916-a67c-432e-b687-730071271216 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/06/2022 dmi.bios.release: 0.1 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: A1ZG0380 X64 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 17Z90Q dmi.board.vendor: LG Electronics dmi.board.version: FAB1 dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LG Electronics dmi.chassis.version: 0.1 dmi.ec.firmware.release: 33.0 dmi.modalias:
[Kernel-packages] [Bug 2008118] Re: Freeze on resume from suspend (amdgpu errors)
This only affects automatic suspension (activated by idle time).
Manually suspending the system works as expected.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2008118
Title:
Freeze on resume from suspend (amdgpu errors)
Status in linux package in Ubuntu:
Confirmed
Bug description:
I'm running Kubuntu 22.04 LTS, fresh install. Most of the time, when
resuming from suspend-to-RAM, the system will freeze. Sometimes the
screen is all black, while other times it is showing the lock screen;
in both cases it's completely unresponsive.
The only way out is to force a reboot with the SYSRQ "REISUB" key
combo. I tried switching VT with Ctrl+Alt+F{1-7}, but it does not
respond.
From a quick look at the logs I can see that it shows a lot of red-
colored error lines from the kernel about amdgpu.
I didn't have this problem with other flavors (used Xubuntu and
Ubuntu, 22.04 and 22.10), so I guess it's a Kubuntu bug.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-60-generic 5.15.0-60.66
ProcVersionSignature: Ubuntu 5.15.0-60.66-generic 5.15.78
Uname: Linux 5.15.0-60-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: dsilva 1217 F pulseaudio
/dev/snd/controlC1: dsilva 1217 F pulseaudio
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: KDE
Date: Wed Feb 22 14:55:20 2023
InstallationDate: Installed on 2023-02-19 (2 days ago)
InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64
(20220809.1)
MachineType: Gigabyte Technology Co., Ltd. B460MDS3H
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-60-generic
root=UUID=5a8a2ff2-be5a-4aa5-ae8b-874e45080a04 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-5.15.0-60-generic N/A
linux-backports-modules-5.15.0-60-generic N/A
linux-firmware 20220329.git681281e4-0ubuntu3.10
RfKill:
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/23/2021
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F5
dmi.board.asset.tag: Default string
dmi.board.name: B460M DS3H
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: Default string
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd11/23/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnB460MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB460MDS3H:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
dmi.product.family: B460 MB
dmi.product.name: B460MDS3H
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008118/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
