October 2021 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1189614] New: GPU hang problem in Kernel 5.13.8
by bugzilla_noreply＠suse.com 25 Nov '21

25 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1189614 Bug ID: 1189614 Summary: GPU hang problem in Kernel 5.13.8 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: imbearchild(a)outlook.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- To who this may concerned, I've met some problem on OpenGL applications. The screen freezes, but the sound and interaction are normal, except that the screen output does not change. You can switch to the kernel terminal with the Ctrl-Alt-Fx key combination, but even after the process that caused the problem is killed, the screen display still freezes, and does not recover. Kernel has message like this: ``` [ 111.900829] Asynchronous wait on fence 0000:00:02.0:kwin_x11[2517]:e88 timed out (hint:intel_atomic_commit_ready [i915]) [ 114.621866] i915 0000:00:02.0: [drm] Resetting rcs0 for preemption time out [ 114.621883] i915 0000:00:02.0: [drm] valley_x64[3756] context reset due to GPU hang [ 114.651360] i915 0000:00:02.0: [drm] GPU HANG: ecode 9:1:85dffffb, in valley_x64 [3756] [ 115.549923] i915 0000:00:02.0: [drm] Resetting rcs0 for preemption time out [ 115.549949] i915 0000:00:02.0: [drm] valley_x64[3756] context reset due to GPU hang [ 115.582029] i915 0000:00:02.0: [drm] GPU HANG: ecode 9:1:87f97cf9, in valley_x64 [3756] ``` I've also found a similar bug a on older kernel, see: https://bugzilla.redhat.com/show_bug.cgi?id=1843274 but it should have been fixed on the latest kernel. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[kernel-bugs] [Bug 1178013] New: Application Crash when using FUSE
by bugzilla_noreply＠suse.com 24 Nov '21

24 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1178013 Bug ID: 1178013 Summary: Application Crash when using FUSE 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: reiokorn(a)tutanota.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Please read this forum thread, with all the information about that bug that I can give you: https://forums.opensuse.org/showthread.php/546202-Cryptomator-Application-C… btw Leap is unaffected. -- You are receiving this mail because: You are the assignee for the bug.

1 10

[Bug 1192190] New: iwlwifi driver fails to load after restart
by bugzilla_noreply＠suse.com 24 Nov '21

24 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1192190 Bug ID: 1192190 Summary: iwlwifi driver fails to load after restart Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: lortegap(a)protonmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 853452 --> http://bugzilla.opensuse.org/attachment.cgi?id=853452&action=edit iwlwifi error output If I restart, iwlwifi for some reason fails to load, as you can see in the file I attached. It only happens when restarting, shutdowns are not affected. It can happen multiple times, but eventually there'll be a restart were the module loads just fine. Hardware is a Lenovo Ideapad 5 15ITL05 laptop, Intel(R) Wireless-AC 9560 chip -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 1191980] New: Touchpad not working during and after install
by bugzilla_noreply＠suse.com 22 Nov '21

22 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1191980 Bug ID: 1191980 Summary: Touchpad not working during and after install Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: x86-64 OS: openSUSE Leap 15.3 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: bschouten(a)protonmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hello, I have a Fujitsu Lifebook T725 where the touchpad device does not work during the 15.3 Leap installation or after the installation. I have been able to duplicate this issue across multiple installation medias, and multiple machines with the same hardware spec. The solution thus far has been to add the following line to /etc/grub/defaults: GRUB_CMDLINE_LINUX="i8042.notimeout i8042.nomux" I'm not sure if something like this should be included in the kernel for the distribution, but I have had to do the same for Tumbleweed. Thank you for your time and trouble! - Bill -- You are receiving this mail because: You are the assignee for the bug.

1 15

[Bug 1192118] New: [Build 20211027] openQA test fails in finit_module02
by bugzilla_noreply＠suse.com 18 Nov '21

