December 2022 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1202570] New: steam deck - echo freeze | tee -a /sys/powerstate glitches the screen
by bugzilla_noreply＠suse.com 02 Feb '23

02 Feb '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1202570 Bug ID: 1202570 Summary: steam deck - echo freeze | tee -a /sys/powerstate glitches the screen Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: monkeyboyted(a)yahoo.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Suspend seems to work in the latest kernel in kernel:HEAD repo. Software suspends seems to glitch the screen upon re-initialization. Wifi and changing to tty works. lsb_release -a LSB Version: n/a Distributor ID: openSUSE Description: openSUSE Tumbleweed Release: 20220817 Codename: n/a zypper info kernel-default Loading repository data... Reading installed packages... Information for package kernel-default: --------------------------------------- Repository : kernel-repo Name : kernel-default Version : 6.0~rc1-3.1.g7bd57d5 Arch : x86_64 Vendor : obs://build.opensuse.org/Kernel Installed Size : 273.3 MiB Installed : Yes Status : up-to-date Source package : kernel-default-6.0~rc1-3.1.g7bd57d5.nosrc Upstream URL : https://www.kernel.org/ Summary : The Standard Kernel Description : The standard kernel for both uniprocessor and multiprocessor systems. Source Timestamp: 2022-08-16 07:58:42 +0000 GIT Revision: 7bd57d59ba8c141be35bb5189487a899d04e76ec GIT Branch: master -- You are receiving this mail because: You are the assignee for the bug.

1 7

[Bug 1202566] New: Steam deck wakes up from hibernate with max brightness
by bugzilla_noreply＠suse.com 02 Feb '23

02 Feb '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1202566 Bug ID: 1202566 Summary: Steam deck wakes up from hibernate with max brightness Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: monkeyboyted(a)yahoo.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- echo 0x1e | sudo tee -a /sys/module/drm/parameters/debug [sudo] password for root: 0x1e -> echo disk | sudo tee -a /sys/power/state disk ~> dmesg > dmesg-suspend-from-disk-with-0x1e-enabled lsb_release -a LSB Version: n/a Distributor ID: openSUSE Description: openSUSE Tumbleweed Release: 20220817 Codename: n/a Linux steamdeck 6.0.0-rc1-1.gd997b88-default #1 SMP PREEMPT_DYNAMIC Thu Aug 18 14:44:01 UTC 2022 (d997b88) x86_64 x86_64 x86_64 GNU/Linux https://build.opensuse.org/project/show/home:tiwai:bsc1201418 -- You are receiving this mail because: You are the assignee for the bug.

1 10

[Bug 1188352] New: Can't enter LUKS password since kernel 5.13 on Pinebook Pro
by bugzilla_noreply＠suse.com 28 Jan '23

28 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1188352 Bug ID: 1188352 Summary: Can't enter LUKS password since kernel 5.13 on Pinebook Pro Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: jonasdcdm(a)mailbox.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 851029 --> http://bugzilla.opensuse.org/attachment.cgi?id=851029&action=edit dmesg Since the upgrade to kernel 5.13 it's no longer possible to enter the LUKS password on boot. The physical keyboard works fine in GRUB, but the LUKS prompt won't see it, it doesn't register any key press. Entering the password via serial console works, and the Pinebook Pro boots to the desktop, where the physical keyboard works again. Kernel 5.12.13-1 is still working fine. -- You are receiving this mail because: You are the assignee for the bug.

1 6

[Bug 1201121] New: kernel: spi-nor spi0.0: BFPT parsing failed. Please consider using SPI_NOR_SKIP_SFDP when declaring the flash
by bugzilla_noreply＠suse.com 28 Jan '23

