June 2023 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1212740] New: sometime inoperable after start run
by bugzilla_noreply＠suse.com 25 Jul '23

25 Jul '23

https://bugzilla.suse.com/show_bug.cgi?id=1212740 Bug ID: 1212740 Summary: sometime inoperable after start run Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: p.thoms(a)t-online.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 867822 --> https://bugzilla.suse.com/attachment.cgi?id=867822&action=edit Journal of operable start run Sometimes after start run the Laptop is inoperable, seems without some drivers, very slow and sticky behavior -- You are receiving this mail because: You are the assignee for the bug.

1 29

[Bug 1211224] New: How does Nvidia KMP work with dracut uefi_secureboot_cert solution when no MOK?
by bugzilla_noreply＠suse.com 24 Jul '23

24 Jul '23

https://bugzilla.suse.com/show_bug.cgi?id=1211224 Bug ID: 1211224 Summary: How does Nvidia KMP work with dracut uefi_secureboot_cert solution when no MOK? Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: jlee(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- This issue is derived from boo#1211166. The openSUSE tumbleweed kernel can work with MOK for Nvidia KMP now. But in the dracut uefi_secureboot_cert case, it doesn't use shim, which means that MOK is not available. How does Nvidia RPM works with dracut solution for modsign? Even when lockdown be enabled in kernel? Does dracut uefi_secureboot_cert solution support dynamic local generated one time key? Nvidia KMP needs the solution. -- You are receiving this mail because: You are the assignee for the bug.

1 6

[Bug 1212691] New: amdgpu Polaris11 not recognized during boot
by bugzilla_noreply＠suse.com 23 Jul '23

23 Jul '23

https://bugzilla.suse.com/show_bug.cgi?id=1212691 Bug ID: 1212691 Summary: amdgpu Polaris11 not recognized during boot Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: x86-64 OS: openSUSE Leap 15.5 Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: bdamasceno(a)hotmail.com.br QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 867809 --> https://bugzilla.suse.com/attachment.cgi?id=867809&action=edit Leap 15.5 boot log using 15.5 and 15.4 kernels After upgrading from leap 15.4 to 15.5, the new kernel can´t recognize my Polaris11 AMD GPU anymore. The display works only if I choose the last Leap 15.4 kernel that is still available on grub's menu. -- You are receiving this mail because: You are the assignee for the bug.

1 8

[Bug 1211353] New: [Build 20230511] LTP: failure in test statx09
by bugzilla_noreply＠suse.com 13 Jul '23

13 Jul '23

https://bugzilla.suse.com/show_bug.cgi?id=1211353 Bug ID: 1211353 Summary: [Build 20230511] LTP: failure in test statx09 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/3285771/modules/stat x09/steps/8 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: openQA Blocker: Yes ## Observation tst_kconfig.c:87: TINFO: Parsing kernel config '/proc/config.gz' tst_cmd.c:285: TINFO: Parsing mkfs.ext4 version tst_device.c:96: TINFO: Found free device 0 '/dev/loop0' tst_test.c:1093: TINFO: Formatting /dev/loop0 with ext4 opts='-O verity' extra opts='' mke2fs 1.46.5 (30-Dec-2021) tst_test.c:1558: TINFO: Timeout per run is 0h 00m 30s statx09.c:108: TBROK: ioctl(3, FS_IOC_ENABLE_VERITY) failed: EINVAL (22) tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 1... tst_device.c:412: TINFO: Likely gvfsd-trash is probing newly mounted fs, kill it to speed up tests. tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 2... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 3... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 4... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 5... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 6... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 7... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 8... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 9... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 10... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 11... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 12... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 13... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 14... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 15... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 16... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 17... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 18... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 19... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 20... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 21... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 22... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 23... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 24... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 25... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 26... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 27... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 28... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 29... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 30... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 31... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 32... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 33... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 34... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 35... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 36... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 37... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 38... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 39... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 40... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 41... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 42... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 43... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 44... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 45... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 46... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 47... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 48... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 49... tst_device.c:408: TINFO: umount('mnt_point') failed with EBUSY, try 50... tst_device.c:419: TWARN: Failed to umount('mnt_point') after 50 retries Summary: passed 0 failed 0 broken 1 skipped 0 warnings 1 tst_device.c:263: TWARN: ioctl(/dev/loop0, LOOP_CLR_FD, 0) no ENXIO for too long tst_tmpdir.c:342: TWARN: tst_rmdir: rmobj(/tmp/LTP_staCoVZgK) failed: remove(/tmp/LTP_staCoVZgK/mnt_point) failed; errno=16: EBUSY ### TEST statx09 COMPLETE >>> 6. openQA test in scenario opensuse-Tumbleweed-JeOS-for-kvm-and-xen-x86_64-jeos-ltp-syscalls@uefi_virtio-2G fails in [statx09](https://openqa.opensuse.org/tests/3285771/modules/statx09/steps/8) ## Test suite description ## Reproducible Fails since (at least) Build [20230503](https://openqa.opensuse.org/tests/3261645) ## Expected result Last good: [20230502](https://openqa.opensuse.org/tests/3259709) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=opensus… -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1212811] New: MokManager wants to remove needed cert
by bugzilla_noreply＠suse.com 10 Jul '23

