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

[Bug 1209524] New: Playstation DualSense driver might be resetting my NVMe SSD controller.
by bugzilla_noreply＠suse.com 01 Apr '23

01 Apr '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1209524 Bug ID: 1209524 Summary: Playstation DualSense driver might be resetting my NVMe SSD controller. 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: jorge.blasio(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/110.0 Build Identifier: Yesterday I was playing FFXIV and suddenly upon log in I tried a controller button combination and wham, client crashed and my Steam Library disappeared. Something similar has happened before so there it was, journalctl informed me my NVMe drive which holds my games was made read-only. However this time it wasn't a faulty drive, one message before the controller goes down, there's a DualSense error. I'm not a developer just a linux convert from a few years so it might not be this but it has happened 3 times already and the playstation driver line keeps appearing just before the controller reset. Reproducible: Always Steps to Reproduce: 1.Start Steam and connect a DualSense controller 2.Play 3. Actual Results: I haven't been able to reproduce it to the letter, I cannot make a controller button press trigger the SSD reset, but I've used a completely different type of controller (an arcade stick from another company in xinput mode) and the system is solid, played for hours. Expected Results: Using the DualSense controller without my system losing SSD access. lavadrop5@klaasje:~> sudo journalctl -k -r -b -2 mar 19 12:49:12 klaasje kernel: audit: type=1305 audit(1679251752.338:485): op=set audit_enabled=0 old=1 auid=4294967295 ses=4294967295 subj=unconfined res=1 mar 19 12:49:12 klaasje kernel: audit: type=1305 audit(1679251752.338:485): op=set audit_enabled=0 old=1 auid=4294967295 ses=4294967295 subj=unconfined res=1 mar 19 12:49:12 klaasje kernel: audit: type=1305 audit(1679251752.310:484): op=set audit_pid=0 old=1241 auid=4294967295 ses=4294967295 subj=unconfined res=1 mar 19 12:49:12 klaasje kernel: kauditd_printk_skb: 55 callbacks suppressed mar 19 12:49:11 klaasje kernel: wlp6s0: deauthenticating from 0c:73:29:a1:49:da by local choice (Reason: 3=DEAUTH_LEAVING) mar 19 12:49:10 klaasje kernel: nfsd: last server has exited, flushing export cache mar 19 12:49:10 klaasje kernel: rfkill: input handler enabled mar 19 12:29:49 klaasje kernel: nvme1n1: detected capacity change from 3907029168 to 0 mar 19 12:29:49 klaasje kernel: nvme nvme1: Disabling device after reset failure: -19 mar 19 12:29:49 klaasje kernel: nvme 0000:04:00.0: enabling device (0000 -> 0002) mar 19 12:29:49 klaasje kernel: nvme nvme1: Try "nvme_core.default_ps_max_latency_us=0 pcie_aspm=off" and report a bug mar 19 12:29:49 klaasje kernel: nvme nvme1: Does your device have a faulty power saving mode enabled? mar 19 12:29:49 klaasje kernel: nvme nvme1: controller is down; will reset: CSTS=0xffffffff, PCI_STATUS=0x10 mar 19 12:20:15 klaasje kernel: BTRFS: error (device nvme0n1p1: state EA) in cleanup_transaction:1984: errno=-5 IO failure mar 19 12:20:15 klaasje kernel: BTRFS error (device nvme0n1p1: state EA): Transaction aborted (error -5) mar 19 12:20:15 klaasje kernel: BTRFS warning (device nvme0n1p1: state E): Skipping commit of aborted transaction. mar 19 12:20:15 klaasje kernel: BTRFS info (device nvme0n1p1: state E): forced readonly mar 19 12:20:15 klaasje kernel: BTRFS: error (device nvme0n1p1) in btrfs_commit_transaction:2474: errno=-5 IO failure (Error while writing out transaction) mar 19 12:20:15 klaasje kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 5, rd 5, flush 0, corrupt 0, gen 0 mar 19 12:20:15 klaasje kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 5, rd 4, flush 0, corrupt 0, gen 0 mar 19 12:20:15 klaasje kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 4, rd 4, flush 0, corrupt 0, gen 0 mar 19 12:20:15 klaasje kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 4, rd 3, flush 0, corrupt 0, gen 0 mar 19 12:20:15 klaasje kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 3, rd 3, flush 0, corrupt 0, gen 0 mar 19 12:20:15 klaasje kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 3, rd 2, flush 0, corrupt 0, gen 0 mar 19 12:20:15 klaasje kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 2, rd 2, flush 0, corrupt 0, gen 0 mar 19 12:20:15 klaasje kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 2, rd 1, flush 0, corrupt 0, gen 0 mar 19 12:20:15 klaasje kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 1, rd 1, flush 0, corrupt 0, gen 0 mar 19 12:20:15 klaasje kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 1, rd 0, flush 0, corrupt 0, gen 0 mar 19 12:20:15 klaasje kernel: nvme0n1: detected capacity change from 1953525168 to 0 mar 19 12:20:15 klaasje kernel: nvme nvme0: Disabling device after reset failure: -19 mar 19 12:20:15 klaasje kernel: nvme 0000:01:00.0: enabling device (0000 -> 0002) mar 19 12:20:15 klaasje kernel: nvme nvme0: Try "nvme_core.default_ps_max_latency_us=0 pcie_aspm=off" and report a bug mar 19 12:20:15 klaasje kernel: nvme nvme0: Does your device have a faulty power saving mode enabled? mar 19 12:20:15 klaasje kernel: nvme nvme0: controller is down; will reset: CSTS=0xffffffff, PCI_STATUS=0x10 mar 19 11:57:40 klaasje kernel: amdgpu 0000:0b:00.0: amdgpu: Disabling VM faults because of PRT request! mar 19 11:57:23 klaasje kernel: input: Microsoft X-Box 360 pad 0 as /devices/virtual/input/input31 mar 19 11:57:09 klaasje kernel: perf: interrupt took too long (2583 > 2500), lowering kernel.perf_event_max_sample_rate to 77250 mar 19 11:46:37 klaasje kernel: playstation: probe of 0003:054C:0CE6.0008 failed with error -17 mar 19 11:46:37 klaasje kernel: playstation 0003:054C:0CE6.0008: Failed to create dualsense. mar 19 11:46:37 klaasje kernel: playstation 0003:054C:0CE6.0008: Duplicate device found for MAC address 48:18:8d:ed:26:c7. mar 19 11:46:37 klaasje kernel: playstation 0003:054C:0CE6.0008: hidraw7: USB HID v1.11 Gamepad [Sony Interactive Entertainment Wireless Controller] on usb-0000:0d:00.3-1.1/input3 mar 19 11:46:36 klaasje kernel: usb 2-1.1: Manufacturer: Sony Interactive Entertainment mar 19 11:46:36 klaasje kernel: usb 2-1.1: Product: Wireless Controller mar 19 11:46:36 klaasje kernel: usb 2-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 mar 19 11:46:36 klaasje kernel: usb 2-1.1: New USB device found, idVendor=054c, idProduct=0ce6, bcdDevice= 1.00 mar 19 11:46:36 klaasje kernel: usb 2-1.1: new high-speed USB device number 5 using xhci_hcd mar 19 11:42:14 klaasje kernel: input: Microsoft X-Box 360 pad 0 as /devices/virtual/input/input30 mar 19 11:39:12 klaasje kernel: BTRFS info (device dm-2): qgroup scan completed (inconsistency flag cleared) mar 19 11:32:08 klaasje kernel: input: Microsoft X-Box 360 pad 0 as /devices/virtual/input/input29 mar 19 11:29:28 klaasje kernel: playstation 0005:054C:0CE6.0007: Registered DualSense controller hw_version=0x00000413 fw_version=0x01040027 mar 19 11:29:28 klaasje kernel: input: Wireless Controller Touchpad as /devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:08.0/0000:08:00.3/usb3/3-5/3-5:1.0/bluetooth/hci0/hci0:256/0005:054C:0CE6.0007/input/input28 mar 19 11:29:28 klaasje kernel: input: Wireless Controller Motion Sensors as /devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:08.0/0000:08:00.3/usb3/3-5/3-5:1.0/bluetooth/hci0/hci0:256/0005:054C:0CE6.0007/input/input27 mar 19 11:29:28 klaasje kernel: input: Wireless Controller as /devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:08.0/0000:08:00.3/usb3/3-5/3-5:1.0/bluetooth/hci0/hci0:256/0005:054C:0CE6.0007/input/input26 mar 19 11:29:28 klaasje kernel: playstation 0005:054C:0CE6.0007: hidraw6: BLUETOOTH HID v1.00 Gamepad [Wireless Controller] on b0:a4:60:ea:ea:b0 mar 19 11:29:28 klaasje kernel: playstation 0005:054C:0CE6.0007: unknown main item tag 0x0 mar 19 11:29:28 klaasje kernel: hid-generic 0005:054C:0CE6.0007: input,hidraw6: BLUETOOTH HID v1.00 Gamepad [Wireless Controller] on b0:a4:60:ea:ea:b0 mar 19 11:29:28 klaasje kernel: input: Wireless Controller as /devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:08.0/0000:08:00.3/usb3/3-5/3-5:1.0/bluetooth/hci0/hci0:256/0005:054C:0CE6.0007/input/input25 mar 19 11:29:28 klaasje kernel: hid-generic 0005:054C:0CE6.0007: unknown main item tag 0x0 mar 19 11:29:28 klaasje kernel: Bluetooth: HIDP socket layer initialized mar 19 11:29:28 klaasje kernel: Bluetooth: HIDP (Human Interface Emulation) ver 1.2 -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1202078] Plasma wayland cannot be set as default with autologin (kernel bug)
by bugzilla_noreply＠suse.com 31 Mar '23

