[Kernel-packages] [Bug 1998024] Re: Xorg crashes on startup if Marco window manager is used
[Expired for nvidia-graphics-drivers-520 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: nvidia-graphics-drivers-520 (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-520 in Ubuntu. https://bugs.launchpad.net/bugs/1998024 Title: Xorg crashes on startup if Marco window manager is used Status in nvidia-graphics-drivers-520 package in Ubuntu: Expired Status in xorg-server package in Ubuntu: Expired Bug description: I'm running MATE desktop and I installed NVIDIA GTX 1060 GPU to my system and Xorg crashes after entering password. I proceeded to run strace with startx trying to debug this and it seems that the window manager `marco` does some (yet unknown) command which causes Xorg to crash with SIGABRT (signal 6) or SIGSEGV (signal 11) and emit stack trace: 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) 2: ? (?+0x0) (EE) Segmentation fault at address 0x0 (EE) Caught signal 11 (Segmentation fault). Server aborting The Xorg itself declares signal 11 but `journalctl --since "5 min ago"` shows kernel: potentially unexpected fatal signal 6. kernel: CPU: 2 PID: 20660 Comm: Xorg Tainted: P OE 5.15.0-53-lowlatency #59~20.04.1-Ubuntu kernel: Hardware name: System manufacturer System Product Name/P8H77-M PRO, BIOS 1505 10/17/2014 followed with register dump. Before crashing, process running `marco` also emits warning which I think is not related to the problem (it may be caused by the fact that I executed marco with startx instead of mate-session): Window manager warning: Log level 128: Name com.canonical.AppMenu.Registrar does not exist on the session bus Workaround: downgrading to NVIDIA driver version 470 avoids the problem (as suggested here: https://ubuntu-mate.community/t/updated-nvidia-settings-now-x-wont-start/24991) # sudo apt install linux-modules-nvidia-470-lowlatency-hwe-20.04 nvidia-driver-470 linux-modules-nvidia-520-lowlatency-hwe-20.04- nvidia-driver-520- I also tried version 515 and it caused the same crash. I'm using following kernel package: linux-lowlatency-hwe-20.04 (+ linux-tools-lowlatency-hwe-20.04) I would guess that the bug is in Xorg OsLookupColor() implementation which gets triggered by recent NVIDIA driver change. Bug https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1853266 might be related. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nvidia-driver-520 (not installed) ProcVersionSignature: Ubuntu 5.15.0-53.59~20.04.1-lowlatency 5.15.64 Uname: Linux 5.15.0-53-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Sat Nov 26 21:42:50 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2019-01-05 (1421 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: nvidia-graphics-drivers-520 UpgradeStatus: Upgraded to focal on 2022-09-13 (74 days ago) modified.conffile..etc.init.d.apport: [modified] mtime.conffile..etc.init.d.apport: 2022-05-19T12:50:20.029158 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-520/+bug/1998024/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998669] Re: after long suspend my keyboard and mouse don't work.
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1998669 Title: after long suspend my keyboard and mouse don't work. Status in linux package in Ubuntu: Expired Bug description: after long suspend my mouse and keyboard don't work every time the devices don't work after suspend, there are three lines of 'acpid: input device has been disconnected...' just the usb ports of my mouse and keyboard don't work part of syslog: Dec 2 23:18:05 justin-MS-7B86 kernel: [ 13.447052] hid-generic 0003:046D:C539.0006: input,hiddev2,hidraw5: USB HID v1.11 Mouse [Logitech USB Receiver] on usb-:28:00.3-2/input1 Dec 2 23:18:05 justin-MS-7B86 kernel: [ 13.451071] hid-generic 0003:046D:C539.0007: hiddev3,hidraw6: USB HID v1.11 Device [Logitech USB Receiver] on usb-:28:00.3-2/input2 Dec 2 23:18:05 justin-MS-7B86 mtp-probe: checking bus 3, device 2: "/sys/devices/pci:00/:00:08.1/:28:00.3/usb3/3-2" Dec 2 23:18:05 justin-MS-7B86 mtp-probe: bus: 3, device: 2 was not an MTP device Dec 2 23:18:05 justin-MS-7B86 fprintd[1556]: libusb: error [udev_hotplug_event] ignoring udev action change Dec 2 23:18:05 justin-MS-7B86 kernel: [ 13.598412] logitech-djreceiver 0003:046D:C539.0005: hidraw4: USB HID v1.11 Keyboard [Logitech USB Receiver] on usb-:28:00.3-2/input0 Dec 2 23:18:05 justin-MS-7B86 acpid: input device has been disconnected, fd 24 Dec 2 23:18:05 justin-MS-7B86 acpid: input device has been disconnected, fd 25 Dec 2 23:18:05 justin-MS-7B86 acpid: input device has been disconnected, fd 26 Dec 2 23:18:05 justin-MS-7B86 kernel: [ 13.810553] logitech-djreceiver 0003:046D:C539.0006: hiddev2,hidraw5: USB HID v1.11 Mouse [Logitech USB Receiver] on usb-:28:00.3-2/input1 Dec 2 23:18:05 justin-MS-7B86 kernel: [ 13.870475] logitech-djreceiver 0003:046D:C539.0007: hiddev3,hidraw6: USB HID v1.11 Device [Logitech USB Receiver] on usb-:28:00.3-2/input2 Dec 2 23:18:05 justin-MS-7B86 kernel: [ 13.931686] logitech-djreceiver 0003:046D:C539.0007: device of type eQUAD Lightspeed 1 (0x0c) connected on slot 1 Dec 2 23:18:05 justin-MS-7B86 kernel: [ 13.931926] input: Logitech Wireless Mouse PID:407f Keyboard as /devices/pci:00/:00:08.1/:28:00.3/usb3/3-2/3-2:1.2/0003:046D:C539.0007/0003:046D:407F.0008/input/input25 Dec 2 23:18:05 justin-MS-7B86 kernel: [ 13.932077] input: Logitech Wireless Mouse PID:407f Mouse as /devices/pci:00/:00:08.1/:28:00.3/usb3/3-2/3-2:1.2/0003:046D:C539.0007/0003:046D:407F.0008/input/input26 Dec 2 23:18:05 justin-MS-7B86 kernel: [ 13.932340] hid-generic 0003:046D:407F.0008: input,hidraw7: USB HID v1.11 Keyboard [Logitech Wireless Mouse PID:407f] on usb-:28:00.3-2/input2:1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998669/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998024] Re: Xorg crashes on startup if Marco window manager is used
[Expired for xorg-server (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg-server (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-520 in Ubuntu. https://bugs.launchpad.net/bugs/1998024 Title: Xorg crashes on startup if Marco window manager is used Status in nvidia-graphics-drivers-520 package in Ubuntu: Expired Status in xorg-server package in Ubuntu: Expired Bug description: I'm running MATE desktop and I installed NVIDIA GTX 1060 GPU to my system and Xorg crashes after entering password. I proceeded to run strace with startx trying to debug this and it seems that the window manager `marco` does some (yet unknown) command which causes Xorg to crash with SIGABRT (signal 6) or SIGSEGV (signal 11) and emit stack trace: 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) 2: ? (?+0x0) (EE) Segmentation fault at address 0x0 (EE) Caught signal 11 (Segmentation fault). Server aborting The Xorg itself declares signal 11 but `journalctl --since "5 min ago"` shows kernel: potentially unexpected fatal signal 6. kernel: CPU: 2 PID: 20660 Comm: Xorg Tainted: P OE 5.15.0-53-lowlatency #59~20.04.1-Ubuntu kernel: Hardware name: System manufacturer System Product Name/P8H77-M PRO, BIOS 1505 10/17/2014 followed with register dump. Before crashing, process running `marco` also emits warning which I think is not related to the problem (it may be caused by the fact that I executed marco with startx instead of mate-session): Window manager warning: Log level 128: Name com.canonical.AppMenu.Registrar does not exist on the session bus Workaround: downgrading to NVIDIA driver version 470 avoids the problem (as suggested here: https://ubuntu-mate.community/t/updated-nvidia-settings-now-x-wont-start/24991) # sudo apt install linux-modules-nvidia-470-lowlatency-hwe-20.04 nvidia-driver-470 linux-modules-nvidia-520-lowlatency-hwe-20.04- nvidia-driver-520- I also tried version 515 and it caused the same crash. I'm using following kernel package: linux-lowlatency-hwe-20.04 (+ linux-tools-lowlatency-hwe-20.04) I would guess that the bug is in Xorg OsLookupColor() implementation which gets triggered by recent NVIDIA driver change. Bug https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1853266 might be related. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nvidia-driver-520 (not installed) ProcVersionSignature: Ubuntu 5.15.0-53.59~20.04.1-lowlatency 5.15.64 Uname: Linux 5.15.0-53-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Sat Nov 26 21:42:50 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2019-01-05 (1421 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: nvidia-graphics-drivers-520 UpgradeStatus: Upgraded to focal on 2022-09-13 (74 days ago) modified.conffile..etc.init.d.apport: [modified] mtime.conffile..etc.init.d.apport: 2022-05-19T12:50:20.029158 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-520/+bug/1998024/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998692] Re: Lenovo ThinkPad E14 Gen 2 reboots after wakeup from suspend
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1998692 Title: Lenovo ThinkPad E14 Gen 2 reboots after wakeup from suspend Status in linux package in Ubuntu: Expired Bug description: When I put the system into suspend state and then wake it up, it reboots after about 30 seconds. I have checked dmesg file, and there're some errors displayed for tpm module as well as ACPI-related ones (please, find it attached). Please, let me know if any additional information is needed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998692/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2005118] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2005118 Title: nvme ssd disappears at wakeup after suspend Status in linux package in Ubuntu: Confirmed Bug description: My newly installed ssd Silicon Power 2TB A80 (SP002TBP34A80M28) disappears after suspend and wakeup. It works correctly after, for example, hibernate. Tested the same ssd both on desktop and laptop. The last working ubuntu version I found is 19.04. The problem persists on ubuntu versions 20.04 - 22.04. The fix probably exists, as it works correctly on ubuntu 22.10. dmesg logs after suspend on ubuntu 22.04 (problematic) [ 216.117333] nvme nvme0: 8/0/0 default/read/poll queues [ 216.131578] nvme nvme0: identifiers changed for nsid 1 on ubuntu 22.10 (correct work): [ 308.175030] nvme nvme0: 8/0/0 default/read/poll queues [ 308.177114] nvme nvme0: Ignoring bogus Namespace Identifiers could the fix be backported into kernel of 22.04 or maybe a workaround exists? lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 apt-cache policy linux-image-5.15.0-58-generic 5.15.0-58.64 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-58-generic 5.15.0-58.64 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 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vkovalen 1208 F pulseaudio /dev/snd/pcmC0D0p: vkovalen 1208 F...m pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Feb 4 04:19:55 2023 HibernationDevice: RESUME=UUID=9711dc42-be74-486c-9639-efaddf7fe0b8 InstallationDate: Installed on 2023-01-26 (8 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 003: ID 8087:0029 Intel Corp. AX200 Bluetooth Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M |__ Port 3: Dev 2, If 0, Class=Vendor Specific Class, Driver=rtsx_usb, 480M |__ Port 10: Dev 3, If 0, Class=Wireless, Driver=btusb, 12M |__ Port 10: Dev 3, If 1, Class=Wireless, Driver=btusb, 12M MachineType: Micro-Star International Co., Ltd. GS40 6QE Phantom ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic root=UUID=6ea99286-8861-4395-962b-f6719dd5105c ro "acpi_osi=!Windows 2013" acpi_osi=Linux resume=UUID=9711dc42-be74-486c-9639-efaddf7fe0b8 loglevel=2 nvme_core.default_ps_max_latency_us=0 RelatedPackageVersions: linux-restricted-modules-5.15.0-58-generic N/A linux-backports-modules-5.15.0-58-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.9 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/15/2018 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E14A1IMS.113 dmi.board.asset.tag: Default string dmi.board.name: MS-14A1 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:0.C dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE14A1IMS.113:bd01/15/2018:br5.11:svnMicro-StarInternationalCo.,Ltd.:pnGS406QEPhantom:pvrREV0.C:rvnMicro-StarInternationalCo.,Ltd.:rnMS-14A1:rvrREV0.C:cvnDefaultstring:ct10:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: GS40 6QE Phantom dmi.product.sku: Default string dmi.product.version: REV:0.C dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2005118/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2005118] [NEW] nvme ssd disappears at wakeup after suspend
Public bug reported: My newly installed ssd Silicon Power 2TB A80 (SP002TBP34A80M28) disappears after suspend and wakeup. It works correctly after, for example, hibernate. Tested the same ssd both on desktop and laptop. The last working ubuntu version I found is 19.04. The problem persists on ubuntu versions 20.04 - 22.04. The fix probably exists, as it works correctly on ubuntu 22.10. dmesg logs after suspend on ubuntu 22.04 (problematic) [ 216.117333] nvme nvme0: 8/0/0 default/read/poll queues [ 216.131578] nvme nvme0: identifiers changed for nsid 1 on ubuntu 22.10 (correct work): [ 308.175030] nvme nvme0: 8/0/0 default/read/poll queues [ 308.177114] nvme nvme0: Ignoring bogus Namespace Identifiers could the fix be backported into kernel of 22.04 or maybe a workaround exists? lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 apt-cache policy linux-image-5.15.0-58-generic 5.15.0-58.64 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-58-generic 5.15.0-58.64 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 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vkovalen 1208 F pulseaudio /dev/snd/pcmC0D0p: vkovalen 1208 F...m pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Feb 4 04:19:55 2023 HibernationDevice: RESUME=UUID=9711dc42-be74-486c-9639-efaddf7fe0b8 InstallationDate: Installed on 2023-01-26 (8 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 003: ID 8087:0029 Intel Corp. AX200 Bluetooth Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M |__ Port 3: Dev 2, If 0, Class=Vendor Specific Class, Driver=rtsx_usb, 480M |__ Port 10: Dev 3, If 0, Class=Wireless, Driver=btusb, 12M |__ Port 10: Dev 3, If 1, Class=Wireless, Driver=btusb, 12M MachineType: Micro-Star International Co., Ltd. GS40 6QE Phantom ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic root=UUID=6ea99286-8861-4395-962b-f6719dd5105c ro "acpi_osi=!Windows 2013" acpi_osi=Linux resume=UUID=9711dc42-be74-486c-9639-efaddf7fe0b8 loglevel=2 nvme_core.default_ps_max_latency_us=0 RelatedPackageVersions: linux-restricted-modules-5.15.0-58-generic N/A linux-backports-modules-5.15.0-58-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.9 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/15/2018 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E14A1IMS.113 dmi.board.asset.tag: Default string dmi.board.name: MS-14A1 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:0.C dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE14A1IMS.113:bd01/15/2018:br5.11:svnMicro-StarInternationalCo.,Ltd.:pnGS406QEPhantom:pvrREV0.C:rvnMicro-StarInternationalCo.,Ltd.:rnMS-14A1:rvrREV0.C:cvnDefaultstring:ct10:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: GS40 6QE Phantom dmi.product.sku: Default string dmi.product.version: REV:0.C dmi.sys.vendor: Micro-Star International Co., Ltd. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy nvme wayland-session ** Attachment added: "full dmesg 22.04" https://bugs.launchpad.net/bugs/2005118/+attachment/5644699/+files/dmesg22.04.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/2005118 Title: nvme ssd disappears at wakeup after suspend Status in linux package in Ubuntu: New Bug description: My newly installed ssd Silicon Power 2TB A80 (SP002TBP34A80M28) disappears after suspend and wakeup. It works correctly after, for example, hibernate. Tested the same ssd both on desktop and laptop. The last working ubuntu version I found is 19.04. The problem persists on ubuntu versions 20.04 - 22.04. The fix probably exists, as it works correctly on ubuntu 22.10. dmesg logs after suspend on ubuntu 22.04 (problematic) [ 216.117333] nvme nvme0: 8/0/0 default/read/poll queues [ 216.131578] nvme nvme0: identifiers changed for nsid 1 on ubuntu 22.10 (correct work): [ 308.175030]
[Kernel-packages] [Bug 2004977] Re: Focal update: v5.4.230 upstream stable release
** Description changed: + SRU Justification - SRU Justification + Impact: + The upstream process for stable tree updates is quite similar + in scope to the Ubuntu SRU process, e.g., each patch has to + demonstrably fix a bug, and each patch is vetted by upstream + by originating either directly from a mainline/stable Linux tree or + a minimally backported form of that patch. The following upstream + stable patches should be included in the Ubuntu kernel: - Impact: -The upstream process for stable tree updates is quite similar -in scope to the Ubuntu SRU process, e.g., each patch has to -demonstrably fix a bug, and each patch is vetted by upstream -by originating either directly from a mainline/stable Linux tree or -a minimally backported form of that patch. The following upstream -stable patches should be included in the Ubuntu kernel: + v5.4.230 upstream stable release + from git://git.kernel.org/ -v5.4.230 upstream stable release -from git://git.kernel.org/ + pNFS/filelayout: Fix coalescing test for single DS + selftests/bpf: check null propagation only neither reg is PTR_TO_BTF_ID + net/ethtool/ioctl: return -EOPNOTSUPP if we have no phy stats + RDMA/srp: Move large values to a new enum for gcc13 + f2fs: let's avoid panic if extent_tree is not created + wifi: brcmfmac: fix regression for Broadcom PCIe wifi devices + Add exception protection processing for vd in axi_chan_handle_err function + nilfs2: fix general protection fault in nilfs_btree_insert() + efi: fix userspace infinite retry read efivars after EFI runtime services page fault + drm/i915/gt: Reset twice + ALSA: hda/realtek - Turn on power early + xhci-pci: set the dma max_seg_size + usb: xhci: Check endpoint is valid before dereferencing it + xhci: Fix null pointer dereference when host dies + xhci: Add update_hub_device override for PCI xHCI hosts + xhci: Add a flag to disable USB3 lpm on a xhci root port level. + usb: acpi: add helper to check port lpm capability using acpi _DSM + xhci: Detect lpm incapable xHC USB3 roothub ports from ACPI tables + prlimit: do_prlimit needs to have a speculation check + USB: serial: option: add Quectel EM05-G (GR) modem + USB: serial: option: add Quectel EM05-G (CS) modem + USB: serial: option: add Quectel EM05-G (RS) modem + USB: serial: option: add Quectel EC200U modem + USB: serial: option: add Quectel EM05CN (SG) modem + USB: serial: option: add Quectel EM05CN modem + USB: misc: iowarrior: fix up header size for USB_DEVICE_ID_CODEMERCS_IOW100 + misc: fastrpc: Don't remove map on creater_process and device_release + misc: fastrpc: Fix use-after-free race condition for maps + usb: core: hub: disable autosuspend for TI TUSB8041 + comedi: adv_pci1760: Fix PWM instruction handling + mmc: sunxi-mmc: Fix clock refcount imbalance during unbind + btrfs: fix race between quota rescan and disable leading to NULL pointer deref + cifs: do not include page data when checking signature + USB: gadgetfs: Fix race between mounting and unmounting + USB: serial: cp210x: add SCALANCE LPE-9000 device id + usb: host: ehci-fsl: Fix module alias + usb: typec: altmodes/displayport: Add pin assignment helper + usb: typec: altmodes/displayport: Fix pin assignment calculation + usb: gadget: g_webcam: Send color matching descriptor per frame + usb: gadget: f_ncm: fix potential NULL ptr deref in ncm_bitrate() + usb-storage: apply IGNORE_UAS only for HIKSEMI MD202 on RTL9210 + dt-bindings: phy: g12a-usb3-pcie-phy: fix compatible string documentation + serial: pch_uart: Pass correct sg to dma_unmap_sg() + dmaengine: tegra210-adma: fix global intr clear + serial: atmel: fix incorrect baudrate setup + gsmi: fix null-deref in gsmi_get_variable + drm/i915: re-disable RC6p on Sandy Bridge + drm/amd/display: Fix set scaling doesn's work + drm/amd/display: Fix COLOR_SPACE_YCBCR2020_TYPE matrix + x86/fpu: Use _Alignof to avoid undefined behavior in TYPE_ALIGN + mm/khugepaged: fix collapse_pte_mapped_thp() to allow anon_vma + Linux 5.4.230 + UBUNTU: Upstream stable to v5.4.230 -- 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/2004977 Title: Focal update: v5.4.230 upstream stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: New Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.230 upstream stable release
[Kernel-packages] [Bug 2004977] [NEW] Focal update: v5.4.230 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.230 upstream stable release from git://git.kernel.org/ ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2004977 Title: Focal update: v5.4.230 upstream stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: New Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.230 upstream stable release from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2004977/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1951447] Re: ubuntu_kernel_selftests: net:udpgso_bench.sh failed
** Tags added: patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1951447 Title: ubuntu_kernel_selftests: net:udpgso_bench.sh failed Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Jammy: In Progress Status in linux source package in Kinetic: In Progress Bug description: 04:41:59 DEBUG| [stdout] # selftests: net: udpgso_bench.sh 04:41:59 DEBUG| [stdout] # ipv4 04:41:59 DEBUG| [stdout] # tcp 04:42:00 DEBUG| [stdout] # tcp tx: 2736 MB/s46415 calls/s 46415 msg/s 04:42:00 DEBUG| [stdout] # tcp rx: 2737 MB/s46161 calls/s 04:42:01 DEBUG| [stdout] # tcp tx: 2735 MB/s46392 calls/s 46392 msg/s 04:42:01 DEBUG| [stdout] # tcp rx: 2739 MB/s46226 calls/s 04:42:02 DEBUG| [stdout] # tcp tx: 2717 MB/s46092 calls/s 46092 msg/s 04:42:02 DEBUG| [stdout] # tcp zerocopy 04:42:02 DEBUG| [stdout] # ./udpgso_bench_tx: connect: Connection refused 04:42:54 DEBUG| [stdout] # udpgso_bench.sh: PASS=17 SKIP=0 FAIL=1 04:42:54 DEBUG| [stdout] # udpgso_bench.sh: ^[[0;31mFAIL^[[0m 04:42:54 DEBUG| [stdout] not ok 1 selftests: net: udpgso_bench.sh # exit=1 04:42:54 DEBUG| [stdout] make: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net' 04:42:54 ERROR| Exception escaping from test: Traceback (most recent call last): File "/home/ubuntu/autotest/client/shared/test.py", line 411, in _exec _call_test_function(self.execute, *p_args, **p_dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 823, in _call_test_function return func(*args, **dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 291, in execute postprocess_profiled_run, args, dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 212, in _call_run_once self.run_once(*args, **dargs) File "/home/ubuntu/autotest/client/tests/ubuntu_kernel_selftests/ubuntu_kernel_selftests.py", line 252, in run_once raise error.TestError(test_name + ' failed.') TestError: net:udpgso_bench.sh failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1951447/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1951447] Re: ubuntu_kernel_selftests: net:udpgso_bench.sh failed
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Kinetic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => In Progress ** Changed in: linux (Ubuntu Focal) Status: New => In Progress ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux (Ubuntu Kinetic) Status: New => In Progress ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Andrei Gherzan (agherzan) ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Andrei Gherzan (agherzan) ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => Andrei Gherzan (agherzan) ** Changed in: linux (Ubuntu Kinetic) Assignee: (unassigned) => Andrei Gherzan (agherzan) -- 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/1951447 Title: ubuntu_kernel_selftests: net:udpgso_bench.sh failed Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Jammy: In Progress Status in linux source package in Kinetic: In Progress Bug description: 04:41:59 DEBUG| [stdout] # selftests: net: udpgso_bench.sh 04:41:59 DEBUG| [stdout] # ipv4 04:41:59 DEBUG| [stdout] # tcp 04:42:00 DEBUG| [stdout] # tcp tx: 2736 MB/s46415 calls/s 46415 msg/s 04:42:00 DEBUG| [stdout] # tcp rx: 2737 MB/s46161 calls/s 04:42:01 DEBUG| [stdout] # tcp tx: 2735 MB/s46392 calls/s 46392 msg/s 04:42:01 DEBUG| [stdout] # tcp rx: 2739 MB/s46226 calls/s 04:42:02 DEBUG| [stdout] # tcp tx: 2717 MB/s46092 calls/s 46092 msg/s 04:42:02 DEBUG| [stdout] # tcp zerocopy 04:42:02 DEBUG| [stdout] # ./udpgso_bench_tx: connect: Connection refused 04:42:54 DEBUG| [stdout] # udpgso_bench.sh: PASS=17 SKIP=0 FAIL=1 04:42:54 DEBUG| [stdout] # udpgso_bench.sh: ^[[0;31mFAIL^[[0m 04:42:54 DEBUG| [stdout] not ok 1 selftests: net: udpgso_bench.sh # exit=1 04:42:54 DEBUG| [stdout] make: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net' 04:42:54 ERROR| Exception escaping from test: Traceback (most recent call last): File "/home/ubuntu/autotest/client/shared/test.py", line 411, in _exec _call_test_function(self.execute, *p_args, **p_dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 823, in _call_test_function return func(*args, **dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 291, in execute postprocess_profiled_run, args, dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 212, in _call_run_once self.run_once(*args, **dargs) File "/home/ubuntu/autotest/client/tests/ubuntu_kernel_selftests/ubuntu_kernel_selftests.py", line 252, in run_once raise error.TestError(test_name + ' failed.') TestError: net:udpgso_bench.sh failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1951447/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2004807] Re: RDMA Back port DMA buffer fix
Patch submitted: https://lists.ubuntu.com/archives/kernel-
team/2023-February/136811.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/2004807
Title:
RDMA Back port DMA buffer fix
Status in linux-aws package in Ubuntu:
Fix Released
Status in linux-aws source package in Focal:
In Progress
Status in linux-aws source package in Jammy:
In Progress
Status in linux-aws source package in Kinetic:
In Progress
Bug description:
SRU Justification
[Impact]
When registering a new DMA MR after selecting the best aligned page size
for it, we iterate over the given sglist to split each entry to smaller,
aligned to the selected page size, DMA blocks.
In given circumstances where the sg entry and page size fit certain
sizes and the sg entry is not aligned to the selected page size, the
total size of the aligned pages we need to cover the sg entry is >= 4GB.
Under this circumstances, while iterating page aligned blocks, the
counter responsible for counting how much we advanced from the start of
the sg entry is overflowed because its type is u32 and we pass 4GB in
size. This can lead to an infinite loop inside the iterator function
because the overflow prevents the counter to be larger
than the size of the sg entry.
Fixes: a808273 ("RDMA/verbs: Add a DMA iterator to return aligned
contiguous memory blocks")
[Test Plan]
AWS tested
[Where things could go wrong]
What could possibly go wrong with Remote DMA scatter/gather list
errors ?
[Other Info]
SF: #00353710
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2004807/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2004807] Re: RDMA Back port DMA buffer fix
** Package changed: linux (Ubuntu) => linux-aws (Ubuntu)
** Changed in: linux-aws (Ubuntu)
Status: Incomplete => New
** Also affects: linux-aws (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux-aws (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: linux-aws (Ubuntu Kinetic)
Importance: Undecided
Status: New
** Changed in: linux-aws (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: linux-aws (Ubuntu Focal)
Status: New => In Progress
** Changed in: linux-aws (Ubuntu Focal)
Assignee: (unassigned) => Tim Gardner (timg-tpi)
** Changed in: linux-aws (Ubuntu Jammy)
Importance: Undecided => Medium
** Changed in: linux-aws (Ubuntu Jammy)
Status: New => In Progress
** Changed in: linux-aws (Ubuntu Jammy)
Assignee: (unassigned) => Tim Gardner (timg-tpi)
** Changed in: linux-aws (Ubuntu Kinetic)
Importance: Undecided => Medium
** Changed in: linux-aws (Ubuntu Kinetic)
Status: New => In Progress
** Changed in: linux-aws (Ubuntu Kinetic)
Assignee: (unassigned) => Tim Gardner (timg-tpi)
** Changed in: linux-aws (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/2004807
Title:
RDMA Back port DMA buffer fix
Status in linux-aws package in Ubuntu:
Fix Released
Status in linux-aws source package in Focal:
In Progress
Status in linux-aws source package in Jammy:
In Progress
Status in linux-aws source package in Kinetic:
In Progress
Bug description:
SRU Justification
[Impact]
When registering a new DMA MR after selecting the best aligned page size
for it, we iterate over the given sglist to split each entry to smaller,
aligned to the selected page size, DMA blocks.
In given circumstances where the sg entry and page size fit certain
sizes and the sg entry is not aligned to the selected page size, the
total size of the aligned pages we need to cover the sg entry is >= 4GB.
Under this circumstances, while iterating page aligned blocks, the
counter responsible for counting how much we advanced from the start of
the sg entry is overflowed because its type is u32 and we pass 4GB in
size. This can lead to an infinite loop inside the iterator function
because the overflow prevents the counter to be larger
than the size of the sg entry.
Fixes: a808273 ("RDMA/verbs: Add a DMA iterator to return aligned
contiguous memory blocks")
[Test Plan]
AWS tested
[Where things could go wrong]
What could possibly go wrong with Remote DMA scatter/gather list
errors ?
[Other Info]
SF: #00353710
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2004807/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2004807] 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 2004807
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/2004807
Title:
RDMA Back port DMA buffer fix
Status in linux-aws package in Ubuntu:
Fix Released
Status in linux-aws source package in Focal:
In Progress
Status in linux-aws source package in Jammy:
In Progress
Status in linux-aws source package in Kinetic:
In Progress
Bug description:
SRU Justification
[Impact]
When registering a new DMA MR after selecting the best aligned page size
for it, we iterate over the given sglist to split each entry to smaller,
aligned to the selected page size, DMA blocks.
In given circumstances where the sg entry and page size fit certain
sizes and the sg entry is not aligned to the selected page size, the
total size of the aligned pages we need to cover the sg entry is >= 4GB.
Under this circumstances, while iterating page aligned blocks, the
counter responsible for counting how much we advanced from the start of
the sg entry is overflowed because its type is u32 and we pass 4GB in
size. This can lead to an infinite loop inside the iterator function
because the overflow prevents the counter to be larger
than the size of the sg entry.
Fixes: a808273 ("RDMA/verbs: Add a DMA iterator to return aligned
contiguous memory blocks")
[Test Plan]
AWS tested
[Where things could go wrong]
What could possibly go wrong with Remote DMA scatter/gather list
errors ?
[Other Info]
SF: #00353710
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2004807/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2004807] [NEW] RDMA Back port DMA buffer fix
Public bug reported:
SRU Justification
[Impact]
When registering a new DMA MR after selecting the best aligned page size
for it, we iterate over the given sglist to split each entry to smaller,
aligned to the selected page size, DMA blocks.
In given circumstances where the sg entry and page size fit certain
sizes and the sg entry is not aligned to the selected page size, the
total size of the aligned pages we need to cover the sg entry is >= 4GB.
Under this circumstances, while iterating page aligned blocks, the
counter responsible for counting how much we advanced from the start of
the sg entry is overflowed because its type is u32 and we pass 4GB in
size. This can lead to an infinite loop inside the iterator function
because the overflow prevents the counter to be larger
than the size of the sg entry.
Fixes: a808273 ("RDMA/verbs: Add a DMA iterator to return aligned
contiguous memory blocks")
[Test Plan]
AWS tested
[Where things could go wrong]
What could possibly go wrong with Remote DMA scatter/gather list errors
?
[Other Info]
SF: #00353710
** Affects: linux-aws (Ubuntu)
Importance: Undecided
Status: Fix Released
** Affects: linux-aws (Ubuntu Focal)
Importance: Medium
Assignee: Tim Gardner (timg-tpi)
Status: In Progress
** Affects: linux-aws (Ubuntu Jammy)
Importance: Medium
Assignee: Tim Gardner (timg-tpi)
Status: In Progress
** Affects: linux-aws (Ubuntu Kinetic)
Importance: Medium
Assignee: Tim Gardner (timg-tpi)
Status: In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2004807
Title:
RDMA Back port DMA buffer fix
Status in linux-aws package in Ubuntu:
Fix Released
Status in linux-aws source package in Focal:
In Progress
Status in linux-aws source package in Jammy:
In Progress
Status in linux-aws source package in Kinetic:
In Progress
Bug description:
SRU Justification
[Impact]
When registering a new DMA MR after selecting the best aligned page size
for it, we iterate over the given sglist to split each entry to smaller,
aligned to the selected page size, DMA blocks.
In given circumstances where the sg entry and page size fit certain
sizes and the sg entry is not aligned to the selected page size, the
total size of the aligned pages we need to cover the sg entry is >= 4GB.
Under this circumstances, while iterating page aligned blocks, the
counter responsible for counting how much we advanced from the start of
the sg entry is overflowed because its type is u32 and we pass 4GB in
size. This can lead to an infinite loop inside the iterator function
because the overflow prevents the counter to be larger
than the size of the sg entry.
Fixes: a808273 ("RDMA/verbs: Add a DMA iterator to return aligned
contiguous memory blocks")
[Test Plan]
AWS tested
[Where things could go wrong]
What could possibly go wrong with Remote DMA scatter/gather list
errors ?
[Other Info]
SF: #00353710
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2004807/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2004613] Re: Intel UHD Graphics 770 (ADL-S GT1) max res 1920x1080, should be 4K
Hi, thanks for the reply. My existing cable claimed to be 4K HDMI 2.0, but in the interest of troubleshooting, I ordered and received a new HDMI Cable: "iBirdie 8K HDMI 2.1 Cable 6 Feet 8K60hz 4K120hz 4K144hz HDCP 2.3 2.2 eARC ARC 48Gbps Ultra High Speed" This has not resolved the issue. I have successfully used 4K with other OSes on this display. Here is the display spec: https://www.tcl.com/us/en/products/home- theater/4-series/tcl-75-class-4-series-4k-uhd-led-roku-smart-tv-75s425 I manually forced the HDMI input on the display to use HDMI 2.0 (It was set to Auto). This required a reboot, and again, no luck setting a 4K resolution automatically or by setting the modeline with Xrandr. -- 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/2004613 Title: Intel UHD Graphics 770 (ADL-S GT1) max res 1920x1080, should be 4K Status in linux package in Ubuntu: Incomplete Bug description: This GPU should be capable of 4K resolution, but it's unavailable. Tried manually adding modeline with xrandr --newmode "3840x2160_60.00" 712.75 3840 4160 4576 5312 2160 2163 2168 2237 -hsync +vsync xrandr --addmode HDMI-3 "3840x2160_60.00" Still fails to set 4K resolution. Upgraded to signed kernel 5.19.0-28-generic #29~22.04.1-Ubuntu, added linux-modules-extra, ensured that system is loading i915 kernel module. inxi -G Graphics: Device-1: Intel driver: i915 v: kernel Display: x11 server: X.Org v: 1.21.1.3 driver: X: loaded: modesetting unloaded: fbdev,vesa gpu: i915 resolution: 1920x1080~60Hz OpenGL: renderer: Mesa Intel UHD Graphics 770 (ADL-S GT1) v: 4.6 Mesa 22.0.5 lspci -k | head -10 00:00.0 Host bridge: Intel Corporation Device 4650 (rev 05) Subsystem: Dell Device 0ac5 00:02.0 VGA compatible controller: Intel Corporation Device 4690 (rev 0c) Subsystem: Dell Device 0ac5 Kernel driver in use: i915 Kernel modules: i915 xrandr Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 16384 x 16384 DP-1 disconnected (normal left inverted right x axis y axis) HDMI-1 disconnected (normal left inverted right x axis y axis) DP-2 disconnected (normal left inverted right x axis y axis) HDMI-2 disconnected (normal left inverted right x axis y axis) HDMI-3 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 800mm x 450mm 1920x1080 60.00* 59.9430.0024.0029.9723.98 1920x1080i60.0059.94 1680x1050 59.88 1280x1024 75.0260.02 1440x900 59.90 1280x960 60.00 1360x768 60.02 1280x800 59.91 1152x864 75.00 1280x720 60.0030.0059.9429.9724.0023.98 1024x768 75.0370.0760.00 800x600 72.1975.0060.32 720x480 60.0059.94 720x480i 60.0059.94 640x480 75.0072.8160.0059.94 720x400 70.08 3840x2160_60.00 59.98 # <--- manually configured xrandr --output HDMI-3 --mode 3840x2160_60.00 xrandr: Configure crtc 0 failed ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-28.29~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: KDE Date: Thu Feb 2 22:00:36 2023 DistUpgraded: 2023-01-28 19:49:57,594 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Device [8086:4690] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0ac5] InstallationDate: Installed on 2020-07-18 (929 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 002: ID 0480:0110 Toshiba America Inc External USB 3.0 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0489:e0c8 Foxconn / Hon Hai Wireless_Device Bus 001 Device 002: ID 248a:8367 Maxxter Telink Wireless Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. OptiPlex 3000 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-28-generic root=/dev/mapper/vgkubuntu-root ro nosplash SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2023-01-29 (5 days ago) dmi.bios.date: 05/18/2022 dmi.bios.release: 1.1 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.60 dmi.board.name: 057FFP dmi.board.vendor: Dell Inc. dmi.board.version: A00
[Kernel-packages] [Bug 1999731] Re: disk stress test failing with code 7
I managed to corner the bug, the termination signal on timeout was
killing the contention process with SIGKILL and this was killing the
bogo-op increment mid increment causing the internal state to be
inconsistent on the bogo-op counter. I've pushed a fix to the main repo:
commit efb0ad344e735986b29e0e1d68454edf9d793ee4 (HEAD -> master)
Author: Colin Ian King
Date: Fri Feb 3 17:36:09 2023 +
stress-lock{a|f|ofd}: terminate contention process with SIGALRM
This will be included in the next stress-ng release at the end of this month.
--
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/1999731
Title:
disk stress test failing with code 7
Status in Stress-ng:
In Progress
Status in linux package in Ubuntu:
In Progress
Status in stress-ng package in Ubuntu:
In Progress
Bug description:
Since mid of November we see lots of disk stress test failing with
multiple Ubuntu kernel e.g. bionic-hwe, focal, focal-hwe. Most of them
are with lockofd stressor and system are still alive after stress
test.
05 Nov 08:51: Running stress-ng lockofd stressor for 240 seconds...
** stress-ng exited with code 7
To manage notifications about this bug go to:
https://bugs.launchpad.net/stress-ng/+bug/1999731/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-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
** Also affects: linux-bluefield (Ubuntu Jammy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/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: New 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 2004087] Re: Azure: Fix TDX backport
** Changed in: linux-azure (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-azure in Ubuntu. https://bugs.launchpad.net/bugs/2004087 Title: Azure: Fix TDX backport Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Kinetic: Fix Committed Bug description: SRU Justification [Impact] A backport caused by a stable updates rebase was not performed correctly. The symptom is a failure to boot on TDX enabled hypervisors. [Fix] Make sure the sources match those of 'https://github.com/dcui/tdx.git decui/upstream-kinetic-22.10/master-next/1209'. [Test Plan] Boot on a TDX enabled hypervisor. Tested by Gauthier Jolly. [Where things could go wrong] This is a new feature isolated to TDX, so there is little chance of regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2004087/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2003390] Re: [23.04 FEAT] Improve PCI Logging
Thanks for sharing the details (commits). Investigations show that they were all upstream accepted in kernel 5.19. With that they are already included in the Ubuntu kernel Ubuntu-5.19.0-10.10, means it is already in lunar, but also already in kinetic. Closing this ticket for kinetic and lunar as 'Fix Released'. ** Also affects: linux (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Lunar) Importance: High Assignee: Skipper Bug Screeners (skipper-screen-team) Status: Incomplete ** Changed in: linux (Ubuntu Kinetic) Importance: Undecided => High ** Changed in: linux (Ubuntu Lunar) Status: Incomplete => Fix Released ** Changed in: linux (Ubuntu Kinetic) Status: New => Fix Released ** Changed in: ubuntu-z-systems Status: Incomplete => Fix Released ** Information type changed from Private to Public -- 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/2003390 Title: [23.04 FEAT] Improve PCI Logging Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux source package in Lunar: Fix Released Bug description: Insufficient or ambiguous logging messages in the platform-specific PCI support layer makes it unnecessarily hard to service client issues. This feature should improve the logging to a point where it is easier to provide a substantial level of support based on logs as collected by dbginfo.sh. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2003390/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
** Description changed: SRU Justification: [Impact] - This change is needed to for eMMC host setting on BlueField-3 SoC to be consistent with UEFI setting and also for stability reason. + This change is needed so the sdhci-of-dwcmshc driver can be loaded automatically when built ad kernel module. [Fix] - This fix adds the missing device table IDs for acpi + add the missing device table IDs for acpi [Test Case] - Same functionality as on BlueField-1/2. + Build sdhci-of-dwcmshc as kernel module, use modinfo command to make sure the output contains 'acpi*:MLNXBF30:*'. [Regression Potential] - Can be considered minimum since similar functionality was already included in the focal branch for BlueField-1/2. The driver is different, but functionality and eMMC device files will be the same. + No changes to driver funtionality. -- 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 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 2004645] Re: mmc: sdhci-of-dwcmshc: add the missing device table IDs for acpi
** Description changed: SRU Justification: [Impact] This change is needed to for eMMC host setting on BlueField-3 SoC to be consistent with UEFI setting and also for stability reason. [Fix] - The fix calls sdhci_enable_v4_mode() for BlueField-3 SoC. + This fix adds the missing device table IDs for acpi [Test Case] Same functionality as on BlueField-1/2. [Regression Potential] Can be considered minimum since similar functionality was already included in the focal branch for BlueField-1/2. The driver is different, but functionality and eMMC device files will be the same. -- 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 Bug description: SRU Justification: [Impact] This change is needed to for eMMC host setting on BlueField-3 SoC to be consistent with UEFI setting and also for stability reason. [Fix] This fix adds the missing device table IDs for acpi [Test Case] Same functionality as on BlueField-1/2. [Regression Potential] Can be considered minimum since similar functionality was already included in the focal branch for BlueField-1/2. The driver is different, but functionality and eMMC device files will be the same. 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 2004645] [NEW] mmc: sdhci-of-dwcmshc: add the missing device table IDs for acpi
Public bug reported: SRU Justification: [Impact] This change is needed to for eMMC host setting on BlueField-3 SoC to be consistent with UEFI setting and also for stability reason. [Fix] This fix adds the missing device table IDs for acpi [Test Case] Same functionality as on BlueField-1/2. [Regression Potential] Can be considered minimum since similar functionality was already included in the focal branch for BlueField-1/2. The driver is different, but functionality and eMMC device files will be the same. ** Affects: linux-bluefield (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2004645 Title: mmc: sdhci-of-dwcmshc: add the missing device table IDs for acpi Status in linux-bluefield package in Ubuntu: New Bug description: SRU Justification: [Impact] This change is needed to for eMMC host setting on BlueField-3 SoC to be consistent with UEFI setting and also for stability reason. [Fix] This fix adds the missing device table IDs for acpi [Test Case] Same functionality as on BlueField-1/2. [Regression Potential] Can be considered minimum since similar functionality was already included in the focal branch for BlueField-1/2. The driver is different, but functionality and eMMC device files will be the same. 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 2002842] Re: UBSAN: array-index-out-of-bounds in drivers/scsi/megaraid/megaraid_sas_fp.c:151:32
Problem: This bug is also being reporting on my Lenovo x3650 Server, so adding here to confirm multiple occurrence/ Ubuntu Version: $ cat /etc/*release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=22.04 DISTRIB_CODENAME=jammy DISTRIB_DESCRIPTION="Ubuntu 22.04.1 LTS" PRETTY_NAME="Ubuntu 22.04.1 LTS" NAME="Ubuntu" VERSION_ID="22.04" VERSION="22.04.1 LTS (Jammy Jellyfish)" VERSION_CODENAME=jammy ID=ubuntu ID_LIKE=debian HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; UBUNTU_CODENAME=jammy kernel version: $ uname -a Linux blue 5.15.0-58-generic #64-Ubuntu SMP Thu Jan 5 11:43:13 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux [4.607349] UBSAN: array-index-out-of-bounds in /build/linux-oKJrrr/linux-5.15.0/drivers/scsi/megaraid/megaraid_sas_fp.c:103:32 [4.607725] index 5 is out of range for type 'MR_LD_SPAN_MAP [1]' [4.607925] CPU: 0 PID: 402 Comm: kworker/0:2 Not tainted 5.15.0-58-generic #64-Ubuntu [4.607930] Hardware name: LENOVO System x3650 M5: -[8871AC1]-/01KN179, BIOS -[TCE148A-3.30]- 10/26/2020 [4.607932] Workqueue: events work_for_cpu_fn [4.607944] Call Trace: [4.607948] [4.607950] show_stack+0x52/0x5c [4.607958] dump_stack_lvl+0x4a/0x63 [4.607968] dump_stack+0x10/0x16 [4.607972] ubsan_epilogue+0x9/0x49 [4.607977] __ubsan_handle_out_of_bounds.cold+0x44/0x49 [4.607982] ? MR_PopulateDrvRaidMap+0x295/0x580 [megaraid_sas] [4.608002] mr_update_load_balance_params+0xb9/0xc0 [megaraid_sas] [4.608014] MR_ValidateMapInfo+0x8d/0x290 [megaraid_sas] [4.608025] megasas_init_adapter_fusion+0x3ce/0x420 [megaraid_sas] [4.608036] ? megasas_setup_reply_map+0x49/0xac [megaraid_sas] [4.608050] megasas_init_fw.cold+0x87f/0x10c8 [megaraid_sas] [4.608064] megasas_probe_one+0x15c/0x4e0 [megaraid_sas] [4.608075] local_pci_probe+0x4b/0x90 [4.608081] work_for_cpu_fn+0x1a/0x30 [4.608085] process_one_work+0x22b/0x3d0 [4.608089] worker_thread+0x223/0x420 [4.608092] ? process_one_work+0x3d0/0x3d0 [4.608095] kthread+0x12a/0x150 [4.608099] ? set_kthread_struct+0x50/0x50 [4.608103] ret_from_fork+0x22/0x30 [4.608110] [4.608111] [4.608385] [4.608655] UBSAN: array-index-out-of-bounds in /build/linux-oKJrrr/linux-5.15.0/drivers/scsi/megaraid/megaraid_sas_fp.c:103:32 [4.609031] index 5 is out of range for type 'MR_LD_SPAN_MAP [1]' [4.609230] CPU: 0 PID: 402 Comm: kworker/0:2 Not tainted 5.15.0-58-generic #64-Ubuntu [4.609233] Hardware name: LENOVO System x3650 M5: -[8871AC1]-/01KN179, BIOS -[TCE148A-3.30]- 10/26/2020 [4.609234] Workqueue: events work_for_cpu_fn [4.609239] Call Trace: [4.609240] [4.609241] show_stack+0x52/0x5c [4.609244] dump_stack_lvl+0x4a/0x63 [4.609249] dump_stack+0x10/0x16 [4.609253] ubsan_epilogue+0x9/0x49 [4.609257] __ubsan_handle_out_of_bounds.cold+0x44/0x49 [4.609262] ? mr_update_load_balance_params+0xb9/0xc0 [megaraid_sas] [4.609274] MR_ValidateMapInfo+0x20f/0x290 [megaraid_sas] [4.609285] megasas_init_adapter_fusion+0x3ce/0x420 [megaraid_sas] [4.609295] ? megasas_setup_reply_map+0x49/0xac [megaraid_sas] [4.609309] megasas_init_fw.cold+0x87f/0x10c8 [megaraid_sas] [4.609322] megasas_probe_one+0x15c/0x4e0 [megaraid_sas] [4.609333] local_pci_probe+0x4b/0x90 [4.609336] work_for_cpu_fn+0x1a/0x30 [4.609340] process_one_work+0x22b/0x3d0 [4.609343] worker_thread+0x223/0x420 [4.609346] ? process_one_work+0x3d0/0x3d0 [4.609349] kthread+0x12a/0x150 [4.609352] ? set_kthread_struct+0x50/0x50 [4.609356] ret_from_fork+0x22/0x30 [4.609361] Also report on kernel.org bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=215943 ** Bug watch added: Linux Kernel Bug Tracker #215943 https://bugzilla.kernel.org/show_bug.cgi?id=215943 -- 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/2002842 Title: UBSAN: array-index-out-of-bounds in drivers/scsi/megaraid/megaraid_sas_fp.c:151:32 Status in linux package in Ubuntu: Confirmed Bug description: I'm getting UBSAN complains every boot, this issue exists for years, but I was lazy to report it as everything works. However, not sure if it is security issue: [1.866789] [1.866992] [1.867187] UBSAN: array-index-out-of-bounds in /build/linux-oKJrrr/linux-5.15.0/drivers/scsi/megaraid/megaraid_sas_fp.c:151:32 [
[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
** Changed in: linux-hwe-5.15 (Ubuntu)
Status: New => Invalid
** Changed in: linux-hwe-5.15 (Ubuntu Focal)
Status: New => Invalid
--
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:
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