10 Jul '23

https://bugzilla.suse.com/show_bug.cgi?id=1212811 Bug ID: 1212811 Summary: MokManager wants to remove needed cert Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: nwr10cst-oslnx(a)yahoo.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Firefox/102.0 Build Identifier: I'm currently using a kernel from Kernel:/stable:/Backport/standard/ (as explained in bug 1212808 ). Yesterday, I decided to update that kernel (from 6.3.9-lp154.2.1.g0df701d to 6.4.0-lp154.2.1.gd68cda5). To do this: I enabled the repo I used Yast software management I told it to install the newer kernel and remove the older one I then disabled the repo once again On reboot, I got a MokManager blue screen wanting to remove the cert that had been added for the older kernel. This seems a mistake, since it is still needed for the newer kernel. As best I can tell, Yast first removed the older kernel and that generated a request to remove the cert. It then installed the newer kernel, but because the cert was already loaded it did not generate a request to add the cert. (When I next update this kernel, I'll make sure to install the new kernel first, and then remove the old kernel afterwards to avoid this issue). Yes, I could have left it to the purge-kernels service to remove the old. But that would have instead removed the standard Leap 15.5 kernel, and I wanted to avoid that. Reproducible: Didn't try -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1212779] New: DELL0A78:00 27C6:0D42 Touchpad (gestures) doesn't work properly after resuming from suspend.
by bugzilla_noreply＠suse.com 10 Jul '23

10 Jul '23

https://bugzilla.suse.com/show_bug.cgi?id=1212779 Bug ID: 1212779 Summary: DELL0A78:00 27C6:0D42 Touchpad (gestures) doesn't work properly after resuming from suspend. Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: 64bit OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: neupanebishal2001(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Opensuse Tumbleweed release 6.3.7-1-default Windowing System: Wayland Hardware: Dell Inspiron 5515, ryzen 5 5500U Touchpad Information from hwinfo --mouse 50: PS/2 00.0: 10500 PS/2 Mouse [Created at input.249] Unique ID: AH6Q.rKa1+aijZtE Hardware Class: mouse Model: "DELL0A78:00 27C6:0D42 Touchpad" Vendor: 0x27c6 Device: 0x0d42 "DELL0A78:00 27C6:0D42 Touchpad" Compatible to: int 0x0210 0x0001 Device File: /dev/input/mice (/dev/input/mouse2) Device Files: /dev/input/mice, /dev/input/mouse2, /dev/input/event3, /dev/input/by-path/platform-AMDI0010:03-event-mouse, /dev/input/by-path/platform-AMDI0010:03-mouse Device Number: char 13:63 (char 13:34) Driver Info #0: Buttons: 1 Wheels: 0 XFree86 Protocol: explorerps/2 GPM Protocol: exps2 Config Status: cfg=no, avail=yes, need=no, active=unknown The exact problem: Touchpad gestures don't work at all after resuming from suspend and the pointer is also somewhat laggy. The bug occurs after closing the lid (which is configured to suspend) or suspending from anywhere else. Workaround: The workaround mentioned in https://bbs.archlinux.org/viewtopic.php?id=282440 also works in my case. So, I created a systemd service which executed before and after suspending and saved it under /usr/lib/systemd/system-sleep/make-touchpad-work.sleep The actual script: ------------------------------------------------------------------------------ #!/bin/sh case $1/$2 in pre/*) echo "Going to $2..." # Place your pre-suspend commands here, or `exit 0` if no pre-suspend action required modprobe -r i2c_hid_acpi ;; post/*) echo "Waking up from $2..." # Place your post suspend (resume) commands here, or `exit 0` if no post suspend action required sleep 2 modprobe i2c_hid_acpi ;; esac ------------------------------------------------------------------------------- As much as I understand it's just a workaround for the problem. Posting it here, so that it is addressed properly and get information about the potential errors it may cause (if there are any). And, this merge request was merged on NixOS for dell inspiron-5515 https://github.com/NixOS/nixos-hardware/commit/d7a12fcc071bff59bd0ead589c97… which seems to address the same issue. -- You are receiving this mail because: You are the assignee for the bug.