18 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1192118 Bug ID: 1192118 Summary: [Build 20211027] openQA test fails in finit_module02 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/1998049/modules/fini t_module02/steps/7 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 Found By: openQA Blocker: Yes ## Observation openQA test in scenario opensuse-Tumbleweed-JeOS-for-kvm-and-xen-x86_64-jeos-ltp-syscalls@uefi_virtio-2G fails in [finit_module02](https://openqa.opensuse.org/tests/1998049/modules/finit_mod… failed # echo 'OpenQA::run_ltp.pm: Starting finit_module02' > /dev/ttyS0; echo EuAAc-$?- EuAAc-0- # finit_module02; echo "### TEST finit_module02 COMPLETE >>> $?" tst_test.c:1363: TINFO: Timeout per run is 0h 05m 00s finit_module02.c:119: TPASS: TestName: invalid-fd : EBADF (9) fin�� finit_module02 finit_module02.c:119: TPASS: TestName: invalid-fd : EBADF (9) finit_module02.c:119: TPASS: TestName: zero-fd : EINVAL (22) finit_module02.c:119: TPASS: TestName: null-param : EFAULT (14) finit_module02.c:119: TPASS: TestName: invalid-param : EINVAL (22) finit_module02.c:119: TPASS: TestName: invalid-flags : EINVAL (22) finit_module02.c:119: TPASS: TestName: no-perm : EPERM (1) finit_module02.c:119: TPASS: TestName: module-exists : EEXIST (17) finit_module02.c:119: TFAIL: TestName: file-not-readable expected EBADF: ETXTBSY (26) finit_module02.c:119: TPASS: TestName: directory : EINVAL (22) Failed. Test took approximately 0.0326297609935864 seconds Some test output could not be parsed: 12 lines were ignored. ## Test suite description ## Reproducible Fails since (at least) Build [20211026](https://openqa.opensuse.org/tests/1994788) ## Expected result Last good: [20211025](https://openqa.opensuse.org/tests/1992656) (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 3

[Bug 1192047] New: Camera module does not work with ov5647 device on RPi3B+
by bugzilla_noreply＠suse.com 12 Nov '21

12 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1192047 Bug ID: 1192047 Summary: Camera module does not work with ov5647 device on RPi3B+ Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: guillaume.gardet(a)arm.com QA Contact: qa-bugs(a)suse.de CC: afaerber(a)suse.com, dmueller(a)suse.com, mbrugger(a)suse.com Found By: --- Blocker: --- Created attachment 853365 --> http://bugzilla.opensuse.org/attachment.cgi?id=853365&action=edit dmesg log I tried to use an IR camera module, based on OV5647 device, but I fail to get it working. On top of Tumbleweed, I installed raspberrypi-firmware-extra and created /boot/efi/extraconfig.txt with: # Camera IR ov5647 start_x=1 gpu_mem=128 dtoverlay=ov5647 # I2C dtparam=i2c_arm=on On reboot, ov5647 and bcm2835_v4l2 kernel drivers are loaded, but no error is displayed in dmesg and there is no /dev/video* devices. 'i2cdetect -l' retuns: i2c-0 i2c i2c-11-mux (chan_id 0) I2C adapter i2c-1 i2c bcm2835 (i2c@7e804000) I2C adapter i2c-2 i2c bcm2835 (i2c@7e805000) I2C adapter i2c-10 i2c i2c-11-mux (chan_id 1) I2C adapter i2c-11 i2c bcm2835 (i2c@7e205000) I2C adapter and 'i2cdetect -y 10' confirms that i2c address 36 is used by a driver, likely ov5647: 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- UU -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- Any idea what I am missing? -- You are receiving this mail because: You are the assignee for the bug.

1 8

[Bug 1188428] New: udev: failed to get device info: could not read 'authorized': No such file or directory
by bugzilla_noreply＠suse.com 08 Nov '21