31 Mar '23

1 0

[Bug 1209980] New: Lenovo L14 Gen3, wifi card not recognized.
by bugzilla_noreply＠suse.com 31 Mar '23

31 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1209980 Bug ID: 1209980 Summary: Lenovo L14 Gen3, wifi card not recognized. Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: x86-64 OS: openSUSE Leap 15.4 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: carlos.e.r(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hi, on new Lenovo L14 Gen3 laptop, AMD CPU, the wifi hardware is not recognized. This is an enterprise class laptop. It is recognized with kernel from "Kernel:stable:Backports" "https://download.opensuse.org/repositories/Kernel:/stable:/Backport/standar…" Laicolasse:~ # uname -a Linux Laicolasse 6.2.8-lp154.3.gc9a94ac-default #1 SMP PREEMPT_DYNAMIC Tue Mar 28 07:54:15 UTC 2023 (c9a94ac) x86_64 x86_64 x86_64 GNU/Linux Laicolasse:~ # Perhaps the driver can be backported? *Information before updating kernel* Laicolasse:~ # inxi --bluetooth -n -N Network: Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169 IF: eth0 state: up speed: 100 Mbps duplex: full mac: f4:a8:0d:7a:49:01 Device-2: MEDIATEK MT7922 802.11ax PCI Express Wireless Network Adapter driver: N/A Bluetooth: Device-1: Foxconn / Hon Hai Wireless_Device type: USB driver: btusb Report: bt-adapter ID: hci0 state: up address: 60:E9:AA:A0:1A:4A Laicolasse:~ # Command "ip addr" displays info on just eth0 and lo. Journal: <https://paste.opensuse.org/pastes/ccc804e35e3c> (if you want it attached to bugzilla, just ask, but it is already there because I asked on mail list) Laicolasse:~ # lspci 00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne Root Complex 00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne IOMMU 00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host Bridge 00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host Bridge 00:02.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne PCIe GPP Bridge 00:02.3 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne PCIe GPP Bridge 00:02.4 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne PCIe GPP Bridge 00:02.6 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne PCIe GPP Bridge 00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host Bridge 00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir Internal PCIe GPP Bridge to Bus 00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 51) 00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 51) 00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 0 00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 1 00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 2 00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 3 00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 4 00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 5 00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 6 00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 7 01:00.0 Non-Volatile memory controller: KIOXIA Corporation Device 000c 03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 0e) 04:00.0 SD Host controller: O2 Micro, Inc. SD/MMC Card Reader Controller (rev 01) 06:00.0 Network controller: MEDIATEK Corp. MT7922 802.11ax PCI Express Wireless Network Adapter <======== 07:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Barcelo (rev d1) 07:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Renoir Radeon High Definition Audio Controller 07:00.2 Encryption controller: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) Platform Security Processor 07:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne USB 3.1 07:00.4 USB controller: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne USB 3.1 07:00.5 Multimedia controller: Advanced Micro Devices, Inc. [AMD] ACP/ACP3X/ACP6x Audio Coprocessor (rev 01) 07:00.6 Audio device: Advanced Micro Devices, Inc. [AMD] Family 17h/19h HD Audio Controller Laicolasse:~ # Laicolasse:~ # hwinfo --netcard 07: PCI 300.0: 0200 Ethernet controller [Created at pci.386] Unique ID: rBUF.Osz2B5WC6KD Parent ID: aYFK.nSObxEWmqk3 SysFS ID: /devices/pci0000:00/0000:00:02.3/0000:03:00.0 SysFS BusID: 0000:03:00.0 Hardware Class: network Model: "Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller" Vendor: pci 0x10ec "Realtek Semiconductor Co., Ltd." Device: pci 0x8168 "RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller" SubVendor: pci 0x17aa "Lenovo" SubDevice: pci 0x50ae Revision: 0x0e Driver: "r8169" Driver Modules: "r8169" Device File: eth0 I/O Ports: 0x2000-0x2fff (rw) Memory Range: 0xfd604000-0xfd604fff (rw,non-prefetchable) Memory Range: 0xfd600000-0xfd603fff (rw,non-prefetchable) IRQ: 41 (no events) HW Address: f4:a8:0d:7a:49:01 Permanent HW Address: f4:a8:0d:7a:49:01 Link detected: yes Module Alias: "pci:v000010ECd00008168sv000017AAsd000050AEbc02sc00i00" Driver Info #0: Driver Status: r8169 is active Driver Activation Cmd: "modprobe r8169" Config Status: cfg=no, avail=yes, need=no, active=unknown Attached to: #14 (PCI bridge) 27: PCI 600.0: 0280 Network controller [Created at pci.386] Unique ID: vTuk.elCpZcgOa6E Parent ID: AXjq.nSObxEWmqk3 SysFS ID: /devices/pci0000:00/0000:00:02.6/0000:06:00.0 SysFS BusID: 0000:06:00.0 Hardware Class: network Model: "MEDIATEK Network controller" Vendor: pci 0x14c3 "MEDIATEK Corp." Device: pci 0x0616 SubVendor: pci 0x17aa "Lenovo" SubDevice: pci 0xe0c6 Memory Range: 0xe0200000-0xe02fffff (ro,non-prefetchable,disabled) Memory Range: 0xfd400000-0xfd407fff (rw,non-prefetchable,disabled) IRQ: 255 (no events) Module Alias: "pci:v000014C3d00000616sv000017AAsd0000E0C6bc02sc80i00" Config Status: cfg=no, avail=yes, need=no, active=unknown Attached to: #28 (PCI bridge) Laicolasse:~ # *After kernel upgrade*, the list of kernel packages is: Laicolasse:~ # rpm -qa | grep kernel kernel-firmware-radeon-20230320-lp154.2.1.noarch kernel-firmware-brcm-20230320-lp154.2.1.noarch kernel-firmware-nfp-20230320-lp154.2.1.noarch kernel-default-6.2.8-lp154.3.1.gc9a94ac.x86_64 kernel-firmware-amdgpu-20230320-lp154.2.1.noarch kernel-firmware-bnx2-20230320-lp154.2.1.noarch kernel-default-optional-5.14.21-150400.24.46.1.x86_64 kernel-firmware-network-20230320-lp154.2.1.noarch kernel-firmware-usb-network-20230320-lp154.2.1.noarch kernel-firmware-all-20230320-lp154.2.1.noarch kernel-firmware-liquidio-20230320-lp154.2.1.noarch kernel-firmware-mwifiex-20230320-lp154.2.1.noarch kernel-firmware-ath10k-20230320-lp154.2.1.noarch kernel-default-5.14.21-150400.24.46.1.x86_64 kernel-firmware-media-20230320-lp154.2.1.noarch kernel-firmware-ueagle-20230320-lp154.2.1.noarch kernel-firmware-serial-20230320-lp154.2.1.noarch kernel-firmware-iwlwifi-20230320-lp154.2.1.noarch kernel-default-extra-5.14.21-150400.24.46.1.x86_64 kernel-firmware-qlogic-20230320-lp154.2.1.noarch kernel-firmware-dpaa2-20230320-lp154.2.1.noarch kernel-firmware-marvell-20230320-lp154.2.1.noarch kernel-firmware-ti-20230320-lp154.2.1.noarch kernel-firmware-realtek-20230320-lp154.2.1.noarch kernel-firmware-intel-20230320-lp154.2.1.noarch kernel-firmware-qcom-20230320-lp154.2.1.noarch kernel-firmware-chelsio-20230320-lp154.2.1.noarch kernel-firmware-nvidia-20230320-lp154.2.1.noarch kernel-firmware-bluetooth-20230320-lp154.2.1.noarch kernel-firmware-i915-20230320-lp154.2.1.noarch kernel-firmware-prestera-20230320-lp154.2.1.noarch purge-kernels-service-0-150200.8.6.1.noarch kernel-firmware-atheros-20230320-lp154.2.1.noarch kernel-firmware-mellanox-20230320-lp154.2.1.noarch kernel-firmware-platform-20230320-lp154.2.1.noarch kernel-firmware-ath11k-20230320-lp154.2.1.noarch kernel-firmware-mediatek-20230320-lp154.2.1.noarch kernel-firmware-sound-20230320-lp154.2.1.noarch Laicolasse:~ # Laicolasse:~ # ip addr 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether f4:a8:0d:7a:49:01 brd ff:ff:ff:ff:ff:ff altname enp3s0f0 inet 192.168.2.17/16 brd 192.168.255.255 scope global dynamic noprefixroute eth0 valid_lft 43148sec preferred_lft 43148sec inet6 fe80::f6a8:dff:fe7a:4901/64 scope link noprefixroute valid_lft forever preferred_lft forever 3: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000 link/ether ee:19:17:ef:15:3d brd ff:ff:ff:ff:ff:ff permaddr 60:e9:aa:a0:1a:49 altname wlp6s0 Laicolasse:~ # Network manager now recognizes wlan, and it works instantly. Although an ssh terminal seems to give slow response to typing, with an AP just 2 meters away. I can provide any other information you need, on request. -- You are receiving this mail because: You are the assignee for the bug.

1 10

[Bug 1207243] kernel 6.1.4 fails to boot: nvme0n1: No UUID available providing old NGUID
by bugzilla_noreply＠suse.com 31 Mar '23

31 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1207243 http://bugzilla.opensuse.org/show_bug.cgi?id=1207243#c19 --- Comment #19 from Daniel Wagner <daniel.wagner(a)suse.com> --- As user space is clearly starting (there systemd output), I think enabling the debug out verbose flags for the kernel and systemd would help a lot. And if possible try to start without the graphical environment, IIRC this a different systemd target for this. All of this can be set on the kernel command line. Though I don't remember this stuff off hand. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1207243] kernel 6.1.4 fails to boot: nvme0n1: No UUID available providing old NGUID
by bugzilla_noreply＠suse.com 31 Mar '23

31 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1207243 http://bugzilla.opensuse.org/show_bug.cgi?id=1207243#c18 --- Comment #18 from Chris Puttick <chris(a)twoten.is> --- This problem has persisted through multiple updates, only the 6.0.12 kernel completes starting up - if it's not kernel related as such, what do I need to do to identify the actual cause (and why does it boot ok with 6.0.12)? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1209499] New: System is freezing with current openSUSE Tumbleweed
by bugzilla_noreply＠suse.com 31 Mar '23

31 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1209499 Bug ID: 1209499 Summary: System is freezing with current openSUSE Tumbleweed 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: adrian.schroeter(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I updated today to current tumbleweed and noticed that I get a freezing system (sometimes just the GUI and sometimes entire network loss). Not sure when this started, because downgrading to last februar snapshot has the same issue now. I made sure that any trace of virtualbox and nvidia drivers got removed, but I can still triggering it by opening a web browser with many tabs. Last words in dmesg are: [ 209.486479] nouveau 0000:02:00.0: fifo: fault 01 [WRITE] at 0000000000048000 engine 03 [PEEPHOLE] client 08 [HUB/BAR_WRITE] reason 02 [PAGE_NOT_PRESENT] on channel 2 [001fcd0000 Xorg.bin[1343]] [ 209.486502] nouveau 0000:02:00.0: fifo:000000:0002:[Xorg.bin[1343]] rc scheduled [ 209.486509] nouveau 0000:02:00.0: fifo:000000: rc scheduled [ 209.486518] nouveau 0000:02:00.0: fifo: INTR 08000000 [ 209.486541] nouveau 0000:02:00.0: fifo:000000:0002:0002:[Xorg.bin[1343]] errored - disabling channel [ 209.486549] nouveau 0000:02:00.0: Xorg.bin[1343]: channel 2 killed! [ 209.503310] nouveau 0000:02:00.0: fifo: fault 01 [WRITE] at 0000000000048000 engine 03 [PEEPHOLE] client 08 [HUB/BAR_WRITE] reason 02 [PAGE_NOT_PRESENT] on channel 2 [001fcd0000 Xorg.bin[1343]] The last line is repeating in an endless loop afterwards, until the system is freezing entirely a few minutes later. The GFX card is a "NVIDIA Corporation GF119 [NVS 310] (rev a1)" running with two displays. -- You are receiving this mail because: You are the assignee for the bug.

1 11

[Bug 1209436] I915 hangs on Kernel vmlinuz-5.14.21-150400.24.49
by bugzilla_noreply＠suse.com 31 Mar '23

31 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1209436 https://bugzilla.suse.com/show_bug.cgi?id=1209436#c67 --- Comment #67 from Maintenance Automation <maint-coord+maintenance-robot(a)suse.de> --- SUSE-SU-2023:1710-1: An update that solves 19 vulnerabilities and has 111 fixes can now be installed. Category: security (important) Bug References: 1166486, 1177529, 1193629, 1197534, 1197617, 1198438, 1202353, 1202633, 1203200, 1203331, 1203332, 1204363, 1204993, 1205544, 1205846, 1206103, 1206224, 1206232, 1206459, 1206492, 1206493, 1206640, 1206824, 1206876, 1206877, 1206878, 1206880, 1206881, 1206882, 1206883, 1206884, 1206885, 1206886, 1206889, 1206894, 1206935, 1207051, 1207270, 1207328, 1207529, 1207560, 1207588, 1207589, 1207590, 1207591, 1207592, 1207593, 1207594, 1207603, 1207605, 1207606, 1207607, 1207608, 1207609, 1207610, 1207613, 1207615, 1207617, 1207618, 1207619, 1207620, 1207621, 1207623, 1207624, 1207625, 1207626, 1207628, 1207630, 1207631, 1207632, 1207634, 1207635, 1207636, 1207638, 1207639, 1207641, 1207642, 1207643, 1207644, 1207645, 1207646, 1207647, 1207648, 1207651, 1207653, 1207770, 1207773, 1207845, 1207875, 1208149, 1208153, 1208179, 1208183, 1208212, 1208290, 1208420, 1208428, 1208429, 1208449, 1208534, 1208541, 1208570, 1208598, 1208599, 1208601, 1208603, 1208605, 1208607, 1208628, 1208700, 1208741, 1208759, 1208776, 1208777, 1208784, 1208787, 1208816, 1208837, 1208843, 1208848, 1209008, 1209159, 1209188, 1209256, 1209258, 1209262, 1209291, 1209436, 1209457, 1209504 CVE References: CVE-2022-3523, CVE-2022-36280, CVE-2022-38096, CVE-2023-0045, CVE-2023-0461, CVE-2023-0597, CVE-2023-1075, CVE-2023-1076, CVE-2023-1078, CVE-2023-1095, CVE-2023-1118, CVE-2023-22995, CVE-2023-22998, CVE-2023-23000, CVE-2023-23004, CVE-2023-23559, CVE-2023-25012, CVE-2023-26545, CVE-2023-28328 Sources used: openSUSE Leap Micro 5.3 (src): kernel-default-base-5.14.21-150400.24.55.3.150400.24.22.7 openSUSE Leap 15.4 (src): kernel-obs-qa-5.14.21-150400.24.55.1, kernel-syms-5.14.21-150400.24.55.1, kernel-source-5.14.21-150400.24.55.2, kernel-default-base-5.14.21-150400.24.55.3.150400.24.22.7, kernel-obs-build-5.14.21-150400.24.55.3 SUSE Linux Enterprise Micro for Rancher 5.3 (src): kernel-default-base-5.14.21-150400.24.55.3.150400.24.22.7 SUSE Linux Enterprise Micro 5.3 (src): kernel-default-base-5.14.21-150400.24.55.3.150400.24.22.7 SUSE Linux Enterprise Micro for Rancher 5.4 (src): kernel-default-base-5.14.21-150400.24.55.3.150400.24.22.7 SUSE Linux Enterprise Micro 5.4 (src): kernel-default-base-5.14.21-150400.24.55.3.150400.24.22.7 Basesystem Module 15-SP4 (src): kernel-source-5.14.21-150400.24.55.2, kernel-default-base-5.14.21-150400.24.55.3.150400.24.22.7 Development Tools Module 15-SP4 (src): kernel-source-5.14.21-150400.24.55.2, kernel-syms-5.14.21-150400.24.55.1, kernel-obs-build-5.14.21-150400.24.55.3 SUSE Linux Enterprise Live Patching 15-SP4 (src): kernel-livepatch-SLE15-SP4_Update_10-1-150400.9.3.7 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206224] Dell notebook drains battery during sleep
by bugzilla_noreply＠suse.com 31 Mar '23

31 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1206224 https://bugzilla.suse.com/show_bug.cgi?id=1206224#c51 --- Comment #51 from Maintenance Automation <maint-coord+maintenance-robot(a)suse.de> --- SUSE-SU-2023:1710-1: An update that solves 19 vulnerabilities and has 111 fixes can now be installed. Category: security (important) Bug References: 1166486, 1177529, 1193629, 1197534, 1197617, 1198438, 1202353, 1202633, 1203200, 1203331, 1203332, 1204363, 1204993, 1205544, 1205846, 1206103, 1206224, 1206232, 1206459, 1206492, 1206493, 1206640, 1206824, 1206876, 1206877, 1206878, 1206880, 1206881, 1206882, 1206883, 1206884, 1206885, 1206886, 1206889, 1206894, 1206935, 1207051, 1207270, 1207328, 1207529, 1207560, 1207588, 1207589, 1207590, 1207591, 1207592, 1207593, 1207594, 1207603, 1207605, 1207606, 1207607, 1207608, 1207609, 1207610, 1207613, 1207615, 1207617, 1207618, 1207619, 1207620, 1207621, 1207623, 1207624, 1207625, 1207626, 1207628, 1207630, 1207631, 1207632, 1207634, 1207635, 1207636, 1207638, 1207639, 1207641, 1207642, 1207643, 1207644, 1207645, 1207646, 1207647, 1207648, 1207651, 1207653, 1207770, 1207773, 1207845, 1207875, 1208149, 1208153, 1208179, 1208183, 1208212, 1208290, 1208420, 1208428, 1208429, 1208449, 1208534, 1208541, 1208570, 1208598, 1208599, 1208601, 1208603, 1208605, 1208607, 1208628, 1208700, 1208741, 1208759, 1208776, 1208777, 1208784, 1208787, 1208816, 1208837, 1208843, 1208848, 1209008, 1209159, 1209188, 1209256, 1209258, 1209262, 1209291, 1209436, 1209457, 1209504 CVE References: CVE-2022-3523, CVE-2022-36280, CVE-2022-38096, CVE-2023-0045, CVE-2023-0461, CVE-2023-0597, CVE-2023-1075, CVE-2023-1076, CVE-2023-1078, CVE-2023-1095, CVE-2023-1118, CVE-2023-22995, CVE-2023-22998, CVE-2023-23000, CVE-2023-23004, CVE-2023-23559, CVE-2023-25012, CVE-2023-26545, CVE-2023-28328 Sources used: openSUSE Leap Micro 5.3 (src): kernel-default-base-5.14.21-150400.24.55.3.150400.24.22.7 openSUSE Leap 15.4 (src): kernel-obs-qa-5.14.21-150400.24.55.1, kernel-syms-5.14.21-150400.24.55.1, kernel-source-5.14.21-150400.24.55.2, kernel-default-base-5.14.21-150400.24.55.3.150400.24.22.7, kernel-obs-build-5.14.21-150400.24.55.3 SUSE Linux Enterprise Micro for Rancher 5.3 (src): kernel-default-base-5.14.21-150400.24.55.3.150400.24.22.7 SUSE Linux Enterprise Micro 5.3 (src): kernel-default-base-5.14.21-150400.24.55.3.150400.24.22.7 SUSE Linux Enterprise Micro for Rancher 5.4 (src): kernel-default-base-5.14.21-150400.24.55.3.150400.24.22.7 SUSE Linux Enterprise Micro 5.4 (src): kernel-default-base-5.14.21-150400.24.55.3.150400.24.22.7 Basesystem Module 15-SP4 (src): kernel-source-5.14.21-150400.24.55.2, kernel-default-base-5.14.21-150400.24.55.3.150400.24.22.7 Development Tools Module 15-SP4 (src): kernel-source-5.14.21-150400.24.55.2, kernel-syms-5.14.21-150400.24.55.1, kernel-obs-build-5.14.21-150400.24.55.3 SUSE Linux Enterprise Live Patching 15-SP4 (src): kernel-livepatch-SLE15-SP4_Update_10-1-150400.9.3.7 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1202353] New: kernel: replace mkinitrd wrapper with native dracut
by bugzilla_noreply＠suse.com 31 Mar '23

31 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1202353 Bug ID: 1202353 Summary: kernel: replace mkinitrd wrapper with native dracut 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: antonio.feijoo(a)suse.com QA Contact: qa-bugs(a)suse.de Blocks: 1202351 Found By: --- Blocker: --- +++ This bug was initially created as a clone of Bug #1202351 +++ Upstream support removed in March 2021 (https://github.com/dracutdevs/dracut/commit/43df4ee2) and deprecation announcement on factory mailing list in May 2021 (https://lists.opensuse.org/archives/list/factory@lists.opensuse.org/thread/…) ALP will not ship the mkinitrd wrapper, so it's better to get rid of it in Tumbleweed first. Affected packages that need to be updated before (at least): # zypper se --requires mkinitrd Loading repository data... Reading installed packages... S | Name | Summary | Type ---+---------------------+----------------------------------------------------+-------- | kernel-debug | A Debug Version of the Kernel | package i+ | kernel-default | The Standard Kernel | package | kernel-default-base | The Standard Kernel - base modules | package | kernel-kvmsmall | The Small Developer Kernel for KVM | package | kernel-pae | Kernel with PAE Support | package | kernel-vanilla | The Standard Kernel - without any SUSE patches | package i | mdadm | Utility for configuring "MD" software RAID devices | package -- You are receiving this mail because: You are the assignee for the bug.

1 39

[Bug 1208822] New: [Build 20230301] openQA test fails in cve-2022-0185
by bugzilla_noreply＠suse.com 31 Mar '23

31 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1208822 Bug ID: 1208822 Summary: [Build 20230301] openQA test fails in cve-2022-0185 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/3152361/modules/cve- 2022-0185/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 fsconfig03.c:62: TPASS: kernel seems to be fine on ext2 fsconfig03.c:62: TPASS: kernel seems to be fine on ext3 fsconfig03.c:62: TPASS: kernel seems to be fine on ext4 fsconfig03.c:62: TPASS: kernel seems to be fine on xfs fsconfig03.c:62: TPASS: kernel seems to be fine on btrfs fsconfig03.c:38: TBROK: fsopen() failed: ENODEV (19) Test process returned unkown none zero value (2). Test took approximately 0.424987542908639 seconds Some test output could not be parsed: 11 lines were ignored. openQA test in scenario opensuse-Tumbleweed-JeOS-for-kvm-and-xen-x86_64-jeos-ltp-cve@uefi_virtio-2G fails in [cve-2022-0185](https://openqa.opensuse.org/tests/3152361/modules/cve-2022-0… ## Test suite description ## Reproducible Fails since (at least) Build [20230301](https://openqa.opensuse.org/tests/3152039) ## Expected result Last good: [20230228](https://openqa.opensuse.org/tests/3150857) (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 9

[Bug 1209674] New: RISC-V Linux 6.3.0-rc3-25-default crashes on boot "Store/AMO access fault"
by bugzilla_noreply＠suse.com 31 Mar '23

31 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1209674 Bug ID: 1209674 Summary: RISC-V Linux 6.3.0-rc3-25-default crashes on boot "Store/AMO access fault" Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: RISC-V OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: kkaempf(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Board: VisionFive2, 8GB Image: openSUSE-Tumbleweed-RISC-V-JeOS-starfivevisionfive2.riscv64-2023.03.02-Build10.14.raw.xz (checksummed ok) Full log (after grub boot screen): Loading Linux 6.3.0-rc3-25-default ... Loading initial ramdisk ... EFI stub: Booting Linux Kernel... Unhandled exception: Store/AMO access fault EPC: 00000000fff48a98 RA: 00000000fff871ea TVAL: 0000000040000000 EPC: 0000000040201a98 RA: 00000000402401ea reloc adjusted SP: 00000000ff734a50 GP: 00000000ff736e00 TP: 0000000000000001 T0: 0000000041c3fb81 T1: 0000005643534952 T2: 0000004005435352 S0: 0000000040000000 S1: 0000000040000000 A0: 0000000040000000 A1: 00000000f8ab1000 A2: 00010d20106f5a4d A3: 0000000000200000 A4: 0000000001d42000 A5: 0000000000000000 A6: 0000000000000002 A7: 0000000000000000 S2: 0000000001d42000 S3: 00000000ff734c18 S4: 0000000001c3fc00 S5: 0000000000200000 S6: 00000000f8ab1000 S7: 0000000000000000 S8: 00000000fe45f490 S9: 0000000000000001 S10: 0000000000000000 S11: 0000000000000000 T3: 0002506400004550 T4: 0000000000000000 T5: 020600a000000000 T6: 0000000040000000 Code: b383 0385 be03 0405 be83 0485 bf03 0505 (e110) UEFI image [0x00000000fe44f000:0x00000000fe713fff] '/efi\boot\bootriscv64.efi' UEFI image [0x00000000f8ab1000:0x00000000fa7f2fff] resetting ... reset not supported yet ### ERROR ### Please RESET the board ### -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1209526] New: WOL not working with RTL8111/8168/8411 with 6.2.x kernel
by bugzilla_noreply＠suse.com 30 Mar '23

30 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1209526 Bug ID: 1209526 Summary: WOL not working with RTL8111/8168/8411 with 6.2.x kernel 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: jiivee(a)iki.fi QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Suspend / resume utilizing WOL (wake-on-LAN) stopped working when Tumbleweed went from 6.1.x kernels to 6.2.x kernels. It worked great until then for a long time. Ethernet interface still tells that wake-on-LAN is enabled like before (setting is defined in /etc/sysconfig/network/ifcfg-eth0). When machine suspends, ethernet adapter shuts down completely. Machine wakes up from suspend by pressing power button. $ ethtool eth0 | grep -i wake Supports Wake-on: pumbg Wake-on: g $ lspci | grep -i ethernet 05:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 09) I can see from system journal logs that nightly backups resumed that machine neatly with 6.1.12 kernel, but no longer with 6.2.0 and later kernels up and including version 6.2.6. There is nothing unusual logged into system journal as fas as I can tell. I haven��t changed any procedures myself. Tumbleweed updates have done all changes. I have also few other machines with different ethernet cards, where WOL still works with 6.2.x kernels. -- You are receiving this mail because: You are the assignee for the bug.

1 18

[Bug 1201066] kernel upgrade fails with Failed to enroll new keys
by bugzilla_noreply＠suse.com 30 Mar '23

30 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1201066 https://bugzilla.suse.com/show_bug.cgi?id=1201066#c38 --- Comment #38 from Maintenance Automation <maint-coord+maintenance-robot(a)suse.de> --- SUSE-SU-2023:1702-1: An update that solves one vulnerability, contains two features and has 10 fixes can now be installed. Category: security (important) Bug References: 1185232, 1185261, 1185441, 1185621, 1187071, 1187260, 1193282, 1198458, 1201066, 1202120, 1205588 CVE References: CVE-2022-28737 Jira References: PED-127, PED-1273 Sources used: openSUSE Leap Micro 5.3 (src): shim-15.7-150300.4.11.1 openSUSE Leap 15.4 (src): shim-15.7-150300.4.11.1 SUSE Linux Enterprise Micro for Rancher 5.3 (src): shim-15.7-150300.4.11.1 SUSE Linux Enterprise Micro 5.3 (src): shim-15.7-150300.4.11.1 SUSE Linux Enterprise Micro for Rancher 5.4 (src): shim-15.7-150300.4.11.1 SUSE Linux Enterprise Micro 5.4 (src): shim-15.7-150300.4.11.1 Basesystem Module 15-SP4 (src): shim-15.7-150300.4.11.1 SUSE Linux Enterprise High Performance Computing ESPOS 15 SP3 (src): shim-15.7-150300.4.11.1 SUSE Linux Enterprise High Performance Computing LTSS 15 SP3 (src): shim-15.7-150300.4.11.1 SUSE Linux Enterprise Real Time 15 SP3 (src): shim-15.7-150300.4.11.1 SUSE Linux Enterprise Server 15 SP3 LTSS 15-SP3 (src): shim-15.7-150300.4.11.1 SUSE Linux Enterprise Server for SAP Applications 15 SP3 (src): shim-15.7-150300.4.11.1 SUSE Manager Proxy 4.2 (src): shim-15.7-150300.4.11.1 SUSE Manager Retail Branch Server 4.2 (src): shim-15.7-150300.4.11.1 SUSE Manager Server 4.2 (src): shim-15.7-150300.4.11.1 SUSE Enterprise Storage 7.1 (src): shim-15.7-150300.4.11.1 SUSE Linux Enterprise Micro 5.1 (src): shim-15.7-150300.4.11.1 SUSE Linux Enterprise Micro 5.2 (src): shim-15.7-150300.4.11.1 SUSE Linux Enterprise Micro for Rancher 5.2 (src): shim-15.7-150300.4.11.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1208069] Leap 15.5 & Gecko rolling plasma does not revive video from suspend?
by bugzilla_noreply＠suse.com 30 Mar '23

30 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1208069 https://bugzilla.suse.com/show_bug.cgi?id=1208069#c23 --- Comment #23 from Fritz Hudnut <non.space.1(a)gmail.com> --- I'm in Leap 15.5 this morning, which is now suspending and reviving OK. Tomorrow might be the Gecko rolling day, that system does not revive from suspend. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1208069] Leap 15.5 & Gecko rolling plasma does not revive video from suspend?
by bugzilla_noreply＠suse.com 30 Mar '23

30 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1208069 https://bugzilla.suse.com/show_bug.cgi?id=1208069#c22 --- Comment #22 from Fritz Hudnut <non.space.1(a)gmail.com> --- Created attachment 866011 --> https://bugzilla.suse.com/attachment.cgi?id=866011&action=edit dmesg file from Leap 15.5 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1208069] Leap 15.5 & Gecko rolling plasma does not revive video from suspend?
by bugzilla_noreply＠suse.com 30 Mar '23

30 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1208069 https://bugzilla.suse.com/show_bug.cgi?id=1208069#c21 --- Comment #21 from Fritz Hudnut <non.space.1(a)gmail.com> --- Created attachment 866010 --> https://bugzilla.suse.com/attachment.cgi?id=866010&action=edit hwinfo file from Leap 15.5 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1207948] Lenovo T14s Gen3 AMD resume from hibernation ends in kernel panic
by bugzilla_noreply＠suse.com 30 Mar '23

30 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1207948 https://bugzilla.suse.com/show_bug.cgi?id=1207948#c38 --- Comment #38 from Takashi Iwai <tiwai(a)suse.com> --- I merged the patch from upstream to reduce the timeout to 20 seconds from 90 seconds. https://patchwork.kernel.org/project/linux-wireless/patch/20230329162038.86… At least this avoids the nasty kernel panic although it still takes time to get out of resume and the WiFi is still broken. The real fix still has to be worked on, of course. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206843] Lenovo T14s Gen3 AMD resume from sleep broken
by bugzilla_noreply＠suse.com 30 Mar '23

30 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1206843 https://bugzilla.suse.com/show_bug.cgi?id=1206843#c10 --- Comment #10 from Christian Goll <cgoll(a)suse.com> --- journalctl showed following suspicious logs entries: ``` Mar 30 16:24:57 denckbrett kernel: [drm:dm_late_init [amdgpu]] *ERROR* DM_MST: Failed to start MST Mar 30 16:24:57 denckbrett kernel: [drm:amdgpu_device_ip_late_init [amdgpu]] *ERROR* late_init of IP bl> Mar 30 16:24:57 denckbrett kernel: amdgpu 0000:33:00.0: PM: dpm_run_callback(): pci_pm_resume+0x0/0x90 > Mar 30 16:24:57 denckbrett kernel: amdgpu 0000:33:00.0: PM: failed to resume async: error -5 Mar 30 16:24:57 denckbrett kernel: OOM killer enabled. Mar 30 16:24:57 denckbrett kernel: Restarting tasks ... Mar 30 16:24:57 denckbrett kernel: usb 10-1: USB disconnect, device number 5 Mar 30 16:24:57 denckbrett kernel: usb 10-1.1: USB disconnect, device number 6 Mar 30 16:24:57 denckbrett kernel: usb 9-1: USB disconnect, device number 7 Mar 30 16:24:57 denckbrett kernel: usb 9-1.1: USB disconnect, device number 8 Mar 30 16:24:57 denckbrett kernel: usb 9-1.1.3: USB disconnect, device number 10 Mar 30 16:24:57 denckbrett kernel: done. Mar 30 16:24:57 denckbrett gnome-shell[19232]: libinput error: client bug: timer event16 keyboard: sche> Mar 30 16:24:57 denckbrett rtkit-daemon[2992]: The canary thread is apparently starving. Taking action. Mar 30 16:24:57 denckbrett rtkit-daemon[2992]: Demoting known real-time threads. Mar 30 16:24:57 denckbrett rtkit-daemon[2992]: Successfully demoted thread 1983 of process 1812 (/usr/l> Mar 30 16:24:57 denckbrett rtkit-daemon[2992]: Successfully demoted thread 20404 of process 20195 (/usr> Mar 30 16:24:57 denckbrett rtkit-daemon[2992]: Successfully demoted thread 19400 of process 19387 (/usr> Mar 30 16:24:57 denckbrett rtkit-daemon[2992]: Successfully demoted thread 19387 of process 19387 (/usr> Mar 30 16:24:57 denckbrett rtkit-daemon[2992]: Successfully demoted thread 19399 of process 19390 (/usr> Mar 30 16:24:57 denckbrett rtkit-daemon[2992]: Successfully demoted thread 19390 of process 19390 (/usr> Mar 30 16:24:57 denckbrett rtkit-daemon[2992]: Successfully demoted thread 19394 of process 19389 (/usr> Mar 30 16:24:57 denckbrett rtkit-daemon[2992]: Successfully demoted thread 19389 of process 19389 (/usr> Mar 30 16:24:57 denckbrett rtkit-daemon[2992]: Demoted 8 threads. Mar 30 16:24:57 denckbrett kernel: usb 9-1.2: USB disconnect, device number 9 Mar 30 16:24:57 denckbrett tlp[13786]: Error: tlp.service is not enabled, power saving will not apply o> Mar 30 16:24:57 denckbrett tlp[13787]: Error: tlp.service is not enabled, power saving will not apply o> Mar 30 16:24:57 denckbrett tlp[13786]: >>> Invoke 'systemctl enable tlp.service' to correct this! Mar 30 16:24:57 denckbrett tlp[13774]: Error: tlp.service is not enabled, power saving will not apply o> Mar 30 16:24:57 denckbrett tlp[13787]: >>> Invoke 'systemctl enable tlp.service' to correct this! Mar 30 16:24:57 denckbrett tlp[13774]: >>> Invoke 'systemctl enable tlp.service' to correct this! ``` -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206843] Lenovo T14s Gen3 AMD resume from sleep broken
by bugzilla_noreply＠suse.com 30 Mar '23

30 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1206843 https://bugzilla.suse.com/show_bug.cgi?id=1206843#c9 --- Comment #9 from Christian Goll <cgoll(a)suse.com> --- @sndirsch I am using the Lenovo Docking station. Suspend and Resume breaks when I remove it suspended from the docking station, wake it up (works) and then it breaks as soon as I suspend it again. I am suing the 5.14.21-150500.99.g89aeefb-default kernel right now. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206843] Lenovo T14s Gen3 AMD resume from sleep broken
by bugzilla_noreply＠suse.com 30 Mar '23

30 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1206843 https://bugzilla.suse.com/show_bug.cgi?id=1206843#c8 Stefan Dirsch <sndirsch(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sndirsch(a)suse.com --- Comment #8 from Stefan Dirsch <sndirsch(a)suse.com> --- @Christian Are you still testing with Dell docking station or did you meanwhile switched to the T14s Docking station? Meanwhile we received a Lenovo T14s docking station for testing here in Nuremberg. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1202353] kernel: replace mkinitrd wrapper with native dracut
by bugzilla_noreply＠suse.com 30 Mar '23

30 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1202353 Michal Suchanek <msuchanek(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks|1209957 | -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1202353] kernel: replace mkinitrd wrapper with native dracut
by bugzilla_noreply＠suse.com 30 Mar '23

30 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1202353 Lubos Kocman <lubos.kocman(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |1209957 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1209032] Keychron K8 kearboard kernel warning: unknown main item tag 0x0
by bugzilla_noreply＠suse.com 30 Mar '23

30 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1209032 https://bugzilla.suse.com/show_bug.cgi?id=1209032#c3 Marcos de Souza <mpdesouza(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #3 from Marcos de Souza <mpdesouza(a)suse.com> --- (In reply to Takashi Iwai from comment #2) > AFAIK, this 0 comes usually from a buggy firmware (doing some padding or > such), and it can be ignored. Ok, thanks. I sent a request to fwupd to add support for upgrading the keychron firmware, but first keychron company needs to upload their firmware to LVFS... so there is a long way until upgrading the keyboard firmwre using gnome-firmare... Either way, thanks for looking at the issue! -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1209254] New: No (wired) network with kernel 6.2.2, only detects 10Mbps
by bugzilla_noreply＠suse.com 30 Mar '23

30 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1209254 Bug ID: 1209254 Summary: No (wired) network with kernel 6.2.2, only detects 10Mbps 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: P.Suetterlin(a)royac.iac.es QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 865506 --> http://bugzilla.opensuse.org/attachment.cgi?id=865506&action=edit journalctl -b of boot with kernel 6.2.2 I just updated my Laptop (Lenovo T460p) to latest TW 20230312. After reboot, I had no (wired) network. The critical part seems it only sees a 10Mbps link: Mar 14 13:09:42 woodstock.pitnet kernel: e1000e 0000:00:1f.6 eth0: NIC Link is Up 10 Mbps Full Duplex, Flow Control: None Mar 14 13:09:38 woodstock.pitnet kernel: e1000e 0000:00:1f.6 eth0: 10/100 speed: disabling TSO This is with kernel 6.2.2. If I reboot the same system with the previous kernel (6.1.12) 1000Mbps is detected, and network comes up as usual. -- You are receiving this mail because: You are the assignee for the bug.

1 11

[Bug 1200983] mouse & keyboard not available after a reboot (needs replug the devices)
by bugzilla_noreply＠suse.com 30 Mar '23

30 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1200983 https://bugzilla.suse.com/show_bug.cgi?id=1200983#c21 --- Comment #21 from Michael Hirmke <opensuse(a)mike.franken.de> --- (In reply to Takashi Iwai from comment #20) > (In reply to Michael Hirmke from comment #19) > > (In reply to Takashi Iwai from comment #18) > > > (In reply to Michael Hirmke from comment #17) > > > > All USB keyboards and mice are affected. > > > > > > Do I understand correctly that, when you login via sddm, all USB keyboards > > > and mouses don't work, no matter how many keyboards / mouses are connected? > > > And, if you reconnect one of them, do they all start working? Or it's only > > > the reconnected one? > > > > No, there is alway only one mouse and one keyboard connected, but I tried 3 > > different keyboards and 2 different mice - and all of them show the same > > behaviour. > > So, if you connect two USB keyboards, both are gone? Also, it happens no > matter which port is used? I guess both yes, but such a thing is worth to > test. It is not possible to connect more than one keyboard and mouse directly, because this machine only has two thunderbolt connectors and my thunderbolt dock also has only two ports remaining. But I have to test, if the problem exists in both cases - directly connected or connected via the thunderbolt box. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1209254] No (wired) network with kernel 6.2.2, only detects 10Mbps
by bugzilla_noreply＠suse.com 30 Mar '23

30 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1209254 https://bugzilla.suse.com/show_bug.cgi?id=1209254#c12 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(P.Suetterlin@roya | |c.iac.es) --- Comment #12 from Takashi Iwai <tiwai(a)suse.com> --- Could you test the kernel in OBS home:tiwai:bsc1209254 repo? (only kernel-default, i.e. no nvidia.) It's a kernel with the revert of all e1000e changes between 6.1 and 6.2. Let's check it after. If this kernel is confirmed to work, we can go further for bisecting those commits. OTOH, if this doesn't work, it implies that the problem lies somewhere else. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1209805] Kernel regression: Possible integer underflow in input pipeline of ThinkPad trackpoint.
by bugzilla_noreply＠suse.com 30 Mar '23

30 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1209805 http://bugzilla.opensuse.org/show_bug.cgi?id=1209805#c20 --- Comment #20 from Honza Nijak� <honzikcernoh(a)gmail.com> --- Thanks to you for the help an the fix! -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1209805] Kernel regression: Possible integer underflow in input pipeline of ThinkPad trackpoint.
by bugzilla_noreply＠suse.com 30 Mar '23

30 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1209805 http://bugzilla.opensuse.org/show_bug.cgi?id=1209805#c19 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED Resolution|--- |FIXED --- Comment #19 from Takashi Iwai <tiwai(a)suse.com> --- OK, I pushed the fix patch to TW stable git branch. It'll be included in the later update kernel. You can keep my test kernel until the fix gets merged. Thanks for the report and testing! -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1209727] [Build 20230324] kernel crash when loading vboxdrv
by bugzilla_noreply＠suse.com 29 Mar '23

29 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1209727 https://bugzilla.suse.com/show_bug.cgi?id=1209727#c8 --- Comment #8 from Larry Finger <Larry.Finger(a)gmail.com> --- Those changes do not look as if anything critical was changed. Is it possible to see the script that openQA was testing? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1209727] [Build 20230324] kernel crash when loading vboxdrv
by bugzilla_noreply＠suse.com 29 Mar '23

29 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1209727 https://bugzilla.suse.com/show_bug.cgi?id=1209727#c7 Dominique Leuenberger <dleuenberger(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dleuenberger(a)suse.com Flags|needinfo? | --- Comment #7 from Dominique Leuenberger <dleuenberger(a)suse.com> --- Most recent qemu changes in Tumbleweed were: changes files: -------------- --- qemu.changes +++ qemu.changes @@ -1,0 +2,14 @@ +Wed Mar 22 09:29:52 UTC 2023 - Dario Faggioli <dfaggioli(a)suse.com> + +- Further fixes for bsc#1209546 +* Patches added: + test-vmstate-fix-bad-GTree-usage-use-aft.patch + +------------------------------------------------------------------- +Tue Mar 21 22:02:50 UTC 2023 - Dario Faggioli <dfaggioli(a)suse.com> + +- Fix bsc#1209546 +* Patches added: + qemu-osdep-Switch-position-of-extern-and.patch + +------------------------------------------------------------------- -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1209727] [Build 20230324] kernel crash when loading vboxdrv
by bugzilla_noreply＠suse.com 29 Mar '23

29 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1209727 https://bugzilla.suse.com/show_bug.cgi?id=1209727#c6 Larry Finger <Larry.Finger(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(dimstar@opensuse. |needinfo? |org) | --- Comment #6 from Larry Finger <Larry.Finger(a)gmail.com> --- (In reply to Takashi Iwai from comment #4) > Which kernel is in question? I see no CONFIG_PROVE_LOCKING changes in our > kernels at all. According to the logging from openQA, the kernel in question is 6.2.8-1-default #1 openSUSE Tumbleweed 3fa4abf6558707e35b8fd19fc1aa28b27d42fa When I run 6.2.8-1-default from the TW repos, VirtualBox works correctly with no errors. I have determined that the problems with CONFIG_PROVE_LOCKING are present in VirtualBox 6.1.42, and predate our recent changes in the locking that were needed to improve long-term stability on hosts with many processors and many guests where the graphics was broken, but the underlying guest OS could still be accessed via SSH. I see that the test in question was started with QEMU. Has it or KVM been changed resently? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1209805] Kernel regression: Possible integer underflow in input pipeline of ThinkPad trackpoint.
by bugzilla_noreply＠suse.com 29 Mar '23

29 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1209805 http://bugzilla.opensuse.org/show_bug.cgi?id=1209805#c18 Honza Nijak� <honzikcernoh(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(honzikcernoh@gmai | |l.com) | --- Comment #18 from Honza Nijak� <honzikcernoh(a)gmail.com> --- Sorry for the delay, was AFK, but the kernel you provided fixed the issue, thank you very much! -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1200983] mouse & keyboard not available after a reboot (needs replug the devices)
by bugzilla_noreply＠suse.com 29 Mar '23

29 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1200983 https://bugzilla.suse.com/show_bug.cgi?id=1200983#c20 --- Comment #20 from Takashi Iwai <tiwai(a)suse.com> --- (In reply to Michael Hirmke from comment #19) > (In reply to Takashi Iwai from comment #18) > > (In reply to Michael Hirmke from comment #17) > > > All USB keyboards and mice are affected. > > > > Do I understand correctly that, when you login via sddm, all USB keyboards > > and mouses don't work, no matter how many keyboards / mouses are connected? > > And, if you reconnect one of them, do they all start working? Or it's only > > the reconnected one? > > No, there is alway only one mouse and one keyboard connected, but I tried 3 > different keyboards and 2 different mice - and all of them show the same > behaviour. So, if you connect two USB keyboards, both are gone? Also, it happens no matter which port is used? I guess both yes, but such a thing is worth to test. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1208069] Leap 15.5 & Gecko rolling plasma does not revive video from suspend?
by bugzilla_noreply＠suse.com 29 Mar '23

29 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1208069 https://bugzilla.suse.com/show_bug.cgi?id=1208069#c20 --- Comment #20 from Takashi Iwai <tiwai(a)suse.com> --- Just run "hwinfo > hwinfo.txt" as root or such would be enough. Ditto for dmesg. This is the very starting point to see what hardware components are included. The debug of suspend/resume is often really tough, unfortunately, as it can't be done remotely and it can't leave useful debug info in many cases (because the device itself is suspended when something happens, hence you can't record it). If we are lucky, it's a crash and leaves some kernel Oops, etc. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1208069] Leap 15.5 & Gecko rolling plasma does not revive video from suspend?
by bugzilla_noreply＠suse.com 29 Mar '23

29 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1208069 https://bugzilla.suse.com/show_bug.cgi?id=1208069#c19 --- Comment #19 from Fritz Hudnut <non.space.1(a)gmail.com> --- (In reply to Takashi Iwai from comment #18) > Well, the request was the hwinfo program output and the dmesg program output > from openSUSE installations. Sure. I'm just booted in Sid today, so I was checking the command out there, which didn't seem "applicable" or installed. So I'm going to run #hwinfo or something like #cat hwinfo >hwinfo.log.txt ???? Or, something more "granular" in the hwinfo output?? I don't mess around "under the hood" so I'm looking for specific commands to run to provide the info you are looking for? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1209727] [Build 20230324] kernel crash when loading vboxdrv
by bugzilla_noreply＠suse.com 29 Mar '23

29 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1209727 https://bugzilla.suse.com/show_bug.cgi?id=1209727#c5 --- Comment #5 from Larry Finger <Larry.Finger(a)gmail.com> --- (In reply to Takashi Iwai from comment #4) > Which kernel is in question? I see no CONFIG_PROVE_LOCKING changes in our > kernels at all. I did not see the problem until I turned on that configuration variable, thus I thought that was the problem. I will take another look. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1200983] mouse & keyboard not available after a reboot (needs replug the devices)
by bugzilla_noreply＠suse.com 29 Mar '23

29 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1200983 https://bugzilla.suse.com/show_bug.cgi?id=1200983#c19 --- Comment #19 from Michael Hirmke <opensuse(a)mike.franken.de> --- (In reply to Takashi Iwai from comment #18) > (In reply to Michael Hirmke from comment #17) > > All USB keyboards and mice are affected. > > Do I understand correctly that, when you login via sddm, all USB keyboards > and mouses don't work, no matter how many keyboards / mouses are connected? > And, if you reconnect one of them, do they all start working? Or it's only > the reconnected one? No, there is alway only one mouse and one keyboard connected, but I tried 3 different keyboards and 2 different mice - and all of them show the same behaviour. And as described in https://bugzilla.suse.com/show_bug.cgi?id=1200983#c9 it has prpbably nothing to do with sddm, because the linux console is also affected - not for the mouse, but for the keyboard. > > > And yes, Iit is possible to access the machine via ssh. > > What exactly do you want me to check then? > > At the moment you have no input control after SDDM login, login via ssh. > Then get the dmesg output at first. You can get the hwinfo output at this > moment, too. It happens in a linux console, too. > > Run evtest as root and check whether the corresponding input device appears > there, and test whether the input reacts. > > If the input still doesn't work on the screen, reconnect. And confirm that > it's working, then get the dmesg output and hwinfo output. Ok. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1208069] Leap 15.5 & Gecko rolling plasma does not revive video from suspend?
by bugzilla_noreply＠suse.com 29 Mar '23

29 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1208069 https://bugzilla.suse.com/show_bug.cgi?id=1208069#c18 --- Comment #18 from Takashi Iwai <tiwai(a)suse.com> --- Well, the request was the hwinfo program output and the dmesg program output from openSUSE installations. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1208069] Leap 15.5 & Gecko rolling plasma does not revive video from suspend?
by bugzilla_noreply＠suse.com 29 Mar '23

29 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1208069 https://bugzilla.suse.com/show_bug.cgi?id=1208069#c17 --- Comment #17 from Fritz Hudnut <non.space.1(a)gmail.com> --- Spent a few minutes, while in Debian Sid to try to run "hwinfo" but Sid didn't understand the request. Did a quick google of "hwinfo" . . . possibly it is iinstalled on Leap, but not on Sid? In looking at a video on "hwinfo" it looks like possibly a large amount of information is provided? What specific commands would you like to see the output of in the hwinfo output and/or in dmesg?? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1208069] Leap 15.5 & Gecko rolling plasma does not revive video from suspend?
by bugzilla_noreply＠suse.com 29 Mar '23

29 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1208069 https://bugzilla.suse.com/show_bug.cgi?id=1208069#c16 --- Comment #16 from Fritz Hudnut <non.space.1(a)gmail.com> --- @Takashi: Sorry . . . perhaps because I didn't hear back, that I "moved on" . . . . I think the Leap side did get "fixed" . . . but I recall a few days back that the Gecko install continues to "not revive from suspend." I'm jammed right now, but when I get back to the Leap and Gecko partitions I'll try to check out your request and post it here. But, system is '12 Mac Pro with Quad-core i7, 16 GB RAM . . . . Reviving from suspend works fine on the machine running TW, Manjaro, and Debian systems. -- You are receiving this mail because: You are the assignee for the bug.

1 0