[Kernel-packages] [Bug 1959867] [NEW] nvidia-kernel-source-460 460.73.01-0ubuntu0.20.04.1: nvidia kernel module failed to build
Public bug reported: not sure? ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-kernel-source-460 460.73.01-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.13.0-28-generic Date: Thu Feb 3 07:36:53 2022 Dependencies: DuplicateSignature: dkms:nvidia-kernel-source-460:460.73.01-0ubuntu0.20.04.1:/var/lib/dkms/nvidia/460.73.01/build/nvidia-drm/nvidia-drm-crtc.c:311:23: error: initialization of ‘int (*)(struct drm_plane *, struct drm_atomic_state *)’ from incompatible pointer type ‘int (*)(struct drm_plane *, struct drm_plane_state *)’ [-Werror=incompatible-pointer-types] InstallationDate: Installed on 2021-03-18 (321 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageVersion: 460.73.01-0ubuntu0.20.04.1 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: nvidia-graphics-drivers-460 Title: nvidia-kernel-source-460 460.73.01-0ubuntu0.20.04.1: nvidia kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-460 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1959867 Title: nvidia-kernel-source-460 460.73.01-0ubuntu0.20.04.1: nvidia kernel module failed to build Status in nvidia-graphics-drivers-460 package in Ubuntu: New Bug description: not sure? ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-kernel-source-460 460.73.01-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.13.0-28-generic Date: Thu Feb 3 07:36:53 2022 Dependencies: DuplicateSignature: dkms:nvidia-kernel-source-460:460.73.01-0ubuntu0.20.04.1:/var/lib/dkms/nvidia/460.73.01/build/nvidia-drm/nvidia-drm-crtc.c:311:23: error: initialization of ‘int (*)(struct drm_plane *, struct drm_atomic_state *)’ from incompatible pointer type ‘int (*)(struct drm_plane *, struct drm_plane_state *)’ [-Werror=incompatible-pointer-types] InstallationDate: Installed on 2021-03-18 (321 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageVersion: 460.73.01-0ubuntu0.20.04.1 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: nvidia-graphics-drivers-460 Title: nvidia-kernel-source-460 460.73.01-0ubuntu0.20.04.1: nvidia kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460/+bug/1959867/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1949106] Re: HP hotkeys does not work.
** Changed in: linux (Ubuntu) Status: Confirmed => New ** Description changed: - HP hotkeys does not work at all on HP 15-da1071ne laptop. Brightness - keys returns the same scancode, airplane mode returns nothing at all, - closing the lid toggles airplane mode. + Some HP hotkeys does not work at all on HP 15-da1071ne laptop. + Brightness keys returns the same scancode, airplane mode returns nothing + at all, closing the lid toggles airplane mode. Using evtest: Available devices: /dev/input/event0:Lid Switch /dev/input/event1:Power Button /dev/input/event2:Power Button /dev/input/event3:AT Translated Set 2 keyboard /dev/input/event4:SynPS/2 Synaptics TouchPad /dev/input/event5:Video Bus /dev/input/event6:Video Bus /dev/input/event7:HP Wireless hotkeys /dev/input/event8:HP TrueVision HD Camera: HP Tru /dev/input/event9:HDA Intel PCH Mic /dev/input/event10: HDA Intel PCH Headphone /dev/input/event11: HDA Intel PCH HDMI/DP,pcm=3 /dev/input/event12: HDA Intel PCH HDMI/DP,pcm=7 /dev/input/event13: HDA Intel PCH HDMI/DP,pcm=8 /dev/input/event14: HDA Intel PCH HDMI/DP,pcm=9 /dev/input/event15: HDA Intel PCH HDMI/DP,pcm=10 /dev/input/event16: HP WMI hotkeys Testing event 16 (HP WMI hotkeys): No output for the mentioned keys. Testing event 3 (AT Translated Set 2 keyboard): #Brightness up/down yield the following (both the same): Event: time 1630657967.702964, type 4 (EV_MSC), code 4 (MSC_SCAN), value ab Event: time 1630657967.702964, -- SYN_REPORT #Closing the lid then reopening it yields the following: Event: time 1630658208.483290, type 4 (EV_MSC), code 4 (MSC_SCAN), value 9c Event: time 1630658208.483290, type 1 (EV_KEY), code 96 (KEY_KPENTER), value 0 Event: time 1630658208.483290, -- SYN_REPORT Event: time 1630658211.288732, type 4 (EV_MSC), code 4 (MSC_SCAN), value d8 Event: time 1630658211.288732, -- SYN_REPORT Event: time 1630658211.298740, type 4 (EV_MSC), code 4 (MSC_SCAN), value d8 Event: time 1630658211.298740, -- SYN_REPORT Event: time 1630658212.041279, type 4 (EV_MSC), code 4 (MSC_SCAN), value d7 Event: time 1630658212.041279, type 1 (EV_KEY), code 238 (KEY_WLAN), value 1 Event: time 1630658212.041279, -- SYN_REPORT Event: time 1630658212.051527, type 4 (EV_MSC), code 4 (MSC_SCAN), value d7 Event: time 1630658212.051527, type 1 (EV_KEY), code 238 (KEY_WLAN), value 0 Event: time 1630658212.051527, -- SYN_REPORT Event: time 1630658212.058783, type 4 (EV_MSC), code 4 (MSC_SCAN), value e3 Event: time 1630658212.058783, type 1 (EV_KEY), code 143 (KEY_WAKEUP), value 1 Event: time 1630658212.058783, -- SYN_REPORT Event: time 1630658212.069128, type 4 (EV_MSC), code 4 (MSC_SCAN), value e3 Event: time 1630658212.069128, type 1 (EV_KEY), code 143 (KEY_WAKEUP), value 0 Event: time 1630658212.069128, -- SYN_REPORT Check the dmesg attached. If anything else is needed I will provide it. This bug has been occurring since at least kernel 5.4 on various Ubuntu based distros, and still happens on kernel 5.13 - --- + --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.3 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: ahmad 2384 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: ahmad 2384 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: pop:GNOME DistroRelease: Pop!_OS 21.04 Lsusb: - Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub - Bus 001 Device 002: ID 04f2:b65d Chicony Electronics Co., Ltd HP TrueVision HD Camera - Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 002: ID 04f2:b65d Chicony Electronics Co., Ltd HP TrueVision HD Camera + 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/6p, 1M - /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M - |__ Port 5: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M - |__ Port 5: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M + /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 1M + /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M + |__ Port 5: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M + |__ Port 5: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M MachineType: HP HP Laptop 15-da1xxx Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: initrd=\EFI\Pop_OS-37d4cd8c-cd5e-47f5-83e1-f04caf17536d\initrd.img root=UUID=37d4cd8c-cd5e-47f5-83e1-f04caf17536d ro quiet loglevel=0
[Kernel-packages] [Bug 1959665] Re: linux-image-5.4.0-97.110 freezes by accessing cifs shares
Hi Tim, thanks for your afford! Best regards, Kai. -- 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/1959665 Title: linux-image-5.4.0-97.110 freezes by accessing cifs shares Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: In Progress Bug description: Ubuntu 20.04 with kernel image 5.4.0-97.110 randomly freezes when we access cifs shares. The system needs a hard reset after the freeze. The previous kernel image (5.4.0-96.109) does not show this behavior. Multiple Ubuntu 20.04 systems running on kernel image 9.4.0-97.110 are affected on our sites. The cifs shares are accessed via autofs using Kerberos authentication. The following info is the only error message we could actively catch on a different system before the system was frozen: general protection fault: [#3] SMP PTI CPU: 0 PID: 21294 Comm: automount Tainted: G DOE 5.4.0-97-generic #110-Ubuntu Hardware name: Dell Inc. Precision 7530/03RV2M, BIOS 1.14.4 10/21/2020 RIP: 0010:kmem_cache_alloc_trace+0x8c/0x240 Code: 08 65 4c 03 05 1d e8 f7 6e 49 83 78 10 00 4d 8b 38 0f 84 92 01 00 00 4d 85 ff 0f 84 89 01 00 00 41 8b 41 20 49 8b 39 4c 01 f8 <48> 8b 18 48 89 c1 49 33 99 70 01 00 00 4c 89 f8 48 0f c9 48 31 cb RSP: 0018:a6ca860f7ba0 EFLAGS: 00010286 RAX: fdd44d7c219190e1 RBX: RCX: RDX: d558 RSI: 0cc0 RDI: 00035060 RBP: a6ca860f7bd0 R08: 99233c035060 R09: 992338c079c0 R10: 0001 R11: 0004 R12: 0cc0 R13: 000b R14: 992338c079c0 R15: fdd44d7c219190e1 FS: 7fdc24e29700() GS:99233c00() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 7f15a80ee010 CR3: 0007e36b2006 CR4: 003606f0 Call Trace: ? proc_self_get_link+0x70/0xd0 proc_self_get_link+0x70/0xd0 link_path_walk.part.0+0x478/0x550 ? trailing_symlink+0x1d1/0x280 path_openat+0xb7/0x290 do_filp_open+0x91/0x100 ? unuse_pde+0x30/0x30 do_sys_open+0x17e/0x290 __x64_sys_openat+0x20/0x30 __orig_openat+0x71/0xc0 [eset_rtp] ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __x64_sys_futex+0x13f/0x170 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 __x64_sys_ertp_openat+0x29/0x60 [eset_rtp] do_syscall_64+0x57/0x190 entry_SYSCALL_64_after_hwframe+0x44/0xa9 RIP: 0033:0x7fdc28a41f24 Code: 24 20 eb 8f 66 90 44 89 54 24 0c e8 56 68 f8 ff 44 8b 54 24 0c 44 89 e2 48 89 ee 41 89 c0 bf 9c ff ff ff b8 01 01 00 00 0f 05 <48> 3d 00 f0 ff ff 77 32 44 89 c7 89 44 24 0c e8 88 68 f8 ff 8b 44 RSP: 002b:7fdc24e25980 EFLAGS: 0293 ORIG_RAX: 0101 RAX: ffda RBX: 7fdc040008d0 RCX: 7fdc28a41f24 ? unuse_pde+0x30/0x30 do_sys_open+0x17e/0x290 __x64_sys_openat+0x20/0x30 __orig_openat+0x71/0xc0 [eset_rtp] ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __x64_sys_futex+0x13f/0x170 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 __x64_sys_ertp_openat+0x29/0x60 [eset_rtp] do_syscall_64+0x57/0x190 entry_SYSCALL_64_after_hwframe+0x44/0xa9 RIP: 0033:0x7fdc28a41f24 Code: 24 20 eb 8f 66 90 44 89 54 24 0c e8 56 68 f8 ff 44 8b 54 24 0c 44 89 e2 48 89 ee 41 89 c0 bf 9c ff ff ff b8 01 01 00 00 0f 05 <48> 3d 00 f0 ff ff 77 32 44 89 c7 89 44 24 0c e8 88 68 f8 ff 8b 44 RSP: 002b:7fdc24e25980 EFLAGS: 0293 ORIG_RAX: 0101 RAX: ffda RBX: 7fdc040008d0 RCX: 7fdc28a41f24 RDX: 0008 RSI: 564d4410a8c8 RDI: ff9c RBP: 564d4410a8c8 R08: R09: 0001 R10: R11: 0293 R12: 0008 R13: 564d4410e28a R14: 7fdc24e25b40 R15: 7fdc24e28fc0 Modules linked in: cmac nls_utf8 cifs fscache libdes ccm vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) eset_rtp(OE) xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype iptable_filter iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ip> snd_seq_midi coretemp snd_seq_midi_event snd_rawmidi kvm_intel snd_seq kvm dell_wmi snd_seq_device rapl dell_smbios snd_timer dcdbas intel_cstate input_leds iwlwifi serio_raw snd intel_wmi_thunderbolt rtsx_pci_ms dell_wmi_descriptor wmi_bmof processor_thermal_device ucsi_acp> pinctrl_cannonlake video pinctrl_intel ---[ end trace 80828f22da45a19b ]--- RIP: 0010:__slab_free+0x199/0x360 Code: 00 48 89 c7 fa 66 0f 1f 44 00 00 f0 49 0f ba 2c 24 00 72 79 4d 3b 6c 24 20 74 11 49 0f ba 34 24 00 57 9d 0f 1f 44 00 00 eb 9f <0f> 0b 49 3b 5c
[Kernel-packages] [Bug 1226855] Re: Cannot use open-iscsi inside LXC container
Closing the LXC side of this bug as there's nothing we can really do here. It's either a kernel issue (needs support for their socket option within a network namespace) or an open-iscsi issue where they could have some kind of fallback mechanism. ** Changed in: lxc (Ubuntu) Status: Confirmed => Invalid -- 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/1226855 Title: Cannot use open-iscsi inside LXC container Status in linux package in Ubuntu: Confirmed Status in lxc package in Ubuntu: Invalid Bug description: Trying to use open-iscsi from within an LXC container, but the iscsi netlink socket does not support multiple namespaces, causing: "iscsid: sendmsg: bug? ctrl_fd 6" error and failure. Command attempted: iscsiadm -m node -p $ip:$port -T $target --login Results in: Exit code: 18 Stdout: 'Logging in to [iface: default, target: $target, portal: $ip,$port] (multiple)' Stderr: 'iscsiadm: got read error (0/0), daemon died? iscsiadm: Could not login to [iface: default, target: $target, portal: $ip,$port]. iscsiadm: initiator reported error (18 - could not communicate to iscsid) iscsiadm: Could not log into all portals' ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: lxc 0.9.0-0ubuntu3.4 ProcVersionSignature: Ubuntu 3.8.0-30.44-generic 3.8.13.6 Uname: Linux 3.8.0-30-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 Date: Tue Sep 17 14:38:08 2013 InstallationDate: Installed on 2013-01-15 (245 days ago) InstallationMedia: Xubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) MarkForUpload: True SourcePackage: lxc UpgradeStatus: Upgraded to raring on 2013-05-16 (124 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1226855/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1642767] Re: starting any container with umask 007 breaks host system shutdown. lxc-stop just hangs.
Moving over to the kernel as a userspace process shouldn't be able to cause such a hang regardless of what it does so this looks like a kernel bug (lock related by the looks of it). ** Package changed: lxc (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/1642767 Title: starting any container with umask 007 breaks host system shutdown. lxc-stop just hangs. Status in linux package in Ubuntu: Confirmed Bug description: If I have umask 007 (or any other value that masks the world-execute bit) when I run lxc-start for the first time after logging in, my host system enters a state with the following problems: * lxc-stop hangs forever instead of stopping any container, even one that wasn't started with umask 007. * lxc-stop --kill --nolock hangs in the same way. * Attempts to reboot or shut down the host system fail, requiring a hard reset to recover. When lxc-stop hangs, messages like these appear in syslog every couple of minutes: Nov 17 01:22:11 hostbox kernel: [ 3360.091624] INFO: task systemd:12179 blocked for more than 120 seconds. Nov 17 01:22:11 hostbox kernel: [ 3360.091629] Tainted: P OE 4.4.0-47-generic #68-Ubuntu Nov 17 01:22:11 hostbox kernel: [ 3360.091631] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Nov 17 01:22:11 hostbox kernel: [ 3360.091633] systemd D 8800c6febb58 0 12179 12168 0x0104 Nov 17 01:22:11 hostbox kernel: [ 3360.091638] 8800c6febb58 8800d318d280 88040c649b80 8800d318d280 Nov 17 01:22:11 hostbox kernel: [ 3360.091641] 8800c6fec000 8800345bc088 8800345bc070 Nov 17 01:22:11 hostbox kernel: [ 3360.091644] fffe0001 8800c6febb70 81830f15 8800d318d280 Nov 17 01:22:11 hostbox kernel: [ 3360.091647] Call Trace: Nov 17 01:22:11 hostbox kernel: [ 3360.091653] [] schedule+0x35/0x80 Nov 17 01:22:11 hostbox kernel: [ 3360.091657] [] rwsem_down_write_failed+0x202/0x350 Nov 17 01:22:11 hostbox kernel: [ 3360.091662] [] ? kernfs_sop_show_options+0x40/0x40 Nov 17 01:22:11 hostbox kernel: [ 3360.091666] [] call_rwsem_down_write_failed+0x13/0x20 Nov 17 01:22:11 hostbox kernel: [ 3360.091669] [] ? down_write+0x2d/0x40 Nov 17 01:22:11 hostbox kernel: [ 3360.091672] [] grab_super+0x30/0xa0 Nov 17 01:22:11 hostbox kernel: [ 3360.091674] [] sget_userns+0x152/0x450 Nov 17 01:22:11 hostbox kernel: [ 3360.091677] [] ? kernfs_sop_show_path+0x50/0x50 Nov 17 01:22:11 hostbox kernel: [ 3360.091680] [] kernfs_mount_ns+0x7e/0x230 Nov 17 01:22:11 hostbox kernel: [ 3360.091685] [] cgroup_mount+0x2eb/0x7f0 Nov 17 01:22:11 hostbox kernel: [ 3360.091687] [] mount_fs+0x38/0x160 Nov 17 01:22:11 hostbox kernel: [ 3360.091691] [] vfs_kern_mount+0x67/0x110 Nov 17 01:22:11 hostbox kernel: [ 3360.091694] [] do_mount+0x269/0xde0 Nov 17 01:22:11 hostbox kernel: [ 3360.091698] [] SyS_mount+0x9f/0x100 Nov 17 01:22:11 hostbox kernel: [ 3360.091701] [] entry_SYSCALL_64_fastpath+0x16/0x71 When system shutdown hangs, similar messages appear on the console every couple of minutes. I can reproduce this at will with a freshly-installed and fully- updated host OS in VirtualBox, and with either an old-ish container or a new one. I'm running lxc 2.0.5-0ubuntu1~ubuntu16.04.2 on xubuntu 16.04.1 LTS amd64. My containers are all unprivileged. My umask at container creation time does not seem to matter. As far as I have seen, my umask only matters the first time I start a container in my login session. I can work around the bug by manually setting my umask to something more permissive before I start my first container of the day, and then setting it back again, but that's rather a hassle. (Even worse, it's very easy to forget this workaround and be left with containers that can't be stopped and a host system that won't shut down cleanly.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1642767/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1642767] [NEW] starting any container with umask 007 breaks host system shutdown. lxc-stop just hangs.
You have been subscribed to a public bug: If I have umask 007 (or any other value that masks the world-execute bit) when I run lxc-start for the first time after logging in, my host system enters a state with the following problems: * lxc-stop hangs forever instead of stopping any container, even one that wasn't started with umask 007. * lxc-stop --kill --nolock hangs in the same way. * Attempts to reboot or shut down the host system fail, requiring a hard reset to recover. When lxc-stop hangs, messages like these appear in syslog every couple of minutes: Nov 17 01:22:11 hostbox kernel: [ 3360.091624] INFO: task systemd:12179 blocked for more than 120 seconds. Nov 17 01:22:11 hostbox kernel: [ 3360.091629] Tainted: P OE 4.4.0-47-generic #68-Ubuntu Nov 17 01:22:11 hostbox kernel: [ 3360.091631] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Nov 17 01:22:11 hostbox kernel: [ 3360.091633] systemd D 8800c6febb58 0 12179 12168 0x0104 Nov 17 01:22:11 hostbox kernel: [ 3360.091638] 8800c6febb58 8800d318d280 88040c649b80 8800d318d280 Nov 17 01:22:11 hostbox kernel: [ 3360.091641] 8800c6fec000 8800345bc088 8800345bc070 Nov 17 01:22:11 hostbox kernel: [ 3360.091644] fffe0001 8800c6febb70 81830f15 8800d318d280 Nov 17 01:22:11 hostbox kernel: [ 3360.091647] Call Trace: Nov 17 01:22:11 hostbox kernel: [ 3360.091653] [] schedule+0x35/0x80 Nov 17 01:22:11 hostbox kernel: [ 3360.091657] [] rwsem_down_write_failed+0x202/0x350 Nov 17 01:22:11 hostbox kernel: [ 3360.091662] [] ? kernfs_sop_show_options+0x40/0x40 Nov 17 01:22:11 hostbox kernel: [ 3360.091666] [] call_rwsem_down_write_failed+0x13/0x20 Nov 17 01:22:11 hostbox kernel: [ 3360.091669] [] ? down_write+0x2d/0x40 Nov 17 01:22:11 hostbox kernel: [ 3360.091672] [] grab_super+0x30/0xa0 Nov 17 01:22:11 hostbox kernel: [ 3360.091674] [] sget_userns+0x152/0x450 Nov 17 01:22:11 hostbox kernel: [ 3360.091677] [] ? kernfs_sop_show_path+0x50/0x50 Nov 17 01:22:11 hostbox kernel: [ 3360.091680] [] kernfs_mount_ns+0x7e/0x230 Nov 17 01:22:11 hostbox kernel: [ 3360.091685] [] cgroup_mount+0x2eb/0x7f0 Nov 17 01:22:11 hostbox kernel: [ 3360.091687] [] mount_fs+0x38/0x160 Nov 17 01:22:11 hostbox kernel: [ 3360.091691] [] vfs_kern_mount+0x67/0x110 Nov 17 01:22:11 hostbox kernel: [ 3360.091694] [] do_mount+0x269/0xde0 Nov 17 01:22:11 hostbox kernel: [ 3360.091698] [] SyS_mount+0x9f/0x100 Nov 17 01:22:11 hostbox kernel: [ 3360.091701] [] entry_SYSCALL_64_fastpath+0x16/0x71 When system shutdown hangs, similar messages appear on the console every couple of minutes. I can reproduce this at will with a freshly-installed and fully-updated host OS in VirtualBox, and with either an old-ish container or a new one. I'm running lxc 2.0.5-0ubuntu1~ubuntu16.04.2 on xubuntu 16.04.1 LTS amd64. My containers are all unprivileged. My umask at container creation time does not seem to matter. As far as I have seen, my umask only matters the first time I start a container in my login session. I can work around the bug by manually setting my umask to something more permissive before I start my first container of the day, and then setting it back again, but that's rather a hassle. (Even worse, it's very easy to forget this workaround and be left with containers that can't be stopped and a host system that won't shut down cleanly.) ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed -- starting any container with umask 007 breaks host system shutdown. lxc-stop just hangs. https://bugs.launchpad.net/bugs/1642767 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 1953022] Re: refcount leak in pep_sock_accept
It looks like I lost track of this browser tab a lot longer than I
expected.
Thanks Hangyu Hua for the fixes! :)
** Information type changed from Private Security to Public Security
--
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/1953022
Title:
refcount leak in pep_sock_accept
Status in linux package in Ubuntu:
New
Bug description:
sock_hold(sk) is invoked in pep_sock_accept(),but __sock_put() is not
invoked in subsequent failure branches(pep_accept_conn() != 0).
static struct sock *pep_sock_accept(struct sock *sk, int flags, int *errp,
bool kern)
{
struct pep_sock *pn = pep_sk(sk), *newpn;
struct sock *newsk = NULL;
struct sk_buff *skb;
struct pnpipehdr *hdr;
struct sockaddr_pn dst, src;
int err;
u16 peer_type;
u8 pipe_handle, enabled, n_sb;
u8 aligned = 0;
...
newsk = sk_alloc(sock_net(sk), PF_PHONET, GFP_KERNEL, sk->sk_prot,
kern);
if (!newsk) {
pep_reject_conn(sk, skb, PN_PIPE_ERR_OVERLOAD, GFP_KERNEL);
err = -ENOBUFS;
goto drop;
}
...
sock_hold(sk);< here,sk->sk_refcnt++
newpn->listener = sk;
skb_queue_head_init(>ctrlreq_queue);
newpn->pipe_handle = pipe_handle;
atomic_set(>tx_credits, 0);
newpn->ifindex = 0;
newpn->peer_type = peer_type;
newpn->rx_credits = 0;
newpn->rx_fc = newpn->tx_fc = PN_LEGACY_FLOW_CONTROL;
newpn->init_enable = enabled;
newpn->aligned = aligned;
err = pep_accept_conn(newsk, skb);
if (err) {
sock_put(newsk);< before sock_put(newsk) may need
sk->sk_refcnt--
newsk = NULL;
goto drop;
}
sk_add_node(newsk, >hlist);
drop:
release_sock(sk);
kfree_skb(skb);
*errp = err;
return newsk;
}
My suggestion for the patch:
static struct sock *pep_sock_accept(struct sock *sk, int flags, int *errp,
bool kern)
{
...
err = pep_accept_conn(newsk, skb);
if (err) {
+++ __sock_put(sk);
sock_put(newsk);
newsk = NULL;
goto drop;
}
sk_add_node(newsk, >hlist);
drop:
release_sock(sk);
kfree_skb(skb);
*errp = err;
return newsk;
}
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953022/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-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.11/5.11.0.60.61)
All autopkgtests for the newly accepted linux-meta-hwe-5.11 (5.11.0.60.61) for focal have finished running. The following regressions have been reported in tests triggered by the package: lxc/1:4.0.6-0ubuntu1~20.04.1 (arm64, amd64) nvidia-graphics-drivers-340/340.108-0ubuntu5.20.04.2 (amd64) systemd/245.4-4ubuntu3.15 (arm64, s390x, ppc64el, 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.11 [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 1950720] Re: GSYNC bug regression in 495.44 Ubuntu 21.10
Something new (2 hours old) for you to try: https://launchpad.net/ubuntu/+source/nvidia-graphics-drivers-510 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1950720 Title: GSYNC bug regression in 495.44 Ubuntu 21.10 Status in nvidia-graphics-drivers-470 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-495 package in Ubuntu: Confirmed Bug description: [ Description ] Video of signal loss with flipping enabled: https://youtu.be/V5DGcHN- BJs In NVIDIA the 495 driver for Ubuntu 21.10, with G-SYNC enabled in OpenGL Settings of NVIDIA Settings, the G-SYNC compatible monitor loses sync momentarily (1~2 seconds) when switching to GPU accelerated application. Examples of this are: - When launching a game full-screen - Launching a GPU accelerated game in Window mode - Launching Steam - Launching kitty terminal https://sw.kovidgoyal.net/kitty/ This issue happens at all refresh rates: 60 Hz, 120 Hz, 144 Hz and 165 Hz. Note: This example doesn't explicitly show G-SYNC being enabled in the onscreen indicator, rather what happens when G-SYNC is enabled in the settings. If I disable G-SYNC, but leave flipping enabled, the issue is not present. If I enabled G-SYNC, but disable flipping, the issue is not present. If both are enabled, then the issue occurs. [ Hardware ] - NVIDIA GeForce RTX 2080 Super - Dell 27" S2721DGF G-Sync Compatible monitor - High quality DisplayPort cable [ Settings ] In the NVIDIA OpenGL settings, the following settings are enabled: - Sync to VBlank Enabled - Allow Flipping Enabled - Image Setting: High Performance - Allow G-SYNC-/G-SYNC Compatible Enabled - Use Conformant Texture Clamping Enabled [ Observations ] When I disable Allow Flipping, the issue goes away. No signal is lost when changing to different GPU accelerated applications. Sometimes there is a brief flicker when opening a GPU accelerated program with flipping disabled, but it's not a signal loss, rather a very fast momentary flick of the display, but it's does not impact usability. As flipping is required for G-SYNC to function, therefore losing the benefit of G-SYNC if I were to disable flipping. [ Correlation to previous bug ] This issue was present in Ubuntu 21.04, eventually driver 495.44 resolved this problem on the 5.14.1 kernel. I will add that when I first had this machine and screen in 20.10 and 21.04, it was not experiencing the signal loss issue. The bug described in the change log in this launchpad bug seems to reference the type of regression I am experiencing https://launchpad.net/bugs/1950665. [ Troubleshooting ] Full driver purges between trying different drivers: - Tried downgrading to 470.82 - Went back to the standard kernel for 21.10 (5.13.0-21-generic) at the time - Tried deleting ~/.nv, ~/.cache/nvidia - Reverted to previous X11 conf - Tried 5.14.1 which was working in Ubuntu 21.04 - Tried kernels 5.14.17, 5.15.6 - Persists in 470.94 (NVIDIA bundle and Graphics Drivers PPA) - Persists in 495.46 (NVIDIA bundle and Graphics Drivers PPA) - Persists in 510.39.01 (NVIDIA bundle) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1950720/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1959752] Re: ubuntu_kernel_selftests.ftrace:ftracetest fails with bionic:linux 4.15.0-168.176 on s390x
** Description changed:
- All ftrace tests from selftests are failing with bionic:linux
- 4.15.0-168.176 on s390x:
+ SRU Justification
+
+ [Impact]
+
+ There seems to have been a typo in Commit 85bf17b28f97
+ ("recordmcount.pl: look for jgnop instruction as well as bcrl on s390")
+ that causes errors in finding mcount locations. This seems to cause problems
with ftrace initialization leading to not being able to use ftrace
+ functions.
+
+ [Fix]
+
+ Fix the typo by changing it to the correct instruction.
+
+ [Test Case]
+
+ Ftrace files in /sys/kernel/debug/tracing should be able to be read from
+ and written to with normal functionality. Ftrace selftests should now
+ pass.
+
+ [Where things could go wrong]
+
+ Its a simple typo fix so none really.
+
+ ---
+ All ftrace tests from selftests are failing with bionic:linux 4.15.0-168.176
on s390x:
https://autopkgtest.ubuntu.com/results/autopkgtest-
bionic/bionic/s390x/l/linux/20220201_190955_5689e@/log.gz
==
selftests: ftracetest
=== Ftrace unit tests ===
[1] Basic trace file check[FAIL]
[2] Basic test for tracers[FAIL]
[3] Basic trace clock test[FAIL]
[4] Basic event tracing check [FAIL]
[5] Snapshot and tracing setting [FAIL]
[6] event tracing - enable/disable with event level files [FAIL]
[7] event tracing - restricts events based on pid [FAIL]
[8] event tracing - enable/disable with subsystem level files [FAIL]
[9] event tracing - enable/disable with top level files [FAIL]
[10] ftrace - function graph filters with stack tracer[FAIL]
[11] ftrace - function graph filters [FAIL]
[12] ftrace - function pid filters[FAIL]
[13] ftrace - test for function event triggers[FAIL]
[14] ftrace - function profiler with function tracing [FAIL]
[15] ftrace - test reading of set_ftrace_filter [FAIL]
[16] ftrace - test for function traceon/off triggers [FAIL]
[17] Test creation and deletion of trace instances while setting an event
[FAIL]
[18] Test creation and deletion of trace instances[FAIL]
[19] Kprobe dynamic event - adding and removing [FAIL]
[20] Kprobe dynamic event - busy event check [FAIL]
[21] Kprobe dynamic event with arguments [FAIL]
[22] Kprobe event string type argument[FAIL]
[23] Kprobe event argument syntax [FAIL]
[24] Kprobes event arguments with types [FAIL]
[25] Kprobe event auto/manual naming [FAIL]
[26] Kprobe dynamic event with function tracer[FAIL]
[27] Kretprobe dynamic event with arguments [FAIL]
[28] Kretprobe dynamic event with maxactive [FAIL]
[29] Register/unregister many kprobe events [FAIL]
[30] event trigger - test multiple actions on hist trigger[FAIL]
[31] event trigger - test synthetic_events syntax parser [FAIL]
[32] event trigger - test event enable/disable trigger[FAIL]
[33] event trigger - test trigger filter [FAIL]
[34] event trigger - test histogram modifiers [FAIL]
[35] event trigger - test multiple histogram triggers [FAIL]
[36] event trigger - test snapshot-trigger[FAIL]
[37] event trigger - test stacktrace-trigger [FAIL]
[38] event trigger - test traceon/off trigger [FAIL]
[39] (instance) Basic test for tracers [FAIL]
[40] (instance) Basic trace clock test [FAIL]
[41] (instance) Snapshot and tracing setting [FAIL]
[42] (instance) event tracing - enable/disable with event level files
[FAIL]
[43] (instance) event tracing - restricts events based on pid[FAIL]
[44] (instance) event tracing - enable/disable with subsystem level files
[FAIL]
[45] (instance) ftrace - test for function event triggers[FAIL]
[46] (instance) ftrace - test for function traceon/off triggers [FAIL]
[47] (instance) event trigger - test event enable/disable trigger[FAIL]
[48] (instance) event trigger - test trigger filter [FAIL]
[49] (instance) event trigger - test histogram modifiers [FAIL]
[50] (instance) event trigger - test multiple histogram triggers [FAIL]
# of passed: 0
# of failed: 50
# of unresolved: 0
# of untested: 0
# of unsupported: 0
# of xfailed: 0
# of undefined(test bug): 0
not ok 1..1 selftests: ftracetest [FAIL]
==
After some debugging I've found out that the testcases are not actually
run, the failure happens while running
'tools/testing/selftests/ftrace/test.d/functions:initialize_ftrace()',
on the following line:
[ -f set_ftrace_filter ] && echo | tee set_ftrace_*
After a reboot for clean ftrace state, with kernel 4.15.0-168-generic:
root@kleber-bionic:/sys/kernel/debug/tracing# head set_ftrace_*
head: cannot open
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-gcp/5.13.0.1014.13)
All autopkgtests for the newly accepted linux-meta-gcp (5.13.0.1014.13) for impish have finished running. The following regressions have been reported in tests triggered by the package: systemd/248.3-1ubuntu8.2 (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/impish/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 1910927] Re: Suspend stopped working since kernel 5.4 (ubuntu 20.04)
Ah, I see the report refers to a Core Duo processor and that is what the T61p has too (Intel T7700 to be precise). -- 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/1910927 Title: Suspend stopped working since kernel 5.4 (ubuntu 20.04) Status in linux package in Ubuntu: Confirmed Bug description: Suspend was working on ubuntu 18.04 with kernel 4.15.0-128. After upgrade to ubuntu 20.04, suspend is not working. The device is on black screen, fully powered and not responding any longer. I can still boot the old kernel 4.15.0-128 from ubuntu 18.04, suspend is working with this kernel! I tested kernel 5.4.0-60 and 5.8.0-36 from hwe. With both kernels, suspend is broken on my older device with Core2Duo. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: xubuntu4020 F pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.445 CurrentDesktop: XFCE DistroRelease: Ubuntu 20.04 LiveMediaBuild: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: SAMSUNG ELECTRONICS CO., LTD. R510/P510 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: file=/cdrom/preseed/username.seed initrd=/casper/initrd quiet splash --- maybe-ubiquity ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-26-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: 04/01/2010 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 10LI.M008.20100401.KSJ dmi.board.name: R510/P510 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr10LI.M008.20100401.KSJ:bd04/01/2010:svnSAMSUNGELECTRONICSCO.,LTD.:pnR510/P510:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR510/P510:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A: dmi.product.name: R510/P510 dmi.product.version: Not Applicable dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910927/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910927] Re: Suspend stopped working since kernel 5.4 (ubuntu 20.04)
Recently I installed Ubuntu 20.04.3 LTS on an old Lenovo laptop (T61p). I was disappointed to discover that suspend did not work (as described in this report, black screen and no way to recover). I tried two version 5 kernels (5.13.0-27-generic and 5.8.0-43-generic). As a wild guess I downloaded 4.19.0-041900-generic and suspend works for me with that kernel. I would prefer to run a newer kernel but I need suspend. -- 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/1910927 Title: Suspend stopped working since kernel 5.4 (ubuntu 20.04) Status in linux package in Ubuntu: Confirmed Bug description: Suspend was working on ubuntu 18.04 with kernel 4.15.0-128. After upgrade to ubuntu 20.04, suspend is not working. The device is on black screen, fully powered and not responding any longer. I can still boot the old kernel 4.15.0-128 from ubuntu 18.04, suspend is working with this kernel! I tested kernel 5.4.0-60 and 5.8.0-36 from hwe. With both kernels, suspend is broken on my older device with Core2Duo. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: xubuntu4020 F pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.445 CurrentDesktop: XFCE DistroRelease: Ubuntu 20.04 LiveMediaBuild: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: SAMSUNG ELECTRONICS CO., LTD. R510/P510 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: file=/cdrom/preseed/username.seed initrd=/casper/initrd quiet splash --- maybe-ubiquity ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-26-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: 04/01/2010 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 10LI.M008.20100401.KSJ dmi.board.name: R510/P510 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr10LI.M008.20100401.KSJ:bd04/01/2010:svnSAMSUNGELECTRONICSCO.,LTD.:pnR510/P510:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR510/P510:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A: dmi.product.name: R510/P510 dmi.product.version: Not Applicable dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910927/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945590] Re: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled
yes, great we finally got there. thumbs up.
works on my e15 gen 2 amd.
--
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/1945590
Title:
Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Impish:
Fix Released
Status in linux source package in Jammy:
Fix Released
Bug description:
[Impact]
On some thinkpads we may get a kernel panic at boot, because the
elantech driver (trakcpad) can trigger out-of-bounds access in the
stack.
[Test case]
Simply boot the kernel on one of the affected systems (e.g., Thinkpad
E14 Gen2).
[Fix]
Prevent the stack out of bound access by applying the following
upstream commit (from linux-next):
1d72d9f960cc ("Input: elantech - fix stack out of bound access in
elantech_change_report_id()")
[Regression potential]
The fix is touching the elantech driver, so we could only see
regressions with this specific trackpad/mouse driver.
[Original bug report]
I installed the Ubuntu 21.10 beta and as soon as I boot I get the
kernel panic that I am attaching.
I also installed Ubuntu 21.04 and upgraded, as soon as I boot with the
5.13 kernel I get the same problem, disabling the trackpad and
trackpoint in the bios the problem disappears.
Everything works with the 5.11 kernel.
I remain available for further details and sorry for my lack of experience.
ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: linux-image-5.13.0-16-generic 5.13.0-16.16
ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
Uname: Linux 5.13.0-16-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu69
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: pietro 1810 F pulseaudio
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Sep 30 10:26:10 2021
InstallationDate: Installed on 2021-09-29 (0 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
MachineType: LENOVO 20TA0033IX
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=it_IT.UTF-8
SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-16-generic
root=UUID=b5ea9465-4cd9-408b-8e30-458acf90181b ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-5.13.0-16-generic N/A
linux-backports-modules-5.13.0-16-generic N/A
linux-firmware 1.201
SourcePackage: linux
UpgradeStatus: Upgraded to impish on 2021-09-29 (0 days ago)
dmi.bios.date: 09/02/2021
dmi.bios.release: 1.43
dmi.bios.vendor: LENOVO
dmi.bios.version: R1EET43W(1.43 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20TA0033IX
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.43
dmi.modalias:
dmi:bvnLENOVO:bvrR1EET43W(1.43):bd09/02/2021:br1.43:efr1.43:svnLENOVO:pn20TA0033IX:pvrThinkPadE14Gen2:skuLENOVO_MT_20TA_BU_Think_FM_ThinkPadE14Gen2:rvnLENOVO:rn20TA0033IX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad E14 Gen 2
dmi.product.name: 20TA0033IX
dmi.product.sku: LENOVO_MT_20TA_BU_Think_FM_ThinkPad E14 Gen 2
dmi.product.version: ThinkPad E14 Gen 2
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945590/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1959852] [NEW] Touchpad isn't working
Public bug reported: I installed ubuntu on my pc, and since then my touchpad is not working. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-28-generic 5.13.0-28.31~20.04.1 ProcVersionSignature: User Name 5.13.0-28.31~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Feb 3 02:39:56 2022 InstallationDate: Installed on 2022-02-02 (0 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.13 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "devices" https://bugs.launchpad.net/bugs/1959852/+attachment/5558792/+files/devices -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1959852 Title: Touchpad isn't working Status in linux-signed-hwe-5.13 package in Ubuntu: New Bug description: I installed ubuntu on my pc, and since then my touchpad is not working. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-28-generic 5.13.0-28.31~20.04.1 ProcVersionSignature: User Name 5.13.0-28.31~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Feb 3 02:39:56 2022 InstallationDate: Installed on 2022-02-02 (0 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1959852/+subscriptions -- Mailing list: https://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 1958289] Re: computer does not shut down completely after the 5.13 kernel automatic updating
Thank you! After yesterday's updates my computer can shutdown correctly, Antonio On Tue, Jan 18, 2022 at 3:30 PM Ubuntu Foundations Team Bug Bot < 1958...@bugs.launchpad.net> wrote: > Thank you for taking the time to report this bug and helping to make > Ubuntu better. It seems that your bug report is not filed about a > specific source package though, rather it is just filed against Ubuntu > in general. It is important that bug reports be filed about source > packages so that people interested in the package can find the bugs > about it. You can find some hints about determining what package your > bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. > You might also ask for help in the #ubuntu-bugs irc channel on Freenode. > > To change the source package that this bug is filed about visit > https://bugs.launchpad.net/ubuntu/+bug/1958289/+editstatus and add the > package name in the text box next to the word Package. > > [This is an automated message. I apologize if it reached you > inappropriately; please just reply to this message indicating so.] > > ** Tags added: bot-comment > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1958289 > > Title: > computer does not shut down completely after the 5.13 kernel > automatic updating > > Status in linux package in Ubuntu: > New > > Bug description: > dell inspiron 7415 2in1 > os 20.04.3lts > gnome 3.36.8 > x11 > > message on black screen > > [ 38.407808] systemd-shutdown [1]: Waiting for process: systemd-udevd, > systemd-udevd > [ 63.708267] systemd-udevd [381]: :03:00.7: Worker [412] processing > SEQNUM=3413 is taking a long time > [ 141.099020] atkbd serio0: Unknown key pressed (translated set 2, code > 0x67 on isa0060/seri00). > [ 141.099110] atkbd serio0: Use 'setkeycodes 67 to make it > known. > [ 141.103874) atkbd serio0: Unknown key released (translated set 2, code > 0x67 on isa0060/seri00). > [ 141.103964] atkbd serio0: Use 'setkeycodes 67 ' to make it > known. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958289/+subscriptions > > -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1958289 Title: [amdgpu] Hang on shutdown: systemd-udevd ... Worker ... processing SEQNUM=... is taking a long time Status in linux-hwe-5.13 package in Ubuntu: Confirmed Bug description: dell inspiron 7415 2in1 os 20.04.3lts gnome 3.36.8 x11 message on black screen [ 38.407808] systemd-shutdown [1]: Waiting for process: systemd-udevd, systemd-udevd [ 63.708267] systemd-udevd [381]: :03:00.7: Worker [412] processing SEQNUM=3413 is taking a long time [ 141.099020] atkbd serio0: Unknown key pressed (translated set 2, code 0x67 on isa0060/seri00). [ 141.099110] atkbd serio0: Use 'setkeycodes 67 to make it known. [ 141.103874) atkbd serio0: Unknown key released (translated set 2, code 0x67 on isa0060/seri00). [ 141.103964] atkbd serio0: Use 'setkeycodes 67 ' to make it known. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: antonio1800 F pulseaudio /dev/snd/controlC0: antonio1800 F pulseaudio /dev/snd/controlC2: antonio1800 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2022-01-06 (12 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: Dell Inc. Inspiron 7415 2-in-1 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-25-generic root=UUID=95fe2347-727f-4d0c-8559-24cb9ae1d39f ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-25.26~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-25-generic N/A linux-backports-modules-5.13.0-25-generic N/A linux-firmware 1.187.25 Tags: focal Uname: Linux 5.13.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/04/2021 dmi.bios.release: 1.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.0 dmi.board.name: 09X2G7 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.6.0 dmi.modalias:
[Kernel-packages] [Bug 1927808] Re: rtw88_8821ce causes freeze
Sorry Mr Launchpad Janitor, you are mistaken. This bug is NOT FIXED in impish 5.13.0-28.31 ... my laptop proves you wrong! -- 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/1927808 Title: rtw88_8821ce causes freeze Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Impish: Fix Released Status in linux-oem-5.13 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Status in linux source package in Jammy: Confirmed Status in linux-oem-5.13 source package in Jammy: Invalid Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: My laptop (Ollee L116HTN6SPW) has a Realtek 8821CE WiFi card. Now at hirsute, this is "supported" in the linux-image-5.11.0-16-generic kernel,and it works "well" for both WiFi and Bluetooth. However, this module (driver) causes frequent freezes, randomly but usually within a few minutes of running (thus very soon after boot): screen display remains frozen, no response to either keyboard or mouse input. All I can do is to hold the power button to power off, then reboot. After reboot, I do not see any crash reports, nor logs about the freeze. Please let me know if I should try to collect some info, and how. For now I use the DKMS module/driver from https://github.com/tomaspinho/rtl8821ce (having blacklisted rtw88_8821ce), and it seems to work perfectly. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-16-generic 5.11.0-16.17 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: psz1189 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat May 8 16:58:19 2021 InstallationDate: Installed on 2021-04-23 (14 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 058f:5608 Alcor Micro Corp. USB 2.0 Camera Bus 001 Device 003: ID 0bda:c821 Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Protempo Ltd L116HTN6SPW ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=f3700d1b-be99-4cb7-baef-c0f157487c64 ro quiet splash pci=noaer vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/26/2020 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: YHSM-BI-11.6-X116AR300-AA55C-195-A dmi.board.asset.tag: Default string dmi.board.name: Default string dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.ec.firmware.release: 1.6 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrYHSM-BI-11.6-X116AR300-AA55C-195-A:bd05/26/2020:br5.12:efr1.6:svnProtempoLtd:pnL116HTN6SPW:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring: dmi.product.family: Notebook dmi.product.name: L116HTN6SPW dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Protempo Ltd To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1927808/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859592] Re: Bluetooth unavailable after updates - Reading Intel version information failed (-110)
Power cable unplug as comment #2 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859592/comments/2 did the trick -- 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/1859592 Title: Bluetooth unavailable after updates - Reading Intel version information failed (-110) Status in linux package in Ubuntu: Confirmed Bug description: After 10 days of uptime with automatic updates, I rebooted. Bluetooth, which I use every day, is no longer available. $ dmesg | grep -i bluetooth [4.846072] Bluetooth: Core ver 2.22 [4.846088] Bluetooth: HCI device and connection manager initialized [4.846092] Bluetooth: HCI socket layer initialized [4.846094] Bluetooth: L2CAP socket layer initialized [4.846096] Bluetooth: SCO socket layer initialized [5.434081] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [5.434082] Bluetooth: BNEP filters: protocol multicast [5.434086] Bluetooth: BNEP socket layer initialized [6.874125] Bluetooth: hci0: command 0xfc05 tx timeout [6.874129] Bluetooth: hci0: Reading Intel version information failed (-110) $ uname -a Linux abu 5.3.2-050302-generic #201910010731 SMP Tue Oct 1 07:33:48 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux AMD Ryzen 5 3400G (Picasso, Raven Ridge) (Asrock A300) Ubuntu 18.04 LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859592/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1959752] Re: ubuntu_kernel_selftests.ftrace:ftracetest fails with bionic:linux 4.15.0-168.176 on s390x
The regression was introduced by the following commit applied to bionic:linux: commit 699bf409d4d2895733d3e2f2eb01166d141650ce Author: Jerome Marchand Date: Fri Dec 10 10:38:27 2021 +0100 recordmcount.pl: look for jgnop instruction as well as bcrl on s390 BugLink: https://bugs.launchpad.net/bugs/1957957 commit 85bf17b28f97ca2749968d8786dc423db320d9c2 upstream. -- 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/1959752 Title: ubuntu_kernel_selftests.ftrace:ftracetest fails with bionic:linux 4.15.0-168.176 on s390x Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: All ftrace tests from selftests are failing with bionic:linux 4.15.0-168.176 on s390x: https://autopkgtest.ubuntu.com/results/autopkgtest- bionic/bionic/s390x/l/linux/20220201_190955_5689e@/log.gz == selftests: ftracetest === Ftrace unit tests === [1] Basic trace file check[FAIL] [2] Basic test for tracers[FAIL] [3] Basic trace clock test[FAIL] [4] Basic event tracing check [FAIL] [5] Snapshot and tracing setting [FAIL] [6] event tracing - enable/disable with event level files [FAIL] [7] event tracing - restricts events based on pid [FAIL] [8] event tracing - enable/disable with subsystem level files [FAIL] [9] event tracing - enable/disable with top level files [FAIL] [10] ftrace - function graph filters with stack tracer[FAIL] [11] ftrace - function graph filters [FAIL] [12] ftrace - function pid filters[FAIL] [13] ftrace - test for function event triggers[FAIL] [14] ftrace - function profiler with function tracing [FAIL] [15] ftrace - test reading of set_ftrace_filter [FAIL] [16] ftrace - test for function traceon/off triggers [FAIL] [17] Test creation and deletion of trace instances while setting an event [FAIL] [18] Test creation and deletion of trace instances[FAIL] [19] Kprobe dynamic event - adding and removing [FAIL] [20] Kprobe dynamic event - busy event check [FAIL] [21] Kprobe dynamic event with arguments [FAIL] [22] Kprobe event string type argument[FAIL] [23] Kprobe event argument syntax [FAIL] [24] Kprobes event arguments with types [FAIL] [25] Kprobe event auto/manual naming [FAIL] [26] Kprobe dynamic event with function tracer[FAIL] [27] Kretprobe dynamic event with arguments [FAIL] [28] Kretprobe dynamic event with maxactive [FAIL] [29] Register/unregister many kprobe events [FAIL] [30] event trigger - test multiple actions on hist trigger[FAIL] [31] event trigger - test synthetic_events syntax parser [FAIL] [32] event trigger - test event enable/disable trigger[FAIL] [33] event trigger - test trigger filter [FAIL] [34] event trigger - test histogram modifiers [FAIL] [35] event trigger - test multiple histogram triggers [FAIL] [36] event trigger - test snapshot-trigger[FAIL] [37] event trigger - test stacktrace-trigger [FAIL] [38] event trigger - test traceon/off trigger [FAIL] [39] (instance) Basic test for tracers [FAIL] [40] (instance) Basic trace clock test [FAIL] [41] (instance) Snapshot and tracing setting [FAIL] [42] (instance) event tracing - enable/disable with event level files [FAIL] [43] (instance) event tracing - restricts events based on pid[FAIL] [44] (instance) event tracing - enable/disable with subsystem level files [FAIL] [45] (instance) ftrace - test for function event triggers[FAIL] [46] (instance) ftrace - test for function traceon/off triggers [FAIL] [47] (instance) event trigger - test event enable/disable trigger[FAIL] [48] (instance) event trigger - test trigger filter [FAIL] [49] (instance) event trigger - test histogram modifiers [FAIL] [50] (instance) event trigger - test multiple histogram triggers [FAIL] # of passed: 0 # of failed: 50 # of unresolved: 0 # of untested: 0 # of unsupported: 0 # of xfailed: 0 # of undefined(test bug): 0 not ok 1..1 selftests: ftracetest [FAIL] == After some debugging I've found out that the testcases are not actually run, the failure happens while running 'tools/testing/selftests/ftrace/test.d/functions:initialize_ftrace()', on the following line: [ -f set_ftrace_filter ] && echo | tee set_ftrace_* After a reboot for clean ftrace state, with kernel 4.15.0-168-generic: root@kleber-bionic:/sys/kernel/debug/tracing# head set_ftrace_* head: cannot open 'set_ftrace_filter' for reading: No
[Kernel-packages] [Bug 1814003] Re: kernel BUG at fs/ext4/inode.c:2679!
20.04, 5.4.0-96-generic. The bug exists. -- 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/1814003 Title: kernel BUG at fs/ext4/inode.c:2679! Status in linux package in Ubuntu: Confirmed Bug description: I started seeing this bug in Ubuntu 18.04 running VMWare Workstation Pro 14. After upgrading to Ubuntu 18.10 and VMware Workstation 15 the bug still appears. I started to ask questions on the VMware Community, https://communities.vmware.com/thread/604705. Because I had some additional time to troubleshoot I am also noticing that this bug is being reported on other Linux Distributions notably: https://bugzilla.redhat.com/show_bug.cgi?id=1662314 Conditions to reproduce. Laptop is running 2 NVMe drives with Cryptfs on each drive (unsure if this is related). Running Vmware Workstation Pro 15 with a Windows 10 Guest upon shutting down the Windows Guest a kernel stack strace appears in both dmesg -w and /var/log/syslog. The VM does not gracefully stop. Stack Trace is Below: Jan 30 17:10:02 system-box kernel: [13117.565550] [ cut here ] Jan 30 17:10:02 system-box kernel: [13116.565552] kernel BUG at fs/ext4/inode.c:2679! Jan 30 17:10:02 system-box kernel: [13117.565558] invalid opcode: [#1] SMP PTI Jan 30 17:10:02 system-box kernel: [13117.565561] CPU: 0 PID: 18820 Comm: kworker/u8:0 Tainted: GW OE 4.18.0-13-generic #14-Ubuntu Jan 30 17:10:02 system-box kernel: [13117.565562] Hardware name: LENOVO 20HES35Q00/20HES35Q00, BIOS N1QET79W (1.54 ) 11/16/2018 Jan 30 17:10:02 system-box kernel: [13117.565566] Workqueue: writeback wb_workfn (flush-253:3) Jan 30 17:10:02 system-box kernel: [13117.565569] RIP: 0010:mpage_prepare_extent_to_map+0x2bc/0x2f0 Jan 30 17:10:02 system-box kernel: [13117.565570] Code: 86 0a fe ff ff 31 c0 eb a4 4c 89 ef e8 4d b3 e9 ff e9 91 fe ff ff be 0e 00 00 00 4c 89 ef e8 5b bb e9 ff e9 e4 fe ff ff 0f 0b <0f> 0b 48 8d bd 50 ff ff ff 89 85 40 ff ff ff e8 50 1a eb ff 8b 85 Jan 30 17:10:02 system-box kernel: [13117.565589] RSP: 0018:99674b78b930 EFLAGS: 00010246 ...skipping... Jan 30 17:10:02 system-box kernel: [13117.565633] ? ext4_mark_inode_dirty+0x1d0/0x1d0 Jan 30 17:10:02 system-box kernel: [13117.565635] ? do_writepages+0x41/0xd0 Jan 30 17:10:02 system-box kernel: [13117.565638] ? check_preempt_wakeup+0x11f/0x250 Jan 30 17:10:02 system-box kernel: [13117.565641] __writeback_single_inode+0x40/0x360 Jan 30 17:10:02 system-box kernel: [13117.565643] writeback_sb_inodes+0x211/0x520 Jan 30 17:10:02 system-box kernel: [13117.565646] __writeback_inodes_wb+0x67/0xb0 Jan 30 17:10:02 system-box kernel: [13117.565648] wb_writeback+0x25f/0x2f0 Jan 30 17:10:02 system-box kernel: [13117.565651] ? get_nr_dirty_inodes+0x46/0x70 Jan 30 17:10:02 system-box kernel: [13117.565654] wb_workfn+0x32c/0x3f0 Jan 30 17:10:02 system-box kernel: [13117.565656] ? __switch_to_asm+0x34/0x70 Jan 30 17:10:02 system-box kernel: [13117.565660] process_one_work+0x20f/0x3c0 Jan 30 17:10:02 system-box kernel: [13117.565662] worker_thread+0x34/0x400 Jan 30 17:10:02 system-box kernel: [13117.565664] kthread+0x120/0x140 Jan 30 17:10:02 system-box kernel: [13117.565667] ? pwq_unbound_release_workfn+0xd0/0xd0 Jan 30 17:10:02 system-box kernel: [13117.565668] ? kthread_bind+0x40/0x40 Jan 30 17:10:02 system-box kernel: [13117.565670] ret_from_fork+0x35/0x40 Jan 30 17:10:02 system-box kernel: [13117.565671] Modules linked in: nf_conntrack_ipv6 nf_defrag_ipv6 vmnet(OE) parport_pc vmw_vsock_vmci_transport vsock vmw_vmci vmmon(OE) thunderbolt rfcomm veth xt_nat nf_conntrack_netlink nfnetlink xt_addrtype br_netfilter xfrm_user xfrm4_tunnel tunnel4 ipcomp xfrm_ipcomp esp4 ah4 af_key xfrm_algo l2tp_ppp l2tp_netlink l2tp_core ip6_udp_tunnel udp_tunnel pppox msr ccm xt_CHECKSUM iptable_mangle ipt_MASQUERADE iptable_nat nf_nat_ipv4 cmac nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack libcrc32c ipt_REJECT nf_reject_ipv4 xt_tcpudp bridge stp llc devlink pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) ip6table_filter ip6_tables vboxdrv(OE) iptable_filter bpfilter aufs overlay bnep uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common btusb btrtl videodev btbcm Jan 30 17:10:02 system-box kernel: [13117.565701] media btintel bluetooth ecdh_generic binfmt_misc nls_iso8859_1 snd_hda_codec_hdmi snd_soc_skl snd_soc_skl_ipc snd_soc_sst_ipc snd_soc_sst_dsp snd_hda_ext_core snd_hda_codec_realtek snd_soc_acpi snd_hda_codec_generic snd_soc_core snd_compress ac97_bus intel_rapl arc4 snd_pcm_dmaengine x86_pkg_temp_thermal intel_powerclamp snd_seq_midi coretemp snd_hda_intel snd_seq_midi_event snd_hda_codec kvm_intel snd_hda_core snd_hwdep snd_rawmidi kvm
[Kernel-packages] [Bug 1959519] Re: kernel BUG at fs/ext4/inode.c:2633!
Seems the same as #1814003. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1959519 Title: kernel BUG at fs/ext4/inode.c:2633! Status in linux-signed-hwe-5.13 package in Ubuntu: New Bug description: kernel BUG at fs/ext4/inode.c:2633! During heavy use of vmware player. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-27-generic 5.13.0-27.29~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Jan 30 18:51:49 2022 InstallationDate: Installed on 2020-09-30 (486 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1959519/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958854] Re: jammy/linux-raspi: Update to upstream raspberrypi rpi-5.15.y (2022-01-24)
This bug was fixed in the package linux-raspi - 5.15.0-1002.2
---
linux-raspi (5.15.0-1002.2) jammy; urgency=medium
* jammy/linux-raspi: 5.15.0-1002.2 -proposed tracker (LP: #1958834)
* Packaging resync (LP: #1786013)
- [Packaging] update Ubuntu.md
- debian/dkms-versions -- update from kernel-versions (main/master)
* Kernel fails to boot in ScalingStack (LP: #1959102)
- [Config] raspi: Set VIRTIO_PCI=m
- [Config] raspi: Set ACPI=y
* jammy/linux-raspi: Update to upstream raspberrypi rpi-5.15.y (2022-01-24)
(LP: #1958854)
- brcmfmac: firmware: Fix crash in brcm_alt_fw_path
- ARM: dts: Remove VL805 USB node from CM4 dts
- mfd: simple-mfd-i2c: Add configuration for RPi POE HAT
- pwm: raspberrypi-poe: Add option of being created by MFD or FW
- power: rpi-poe: Drop CURRENT_AVG as it is not hardware averaged
- power: rpi-poe: Add option of being created by MFD or FW
- defconfigs: Add MFD_RASPBERRYPI_POE_HAT to Pi defconfigs.
- dtoverlays: Add option for PoE HAT to use Linux I2C instead of FW.
- drivers: bcm2835_unicam: Disable trigger mode operation
- arm: Remove spurious .fnend directive
- drm/vc4: Fix deadlock on DSI device attach error
- drm/vc4: dsi: Correct max divider to 255 (not 7)
- defconfig: Add BACKLIGHT_PWM to bcm2709 and bcmrpi defconfigs
- dtoverlays: Add pwm backlight option to vc4-kms-dpi-generic
- dtoverlays: Correct [h|v]sync_invert config in vc4-kms-dpi-generic
- ARM: dts: BCM2711 AON_INTR2 generates IRQ edges
- update rpi-display-overlay.dts pins for 5.10+
[ Ubuntu: 5.15.0-18.18 ]
* jammy/linux: 5.15.0-18.18 -proposed tracker (LP: #1958638)
* CVE-2021-4155
- xfs: map unwritten blocks in XFS_IOC_{ALLOC, FREE}SP just like fallocate
* CVE-2022-0185
- SAUCE: vfs: test that one given mount param is not larger than PAGE_SIZE
* [UBUNTU 20.04] KVM hardware diagnose data improvements for guest kernel -
kernel part (LP: #1953334)
- KVM: s390: add debug statement for diag 318 CPNC data
* OOB write on BPF_RINGBUF (LP: #1956585)
- SAUCE: bpf: prevent helper argument PTR_TO_ALLOC_MEM to have offset other
than 0
* Miscellaneous Ubuntu changes
- [Config] re-enable shiftfs
- [SAUCE] shiftfs: support kernel 5.15
- [Config] update toolchain versions
* Miscellaneous upstream changes
- vfs: fs_context: fix up param length parsing in legacy_parse_param
linux-raspi (5.15.0-1001.1) jammy; urgency=medium
* Missing overlays/README (LP: #1954757)
- SAUCE: Install overlays/README
* dtoverlay=uart4 breaks Raspberry Pi 4B boot (LP: #1875454)
- SAUCE: arm: dts: Add 'brcm,bcm2835-pl011' compatible for uart2-5
* jammy/linux-raspi: Update to upstream raspberrypi rpi-5.15.y (2022-01-14)
(LP: #1958146)
- clk: bcm-2835: Pick the closest clock rate
- clk: bcm-2835: Remove rounding up the dividers
- drm/vc4: hdmi: Set a default HSM rate
- drm/vc4: hdmi: Move the HSM clock enable to runtime_pm
- drm/vc4: hdmi: Make sure the controller is powered in detect
- drm/vc4: hdmi: Make sure the controller is powered up during bind
- drm/vc4: hdmi: Rework the pre_crtc_configure error handling
- drm/vc4: hdmi: Split the CEC disable / enable functions in two
- drm/vc4: hdmi: Make sure the device is powered with CEC
- drm/vc4: hdmi: Warn if we access the controller while disabled
- drm/vc4: crtc: Make sure the HDMI controller is powered when disabling
- drm/vc4: crtc: Drop feed_txp from state
- drm/vc4: Fix non-blocking commit getting stuck forever
- drm/vc4: crtc: Copy assigned channel to the CRTC
- drm/vc4: hdmi: Add a spinlock to protect register access
- drm/vc4: hdmi: Use a mutex to prevent concurrent framework access
- drm/vc4: hdmi: Prevent access to crtc->state outside of KMS
- drm/vc4: hdmi: Check the device state in prepare()
- drm/vc4: hdmi: Introduce an output_enabled flag
- drm/vc4: hdmi: Introduce a scdc_enabled flag
- drm/vc4: hdmi: Remove the DDC probing for status detection
- drm/vc4: hdmi: Fix HPD GPIO detection
- drm/vc4: Make vc4_crtc_get_encoder public
- drm/vc4: crtc: Add encoder to vc4_crtc_config_pv prototype
- drm/vc4: crtc: Rework the encoder retrieval code (again)
- drm/vc4: crtc: Add some logging
- drm/vc4: Leverage the load tracker on the BCM2711
- drm/vc4: hdmi: Raise the maximum clock rate
- drm/vc4: hdmi: Enable the scrambler on reconnection
- drm/vc4: Increase the core clock based on HVS load
- drm/vc4: select PM
- drm/probe-helper: Create a HPD IRQ event helper for a single connector
- drm/vc4: hdmi: Actually check for the connector status in hotplug
- firmware: raspberrypi: Add RPI_FIRMWARE_NOTIFY_DISPLAY_DONE
- drm/vc4: Remove conflicting framebuffers before callind bind_all
- drm/vc4: Notify the firmware when DRM is in charge
- arm: partially revert
[Kernel-packages] [Bug 1906476] Re: PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, >z_sa_hdl)) failed
This bug was fixed in the package linux-raspi - 5.15.0-1002.2
---
linux-raspi (5.15.0-1002.2) jammy; urgency=medium
* jammy/linux-raspi: 5.15.0-1002.2 -proposed tracker (LP: #1958834)
* Packaging resync (LP: #1786013)
- [Packaging] update Ubuntu.md
- debian/dkms-versions -- update from kernel-versions (main/master)
* Kernel fails to boot in ScalingStack (LP: #1959102)
- [Config] raspi: Set VIRTIO_PCI=m
- [Config] raspi: Set ACPI=y
* jammy/linux-raspi: Update to upstream raspberrypi rpi-5.15.y (2022-01-24)
(LP: #1958854)
- brcmfmac: firmware: Fix crash in brcm_alt_fw_path
- ARM: dts: Remove VL805 USB node from CM4 dts
- mfd: simple-mfd-i2c: Add configuration for RPi POE HAT
- pwm: raspberrypi-poe: Add option of being created by MFD or FW
- power: rpi-poe: Drop CURRENT_AVG as it is not hardware averaged
- power: rpi-poe: Add option of being created by MFD or FW
- defconfigs: Add MFD_RASPBERRYPI_POE_HAT to Pi defconfigs.
- dtoverlays: Add option for PoE HAT to use Linux I2C instead of FW.
- drivers: bcm2835_unicam: Disable trigger mode operation
- arm: Remove spurious .fnend directive
- drm/vc4: Fix deadlock on DSI device attach error
- drm/vc4: dsi: Correct max divider to 255 (not 7)
- defconfig: Add BACKLIGHT_PWM to bcm2709 and bcmrpi defconfigs
- dtoverlays: Add pwm backlight option to vc4-kms-dpi-generic
- dtoverlays: Correct [h|v]sync_invert config in vc4-kms-dpi-generic
- ARM: dts: BCM2711 AON_INTR2 generates IRQ edges
- update rpi-display-overlay.dts pins for 5.10+
[ Ubuntu: 5.15.0-18.18 ]
* jammy/linux: 5.15.0-18.18 -proposed tracker (LP: #1958638)
* CVE-2021-4155
- xfs: map unwritten blocks in XFS_IOC_{ALLOC, FREE}SP just like fallocate
* CVE-2022-0185
- SAUCE: vfs: test that one given mount param is not larger than PAGE_SIZE
* [UBUNTU 20.04] KVM hardware diagnose data improvements for guest kernel -
kernel part (LP: #1953334)
- KVM: s390: add debug statement for diag 318 CPNC data
* OOB write on BPF_RINGBUF (LP: #1956585)
- SAUCE: bpf: prevent helper argument PTR_TO_ALLOC_MEM to have offset other
than 0
* Miscellaneous Ubuntu changes
- [Config] re-enable shiftfs
- [SAUCE] shiftfs: support kernel 5.15
- [Config] update toolchain versions
* Miscellaneous upstream changes
- vfs: fs_context: fix up param length parsing in legacy_parse_param
linux-raspi (5.15.0-1001.1) jammy; urgency=medium
* Missing overlays/README (LP: #1954757)
- SAUCE: Install overlays/README
* dtoverlay=uart4 breaks Raspberry Pi 4B boot (LP: #1875454)
- SAUCE: arm: dts: Add 'brcm,bcm2835-pl011' compatible for uart2-5
* jammy/linux-raspi: Update to upstream raspberrypi rpi-5.15.y (2022-01-14)
(LP: #1958146)
- clk: bcm-2835: Pick the closest clock rate
- clk: bcm-2835: Remove rounding up the dividers
- drm/vc4: hdmi: Set a default HSM rate
- drm/vc4: hdmi: Move the HSM clock enable to runtime_pm
- drm/vc4: hdmi: Make sure the controller is powered in detect
- drm/vc4: hdmi: Make sure the controller is powered up during bind
- drm/vc4: hdmi: Rework the pre_crtc_configure error handling
- drm/vc4: hdmi: Split the CEC disable / enable functions in two
- drm/vc4: hdmi: Make sure the device is powered with CEC
- drm/vc4: hdmi: Warn if we access the controller while disabled
- drm/vc4: crtc: Make sure the HDMI controller is powered when disabling
- drm/vc4: crtc: Drop feed_txp from state
- drm/vc4: Fix non-blocking commit getting stuck forever
- drm/vc4: crtc: Copy assigned channel to the CRTC
- drm/vc4: hdmi: Add a spinlock to protect register access
- drm/vc4: hdmi: Use a mutex to prevent concurrent framework access
- drm/vc4: hdmi: Prevent access to crtc->state outside of KMS
- drm/vc4: hdmi: Check the device state in prepare()
- drm/vc4: hdmi: Introduce an output_enabled flag
- drm/vc4: hdmi: Introduce a scdc_enabled flag
- drm/vc4: hdmi: Remove the DDC probing for status detection
- drm/vc4: hdmi: Fix HPD GPIO detection
- drm/vc4: Make vc4_crtc_get_encoder public
- drm/vc4: crtc: Add encoder to vc4_crtc_config_pv prototype
- drm/vc4: crtc: Rework the encoder retrieval code (again)
- drm/vc4: crtc: Add some logging
- drm/vc4: Leverage the load tracker on the BCM2711
- drm/vc4: hdmi: Raise the maximum clock rate
- drm/vc4: hdmi: Enable the scrambler on reconnection
- drm/vc4: Increase the core clock based on HVS load
- drm/vc4: select PM
- drm/probe-helper: Create a HPD IRQ event helper for a single connector
- drm/vc4: hdmi: Actually check for the connector status in hotplug
- firmware: raspberrypi: Add RPI_FIRMWARE_NOTIFY_DISPLAY_DONE
- drm/vc4: Remove conflicting framebuffers before callind bind_all
- drm/vc4: Notify the firmware when DRM is in charge
- arm: partially revert
[Kernel-packages] [Bug 1958146] Re: jammy/linux-raspi: Update to upstream raspberrypi rpi-5.15.y (2022-01-14)
This bug was fixed in the package linux-raspi - 5.15.0-1002.2
---
linux-raspi (5.15.0-1002.2) jammy; urgency=medium
* jammy/linux-raspi: 5.15.0-1002.2 -proposed tracker (LP: #1958834)
* Packaging resync (LP: #1786013)
- [Packaging] update Ubuntu.md
- debian/dkms-versions -- update from kernel-versions (main/master)
* Kernel fails to boot in ScalingStack (LP: #1959102)
- [Config] raspi: Set VIRTIO_PCI=m
- [Config] raspi: Set ACPI=y
* jammy/linux-raspi: Update to upstream raspberrypi rpi-5.15.y (2022-01-24)
(LP: #1958854)
- brcmfmac: firmware: Fix crash in brcm_alt_fw_path
- ARM: dts: Remove VL805 USB node from CM4 dts
- mfd: simple-mfd-i2c: Add configuration for RPi POE HAT
- pwm: raspberrypi-poe: Add option of being created by MFD or FW
- power: rpi-poe: Drop CURRENT_AVG as it is not hardware averaged
- power: rpi-poe: Add option of being created by MFD or FW
- defconfigs: Add MFD_RASPBERRYPI_POE_HAT to Pi defconfigs.
- dtoverlays: Add option for PoE HAT to use Linux I2C instead of FW.
- drivers: bcm2835_unicam: Disable trigger mode operation
- arm: Remove spurious .fnend directive
- drm/vc4: Fix deadlock on DSI device attach error
- drm/vc4: dsi: Correct max divider to 255 (not 7)
- defconfig: Add BACKLIGHT_PWM to bcm2709 and bcmrpi defconfigs
- dtoverlays: Add pwm backlight option to vc4-kms-dpi-generic
- dtoverlays: Correct [h|v]sync_invert config in vc4-kms-dpi-generic
- ARM: dts: BCM2711 AON_INTR2 generates IRQ edges
- update rpi-display-overlay.dts pins for 5.10+
[ Ubuntu: 5.15.0-18.18 ]
* jammy/linux: 5.15.0-18.18 -proposed tracker (LP: #1958638)
* CVE-2021-4155
- xfs: map unwritten blocks in XFS_IOC_{ALLOC, FREE}SP just like fallocate
* CVE-2022-0185
- SAUCE: vfs: test that one given mount param is not larger than PAGE_SIZE
* [UBUNTU 20.04] KVM hardware diagnose data improvements for guest kernel -
kernel part (LP: #1953334)
- KVM: s390: add debug statement for diag 318 CPNC data
* OOB write on BPF_RINGBUF (LP: #1956585)
- SAUCE: bpf: prevent helper argument PTR_TO_ALLOC_MEM to have offset other
than 0
* Miscellaneous Ubuntu changes
- [Config] re-enable shiftfs
- [SAUCE] shiftfs: support kernel 5.15
- [Config] update toolchain versions
* Miscellaneous upstream changes
- vfs: fs_context: fix up param length parsing in legacy_parse_param
linux-raspi (5.15.0-1001.1) jammy; urgency=medium
* Missing overlays/README (LP: #1954757)
- SAUCE: Install overlays/README
* dtoverlay=uart4 breaks Raspberry Pi 4B boot (LP: #1875454)
- SAUCE: arm: dts: Add 'brcm,bcm2835-pl011' compatible for uart2-5
* jammy/linux-raspi: Update to upstream raspberrypi rpi-5.15.y (2022-01-14)
(LP: #1958146)
- clk: bcm-2835: Pick the closest clock rate
- clk: bcm-2835: Remove rounding up the dividers
- drm/vc4: hdmi: Set a default HSM rate
- drm/vc4: hdmi: Move the HSM clock enable to runtime_pm
- drm/vc4: hdmi: Make sure the controller is powered in detect
- drm/vc4: hdmi: Make sure the controller is powered up during bind
- drm/vc4: hdmi: Rework the pre_crtc_configure error handling
- drm/vc4: hdmi: Split the CEC disable / enable functions in two
- drm/vc4: hdmi: Make sure the device is powered with CEC
- drm/vc4: hdmi: Warn if we access the controller while disabled
- drm/vc4: crtc: Make sure the HDMI controller is powered when disabling
- drm/vc4: crtc: Drop feed_txp from state
- drm/vc4: Fix non-blocking commit getting stuck forever
- drm/vc4: crtc: Copy assigned channel to the CRTC
- drm/vc4: hdmi: Add a spinlock to protect register access
- drm/vc4: hdmi: Use a mutex to prevent concurrent framework access
- drm/vc4: hdmi: Prevent access to crtc->state outside of KMS
- drm/vc4: hdmi: Check the device state in prepare()
- drm/vc4: hdmi: Introduce an output_enabled flag
- drm/vc4: hdmi: Introduce a scdc_enabled flag
- drm/vc4: hdmi: Remove the DDC probing for status detection
- drm/vc4: hdmi: Fix HPD GPIO detection
- drm/vc4: Make vc4_crtc_get_encoder public
- drm/vc4: crtc: Add encoder to vc4_crtc_config_pv prototype
- drm/vc4: crtc: Rework the encoder retrieval code (again)
- drm/vc4: crtc: Add some logging
- drm/vc4: Leverage the load tracker on the BCM2711
- drm/vc4: hdmi: Raise the maximum clock rate
- drm/vc4: hdmi: Enable the scrambler on reconnection
- drm/vc4: Increase the core clock based on HVS load
- drm/vc4: select PM
- drm/probe-helper: Create a HPD IRQ event helper for a single connector
- drm/vc4: hdmi: Actually check for the connector status in hotplug
- firmware: raspberrypi: Add RPI_FIRMWARE_NOTIFY_DISPLAY_DONE
- drm/vc4: Remove conflicting framebuffers before callind bind_all
- drm/vc4: Notify the firmware when DRM is in charge
- arm: partially revert
[Kernel-packages] [Bug 1946368] Re: HDMI output freezes under current/proposed impish kernels
This bug was fixed in the package linux-raspi - 5.15.0-1002.2
---
linux-raspi (5.15.0-1002.2) jammy; urgency=medium
* jammy/linux-raspi: 5.15.0-1002.2 -proposed tracker (LP: #1958834)
* Packaging resync (LP: #1786013)
- [Packaging] update Ubuntu.md
- debian/dkms-versions -- update from kernel-versions (main/master)
* Kernel fails to boot in ScalingStack (LP: #1959102)
- [Config] raspi: Set VIRTIO_PCI=m
- [Config] raspi: Set ACPI=y
* jammy/linux-raspi: Update to upstream raspberrypi rpi-5.15.y (2022-01-24)
(LP: #1958854)
- brcmfmac: firmware: Fix crash in brcm_alt_fw_path
- ARM: dts: Remove VL805 USB node from CM4 dts
- mfd: simple-mfd-i2c: Add configuration for RPi POE HAT
- pwm: raspberrypi-poe: Add option of being created by MFD or FW
- power: rpi-poe: Drop CURRENT_AVG as it is not hardware averaged
- power: rpi-poe: Add option of being created by MFD or FW
- defconfigs: Add MFD_RASPBERRYPI_POE_HAT to Pi defconfigs.
- dtoverlays: Add option for PoE HAT to use Linux I2C instead of FW.
- drivers: bcm2835_unicam: Disable trigger mode operation
- arm: Remove spurious .fnend directive
- drm/vc4: Fix deadlock on DSI device attach error
- drm/vc4: dsi: Correct max divider to 255 (not 7)
- defconfig: Add BACKLIGHT_PWM to bcm2709 and bcmrpi defconfigs
- dtoverlays: Add pwm backlight option to vc4-kms-dpi-generic
- dtoverlays: Correct [h|v]sync_invert config in vc4-kms-dpi-generic
- ARM: dts: BCM2711 AON_INTR2 generates IRQ edges
- update rpi-display-overlay.dts pins for 5.10+
[ Ubuntu: 5.15.0-18.18 ]
* jammy/linux: 5.15.0-18.18 -proposed tracker (LP: #1958638)
* CVE-2021-4155
- xfs: map unwritten blocks in XFS_IOC_{ALLOC, FREE}SP just like fallocate
* CVE-2022-0185
- SAUCE: vfs: test that one given mount param is not larger than PAGE_SIZE
* [UBUNTU 20.04] KVM hardware diagnose data improvements for guest kernel -
kernel part (LP: #1953334)
- KVM: s390: add debug statement for diag 318 CPNC data
* OOB write on BPF_RINGBUF (LP: #1956585)
- SAUCE: bpf: prevent helper argument PTR_TO_ALLOC_MEM to have offset other
than 0
* Miscellaneous Ubuntu changes
- [Config] re-enable shiftfs
- [SAUCE] shiftfs: support kernel 5.15
- [Config] update toolchain versions
* Miscellaneous upstream changes
- vfs: fs_context: fix up param length parsing in legacy_parse_param
linux-raspi (5.15.0-1001.1) jammy; urgency=medium
* Missing overlays/README (LP: #1954757)
- SAUCE: Install overlays/README
* dtoverlay=uart4 breaks Raspberry Pi 4B boot (LP: #1875454)
- SAUCE: arm: dts: Add 'brcm,bcm2835-pl011' compatible for uart2-5
* jammy/linux-raspi: Update to upstream raspberrypi rpi-5.15.y (2022-01-14)
(LP: #1958146)
- clk: bcm-2835: Pick the closest clock rate
- clk: bcm-2835: Remove rounding up the dividers
- drm/vc4: hdmi: Set a default HSM rate
- drm/vc4: hdmi: Move the HSM clock enable to runtime_pm
- drm/vc4: hdmi: Make sure the controller is powered in detect
- drm/vc4: hdmi: Make sure the controller is powered up during bind
- drm/vc4: hdmi: Rework the pre_crtc_configure error handling
- drm/vc4: hdmi: Split the CEC disable / enable functions in two
- drm/vc4: hdmi: Make sure the device is powered with CEC
- drm/vc4: hdmi: Warn if we access the controller while disabled
- drm/vc4: crtc: Make sure the HDMI controller is powered when disabling
- drm/vc4: crtc: Drop feed_txp from state
- drm/vc4: Fix non-blocking commit getting stuck forever
- drm/vc4: crtc: Copy assigned channel to the CRTC
- drm/vc4: hdmi: Add a spinlock to protect register access
- drm/vc4: hdmi: Use a mutex to prevent concurrent framework access
- drm/vc4: hdmi: Prevent access to crtc->state outside of KMS
- drm/vc4: hdmi: Check the device state in prepare()
- drm/vc4: hdmi: Introduce an output_enabled flag
- drm/vc4: hdmi: Introduce a scdc_enabled flag
- drm/vc4: hdmi: Remove the DDC probing for status detection
- drm/vc4: hdmi: Fix HPD GPIO detection
- drm/vc4: Make vc4_crtc_get_encoder public
- drm/vc4: crtc: Add encoder to vc4_crtc_config_pv prototype
- drm/vc4: crtc: Rework the encoder retrieval code (again)
- drm/vc4: crtc: Add some logging
- drm/vc4: Leverage the load tracker on the BCM2711
- drm/vc4: hdmi: Raise the maximum clock rate
- drm/vc4: hdmi: Enable the scrambler on reconnection
- drm/vc4: Increase the core clock based on HVS load
- drm/vc4: select PM
- drm/probe-helper: Create a HPD IRQ event helper for a single connector
- drm/vc4: hdmi: Actually check for the connector status in hotplug
- firmware: raspberrypi: Add RPI_FIRMWARE_NOTIFY_DISPLAY_DONE
- drm/vc4: Remove conflicting framebuffers before callind bind_all
- drm/vc4: Notify the firmware when DRM is in charge
- arm: partially revert
[Kernel-packages] [Bug 1954757] Re: Missing overlays/README
This bug was fixed in the package linux-raspi - 5.15.0-1002.2
---
linux-raspi (5.15.0-1002.2) jammy; urgency=medium
* jammy/linux-raspi: 5.15.0-1002.2 -proposed tracker (LP: #1958834)
* Packaging resync (LP: #1786013)
- [Packaging] update Ubuntu.md
- debian/dkms-versions -- update from kernel-versions (main/master)
* Kernel fails to boot in ScalingStack (LP: #1959102)
- [Config] raspi: Set VIRTIO_PCI=m
- [Config] raspi: Set ACPI=y
* jammy/linux-raspi: Update to upstream raspberrypi rpi-5.15.y (2022-01-24)
(LP: #1958854)
- brcmfmac: firmware: Fix crash in brcm_alt_fw_path
- ARM: dts: Remove VL805 USB node from CM4 dts
- mfd: simple-mfd-i2c: Add configuration for RPi POE HAT
- pwm: raspberrypi-poe: Add option of being created by MFD or FW
- power: rpi-poe: Drop CURRENT_AVG as it is not hardware averaged
- power: rpi-poe: Add option of being created by MFD or FW
- defconfigs: Add MFD_RASPBERRYPI_POE_HAT to Pi defconfigs.
- dtoverlays: Add option for PoE HAT to use Linux I2C instead of FW.
- drivers: bcm2835_unicam: Disable trigger mode operation
- arm: Remove spurious .fnend directive
- drm/vc4: Fix deadlock on DSI device attach error
- drm/vc4: dsi: Correct max divider to 255 (not 7)
- defconfig: Add BACKLIGHT_PWM to bcm2709 and bcmrpi defconfigs
- dtoverlays: Add pwm backlight option to vc4-kms-dpi-generic
- dtoverlays: Correct [h|v]sync_invert config in vc4-kms-dpi-generic
- ARM: dts: BCM2711 AON_INTR2 generates IRQ edges
- update rpi-display-overlay.dts pins for 5.10+
[ Ubuntu: 5.15.0-18.18 ]
* jammy/linux: 5.15.0-18.18 -proposed tracker (LP: #1958638)
* CVE-2021-4155
- xfs: map unwritten blocks in XFS_IOC_{ALLOC, FREE}SP just like fallocate
* CVE-2022-0185
- SAUCE: vfs: test that one given mount param is not larger than PAGE_SIZE
* [UBUNTU 20.04] KVM hardware diagnose data improvements for guest kernel -
kernel part (LP: #1953334)
- KVM: s390: add debug statement for diag 318 CPNC data
* OOB write on BPF_RINGBUF (LP: #1956585)
- SAUCE: bpf: prevent helper argument PTR_TO_ALLOC_MEM to have offset other
than 0
* Miscellaneous Ubuntu changes
- [Config] re-enable shiftfs
- [SAUCE] shiftfs: support kernel 5.15
- [Config] update toolchain versions
* Miscellaneous upstream changes
- vfs: fs_context: fix up param length parsing in legacy_parse_param
linux-raspi (5.15.0-1001.1) jammy; urgency=medium
* Missing overlays/README (LP: #1954757)
- SAUCE: Install overlays/README
* dtoverlay=uart4 breaks Raspberry Pi 4B boot (LP: #1875454)
- SAUCE: arm: dts: Add 'brcm,bcm2835-pl011' compatible for uart2-5
* jammy/linux-raspi: Update to upstream raspberrypi rpi-5.15.y (2022-01-14)
(LP: #1958146)
- clk: bcm-2835: Pick the closest clock rate
- clk: bcm-2835: Remove rounding up the dividers
- drm/vc4: hdmi: Set a default HSM rate
- drm/vc4: hdmi: Move the HSM clock enable to runtime_pm
- drm/vc4: hdmi: Make sure the controller is powered in detect
- drm/vc4: hdmi: Make sure the controller is powered up during bind
- drm/vc4: hdmi: Rework the pre_crtc_configure error handling
- drm/vc4: hdmi: Split the CEC disable / enable functions in two
- drm/vc4: hdmi: Make sure the device is powered with CEC
- drm/vc4: hdmi: Warn if we access the controller while disabled
- drm/vc4: crtc: Make sure the HDMI controller is powered when disabling
- drm/vc4: crtc: Drop feed_txp from state
- drm/vc4: Fix non-blocking commit getting stuck forever
- drm/vc4: crtc: Copy assigned channel to the CRTC
- drm/vc4: hdmi: Add a spinlock to protect register access
- drm/vc4: hdmi: Use a mutex to prevent concurrent framework access
- drm/vc4: hdmi: Prevent access to crtc->state outside of KMS
- drm/vc4: hdmi: Check the device state in prepare()
- drm/vc4: hdmi: Introduce an output_enabled flag
- drm/vc4: hdmi: Introduce a scdc_enabled flag
- drm/vc4: hdmi: Remove the DDC probing for status detection
- drm/vc4: hdmi: Fix HPD GPIO detection
- drm/vc4: Make vc4_crtc_get_encoder public
- drm/vc4: crtc: Add encoder to vc4_crtc_config_pv prototype
- drm/vc4: crtc: Rework the encoder retrieval code (again)
- drm/vc4: crtc: Add some logging
- drm/vc4: Leverage the load tracker on the BCM2711
- drm/vc4: hdmi: Raise the maximum clock rate
- drm/vc4: hdmi: Enable the scrambler on reconnection
- drm/vc4: Increase the core clock based on HVS load
- drm/vc4: select PM
- drm/probe-helper: Create a HPD IRQ event helper for a single connector
- drm/vc4: hdmi: Actually check for the connector status in hotplug
- firmware: raspberrypi: Add RPI_FIRMWARE_NOTIFY_DISPLAY_DONE
- drm/vc4: Remove conflicting framebuffers before callind bind_all
- drm/vc4: Notify the firmware when DRM is in charge
- arm: partially revert
[Kernel-packages] [Bug 1949370] Re: Missing modules in linux-modules
This bug was fixed in the package linux-raspi - 5.15.0-1002.2
---
linux-raspi (5.15.0-1002.2) jammy; urgency=medium
* jammy/linux-raspi: 5.15.0-1002.2 -proposed tracker (LP: #1958834)
* Packaging resync (LP: #1786013)
- [Packaging] update Ubuntu.md
- debian/dkms-versions -- update from kernel-versions (main/master)
* Kernel fails to boot in ScalingStack (LP: #1959102)
- [Config] raspi: Set VIRTIO_PCI=m
- [Config] raspi: Set ACPI=y
* jammy/linux-raspi: Update to upstream raspberrypi rpi-5.15.y (2022-01-24)
(LP: #1958854)
- brcmfmac: firmware: Fix crash in brcm_alt_fw_path
- ARM: dts: Remove VL805 USB node from CM4 dts
- mfd: simple-mfd-i2c: Add configuration for RPi POE HAT
- pwm: raspberrypi-poe: Add option of being created by MFD or FW
- power: rpi-poe: Drop CURRENT_AVG as it is not hardware averaged
- power: rpi-poe: Add option of being created by MFD or FW
- defconfigs: Add MFD_RASPBERRYPI_POE_HAT to Pi defconfigs.
- dtoverlays: Add option for PoE HAT to use Linux I2C instead of FW.
- drivers: bcm2835_unicam: Disable trigger mode operation
- arm: Remove spurious .fnend directive
- drm/vc4: Fix deadlock on DSI device attach error
- drm/vc4: dsi: Correct max divider to 255 (not 7)
- defconfig: Add BACKLIGHT_PWM to bcm2709 and bcmrpi defconfigs
- dtoverlays: Add pwm backlight option to vc4-kms-dpi-generic
- dtoverlays: Correct [h|v]sync_invert config in vc4-kms-dpi-generic
- ARM: dts: BCM2711 AON_INTR2 generates IRQ edges
- update rpi-display-overlay.dts pins for 5.10+
[ Ubuntu: 5.15.0-18.18 ]
* jammy/linux: 5.15.0-18.18 -proposed tracker (LP: #1958638)
* CVE-2021-4155
- xfs: map unwritten blocks in XFS_IOC_{ALLOC, FREE}SP just like fallocate
* CVE-2022-0185
- SAUCE: vfs: test that one given mount param is not larger than PAGE_SIZE
* [UBUNTU 20.04] KVM hardware diagnose data improvements for guest kernel -
kernel part (LP: #1953334)
- KVM: s390: add debug statement for diag 318 CPNC data
* OOB write on BPF_RINGBUF (LP: #1956585)
- SAUCE: bpf: prevent helper argument PTR_TO_ALLOC_MEM to have offset other
than 0
* Miscellaneous Ubuntu changes
- [Config] re-enable shiftfs
- [SAUCE] shiftfs: support kernel 5.15
- [Config] update toolchain versions
* Miscellaneous upstream changes
- vfs: fs_context: fix up param length parsing in legacy_parse_param
linux-raspi (5.15.0-1001.1) jammy; urgency=medium
* Missing overlays/README (LP: #1954757)
- SAUCE: Install overlays/README
* dtoverlay=uart4 breaks Raspberry Pi 4B boot (LP: #1875454)
- SAUCE: arm: dts: Add 'brcm,bcm2835-pl011' compatible for uart2-5
* jammy/linux-raspi: Update to upstream raspberrypi rpi-5.15.y (2022-01-14)
(LP: #1958146)
- clk: bcm-2835: Pick the closest clock rate
- clk: bcm-2835: Remove rounding up the dividers
- drm/vc4: hdmi: Set a default HSM rate
- drm/vc4: hdmi: Move the HSM clock enable to runtime_pm
- drm/vc4: hdmi: Make sure the controller is powered in detect
- drm/vc4: hdmi: Make sure the controller is powered up during bind
- drm/vc4: hdmi: Rework the pre_crtc_configure error handling
- drm/vc4: hdmi: Split the CEC disable / enable functions in two
- drm/vc4: hdmi: Make sure the device is powered with CEC
- drm/vc4: hdmi: Warn if we access the controller while disabled
- drm/vc4: crtc: Make sure the HDMI controller is powered when disabling
- drm/vc4: crtc: Drop feed_txp from state
- drm/vc4: Fix non-blocking commit getting stuck forever
- drm/vc4: crtc: Copy assigned channel to the CRTC
- drm/vc4: hdmi: Add a spinlock to protect register access
- drm/vc4: hdmi: Use a mutex to prevent concurrent framework access
- drm/vc4: hdmi: Prevent access to crtc->state outside of KMS
- drm/vc4: hdmi: Check the device state in prepare()
- drm/vc4: hdmi: Introduce an output_enabled flag
- drm/vc4: hdmi: Introduce a scdc_enabled flag
- drm/vc4: hdmi: Remove the DDC probing for status detection
- drm/vc4: hdmi: Fix HPD GPIO detection
- drm/vc4: Make vc4_crtc_get_encoder public
- drm/vc4: crtc: Add encoder to vc4_crtc_config_pv prototype
- drm/vc4: crtc: Rework the encoder retrieval code (again)
- drm/vc4: crtc: Add some logging
- drm/vc4: Leverage the load tracker on the BCM2711
- drm/vc4: hdmi: Raise the maximum clock rate
- drm/vc4: hdmi: Enable the scrambler on reconnection
- drm/vc4: Increase the core clock based on HVS load
- drm/vc4: select PM
- drm/probe-helper: Create a HPD IRQ event helper for a single connector
- drm/vc4: hdmi: Actually check for the connector status in hotplug
- firmware: raspberrypi: Add RPI_FIRMWARE_NOTIFY_DISPLAY_DONE
- drm/vc4: Remove conflicting framebuffers before callind bind_all
- drm/vc4: Notify the firmware when DRM is in charge
- arm: partially revert
[Kernel-packages] [Bug 1959102] Re: Kernel fails to boot in ScalingStack
This bug was fixed in the package linux-raspi - 5.15.0-1002.2
---
linux-raspi (5.15.0-1002.2) jammy; urgency=medium
* jammy/linux-raspi: 5.15.0-1002.2 -proposed tracker (LP: #1958834)
* Packaging resync (LP: #1786013)
- [Packaging] update Ubuntu.md
- debian/dkms-versions -- update from kernel-versions (main/master)
* Kernel fails to boot in ScalingStack (LP: #1959102)
- [Config] raspi: Set VIRTIO_PCI=m
- [Config] raspi: Set ACPI=y
* jammy/linux-raspi: Update to upstream raspberrypi rpi-5.15.y (2022-01-24)
(LP: #1958854)
- brcmfmac: firmware: Fix crash in brcm_alt_fw_path
- ARM: dts: Remove VL805 USB node from CM4 dts
- mfd: simple-mfd-i2c: Add configuration for RPi POE HAT
- pwm: raspberrypi-poe: Add option of being created by MFD or FW
- power: rpi-poe: Drop CURRENT_AVG as it is not hardware averaged
- power: rpi-poe: Add option of being created by MFD or FW
- defconfigs: Add MFD_RASPBERRYPI_POE_HAT to Pi defconfigs.
- dtoverlays: Add option for PoE HAT to use Linux I2C instead of FW.
- drivers: bcm2835_unicam: Disable trigger mode operation
- arm: Remove spurious .fnend directive
- drm/vc4: Fix deadlock on DSI device attach error
- drm/vc4: dsi: Correct max divider to 255 (not 7)
- defconfig: Add BACKLIGHT_PWM to bcm2709 and bcmrpi defconfigs
- dtoverlays: Add pwm backlight option to vc4-kms-dpi-generic
- dtoverlays: Correct [h|v]sync_invert config in vc4-kms-dpi-generic
- ARM: dts: BCM2711 AON_INTR2 generates IRQ edges
- update rpi-display-overlay.dts pins for 5.10+
[ Ubuntu: 5.15.0-18.18 ]
* jammy/linux: 5.15.0-18.18 -proposed tracker (LP: #1958638)
* CVE-2021-4155
- xfs: map unwritten blocks in XFS_IOC_{ALLOC, FREE}SP just like fallocate
* CVE-2022-0185
- SAUCE: vfs: test that one given mount param is not larger than PAGE_SIZE
* [UBUNTU 20.04] KVM hardware diagnose data improvements for guest kernel -
kernel part (LP: #1953334)
- KVM: s390: add debug statement for diag 318 CPNC data
* OOB write on BPF_RINGBUF (LP: #1956585)
- SAUCE: bpf: prevent helper argument PTR_TO_ALLOC_MEM to have offset other
than 0
* Miscellaneous Ubuntu changes
- [Config] re-enable shiftfs
- [SAUCE] shiftfs: support kernel 5.15
- [Config] update toolchain versions
* Miscellaneous upstream changes
- vfs: fs_context: fix up param length parsing in legacy_parse_param
linux-raspi (5.15.0-1001.1) jammy; urgency=medium
* Missing overlays/README (LP: #1954757)
- SAUCE: Install overlays/README
* dtoverlay=uart4 breaks Raspberry Pi 4B boot (LP: #1875454)
- SAUCE: arm: dts: Add 'brcm,bcm2835-pl011' compatible for uart2-5
* jammy/linux-raspi: Update to upstream raspberrypi rpi-5.15.y (2022-01-14)
(LP: #1958146)
- clk: bcm-2835: Pick the closest clock rate
- clk: bcm-2835: Remove rounding up the dividers
- drm/vc4: hdmi: Set a default HSM rate
- drm/vc4: hdmi: Move the HSM clock enable to runtime_pm
- drm/vc4: hdmi: Make sure the controller is powered in detect
- drm/vc4: hdmi: Make sure the controller is powered up during bind
- drm/vc4: hdmi: Rework the pre_crtc_configure error handling
- drm/vc4: hdmi: Split the CEC disable / enable functions in two
- drm/vc4: hdmi: Make sure the device is powered with CEC
- drm/vc4: hdmi: Warn if we access the controller while disabled
- drm/vc4: crtc: Make sure the HDMI controller is powered when disabling
- drm/vc4: crtc: Drop feed_txp from state
- drm/vc4: Fix non-blocking commit getting stuck forever
- drm/vc4: crtc: Copy assigned channel to the CRTC
- drm/vc4: hdmi: Add a spinlock to protect register access
- drm/vc4: hdmi: Use a mutex to prevent concurrent framework access
- drm/vc4: hdmi: Prevent access to crtc->state outside of KMS
- drm/vc4: hdmi: Check the device state in prepare()
- drm/vc4: hdmi: Introduce an output_enabled flag
- drm/vc4: hdmi: Introduce a scdc_enabled flag
- drm/vc4: hdmi: Remove the DDC probing for status detection
- drm/vc4: hdmi: Fix HPD GPIO detection
- drm/vc4: Make vc4_crtc_get_encoder public
- drm/vc4: crtc: Add encoder to vc4_crtc_config_pv prototype
- drm/vc4: crtc: Rework the encoder retrieval code (again)
- drm/vc4: crtc: Add some logging
- drm/vc4: Leverage the load tracker on the BCM2711
- drm/vc4: hdmi: Raise the maximum clock rate
- drm/vc4: hdmi: Enable the scrambler on reconnection
- drm/vc4: Increase the core clock based on HVS load
- drm/vc4: select PM
- drm/probe-helper: Create a HPD IRQ event helper for a single connector
- drm/vc4: hdmi: Actually check for the connector status in hotplug
- firmware: raspberrypi: Add RPI_FIRMWARE_NOTIFY_DISPLAY_DONE
- drm/vc4: Remove conflicting framebuffers before callind bind_all
- drm/vc4: Notify the firmware when DRM is in charge
- arm: partially revert
[Kernel-packages] [Bug 1957753] Re: net/mlx5e: EPERM on vlan 0 programming
Tested the proposed focal kernel - looks good as well: $ uname -r 5.4.0-98-generic $ apt policy linux-image-5.4.0-98-generic linux-image-5.4.0-98-generic: Installed: 5.4.0-98.111 Candidate: 5.4.0-98.111 Version table: *** 5.4.0-98.111 500 500 http://ppa.launchpad.net/canonical-kernel-team/proposed/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status $ readlink /sys/class/net/enp130s0f0v0/device ../../../:82:00.3 $ sudo lspci -s :82:00.3 -v 82:00.3 Ethernet controller: Mellanox Technologies ConnectX Family mlx5Gen Virtual Function (rev 01) Subsystem: Mellanox Technologies ConnectX Family mlx5Gen Virtual Function Flags: bus master, fast devsel, latency 0, NUMA node 1 Memory at 3c00400 (64-bit, prefetchable) [virtual] [size=2M] Capabilities: [60] Express Endpoint, MSI 00 Capabilities: [48] Vital Product Data Capabilities: [9c] MSI-X: Enable+ Count=12 Masked- Capabilities: [100] Vendor Specific Information: ID= Rev=0 Len=00c Capabilities: [150] Alternative Routing-ID Interpretation (ARI) Kernel driver in use: mlx5_core Kernel modules: mlx5_core $ sudo lspci -s :82:00.0 -v 82:00.0 Ethernet controller: Mellanox Technologies MT42822 BlueField-2 integrated ConnectX-6 Dx network controller (rev 01) Subsystem: Mellanox Technologies MT42822 BlueField-2 integrated ConnectX-6 Dx network controller Flags: bus master, fast devsel, latency 0, IRQ 99, NUMA node 1 Memory at 3c00200 (64-bit, prefetchable) [size=32M] Expansion ROM at [disabled] Capabilities: [60] Express Endpoint, MSI 00 Capabilities: [48] Vital Product Data Capabilities: [9c] MSI-X: Enable+ Count=64 Masked- Capabilities: [c0] Vendor Specific Information: Len=18 Capabilities: [40] Power Management version 3 Capabilities: [100] Advanced Error Reporting Capabilities: [150] Alternative Routing-ID Interpretation (ARI) Capabilities: [180] Single Root I/O Virtualization (SR-IOV) Capabilities: [1c0] Secondary PCI Express Capabilities: [230] Access Control Services Capabilities: [320] Lane Margining at the Receiver Capabilities: [370] Physical Layer 16.0 GT/s Capabilities: [420] Data Link Feature Kernel driver in use: mlx5_core Kernel modules: mlx5_core $ sudo ip link set enp130s0f0 vf 0 vlan 1 ; echo $? RTNETLINK answers: Operation not permitted 2 $ sudo ip link set enp130s0f0 vf 0 vlan 0 ; echo $? 0 ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- 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/1957753 Title: net/mlx5e: EPERM on vlan 0 programming Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: Fix Committed Status in linux source package in Hirsute: Won't Fix Status in linux source package in Impish: Fix Committed Status in linux source package in Jammy: In Progress Bug description: [Impact] There is an issue with hypervisor host side mlx5 driver operation on Bluefield devices in kernels <=5.16 From patch description: When using libvirt to passthrough VF to VM it will always set the VF vlan to 0 even if user didn’t request it, this will cause libvirt to fail to boot in case the PF isn't eswitch owner. Example of such case is the DPU host PF which isn't eswitch manager, so any attempt to passthrough VF of it using libvirt will fail. [Fix] * 7846665d net/mlx5e: Unblock setting vid 0 for VF in case PF isn't eswitch manager This patch can be cherry-picked into Impish and newer kernels, but it requires some backport work on F/H due to they're missing commit b55b3538 that split the legacy code out. The ESW_ALLOWED marco was later converted into a helper routine in commit b16f2bb6. [Test] Test kernels can be found here: F: https://people.canonical.com/~phlin/kernel/lp-1957753-mlx5e/F/ H: https://people.canonical.com/~phlin/kernel/lp-1957753-mlx5e/H/ I: https://people.canonical.com/~phlin/kernel/lp-1957753-mlx5e/I/ J: https://people.canonical.com/~phlin/kernel/lp-1957753-mlx5e/J/ Kernels tested on a SUT with this device by Dmitrii Shcherbakov, test passed with positive feedback. [Where problems could occur] If this patch is erroneous, it might cause issue to this mlx5 driver with certain operations (setting vid 0). And other programs such as libvirt that depends on this return value might be affected as well. [Original Bug Description] There is an issue with hypervisor host side mlx5 driver operation on Bluefield devices in kernels <=5.16 that was recently fixed in master with a one-liner:
[Kernel-packages] [Bug 1958289] Re: [amdgpu] Hang on shutdown: systemd-udevd ... Worker ... processing SEQNUM=... is taking a long time
Hi All, I confirm also in my case the bug is fixed with 5.13.0-28-generic. Thank you all guys! Marco -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1958289 Title: [amdgpu] Hang on shutdown: systemd-udevd ... Worker ... processing SEQNUM=... is taking a long time Status in linux-hwe-5.13 package in Ubuntu: Confirmed Bug description: dell inspiron 7415 2in1 os 20.04.3lts gnome 3.36.8 x11 message on black screen [ 38.407808] systemd-shutdown [1]: Waiting for process: systemd-udevd, systemd-udevd [ 63.708267] systemd-udevd [381]: :03:00.7: Worker [412] processing SEQNUM=3413 is taking a long time [ 141.099020] atkbd serio0: Unknown key pressed (translated set 2, code 0x67 on isa0060/seri00). [ 141.099110] atkbd serio0: Use 'setkeycodes 67 to make it known. [ 141.103874) atkbd serio0: Unknown key released (translated set 2, code 0x67 on isa0060/seri00). [ 141.103964] atkbd serio0: Use 'setkeycodes 67 ' to make it known. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: antonio1800 F pulseaudio /dev/snd/controlC0: antonio1800 F pulseaudio /dev/snd/controlC2: antonio1800 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2022-01-06 (12 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: Dell Inc. Inspiron 7415 2-in-1 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-25-generic root=UUID=95fe2347-727f-4d0c-8559-24cb9ae1d39f ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-25.26~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-25-generic N/A linux-backports-modules-5.13.0-25-generic N/A linux-firmware 1.187.25 Tags: focal Uname: Linux 5.13.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/04/2021 dmi.bios.release: 1.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.0 dmi.board.name: 09X2G7 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.6.0 dmi.modalias: dmi:bvnDellInc.:bvr1.6.0:bd11/04/2021:br1.6:svnDellInc.:pnInspiron74152-in-1:pvr1.6.0:rvnDellInc.:rn09X2G7:rvrA01:cvnDellInc.:ct31:cvr1.6.0:sku0A8C: dmi.product.family: Inspiron dmi.product.name: Inspiron 7415 2-in-1 dmi.product.sku: 0A8C dmi.product.version: 1.6.0 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: antonio1792 F pulseaudio /dev/snd/controlC0: antonio1792 F pulseaudio /dev/snd/controlC2: antonio1792 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2022-01-06 (12 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: Dell Inc. Inspiron 7415 2-in-1 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-25-generic root=UUID=95fe2347-727f-4d0c-8559-24cb9ae1d39f ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-25.26~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-25-generic N/A linux-backports-modules-5.13.0-25-generic N/A linux-firmware 1.187.25 Tags: focal Uname: Linux 5.13.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/04/2021 dmi.bios.release: 1.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.0 dmi.board.name: 09X2G7 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.6.0 dmi.modalias: dmi:bvnDellInc.:bvr1.6.0:bd11/04/2021:br1.6:svnDellInc.:pnInspiron74152-in-1:pvr1.6.0:rvnDellInc.:rn09X2G7:rvrA01:cvnDellInc.:ct31:cvr1.6.0:sku0A8C: dmi.product.family: Inspiron dmi.product.name: Inspiron 7415 2-in-1 dmi.product.sku: 0A8C dmi.product.version: 1.6.0 dmi.sys.vendor:
[Kernel-packages] [Bug 1957753] Re: net/mlx5e: EPERM on vlan 0 programming
Tried the proposed impish kernel - looks good: $ uname -r 5.13.0-29-generic $ apt policy linux-image-5.13.0-29-generic linux-image-5.13.0-29-generic: Installed: 5.13.0-29.32 Candidate: 5.13.0-29.32 Version table: *** 5.13.0-29.32 500 500 http://ppa.launchpad.net/canonical-kernel-team/proposed/ubuntu impish/main amd64 Packages 100 /var/lib/dpkg/status $ readlink /sys/class/net/enp130s0f0v0/device ../../../:82:00.3 # VF $ sudo lspci -s :82:00.3 -v 82:00.3 Ethernet controller: Mellanox Technologies ConnectX Family mlx5Gen Virtual Function (rev 01) Subsystem: Mellanox Technologies ConnectX Family mlx5Gen Virtual Function Flags: bus master, fast devsel, latency 0, NUMA node 1 Memory at 3c00400 (64-bit, prefetchable) [virtual] [size=2M] Capabilities: [60] Express Endpoint, MSI 00 Capabilities: [48] Vital Product Data Capabilities: [9c] MSI-X: Enable+ Count=12 Masked- Capabilities: [100] Vendor Specific Information: ID= Rev=0 Len=00c Capabilities: [150] Alternative Routing-ID Interpretation (ARI) Kernel driver in use: mlx5_core Kernel modules: mlx5_core # Parent PF $ sudo lspci -s :82:00.0 -v 82:00.0 Ethernet controller: Mellanox Technologies MT42822 BlueField-2 integrated ConnectX-6 Dx network controller (rev 01) Subsystem: Mellanox Technologies MT42822 BlueField-2 integrated ConnectX-6 Dx network controller Flags: bus master, fast devsel, latency 0, IRQ 101, NUMA node 1 Memory at 3c00200 (64-bit, prefetchable) [size=32M] Expansion ROM at [disabled] Capabilities: [60] Express Endpoint, MSI 00 Capabilities: [48] Vital Product Data Capabilities: [9c] MSI-X: Enable+ Count=64 Masked- Capabilities: [c0] Vendor Specific Information: Len=18 Capabilities: [40] Power Management version 3 Capabilities: [100] Advanced Error Reporting Capabilities: [150] Alternative Routing-ID Interpretation (ARI) Capabilities: [180] Single Root I/O Virtualization (SR-IOV) Capabilities: [1c0] Secondary PCI Express Capabilities: [230] Access Control Services Capabilities: [320] Lane Margining at the Receiver Capabilities: [370] Physical Layer 16.0 GT/s Capabilities: [420] Data Link Feature Kernel driver in use: mlx5_core Kernel modules: mlx5_core $ sudo ip link set enp130s0f0 vf 0 vlan 1 ; echo $? RTNETLINK answers: Operation not permitted 2 $ sudo ip link set enp130s0f0 vf 0 vlan 0 ; echo $? 0 ** Tags removed: verification-needed-impish ** Tags added: verification-done-impish -- 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/1957753 Title: net/mlx5e: EPERM on vlan 0 programming Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: Fix Committed Status in linux source package in Hirsute: Won't Fix Status in linux source package in Impish: Fix Committed Status in linux source package in Jammy: In Progress Bug description: [Impact] There is an issue with hypervisor host side mlx5 driver operation on Bluefield devices in kernels <=5.16 From patch description: When using libvirt to passthrough VF to VM it will always set the VF vlan to 0 even if user didn’t request it, this will cause libvirt to fail to boot in case the PF isn't eswitch owner. Example of such case is the DPU host PF which isn't eswitch manager, so any attempt to passthrough VF of it using libvirt will fail. [Fix] * 7846665d net/mlx5e: Unblock setting vid 0 for VF in case PF isn't eswitch manager This patch can be cherry-picked into Impish and newer kernels, but it requires some backport work on F/H due to they're missing commit b55b3538 that split the legacy code out. The ESW_ALLOWED marco was later converted into a helper routine in commit b16f2bb6. [Test] Test kernels can be found here: F: https://people.canonical.com/~phlin/kernel/lp-1957753-mlx5e/F/ H: https://people.canonical.com/~phlin/kernel/lp-1957753-mlx5e/H/ I: https://people.canonical.com/~phlin/kernel/lp-1957753-mlx5e/I/ J: https://people.canonical.com/~phlin/kernel/lp-1957753-mlx5e/J/ Kernels tested on a SUT with this device by Dmitrii Shcherbakov, test passed with positive feedback. [Where problems could occur] If this patch is erroneous, it might cause issue to this mlx5 driver with certain operations (setting vid 0). And other programs such as libvirt that depends on this return value might be affected as well. [Original Bug Description] There is an issue with hypervisor host side mlx5 driver operation on Bluefield devices in kernels <=5.16 that was recently fixed in master with a one-liner:
[Kernel-packages] [Bug 1958155] Re: Pod traffic not taking advantage of interfaces with multiple tx queues
** Tags removed: verification-needed-impish
** Tags added: verification-done-impish
--
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/1958155
Title:
Pod traffic not taking advantage of interfaces with multiple tx queues
Status in linux package in Ubuntu:
Fix Released
Status in linux-hwe-5.11 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Invalid
Status in linux-hwe-5.11 source package in Focal:
Fix Committed
Status in linux source package in Hirsute:
Won't Fix
Status in linux-hwe-5.11 source package in Hirsute:
Invalid
Status in linux source package in Impish:
Fix Committed
Status in linux-hwe-5.11 source package in Impish:
Invalid
Bug description:
SRU Justification
[Impact]
https://patchwork.kernel.org/project/netdevbpf/patch/ef4cf3168907944502c81d8bf45e24eea1061e47.1641427152.git.dan...@iogearbox.net/
Performance is impacted when multiple TX queues are enabled.
[Fix]
commit 710ad98c363a66a0cd8526465426c5c5f8377ee0 ("veth: Do not record rx
queue hint in veth_xmit")
This patch is already scheduled for release in these stable kernel
versions:
linux-5.10.y.txt:5f76445a31b79be85b337cce5f35affb77cc18fc veth: Do not record
rx queue hint in veth_xmit
linux-5.15.y.txt:78a19e506bdcd1bfff73523ec99190794e0af39c veth: Do not record
rx queue hint in veth_xmit
linux-5.16.y.txt:bf8963ea39ecfd1bddc657a81f1d657b43c950e8 veth: Do not record
rx queue hint in veth_xmit
linux-5.4.y.txt:d08a0a88db88462bdf1b2df33ded23269b832afc veth: Do not record
rx queue hint in veth_xmit
[Test Plan]
Upstream tested
[Where things could go wrong]
Transmit performance could be impacted in other ways.
[Other Info]
SF: #00326544
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958155/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958295] Re: Using Touchscreen creates soft lockup - Lenovo Yoga 9i - KDE
** Summary changed: - Using Touchscreen creates soft lockup - Lenovo Yoga 9i + Using Touchscreen creates soft lockup - Lenovo Yoga 9i - KDE -- 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/1958295 Title: Using Touchscreen creates soft lockup - Lenovo Yoga 9i - KDE Status in linux package in Ubuntu: Confirmed Bug description: 1)lsbrelease -rd: Description:Ubuntu 21.10 Release:21.10 2) i dont know if it is the kernel or an KDE problem, but i would guess the kernel 3) Use the touchscreen without errors 4) The following Error-Message pops up, sometimes(!) when i use the touchscreen. It is not every time and i dont know how to re-create it: kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 108s! [irq/158-WACF220:257] ... complete error-message is an attachment --- When this happens i cant use my touchscreen or touchpad. It is stuck for ~30 seconds. I can still use my keyboard. *Edit: now it also affected my Keyboard and i couldn't use it. After it worked again, i could not scroll up/down with my touchpad (see "complete-error-report-2") --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: anon 3421 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-07-21 (181 days ago) InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 82BG Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-25-generic root=UUID=c0c7dfa0-95cf-4a4f-a107-ddbd3ed7c4e2 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-25.26-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-25-generic N/A linux-backports-modules-5.13.0-25-generic N/A linux-firmware 1.201.3 Tags: impish Uname: Linux 5.13.0-25-generic x86_64 UpgradeStatus: Upgraded to impish on 2021-10-22 (88 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/01/2021 dmi.bios.release: 1.65 dmi.bios.vendor: LENOVO dmi.bios.version: EHCN65WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga 9 14ITL5 dmi.ec.firmware.release: 1.65 dmi.modalias: dmi:bvnLENOVO:bvrEHCN65WW:bd07/01/2021:br1.65:efr1.65:svnLENOVO:pn82BG:pvrYoga914ITL5:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrYoga914ITL5:skuLENOVO_MT_82BG_BU_idea_FM_Yoga914ITL5: dmi.product.family: Yoga 9 14ITL5 dmi.product.name: 82BG dmi.product.sku: LENOVO_MT_82BG_BU_idea_FM_Yoga 9 14ITL5 dmi.product.version: Yoga 9 14ITL5 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958295/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958155] Re: Pod traffic not taking advantage of interfaces with multiple tx queues
This bug is awaiting verification that the linux-hwe-5.11/5.11.0-60.60
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-focal' to 'verification-done-focal'. If the
problem still exists, change the tag 'verification-needed-focal' to
'verification-failed-focal'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: verification-needed-focal
--
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/1958155
Title:
Pod traffic not taking advantage of interfaces with multiple tx queues
Status in linux package in Ubuntu:
Fix Released
Status in linux-hwe-5.11 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Invalid
Status in linux-hwe-5.11 source package in Focal:
Fix Committed
Status in linux source package in Hirsute:
Won't Fix
Status in linux-hwe-5.11 source package in Hirsute:
Invalid
Status in linux source package in Impish:
Fix Committed
Status in linux-hwe-5.11 source package in Impish:
Invalid
Bug description:
SRU Justification
[Impact]
https://patchwork.kernel.org/project/netdevbpf/patch/ef4cf3168907944502c81d8bf45e24eea1061e47.1641427152.git.dan...@iogearbox.net/
Performance is impacted when multiple TX queues are enabled.
[Fix]
commit 710ad98c363a66a0cd8526465426c5c5f8377ee0 ("veth: Do not record rx
queue hint in veth_xmit")
This patch is already scheduled for release in these stable kernel
versions:
linux-5.10.y.txt:5f76445a31b79be85b337cce5f35affb77cc18fc veth: Do not record
rx queue hint in veth_xmit
linux-5.15.y.txt:78a19e506bdcd1bfff73523ec99190794e0af39c veth: Do not record
rx queue hint in veth_xmit
linux-5.16.y.txt:bf8963ea39ecfd1bddc657a81f1d657b43c950e8 veth: Do not record
rx queue hint in veth_xmit
linux-5.4.y.txt:d08a0a88db88462bdf1b2df33ded23269b832afc veth: Do not record
rx queue hint in veth_xmit
[Test Plan]
Upstream tested
[Where things could go wrong]
Transmit performance could be impacted in other ways.
[Other Info]
SF: #00326544
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958155/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958518] Re: split some large, lesser-used firmware files into -extra package
The linux-firmware package in jammy grew considerably and is now almost 1GB in size. -- 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/1958518 Title: split some large, lesser-used firmware files into -extra package Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Jammy: New Bug description: The linux-image-generic package depends on linux-firmware which is over half a gigabyte in size installed. I will assume that quite many people do not have netronome hardware which weighs in at almost 150MB of that. I kindly suggest to put such large firmware for less common hardware into its own linux-firmware-extra package which would be recommended by linux-firmare. Comments? I'm willing to help with the packaging provided that the changes have a chance to land. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1958518/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958518] Re: split some large, lesser-used firmware files into -extra package
Juerg, thank you for picking this up and my apologies for the late response. You are of course right that there is no scientific answer or approach to this question. I'd simply look at the biggest directories with ncdu and make a decision if I thought that hardware was common when going down the list from top towards the bottom (first few entries only, of course). Let's be clear that this is not about stopping to support anything, upsetting anybody or break things or make things harder for people. Anybody who has the default of installing recommends by default will not be affected by this at all. It is about choice, for people in a scenario with limited ressources who'd like to trim some fat. Those people would need to make a conscious choice to remove the unnecessary (for them) packages. I certainly won't need support for netronome on any of my machines and would not install the package that contains it if it were optional. -- 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/1958518 Title: split some large, lesser-used firmware files into -extra package Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Jammy: New Bug description: The linux-image-generic package depends on linux-firmware which is over half a gigabyte in size installed. I will assume that quite many people do not have netronome hardware which weighs in at almost 150MB of that. I kindly suggest to put such large firmware for less common hardware into its own linux-firmware-extra package which would be recommended by linux-firmare. Comments? I'm willing to help with the packaging provided that the changes have a chance to land. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1958518/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958295] Re: Using Touchscreen creates soft lockup - Lenovo Yoga 9i
** Attachment added: "complete-error-report-2 - Keyboard affected" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958295/+attachment/5558765/+files/complete-error-report-2 ** Changed in: linux (Ubuntu) Status: Incomplete => 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/1958295 Title: Using Touchscreen creates soft lockup - Lenovo Yoga 9i Status in linux package in Ubuntu: Confirmed Bug description: 1)lsbrelease -rd: Description:Ubuntu 21.10 Release:21.10 2) i dont know if it is the kernel or an KDE problem, but i would guess the kernel 3) Use the touchscreen without errors 4) The following Error-Message pops up, sometimes(!) when i use the touchscreen. It is not every time and i dont know how to re-create it: kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 108s! [irq/158-WACF220:257] ... complete error-message is an attachment --- When this happens i cant use my touchscreen or touchpad. It is stuck for ~30 seconds. I can still use my keyboard. *Edit: now it also affected my Keyboard and i couldn't use it. After it worked again, i could not scroll up/down with my touchpad (see "complete-error-report-2") --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: anon 3421 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-07-21 (181 days ago) InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 82BG Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-25-generic root=UUID=c0c7dfa0-95cf-4a4f-a107-ddbd3ed7c4e2 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-25.26-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-25-generic N/A linux-backports-modules-5.13.0-25-generic N/A linux-firmware 1.201.3 Tags: impish Uname: Linux 5.13.0-25-generic x86_64 UpgradeStatus: Upgraded to impish on 2021-10-22 (88 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/01/2021 dmi.bios.release: 1.65 dmi.bios.vendor: LENOVO dmi.bios.version: EHCN65WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga 9 14ITL5 dmi.ec.firmware.release: 1.65 dmi.modalias: dmi:bvnLENOVO:bvrEHCN65WW:bd07/01/2021:br1.65:efr1.65:svnLENOVO:pn82BG:pvrYoga914ITL5:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrYoga914ITL5:skuLENOVO_MT_82BG_BU_idea_FM_Yoga914ITL5: dmi.product.family: Yoga 9 14ITL5 dmi.product.name: 82BG dmi.product.sku: LENOVO_MT_82BG_BU_idea_FM_Yoga 9 14ITL5 dmi.product.version: Yoga 9 14ITL5 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958295/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958295] Re: Using Touchscreen creates soft lockup - Lenovo Yoga 9i
** Description changed: 1)lsbrelease -rd: - Description:Ubuntu 21.10 - Release:21.10 + Description:Ubuntu 21.10 + Release:21.10 2) i dont know if it is the kernel or an KDE problem, but i would guess the kernel 3) Use the touchscreen without errors 4) The following Error-Message pops up, sometimes(!) when i use the touchscreen. It is not every time and i dont know how to re-create it: kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 108s! [irq/158-WACF220:257] ... complete error-message is an attachment --- - When this happens i cant use my touchscreen or touchpad. It is stuck for ~30 seconds. I cant still use my keyboard. - --- + When this happens i cant use my touchscreen or touchpad. It is stuck for ~30 seconds. I can still use my keyboard. + + *Edit: + now it also affected my Keyboard and i couldn't use it. After it worked again, i could not scroll up/down with my touchpad (see "complete-error-report-2") + --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: anon 3421 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: anon 3421 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-07-21 (181 days ago) InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 82BG Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-25-generic root=UUID=c0c7dfa0-95cf-4a4f-a107-ddbd3ed7c4e2 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-25.26-generic 5.13.19 RelatedPackageVersions: - linux-restricted-modules-5.13.0-25-generic N/A - linux-backports-modules-5.13.0-25-generic N/A - linux-firmware 1.201.3 + linux-restricted-modules-5.13.0-25-generic N/A + linux-backports-modules-5.13.0-25-generic N/A + linux-firmware 1.201.3 Tags: impish Uname: Linux 5.13.0-25-generic x86_64 UpgradeStatus: Upgraded to impish on 2021-10-22 (88 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/01/2021 dmi.bios.release: 1.65 dmi.bios.vendor: LENOVO dmi.bios.version: EHCN65WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga 9 14ITL5 dmi.ec.firmware.release: 1.65 dmi.modalias: dmi:bvnLENOVO:bvrEHCN65WW:bd07/01/2021:br1.65:efr1.65:svnLENOVO:pn82BG:pvrYoga914ITL5:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrYoga914ITL5:skuLENOVO_MT_82BG_BU_idea_FM_Yoga914ITL5: dmi.product.family: Yoga 9 14ITL5 dmi.product.name: 82BG dmi.product.sku: LENOVO_MT_82BG_BU_idea_FM_Yoga 9 14ITL5 dmi.product.version: Yoga 9 14ITL5 dmi.sys.vendor: LENOVO -- 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/1958295 Title: Using Touchscreen creates soft lockup - Lenovo Yoga 9i Status in linux package in Ubuntu: Confirmed Bug description: 1)lsbrelease -rd: Description:Ubuntu 21.10 Release:21.10 2) i dont know if it is the kernel or an KDE problem, but i would guess the kernel 3) Use the touchscreen without errors 4) The following Error-Message pops up, sometimes(!) when i use the touchscreen. It is not every time and i dont know how to re-create it: kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 108s! [irq/158-WACF220:257] ... complete error-message is an attachment --- When this happens i cant use my touchscreen or touchpad. It is stuck for ~30 seconds. I can still use my keyboard. *Edit: now it also affected my Keyboard and i couldn't use it. After it worked again, i could not scroll up/down with my touchpad (see "complete-error-report-2") --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: anon 3421 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-07-21 (181 days ago) InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 82BG Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-25-generic root=UUID=c0c7dfa0-95cf-4a4f-a107-ddbd3ed7c4e2 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-25.26-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-25-generic N/A
[Kernel-packages] [Bug 1956422] Re: Linux Kernel 5.13.0-23 Suspend Modus
*** This bug is a duplicate of bug 1956401 *** https://bugs.launchpad.net/bugs/1956401 Re-added duplicate mark, as on 5.13.0-28(5.13.0.28.31~20.04.15) suspend is working fine again. ** This bug has been marked a duplicate of bug 1956401 amdgpu hangs for 90 seconds at a time in 5.13.0-23, but 5.13.0-22 works -- 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/1956422 Title: Linux Kernel 5.13.0-23 Suspend Modus Status in linux package in Ubuntu: Confirmed Bug description: Hi there, after updating to kernel 5.13.0-23 the suspend modus is not working anymore. I tried it with a Dell inspiron 5415 with AMD processor and a MacBook with a Intel processor. I have to start with Kernel 5.13.0-22 and then it works fine. When is suspend modus the computer doesn't wake up again. Thanx in advance. Dietmar ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-23-generic 5.13.0-23.23 ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19 Uname: Linux 5.13.0-23-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dietmar1227 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jan 5 08:06:59 2022 InstallationDate: Installed on 2021-10-21 (75 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: Apple Inc. MacBook5,1 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-23-generic root=UUID=dfd4fa6d-1d92-4d20-b916-8d9ed9588566 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-23-generic N/A linux-backports-modules-5.13.0-23-generic N/A linux-firmware 1.201.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/27/09 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: MB51.88Z.007D.B03.0904271443 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-F42D89C8 dmi.board.vendor: Apple Inc. dmi.board.version: Proto dmi.chassis.asset.tag: Asset Tag# dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F42D89C8 dmi.modalias: dmi:bvnAppleInc.:bvrMB51.88Z.007D.B03.0904271443:bd04/27/09:br0.1:svnAppleInc.:pnMacBook5,1:pvr1.0:rvnAppleInc.:rnMac-F42D89C8:rvrProto:cvnAppleInc.:ct10:cvrMac-F42D89C8:skuSystemSKU#: dmi.product.family: MacBook dmi.product.name: MacBook5,1 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956422/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956401] Re: amdgpu hangs for 90 seconds at a time in 5.13.0-23, but 5.13.0-22 works
Yup, can confirm this on my end as well for
5.13.0-28-generic(5.13.0.28.31~20.04.15) suspend is working fine again.
--
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/1956401
Title:
amdgpu hangs for 90 seconds at a time in 5.13.0-23, but 5.13.0-22
works
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Impish:
Fix Released
Status in linux source package in Jammy:
Fix Released
Bug description:
SRU Justification
Impact:
This does not occur with linux-image-5.13.0-22-generic, but does with
linux-image-5.13.0-23-generic.
On startup, I get about a 60 second hang, with the following in the kernel
dmesg:
Jan 4 15:26:36 inspiron-3505 kernel: [ 34.160572] amdgpu :04:00.0:
amdgp : failed to write reg 28b4 wait reg 28c6
Jan 4 15:26:56 inspiron-3505 kernel: [ 54.189055] amdgpu :04:00.0:
amdgp : failed to write reg 1a6f4 wait reg 1a706
Jan 4 15:27:16 inspiron-3505 kernel: [ 74.329264] amdgpu :04:00.0:
amdgp : failed to write reg 28b4 wait reg 28c6
Jan 4 15:27:36 inspiron-3505 kernel: [ 94.337904] amdgpu :04:00.0:
amdgp : failed to write reg 1a6f4 wait reg 1a706
I have the following GPU:
04:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI]
Picass
o (rev c2) (prog-if 00 [VGA controller])
04:00.0 0300: 1002:15d8 (rev c2)
(This is a Ryzen 5 3450U CPU with Radeon Vega Mobile.)
I get a similar hang if I start firefox (when it's probing OpenGL
contexts), and even with glxgears and glxinfo. Seems like anything
that'd kick on a OpenGL context does it. I had a freeze as well when
I tried running firefox and glxgears both. Along with odd BUG:
messages logged (I have some in the attached log.)
I was running with "iommu=pt", but did try with this removed, still
got the errors (I think amdgpu driver uses the IOMMU even when it's
set to IOMMU=pt though.). See the attached log for some very odd
"[Hardware Error]" messages that were logged on one test run. I think
this was when I tried to run firestorm (second life viewer) -- that
had a large pause then opened to a black window.
Per Google, I see there was a bug like this that turned up in kernel
5.14.15 but fixed in 5.14.17. See
https://gitlab.freedesktop.org/drm/amd/-/issues/1770
Thanks!
--Henry
Fix:
upstream commit afd18180c070 ("drm/amdkfd: fix boot failure when iommu is
disabled in Picasso.")
Patch was included in the Impish kernel in -proposed (5.13.0.24.24)
from an upstream patch set. multiple confirmations the problem is
resolved with the kernel in -proposed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956401/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954638] Re: nvidia-kernel-source-450 450.66-0ubuntu0.20.04.1: nvidia kernel module failed to build
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-450 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-450 in Ubuntu. https://bugs.launchpad.net/bugs/1954638 Title: nvidia-kernel-source-450 450.66-0ubuntu0.20.04.1: nvidia kernel module failed to build Status in nvidia-graphics-drivers-450 package in Ubuntu: Confirmed Bug description: Automatic install ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-kernel-source-450 450.66-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.6.0-1028.28-oem 5.6.19 Uname: Linux 5.6.0-1028-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.10.0-1051-oem Date: Mon Dec 13 12:21:08 2021 Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85 DuplicateSignature: dkms:nvidia-kernel-source-450:450.66-0ubuntu0.20.04.1:/var/lib/dkms/nvidia/450.66/build/common/inc/nv-mm.h:149:45: error: passing argument 1 of ‘get_user_pages_remote’ from incompatible pointer type [-Werror=incompatible-pointer-types] InstallationDate: Installed on 2021-12-11 (1 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 PackageVersion: 450.66-0ubuntu0.20.04.1 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.2 SourcePackage: nvidia-graphics-drivers-450 Title: nvidia-kernel-source-450 450.66-0ubuntu0.20.04.1: nvidia kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-450/+bug/1954638/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1957790] Re: NVIDIA CVE-2022-{21813|21814}
** Information type changed from Private Security to Public
--
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/1957790
Title:
NVIDIA CVE-2022-{21813|21814}
Status in fabric-manager-450 package in Ubuntu:
New
Status in fabric-manager-470 package in Ubuntu:
New
Status in libnvidia-nscq-450 package in Ubuntu:
New
Status in libnvidia-nscq-470 package in Ubuntu:
New
Status in linux-restricted-modules package in Ubuntu:
New
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
New
Status in nvidia-graphics-drivers-470 package in Ubuntu:
New
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
New
Status in nvidia-graphics-drivers-495 package in Ubuntu:
New
Status in fabric-manager-450 source package in Bionic:
New
Status in fabric-manager-470 source package in Bionic:
New
Status in libnvidia-nscq-450 source package in Bionic:
New
Status in libnvidia-nscq-470 source package in Bionic:
New
Status in linux-restricted-modules source package in Bionic:
New
Status in nvidia-graphics-drivers-450-server source package in Bionic:
New
Status in nvidia-graphics-drivers-470 source package in Bionic:
New
Status in nvidia-graphics-drivers-470-server source package in Bionic:
New
Status in nvidia-graphics-drivers-495 source package in Bionic:
New
Status in fabric-manager-450 source package in Focal:
New
Status in fabric-manager-470 source package in Focal:
New
Status in libnvidia-nscq-450 source package in Focal:
New
Status in libnvidia-nscq-470 source package in Focal:
New
Status in linux-restricted-modules source package in Focal:
New
Status in nvidia-graphics-drivers-450-server source package in Focal:
New
Status in nvidia-graphics-drivers-470 source package in Focal:
New
Status in nvidia-graphics-drivers-470-server source package in Focal:
New
Status in nvidia-graphics-drivers-495 source package in Focal:
New
Status in fabric-manager-450 source package in Impish:
New
Status in fabric-manager-470 source package in Impish:
New
Status in libnvidia-nscq-450 source package in Impish:
New
Status in libnvidia-nscq-470 source package in Impish:
New
Status in linux-restricted-modules source package in Impish:
New
Status in nvidia-graphics-drivers-450-server source package in Impish:
New
Status in nvidia-graphics-drivers-470 source package in Impish:
New
Status in nvidia-graphics-drivers-470-server source package in Impish:
New
Status in nvidia-graphics-drivers-495 source package in Impish:
New
Bug description:
As per the subject, the update includes fixes for the following CVEs:
CVE-2022-21813
CVE-2022-21814
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fabric-manager-450/+bug/1957790/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1959665] Re: linux-image-5.4.0-97.110 freezes by accessing cifs shares
Hi all - thanks for the quick testing. We are evaluating the best course of action. In the short term that will likely be a respin with these patches reverted. Longer term I will work to figure out the error and find a correction. rtg -- 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/1959665 Title: linux-image-5.4.0-97.110 freezes by accessing cifs shares Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: In Progress Bug description: Ubuntu 20.04 with kernel image 5.4.0-97.110 randomly freezes when we access cifs shares. The system needs a hard reset after the freeze. The previous kernel image (5.4.0-96.109) does not show this behavior. Multiple Ubuntu 20.04 systems running on kernel image 9.4.0-97.110 are affected on our sites. The cifs shares are accessed via autofs using Kerberos authentication. The following info is the only error message we could actively catch on a different system before the system was frozen: general protection fault: [#3] SMP PTI CPU: 0 PID: 21294 Comm: automount Tainted: G DOE 5.4.0-97-generic #110-Ubuntu Hardware name: Dell Inc. Precision 7530/03RV2M, BIOS 1.14.4 10/21/2020 RIP: 0010:kmem_cache_alloc_trace+0x8c/0x240 Code: 08 65 4c 03 05 1d e8 f7 6e 49 83 78 10 00 4d 8b 38 0f 84 92 01 00 00 4d 85 ff 0f 84 89 01 00 00 41 8b 41 20 49 8b 39 4c 01 f8 <48> 8b 18 48 89 c1 49 33 99 70 01 00 00 4c 89 f8 48 0f c9 48 31 cb RSP: 0018:a6ca860f7ba0 EFLAGS: 00010286 RAX: fdd44d7c219190e1 RBX: RCX: RDX: d558 RSI: 0cc0 RDI: 00035060 RBP: a6ca860f7bd0 R08: 99233c035060 R09: 992338c079c0 R10: 0001 R11: 0004 R12: 0cc0 R13: 000b R14: 992338c079c0 R15: fdd44d7c219190e1 FS: 7fdc24e29700() GS:99233c00() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 7f15a80ee010 CR3: 0007e36b2006 CR4: 003606f0 Call Trace: ? proc_self_get_link+0x70/0xd0 proc_self_get_link+0x70/0xd0 link_path_walk.part.0+0x478/0x550 ? trailing_symlink+0x1d1/0x280 path_openat+0xb7/0x290 do_filp_open+0x91/0x100 ? unuse_pde+0x30/0x30 do_sys_open+0x17e/0x290 __x64_sys_openat+0x20/0x30 __orig_openat+0x71/0xc0 [eset_rtp] ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __x64_sys_futex+0x13f/0x170 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 __x64_sys_ertp_openat+0x29/0x60 [eset_rtp] do_syscall_64+0x57/0x190 entry_SYSCALL_64_after_hwframe+0x44/0xa9 RIP: 0033:0x7fdc28a41f24 Code: 24 20 eb 8f 66 90 44 89 54 24 0c e8 56 68 f8 ff 44 8b 54 24 0c 44 89 e2 48 89 ee 41 89 c0 bf 9c ff ff ff b8 01 01 00 00 0f 05 <48> 3d 00 f0 ff ff 77 32 44 89 c7 89 44 24 0c e8 88 68 f8 ff 8b 44 RSP: 002b:7fdc24e25980 EFLAGS: 0293 ORIG_RAX: 0101 RAX: ffda RBX: 7fdc040008d0 RCX: 7fdc28a41f24 ? unuse_pde+0x30/0x30 do_sys_open+0x17e/0x290 __x64_sys_openat+0x20/0x30 __orig_openat+0x71/0xc0 [eset_rtp] ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __x64_sys_futex+0x13f/0x170 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 __x64_sys_ertp_openat+0x29/0x60 [eset_rtp] do_syscall_64+0x57/0x190 entry_SYSCALL_64_after_hwframe+0x44/0xa9 RIP: 0033:0x7fdc28a41f24 Code: 24 20 eb 8f 66 90 44 89 54 24 0c e8 56 68 f8 ff 44 8b 54 24 0c 44 89 e2 48 89 ee 41 89 c0 bf 9c ff ff ff b8 01 01 00 00 0f 05 <48> 3d 00 f0 ff ff 77 32 44 89 c7 89 44 24 0c e8 88 68 f8 ff 8b 44 RSP: 002b:7fdc24e25980 EFLAGS: 0293 ORIG_RAX: 0101 RAX: ffda RBX: 7fdc040008d0 RCX: 7fdc28a41f24 RDX: 0008 RSI: 564d4410a8c8 RDI: ff9c RBP: 564d4410a8c8 R08: R09: 0001 R10: R11: 0293 R12: 0008 R13: 564d4410e28a R14: 7fdc24e25b40 R15: 7fdc24e28fc0 Modules linked in: cmac nls_utf8 cifs fscache libdes ccm vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) eset_rtp(OE) xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype iptable_filter iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ip> snd_seq_midi coretemp snd_seq_midi_event snd_rawmidi kvm_intel snd_seq kvm dell_wmi snd_seq_device rapl dell_smbios snd_timer dcdbas intel_cstate input_leds iwlwifi serio_raw snd intel_wmi_thunderbolt rtsx_pci_ms dell_wmi_descriptor wmi_bmof processor_thermal_device ucsi_acp> pinctrl_cannonlake video pinctrl_intel ---[ end trace 80828f22da45a19b ]--- RIP:
[Kernel-packages] [Bug 1954676] Re: jammy 5.15 kernel soft lockup when zfs.ko is loaded on s390x w/ gcc >= 11.2.0-10ubuntu1 / gcc-11 PLT regression on s390x
JFYI, I've sent an SRU email to apply the kernel fix also to Impish 5.13, just to be safe in case the gcc patch lands in Impish: https://lists.ubuntu.com/archives/kernel-team/2022-February/127652.html ** Also affects: zfs-linux (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: gcc-11 (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Jammy) Status: New => Fix Committed ** No longer affects: zfs-linux (Ubuntu) ** No longer affects: zfs-linux (Ubuntu Impish) ** No longer affects: zfs-linux (Ubuntu Jammy) ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => Critical ** Changed in: linux (Ubuntu Impish) Importance: Undecided => High -- 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/1954676 Title: jammy 5.15 kernel soft lockup when zfs.ko is loaded on s390x w/ gcc >= 11.2.0-10ubuntu1 / gcc-11 PLT regression on s390x Status in Ubuntu on IBM z Systems: Fix Committed Status in gcc-11 package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Committed Status in gcc-11 source package in Impish: New Status in linux source package in Impish: New Status in gcc-11 source package in Jammy: Fix Released Status in linux source package in Jammy: Fix Committed Bug description: [Impact] Installing zfs-dkms seems to trigger a soft lockup issue as soon as zfs.ko is loaded. When the soft lockup happens the system isn't reachable anymore via ssh and on the console we can see some exlicit rcu stall warnings. This seems to happen only when zfs is compile with gcc >= 11.2.0-10ubuntu1. Downgrading gcc to previous versions doesn't show the problem and zfs is working just fine. [Test case] On s390x install the latest 5.15 Jammy kernel and run: apt install zfs-dkms [Fix] Temporary workaround is to build zfs with gcc-10 on s390x. [Regression potential] Building a kernel module with a different compiler is never 100% safe, we may experience potential crashes / panics if the ABI is not compatible. Moreover, if we build zfs with gcc-10 we are going to lose some of the performance benefits provided by gcc-11. However these regressions are limited to zfs on s390x and without this change zfs is broken anyway on this architecture. [Further analysis] @IBM Issue report to zfs upstream at https://github.com/openzfs/zfs/issues/12942 Reverting https://gcc.gnu.org/git/?p=gcc.git;a=patch;h=2335aa8771acd06b082d3e15d9f21ae0a802afd7 appears to make everything work, the compiled kernel and zfs.ko are loadable/unloadable once again. Please bring this issue to the attention of Ilya Leoshkevich Potentially this means we may have missbuilt userspace binaries in the archive for s390x. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1954676/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954676] Re: jammy 5.15 kernel soft lockup when zfs.ko is loaded on s390x w/ gcc >= 11.2.0-10ubuntu1 / gcc-11 PLT regression on s390x
I would reapply the gcc patch. It should not affect most userspace binaries - for example, it did not produce any changes whatsoever in SPEC suite. Even if there are some binaries that are built with kernel- like options and get extra relocations as a result, ld.so processes such relocations correctly, so nothing bad should happen. -- 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/1954676 Title: jammy 5.15 kernel soft lockup when zfs.ko is loaded on s390x w/ gcc >= 11.2.0-10ubuntu1 / gcc-11 PLT regression on s390x Status in Ubuntu on IBM z Systems: Fix Committed Status in gcc-11 package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: New Status in gcc-11 source package in Jammy: Fix Released Status in zfs-linux source package in Jammy: New Bug description: [Impact] Installing zfs-dkms seems to trigger a soft lockup issue as soon as zfs.ko is loaded. When the soft lockup happens the system isn't reachable anymore via ssh and on the console we can see some exlicit rcu stall warnings. This seems to happen only when zfs is compile with gcc >= 11.2.0-10ubuntu1. Downgrading gcc to previous versions doesn't show the problem and zfs is working just fine. [Test case] On s390x install the latest 5.15 Jammy kernel and run: apt install zfs-dkms [Fix] Temporary workaround is to build zfs with gcc-10 on s390x. [Regression potential] Building a kernel module with a different compiler is never 100% safe, we may experience potential crashes / panics if the ABI is not compatible. Moreover, if we build zfs with gcc-10 we are going to lose some of the performance benefits provided by gcc-11. However these regressions are limited to zfs on s390x and without this change zfs is broken anyway on this architecture. [Further analysis] @IBM Issue report to zfs upstream at https://github.com/openzfs/zfs/issues/12942 Reverting https://gcc.gnu.org/git/?p=gcc.git;a=patch;h=2335aa8771acd06b082d3e15d9f21ae0a802afd7 appears to make everything work, the compiled kernel and zfs.ko are loadable/unloadable once again. Please bring this issue to the attention of Ilya Leoshkevich Potentially this means we may have missbuilt userspace binaries in the archive for s390x. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1954676/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954676] Re: jammy 5.15 kernel soft lockup when zfs.ko is loaded on s390x w/ gcc >= 11.2.0-10ubuntu1 / gcc-11 PLT regression on s390x
@fheimes @iii-i thank you for this, we will include that patch into our kernels. Do you expect that the toolchain change may have affected any other binaries (ie. userspace binaries)? Or should we re-apply the reverted patch back in our gcc-11 (given the improvements that it brings)? -- 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/1954676 Title: jammy 5.15 kernel soft lockup when zfs.ko is loaded on s390x w/ gcc >= 11.2.0-10ubuntu1 / gcc-11 PLT regression on s390x Status in Ubuntu on IBM z Systems: Fix Committed Status in gcc-11 package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: New Status in gcc-11 source package in Jammy: Fix Released Status in zfs-linux source package in Jammy: New Bug description: [Impact] Installing zfs-dkms seems to trigger a soft lockup issue as soon as zfs.ko is loaded. When the soft lockup happens the system isn't reachable anymore via ssh and on the console we can see some exlicit rcu stall warnings. This seems to happen only when zfs is compile with gcc >= 11.2.0-10ubuntu1. Downgrading gcc to previous versions doesn't show the problem and zfs is working just fine. [Test case] On s390x install the latest 5.15 Jammy kernel and run: apt install zfs-dkms [Fix] Temporary workaround is to build zfs with gcc-10 on s390x. [Regression potential] Building a kernel module with a different compiler is never 100% safe, we may experience potential crashes / panics if the ABI is not compatible. Moreover, if we build zfs with gcc-10 we are going to lose some of the performance benefits provided by gcc-11. However these regressions are limited to zfs on s390x and without this change zfs is broken anyway on this architecture. [Further analysis] @IBM Issue report to zfs upstream at https://github.com/openzfs/zfs/issues/12942 Reverting https://gcc.gnu.org/git/?p=gcc.git;a=patch;h=2335aa8771acd06b082d3e15d9f21ae0a802afd7 appears to make everything work, the compiled kernel and zfs.ko are loadable/unloadable once again. Please bring this issue to the attention of Ilya Leoshkevich Potentially this means we may have missbuilt userspace binaries in the archive for s390x. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1954676/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1955591] Re: gpu hang on intel iris xe
current version as of now is 5.14.0.1020.17, was there any activity which could affect this issue? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1955591 Title: gpu hang on intel iris xe Status in linux-meta-oem-5.14 package in Ubuntu: New Bug description: see https://gitlab.freedesktop.org/drm/intel/-/issues/4530 happens with: linux-oem-20.04d/focal-updates 5.14.0.1011.11 does not happen with: linux-oem-20.04c/focal-updates,now 5.13.0.1022.26 so I assume the problematic patch causing this issue was backported to 20.04d. if so, the fix should also be backported... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-oem-5.14/+bug/1955591/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1957753] Re: net/mlx5e: EPERM on vlan 0 programming
This bug is awaiting verification that the linux/5.4.0-98.111 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- 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/1957753 Title: net/mlx5e: EPERM on vlan 0 programming Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: Fix Committed Status in linux source package in Hirsute: Won't Fix Status in linux source package in Impish: Fix Committed Status in linux source package in Jammy: In Progress Bug description: [Impact] There is an issue with hypervisor host side mlx5 driver operation on Bluefield devices in kernels <=5.16 From patch description: When using libvirt to passthrough VF to VM it will always set the VF vlan to 0 even if user didn’t request it, this will cause libvirt to fail to boot in case the PF isn't eswitch owner. Example of such case is the DPU host PF which isn't eswitch manager, so any attempt to passthrough VF of it using libvirt will fail. [Fix] * 7846665d net/mlx5e: Unblock setting vid 0 for VF in case PF isn't eswitch manager This patch can be cherry-picked into Impish and newer kernels, but it requires some backport work on F/H due to they're missing commit b55b3538 that split the legacy code out. The ESW_ALLOWED marco was later converted into a helper routine in commit b16f2bb6. [Test] Test kernels can be found here: F: https://people.canonical.com/~phlin/kernel/lp-1957753-mlx5e/F/ H: https://people.canonical.com/~phlin/kernel/lp-1957753-mlx5e/H/ I: https://people.canonical.com/~phlin/kernel/lp-1957753-mlx5e/I/ J: https://people.canonical.com/~phlin/kernel/lp-1957753-mlx5e/J/ Kernels tested on a SUT with this device by Dmitrii Shcherbakov, test passed with positive feedback. [Where problems could occur] If this patch is erroneous, it might cause issue to this mlx5 driver with certain operations (setting vid 0). And other programs such as libvirt that depends on this return value might be affected as well. [Original Bug Description] There is an issue with hypervisor host side mlx5 driver operation on Bluefield devices in kernels <=5.16 that was recently fixed in master with a one-liner: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7846665d3504812acaebf920d1141851379a7f37 It would be good to have this fix in Focal+ kernels. This is not needed in https://bugs.launchpad.net/ubuntu/+source/linux- bluefield since it's used at the DPU side whereas the issue in question affects the hypervisor side. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957753/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958990] Re: Add sunrpc module parameters for NFSv3 nconnect
** Changed in: linux-azure (Ubuntu Jammy) Status: New => Fix Committed ** Changed in: linux-azure (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux-azure (Ubuntu Jammy) Assignee: (unassigned) => Tim Gardner (timg-tpi) ** Also affects: linux-azure-5.11 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-azure-5.11 (Ubuntu Focal) Status: New => Fix Committed ** Changed in: linux-azure-5.11 (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux-azure-5.11 (Ubuntu Focal) Assignee: (unassigned) => Tim Gardner (timg-tpi) ** Changed in: linux-azure-5.11 (Ubuntu Impish) Status: New => Invalid ** Changed in: linux-azure-5.11 (Ubuntu Jammy) Status: New => Invalid -- 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/1958990 Title: Add sunrpc module parameters for NFSv3 nconnect Status in linux-azure package in Ubuntu: Fix Committed Status in linux-azure-5.11 package in Ubuntu: Invalid Status in linux-azure source package in Focal: Fix Committed Status in linux-azure-5.11 source package in Focal: Fix Committed Status in linux-azure source package in Impish: Fix Committed Status in linux-azure-5.11 source package in Impish: Invalid Status in linux-azure source package in Jammy: Fix Committed Status in linux-azure-5.11 source package in Jammy: Invalid Bug description: SRU Justification [Impact] Microsoft has requested the addition of 2 module parameters to sunrpc. The primary purpose of which is to restrict or pin NFSv3 TCP connections to one server in order to take advantage of local server connection caching. In the presence of a load balancer, round robin connection requests defeats the advantages of local caching. [Test Plan] Microsoft tested [Where things could go wrong] NFSv3 connection attempts could be slow or fail altogether. [Other Info] SF: #00312346 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1958990/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1922099] Re: nvidia-graphics-drivers-390/390.141-0ubuntu0.20.10.1 ADT test failure with linux/5.8.0-49.55 on armhf
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux (Ubuntu Focal) Status: New => Confirmed -- 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/1922099 Title: nvidia-graphics-drivers-390/390.141-0ubuntu0.20.10.1 ADT test failure with linux/5.8.0-49.55 on armhf Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in linux source package in Focal: Confirmed Status in nvidia-graphics-drivers-390 source package in Focal: Confirmed Status in linux source package in Groovy: Invalid Status in nvidia-graphics-drivers-390 source package in Groovy: Invalid Bug description: This is a scripted bug report about ADT failures while running nvidia- graphics-drivers-390 tests for linux/5.8.0-49.55 on groovy. Whether this is caused by the tested source or the kernel has, yet, to be determined. Testing failed on: armhf: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy/groovy/armhf/n/nvidia-graphics-drivers-390/20210330_222456_fdb1a@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922099/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1922099] Re: nvidia-graphics-drivers-390/390.141-0ubuntu0.20.10.1 ADT test failure with linux/5.8.0-49.55 on armhf
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-390 (Ubuntu Focal) Status: New => Confirmed -- 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/1922099 Title: nvidia-graphics-drivers-390/390.141-0ubuntu0.20.10.1 ADT test failure with linux/5.8.0-49.55 on armhf Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in linux source package in Focal: Confirmed Status in nvidia-graphics-drivers-390 source package in Focal: Confirmed Status in linux source package in Groovy: Invalid Status in nvidia-graphics-drivers-390 source package in Groovy: Invalid Bug description: This is a scripted bug report about ADT failures while running nvidia- graphics-drivers-390 tests for linux/5.8.0-49.55 on groovy. Whether this is caused by the tested source or the kernel has, yet, to be determined. Testing failed on: armhf: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy/groovy/armhf/n/nvidia-graphics-drivers-390/20210330_222456_fdb1a@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922099/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958990] Re: Add sunrpc module parameters for NFSv3 nconnect
** Changed in: linux-azure (Ubuntu Impish) Status: New => Fix Committed ** Changed in: linux-azure (Ubuntu Impish) Importance: Undecided => Medium ** Changed in: linux-azure (Ubuntu Impish) Assignee: (unassigned) => Tim Gardner (timg-tpi) ** Changed in: linux-azure (Ubuntu Focal) Importance: Undecided => Medium -- 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/1958990 Title: Add sunrpc module parameters for NFSv3 nconnect Status in linux-azure package in Ubuntu: New Status in linux-azure source package in Focal: Fix Committed Status in linux-azure source package in Impish: Fix Committed Status in linux-azure source package in Jammy: New Bug description: SRU Justification [Impact] Microsoft has requested the addition of 2 module parameters to sunrpc. The primary purpose of which is to restrict or pin NFSv3 TCP connections to one server in order to take advantage of local server connection caching. In the presence of a load balancer, round robin connection requests defeats the advantages of local caching. [Test Plan] Microsoft tested [Where things could go wrong] NFSv3 connection attempts could be slow or fail altogether. [Other Info] SF: #00312346 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1958990/+subscriptions -- Mailing list: https://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 1959477] Re: USB dies, GUI hangs after plugging in Brother DS-740D scanner
Op 02-02-2022 om 13:59 schreef Isaac True: > This seems to be related to > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956849 > > The dmesg output is the same as mine when the host controller stops > working: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956849/comments/13 > > Are you using the 5.13 HWE kernel? $ uname -a Linux precies 5.4.0-96-generic #109-Ubuntu SMP Wed Jan 12 16:49:16 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux Is that what you were looking for? -maarten -- 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/1959477 Title: USB dies, GUI hangs after plugging in Brother DS-740D scanner Status in linux package in Ubuntu: New Bug description: The Brother DS-740D scanner I have used to work fine until a couple of weeks ago. Now, whenever I plug it the GUI freezes (default Ubuntu LTS 20.04). Logging in from another computer works. Restarting GDM3 does not help, mouse is frozen. No crash log. But kern.log says: Jan 29 10:12:25 precies kernel: [ 1129.014431] xhci_hcd :00:14.0: Abort failed to stop command ring: -110 Jan 29 10:12:25 precies kernel: [ 1129.014437] xhci_hcd :00:14.0: xHCI host controller not responding, assume dead Jan 29 10:12:25 precies kernel: [ 1129.01] xhci_hcd :00:14.0: HC died; cleaning up Jan 29 10:12:25 precies kernel: [ 1129.014477] xhci_hcd :00:14.0: Timeout while waiting for setup device command I tried updating the driver to the latest version (brscan5-1.2.9-0.amd64.deb) but that did not help. Additional info: $ lsb_release -rd Description:Ubuntu 20.04.3 LTS Release:20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1959477/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958990] Re: Add sunrpc module parameters for NFSv3 nconnect
** Changed in: linux-azure (Ubuntu Focal) Status: New => Fix Committed ** Changed in: linux-azure (Ubuntu Focal) Assignee: (unassigned) => Tim Gardner (timg-tpi) -- 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/1958990 Title: Add sunrpc module parameters for NFSv3 nconnect Status in linux-azure package in Ubuntu: New Status in linux-azure source package in Focal: Fix Committed Status in linux-azure source package in Impish: New Status in linux-azure source package in Jammy: New Bug description: SRU Justification [Impact] Microsoft has requested the addition of 2 module parameters to sunrpc. The primary purpose of which is to restrict or pin NFSv3 TCP connections to one server in order to take advantage of local server connection caching. In the presence of a load balancer, round robin connection requests defeats the advantages of local caching. [Test Plan] Microsoft tested [Where things could go wrong] NFSv3 connection attempts could be slow or fail altogether. [Other Info] SF: #00312346 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1958990/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1957094] Re: on-demand mode doesn't work with nvidia-390
I have also fixed the part of the test-plan that Chris mentioned. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1957094 Title: on-demand mode doesn't work with nvidia-390 Status in OEM Priority Project: New Status in nvidia-settings package in Ubuntu: New Status in ubuntu-drivers-common package in Ubuntu: Fix Committed Status in ubuntu-drivers-common source package in Focal: Fix Committed Status in nvidia-settings source package in Impish: New Status in ubuntu-drivers-common source package in Impish: Fix Committed Status in nvidia-settings source package in Jammy: New Status in ubuntu-drivers-common source package in Jammy: Fix Committed Bug description: [Impact] * In any Ubuntu series, if user using a old GPU (which supported by nvidia-390 only) then issuing glxinfo will get "Error: couldn't find RGB GLX visual or fbconfig". Which mean the Xorg doesn't load dri driver correctly. [Test Plan] * install nvidia-390 on nvidia-390 supported system. * prime-select on-demand * reboot * glxinfo * after applying this patch, it will fall back to "ON" mode after reboot. * install nvidia-450 on nvidia-450 supported system. * prime-select on-demand * reboot the system * prime-select query (and check that on-demand mode is still in use). [Where problems could occur] * Since nvidia-390 doesn't support on-demand mode (RTD3 either). If a user stays in on-demand mode with 390 without problem, the after upgrading u-d-c and reboot. The mode will fall back to "ON" mode. * From my point of view, it's fine because nvidia-390 doesn't support RTD3. Thus, the nvidia will always stay in "Active" stage no matter which mode it is. * While there is no way to inform the user about this change, changing to the only supported default will avoid breaking GLX. --- The regression from https://bugs.launchpad.net/ubuntu/+source/ubuntu- drivers-common/+bug/1942789. It impacts Jammy and Impish so far. [Steps to reproduce] 1. Find a GPU supports nvidia-390 2. ubuntu-drivers install nvidia:390 3. prime-select on-demand 4. glxinfo [Expected result] Shows intel or nvidia drives monitor [Actual result] Error: couldn't find RGB GLX visual or fbconfig Since we are all agree "on-demand" mode as default mode. Pre-talk with Alberto, on-demand doesn't support with nvidia-390 (no matter RTD3). We could consider to make it as performance mode and leave a note on nvidia-settings. I'll prepare some test packages. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1957094/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1957094] Re: on-demand mode doesn't work with nvidia-390
I suppose I could simply detect the version in nvidia-settings. I already have code that does that in a different patch that I wrote for nvidia-settings. ** Description changed: [Impact] * In any Ubuntu series, if user using a old GPU (which supported by nvidia-390 only) then issuing glxinfo will get "Error: couldn't find RGB GLX visual or fbconfig". Which mean the Xorg doesn't load dri driver correctly. [Test Plan] * install nvidia-390 on nvidia-390 supported system. * prime-select on-demand * reboot * glxinfo * after applying this patch, it will fall back to "ON" mode after reboot. - * install nvidia-450 on nvidia-450 supported system. - * prime-select on-demand - * + * install nvidia-450 on nvidia-450 supported system. + * prime-select on-demand + * reboot the system + * prime-select query (and check that on-demand mode is still in use). [Where problems could occur] * Since nvidia-390 doesn't support on-demand mode (RTD3 either). If a user stays in on-demand mode with 390 without problem, the after upgrading u-d-c and reboot. The mode will fall back to "ON" mode. * From my point of view, it's fine because nvidia-390 doesn't support RTD3. Thus, the nvidia will always stay in "Active" stage no matter which mode it is. * While there is no way to inform the user about this change, changing to the only supported default will avoid breaking GLX. --- The regression from https://bugs.launchpad.net/ubuntu/+source/ubuntu- drivers-common/+bug/1942789. It impacts Jammy and Impish so far. [Steps to reproduce] 1. Find a GPU supports nvidia-390 2. ubuntu-drivers install nvidia:390 3. prime-select on-demand 4. glxinfo [Expected result] Shows intel or nvidia drives monitor [Actual result] Error: couldn't find RGB GLX visual or fbconfig Since we are all agree "on-demand" mode as default mode. Pre-talk with Alberto, on-demand doesn't support with nvidia-390 (no matter RTD3). We could consider to make it as performance mode and leave a note on nvidia-settings. I'll prepare some test packages. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1957094 Title: on-demand mode doesn't work with nvidia-390 Status in OEM Priority Project: New Status in nvidia-settings package in Ubuntu: New Status in ubuntu-drivers-common package in Ubuntu: Fix Committed Status in ubuntu-drivers-common source package in Focal: Fix Committed Status in nvidia-settings source package in Impish: New Status in ubuntu-drivers-common source package in Impish: Fix Committed Status in nvidia-settings source package in Jammy: New Status in ubuntu-drivers-common source package in Jammy: Fix Committed Bug description: [Impact] * In any Ubuntu series, if user using a old GPU (which supported by nvidia-390 only) then issuing glxinfo will get "Error: couldn't find RGB GLX visual or fbconfig". Which mean the Xorg doesn't load dri driver correctly. [Test Plan] * install nvidia-390 on nvidia-390 supported system. * prime-select on-demand * reboot * glxinfo * after applying this patch, it will fall back to "ON" mode after reboot. * install nvidia-450 on nvidia-450 supported system. * prime-select on-demand * reboot the system * prime-select query (and check that on-demand mode is still in use). [Where problems could occur] * Since nvidia-390 doesn't support on-demand mode (RTD3 either). If a user stays in on-demand mode with 390 without problem, the after upgrading u-d-c and reboot. The mode will fall back to "ON" mode. * From my point of view, it's fine because nvidia-390 doesn't support RTD3. Thus, the nvidia will always stay in "Active" stage no matter which mode it is. * While there is no way to inform the user about this change, changing to the only supported default will avoid breaking GLX. --- The regression from https://bugs.launchpad.net/ubuntu/+source/ubuntu- drivers-common/+bug/1942789. It impacts Jammy and Impish so far. [Steps to reproduce] 1. Find a GPU supports nvidia-390 2. ubuntu-drivers install nvidia:390 3. prime-select on-demand 4. glxinfo [Expected result] Shows intel or nvidia drives monitor [Actual result] Error: couldn't find RGB GLX visual or fbconfig Since we are all agree "on-demand" mode as default mode. Pre-talk with Alberto, on-demand doesn't support with nvidia-390 (no matter RTD3). We could consider to make it as performance mode and leave a note on nvidia-settings. I'll prepare some test packages. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1957094/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More
[Kernel-packages] [Bug 1959477] Re: USB dies, GUI hangs after plugging in Brother DS-740D scanner
This seems to be related to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956849 The dmesg output is the same as mine when the host controller stops working: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956849/comments/13 Are you using the 5.13 HWE kernel? -- 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/1959477 Title: USB dies, GUI hangs after plugging in Brother DS-740D scanner Status in linux package in Ubuntu: New Bug description: The Brother DS-740D scanner I have used to work fine until a couple of weeks ago. Now, whenever I plug it the GUI freezes (default Ubuntu LTS 20.04). Logging in from another computer works. Restarting GDM3 does not help, mouse is frozen. No crash log. But kern.log says: Jan 29 10:12:25 precies kernel: [ 1129.014431] xhci_hcd :00:14.0: Abort failed to stop command ring: -110 Jan 29 10:12:25 precies kernel: [ 1129.014437] xhci_hcd :00:14.0: xHCI host controller not responding, assume dead Jan 29 10:12:25 precies kernel: [ 1129.01] xhci_hcd :00:14.0: HC died; cleaning up Jan 29 10:12:25 precies kernel: [ 1129.014477] xhci_hcd :00:14.0: Timeout while waiting for setup device command I tried updating the driver to the latest version (brscan5-1.2.9-0.amd64.deb) but that did not help. Additional info: $ lsb_release -rd Description:Ubuntu 20.04.3 LTS Release:20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1959477/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1959762] [NEW] HID_ASUS should depend on USB_HID in stable v4.15 backports
Public bug reported:
[Impact]
Backported to bionic/linux commit f83baa0cb6cf ("HID: add hid_is_usb() function
to make it simpler for USB detection") brings to HID_ASUS usage of hid_is_usb()
which is provided by USB_HID. If HID_ASUS is built as module but USB_HID is
not, the kernel build will fail (like linux-azure) did:
ERROR: "usb_hid_driver" [drivers/hid/hid-asus.ko] undefined!
[Fix]
Because of backport of commit commit f83baa0cb6cf ("HID: add
hid_is_usb() function to make it simpler for USB detection"), the
bionic/linux needs also backport of commit c4f0126d487f ("HID: asus: Add
depends on USB_HID to HID_ASUS Kconfig option").
[Test Plan]
Build HID_ASUS as module with or without USB_HID.
[Where problems could occur]
It's a new KConfig dependency, so configs using HID_ASUS without USB_HID
will loose HID_ASUS. This is expected, so no problems should occur.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Tags: bionic
** Tags added: bionic
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Description changed:
+ [Impact]
+
Backported to bionic/linux commit f83baa0cb6cf ("HID: add hid_is_usb()
function to make it simpler for USB detection") brings to HID_ASUS usage of
hid_is_usb() which is provided by USB_HID. If HID_ASUS is built as module but
USB_HID is not, the kernel build will fail (like linux-azure) did:
- ERROR: "usb_hid_driver" [drivers/hid/hid-asus.ko] undefined!
+ ERROR: "usb_hid_driver" [drivers/hid/hid-asus.ko] undefined!
+
+ [Fix]
Because of backport of commit commit f83baa0cb6cf ("HID: add
hid_is_usb() function to make it simpler for USB detection"), the
bionic/linux needs also backport of commit c4f0126d487f ("HID: asus: Add
depends on USB_HID to HID_ASUS Kconfig option").
+
+ [Test Plan]
+
+ Build HID_ASUS as module with or without USB_HID.
+
+ [Where problems could occur]
+
+ It's a new KConfig dependency, so configs using HID_ASUS without USB_HID
+ will loose HID_ASUS. This is expected, so no problems should occur.
--
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/1959762
Title:
HID_ASUS should depend on USB_HID in stable v4.15 backports
Status in linux package in Ubuntu:
New
Status in linux source package in Bionic:
New
Bug description:
[Impact]
Backported to bionic/linux commit f83baa0cb6cf ("HID: add hid_is_usb()
function to make it simpler for USB detection") brings to HID_ASUS usage of
hid_is_usb() which is provided by USB_HID. If HID_ASUS is built as module but
USB_HID is not, the kernel build will fail (like linux-azure) did:
ERROR: "usb_hid_driver" [drivers/hid/hid-asus.ko] undefined!
[Fix]
Because of backport of commit commit f83baa0cb6cf ("HID: add
hid_is_usb() function to make it simpler for USB detection"), the
bionic/linux needs also backport of commit c4f0126d487f ("HID: asus:
Add depends on USB_HID to HID_ASUS Kconfig option").
[Test Plan]
Build HID_ASUS as module with or without USB_HID.
[Where problems could occur]
It's a new KConfig dependency, so configs using HID_ASUS without
USB_HID will loose HID_ASUS. This is expected, so no problems should
occur.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1959762/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1959759] Re: bluez-firmware is actually needed
** Description changed: bluez-firmware is in sync-blacklist, but also repackaged in snappy-dev PPA and installed in pi-kernel snaps. Some of the firmware files shipped in bluez-firmware are not present in neither src:linux-firmware nor src:linux-firmware-raspi It seems like it is an oversight, and we should sync bluez-firmware from Debian. $ syncpackage bluez-firmware Source package bluez-firmware is blacklisted. If this package needs a fakesync, use --fakesync If you think this package shouldn't be blacklisted, please file a bug explaining your reasoning and subscribe ~ubuntu-archive. Blacklist Comments: From sync-blacklist.txt: # benc: we do our own kernel bluez-firmware Missing in ubuntu: BCM2033-FW.bin BCM2033-MD.hex STLC2500_R4_00_03.ptc STLC2500_R4_00_06.ssf STLC2500_R4_02_02_WLAN.ssf STLC2500_R4_02_04.ptc Available in linux-firmware-raspi2 (conflicting): BCM43430A1.hcd BCM43430B0.hcd BCM4345C0.hcd BCM4345C5.hcd + + Alternative to syncing bluez-firmware, is to ship missing in ubuntu + files in linux-firmware ** Description changed: bluez-firmware is in sync-blacklist, but also repackaged in snappy-dev PPA and installed in pi-kernel snaps. Some of the firmware files shipped in bluez-firmware are not present in neither src:linux-firmware nor src:linux-firmware-raspi It seems like it is an oversight, and we should sync bluez-firmware from Debian. $ syncpackage bluez-firmware Source package bluez-firmware is blacklisted. If this package needs a fakesync, use --fakesync If you think this package shouldn't be blacklisted, please file a bug explaining your reasoning and subscribe ~ubuntu-archive. Blacklist Comments: From sync-blacklist.txt: # benc: we do our own kernel bluez-firmware Missing in ubuntu: BCM2033-FW.bin BCM2033-MD.hex STLC2500_R4_00_03.ptc STLC2500_R4_00_06.ssf STLC2500_R4_02_02_WLAN.ssf STLC2500_R4_02_04.ptc Available in linux-firmware-raspi2 (conflicting): BCM43430A1.hcd BCM43430B0.hcd BCM4345C0.hcd BCM4345C5.hcd Alternative to syncing bluez-firmware, is to ship missing in ubuntu - files in linux-firmware + files in linux-firmware, but that would not be in line with what we do + for many other firmware packages which are easier to update when they + are stand alone. ** Changed in: linux-firmware (Ubuntu) Status: New => Triaged ** Changed in: linux-firmware-raspi (Ubuntu) Status: New => Triaged ** Summary changed: - bluez-firmware is actually needed + Please remove bluez-firmware from sync denylist -- 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/1959759 Title: Please remove bluez-firmware from sync denylist Status in linux-firmware package in Ubuntu: Triaged Status in linux-firmware-raspi package in Ubuntu: Triaged Bug description: bluez-firmware is in sync-blacklist, but also repackaged in snappy-dev PPA and installed in pi-kernel snaps. Some of the firmware files shipped in bluez-firmware are not present in neither src:linux-firmware nor src:linux-firmware-raspi It seems like it is an oversight, and we should sync bluez-firmware from Debian. $ syncpackage bluez-firmware Source package bluez-firmware is blacklisted. If this package needs a fakesync, use --fakesync If you think this package shouldn't be blacklisted, please file a bug explaining your reasoning and subscribe ~ubuntu-archive. Blacklist Comments: From sync-blacklist.txt: # benc: we do our own kernel bluez-firmware Missing in ubuntu: BCM2033-FW.bin BCM2033-MD.hex STLC2500_R4_00_03.ptc STLC2500_R4_00_06.ssf STLC2500_R4_02_02_WLAN.ssf STLC2500_R4_02_04.ptc Available in linux-firmware-raspi2 (conflicting): BCM43430A1.hcd BCM43430B0.hcd BCM4345C0.hcd BCM4345C5.hcd Alternative to syncing bluez-firmware, is to ship missing in ubuntu files in linux-firmware, but that would not be in line with what we do for many other firmware packages which are easier to update when they are stand alone. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1959759/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1959760] [NEW] Broken displayport driver
Public bug reported: Using Dell D3100 docking station with dell xps13 with latest version of the Displayport drivers. After kernel installation on reboot external monitor not detected anymore Last working kernel is 5.11 lsb_release -rd Description:Linux Mint 20.3 Release:20.3 ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1959760 Title: Broken displayport driver Status in linux package in Ubuntu: New Bug description: Using Dell D3100 docking station with dell xps13 with latest version of the Displayport drivers. After kernel installation on reboot external monitor not detected anymore Last working kernel is 5.11 lsb_release -rd Description: Linux Mint 20.3 Release: 20.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1959760/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1959759] [NEW] bluez-firmware is actually needed
Public bug reported: bluez-firmware is in sync-blacklist, but also repackaged in snappy-dev PPA and installed in pi-kernel snaps. Some of the firmware files shipped in bluez-firmware are not present in neither src:linux-firmware nor src:linux-firmware-raspi It seems like it is an oversight, and we should sync bluez-firmware from Debian. $ syncpackage bluez-firmware Source package bluez-firmware is blacklisted. If this package needs a fakesync, use --fakesync If you think this package shouldn't be blacklisted, please file a bug explaining your reasoning and subscribe ~ubuntu-archive. Blacklist Comments: From sync-blacklist.txt: # benc: we do our own kernel bluez-firmware Missing in ubuntu: BCM2033-FW.bin BCM2033-MD.hex STLC2500_R4_00_03.ptc STLC2500_R4_00_06.ssf STLC2500_R4_02_02_WLAN.ssf STLC2500_R4_02_04.ptc Available in linux-firmware-raspi2 (conflicting): BCM43430A1.hcd BCM43430B0.hcd BCM4345C0.hcd BCM4345C5.hcd ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Affects: linux-firmware-raspi (Ubuntu) Importance: Undecided Status: New ** Package changed: ubuntu => linux-firmware (Ubuntu) ** Description changed: bluez-firmware is in sync-blacklist, but also repackaged in snappy-dev PPA and installed in pi-kernel snaps. Some of the firmware files shipped in bluez-firmware are not present in neither src:linux-firmware nor src:linux-firmware-raspi It seems like it is an oversight, and we should sync bluez-firmware from Debian. $ syncpackage bluez-firmware Source package bluez-firmware is blacklisted. If this package needs a fakesync, use --fakesync If you think this package shouldn't be blacklisted, please file a bug explaining your reasoning and subscribe ~ubuntu-archive. Blacklist Comments: - From sync-blacklist.txt: - # benc: we do our own kernel - bluez-firmware + From sync-blacklist.txt: + # benc: we do our own kernel + bluez-firmware + + BCM2033-FW.bin + BCM2033-MD.hex + STLC2500_R4_00_03.ptc + STLC2500_R4_00_06.ssf + STLC2500_R4_02_02_WLAN.ssf + STLC2500_R4_02_04.ptc + + Appear to be missing in Ubuntu ** Description changed: bluez-firmware is in sync-blacklist, but also repackaged in snappy-dev PPA and installed in pi-kernel snaps. Some of the firmware files shipped in bluez-firmware are not present in neither src:linux-firmware nor src:linux-firmware-raspi It seems like it is an oversight, and we should sync bluez-firmware from Debian. $ syncpackage bluez-firmware Source package bluez-firmware is blacklisted. If this package needs a fakesync, use --fakesync If you think this package shouldn't be blacklisted, please file a bug explaining your reasoning and subscribe ~ubuntu-archive. Blacklist Comments: From sync-blacklist.txt: # benc: we do our own kernel bluez-firmware + Missing in ubuntu: BCM2033-FW.bin BCM2033-MD.hex STLC2500_R4_00_03.ptc STLC2500_R4_00_06.ssf STLC2500_R4_02_02_WLAN.ssf STLC2500_R4_02_04.ptc - Appear to be missing in Ubuntu + Available in linux-firmware-raspi2 (conflicting): + BCM43430A1.hcd + BCM43430B0.hcd + BCM4345C0.hcd + BCM4345C5.hcd ** Also affects: linux-firmware-raspi (Ubuntu) Importance: Undecided Status: New -- 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/1959759 Title: bluez-firmware is actually needed Status in linux-firmware package in Ubuntu: New Status in linux-firmware-raspi package in Ubuntu: New Bug description: bluez-firmware is in sync-blacklist, but also repackaged in snappy-dev PPA and installed in pi-kernel snaps. Some of the firmware files shipped in bluez-firmware are not present in neither src:linux-firmware nor src:linux-firmware-raspi It seems like it is an oversight, and we should sync bluez-firmware from Debian. $ syncpackage bluez-firmware Source package bluez-firmware is blacklisted. If this package needs a fakesync, use --fakesync If you think this package shouldn't be blacklisted, please file a bug explaining your reasoning and subscribe ~ubuntu-archive. Blacklist Comments: From sync-blacklist.txt: # benc: we do our own kernel bluez-firmware Missing in ubuntu: BCM2033-FW.bin BCM2033-MD.hex STLC2500_R4_00_03.ptc STLC2500_R4_00_06.ssf STLC2500_R4_02_02_WLAN.ssf STLC2500_R4_02_04.ptc Available in linux-firmware-raspi2 (conflicting): BCM43430A1.hcd BCM43430B0.hcd BCM4345C0.hcd BCM4345C5.hcd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1959759/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1959759] [NEW] bluez-firmware is actually needed
You have been subscribed to a public bug: bluez-firmware is in sync-blacklist, but also repackaged in snappy-dev PPA and installed in pi-kernel snaps. Some of the firmware files shipped in bluez-firmware are not present in neither src:linux-firmware nor src:linux-firmware-raspi It seems like it is an oversight, and we should sync bluez-firmware from Debian. $ syncpackage bluez-firmware Source package bluez-firmware is blacklisted. If this package needs a fakesync, use --fakesync If you think this package shouldn't be blacklisted, please file a bug explaining your reasoning and subscribe ~ubuntu-archive. Blacklist Comments: From sync-blacklist.txt: # benc: we do our own kernel bluez-firmware ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New -- bluez-firmware is actually needed https://bugs.launchpad.net/bugs/1959759 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware 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 1959746] Re: touchpad/keyboard actions not working
** Package changed: ubuntu => linux-signed-hwe-5.13 (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1959746 Title: touchpad/keyboard actions not working Status in linux-signed-hwe-5.13 package in Ubuntu: New Bug description: Touchpad not working and not appearing inside xinput list and cat /proc/bus/input/devices. Battery percentage not appearing on the top bar. Keyboard actions not working. Computer : HP ENVY x360 Convert 15-eu0020nf. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-28-generic 5.13.0-28.31~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Feb 2 09:29:42 2022 InstallationDate: Installed on 2022-01-22 (10 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1959746/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1959746] [NEW] touchpad/keyboard actions not working
You have been subscribed to a public bug: Touchpad not working and not appearing inside xinput list and cat /proc/bus/input/devices. Battery percentage not appearing on the top bar. Keyboard actions not working. Computer : HP ENVY x360 Convert 15-eu0020nf. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-28-generic 5.13.0-28.31~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Feb 2 09:29:42 2022 InstallationDate: Installed on 2022-01-22 (10 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.13 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- touchpad/keyboard actions not working https://bugs.launchpad.net/bugs/1959746 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.13 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 1959665] Re: linux-image-5.4.0-97.110 freezes by accessing cifs shares
Just a quick heads up on my tests with different kernel versions. I have installed all available Updates for Ubuntu 20.04 (including samba-*= 2:4.13.17~dfsg-0ubuntu0.21.04.1; CVE-2022-0336). These are the results: GA: 5.4.0-98.111~lp1959665.1 -> no freezes in 3 hours of testing 5.4.0-97.110 -> still keeps freezing HWE: 5.13.0-27.29~20.04.1 -> no freezes in 1 hour of testing 5.13.0-28.31~20.04.1 -> no freezes in 1 hour of testing ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-0336 -- 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/1959665 Title: linux-image-5.4.0-97.110 freezes by accessing cifs shares Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: In Progress Bug description: Ubuntu 20.04 with kernel image 5.4.0-97.110 randomly freezes when we access cifs shares. The system needs a hard reset after the freeze. The previous kernel image (5.4.0-96.109) does not show this behavior. Multiple Ubuntu 20.04 systems running on kernel image 9.4.0-97.110 are affected on our sites. The cifs shares are accessed via autofs using Kerberos authentication. The following info is the only error message we could actively catch on a different system before the system was frozen: general protection fault: [#3] SMP PTI CPU: 0 PID: 21294 Comm: automount Tainted: G DOE 5.4.0-97-generic #110-Ubuntu Hardware name: Dell Inc. Precision 7530/03RV2M, BIOS 1.14.4 10/21/2020 RIP: 0010:kmem_cache_alloc_trace+0x8c/0x240 Code: 08 65 4c 03 05 1d e8 f7 6e 49 83 78 10 00 4d 8b 38 0f 84 92 01 00 00 4d 85 ff 0f 84 89 01 00 00 41 8b 41 20 49 8b 39 4c 01 f8 <48> 8b 18 48 89 c1 49 33 99 70 01 00 00 4c 89 f8 48 0f c9 48 31 cb RSP: 0018:a6ca860f7ba0 EFLAGS: 00010286 RAX: fdd44d7c219190e1 RBX: RCX: RDX: d558 RSI: 0cc0 RDI: 00035060 RBP: a6ca860f7bd0 R08: 99233c035060 R09: 992338c079c0 R10: 0001 R11: 0004 R12: 0cc0 R13: 000b R14: 992338c079c0 R15: fdd44d7c219190e1 FS: 7fdc24e29700() GS:99233c00() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 7f15a80ee010 CR3: 0007e36b2006 CR4: 003606f0 Call Trace: ? proc_self_get_link+0x70/0xd0 proc_self_get_link+0x70/0xd0 link_path_walk.part.0+0x478/0x550 ? trailing_symlink+0x1d1/0x280 path_openat+0xb7/0x290 do_filp_open+0x91/0x100 ? unuse_pde+0x30/0x30 do_sys_open+0x17e/0x290 __x64_sys_openat+0x20/0x30 __orig_openat+0x71/0xc0 [eset_rtp] ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __x64_sys_futex+0x13f/0x170 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 __x64_sys_ertp_openat+0x29/0x60 [eset_rtp] do_syscall_64+0x57/0x190 entry_SYSCALL_64_after_hwframe+0x44/0xa9 RIP: 0033:0x7fdc28a41f24 Code: 24 20 eb 8f 66 90 44 89 54 24 0c e8 56 68 f8 ff 44 8b 54 24 0c 44 89 e2 48 89 ee 41 89 c0 bf 9c ff ff ff b8 01 01 00 00 0f 05 <48> 3d 00 f0 ff ff 77 32 44 89 c7 89 44 24 0c e8 88 68 f8 ff 8b 44 RSP: 002b:7fdc24e25980 EFLAGS: 0293 ORIG_RAX: 0101 RAX: ffda RBX: 7fdc040008d0 RCX: 7fdc28a41f24 ? unuse_pde+0x30/0x30 do_sys_open+0x17e/0x290 __x64_sys_openat+0x20/0x30 __orig_openat+0x71/0xc0 [eset_rtp] ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __x64_sys_futex+0x13f/0x170 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 __x64_sys_ertp_openat+0x29/0x60 [eset_rtp] do_syscall_64+0x57/0x190 entry_SYSCALL_64_after_hwframe+0x44/0xa9 RIP: 0033:0x7fdc28a41f24 Code: 24 20 eb 8f 66 90 44 89 54 24 0c e8 56 68 f8 ff 44 8b 54 24 0c 44 89 e2 48 89 ee 41 89 c0 bf 9c ff ff ff b8 01 01 00 00 0f 05 <48> 3d 00 f0 ff ff 77 32 44 89 c7 89 44 24 0c e8 88 68 f8 ff 8b 44 RSP: 002b:7fdc24e25980 EFLAGS: 0293 ORIG_RAX: 0101 RAX: ffda RBX: 7fdc040008d0 RCX: 7fdc28a41f24 RDX: 0008 RSI: 564d4410a8c8 RDI: ff9c RBP: 564d4410a8c8 R08: R09: 0001 R10: R11: 0293 R12: 0008 R13: 564d4410e28a R14: 7fdc24e25b40 R15: 7fdc24e28fc0 Modules linked in: cmac nls_utf8 cifs fscache libdes ccm vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) eset_rtp(OE) xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype iptable_filter iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ip> snd_seq_midi coretemp snd_seq_midi_event snd_rawmidi kvm_intel snd_seq kvm dell_wmi
[Kernel-packages] [Bug 1956238] Re: [BlueField] Unable to set TCP MD5SIG option on socket
This bug was fixed in the package linux-bluefield - 5.4.0-1026.29 --- linux-bluefield (5.4.0-1026.29) focal; urgency=medium * focal/linux-bluefield: 5.4.0-1026.29 -proposed tracker (LP: #1955220) * [BlueField] Unable to set TCP MD5SIG option on socket (LP: #1956238) - [Config] CONFIG_TCP_MD5SIG=y [ Ubuntu: 5.4.0-97.110 ] * icmp_redirect from selftests fails on F/kvm (unary operator expected) (LP: #1938964) - selftests: icmp_redirect: pass xfail=0 to log_test() * Focal: CIFS stable updates (LP: #1954926) - cifs: use the expiry output of dns_query to schedule next resolution - cifs: set a minimum of 120s for next dns resolution - cifs: To match file servers, make sure the server hostname matches * seccomp_bpf in seccomp from ubuntu_kernel_selftests failed to build on B-5.4 (LP: #1896420) - SAUCE: selftests/seccomp: fix "storage size of 'md' isn't known" build issue - SAUCE: selftests/seccomp: Fix s390x regs not defined issue * system crash when removing ipmi_msghandler module (LP: #1950666) - ipmi: Move remove_work to dedicated workqueue - ipmi: msghandler: Make symbol 'remove_work_wq' static * zcrypt DD: Toleration for new IBM Z Crypto Hardware - (Backport to Ubuntu 20.04) (LP: #1954680) - s390/AP: support new dynamic AP bus size limit * [UBUNTU 20.04] KVM hardware diagnose data improvements for guest kernel - kernel part (LP: #1953334) - s390/setup: diag 318: refactor struct - s390/kvm: diagnose 0x318 sync and reset - KVM: s390: remove diag318 reset code - KVM: s390: add debug statement for diag 318 CPNC data * Updates to ib_peer_memory requested by Nvidia (LP: #1947206) - SAUCE: RDMA/core: Updated ib_peer_memory * Include Infiniband Peer Memory interface (LP: #1923104) - IB: Allow calls to ib_umem_get from kernel ULPs - SAUCE: RDMA/core: Introduce peer memory interface * Focal update: v5.4.162 upstream stable release (LP: #1954834) - arm64: zynqmp: Do not duplicate flash partition label property - arm64: zynqmp: Fix serial compatible string - ARM: dts: NSP: Fix mpcore, mmc node names - scsi: lpfc: Fix list_add() corruption in lpfc_drain_txq() - arm64: dts: hisilicon: fix arm,sp805 compatible string - RDMA/bnxt_re: Check if the vlan is valid before reporting - usb: musb: tusb6010: check return value after calling platform_get_resource() - usb: typec: tipd: Remove WARN_ON in tps6598x_block_read - arm64: dts: qcom: msm8998: Fix CPU/L2 idle state latency and residency - arm64: dts: freescale: fix arm,sp805 compatible string - ASoC: SOF: Intel: hda-dai: fix potential locking issue - clk: imx: imx6ul: Move csi_sel mux to correct base register - ASoC: nau8824: Add DMI quirk mechanism for active-high jack-detect - scsi: advansys: Fix kernel pointer leak - firmware_loader: fix pre-allocated buf built-in firmware use - ARM: dts: omap: fix gpmc,mux-add-data type - usb: host: ohci-tmio: check return value after calling platform_get_resource() - ARM: dts: ls1021a: move thermal-zones node out of soc/ - ARM: dts: ls1021a-tsn: use generic "jedec,spi-nor" compatible for flash - ALSA: ISA: not for M68K - tty: tty_buffer: Fix the softlockup issue in flush_to_ldisc - MIPS: sni: Fix the build - scsi: target: Fix ordered tag handling - scsi: target: Fix alua_tg_pt_gps_count tracking - iio: imu: st_lsm6dsx: Avoid potential array overflow in st_lsm6dsx_set_odr() - powerpc/5200: dts: fix memory node unit name - ALSA: gus: fix null pointer dereference on pointer block - powerpc/dcr: Use cmplwi instead of 3-argument cmpli - sh: check return code of request_irq - maple: fix wrong return value of maple_bus_init(). - f2fs: fix up f2fs_lookup tracepoints - sh: fix kconfig unmet dependency warning for FRAME_POINTER - sh: math-emu: drop unused functions - sh: define __BIG_ENDIAN for math-emu - clk: ingenic: Fix bugs with divided dividers - clk/ast2600: Fix soc revision for AHB - clk: qcom: gcc-msm8996: Drop (again) gcc_aggre1_pnoc_ahb_clk - mips: BCM63XX: ensure that CPU_SUPPORTS_32BIT_KERNEL is set - sched/core: Mitigate race cpus_share_cache()/update_top_cache_domain() - tracing: Save normal string variables - tracing/histogram: Do not copy the fixed-size char array field over the field size - RDMA/netlink: Add __maybe_unused to static inline in C file - perf bpf: Avoid memory leak from perf_env__insert_btf() - perf bench futex: Fix memory leak of perf_cpu_map__new() - perf tests: Remove bash construct from record+zstd_comp_decomp.sh - net: bnx2x: fix variable dereferenced before check - iavf: check for null in iavf_fix_features - iavf: free q_vectors before queues in iavf_disable_vf - iavf: Fix failure to exit out from last all-multicast mode - iavf: prevent accidental free of filter structure
[Kernel-packages] [Bug 1927808] Re: rtw88_8821ce causes freeze
This bug was fixed in the package linux - 5.13.0-28.31 --- linux (5.13.0-28.31) impish; urgency=medium * amd_sfh: Null pointer dereference on early device init causes early panic and fails to boot (LP: #1956519) - HID: amd_sfh: Fix potential NULL pointer dereference * impish: ddebs build take too long and times out (LP: #1957810) - [Packaging] enforce xz compression for ddebs * audio mute/ mic mute are not working on a HP machine (LP: #1955691) - ALSA: hda/realtek: fix mute/micmute LEDs for a HP ProBook * rtw88_8821ce causes freeze (LP: #1927808) - rtw88: Disable PCIe ASPM while doing NAPI poll on 8821CE * alsa/sdw: fix the audio sdw codec parsing logic in the acpi table (LP: #1955686) - ALSA: hda: intel-sdw-acpi: harden detection of controller - ALSA: hda: intel-sdw-acpi: go through HDAS ACPI at max depth of 2 * icmp_redirect from selftests fails on F/kvm (unary operator expected) (LP: #1938964) - selftests: icmp_redirect: pass xfail=0 to log_test() * Impish update: upstream stable patchset 2021-12-17 (LP: #1955180) - arm64: zynqmp: Do not duplicate flash partition label property - arm64: zynqmp: Fix serial compatible string - ARM: dts: sunxi: Fix OPPs node name - arm64: dts: allwinner: h5: Fix GPU thermal zone node name - arm64: dts: allwinner: a100: Fix thermal zone node name - staging: wfx: ensure IRQ is ready before enabling it - ARM: dts: NSP: Fix mpcore, mmc node names - scsi: lpfc: Fix list_add() corruption in lpfc_drain_txq() - arm64: dts: rockchip: Disable CDN DP on Pinebook Pro - arm64: dts: hisilicon: fix arm,sp805 compatible string - RDMA/bnxt_re: Check if the vlan is valid before reporting - bus: ti-sysc: Add quirk handling for reinit on context lost - bus: ti-sysc: Use context lost quirk for otg - usb: musb: tusb6010: check return value after calling platform_get_resource() - usb: typec: tipd: Remove WARN_ON in tps6598x_block_read - ARM: dts: ux500: Skomer regulator fixes - staging: rtl8723bs: remove possible deadlock when disconnect (v2) - ARM: BCM53016: Specify switch ports for Meraki MR32 - arm64: dts: qcom: msm8998: Fix CPU/L2 idle state latency and residency - arm64: dts: qcom: ipq6018: Fix qcom,controlled-remotely property - arm64: dts: freescale: fix arm,sp805 compatible string - ASoC: SOF: Intel: hda-dai: fix potential locking issue - clk: imx: imx6ul: Move csi_sel mux to correct base register - ASoC: nau8824: Add DMI quirk mechanism for active-high jack-detect - scsi: advansys: Fix kernel pointer leak - ALSA: intel-dsp-config: add quirk for APL/GLK/TGL devices based on ES8336 codec - firmware_loader: fix pre-allocated buf built-in firmware use - ARM: dts: omap: fix gpmc,mux-add-data type - usb: host: ohci-tmio: check return value after calling platform_get_resource() - ARM: dts: ls1021a: move thermal-zones node out of soc/ - ARM: dts: ls1021a-tsn: use generic "jedec,spi-nor" compatible for flash - ALSA: ISA: not for M68K - tty: tty_buffer: Fix the softlockup issue in flush_to_ldisc - MIPS: sni: Fix the build - scsi: scsi_debug: Fix out-of-bound read in resp_readcap16() - scsi: scsi_debug: Fix out-of-bound read in resp_report_tgtpgs() - scsi: target: Fix ordered tag handling - scsi: target: Fix alua_tg_pt_gps_count tracking - iio: imu: st_lsm6dsx: Avoid potential array overflow in st_lsm6dsx_set_odr() - powerpc/5200: dts: fix memory node unit name - ARM: dts: qcom: fix memory and mdio nodes naming for RB3011 - ALSA: gus: fix null pointer dereference on pointer block - powerpc/dcr: Use cmplwi instead of 3-argument cmpli - powerpc/8xx: Fix Oops with STRICT_KERNEL_RWX without DEBUG_RODATA_TEST - sh: check return code of request_irq - maple: fix wrong return value of maple_bus_init(). - f2fs: fix up f2fs_lookup tracepoints - f2fs: fix to use WHINT_MODE - sh: fix kconfig unmet dependency warning for FRAME_POINTER - sh: math-emu: drop unused functions - sh: define __BIG_ENDIAN for math-emu - f2fs: compress: disallow disabling compress on non-empty compressed file - f2fs: fix incorrect return value in f2fs_sanity_check_ckpt() - clk: ingenic: Fix bugs with divided dividers - clk/ast2600: Fix soc revision for AHB - clk: qcom: gcc-msm8996: Drop (again) gcc_aggre1_pnoc_ahb_clk - mips: BCM63XX: ensure that CPU_SUPPORTS_32BIT_KERNEL is set - sched/core: Mitigate race cpus_share_cache()/update_top_cache_domain() - perf/x86/vlbr: Add c->flags to vlbr event constraints - blkcg: Remove extra blkcg_bio_issue_init - tracing/histogram: Do not copy the fixed-size char array field over the field size - perf bpf: Avoid memory leak from perf_env__insert_btf() - perf bench futex: Fix memory leak of perf_cpu_map__new() - perf tests: Remove bash construct from
[Kernel-packages] [Bug 1927808] Re: rtw88_8821ce causes freeze
This bug was fixed in the package linux-oem-5.13 - 5.13.0-1029.36 --- linux-oem-5.13 (5.13.0-1029.36) focal; urgency=medium * focal/linux-oem-5.13: 5.13.0-1029.36 -proposed tracker (LP: #1955196) * support signed v4l2loopback dkms build (LP: #1938531) - support v4l2loopback dkms build - enable v4l2loopback builds on oem kernels * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/2022.01.03) * Add missing BT ID for Qualcomm WCN6856 (LP: #1956407) - Bluetooth: btusb: Add one more Bluetooth part for WCN6855 * Add Bluetooth support for Qualcomm WCN6856 (LP: #1955689) - Bluetooth: btusb: Add support using different nvm for variant WCN6855 controller - Bluetooth: btusb: re-definition for board_id in struct qca_version - Bluetooth: btusb: Add the new support IDs for WCN6855 [ Ubuntu: 5.13.0-28.31 ] * amd_sfh: Null pointer dereference on early device init causes early panic and fails to boot (LP: #1956519) - HID: amd_sfh: Fix potential NULL pointer dereference * impish: ddebs build take too long and times out (LP: #1957810) - [Packaging] enforce xz compression for ddebs * audio mute/ mic mute are not working on a HP machine (LP: #1955691) - ALSA: hda/realtek: fix mute/micmute LEDs for a HP ProBook * rtw88_8821ce causes freeze (LP: #1927808) - rtw88: Disable PCIe ASPM while doing NAPI poll on 8821CE * alsa/sdw: fix the audio sdw codec parsing logic in the acpi table (LP: #1955686) - ALSA: hda: intel-sdw-acpi: harden detection of controller - ALSA: hda: intel-sdw-acpi: go through HDAS ACPI at max depth of 2 * icmp_redirect from selftests fails on F/kvm (unary operator expected) (LP: #1938964) - selftests: icmp_redirect: pass xfail=0 to log_test() * Impish update: upstream stable patchset 2021-12-17 (LP: #1955180) - arm64: zynqmp: Do not duplicate flash partition label property - arm64: zynqmp: Fix serial compatible string - ARM: dts: sunxi: Fix OPPs node name - arm64: dts: allwinner: h5: Fix GPU thermal zone node name - arm64: dts: allwinner: a100: Fix thermal zone node name - staging: wfx: ensure IRQ is ready before enabling it - ARM: dts: NSP: Fix mpcore, mmc node names - scsi: lpfc: Fix list_add() corruption in lpfc_drain_txq() - arm64: dts: rockchip: Disable CDN DP on Pinebook Pro - arm64: dts: hisilicon: fix arm,sp805 compatible string - RDMA/bnxt_re: Check if the vlan is valid before reporting - bus: ti-sysc: Add quirk handling for reinit on context lost - bus: ti-sysc: Use context lost quirk for otg - usb: musb: tusb6010: check return value after calling platform_get_resource() - usb: typec: tipd: Remove WARN_ON in tps6598x_block_read - ARM: dts: ux500: Skomer regulator fixes - staging: rtl8723bs: remove possible deadlock when disconnect (v2) - ARM: BCM53016: Specify switch ports for Meraki MR32 - arm64: dts: qcom: msm8998: Fix CPU/L2 idle state latency and residency - arm64: dts: qcom: ipq6018: Fix qcom,controlled-remotely property - arm64: dts: freescale: fix arm,sp805 compatible string - ASoC: SOF: Intel: hda-dai: fix potential locking issue - clk: imx: imx6ul: Move csi_sel mux to correct base register - ASoC: nau8824: Add DMI quirk mechanism for active-high jack-detect - scsi: advansys: Fix kernel pointer leak - ALSA: intel-dsp-config: add quirk for APL/GLK/TGL devices based on ES8336 codec - firmware_loader: fix pre-allocated buf built-in firmware use - ARM: dts: omap: fix gpmc,mux-add-data type - usb: host: ohci-tmio: check return value after calling platform_get_resource() - ARM: dts: ls1021a: move thermal-zones node out of soc/ - ARM: dts: ls1021a-tsn: use generic "jedec,spi-nor" compatible for flash - ALSA: ISA: not for M68K - tty: tty_buffer: Fix the softlockup issue in flush_to_ldisc - MIPS: sni: Fix the build - scsi: scsi_debug: Fix out-of-bound read in resp_readcap16() - scsi: scsi_debug: Fix out-of-bound read in resp_report_tgtpgs() - scsi: target: Fix ordered tag handling - scsi: target: Fix alua_tg_pt_gps_count tracking - iio: imu: st_lsm6dsx: Avoid potential array overflow in st_lsm6dsx_set_odr() - powerpc/5200: dts: fix memory node unit name - ARM: dts: qcom: fix memory and mdio nodes naming for RB3011 - ALSA: gus: fix null pointer dereference on pointer block - powerpc/dcr: Use cmplwi instead of 3-argument cmpli - powerpc/8xx: Fix Oops with STRICT_KERNEL_RWX without DEBUG_RODATA_TEST - sh: check return code of request_irq - maple: fix wrong return value of maple_bus_init(). - f2fs: fix up f2fs_lookup tracepoints - f2fs: fix to use WHINT_MODE - sh: fix kconfig unmet dependency warning for FRAME_POINTER - sh: math-emu: drop unused functions - sh: define __BIG_ENDIAN for math-emu - f2fs: compress: disallow
[Kernel-packages] [Bug 1959752] [NEW] ubuntu_kernel_selftests.ftrace:ftracetest fails with bionic:linux 4.15.0-168.176 on s390x
Public bug reported: All ftrace tests from selftests are failing with bionic:linux 4.15.0-168.176 on s390x: https://autopkgtest.ubuntu.com/results/autopkgtest- bionic/bionic/s390x/l/linux/20220201_190955_5689e@/log.gz == selftests: ftracetest === Ftrace unit tests === [1] Basic trace file check [FAIL] [2] Basic test for tracers [FAIL] [3] Basic trace clock test [FAIL] [4] Basic event tracing check [FAIL] [5] Snapshot and tracing setting[FAIL] [6] event tracing - enable/disable with event level files [FAIL] [7] event tracing - restricts events based on pid [FAIL] [8] event tracing - enable/disable with subsystem level files [FAIL] [9] event tracing - enable/disable with top level files [FAIL] [10] ftrace - function graph filters with stack tracer [FAIL] [11] ftrace - function graph filters[FAIL] [12] ftrace - function pid filters [FAIL] [13] ftrace - test for function event triggers [FAIL] [14] ftrace - function profiler with function tracing [FAIL] [15] ftrace - test reading of set_ftrace_filter [FAIL] [16] ftrace - test for function traceon/off triggers[FAIL] [17] Test creation and deletion of trace instances while setting an event [FAIL] [18] Test creation and deletion of trace instances [FAIL] [19] Kprobe dynamic event - adding and removing [FAIL] [20] Kprobe dynamic event - busy event check[FAIL] [21] Kprobe dynamic event with arguments[FAIL] [22] Kprobe event string type argument [FAIL] [23] Kprobe event argument syntax [FAIL] [24] Kprobes event arguments with types [FAIL] [25] Kprobe event auto/manual naming[FAIL] [26] Kprobe dynamic event with function tracer [FAIL] [27] Kretprobe dynamic event with arguments [FAIL] [28] Kretprobe dynamic event with maxactive [FAIL] [29] Register/unregister many kprobe events [FAIL] [30] event trigger - test multiple actions on hist trigger [FAIL] [31] event trigger - test synthetic_events syntax parser[FAIL] [32] event trigger - test event enable/disable trigger [FAIL] [33] event trigger - test trigger filter[FAIL] [34] event trigger - test histogram modifiers [FAIL] [35] event trigger - test multiple histogram triggers [FAIL] [36] event trigger - test snapshot-trigger [FAIL] [37] event trigger - test stacktrace-trigger[FAIL] [38] event trigger - test traceon/off trigger [FAIL] [39] (instance) Basic test for tracers [FAIL] [40] (instance) Basic trace clock test [FAIL] [41] (instance) Snapshot and tracing setting [FAIL] [42] (instance) event tracing - enable/disable with event level files [FAIL] [43] (instance) event tracing - restricts events based on pid [FAIL] [44] (instance) event tracing - enable/disable with subsystem level files [FAIL] [45] (instance) ftrace - test for function event triggers [FAIL] [46] (instance) ftrace - test for function traceon/off triggers[FAIL] [47] (instance) event trigger - test event enable/disable trigger [FAIL] [48] (instance) event trigger - test trigger filter[FAIL] [49] (instance) event trigger - test histogram modifiers [FAIL] [50] (instance) event trigger - test multiple histogram triggers [FAIL] # of passed: 0 # of failed: 50 # of unresolved: 0 # of untested: 0 # of unsupported: 0 # of xfailed: 0 # of undefined(test bug): 0 not ok 1..1 selftests: ftracetest [FAIL] == After some debugging I've found out that the testcases are not actually run, the failure happens while running 'tools/testing/selftests/ftrace/test.d/functions:initialize_ftrace()', on the following line: [ -f set_ftrace_filter ] && echo | tee set_ftrace_* After a reboot for clean ftrace state, with kernel 4.15.0-168-generic: root@kleber-bionic:/sys/kernel/debug/tracing# head set_ftrace_* head: cannot open 'set_ftrace_filter' for reading: No such device head: cannot open 'set_ftrace_notrace' for reading: No such device ==> set_ftrace_pid <== no pid With kernel 4.15.0-167-generic: root@kleber-bionic-2:/sys/kernel/debug/tracing# head set_ftrace_* ==> set_ftrace_filter <== all functions enabled ==> set_ftrace_notrace <== no functions disabled ==> set_ftrace_pid <== no pid ** Affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Bionic) Importance: Undecided Status: Confirmed ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Invalid ** Changed in: linux (Ubuntu Bionic) Status: New => Confirmed ** Description changed: All ftrace tests
[Kernel-packages] [Bug 1958591] Re: [amdgpu] Random noise 'static' display after internal display turned off/on
I am also affected by this bug on my Lenovo laptop I have an external monitor plugged in all the time, that means after the display manager starts, the internal monitor is unusable (showing "snow" and lines). fixed this temporarily by booting 5.11 kernel instead of 5.13 *-display description: VGA compatible controller product: Renoir vendor: Advanced Micro Devices, Inc. [AMD/ATI] physical id: 0 bus info: pci@:07:00.0 logical name: /dev/fb0 version: d1 width: 64 bits clock: 33MHz capabilities: pm pciexpress msi msix vga_controller bus_master cap_list fb configuration: depth=32 driver=amdgpu latency=0 mode=1920x1080 visual=truecolor xres=1920 yres=1080 resources: iomemory:40-3f iomemory:40-3f irq:87 memory:46000-46fff memory:47000-4701f ioport:1000(size=256) memory:fd30-fd37 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1958591 Title: [amdgpu] Random noise 'static' display after internal display turned off/on Status in linux-hwe-5.13 package in Ubuntu: Confirmed Bug description: Laptop internal display shows random looking 'static' after it's turned off and then on again. e.g. on suspend/resume, or when plugging/unplugging an external monitor. This appeared to come after a `dist-upgrade` took the kernel from 5.11.0-44 to 5.13.0-25 (hwe). Others are seeing this with both NVidia and AMD graphics hardware: - https://www.reddit.com/r/Ubuntu/comments/s8c83w/laptop_shows_static_screen_after_going_into_lock/ - https://www.reddit.com/r/Ubuntu/comments/s8fit0/please_help_static_noise_display_on_ubuntu_2004/ I use i3 under gnome-flashback, but tried using default Ubuntu/Gnome both X and Wayland, and gnome-flashback/metacity. All showed the same problem. Also tried an `apt install --reinstall xserver-xorg-video-radeon libdrm-radeon1` for luck - no joy. Running a 20.04.3 live stick the problem does *not* occur. System: Thinkpad X13 Gen1 Processor: AMD Ryzen 7 PRO 4750U System Firmware: 1.35 $ lsb_release -rd Description:Ubuntu 20.04.3 LTS Release:20.04 Happy to assist with investigations. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: i3-GNOME-Flashback:GNOME-Flashback:GNOME Date: Thu Jan 20 19:37:09 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev d1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Renoir [17aa:5082] InstallationDate: Installed on 2021-06-24 (210 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 20UF0014US ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic root=UUID=5db0269f-fa23-487e-ace8-ba99bca814a8 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/20/2021 dmi.bios.release: 1.36 dmi.bios.vendor: LENOVO dmi.bios.version: R1CET67W(1.36 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UF0014US dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.36 dmi.modalias: dmi:bvnLENOVO:bvrR1CET67W(1.36):bd10/20/2021:br1.36:efr1.36:svnLENOVO:pn20UF0014US:pvrThinkPadX13Gen1:rvnLENOVO:rn20UF0014US:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20UF_BU_Think_FM_ThinkPadX13Gen1: dmi.product.family: ThinkPad X13 Gen 1 dmi.product.name: 20UF0014US dmi.product.sku: LENOVO_MT_20UF_BU_Think_FM_ThinkPad X13 Gen 1 dmi.product.version: ThinkPad X13 Gen 1 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.5 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.5 version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
[Kernel-packages] [Bug 1950720] Re: GSYNC bug regression in 495.44 Ubuntu 21.10
Thanks for the response, The G-SYNC mode does work for applications that utilise it, such as games. It just drops sync like that. I've commented on this thread which has since gone cold: https://forums.developer.nvidia.com/t/nvidia-470-74-breaks-gsync- compatible-support-monitor-modulates-between-0-or-144hz-and-flickers- black/189716/39 I'm not really sure what to say, other than it was drivers changing that changed the behaviour. Guess I can try to start a new thread to see if it gets some attention. I'd add, I've been using G-SYNC on Linux for quite some time, so it's strange it's affecting me. I do have another G-SYNC display at work, however, we're currently on WFH orders with COVID-19 etc. I'll try this out when I am allowed back in the office. I'm not sure if there is anything I can do to debug the mode changes to see if I can get more info, I'm guessing that there are limited options with proprietary drivers. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1950720 Title: GSYNC bug regression in 495.44 Ubuntu 21.10 Status in nvidia-graphics-drivers-470 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-495 package in Ubuntu: Confirmed Bug description: [ Description ] Video of signal loss with flipping enabled: https://youtu.be/V5DGcHN- BJs In NVIDIA the 495 driver for Ubuntu 21.10, with G-SYNC enabled in OpenGL Settings of NVIDIA Settings, the G-SYNC compatible monitor loses sync momentarily (1~2 seconds) when switching to GPU accelerated application. Examples of this are: - When launching a game full-screen - Launching a GPU accelerated game in Window mode - Launching Steam - Launching kitty terminal https://sw.kovidgoyal.net/kitty/ This issue happens at all refresh rates: 60 Hz, 120 Hz, 144 Hz and 165 Hz. Note: This example doesn't explicitly show G-SYNC being enabled in the onscreen indicator, rather what happens when G-SYNC is enabled in the settings. If I disable G-SYNC, but leave flipping enabled, the issue is not present. If I enabled G-SYNC, but disable flipping, the issue is not present. If both are enabled, then the issue occurs. [ Hardware ] - NVIDIA GeForce RTX 2080 Super - Dell 27" S2721DGF G-Sync Compatible monitor - High quality DisplayPort cable [ Settings ] In the NVIDIA OpenGL settings, the following settings are enabled: - Sync to VBlank Enabled - Allow Flipping Enabled - Image Setting: High Performance - Allow G-SYNC-/G-SYNC Compatible Enabled - Use Conformant Texture Clamping Enabled [ Observations ] When I disable Allow Flipping, the issue goes away. No signal is lost when changing to different GPU accelerated applications. Sometimes there is a brief flicker when opening a GPU accelerated program with flipping disabled, but it's not a signal loss, rather a very fast momentary flick of the display, but it's does not impact usability. As flipping is required for G-SYNC to function, therefore losing the benefit of G-SYNC if I were to disable flipping. [ Correlation to previous bug ] This issue was present in Ubuntu 21.04, eventually driver 495.44 resolved this problem on the 5.14.1 kernel. I will add that when I first had this machine and screen in 20.10 and 21.04, it was not experiencing the signal loss issue. The bug described in the change log in this launchpad bug seems to reference the type of regression I am experiencing https://launchpad.net/bugs/1950665. [ Troubleshooting ] Full driver purges between trying different drivers: - Tried downgrading to 470.82 - Went back to the standard kernel for 21.10 (5.13.0-21-generic) at the time - Tried deleting ~/.nv, ~/.cache/nvidia - Reverted to previous X11 conf - Tried 5.14.1 which was working in Ubuntu 21.04 - Tried kernels 5.14.17, 5.15.6 - Persists in 470.94 (NVIDIA bundle and Graphics Drivers PPA) - Persists in 495.46 (NVIDIA bundle and Graphics Drivers PPA) - Persists in 510.39.01 (NVIDIA bundle) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1950720/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1959715] Re: Touchpad is not working after installing Ubuntu. Worked fine with windows
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-signed-hwe-5.13 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1959715 Title: Touchpad is not working after installing Ubuntu. Worked fine with windows Status in linux-signed-hwe-5.13 package in Ubuntu: Confirmed Bug description: Ubuntu not finding the touchpad. Attaching output from cat /proc/bus/input/devices. Followed guide on https://wiki.ubuntu.com/DebuggingTouchpadDetection. Please let me know if there is anything else you need from me. Description: Ubuntu 20.04.3 LTS Release: 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-28-generic 5.13.0-28.31~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Feb 1 20:33:13 2022 InstallationDate: Installed on 2022-02-01 (0 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=sv_SE.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1959715/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1941829] Re: ubuntu_kernel_selftests: memory-hotplug: avoid spamming logs with dump_page()
** Summary changed: - ubunut_kernel_selftests: memory-hotplug: avoid spamming logs with dump_page() + ubuntu_kernel_selftests: memory-hotplug: avoid spamming logs with dump_page() -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1941829 Title: ubuntu_kernel_selftests: memory-hotplug: avoid spamming logs with dump_page() Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Released Status in linux-oem-5.10 source package in Bionic: Invalid Status in linux-oem-5.13 source package in Bionic: Invalid Status in linux source package in Focal: Fix Released Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux source package in Hirsute: Fix Released Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux source package in Impish: Fix Committed Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.10 source package in Jammy: Invalid Status in linux-oem-5.13 source package in Jammy: Invalid Bug description: [Impact] The memory-hotplug test has been intermittently timing out (or trashing the test VM, see below) on Impish/Hirsute ppc64el and x86-64 for quite some time now. While the offline memory test obey ratio limit, the same test with error injection does not and tries to offline all the hotpluggable memory, spamming system logs with hundreds of thousands of dump_page() entries, slowing system down (to the point the test itself timesout and gets terminated) and excessive fs occupation: ... [ 9784.393354] page:c00c007d1b40 refcount:3 mapcount:0 mapping:c001fc03e950 index:0xe7b [ 9784.393355] def_blk_aops [ 9784.393356] flags: 0x382062(referenced|active|workingset|private) [ 9784.393358] raw: 00382062 c001b9343a68 c001b9343a68 c001fc03e950 [ 9784.393359] raw: 0e7b c6607b18 0003 c490d000 [ 9784.393359] page dumped because: migration failure [ 9784.393360] page->mem_cgroup:c490d000 [ 9784.393416] migrating pfn 1f46d failed ret:1 ... $ grep "page dumped because: migration failure" /var/log/kern.log | wc -l 2405558 $ ls -la /var/log/kern.log -rw-r- 1 syslog adm 2256109539 Jun 30 14:19 /var/log/kern.log [Fix] * 0c0f6299ba71fa selftests: memory-hotplug: avoid spamming logs with dump_page(), ratio limit hot-remove error test [Test Plan] Run the memory-hotplug test, this log spamming issue should not happen again. [Where problems could occur] If this fix is incorrect we might be unable to catch some other issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1941829/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950720] Re: GSYNC bug regression in 495.44 Ubuntu 21.10
Thanks for the details and video. I've only ever seen G-SYNC on a Windows machine, in which case the display would blank whenever G-SYNC was enabled, just like you describe. So if the same happens in both Windows and Linux then maybe it's not a bug?... If you didn't see the blanking in the past then that might just indicate that no switching was occurring. Perhaps the monitor was either permanently in, or never in, G-SYNC mode. If the driver needs to blank the screen for a second or two to switch modes then I'm not sure that's a bug. You should probably ask in https://forums.developer.nvidia.com/c/gpu-graphics/linux/148 or a similar forum. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1950720 Title: GSYNC bug regression in 495.44 Ubuntu 21.10 Status in nvidia-graphics-drivers-470 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-495 package in Ubuntu: Confirmed Bug description: [ Description ] Video of signal loss with flipping enabled: https://youtu.be/V5DGcHN- BJs In NVIDIA the 495 driver for Ubuntu 21.10, with G-SYNC enabled in OpenGL Settings of NVIDIA Settings, the G-SYNC compatible monitor loses sync momentarily (1~2 seconds) when switching to GPU accelerated application. Examples of this are: - When launching a game full-screen - Launching a GPU accelerated game in Window mode - Launching Steam - Launching kitty terminal https://sw.kovidgoyal.net/kitty/ This issue happens at all refresh rates: 60 Hz, 120 Hz, 144 Hz and 165 Hz. Note: This example doesn't explicitly show G-SYNC being enabled in the onscreen indicator, rather what happens when G-SYNC is enabled in the settings. If I disable G-SYNC, but leave flipping enabled, the issue is not present. If I enabled G-SYNC, but disable flipping, the issue is not present. If both are enabled, then the issue occurs. [ Hardware ] - NVIDIA GeForce RTX 2080 Super - Dell 27" S2721DGF G-Sync Compatible monitor - High quality DisplayPort cable [ Settings ] In the NVIDIA OpenGL settings, the following settings are enabled: - Sync to VBlank Enabled - Allow Flipping Enabled - Image Setting: High Performance - Allow G-SYNC-/G-SYNC Compatible Enabled - Use Conformant Texture Clamping Enabled [ Observations ] When I disable Allow Flipping, the issue goes away. No signal is lost when changing to different GPU accelerated applications. Sometimes there is a brief flicker when opening a GPU accelerated program with flipping disabled, but it's not a signal loss, rather a very fast momentary flick of the display, but it's does not impact usability. As flipping is required for G-SYNC to function, therefore losing the benefit of G-SYNC if I were to disable flipping. [ Correlation to previous bug ] This issue was present in Ubuntu 21.04, eventually driver 495.44 resolved this problem on the 5.14.1 kernel. I will add that when I first had this machine and screen in 20.10 and 21.04, it was not experiencing the signal loss issue. The bug described in the change log in this launchpad bug seems to reference the type of regression I am experiencing https://launchpad.net/bugs/1950665. [ Troubleshooting ] Full driver purges between trying different drivers: - Tried downgrading to 470.82 - Went back to the standard kernel for 21.10 (5.13.0-21-generic) at the time - Tried deleting ~/.nv, ~/.cache/nvidia - Reverted to previous X11 conf - Tried 5.14.1 which was working in Ubuntu 21.04 - Tried kernels 5.14.17, 5.15.6 - Persists in 470.94 (NVIDIA bundle and Graphics Drivers PPA) - Persists in 495.46 (NVIDIA bundle and Graphics Drivers PPA) - Persists in 510.39.01 (NVIDIA bundle) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1950720/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950720] Re: GSYNC bug regression in 495.44 Ubuntu 21.10
** Tags added: impish -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1950720 Title: GSYNC bug regression in 495.44 Ubuntu 21.10 Status in nvidia-graphics-drivers-470 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-495 package in Ubuntu: Confirmed Bug description: [ Description ] Video of signal loss with flipping enabled: https://youtu.be/V5DGcHN- BJs In NVIDIA the 495 driver for Ubuntu 21.10, with G-SYNC enabled in OpenGL Settings of NVIDIA Settings, the G-SYNC compatible monitor loses sync momentarily (1~2 seconds) when switching to GPU accelerated application. Examples of this are: - When launching a game full-screen - Launching a GPU accelerated game in Window mode - Launching Steam - Launching kitty terminal https://sw.kovidgoyal.net/kitty/ This issue happens at all refresh rates: 60 Hz, 120 Hz, 144 Hz and 165 Hz. Note: This example doesn't explicitly show G-SYNC being enabled in the onscreen indicator, rather what happens when G-SYNC is enabled in the settings. If I disable G-SYNC, but leave flipping enabled, the issue is not present. If I enabled G-SYNC, but disable flipping, the issue is not present. If both are enabled, then the issue occurs. [ Hardware ] - NVIDIA GeForce RTX 2080 Super - Dell 27" S2721DGF G-Sync Compatible monitor - High quality DisplayPort cable [ Settings ] In the NVIDIA OpenGL settings, the following settings are enabled: - Sync to VBlank Enabled - Allow Flipping Enabled - Image Setting: High Performance - Allow G-SYNC-/G-SYNC Compatible Enabled - Use Conformant Texture Clamping Enabled [ Observations ] When I disable Allow Flipping, the issue goes away. No signal is lost when changing to different GPU accelerated applications. Sometimes there is a brief flicker when opening a GPU accelerated program with flipping disabled, but it's not a signal loss, rather a very fast momentary flick of the display, but it's does not impact usability. As flipping is required for G-SYNC to function, therefore losing the benefit of G-SYNC if I were to disable flipping. [ Correlation to previous bug ] This issue was present in Ubuntu 21.04, eventually driver 495.44 resolved this problem on the 5.14.1 kernel. I will add that when I first had this machine and screen in 20.10 and 21.04, it was not experiencing the signal loss issue. The bug described in the change log in this launchpad bug seems to reference the type of regression I am experiencing https://launchpad.net/bugs/1950665. [ Troubleshooting ] Full driver purges between trying different drivers: - Tried downgrading to 470.82 - Went back to the standard kernel for 21.10 (5.13.0-21-generic) at the time - Tried deleting ~/.nv, ~/.cache/nvidia - Reverted to previous X11 conf - Tried 5.14.1 which was working in Ubuntu 21.04 - Tried kernels 5.14.17, 5.15.6 - Persists in 470.94 (NVIDIA bundle and Graphics Drivers PPA) - Persists in 495.46 (NVIDIA bundle and Graphics Drivers PPA) - Persists in 510.39.01 (NVIDIA bundle) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1950720/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1933201] Re: ath10k_pci QCA6174 firmware crash on suspend
Same thing for me: Dell XPS 13 with QCA6174 wlan card It often crashes after the laptop suspend No porblem if I manually switch off the wlan before suspending. -- 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/1933201 Title: ath10k_pci QCA6174 firmware crash on suspend Status in linux package in Ubuntu: Confirmed Bug description: Hi, Another issue with Qualcomm Atheros QCA6174 (very similar to https://bugs.launchpad.net/ubuntu/+bug/1827879), this time using Mint 20.1/Ubuntu 20.04: when suspending laptop, firmware often (80%) crashes (see kernel log at bottom). It prevents the computer from properly suspend, and many component hang (can't poweroff properly, can't use "sudo", can't "modprobe -r" or "rmmod"…), so it basically makes the computer unusable once this happens. If I manually unload ath10k_pci module before suspend, suspend/resume works perfectly. Unfortunately, I could not find a reliable way to unload this module before suspend (either via a systemd unit or via /lib/systemd/system-sleep/ script). If I understand properly, the issue comes from the loaded firmware (/lib/firmware/ath10k/QCA6142/hw2.1/firmware-5.bin) which is proprietary so can't be fixed. However, fixing the ath10k module or the kernel so that it can recover from such a problem would be great if possible. Note that I tried with linux-image-generic (linux- headers-5.4.0-74-generic) and linux-image-generic-hwe-20.04 (linux- image-5.8.0-55-generic). Package linux-firmware is in version 1.187.14. Regards, Yvan juin 21 23:22:04 kernel: wlp2s0: deauthenticating from 38:35:fb:fa:75:64 by local choice (Reason: 3=DEAUTH_LEAVING) juin 21 23:22:04 kernel: ath10k_pci :02:00.0: firmware crashed! (guid 4f13694a-78f7-460f-95ad-ed3e8ea8ff32) juin 21 23:22:04 kernel: ath10k_pci :02:00.0: qca6174 hw2.1 target 0x0501 chip_id 0x003405ff sub 105b:e08e juin 21 23:22:04 kernel: ath10k_pci :02:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 juin 21 23:22:04 kernel: ath10k_pci :02:00.0: firmware ver SW_RM.1.1.1-00157-QCARMSWPZ-1 api 5 features ignore-otp,no-4addr-pad crc32 10bf8e08 juin 21 23:22:04 kernel: ath10k_pci :02:00.0: board_file api 2 bmi_id N/A crc32 ae2e275a juin 21 23:22:04 kernel: ath10k_pci :02:00.0: htt-ver 3.1 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1 juin 21 23:22:04 kernel: ath10k_pci :02:00.0: firmware register dump: juin 21 23:22:04 kernel: ath10k_pci :02:00.0: [00]: 0x0501 0x 0x0092E4DC 0x2EB96CFB juin 21 23:22:04 kernel: ath10k_pci :02:00.0: [04]: 0x0092E4DC 0x00060130 0x0018 0x0041A760 juin 21 23:22:04 kernel: ath10k_pci :02:00.0: [08]: 0x2EB96CE7 0x0040 0x 0x000A5C88 juin 21 23:22:04 kernel: ath10k_pci :02:00.0: [12]: 0x0009 0x 0x0096C09C 0x0096C0A7 juin 21 23:22:04 kernel: ath10k_pci :02:00.0: [16]: 0x0096BDBC 0x0092B5C7 0x 0x009287BD juin 21 23:22:04 kernel: ath10k_pci :02:00.0: [20]: 0x4092E4DC 0x0041A710 0x 0x0F00 juin 21 23:22:04 kernel: ath10k_pci :02:00.0: [24]: 0x809432A7 0x0041A770 0x0040D400 0xC092E4DC juin 21 23:22:04 kernel: ath10k_pci :02:00.0: [28]: 0x80942BC4 0x0041A790 0x2EB96CE7 0x0040 juin 21 23:22:04 kernel: ath10k_pci :02:00.0: [32]: 0x80947BA7 0x0041A7B0 0x00404D88 0x0040E074 juin 21 23:22:04 kernel: ath10k_pci :02:00.0: [36]: 0x809BDECC 0x0041A7D0 0x00404D88 0x0040E074 juin 21 23:22:04 kernel: ath10k_pci :02:00.0: [40]: 0x8099638C 0x0041A7F0 0x00404D88 0x juin 21 23:22:04 kernel: ath10k_pci :02:00.0: [44]: 0x80992076 0x0041A810 0x0044FD68 0x0046FFE8 juin 21 23:22:04 kernel: ath10k_pci :02:00.0: [48]: 0x80996BD3 0x0041A830 0x0044FD68 0x juin 21 23:22:04 kernel: ath10k_pci :02:00.0: [52]: 0x800B4405 0x0041A850 0x00422318 0x5002 juin 21 23:22:04 kernel: ath10k_pci :02:00.0: [56]: 0x809A6C34 0x0041A8E0 0x0042932C 0x0042CA20 juin 21 23:22:04 kernel: ath10k_pci :02:00.0: Copy Engine register dump: juin 21 23:22:04 kernel: ath10k_pci :02:00.0: [00]: 0x00034400 1 1 3 3 juin 21 23:22:04 kernel: ath10k_pci :02:00.0: [01]: 0x00034800 24 24 379 380 juin 21 23:22:04 kernel: ath10k_pci :02:00.0: [02]: 0x00034c00 35 35 34 35 juin 21 23:22:04 kernel: ath10k_pci :02:00.0: [03]: 0x00035000 20 20 21 20 juin 21 23:22:04 kernel: ath10k_pci :02:00.0: [04]: 0x00035400 739 739 179 115 juin 21 23:22:04 kernel: ath10k_pci :02:00.0: [05]: 0x00035800 0 0 0 0 juin 21 23:22:04 kernel: ath10k_pci :02:00.0: [06]: 0x00035c00 21 21 21 21 juin 21 23:22:04 kernel: ath10k_pci :02:00.0: [07]: 0x00036000 1 1 1 1 juin 21 23:22:04 kernel: ieee80211 phy0: Hardware restart was requested juin 21 23:22:04 kernel: ath10k_pci
[Kernel-packages] [Bug 1945590] Re: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled
Thanks a bunch. It also works on a ThinkPad E14 Gen 2 with Ryzen 7 4700u
and AMD Renoir.
When I started with the new kernel I first had graphics issues. No
animations, only internal monitor working, black screen after sleep.
That was caused by a missing graphics driver. Software Updater suggested
me to install some kernel headers for 5.13.0. After installing them and
rebooting everything works perfectly now. Maybe I've installed the
kernel in a strange way. (just a hint if someone else has this issue)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1945590
Title:
Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Impish:
Fix Released
Status in linux source package in Jammy:
Fix Released
Bug description:
[Impact]
On some thinkpads we may get a kernel panic at boot, because the
elantech driver (trakcpad) can trigger out-of-bounds access in the
stack.
[Test case]
Simply boot the kernel on one of the affected systems (e.g., Thinkpad
E14 Gen2).
[Fix]
Prevent the stack out of bound access by applying the following
upstream commit (from linux-next):
1d72d9f960cc ("Input: elantech - fix stack out of bound access in
elantech_change_report_id()")
[Regression potential]
The fix is touching the elantech driver, so we could only see
regressions with this specific trackpad/mouse driver.
[Original bug report]
I installed the Ubuntu 21.10 beta and as soon as I boot I get the
kernel panic that I am attaching.
I also installed Ubuntu 21.04 and upgraded, as soon as I boot with the
5.13 kernel I get the same problem, disabling the trackpad and
trackpoint in the bios the problem disappears.
Everything works with the 5.11 kernel.
I remain available for further details and sorry for my lack of experience.
ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: linux-image-5.13.0-16-generic 5.13.0-16.16
ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
Uname: Linux 5.13.0-16-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu69
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: pietro 1810 F pulseaudio
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Sep 30 10:26:10 2021
InstallationDate: Installed on 2021-09-29 (0 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
MachineType: LENOVO 20TA0033IX
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=it_IT.UTF-8
SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-16-generic
root=UUID=b5ea9465-4cd9-408b-8e30-458acf90181b ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-5.13.0-16-generic N/A
linux-backports-modules-5.13.0-16-generic N/A
linux-firmware 1.201
SourcePackage: linux
UpgradeStatus: Upgraded to impish on 2021-09-29 (0 days ago)
dmi.bios.date: 09/02/2021
dmi.bios.release: 1.43
dmi.bios.vendor: LENOVO
dmi.bios.version: R1EET43W(1.43 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20TA0033IX
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.43
dmi.modalias:
dmi:bvnLENOVO:bvrR1EET43W(1.43):bd09/02/2021:br1.43:efr1.43:svnLENOVO:pn20TA0033IX:pvrThinkPadE14Gen2:skuLENOVO_MT_20TA_BU_Think_FM_ThinkPadE14Gen2:rvnLENOVO:rn20TA0033IX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad E14 Gen 2
dmi.product.name: 20TA0033IX
dmi.product.sku: LENOVO_MT_20TA_BU_Think_FM_ThinkPad E14 Gen 2
dmi.product.version: ThinkPad E14 Gen 2
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945590/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945590] Re: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled
Thank you very much! Works for me on ThinkPad E15 Gen 2.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1945590
Title:
Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Impish:
Fix Released
Status in linux source package in Jammy:
Fix Released
Bug description:
[Impact]
On some thinkpads we may get a kernel panic at boot, because the
elantech driver (trakcpad) can trigger out-of-bounds access in the
stack.
[Test case]
Simply boot the kernel on one of the affected systems (e.g., Thinkpad
E14 Gen2).
[Fix]
Prevent the stack out of bound access by applying the following
upstream commit (from linux-next):
1d72d9f960cc ("Input: elantech - fix stack out of bound access in
elantech_change_report_id()")
[Regression potential]
The fix is touching the elantech driver, so we could only see
regressions with this specific trackpad/mouse driver.
[Original bug report]
I installed the Ubuntu 21.10 beta and as soon as I boot I get the
kernel panic that I am attaching.
I also installed Ubuntu 21.04 and upgraded, as soon as I boot with the
5.13 kernel I get the same problem, disabling the trackpad and
trackpoint in the bios the problem disappears.
Everything works with the 5.11 kernel.
I remain available for further details and sorry for my lack of experience.
ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: linux-image-5.13.0-16-generic 5.13.0-16.16
ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
Uname: Linux 5.13.0-16-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu69
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: pietro 1810 F pulseaudio
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Sep 30 10:26:10 2021
InstallationDate: Installed on 2021-09-29 (0 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
MachineType: LENOVO 20TA0033IX
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=it_IT.UTF-8
SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-16-generic
root=UUID=b5ea9465-4cd9-408b-8e30-458acf90181b ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-5.13.0-16-generic N/A
linux-backports-modules-5.13.0-16-generic N/A
linux-firmware 1.201
SourcePackage: linux
UpgradeStatus: Upgraded to impish on 2021-09-29 (0 days ago)
dmi.bios.date: 09/02/2021
dmi.bios.release: 1.43
dmi.bios.vendor: LENOVO
dmi.bios.version: R1EET43W(1.43 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20TA0033IX
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.43
dmi.modalias:
dmi:bvnLENOVO:bvrR1EET43W(1.43):bd09/02/2021:br1.43:efr1.43:svnLENOVO:pn20TA0033IX:pvrThinkPadE14Gen2:skuLENOVO_MT_20TA_BU_Think_FM_ThinkPadE14Gen2:rvnLENOVO:rn20TA0033IX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad E14 Gen 2
dmi.product.name: 20TA0033IX
dmi.product.sku: LENOVO_MT_20TA_BU_Think_FM_ThinkPad E14 Gen 2
dmi.product.version: ThinkPad E14 Gen 2
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945590/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1959665] Re: linux-image-5.4.0-97.110 freezes by accessing cifs shares
Hi, thanks for the quick reply. I can confirm, that while running on 5.4.0-98-generic #111~lp1959665.1 I was able to access all of our cifs shares without issues. A script, which creates, reads, modifies and deletes files on different cifs shares also works without any issue. Removing the latest cifs patches from kernel 5.4.0-97.110 seems to fix our issue. I will keep testing on 5.4.0-98-generic #111~lp1959665.1. Best regards, Sebastian -- 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/1959665 Title: linux-image-5.4.0-97.110 freezes by accessing cifs shares Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: In Progress Bug description: Ubuntu 20.04 with kernel image 5.4.0-97.110 randomly freezes when we access cifs shares. The system needs a hard reset after the freeze. The previous kernel image (5.4.0-96.109) does not show this behavior. Multiple Ubuntu 20.04 systems running on kernel image 9.4.0-97.110 are affected on our sites. The cifs shares are accessed via autofs using Kerberos authentication. The following info is the only error message we could actively catch on a different system before the system was frozen: general protection fault: [#3] SMP PTI CPU: 0 PID: 21294 Comm: automount Tainted: G DOE 5.4.0-97-generic #110-Ubuntu Hardware name: Dell Inc. Precision 7530/03RV2M, BIOS 1.14.4 10/21/2020 RIP: 0010:kmem_cache_alloc_trace+0x8c/0x240 Code: 08 65 4c 03 05 1d e8 f7 6e 49 83 78 10 00 4d 8b 38 0f 84 92 01 00 00 4d 85 ff 0f 84 89 01 00 00 41 8b 41 20 49 8b 39 4c 01 f8 <48> 8b 18 48 89 c1 49 33 99 70 01 00 00 4c 89 f8 48 0f c9 48 31 cb RSP: 0018:a6ca860f7ba0 EFLAGS: 00010286 RAX: fdd44d7c219190e1 RBX: RCX: RDX: d558 RSI: 0cc0 RDI: 00035060 RBP: a6ca860f7bd0 R08: 99233c035060 R09: 992338c079c0 R10: 0001 R11: 0004 R12: 0cc0 R13: 000b R14: 992338c079c0 R15: fdd44d7c219190e1 FS: 7fdc24e29700() GS:99233c00() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 7f15a80ee010 CR3: 0007e36b2006 CR4: 003606f0 Call Trace: ? proc_self_get_link+0x70/0xd0 proc_self_get_link+0x70/0xd0 link_path_walk.part.0+0x478/0x550 ? trailing_symlink+0x1d1/0x280 path_openat+0xb7/0x290 do_filp_open+0x91/0x100 ? unuse_pde+0x30/0x30 do_sys_open+0x17e/0x290 __x64_sys_openat+0x20/0x30 __orig_openat+0x71/0xc0 [eset_rtp] ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __x64_sys_futex+0x13f/0x170 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 __x64_sys_ertp_openat+0x29/0x60 [eset_rtp] do_syscall_64+0x57/0x190 entry_SYSCALL_64_after_hwframe+0x44/0xa9 RIP: 0033:0x7fdc28a41f24 Code: 24 20 eb 8f 66 90 44 89 54 24 0c e8 56 68 f8 ff 44 8b 54 24 0c 44 89 e2 48 89 ee 41 89 c0 bf 9c ff ff ff b8 01 01 00 00 0f 05 <48> 3d 00 f0 ff ff 77 32 44 89 c7 89 44 24 0c e8 88 68 f8 ff 8b 44 RSP: 002b:7fdc24e25980 EFLAGS: 0293 ORIG_RAX: 0101 RAX: ffda RBX: 7fdc040008d0 RCX: 7fdc28a41f24 ? unuse_pde+0x30/0x30 do_sys_open+0x17e/0x290 __x64_sys_openat+0x20/0x30 __orig_openat+0x71/0xc0 [eset_rtp] ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __x64_sys_futex+0x13f/0x170 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 __x64_sys_ertp_openat+0x29/0x60 [eset_rtp] do_syscall_64+0x57/0x190 entry_SYSCALL_64_after_hwframe+0x44/0xa9 RIP: 0033:0x7fdc28a41f24 Code: 24 20 eb 8f 66 90 44 89 54 24 0c e8 56 68 f8 ff 44 8b 54 24 0c 44 89 e2 48 89 ee 41 89 c0 bf 9c ff ff ff b8 01 01 00 00 0f 05 <48> 3d 00 f0 ff ff 77 32 44 89 c7 89 44 24 0c e8 88 68 f8 ff 8b 44 RSP: 002b:7fdc24e25980 EFLAGS: 0293 ORIG_RAX: 0101 RAX: ffda RBX: 7fdc040008d0 RCX: 7fdc28a41f24 RDX: 0008 RSI: 564d4410a8c8 RDI: ff9c RBP: 564d4410a8c8 R08: R09: 0001 R10: R11: 0293 R12: 0008 R13: 564d4410e28a R14: 7fdc24e25b40 R15: 7fdc24e28fc0 Modules linked in: cmac nls_utf8 cifs fscache libdes ccm vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) eset_rtp(OE) xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype iptable_filter iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ip> snd_seq_midi coretemp snd_seq_midi_event snd_rawmidi kvm_intel snd_seq kvm dell_wmi snd_seq_device rapl dell_smbios snd_timer dcdbas intel_cstate