08 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1188428 Bug ID: 1188428 Summary: udev: failed to get device info: could not read 'authorized': No such file or directory 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 kernel 5.13.0-1 (Jul 09) on boot I always get an error message (see subject) from boltd regarding device cd010000-0060-XPS 9370. All messages from boltd: boltd[1189]: bolt 0.9.1 starting up. boltd[1189]: manager: initializing store boltd[1189]: store: located at: /var/lib/boltd boltd[1189]: config: loading user config boltd[1189]: bouncer: initializing polkit boltd[1189]: watchdog: enabled [pulse: 90s] boltd[1189]: udev: initializing udev boltd[1189]: store: loading domains boltd[1189]: [cd010000-0060-domain? ] store: loading domain boltd[1189]: journal: opened for 'cd010000-0060'; size: 0 bytes boltd[1189]: [cd010000-0060-domain? ] domain: registered (bootacl: 16/16) boltd[1189]: store: loading devices boltd[1189]: [00cd30c8-3205 ] store: loading device boltd[1189]: [cd010000-0060 ] store: loading device boltd[1189]: global 'generation' set to '3' boltd[1189]: [da010000-0070 ] store: loading device boltd[1189]: power: state located at: /run/boltd/power boltd[1189]: power: force power support: yes boltd[1189]: udev: found 1 domain boltd[1189]: udev: enumerating devices boltd[1189]: probing: adding /sys/devices/pci0000:00/0000:00:1c.4/0000:03:00.0 to roots boltd[1189]: [cd010000-0060-domain0 ] bootacl: synchronizing journal boltd[1189]: security level set to 'user' boltd[1189]: [cd010000-0060-domain0 ] connected: as domain0 [user] (/sys/devices/pci0000:00/0000:00:1c.4/0000:03:00.0/0000:04:00.0/0000:05:00.0/domain0) boltd[1189]: [cd010000-0060-XPS 9370 ] udev: failed to get device info: could not read 'authorized': No such file or directory boltd[1189]: [cd010000-0060-XPS 9370 ] parent is (null)... boltd[1189]: [cd010000-0060-XPS 9370 ] store: updating device boltd[1189]: [cd010000-0060-XPS 9370 ] connected: unknown (/sys/devices/pci0000:00/0000:00:1c.4/0000:03:00.0/0000:04:00.0/0000:05:00.0/domain0/0-0) boltd[1189]: [00cd30c8-3205-TS3 Plus ] parent is cd010000-0060... boltd[1189]: [00cd30c8-3205-TS3 Plus ] connected: authorized (/sys/devices/pci0000:00/0000:00:1c.4/0000:03:00.0/0000:04:00.0/0000:05:00.0/domain0/0-0/0-3) boltd[1189]: [cd010000-0060-domain0 ] dbus: exported domain at /org/freedesktop/bolt/domains/cd010000_0060_6d18_a364_e809ccc32820 boltd[1189]: [00cd30c8-3205-TS3 Plus ] dbus: exported device at /org/freedesktop/bolt/devices/00cd30c8_3205... boltd[1189]: [cd010000-0060-XPS 9370 ] dbus: exported device at /org/freedesktop/bolt/devices/cd010000_0060... boltd[1189]: [da010000-0070-XPS 13 9370 ] dbus: exported device at /org/freedesktop/bolt/devices/da010000_0070... boltd[1189]: probing: started [1000] boltd[1189]: [00cd30c8-3205-TS3 Plus ] udev: device changed: authorized -> authorized boltd[1189]: probing: timeout, done: [2974874] (2000000) System info: Operating System: openSUSE Tumbleweed 20210715 KDE Plasma Version: 5.22.3 KDE Frameworks Version: 5.84.0 Qt Version: 5.15.2 Kernel Version: 5.13.1-1-default (64-bit) Graphics Platform: X11 Processors: 8 �� Intel�� Core�� i7-8550U CPU @ 1.80GHz Memory: 15,0 GiB of RAM Graphics Processor: Mesa DRI Intel�� UHD Graphics 620 This is a DELL XPS 9370 notebook. -- You are receiving this mail because: You are the assignee for the bug.

1 9

[Bug 1190095] New: Kernel 5.13.12: Intel graphics suddenly very slow on redraw
by bugzilla_noreply＠suse.com 04 Nov '21

