March 2023 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1209441] New: Thinkpad P16 Gen 1 doesnt detect monitor when plugged into docking station
by bugzilla_noreply＠suse.com 18 Apr '23

18 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1209441 Bug ID: 1209441 Summary: Thinkpad P16 Gen 1 doesnt detect monitor when plugged into docking station 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: mvetter(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Thinkpad P16 Gen 1 doesnt detect monitor when plugged into docking station. Notebook is running and attached to docking station. Only external monitor is used, internal one disabled in GNOME settings. Works fine. Occasionally screen tearing (quite unregular, every few days suddenly). I plug it out of the docking station and in again. Only the notebook montir is used and external one not properly detected. It is seen as "unknown monitor/device" but not with the actual name as usual. hwinfo file can be found in original bug report for system freeze upon connecting to docking station: https://bugzilla.suse.com/show_bug.cgi?id=1207900 -- You are receiving this mail because: You are the assignee for the bug.

1 16

[Bug 1205603] New: bpf lsm enabled but not included in LSM list
by bugzilla_noreply＠suse.com 17 Apr '23

17 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1205603 Bug ID: 1205603 Summary: bpf lsm enabled but not included in LSM list 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: mrueckert(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- During my system upgrades i noticed the following message: ```systemd[1]: bpf-lsm: BPF LSM hook not enabled in the kernel, BPF LSM not supported``` but we have: ```CONFIG_BPF_LSM=y``` i asked Frank Bui what it checks for. it checks for the string "bpf" in this list: ``` cat /sys/kernel/security/lsm lockdown,capability,apparmor ``` it seems ```CONFIG_LSM="integrity,apparmor"``` needs an update. -- You are receiving this mail because: You are the assignee for the bug.

1 8

[Bug 1208161] New: Timeout waiting for encrypted disk
by bugzilla_noreply＠suse.com 17 Apr '23

17 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1208161 Bug ID: 1208161 Summary: Timeout waiting for encrypted disk 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: --- Since openSUSE Tumbleweed 20230209 and kernel 6.1.10-1 I got an additional "sleep" time when booting the system. I suppose the following log entries give a hint on the reason. To my surprise the system nevertheless starts normally afterwards. Feb 11 15:50:14 transformer systemd[1]: dev-disk-by\x2duuid-47c6783a\x2d2b0\x24740\x2abd3\x24f0f43f63d8c.device: Job dev-disk-by\x2duuid-47c6783a\x2d2b0\x24740\x2abd3\x24f0f43f63d8c.device/start timed out. Feb 11 15:50:14 transformer systemd[1]: Timed out waiting for device /dev/disk/by-uuid/47c6783a-2b0$740*bd3$f0f43f63d8c. Feb 11 15:50:14 transformer systemd[1]: Dependency failed for Cryptography Setup for root. Feb 11 15:50:14 transformer systemd[1]: Dependency failed for Local Encrypted Volumes. Feb 11 15:50:14 transformer systemd[1]: cryptsetup.target: Job cryptsetup.target/start failed with result 'dependency'. Feb 11 15:50:14 transformer systemd[1]: systemd-cryptsetup(a)root.service: Job systemd-cryptsetup(a)root.service/start failed with result 'dependency'. Feb 11 15:50:14 transformer systemd[1]: dev-disk-by\x2duuid-47c6783a\x2d2b0\x24740\x2abd3\x24f0f43f63d8c.device: Job dev-disk-by\x2duuid-47c6783a\x2d2b0\x24740\x2abd3\x24f0f43f63d8c.device/start failed with result 'timeout'. Feb 11 15:50:14 transformer systemd[1]: Reached target Block Device Preparation for /dev/mapper/root. -- You are receiving this mail because: You are the assignee for the bug.

2 14

[Bug 1209197] New: Kernel 6.2.2 with older NVIDIA graphics won't boot (freeze after 4.5 sec into boot process)
by bugzilla_noreply＠suse.com 16 Apr '23

16 Apr '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1209197 Bug ID: 1209197 Summary: Kernel 6.2.2 with older NVIDIA graphics won't boot (freeze after 4.5 sec into boot process) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: sddrossy(a)aol.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hi! On Tumbleweed, updated this morning (20230311 with kernel 6.2.2) and since kernel 6.2.1 won't boot without "nomodeset", freezing when switching graphics after about 4.5 sec into boot: https://paste.opensuse.org/pastes/22f64611e02d Here is dmesg of successful boot with kernel 6.1.12 https://paste.opensuse.org/pastes/194765a7e091 output of lspci and inxi can be found in this thread https://forums.opensuse.org/t/no-boot-with-kernel-6-2/164791 -- You are receiving this mail because: You are the assignee for the bug.

1 13

[Bug 1188954] New: black screen on initial X open on Kaveri Radeon R7, /dev/dri/card0: No such file or directory with radeon.cik_support=0 amdgpu.cik_support=1
by bugzilla_noreply＠suse.com 14 Apr '23

14 Apr '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1188954 Bug ID: 1188954 Summary: black screen on initial X open on Kaveri Radeon R7, /dev/dri/card0: No such file or directory with radeon.cik_support=0 amdgpu.cik_support=1 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: mrmazda(a)earthlink.net QA Contact: qa-bugs(a)suse.de CC: sndirsch(a)suse.com Found By: --- Blocker: --- Created attachment 851460 --> http://bugzilla.opensuse.org/attachment.cgi?id=851460&action=edit Xorg.0.log and dmesg Initial summary: black screen on initial X open on Kaveri Radeon R7, /dev/dri/card0: No such file or directory with radeon.cik_support=0 amdgpu.cik_support=1 To reproduce: 1-boot with included on kernel cmdline radeon.cik_support=0 amdgpu.cik_support=1 2-wait for X to fail to start 3-login on a tty 4-systemctl restart xdm Actual behavior: 1-X fails to start, finding no /dev/dri/card0, leaving login prompt on tty1 on display screen 2-X starts normally using amdgpu DDX driver Expected behavior: 1-X starts normally using amdgpu DDX driver Tested with kernels 5.12.13, 5.11.16, 5.7.11 # inxi -SGIay System: Host: asa88 Kernel: 5.12.13-1-default x86_64 bits: 64 compiler: gcc v: 11.1.1 parameters: BOOT_IMAGE=/boot/vmlinuz root=LABEL=tvgp07stw noresume ipv6.disable=1 net.ifnames=0 mitigations=auto consoleblank=0 radeon.cik_support=0 amdgpu.cik_support=1 video=1024x768@60 video=1440x900@60 drm.debug=0x1e log_buf_len=1M Console: tty pts/0 DM: TDM Distro: openSUSE Tumbleweed 20210730 Graphics: Device-1: AMD Kaveri [Radeon R7 Graphics] vendor: ASUSTeK driver: amdgpu v: kernel alternate: radeon bus-ID: 00:01.0 chip-ID: 1002:130f class-ID: 0300 Display: server: X.org 1.20.12 driver: loaded: vesa unloaded: fbdev,modesetting alternate: ati Message: Advanced graphics data unavailable for root. Info:...inxi: 3.3.06 Comments: 1-without radeon.cik_support=0 amdgpu.cik_support=1 on cmdline, X cannot be coaxed into using amdgpu DDX driver via /etc/X11/xorg.conf.d/*conf 2-without radeon.cik_support=0 amdgpu.cik_support=1, greeter startup completes (normally, on first try) using modesetting DIX driver -- You are receiving this mail because: You are the assignee for the bug.

1 27

[Bug 1209724] New: kernel can not be built for s390x because of outside array bounds
by bugzilla_noreply＠suse.com 13 Apr '23

13 Apr '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1209724 Bug ID: 1209724 Summary: kernel can not be built for s390x because of outside array bounds Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: S/390-64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: ada.lovelace(a)gmx.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Multiple packages can not be built for s390x because kernel-default can not be built for openSUSE Tumbleweed. The problem exist since version kernel-default-6.2.8. I can find following error message: [ 4176s] In function 'do_ip6t_set_ctl': [ 4176s] cc1: note: source object is likely at address zero [ 4176s] CC [M] drivers/net/wwan/mhi_wwan_mbim.o [ 4177s] CC [M] net/ipv6/netfilter/ip6table_filter.o [ 4177s] CC [M] drivers/net/wwan/rpmsg_wwan_ctrl.o [ 4179s] CC [M] net/ipv6/netfilter/ip6table_mangle.o [ 4179s] CC [M] drivers/net/wwan/t7xx/t7xx_pci.o [ 4180s] CC [M] drivers/net/wwan/t7xx/t7xx_pcie_mac.o [ 4180s] CC [M] net/ipv6/netfilter/ip6table_raw.o [ 4181s] CC [M] drivers/net/wwan/t7xx/t7xx_mhccif.o [ 4181s] CC [M] net/ipv6/netfilter/ip6table_security.o [ 4182s] CC [M] drivers/net/wwan/t7xx/t7xx_state_monitor.o [ 4182s] In file included from ./arch/s390/include/generated/asm/rwonce.h:1, [ 4182s] from ../include/linux/compiler.h:247, [ 4182s] from ../include/linux/build_bug.h:5, [ 4182s] from ../include/linux/bits.h:22, [ 4182s] from ../drivers/net/wwan/t7xx/t7xx_state_monitor.c:17: [ 4182s] In function 'preempt_count', [ 4182s] inlined from 't7xx_fsm_append_event' at ../drivers/net/wwan/t7xx/t7xx_state_monitor.c:439:43: [ 4182s] ../include/asm-generic/rwonce.h:44:26: error: array subscript 0 is outside array bounds of 'const volatile int[0]' [-Werror=array-bounds=] [ 4182s] 44 | #define __READ_ONCE(x) (*(const volatile __unqual_scalar_typeof(x) *)&(x)) [ 4182s] | ~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ [ 4182s] ../include/asm-generic/rwonce.h:50:9: note: in expansion of macro '__READ_ONCE' [ 4182s] 50 | __READ_ONCE(x); \ [ 4182s] | ^~~~~~~~~~~ [ 4182s] ../arch/s390/include/asm/preempt.h:17:16: note: in expansion of macro 'READ_ONCE' [ 4182s] 17 | return READ_ONCE(S390_lowcore.preempt_count) & ~PREEMPT_NEED_RESCHED; [ 4182s] | ^~~~~~~~~ [ 4182s] In function 't7xx_fsm_append_event': [ 4182s] cc1: note: source object is likely at address zero [ 4182s] In function 'preempt_count', [ 4182s] inlined from 't7xx_fsm_append_event' at ../drivers/net/wwan/t7xx/t7xx_state_monitor.c:439:43: [ 4182s] ../include/asm-generic/rwonce.h:44:26: error: array subscript 0 is outside array bounds of 'const volatile int[0]' [-Werror=array-bounds=] [ 4182s] 44 | #define __READ_ONCE(x) (*(const volatile __unqual_scalar_typeof(x) *)&(x)) [ 4182s] | ~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ [ 4182s] ../include/asm-generic/rwonce.h:50:9: note: in expansion of macro '__READ_ONCE' [ 4182s] 50 | __READ_ONCE(x); \ [ 4182s] | ^~~~~~~~~~~ [ 4182s] ../arch/s390/include/asm/preempt.h:17:16: note: in expansion of macro 'READ_ONCE' [ 4182s] 17 | return READ_ONCE(S390_lowcore.preempt_count) & ~PREEMPT_NEED_RESCHED; [ 4182s] | ^~~~~~~~~ [ 4182s] In function 't7xx_fsm_append_event': [ 4182s] cc1: note: source object is likely at address zero [ 4182s] In function 'preempt_count', [ 4182s] inlined from 't7xx_fsm_append_event' at ../drivers/net/wwan/t7xx/t7xx_state_monitor.c:439:43: [ 4182s] ../include/asm-generic/rwonce.h:44:26: error: array subscript 0 is outside array bounds of 'const volatile int[0]' [-Werror=array-bounds=] [ 4182s] 44 | #define __READ_ONCE(x) (*(const volatile __unqual_scalar_typeof(x) *)&(x)) [ 4182s] | ~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ [ 4182s] ../include/asm-generic/rwonce.h:50:9: note: in expansion of macro '__READ_ONCE' [ 4182s] 50 | __READ_ONCE(x); \ [ 4182s] | ^~~~~~~~~~~ [ 4182s] ../arch/s390/include/asm/preempt.h:17:16: note: in expansion of macro 'READ_ONCE' [ 4182s] 17 | return READ_ONCE(S390_lowcore.preempt_count) & ~PREEMPT_NEED_RESCHED; [ 4182s] | ^~~~~~~~~ [ 4182s] In function 't7xx_fsm_append_event': [ 4182s] cc1: note: source object is likely at address zero [ 4182s] cc1: all warnings being treated as errors [ 4182s] make[5]: *** [../scripts/Makefile.build:253: drivers/net/wwan/t7xx/t7xx_state_monitor.o] Error 1 -- You are receiving this mail because: You are the assignee for the bug.

2 7

[Bug 1209620] New: dup from 6.1.8-1 to 6.2.6-1-default breaks mount cifs user access to NAS
by bugzilla_noreply＠suse.com 11 Apr '23

11 Apr '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1209620 Bug ID: 1209620 Summary: dup from 6.1.8-1 to 6.2.6-1-default breaks mount cifs user access to NAS 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: rickbonanno(a)bellsouth.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- with Tumbleweed 6.1.8-1 and prior versions a user could mount a NAS connected via thunderbolt with "sudo mount -t cifs //169.254.8.252/NAS ~/Mount/NAS --verbose -o user=username" After distribution upgrade the user can no longer access the NAS and when attempting to access the mounted folder receives "Error opening directory 'directory name': No such file or or directory. This is repeatable: rollback to 6.1.8-1 NAS again becomes accessible to user, distribution upgrade again and user no longer has access. Prior to upgrade the owner of the cifs mounted folders is User with Read & Write Access. After upgrade, the owner of the cifs mounted folder is root with Read & Write access. -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 1191924] New: kernel-source.git/README outdated
by bugzilla_noreply＠suse.com 10 Apr '23

10 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1191924 Bug ID: 1191924 Summary: kernel-source.git/README outdated Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Linux Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: ohering(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- There is a section "Before You Commit -- Things To Check" in kernel-source.git/README, it will likely not work out of the box. According to rpm/kernel-binary.spec.in, at least three more packages beside the obvious gcc/make/patch need to be installed: BuildRequires: libopenssl-devel BuildRequires: libelf-devel BuildRequires: dwarves >= 1.21 Furthermore rapidquilt is not mentioned. It is not strictly required, but one can hardly live without it. -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1208756] New: Goodix GDIX1003/GT9110P i2c device is Unsupported
by bugzilla_noreply＠suse.com 03 Apr '23

03 Apr '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1208756 Bug ID: 1208756 Summary: Goodix GDIX1003/GT9110P i2c device is Unsupported 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: need2burn(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 865155 --> http://bugzilla.opensuse.org/attachment.cgi?id=865155&action=edit dmesg output I have a new version of a POS-X Ion 8 tablet that seems to have some hardware not yet supported by openSUSE. This doesn't work on any version of openSUSE. The manufacturer tells me it's a Goodix T080642-01D-GTC, with a GT9110P IC. The OS (openSUSE Tumbleweed 20230226 running 6.1.12-1-default) reports it under /sys/bus/i2c/devices as i2c-GDIX1003:00. No dmesg logs mention goodix, the driver does not load, and it does not pick up the touchscreen when loaded. Evtest does not show the device either. From what I can tell looking at the Goodix driver, it only refers to GDIX1001 and GDIX1002, and no mention of GDIX1003. Attaching dmesg and can provide any other information. -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 1209436] New: I915 hangs on Kernel vmlinuz-5.14.21-150400.24.49
by bugzilla_noreply＠suse.com 02 Apr '23

02 Apr '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1209436 Bug ID: 1209436 Summary: I915 hangs on Kernel vmlinuz-5.14.21-150400.24.49 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: x86-64 OS: openSUSE Leap 15.4 Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: llrainey15(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Got new kernel from zypper up. Rebooted and it hang on line switching from VGA to i915. Had to power off and select previous kernel. -- You are receiving this mail because: You are the assignee for the bug.

1 49

2023

2022

2021

2020

openSUSE Kernel Bugs March 2023