28 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1201121 Bug ID: 1201121 Summary: kernel: spi-nor spi0.0: BFPT parsing failed. Please consider using SPI_NOR_SKIP_SFDP when declaring the flash Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: opensuse(a)mike.franken.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Starting with the Tumbleweed snapshot installed on June 7th I get kernel: spi-nor spi0.0: BFPT parsing failed. Please consider using SPI_NOR_SKIP_SFDP when declaring the flash in my journal on every boot. Running fwupdmgr I get fwupd[6102]: 12:26:06:0015 FuPluginDfu truncated DFU interface data, no bcdDFUVersion The daemon nevertheless is starting. Because there is no newer firmware for any of my devices I am not able to test, if an update would work despite these error messages. This is a XPS 13 9310 2-in-1/0NVVG0, BIOS 2.8.1 02/25/2022. -- You are receiving this mail because: You are the assignee for the bug.

1 8

[Bug 1198722] New: initialize useful compiled in LSMs by default
by bugzilla_noreply＠suse.com 27 Jan '23

27 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1198722 Bug ID: 1198722 Summary: initialize useful compiled in LSMs by default 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: dmueller(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Currently CONFIG_LSM is very minimal, not even listing the LSMs that we compile into the kernel, which requires manual fixing on kernel boot cmdline using the "lsm=" parameter. we can enable these * landlock: optional ability for user land applications to sandbox themselves * yama: optional restrict of use of ptrace for nonprivileged users * bpf: create eBPF based LSMs dynamically bpf was enabled earlier already, but reverted due to bsc#1197746 -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 1196048] New: audit file watches do not really work?
by bugzilla_noreply＠suse.com 27 Jan '23

27 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1196048 Bug ID: 1196048 Summary: audit file watches do not really work? 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: meissner(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- auditctl -e 1 auditctl -w /etc/issue if i do echo hallo >> /etc/issue -> not audited if i do vim /etc/issue ... remove hallo line and save ... -> audited cat /etc/issue -> not audited Not sure if I am doing it right. -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1194268] New: disable btrfs asserts in default kernels
by bugzilla_noreply＠suse.com 27 Jan '23

27 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1194268 Bug ID: 1194268 Summary: disable btrfs asserts in default kernels 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: dmueller(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- while chasing for I/O performance issues in virtualized environments (usecase Open Build Service package builds for example), I noticed that btrfs in our default kernel has asserts enabled. according to the Kconfig help setting, this setting is purely for development purposes. I suggested to move the setting CONFIG_BTRFS_ASSERT only into the debug flavors, however there was concerns that this affects finding memory corruptions and other hardware related issues. On the other side, in my brief testing it appeared disabling reduced code size noticeably (in dual-digit percentage range) and also improved IOPS on a FIO randrw test (on a cow file) by over 20%. I will replicate the tests to be sure. This bug is to track how to address the issue and making asserts purely developer only and disable them in production builds of the openSUSE distribution. -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1195297] New: fbtft spi screens no longer functions properly.
by bugzilla_noreply＠suse.com 27 Jan '23

27 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1195297 Bug ID: 1195297 Summary: fbtft spi screens no longer functions properly. Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: simonf.lees(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Connected to the raspberry pi on my Robot I have a small 3.2" display [1] (or a clone / older version) it connects via SPI on the raspberry pi's GPIO header. In the past i've had it working with the overlay at [2] and the fbtft driver. This kinda setup is pretty common in the embedded / hobbyist world, I don't use a desktop or anything just simple status apps using the framebuffer directly on the other hand it wouldn't be the end of the world if I moved to Qt. Today I finally got a chance to update and as of now I no longer have an /dev/fb1 (/dev/fb0 is hdmi) is that expected with my current setup? I had other issues with the update and had to grab a fresh image and re add my overlay and raspbery pi config so there is also a chance I missed something setting it up again. I've put some dmesg output from the older system the new system shows nothing and below that is an fbi command I use for testing. Log from previously working system: [ 59.468595] fbtft: module is from the staging directory, the quality is unknown, you have been warned. [ 59.714749] fb_ili9340: module is from the staging directory, the quality is unknown, you have been warned. [ 59.716023] fb_ili9340 spi0.0: fbtft_property_value: buswidth = 8 [ 59.716049] fb_ili9340 spi0.0: fbtft_property_value: debug = 0 [ 59.716063] fb_ili9340 spi0.0: fbtft_property_value: rotate = 270 [ 59.716079] fb_ili9340 spi0.0: fbtft_property_value: fps = 25 [ 59.716093] fb_ili9340 spi0.0: fbtft_property_value: txbuflen = 32768 [ 61.352903] graphics fb1: fb_ili9340 frame buffer, 320x240, 150 KiB video memory, 32 KiB buffer memory, fps=25, spi0.0 at 16 MHz Test command: sudo fbi -T 13 -d /dev/fb1 --noverbose 1-110313112A3.jpg 1. https://www.waveshare.com/wiki/3.2inch_RPi_LCD_(B) 2. https://github.com/swkim01/waveshare-dtoverlays -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1179894] New: warnings in OBS builds from kernel+initrd about "Warning: running kernel does not support fscaps"
by bugzilla_noreply＠suse.com 27 Jan '23

27 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1179894 Bug ID: 1179894 Summary: warnings in OBS builds from kernel+initrd about "Warning: running kernel does not support fscaps" 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: okurz(a)suse.com QA Contact: qa-bugs(a)suse.de CC: fvogt(a)suse.com, jslaby(a)suse.com, msuchanek(a)suse.com, okurz(a)suse.com, thomas.blume(a)suse.com, tiwai(a)suse.com Depends on: 1178401 Found By: --- Blocker: --- +++ This bug was initially created as a clone of Bug #1178401 +++ ## Observation https://build.opensuse.org/build/openSUSE:Factory/images/local/000product:o… shows repeated warnings about: ``` [ 14s] Warning: running kernel does not support fscaps [ 14s] Warning: running kernel does not support fscaps [ 14s] Warning: running kernel does not support fscaps [ 14s] Warning: running kernel does not support fscaps [ 14s] Warning: running kernel does not support fscaps [ 14s] Warning: running kernel does not support fscaps [ 14s] Warning: running kernel does not support fscaps [ 14s] Warning: running kernel does not support fscaps ``` ## Steps to reproduce Seemingly reproducible in any build of packages, e.g. https://build.opensuse.org/public/build/openSUSE:Factory/standard/x86_64/00… shows the same ## Expected result Only errors and warnings in the log that I as package/project maintainer can fix -- You are receiving this mail because: You are the assignee for the bug.

1 6

[kernel-bugs] [Bug 1178463] New: Flood of "usb usb{2,6}-port1: Cannot enable." messages
by bugzilla_noreply＠suse.com 27 Jan '23

27 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1178463 Bug ID: 1178463 Summary: Flood of "usb usb{2,6}-port1: Cannot enable." messages 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: lmb(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 843325 --> https://bugzilla.suse.com/attachment.cgi?id=843325&action=edit lsusb -vv With the 5.10.0rc2 kernel from Kernel:HEAD, I'm experiencing a flood of: ... [ 372.567942] usb usb2-port1: Cannot enable. Maybe the USB cable is bad? [ 374.686509] usb usb6-port1: Cannot enable. Maybe the USB cable is bad? [ 377.026495] usb usb2-port1: Cannot enable. Maybe the USB cable is bad? [ 378.986503] usb usb6-port1: Cannot enable. Maybe the USB cable is bad? [ 381.446415] usb usb2-port1: Cannot enable. Maybe the USB cable is bad? [ 383.290504] usb usb6-port1: Cannot enable. Maybe the USB cable is bad? [ 385.918496] usb usb2-port1: Cannot enable. Maybe the USB cable is bad? [ 387.586478] usb usb6-port1: Cannot enable. Maybe the USB cable is bad? [ 390.386475] usb usb2-port1: Cannot enable. Maybe the USB cable is bad? [ 391.894454] usb usb6-port1: Cannot enable. Maybe the USB cable is bad? ... The XPS 13 is connected to a Belkin Thunberbird dock. As far as I can tell, except for these messages, all USB connected peripherals (keyboard, mouse, webcam) are working. Attaching lsusb -vv and dmesg output. -- You are receiving this mail because: You are the assignee for the bug.

1 7