04 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1190095 Bug ID: 1190095 Summary: Kernel 5.13.12: Intel graphics suddenly very slow on redraw 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: axel.braun(a)gmx.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I did a dup from 20210810 to 20210828, and since then I noticed a very slow redraw on KDE Plasma: when scolling in a terminal or in a window, the screen looks 'broken' for a moment, then the rendering is back. 30: PCI 02.0: 0300 VGA compatible controller (VGA) [Created at pci.386] Unique ID: _Znp.WlxwpsiDkK3 SysFS ID: /devices/pci0000:00/0000:00:02.0 SysFS BusID: 0000:00:02.0 Hardware Class: graphics card Model: "Intel CoffeeLake-H GT2 [UHD Graphics 630]" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x3e9b "CoffeeLake-H GT2 [UHD Graphics 630]" SubVendor: pci 0x17aa "Lenovo" SubDevice: pci 0x229f Driver: "i915" Driver Modules: "i915" Memory Range: 0xe9000000-0xe9ffffff (rw,non-prefetchable) Memory Range: 0xc0000000-0xcfffffff (ro,non-prefetchable) I/O Ports: 0x4000-0x403f (rw) Memory Range: 0x000c0000-0x000dffff (rw,non-prefetchable,disabled) IRQ: 143 (1116926 events) Module Alias: "pci:v00008086d00003E9Bsv000017AAsd0000229Fbc03sc00i00" Driver Info #0: Driver Status: i915 is active Driver Activation Cmd: "modprobe i915" Config Status: cfg=new, avail=yes, need=no, active=unknown Switching to nvidia chipset (prime-select) the issue is gone Other users to confirm this issue (see factory mailing list) -- You are receiving this mail because: You are the assignee for the bug.

1 18

[Bug 1190200] New: Severe graphics glitches in KDE applications when compositor is disabled
by bugzilla_noreply＠suse.com 03 Nov '21

03 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1190200 Bug ID: 1190200 Summary: Severe graphics glitches in KDE applications when compositor is disabled 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: psychonaut(a)nothingisreal.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I normally run KDE with the compositor disabled. In this mode, all KDE applications exhibit severe screen corruption: all new text or graphics that appear have a garbled appearance, to the extent that text is completely illegible. The corruption sometimes disappears after a few seconds or after the window is scrolled. The problem does not affect GTK+ applications. The problem can be worked around by using systemsettings5 to tell KDE to enable the compositor at startup. However, simply changing the rendering backend (XRender vs. OpenGL) has no effect. I am using an onboard Intel HD Graphics 630 controller with the i915 driver. I'm not sure if it's the kernel driver/firmware which is causing the problem, but based on past experience with Intel graphics glitches, I am tentatively assuming it is. The problem occurred after updating Tumbleweed from version 20210810 to version 20210827. (In case it's relevant, this included an update of kernel-default 5.13.8 to 5.13.12, and from kernel-firmware-i915 from 20210719 to 20210812.) The problem persists in version 20210830. Booting from the old 5.13.8 kernel doesn't work around the problem. I could also try reverting kernel-firmware-i915 if I can find or build an old package. -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 1191229] New: [Staging][rpm4.17] Kernel fails to build with rpm 4.17
by bugzilla_noreply＠suse.com 02 Nov '21

02 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1191229 Bug ID: 1191229 Summary: [Staging][rpm4.17] Kernel fails to build with rpm 4.17 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: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- RPM 4.17 has been submitted for inclusion into Tumbleweed. There is at least one backwards incompatible change that affects the kernel builds. The build fails with: [ 134s] error: /home/abuild/rpmbuild/SOURCES/kernel-source.spec: line 130: %verbose: unexpected argument [ 134s] 2< (%verbose) The problem there is that %{verbose} is no longer a 'function' taking an argument, but rather a variable, set to 0/1. In other packages where we encountered this issue, we simply gave up on the construct of using verbose to adjust the build log level -- You are receiving this mail because: You are the assignee for the bug.

1 1