1 8

[Bug 1212506] New: cannot wake from suspend to ram
by bugzilla_noreply＠suse.com 10 Jul '23

10 Jul '23

https://bugzilla.suse.com/show_bug.cgi?id=1212506 Bug ID: 1212506 Summary: cannot wake from suspend to ram Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: msuchanek(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- This is a problem with kernel-default-6.3.4-lp154.5.1.gbfc9f93.x86_64 kernel-default-6.3.8-lp154.2.1.g627a49e.x86_64 and is a regression since kernel-default-5.14.21-150500.53.2.x86_64 The problem is not reproducible reliably - sometimes tying suspend right after boot waking the system works but most of the time it stays asleep and cannot be waked. -- You are receiving this mail because: You are the assignee for the bug.

1 8

[Bug 1212848] New: System lock up - kernel null pointer dereference - page fault
by bugzilla_noreply＠suse.com 07 Jul '23

07 Jul '23

https://bugzilla.suse.com/show_bug.cgi?id=1212848 Bug ID: 1212848 Summary: System lock up - kernel null pointer dereference - page fault Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: db(a)mail25.net QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 867882 --> https://bugzilla.suse.com/attachment.cgi?id=867882&action=edit journal-logs Booted up my laptop from full shutdown, logged in, Slack (Flatpak) started automatically, clicked on a few Slack channels and the system froze, couldn't switch between TTYs either. Forced shutdown with the power button. OS: openSUSE Tumbleweed 20230624 Kernel: 6.3.9-1-default DE: GNOME 44.2 Wayland Laptop: Lenovo ThinkPad T14s Gen 1 (AMD 4650U with integrated graphics) Attached some logs from the journal. -- You are receiving this mail because: You are the assignee for the bug.

1 9

[Bug 1212899] New: nothing provides 'kernel-devel = 6.4.0-lp154.6.g192b657'
by bugzilla_noreply＠suse.com 02 Jul '23

02 Jul '23

https://bugzilla.suse.com/show_bug.cgi?id=1212899 Bug ID: 1212899 Summary: nothing provides 'kernel-devel = 6.4.0-lp154.6.g192b657' Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: zeitlinie(a)yahoo.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Updating to kernel 6.4.0-lp154.6.g192b657-default does not allow to update to kernel-default-devel-6.4.0-lp154.6.1.g192b657.x86_64 kernel-syms-6.4.0-lp154.8.1.g192b657.x86_64 also, because of #### YaST2 conflicts list - generated 2023-06-30 19:53:10 #### nothing provides 'kernel-devel = 6.4.0-lp154.6.g192b657' needed by the to be installed kernel-default-devel-6.4.0-lp154.6.1.g192b657.x86_64 nothing provides 'kernel-default-devel = 6.4.0-lp154.8.g192b657' needed by the to be installed kernel-syms-6.4.0-lp154.8.1.g192b657.x86_64 Consequentially virtualbox kernel modules cannot be compiled, breaking also virtualbox -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 1212763] cifs: Content Duplication: <Windows share>Mounting Secondary Folder Shows Contents of First Folder in both the Mount Points
by bugzilla_noreply＠suse.com 30 Jun '23

30 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1212763 https://bugzilla.suse.com/show_bug.cgi?id=1212763#c2 Andreas Stieger <Andreas.Stieger(a)gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|GNOME |Kernel Assignee|gnome-bugs(a)suse.de |kernel-bugs(a)opensuse.org Summary|Content Duplication: |cifs: Content Duplication: |<Windows share>Mounting |<Windows share>Mounting |Secondary Folder Shows |Secondary Folder Shows |Contents of First Folder in |Contents of First Folder in |both the Mount Points |both the Mount Points Priority|P2 - High |P5 - None CC| |Andreas.Stieger(a)gmx.de --- Comment #2 from Andreas Stieger <Andreas.Stieger(a)gmx.de> --- Do not touch the priority field unless you are a developer. Moving to kernel as cigs is in the kernel. -- You are receiving this mail because: You are the assignee for the bug.

1 0