April 2023 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1210329] VUL-0: CVE-2023-30772: kernel: use after free bug in da9150_charger_remove due to race condition
by bugzilla_noreply＠suse.com 16 Apr '23

16 Apr '23

http://bugzilla.suse.com/show_bug.cgi?id=1210329 SMASH SMASH <smash_bz(a)suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Whiteboard| |CVSSv3.1:SUSE:CVE-2023-3077 | |2:6.4:(AV:L/AC:H/PR:H/UI:N/ | |S:U/C:H/I:H/A:H) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1210329] VUL-0: CVE-2023-30772: kernel: use after free bug in da9150_charger_remove due to race condition
by bugzilla_noreply＠suse.com 16 Apr '23

16 Apr '23

1 0

[Bug 1210473] amdgpu[RX 590] Failed to read EDID from display
by bugzilla_noreply＠suse.com 15 Apr '23

15 Apr '23

http://bugzilla.suse.com/show_bug.cgi?id=1210473 Stefan Dirsch <sndirsch(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Failed to read EDID from |amdgpu[RX 590] Failed to |display |read EDID from display -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1210473] Failed to read EDID from display
by bugzilla_noreply＠suse.com 15 Apr '23

15 Apr '23

http://bugzilla.suse.com/show_bug.cgi?id=1210473 http://bugzilla.suse.com/show_bug.cgi?id=1210473#c1 Stefan Dirsch <sndirsch(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|gfx-bugs(a)suse.de |kernel-bugs(a)opensuse.org Component|X.Org |Kernel CC| |patrik.jakobsson(a)suse.com, | |tiwai(a)suse.com, | |tzimmermann(a)suse.com QA Contact|gfx-bugs(a)suse.de |qa-bugs(a)suse.de --- Comment #1 from Stefan Dirsch <sndirsch(a)suse.com> --- Sounds like a kernel issue to me. Reassigning. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1210329] VUL-0: kernel: use after free bug in da9150_charger_remove due to race condition
by bugzilla_noreply＠suse.com 15 Apr '23

15 Apr '23

http://bugzilla.suse.com/show_bug.cgi?id=1210329 http://bugzilla.suse.com/show_bug.cgi?id=1210329#c11 --- Comment #11 from Zheng Wang <hackerzheng666(a)gmail.com> --- (In reply to Marcus Meissner from comment #10) > I filed a CVE request with Mitre for this issue. Thanks a lot :) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1210470] New: samba mount following DFS to the wrong path
by bugzilla_noreply＠suse.com 14 Apr '23

14 Apr '23

http://bugzilla.suse.com/show_bug.cgi?id=1210470 Bug ID: 1210470 Summary: samba mount following DFS to the wrong path 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: luizluca(a)tre-sc.jus.br QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- In a share with a couple of DFS entries, sometimes the kernel follows the wrong path. Something like this: server: /share/dir/subdir1 -> msdfs:server\share1$ server: /share/dir/subdir2 -> msdfs:server\share2$ ... server: /share/dir/subdir11 -> msdfs:server\share11$ server: /share/dir/subdir12 -> msdfs:server\share12$ And in the client, we have: client: //server/dir/subdir1 on /mnt/share/dir/subdir1 client: //server/dir/subdir2 on /mnt/share/dir/subdir2 ... client: //server/dir/subdir11 on /mnt/share/dir/subdir11 client: //server/dir/subdir12 on /mnt/share/dir/subdir11 <<< (should be subdir12!) It always happens with older kernels (5.14 from opensuse/sle 15.4), where the first DFS is always used everywhere. However it still randomly happens with newer kernels like 6.2.9-1-default from opensuse tumbleweed. I can always reproduce it if I do a "ls subdir*" but it does not happen if I first "ls subdir12" and then "ls subdir*". It looks like a race condition, but it might be an off-by-one case as I only observed that with the last DFS in the directory (12th in my real case). -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1210329] VUL-0: kernel: use after free bug in da9150_charger_remove due to race condition
by bugzilla_noreply＠suse.com 14 Apr '23

14 Apr '23

http://bugzilla.suse.com/show_bug.cgi?id=1210329 Maintenance Automation <maint-coord+maintenance-robot(a)suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1210329] VUL-0: kernel: use after free bug in da9150_charger_remove due to race condition
by bugzilla_noreply＠suse.com 14 Apr '23

14 Apr '23

1 0

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

14 Apr '23

http://bugzilla.suse.com/show_bug.cgi?id=1206843 http://bugzilla.suse.com/show_bug.cgi?id=1206843#c31 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(cgoll(a)suse.com) | --- Comment #31 from Takashi Iwai <tiwai(a)suse.com> --- I noticed that the reason of the lack of WiFi was the missing kernel-default-extra; the ath11k driver module is included in kernel-default-extra. I pushed my backport patches to SLE15-SP5/for-next. Also I'll retest the stuff locally in the next week again. Hopefully they get fixed 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 14 Apr '23

14 Apr '23

http://bugzilla.suse.com/show_bug.cgi?id=1206843 http://bugzilla.suse.com/show_bug.cgi?id=1206843#c30 --- Comment #30 from Christian Goll <cgoll(a)suse.com> --- Installing the optional and extra rpms did the job. Wireless and Suspend/Resume works now without any flaw. Thanks for all Takashi -- 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 14 Apr '23

14 Apr '23

http://bugzilla.suse.com/show_bug.cgi?id=1206843 http://bugzilla.suse.com/show_bug.cgi?id=1206843#c29 --- Comment #29 from Takashi Iwai <tiwai(a)suse.com> --- Try to install kernel-default-extra and kernel-default-optional in addition, just to be sure. That's what I've tested on T14s here. It's strange that WiFi doesn't work -- that should be irrelevant with the dock. You have the systemd script to reload ath11k at resume (as in bug 1207948), right? -- 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 14 Apr '23

14 Apr '23

http://bugzilla.suse.com/show_bug.cgi?id=1206843 http://bugzilla.suse.com/show_bug.cgi?id=1206843#c28 --- Comment #28 from Christian Goll <cgoll(a)suse.com> --- Still the same problem, no suspend after disconnecting from the docking station and Wireless is not detected any more. Just installed the kernel-default-5.14.21-150500.1.1.g91d74f7.x86_64.rpm or did I miss additional rpms? -- 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 14 Apr '23

14 Apr '23

http://bugzilla.suse.com/show_bug.cgi?id=1206843 http://bugzilla.suse.com/show_bug.cgi?id=1206843#c27 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(cgoll(a)suse.com) --- Comment #27 from Takashi Iwai <tiwai(a)suse.com> --- I'm building yet another SLE15-SP5 kernel with the latest fixes landed in Linus tree yesterday. It's being built in OBS home:tiwai:bsc1206843-3 repo. The package will appear shortly later at http://download.opensuse.org/repositories/home:/tiwai:/bsc1206843-3/pool/ Christian, could you give it a try later? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1210271] nouveau: fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT]
by bugzilla_noreply＠suse.com 14 Apr '23

14 Apr '23

http://bugzilla.suse.com/show_bug.cgi?id=1210271 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- URL| |https://gitlab.freedesktop. | |org/xorg/driver/xf86-video- | |nouveau/-/issues/339 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[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 1210329] use after free bug in da9150_charger_remove due to race condition
by bugzilla_noreply＠suse.com 13 Apr '23

13 Apr '23

http://bugzilla.suse.com/show_bug.cgi?id=1210329 http://bugzilla.suse.com/show_bug.cgi?id=1210329#c9 --- Comment #9 from Zheng Wang <hackerzheng666(a)gmail.com> --- (In reply to Marcus Meissner from comment #8) > This happens only on module removal? > > I currently find it hard to see an attacker controlled exploitation vector > for this issue. No, this is a similar problem like CVE-2023-1855 CVE-2023-1670 and some other issues I have been reported. It assumes the attacker can access the device physically. When the driver-related device was unpluged, the remove function will be triggered. So this is an attack with special requirement. Here is the original report where I learned from [1]. [1] https://github.com/V4bel/CVE-2022-41218 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1210329] use after free bug in da9150_charger_remove due to race condition
by bugzilla_noreply＠suse.com 13 Apr '23

13 Apr '23

http://bugzilla.suse.com/show_bug.cgi?id=1210329 http://bugzilla.suse.com/show_bug.cgi?id=1210329#c8 --- Comment #8 from Marcus Meissner <meissner(a)suse.com> --- This happens only on module removal? I currently find it hard to see an attacker controlled exploitation vector for this issue. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1206814] [Build 20230104-1] openQA test fails in snapper_cleanup, 'snapper cleanup number' gets error 'Failure (error.something)'
by bugzilla_noreply＠suse.com 13 Apr '23

13 Apr '23

http://bugzilla.suse.com/show_bug.cgi?id=1206814 Arvin Schnell <aschnell(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |http://bugzilla.suse.com/sh | |ow_bug.cgi?id=1210150 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1209724] 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.suse.com/show_bug.cgi?id=1209724 http://bugzilla.suse.com/show_bug.cgi?id=1209724#c23 --- Comment #23 from Jiri Slaby <jslaby(a)suse.com> --- (In reply to Martin Liška from comment #19) > The fixed gcc13 reached Factory, Jiri do you want to revert the workaround? As it made sense to have the same fix in upstream, I tried to submit and succeeded. So it is now in 6.3-rc6 as: commit 362f0b6678ad1377c322a7dd237ea6785efc7342 Author: Jiri Slaby (SUSE) <jirislaby(a)kernel.org> Date: Fri Mar 31 08:35:15 2023 +0200 net: wwan: t7xx: do not compile with -Werror I only updated metadata and will keep the patch until 6.3 master->stable merge. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1209724] 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.suse.com/show_bug.cgi?id=1209724 http://bugzilla.suse.com/show_bug.cgi?id=1209724#c22 --- Comment #22 from Thomas Staudt <tstaudt(a)de.ibm.com> --- (In reply to Sarah Kriesch from comment #21) > Hi Thomas, > > you should wait for a Tumbleweed release of today. > 12 hours ago was a release, which is based on openSUSE Factory with the > content of 1 day before. > The code will be reviewed for openSUSE Factory, tested there and afterwards > forwarded to the different ports, where the specific releases will be built > (and tested with openQA). > > Sorry, that your mirror request has been too early from my point of view. Hi Sarah - no problem. The whole bug is mirrored and getting synced already. I only saw that - probably because of the SUSE bugzilla upgrade yesterday - comment #19 from the SUSE bug was not synced, and "woke up" the mirroring through a new comment. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[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 1209724] 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.suse.com/show_bug.cgi?id=1209724 http://bugzilla.suse.com/show_bug.cgi?id=1209724#c20 --- Comment #20 from LTC BugProxy <bugproxy(a)us.ibm.com> --- ------- Comment From tstaudt(a)de.ibm.com 2023-04-13 01:26 EDT------- . (triggering mirror of latest comment) -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1210329] use after free bug in da9150_charger_remove due to race condition
by bugzilla-noreply＠suse.com 12 Apr '23

12 Apr '23

http://bugzilla.suse.com/show_bug.cgi?id=1210329 http://bugzilla.suse.com/show_bug.cgi?id=1210329#c7 --- Comment #7 from Zheng Wang <hackerzheng666(a)gmail.com> --- (In reply to Takashi Iwai from comment #6) > OK, then let's toss to the security team. > > The corresponding upstream commit is 06615d11cc78162dfd5116efb71f29eb29502d37 Thanks for your effort. Hope you have a nice day. Best regards, Zheng -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1210329] use after free bug in da9150_charger_remove due to race condition
by bugzilla-noreply＠suse.com 12 Apr '23

12 Apr '23

http://bugzilla.suse.com/show_bug.cgi?id=1210329 http://bugzilla.suse.com/show_bug.cgi?id=1210329#c6 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Kernel |Security Flags|needinfo?(kernel-bugs@opens | |use.org) | Assignee|kernel-bugs(a)opensuse.org |security-team(a)suse.de --- Comment #6 from Takashi Iwai <tiwai(a)suse.com> --- OK, then let's toss to the security team. The corresponding upstream commit is 06615d11cc78162dfd5116efb71f29eb29502d37 -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.

1 0

needinfo requested: [Bug 1210329] use after free bug in da9150_charger_remove due to race condition
by bugzilla-noreply＠suse.com 12 Apr '23

12 Apr '23

Zheng Wang <hackerzheng666(a)gmail.com> has asked openSUSE Kernel Bugs <kernel-bugs(a)opensuse.org> for needinfo: Bug 1210329: use after free bug in da9150_charger_remove due to race condition http://bugzilla.suse.com/show_bug.cgi?id=1210329 --- Comment #5 from Zheng Wang <hackerzheng666(a)gmail.com> --- (In reply to Takashi Iwai from comment #4) > (In reply to Zheng Wang from comment #3) > > (In reply to Takashi Iwai from comment #2) > > > The fix patch has been already backported to stable and SLE15-SP4/SP5 > > > branches. > > > > May I ask if this issue will be assigned with a CVE number ? > > No, unless you explicitly ask for it. > Do you want us to request a CVE number? Sorry for my unfamiliar about bug-report policy. Thanks for your explain and I want to request a CVE number. Here is the credit Information: Zheng Wang(@xmzyshypnc), Zhuorao Yang(@A1ex), Yang Hu(@BlueSheep) and Zong Cao(@P1umer) If you need any other information, please feel free to let me know. Best reagrds, Zheng Wang

1 0

[Bug 1210329] use after free bug in da9150_charger_remove due to race condition
by bugzilla-noreply＠suse.com 12 Apr '23

12 Apr '23

http://bugzilla.suse.com/show_bug.cgi?id=1210329 http://bugzilla.suse.com/show_bug.cgi?id=1210329#c5 Zheng Wang <hackerzheng666(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kernel-bugs(a)opensuse.org Flags| |needinfo?(kernel-bugs@opens | |use.org) --- Comment #5 from Zheng Wang <hackerzheng666(a)gmail.com> --- (In reply to Takashi Iwai from comment #4) > (In reply to Zheng Wang from comment #3) > > (In reply to Takashi Iwai from comment #2) > > > The fix patch has been already backported to stable and SLE15-SP4/SP5 > > > branches. > > > > May I ask if this issue will be assigned with a CVE number ? > > No, unless you explicitly ask for it. > Do you want us to request a CVE number? Sorry for my unfamiliar about bug-report policy. Thanks for your explain and I want to request a CVE number. Here is the credit Information: Zheng Wang(@xmzyshypnc), Zhuorao Yang(@A1ex), Yang Hu(@BlueSheep) and Zong Cao(@P1umer) If you need any other information, please feel free to let me know. Best reagrds, Zheng Wang -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.

1 0

[Bug 1206843] Lenovo T14s Gen3 AMD resume from sleep broken
by bugzilla-noreply＠suse.com 12 Apr '23

12 Apr '23

http://bugzilla.suse.com/show_bug.cgi?id=1206843 http://bugzilla.suse.com/show_bug.cgi?id=1206843#c26 --- Comment #26 from Takashi Iwai <tiwai(a)suse.com> --- The above is the dmesg output from 6.3-rc6 kernel with S3. The dock is removed before S3 resume (around 35.0), then it spews the kernel warning from DRM core. The graphics on the laptop screen returns, nevertheless. Then, reconnecting the dock and configuring the graphics leads to another kernel warning (around 61.0), leading to the failure like: amdgpu 0000:33:00.0: [drm] *ERROR* No payload for [MST PORT:00000000e4d2801f] found in mst state 0000000002176b50 In the log, it's tried again around (62.9), leading to the similar error in the end. -- 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 12 Apr '23

12 Apr '23

http://bugzilla.suse.com/show_bug.cgi?id=1206843 http://bugzilla.suse.com/show_bug.cgi?id=1206843#c25 --- Comment #25 from Takashi Iwai <tiwai(a)suse.com> --- Created attachment 866267 --> http://bugzilla.suse.com/attachment.cgi?id=866267&action=edit dmesg from S3 test with dock removal on 6.3-rc6 kernel (failed) -- 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 12 Apr '23

12 Apr '23

http://bugzilla.suse.com/show_bug.cgi?id=1206843 http://bugzilla.suse.com/show_bug.cgi?id=1206843#c24 --- Comment #24 from Takashi Iwai <tiwai(a)suse.com> --- (In reply to Patrik Jakobsson from comment #22) > Christian, can you please try the kernel at home:patrikjakobsson:bsc1206843 I checked it and this kernel resulted in NULL dereference Oops at plugging the dock and configuring the graphics, unfortunately. Meanwhile, I backported DP-MST-related patches on top of my amdgpu backports, too (even with kABI workaround). You can try the kernel in OBS home:tiwai:bsc1206843-2 repo: http://download.opensuse.org/repositories/home:/tiwai:/bsc1206843-2/pool/ This should lead to the similar result as on the recent upstream 6.2.x and 6.3-rc. *HOWEVER* I noticed that the S3/S4 with the removal of the dock doesn't work properly even with the recent upstream 6.2.9 and 6.3-rc6. My patched kernel above suffers from the same problem, too. So this should be addressed in the upstream at first, then we may backport the fixes later. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1209724] kernel can not be built for s390x because of outside array bounds
by bugzilla-noreply＠suse.com 12 Apr '23

12 Apr '23

The content of this message was lost. It was probably cross-posted to multiple lists and previously handled on another list.

1 0

[Bug 1210329] New: use after free bug in da9150_charger_remove due to race condition
by bugzilla_noreply＠suse.com 12 Apr '23

12 Apr '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1210329 Bug ID: 1210329 Summary: use after free bug in da9150_charger_remove due to race condition Classification: openSUSE Product: openSUSE Distribution Version: Leap 16.0 Hardware: x86-64 OS: Linux Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: hackerzheng666(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- In da9150_charger_probe, &charger->otg_work is bound with da9150_charger_otg_work. da9150_charger_otg_ncb may be called to start the work. If we remove the module which will call da9150_charger_remove to make cleanup, there may be a unfinished work. The possible sequence is as follows: Fix it by canceling the work before cleanup in the da9150_charger_remove CPU0 CPUc1 |da9150_charger_otg_work da9150_charger_remove | power_supply_unregister | device_unregister | power_supply_dev_release | kfree(psy) | | | power_supply_changed(charger->usb); | //use There's no kernel log. Here is the patch link of [1] Linux-v6.3 and [2]patchwork [1] https://lore.kernel.org/all/CAHk-=whcaHLNpb7Mu_QX7ABwPgyRyfW-V8=v4Mv0S22fpj… [2] https://lore.kernel.org/all/20230328142620.323334485@linuxfoundation.org/ -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 1210271] New: nouveau: RIP: 0010:__handle_irq_event_percpu+0x150/0x1a0
by bugzilla_noreply＠suse.com 11 Apr '23

11 Apr '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1210271 Bug ID: 1210271 Summary: nouveau: RIP: 0010:__handle_irq_event_percpu+0x150/0x1a0 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: dufresnep(a)zoho.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 866217 --> http://bugzilla.opensuse.org/attachment.cgi?id=866217&action=edit first dmesg.txt This is a GTX 660 card I acquired in the last few days. Seems stable under Windows 11, although one of the 2 fans stops seconds after starting computer. Have issued with nouveau driver on probably all distributions tested when using drm-nouveau (softwre renderer seems fine, but too slow). Usually about CTX_SWITCH, (happend just now while doing Alt-Tab), but this one is an error in a irq_event: oh well, much more complex that I thought: journalctl -b -1 > err3.txt localhost:~ # ls -lh err3.txt -rw-r--r-- 1 root root 604K Apr 9 20:35 err3.txt localhost:~ # I'll try to attach the file. -- You are receiving this mail because: You are the assignee for the bug.

1 6

[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 1206846] sysfs: cannot create duplicate filename '/bus/nvmem/devices/rmem0'
by bugzilla_noreply＠suse.com 11 Apr '23

11 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1206846 https://bugzilla.suse.com/show_bug.cgi?id=1206846#c6 Ivan Ivanov <ivan.ivanov(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS Assignee|kernel-bugs(a)opensuse.org |ivan.ivanov(a)suse.com --- Comment #6 from Ivan Ivanov <ivan.ivanov(a)suse.com> --- Hi, sorry for delayed answer. Regarding rmem0 issue hopefully this patch [1] will accepted soon. It will fix this bug. [1] https://lore.kernel.org/all/20230411135035.106725-1-iivanov@suse.de/ -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1193596] No graphical display in Plymouth on Raspberry Pi 4
by bugzilla_noreply＠suse.com 11 Apr '23

11 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1193596 Ivan Ivanov <ivan.ivanov(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Kernel |Installation Assignee|kernel-bugs(a)opensuse.org |yast2-maintainers(a)suse.de QA Contact|qa-bugs(a)suse.de |jsrain(a)suse.com -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1193596] No graphical display in Plymouth on Raspberry Pi 4
by bugzilla_noreply＠suse.com 11 Apr '23

11 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1193596 https://bugzilla.suse.com/show_bug.cgi?id=1193596#c8 --- Comment #8 from Ivan Ivanov <ivan.ivanov(a)suse.com> --- I also think that some initrd adjustment for installation images should be made, but I don't think we at @kernel-bugs could help. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1210111] intel 3400 sata controller fail on 6.2.9 kernel
by bugzilla_noreply＠suse.com 11 Apr '23

11 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1210111 https://bugzilla.suse.com/show_bug.cgi?id=1210111#c4 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(werwolf131313@gma | |il.com) --- Comment #4 from Takashi Iwai <tiwai(a)suse.com> --- And the problem persists with the latest 6.2.x kernel on OBS Kernel:stable, too? If yes, what's about 6.3-rc in OBS Kernel:HEAD repo? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1210271] nouveau: fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT]
by bugzilla_noreply＠suse.com 11 Apr '23

11 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1210271 https://bugzilla.suse.com/show_bug.cgi?id=1210271#c4 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dufresnep(a)zoho.com, | |tiwai(a)suse.com Flags| |needinfo?(dufresnep(a)zoho.co | |m) --- Comment #4 from Takashi Iwai <tiwai(a)suse.com> --- The best for this kind of nouveau bug would be to report to the upstream, gitlab.freedesktop.org Issues. Care to open the report there and give back the URL? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1210131] Cannot install "kernel-default-devel"
by bugzilla_noreply＠suse.com 11 Apr '23

11 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1210131 https://bugzilla.suse.com/show_bug.cgi?id=1210131#c3 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Kernel |Patterns Assignee|kernel-bugs(a)opensuse.org |lubos.kocman(a)suse.com --- Comment #3 from Takashi Iwai <tiwai(a)suse.com> --- dwarves with the new libbpf for SLE15-SP5 should be available. In anyway, Kernel is no right category. Reassigned. -- 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 10 Apr '23

10 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1209805 https://bugzilla.suse.com/show_bug.cgi?id=1209805#c26 --- Comment #26 from Maintenance Automation <maint-coord+maintenance-robot(a)suse.de> --- SUSE-SU-2023:1802-1: An update that solves 11 vulnerabilities and has 25 fixes can now be installed. Category: security (important) Bug References: 1065729, 1109158, 1189998, 1193629, 1194869, 1198400, 1203200, 1206552, 1207168, 1207185, 1207574, 1208602, 1208815, 1208902, 1209052, 1209118, 1209256, 1209290, 1209292, 1209366, 1209532, 1209547, 1209556, 1209600, 1209634, 1209635, 1209636, 1209681, 1209684, 1209779, 1209788, 1209798, 1209799, 1209804, 1209805, 1210050 CVE References: CVE-2017-5753, CVE-2022-4744, CVE-2023-0394, CVE-2023-1281, CVE-2023-1513, CVE-2023-1582, CVE-2023-1637, CVE-2023-1652, CVE-2023-28327, CVE-2023-28464, CVE-2023-28466 Sources used: openSUSE Leap 15.4 (src): kernel-source-azure-5.14.21-150400.14.43.1, kernel-syms-azure-5.14.21-150400.14.43.1 Public Cloud Module 15-SP4 (src): kernel-source-azure-5.14.21-150400.14.43.1, kernel-syms-azure-5.14.21-150400.14.43.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 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 1209680] ata1.00: exception Emask 0x40 SAct 0x3f0 SErr 0xd0800 action 0x6 frozen
by bugzilla_noreply＠suse.com 10 Apr '23

10 Apr '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1209680 http://bugzilla.opensuse.org/show_bug.cgi?id=1209680#c9 John Shand <jshand2013(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #9 from John Shand <jshand2013(a)gmail.com> --- this was a once off. i will now close -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1210029] New: Can't hibernate laptop Lenovo L14 Gen 3 AMD
by bugzilla_noreply＠suse.com 07 Apr '23

07 Apr '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1210029 Bug ID: 1210029 Summary: Can't hibernate laptop Lenovo L14 Gen 3 AMD Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: x86-64 OS: openSUSE Leap 15.5 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: --- Created attachment 866050 --> http://bugzilla.opensuse.org/attachment.cgi?id=866050&action=edit journal using "Sleep State: Windows and Linux" Laptop can be suspended, but not hibernated. I am using "systemctl hibernate" as root. BIOS aka UEFI configuration has this selector: Sleep State: Windows and Linux vs Linux S3 hibernation In the first mode, screen goes to black for an instant, then pops for user password. I save the journal, and I see this: Apr 01 22:13:12 Beta.valinor kernel: Disabling non-boot CPUs ... Apr 01 22:13:12 Beta.valinor kernel: Wakeup pending. Abort CPU freeze I will attach the journal. I have been directed to read <https://wiki.archlinux.org/title/Power_management/Wakeup_triggers> and google that message, but so far, no success. On 15.4 I tried the second config option (Linux S3 hibernation) and it locked kernel hard, but journal was written. I will try again on 15.5 and report. I can also try kernel 6.2.8 from "Kernel:stable:Backports" on 15.4 -- You are receiving this mail because: You are the assignee for the bug.

1 25

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

06 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1209620 https://bugzilla.suse.com/show_bug.cgi?id=1209620#c2 --- Comment #2 from Paulo Alcantara <palcantara(a)suse.com> --- Ping? Could you also test the mount with 'forceuid,forcegid' options? -- 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 06 Apr '23

06 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1206843 https://bugzilla.suse.com/show_bug.cgi?id=1206843#c23 --- Comment #23 from Takashi Iwai <tiwai(a)suse.com> --- I pushed the backports of missing fixes and a few code corrections of amdgpu driver to users/tiwai/SLE15-SP5/for-next branch. Once when the DP-MST changes are merged, we'll catch up almost all in the latest 6.1.x tree code. -- 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 06 Apr '23

06 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1206843 https://bugzilla.suse.com/show_bug.cgi?id=1206843#c22 --- Comment #22 from Patrik Jakobsson <patrik.jakobsson(a)suse.com> --- Christian, can you please try the kernel at home:patrikjakobsson:bsc1206843 -- 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 06 Apr '23

06 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1206843 https://bugzilla.suse.com/show_bug.cgi?id=1206843#c21 --- Comment #21 from Takashi Iwai <tiwai(a)suse.com> --- Let's build the kernel with kABI breakage just for testing at first. You can pass --ignore-kabi option to scripts/tar-up.sh. -- 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 06 Apr '23

06 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1206843 https://bugzilla.suse.com/show_bug.cgi?id=1206843#c20 --- Comment #20 from Patrik Jakobsson <patrik.jakobsson(a)suse.com> --- Yeah the breakage is pretty bad drivers/gpu/drm/display/drm_dp_mst_topology.c:1502: warning: drm_dp_mst_get_port_malloc: modversion changed because of changes in struct drm_dp_mst_topology_mgr, struct drm_dp_mst_port drivers/gpu/drm/display/drm_dp_mst_topology.c:1520: warning: drm_dp_mst_put_port_malloc: modversion changed because of changes in struct drm_dp_mst_topology_mgr, struct drm_dp_mst_port drivers/gpu/drm/display/drm_dp_mst_topology.c:1701: warning: drm_atomic_get_mst_payload_state: modversion changed because of changes in struct drm_dp_mst_topology_state, struct drm_dp_mst_topology_mgr, struct drm_dp_mst_port drivers/gpu/drm/display/drm_dp_mst_topology.c:2237: warning: drm_dp_mst_connector_late_register: modversion changed because of changes in struct drm_dp_mst_topology_mgr, struct drm_dp_mst_port drivers/gpu/drm/display/drm_dp_mst_topology.c:2255: warning: drm_dp_mst_connector_early_unregister: modversion changed because of changes in struct drm_dp_mst_topology_mgr, struct drm_dp_mst_port drivers/gpu/drm/display/drm_dp_mst_topology.c:3198: warning: drm_dp_send_power_updown_phy: modversion changed because of changes in struct drm_dp_mst_port, struct drm_dp_mst_topology_mgr drivers/gpu/drm/display/drm_dp_mst_topology.c:3256: warning: drm_dp_send_query_stream_enc_status: modversion changed because of changes in struct drm_dp_mst_port, struct drm_dp_mst_topology_mgr drivers/gpu/drm/display/drm_dp_mst_topology.c:3334: warning: drm_dp_add_payload_part1: modversion changed because of changes in struct drm_dp_mst_topology_state, struct drm_dp_mst_port, struct drm_dp_mst_topology_mgr drivers/gpu/drm/display/drm_dp_mst_topology.c:3376: warning: drm_dp_remove_payload: modversion changed because of changes in struct drm_dp_mst_topology_state, struct drm_dp_mst_port, struct drm_dp_mst_topology_mgr drivers/gpu/drm/display/drm_dp_mst_topology.c:3414: warning: drm_dp_add_payload_part2: modversion changed because of changes in struct drm_dp_mst_port, struct drm_dp_mst_topology_mgr drivers/gpu/drm/display/drm_dp_mst_topology.c:3557: warning: drm_dp_get_vc_payload_bw: modversion changed because of changes in struct drm_dp_mst_port, struct drm_dp_mst_topology_mgr drivers/gpu/drm/display/drm_dp_mst_topology.c:3656: warning: drm_dp_mst_topology_mgr_set_mst: modversion changed because of changes in struct drm_dp_mst_port, struct drm_dp_mst_topology_mgr drivers/gpu/drm/display/drm_dp_mst_topology.c:3693: warning: drm_dp_mst_topology_mgr_suspend: modversion changed because of changes in struct drm_dp_mst_port, struct drm_dp_mst_topology_mgr drivers/gpu/drm/display/drm_dp_mst_topology.c:3772: warning: drm_dp_mst_topology_mgr_resume: modversion changed because of changes in struct drm_dp_mst_port, struct drm_dp_mst_topology_mgr drivers/gpu/drm/display/drm_dp_mst_topology.c:4081: warning: drm_dp_mst_hpd_irq: modversion changed because of changes in struct drm_dp_mst_port, struct drm_dp_mst_topology_mgr drivers/gpu/drm/display/drm_dp_mst_topology.c:4137: warning: drm_dp_mst_detect_port: modversion changed because of changes in struct drm_dp_mst_port, struct drm_dp_mst_topology_mgr drivers/gpu/drm/display/drm_dp_mst_topology.c:4167: warning: drm_dp_mst_get_edid: modversion changed because of changes in struct drm_dp_mst_port, struct drm_dp_mst_topology_mgr drivers/gpu/drm/display/drm_dp_mst_topology.c:4257: warning: drm_dp_atomic_find_time_slots: modversion changed because of changes in struct drm_dp_mst_port, struct drm_dp_mst_topology_mgr drivers/gpu/drm/display/drm_dp_mst_topology.c:4338: warning: drm_dp_atomic_release_time_slots: modversion changed because of changes in struct drm_dp_mst_port, struct drm_dp_mst_topology_mgr drivers/gpu/drm/display/drm_dp_mst_topology.c:4488: warning: drm_dp_mst_root_conn_atomic_check: modversion changed because of changes in struct drm_dp_mst_port, struct drm_dp_mst_topology_mgr drivers/gpu/drm/display/drm_dp_mst_topology.c:4509: warning: drm_dp_mst_update_slots: modversion changed because of changes in struct drm_dp_mst_port, struct drm_dp_mst_topology_mgr, struct drm_dp_mst_topology_state drivers/gpu/drm/display/drm_dp_mst_topology.c:4606: warning: drm_dp_check_act_status: modversion changed because of changes in struct drm_dp_mst_port, struct drm_dp_mst_topology_mgr drivers/gpu/drm/display/drm_dp_mst_topology.c:4825: warning: drm_dp_mst_dump_topology: modversion changed because of changes in struct drm_dp_mst_port, struct drm_dp_mst_topology_mgr drivers/gpu/drm/display/drm_dp_mst_topology.c:5223: warning: drm_dp_mst_add_affected_dsc_crtcs: modversion changed because of changes in struct drm_dp_mst_port, struct drm_dp_mst_topology_mgr drivers/gpu/drm/display/drm_dp_mst_topology.c:5278: warning: drm_dp_mst_atomic_enable_dsc: modversion changed because of changes in struct drm_dp_mst_topology_mgr, struct drm_dp_mst_port, drm_dp_mst_atomic_enable_dsc drivers/gpu/drm/display/drm_dp_mst_topology.c:5353: warning: drm_atomic_get_mst_topology_state: modversion changed because of changes in struct drm_dp_mst_port, struct drm_dp_mst_topology_mgr, struct drm_dp_mst_topology_state drivers/gpu/drm/display/drm_dp_mst_topology.c:5378: warning: drm_atomic_get_new_mst_topology_state: modversion changed because of changes in struct drm_dp_mst_port, struct drm_dp_mst_topology_mgr, struct drm_dp_mst_topology_state drivers/gpu/drm/display/drm_dp_mst_topology.c:5447: warning: drm_dp_mst_topology_mgr_init: modversion changed because of changes in struct drm_dp_mst_port, struct drm_dp_mst_topology_mgr, drm_dp_mst_topology_mgr_init drivers/gpu/drm/display/drm_dp_mst_topology.c:5476: warning: drm_dp_mst_topology_mgr_destroy: modversion changed because of changes in struct drm_dp_mst_port, struct drm_dp_mst_topology_mgr drivers/gpu/drm/display/drm_dp_mst_topology.c:5852: warning: drm_dp_mst_dsc_aux_for_port: modversion changed because of changes in struct drm_dp_mst_topology_mgr, struct drm_dp_mst_port -- 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 06 Apr '23

06 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1206843 https://bugzilla.suse.com/show_bug.cgi?id=1206843#c19 --- Comment #19 from Patrik Jakobsson <patrik.jakobsson(a)suse.com> --- (In reply to Takashi Iwai from comment #18) > Yeah, we should definitely check it (although there can be a fear of kABI > breakage...) I backported the series to users/pjakobsson/SLE15-SP5/bsc1206843 And building it at: home:patrikjakobsson:bsc1206843 Let's hope it doesn't break kabi too badly. > > Also I found 6.1.x stable gained lots of fixes for amdgpu, and we seem > missing them. I'll try to backport them, too. Great. Yes it looks like there is additional patches needed on top of that series. -- 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 06 Apr '23

06 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1206843 https://bugzilla.suse.com/show_bug.cgi?id=1206843#c18 --- Comment #18 from Takashi Iwai <tiwai(a)suse.com> --- Yeah, we should definitely check it (although there can be a fear of kABI breakage...) Also I found 6.1.x stable gained lots of fixes for amdgpu, and we seem missing them. I'll try to backport them, too. -- 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 06 Apr '23

06 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1206843 https://bugzilla.suse.com/show_bug.cgi?id=1206843#c17 Patrik Jakobsson <patrik.jakobsson(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(patrik.jakobsson@ | |suse.com) | --- Comment #17 from Patrik Jakobsson <patrik.jakobsson(a)suse.com> --- (In reply to Takashi Iwai from comment #11) > There seems still some issue with MST. > Now we received a Lenovo dock and I've tested T14s Gen 3 with the Lenovo > dock. > > Both S3 and S4 work fine as long as no dock is connected or the dock is kept > connected while suspend/resume (although we see some spurious kernel > WARNING). > > But when a dock is connected at S3/S4 and gets removed before the resume: > the machine can be resumed on the laptop screen, but the monitor on the dock > can't be enabled after re-plugging the dock. > > (Actually, the first replug doesn't detect the monitor at all. When you > replug twice, it'll probe the monitor, but the mode switching fails.) > > On 6.1.12 and 6.2.9 kernels, the situation is better, the monitor works > again after the second replug. > > Patrik, on which kernel version is the DRM code of our SP5 based? > I'm suspecting we're scratching the bug in the past upstream: > https://gitlab.freedesktop.org/drm/amd/-/issues/2171 This sounds familiar. I updated DRM to v6.0 but AMDGPU to v6.1. While doing so I had to exclude a series of DP-MST refactoring from Lyude Paul [1]. Perhaps this is a series that is needed? IIRC these patches also affected the extra DG2 patches I had to add to i915. [1] https://patchwork.freedesktop.org/series/104844/#rev5 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1210163] Kernel panic on boot with kernel 6.2.9-1
by bugzilla_noreply＠suse.com 06 Apr '23

06 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1210163 https://bugzilla.suse.com/show_bug.cgi?id=1210163#c4 Rodney Baker <rodney.baker(a)iinet.net.au> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #4 from Rodney Baker <rodney.baker(a)iinet.net.au> --- Installed kernel 6.2.8-1-default from TW history as requested, installed nvidia kernel module via dkms, re-ran dracut again and rebooted into 6.2.8-1-default with no issues. Tried again with version 6.2.9-1-default and now its working! Seems it was indeed something with initramfs that is now resolved. Thanks for the help, and sorry for the noise. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1210163] Kernel panic on boot with kernel 6.2.9-1
by bugzilla_noreply＠suse.com 06 Apr '23

06 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1210163 https://bugzilla.suse.com/show_bug.cgi?id=1210163#c3 Rodney Baker <rodney.baker(a)iinet.net.au> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(rodney.baker@iine | |t.net.au) | --- Comment #3 from Rodney Baker <rodney.baker(a)iinet.net.au> --- I ran dracut -f with both the working 6.2.6 kernel and passing --kver 6.2.9-1-default for the 6.2.9 kernel. Here is the output from both runs: dracut -f dracut: Executing: /usr/bin/dracut -f dracut: dracut module 'systemd-coredump' will not be installed, because command 'coredumpctl' could not be found! dracut: dracut module 'systemd-coredump' will not be installed, because command '/usr/lib/systemd/systemd-coredump' could not be found! dracut: dracut module 'systemd-pcrphase' will not be installed, because command '/usr/lib/systemd/systemd-pcrphase' could not be found! dracut: dracut module 'systemd-portabled' will not be installed, because command 'portablectl' could not be found! dracut: dracut module 'systemd-portabled' will not be installed, because command '/usr/lib/systemd/systemd-portabled' could not be found! dracut: dracut module 'systemd-repart' will not be installed, because command 'systemd-repart' could not be found! dracut: dracut module 'dbus-broker' will not be installed, because command 'dbus-broker' could not be found! dracut: dracut module 'rngd' will not be installed, because command 'rngd' could not be found! dracut: dracut module 'connman' will not be installed, because command 'connmand' could not be found! dracut: dracut module 'connman' will not be installed, because command 'connmanctl' could not be found! dracut: dracut module 'connman' will not be installed, because command 'connmand-wait-online' could not be found! dracut: dracut module 'btrfs' will not be installed, because command 'btrfs' could not be found! dracut: dracut module 'tpm2-tss' will not be installed, because command 'tpm2' could not be found! dracut: dracut module 'nvmf' will not be installed, because command 'nvme' could not be found! dracut: dracut module 'biosdevname' will not be installed, because command 'biosdevname' could not be found! dracut: dracut module 'memstrack' will not be installed, because command 'memstrack' could not be found! dracut: memstrack is not available dracut: If you need to use rd.memdebug>=4, please install memstrack and procps-ng dracut: dracut module 'squash' will not be installed, because command 'mksquashfs' could not be found! dracut: dracut module 'squash' will not be installed, because command 'unsquashfs' could not be found! dracut: dracut module 'systemd-coredump' will not be installed, because command 'coredumpctl' could not be found! dracut: dracut module 'systemd-coredump' will not be installed, because command '/usr/lib/systemd/systemd-coredump' could not be found! dracut: dracut module 'systemd-pcrphase' will not be installed, because command '/usr/lib/systemd/systemd-pcrphase' could not be found! dracut: dracut module 'systemd-portabled' will not be installed, because command 'portablectl' could not be found! dracut: dracut module 'systemd-portabled' will not be installed, because command '/usr/lib/systemd/systemd-portabled' could not be found! dracut: dracut module 'systemd-repart' will not be installed, because command 'systemd-repart' could not be found! dracut: dracut module 'dbus-broker' will not be installed, because command 'dbus-broker' could not be found! dracut: dracut module 'rngd' will not be installed, because command 'rngd' could not be found! dracut: dracut module 'connman' will not be installed, because command 'connmand' could not be found! dracut: dracut module 'connman' will not be installed, because command 'connmanctl' could not be found! dracut: dracut module 'connman' will not be installed, because command 'connmand-wait-online' could not be found! dracut: dracut module 'btrfs' will not be installed, because command 'btrfs' could not be found! dracut: dracut module 'tpm2-tss' will not be installed, because command 'tpm2' could not be found! dracut: dracut module 'nvmf' will not be installed, because command 'nvme' could not be found! dracut: dracut module 'memstrack' will not be installed, because command 'memstrack' could not be found! dracut: memstrack is not available dracut: If you need to use rd.memdebug>=4, please install memstrack and procps-ng dracut: dracut module 'squash' will not be installed, because command 'mksquashfs' could not be found! dracut: dracut module 'squash' will not be installed, because command 'unsquashfs' could not be found! dracut: *** Including module: systemd *** dracut: *** Including module: systemd-initrd *** dracut: *** Including module: i18n *** dracut: *** Including module: drm *** dracut: *** Including module: plymouth *** dracut: *** Including module: kernel-modules *** dracut: *** Including module: kernel-modules-extra *** dracut: *** Including module: nvdimm *** dracut: *** Including module: rootfs-block *** dracut: *** Including module: suse-xfs *** dracut: *** Including module: terminfo *** dracut: *** Including module: udev-rules *** dracut: Skipping udev rule: 40-redhat.rules dracut: Skipping udev rule: 50-firmware.rules dracut: Skipping udev rule: 50-udev.rules dracut: Skipping udev rule: 91-permissions.rules dracut: Skipping udev rule: 80-drivers-modprobe.rules dracut: Skipping udev rule: 70-persistent-net.rules dracut: *** Including module: dracut-systemd *** dracut: *** Including module: haveged *** dracut: *** Including module: ostree *** dracut: *** Including module: usrmount *** dracut: *** Including module: base *** dracut: *** Including module: fs-lib *** dracut: *** Including module: shutdown *** dracut: *** Including module: suse *** dracut: *** Including module: suse-initrd *** dracut: *** Including modules done *** dracut: *** Installing kernel module dependencies *** dracut: *** Installing kernel module dependencies done *** dracut: *** Resolving executable dependencies *** dracut: *** Resolving executable dependencies done *** dracut: *** Hardlinking files *** dracut: Mode: real dracut: Method: sha256 dracut: Files: 1107 dracut: Linked: 2 files dracut: Compared: 0 xattrs dracut: Compared: 119 files dracut: Saved: 352.16 KiB dracut: Duration: 0.006604 seconds dracut: *** Hardlinking files done *** dracut: *** Generating early-microcode cpio image *** dracut: *** Constructing GenuineIntel.bin *** dracut: *** Store current command line parameters *** dracut: Stored kernel commandline: dracut: root=UUID=93cda319-ba05-4170-a509-8f43ad15dc44 rootfstype=ext4 rootflags=rw,noatime dracut: *** Stripping files *** dracut: *** Stripping files done *** dracut: *** Creating image file '/boot/initrd-6.2.6-1-default' *** dracut: *** Creating initramfs image file '/boot/initrd-6.2.6-1-default' done *** dracut -f --kver 6.2.9-1-default dracut: Executing: /usr/bin/dracut -f --kver 6.2.9-1-default dracut: dracut module 'systemd-coredump' will not be installed, because command 'coredumpctl' could not be found! dracut: dracut module 'systemd-coredump' will not be installed, because command '/usr/lib/systemd/systemd-coredump' could not be found! dracut: dracut module 'systemd-pcrphase' will not be installed, because command '/usr/lib/systemd/systemd-pcrphase' could not be found! dracut: dracut module 'systemd-portabled' will not be installed, because command 'portablectl' could not be found! dracut: dracut module 'systemd-portabled' will not be installed, because command '/usr/lib/systemd/systemd-portabled' could not be found! dracut: dracut module 'systemd-repart' will not be installed, because command 'systemd-repart' could not be found! dracut: dracut module 'dbus-broker' will not be installed, because command 'dbus-broker' could not be found! dracut: dracut module 'rngd' will not be installed, because command 'rngd' could not be found! dracut: dracut module 'connman' will not be installed, because command 'connmand' could not be found! dracut: dracut module 'connman' will not be installed, because command 'connmanctl' could not be found! dracut: dracut module 'connman' will not be installed, because command 'connmand-wait-online' could not be found! dracut: dracut module 'btrfs' will not be installed, because command 'btrfs' could not be found! dracut: dracut module 'tpm2-tss' will not be installed, because command 'tpm2' could not be found! dracut: dracut module 'nvmf' will not be installed, because command 'nvme' could not be found! dracut: dracut module 'biosdevname' will not be installed, because command 'biosdevname' could not be found! dracut: dracut module 'memstrack' will not be installed, because command 'memstrack' could not be found! dracut: memstrack is not available dracut: If you need to use rd.memdebug>=4, please install memstrack and procps-ng dracut: dracut module 'squash' will not be installed, because command 'mksquashfs' could not be found! dracut: dracut module 'squash' will not be installed, because command 'unsquashfs' could not be found! dracut: dracut module 'systemd-coredump' will not be installed, because command 'coredumpctl' could not be found! dracut: dracut module 'systemd-coredump' will not be installed, because command '/usr/lib/systemd/systemd-coredump' could not be found! dracut: dracut module 'systemd-pcrphase' will not be installed, because command '/usr/lib/systemd/systemd-pcrphase' could not be found! dracut: dracut module 'systemd-portabled' will not be installed, because command 'portablectl' could not be found! dracut: dracut module 'systemd-portabled' will not be installed, because command '/usr/lib/systemd/systemd-portabled' could not be found! dracut: dracut module 'systemd-repart' will not be installed, because command 'systemd-repart' could not be found! dracut: dracut module 'dbus-broker' will not be installed, because command 'dbus-broker' could not be found! dracut: dracut module 'rngd' will not be installed, because command 'rngd' could not be found! dracut: dracut module 'connman' will not be installed, because command 'connmand' could not be found! dracut: dracut module 'connman' will not be installed, because command 'connmanctl' could not be found! dracut: dracut module 'connman' will not be installed, because command 'connmand-wait-online' could not be found! dracut: dracut module 'btrfs' will not be installed, because command 'btrfs' could not be found! dracut: dracut module 'tpm2-tss' will not be installed, because command 'tpm2' could not be found! dracut: dracut module 'nvmf' will not be installed, because command 'nvme' could not be found! dracut: dracut module 'memstrack' will not be installed, because command 'memstrack' could not be found! dracut: memstrack is not available dracut: If you need to use rd.memdebug>=4, please install memstrack and procps-ng dracut: dracut module 'squash' will not be installed, because command 'mksquashfs' could not be found! dracut: dracut module 'squash' will not be installed, because command 'unsquashfs' could not be found! dracut: *** Including module: systemd *** dracut: *** Including module: systemd-initrd *** dracut: *** Including module: i18n *** dracut: *** Including module: drm *** dracut: *** Including module: plymouth *** dracut: *** Including module: kernel-modules *** dracut: *** Including module: kernel-modules-extra *** dracut: *** Including module: nvdimm *** dracut: *** Including module: rootfs-block *** dracut: *** Including module: suse-xfs *** dracut: *** Including module: terminfo *** dracut: *** Including module: udev-rules *** dracut: Skipping udev rule: 40-redhat.rules dracut: Skipping udev rule: 50-firmware.rules dracut: Skipping udev rule: 50-udev.rules dracut: Skipping udev rule: 91-permissions.rules dracut: Skipping udev rule: 80-drivers-modprobe.rules dracut: Skipping udev rule: 70-persistent-net.rules dracut: *** Including module: dracut-systemd *** dracut: *** Including module: haveged *** dracut: *** Including module: ostree *** dracut: *** Including module: usrmount *** dracut: *** Including module: base *** dracut: *** Including module: fs-lib *** dracut: *** Including module: shutdown *** dracut: *** Including module: suse *** dracut: *** Including module: suse-initrd *** dracut: *** Including modules done *** dracut: *** Installing kernel module dependencies *** dracut: *** Installing kernel module dependencies done *** dracut: *** Resolving executable dependencies *** dracut: *** Resolving executable dependencies done *** dracut: *** Hardlinking files *** dracut: Mode: real dracut: Method: sha256 dracut: Files: 1108 dracut: Linked: 2 files dracut: Compared: 0 xattrs dracut: Compared: 120 files dracut: Saved: 352.16 KiB dracut: Duration: 0.006507 seconds dracut: *** Hardlinking files done *** dracut: *** Generating early-microcode cpio image *** dracut: *** Constructing GenuineIntel.bin *** dracut: *** Store current command line parameters *** dracut: Stored kernel commandline: dracut: root=UUID=93cda319-ba05-4170-a509-8f43ad15dc44 rootfstype=ext4 rootflags=rw,noatime dracut: *** Stripping files *** dracut: *** Stripping files done *** dracut: *** Creating image file '/boot/initrd-6.2.9-1-default' *** dracut: *** Creating initramfs image file '/boot/initrd-6.2.9-1-default' done *** Still get the same result when trying to boot to kernel 6.2.9. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1210131] New: Cannot install "kernel-default-devel"
by bugzilla_noreply＠suse.com 05 Apr '23

05 Apr '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1210131 Bug ID: 1210131 Summary: Cannot install "kernel-default-devel" Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: x86-64 OS: openSUSE Leap 15.5 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: nwr10cst-oslnx(a)yahoo.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Firefox/102.0 Build Identifier: ---- # zypper --terse install kernel-default-devel Loading repository data... Warning: Repository 'Update repository of openSUSE Backports' metadata expired since 2023-03-15 15:05:58 CDT. ... Problem: nothing provides 'libbpf.so.0()(64bit)' needed by the to be installed dwarves-1.22-150400.2.10.x86_64 Solution 1: do not install kernel-default-devel-5.14.21-150500.46.1.x86_64 Solution 2: break dwarves-1.22-150400.2.10.x86_64 by ignoring some of its dependencies Choose from above solutions by number or cancel [1/2/c/d/?] (c): c ---- It seems that "kernel-default-devel" wants to pull in "dwarves" but there's an incompatibility. Reproducible: Always -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1210163] Kernel panic on boot with kernel 6.2.9-1
by bugzilla_noreply＠suse.com 05 Apr '23

05 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1210163 https://bugzilla.suse.com/show_bug.cgi?id=1210163#c2 Fabian Vogt <fvogt(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fvogt(a)suse.com, | |rodney.baker(a)iinet.net.au Flags| |needinfo?(rodney.baker@iine | |t.net.au) --- Comment #2 from Fabian Vogt <fvogt(a)suse.com> --- > Kernel Panic - not syncing: VFS: Unable to mount root fs on unknown-block(8,5) This is actually about mounting the initramfs. I suspect it's simply corrupt or for some reason not loaded correctly. I suggest you run "dracut -f" when booting with the working kernel+initrd and try again. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1210163] Kernel panic on boot with kernel 6.2.9-1
by bugzilla_noreply＠suse.com 05 Apr '23

05 Apr '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1210163 http://bugzilla.opensuse.org/show_bug.cgi?id=1210163#c1 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tiwai(a)suse.com --- Comment #1 from Takashi Iwai <tiwai(a)suse.com> --- Please verify with 6.2.8 kernel found in OBS TW history repo to narrow down the range, too: http://download.opensuse.org/history/ -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1210163] Kernel panic on boot with kernel 6.2.9-1
by bugzilla_noreply＠suse.com 05 Apr '23

05 Apr '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1210163 Andreas Stieger <Andreas.Stieger(a)gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Basesystem |Kernel Assignee|screening-team-bugs(a)suse.de |kernel-bugs(a)opensuse.org -- 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 05 Apr '23

05 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1206843 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(patrik.jakobsson@ | |suse.com) -- 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 05 Apr '23

05 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1206843 https://bugzilla.suse.com/show_bug.cgi?id=1206843#c16 --- Comment #16 from Takashi Iwai <tiwai(a)suse.com> --- Created attachment 866147 --> https://bugzilla.suse.com/attachment.cgi?id=866147&action=edit dmesg from 6.1.x kernel -- 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 05 Apr '23

05 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1206843 https://bugzilla.suse.com/show_bug.cgi?id=1206843#c15 --- Comment #15 from Takashi Iwai <tiwai(a)suse.com> --- Created attachment 866146 --> https://bugzilla.suse.com/attachment.cgi?id=866146&action=edit dmesg from 6.2.x kernel -- 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 05 Apr '23

05 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1206843 https://bugzilla.suse.com/show_bug.cgi?id=1206843#c14 --- Comment #14 from Takashi Iwai <tiwai(a)suse.com> --- Created attachment 866145 --> https://bugzilla.suse.com/attachment.cgi?id=866145&action=edit SLE15-SP5 dmesg with S4 resume and kernel warnings -- 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 05 Apr '23

05 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1206843 https://bugzilla.suse.com/show_bug.cgi?id=1206843#c13 --- Comment #13 from Takashi Iwai <tiwai(a)suse.com> --- (In reply to Takashi Iwai from comment #11) > Both S3 and S4 work fine as long as no dock is connected or the dock is kept > connected while suspend/resume (although we see some spurious kernel > WARNING). The warning from thunderbolt is tracked in bug 1210165. -- 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 05 Apr '23

05 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1206843 https://bugzilla.suse.com/show_bug.cgi?id=1206843#c12 --- Comment #12 from Takashi Iwai <tiwai(a)suse.com> --- ... and more https://gitlab.freedesktop.org/drm/amd/-/issues/1926 https://gitlab.freedesktop.org/drm/amd/-/issues/2181 -- 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 05 Apr '23

05 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1206843 https://bugzilla.suse.com/show_bug.cgi?id=1206843#c11 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |patrik.jakobsson(a)suse.com --- Comment #11 from Takashi Iwai <tiwai(a)suse.com> --- There seems still some issue with MST. Now we received a Lenovo dock and I've tested T14s Gen 3 with the Lenovo dock. Both S3 and S4 work fine as long as no dock is connected or the dock is kept connected while suspend/resume (although we see some spurious kernel WARNING). But when a dock is connected at S3/S4 and gets removed before the resume: the machine can be resumed on the laptop screen, but the monitor on the dock can't be enabled after re-plugging the dock. (Actually, the first replug doesn't detect the monitor at all. When you replug twice, it'll probe the monitor, but the mode switching fails.) On 6.1.12 and 6.2.9 kernels, the situation is better, the monitor works again after the second replug. Patrik, on which kernel version is the DRM code of our SP5 based? I'm suspecting we're scratching the bug in the past upstream: https://gitlab.freedesktop.org/drm/amd/-/issues/2171 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1210146] New: New kernel-6.2.9-1.1 panics on all my systems
by bugzilla_noreply＠suse.com 05 Apr '23

05 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1210146 Bug ID: 1210146 Summary: New kernel-6.2.9-1.1 panics on all my systems 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: manfred.h(a)gmx.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 866130 --> https://bugzilla.suse.com/attachment.cgi?id=866130&action=edit Panic on my system saturn kernel-6.2.9-1.1 panics hereon all my systems when swithing the root filesystem. Common to all my systems is they are all Intel based and use an NVME boot disk. As the problem occurs this early in the boot phase, I can only attach a photo of one of my systems display; if this is not sufficient, please tell me how to capture the boot logs you need. FWIW, the kernel from Kernel:stable shows the same issue, while the same 6.2.9 kernel from Kernel:stable:Backport boots happily on Leap 15.4... Here are the details of all systems: 1. saturn (my primary work horse): # inxi -CSM System: Host: saturn Kernel: 6.2.8-2.gc9a94ac-default arch: x86_64 bits: 64 Desktop: Xfce v: 4.18.1 Distro: openSUSE Tumbleweed 20230402 Machine: Type: Desktop System: Micro-Star product: MS-7D09 v: 1.0 serial: N/A Mobo: Micro-Star model: Z590 PRO WIFI (MS-7D09) v: 1.0 serial: 07D0910_L21E595977 UEFI: American Megatrends LLC. v: 1.60 date: 05/19/2022 CPU: Info: 8-core model: 11th Gen Intel Core i9-11900 bits: 64 type: MT MCP cache: L2: 4 MiB Speed (MHz): avg: 2500 min/max: 800/5000:5200 cores: 1: 2500 2: 2500 3: 2500 4: 2500 5: 2500 6: 2500 7: 2500 8: 2500 9: 2500 10: 2500 11: 2500 12: 2500 13: 2500 14: 2500 15: 2500 16: 2500 2. melmac (the central server for all my systems): # inxi -CSM System: Host: melmac Kernel: 6.2.8-2.gc9a94ac-default arch: x86_64 bits: 64 Desktop: Xfce v: 4.18.1 Distro: openSUSE Tumbleweed 20230402 Machine: Type: Desktop System: Micro-Star product: MS-7D09 v: 1.0 serial: N/A Mobo: Micro-Star model: Z590 PRO WIFI (MS-7D09) v: 1.0 serial: 07D0910_L21E595656 UEFI: American Megatrends LLC. v: 1.60 date: 05/19/2022 CPU: Info: 8-core model: 11th Gen Intel Core i9-11900 bits: 64 type: MT MCP cache: L2: 4 MiB Speed (MHz): avg: 2181 min/max: 800/5000:5200 cores: 1: 2500 2: 2500 3: 2500 4: 801 5: 2500 6: 2500 7: 2500 8: 800 9: 2500 10: 2500 11: 2500 12: 2500 13: 2500 14: 800 15: 2500 16: 2500 3. neptun (laptop): # inxi -CSM System: Host: neptun Kernel: 6.2.8-2.gc9a94ac-default arch: x86_64 bits: 64 Desktop: Xfce v: 4.18.1 Distro: openSUSE Tumbleweed 20230402 Machine: Type: Laptop System: Dell product: Latitude 5500 v: N/A serial: FWP37Y2 Mobo: Dell model: 0M14W7 v: A00 serial: /FWP37Y2/CNCMK0097I02AC/ UEFI: Dell v: 1.18.0 date: 04/19/2022 CPU: Info: quad core model: Intel Core i5-8365U bits: 64 type: MT MCP cache: L2: 1024 KiB Speed (MHz): avg: 1800 min/max: 400/4100 cores: 1: 1900 2: 1900 3: 1900 4: 1900 5: 1900 6: 1900 7: 1100 8: 1900 4. htpc-3: # inxi -CSM System: Host: htpc-3 Kernel: 6.2.8-2.gc9a94ac-default arch: x86_64 bits: 64 Desktop: Xfce v: 4.18.1 Distro: openSUSE Tumbleweed 20230402 Machine: Type: Desktop Mobo: ASRock model: Z390 Phantom Gaming-ITX/ac serial: M80-C6012400909 UEFI: American Megatrends v: P4.40 date: 11/26/2019 CPU: Info: 6-core model: Intel Core i5-8400 bits: 64 type: MCP cache: L2: 1.5 MiB Speed (MHz): avg: 2466 min/max: 800/4000 cores: 1: 2800 2: 2800 3: 800 4: 2800 5: 2800 6: 2800 Screenshot has been taken on saturn. -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1210090] Kenrel 6.2.9 crash on boot when retbleed=stuff is enbaled
by bugzilla_noreply＠suse.com 05 Apr '23

05 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1210090 https://bugzilla.suse.com/show_bug.cgi?id=1210090#c4 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |manfred.h(a)gmx.net --- Comment #4 from Takashi Iwai <tiwai(a)suse.com> --- *** Bug 1210146 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1210133] New: [Build 20230403] openQA test fails in cve-2021-22555
by bugzilla_noreply＠suse.com 05 Apr '23

05 Apr '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1210133 Bug ID: 1210133 Summary: [Build 20230403] openQA test fails in cve-2021-22555 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 URL: https://openqa.opensuse.org/tests/3210302/modules/cve- 2021-22555/steps/8 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: guillaume.gardet(a)arm.com QA Contact: qa-bugs(a)suse.de Found By: openQA Blocker: Yes ## Observation openQA test in scenario opensuse-Tumbleweed-JeOS-for-AArch64-aarch64-jeos-ltp-cve@aarch64-HD20G fails in [cve-2021-22555](https://openqa.opensuse.org/tests/3210302/modules/cve-2021-… ## Test suite description ## Reproducible Fails since (at least) Build [20230403](https://openqa.opensuse.org/tests/3209555) ## Expected result Last good: [20230330](https://openqa.opensuse.org/tests/3203472) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=aarch64&distri=opensu… -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1210134] New: [Build 20230403] openQA test fails in setsockopt08
by bugzilla_noreply＠suse.com 05 Apr '23

05 Apr '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1210134 Bug ID: 1210134 Summary: [Build 20230403] openQA test fails in setsockopt08 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 URL: https://openqa.opensuse.org/tests/3210303/modules/sets ockopt08/steps/7 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: guillaume.gardet(a)arm.com QA Contact: qa-bugs(a)suse.de Found By: openQA Blocker: Yes ## Observation openQA test in scenario opensuse-Tumbleweed-JeOS-for-AArch64-aarch64-jeos-ltp-syscalls@aarch64-HD20G fails in [setsockopt08](https://openqa.opensuse.org/tests/3210303/modules/setsockopt0… ## Test suite description ## Reproducible Fails since (at least) Build [20230130](https://openqa.opensuse.org/tests/3084683) ## Expected result Last good: (unknown) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=aarch64&distri=opensu… -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1207554] openSUSE Tumbleweed 20230123 doesn't boot after installation on Intel RST VMD volume
by bugzilla_noreply＠suse.com 05 Apr '23

05 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1207554 https://bugzilla.suse.com/show_bug.cgi?id=1207554#c5 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|kernel-bugs(a)opensuse.org |screening-team-bugs(a)suse.de Flags|needinfo?(master.yodo@gmail | |.com) | --- Comment #5 from Takashi Iwai <tiwai(a)suse.com> --- Ah OK, it's about the bootloader setup. It was wrongly assigned to screening team. Let's try to reassign. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1207554] openSUSE Tumbleweed 20230123 doesn't boot after installation on Intel RST VMD volume
by bugzilla_noreply＠suse.com 04 Apr '23

04 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1207554 https://bugzilla.suse.com/show_bug.cgi?id=1207554#c4 --- Comment #4 from Master Yodo <master.yodo(a)gmail.com> --- You didn't pay attention to my last comment, did you? My previous message starts with "Fixed by adding additional UEFI boot entry". I fixed it and now I have dual boot linux & windows installed on Intel RST VMD RAID0 array with two SSDs which gives me blazing fast I/O performance. Just to be clear: using Intel RST VMD is worthy in my case as I configured RAID0 and doubled the read/write speed. Please _do not brake it_ with upcoming updates. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1210090] New: Kenrel 6.2.9 crash on boot when retbleed=stuff is enbaled
by bugzilla_noreply＠suse.com 04 Apr '23

04 Apr '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1210090 Bug ID: 1210090 Summary: Kenrel 6.2.9 crash on boot when retbleed=stuff is enbaled 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: alessandro.sturniolo(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 866098 --> http://bugzilla.opensuse.org/attachment.cgi?id=866098&action=edit First crash After today updates, I rebooted my system to apply new kernel 6.2.9, and it don't boot anymore. I had done a little investigation, and I found that retbleed=stuff in my kernel command line is the cause of this crashes at boot with this kernel version. With previous kernel versions I never had issues. On logs, the system, was unable to write anything, so I shot some photos with my phone (see attachments), but the messages on video, I don't know if they can be of any interest, because they are any time different and partials. The only thing that I found interesting on this messages, is the timestamps: all messages report a timestamp of about 14-15 seconds, then the system freeze. Watching a log of a normal boot, usually, at this time, the module amdgpu is initialize. Relevant system specs: - 2x AMD Opteron 6386 SE - ASUS KGPE-D16 Motherboard - 32GB DDR3 RAM Ecc - AMD Radeon RX 6600 8GB GPU -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 1210029] Can't hibernate laptop Lenovo L14 Gen 3 AMD
by bugzilla_noreply＠suse.com 04 Apr '23

04 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1210029 https://bugzilla.suse.com/show_bug.cgi?id=1210029#c6 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tiwai(a)suse.com --- Comment #6 from Takashi Iwai <tiwai(a)suse.com> --- So, with the latest SLE15-SP5 kernel I provided for mt76, and switching the BIOS sleep mode to "Linux S3 hibernation", S4 works fine now? It's interesting that this BIOS item isn't found on Thinkpad T14s Gen 3 I'm testing now... -- You are receiving this mail because: You are the assignee for the bug.

1 0

[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 1210050] New: Missing fixes / quirks for Thinkkpad
by bugzilla_noreply＠suse.com 03 Apr '23

03 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1210050 Bug ID: 1210050 Summary: Missing fixes / quirks for Thinkkpad Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: tiwai(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- There have been quite a few missing fixes and quirks in the kernel driver such as thinkpad_acpi for various Lenovo Thinkpad models. This entry is used for tracking to backport those missing fixes. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1207554] openSUSE Tumbleweed 20230123 doesn't boot after installation on Intel RST VMD volume
by bugzilla_noreply＠suse.com 03 Apr '23

03 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1207554 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |master.yodo(a)gmail.com Flags| |needinfo?(master.yodo@gmail | |.com) -- You are receiving this mail because: You are the assignee for the bug.

1 0

[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 1209436] I915 hangs on Kernel vmlinuz-5.14.21-150400.24.49
by bugzilla_noreply＠suse.com 02 Apr '23

02 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1209436 https://bugzilla.suse.com/show_bug.cgi?id=1209436#c76 --- Comment #76 from George Johnson <gjjohnson(a)fwsi.com> --- New Kernel 5.14.21-150400.24.55-default resolves the hang for me on Lenovo Thinkpad p50. -- You are receiving this mail because: You are the assignee for the bug.

1 0

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

01 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1209436 https://bugzilla.suse.com/show_bug.cgi?id=1209436#c75 --- Comment #75 from Rolf Breuning <Rolf.Breuning(a)t-online.de> --- Solved for me by the new kernel 5.14.21-150400.24.55, thanks -- You are receiving this mail because: You are the assignee for the bug.

1 0

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

01 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1209436 https://bugzilla.suse.com/show_bug.cgi?id=1209436#c74 --- Comment #74 from Volker Kuhlmann <bugz57(a)top.geek.nz> --- 5.14.21-150400.24.55-default works again and boots fine - thank you! -- You are receiving this mail because: You are the assignee for the bug.

1 0

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

01 Apr '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1202078 http://bugzilla.opensuse.org/show_bug.cgi?id=1202078#c3 --- Comment #3 from Daniel Noga <noga.dany(a)gmail.com> --- It looks much more dificult then I thought... Yesterdays update does not work anymore today on VirtualBox. On real PC with AMD graphics it works with original Leap's kernel. On real PC with Intel graphics it does not work. And I read somewhere on reddit, it does not work sometimes even on Tumbleweed... So I will just use it without autologin. Should I close the bug as too much broken to fix? -- 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 01 Apr '23

01 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1208069 https://bugzilla.suse.com/show_bug.cgi?id=1208069#c26 --- Comment #26 from Fritz Hudnut <non.space.1(a)gmail.com> --- So, today booted in Gecko MATE rolling, and this is the OS that is not reviving from suspend, tested that out again today. And it appears that I did also upgrade the kernel to 6.2 lp xxxx and that did not seem to help out with the issue. Ran a zypper and it hit a dependency on nvidia G06 xxxxx . . . which previously created problems in TW, and there I locked it out of the rotation. Possibly missed it over here in Gecko?? [CODE] uname -r 6.2.4-lp154.2.g0532a55-default [/CODE] -- 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 01 Apr '23

01 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1208069 https://bugzilla.suse.com/show_bug.cgi?id=1208069#c25 --- Comment #25 from Fritz Hudnut <non.space.1(a)gmail.com> --- Created attachment 866049 --> https://bugzilla.suse.com/attachment.cgi?id=866049&action=edit dmesg file from Gecko rolling on same machine -- 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 01 Apr '23

01 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1208069 https://bugzilla.suse.com/show_bug.cgi?id=1208069#c24 --- Comment #24 from Fritz Hudnut <non.space.1(a)gmail.com> --- Created attachment 866048 --> https://bugzilla.suse.com/attachment.cgi?id=866048&action=edit hwinfo file from Gecko rolling, same machine -- 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 01 Apr '23

01 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1200983 https://bugzilla.suse.com/show_bug.cgi?id=1200983#c23 --- Comment #23 from Michael Hirmke <opensuse(a)mike.franken.de> --- The situation even got worse after installing the latest snapshots. Now the keyboard stops working while logged into an X11 session. You are typing some text und suddenly the keyboard does either stop completely or gets extremly slow, i.e. one keypress every 10 seconds. If this happens, it doesn't help to switch to a different keyboard and/or connect the keyboard to a different port. Switching to the console with Alt-F2 works, though, and in this situation typing in a console window also works without any problem. Back to the X11 session the keyboard is still dead there. The mouse is not affected in this situation. I'm not sure if this is another incarnation of the same problem or a different one. -- 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 01 Apr '23

01 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1200983 https://bugzilla.suse.com/show_bug.cgi?id=1200983#c22 --- Comment #22 from Michael Hirmke <opensuse(a)mike.franken.de> --- Created attachment 866042 --> https://bugzilla.suse.com/attachment.cgi?id=866042&action=edit latest journal entries regarding usb The log contains all "usb" entries from the last boot. All devices are found during boot. The keyboard works in grub and in the plymouth dialog for the LUKS passphrase. All /dev/event entries are present. There are no errors or warnings in the log regarding usb. At Apr 01 12:13:32 the boot process finished and the sddm login screen was shown. At this point according to the journal still all devices were present (also checked the presence of the devices from remote), but keyboard and mouse didn't work as expected. Using a linux console the keyboard misbehaved as described in https://bugzilla.suse.com/show_bug.cgi?id=1200983#c10. Returning to sddm login, keyboard and mouse didn't work at all. At Apr 01 12:34:19 I disconnected and reconnected keyboard and mouse and both started working immediately. If you need more logging or more debugging, ... -- You are receiving this mail because: You are the assignee for the bug.

1 0

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

01 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1209436 https://bugzilla.suse.com/show_bug.cgi?id=1209436#c70 --- Comment #70 from Christian Kurtsiefer <christian.kurtsiefer(a)gmail.com> --- Thanks a lot - .55 kernel works great :) -- You are receiving this mail because: You are the assignee for the bug.

1 0

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

01 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1209436 https://bugzilla.suse.com/show_bug.cgi?id=1209436#c69 Marcus Meissner <meissner(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #69 from Marcus Meissner <meissner(a)suse.com> --- fixed finally -- You are receiving this mail because: You are the assignee for the bug.

1 0

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

01 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1209436 https://bugzilla.suse.com/show_bug.cgi?id=1209436#c68 --- Comment #68 from ernst Riepenhausen <riepe(a)muenster.de> --- on my i5-2520 the .55 kernel is starting now correctly. Thank you all for your work! -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1209980] Lenovo L14 Gen3 AMD, wifi card (Mediatek) not recognized.
by bugzilla_noreply＠suse.com 01 Apr '23

01 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1209980 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|kernel-bugs(a)opensuse.org |tiwai(a)suse.com -- You are receiving this mail because: You are the assignee for the bug.

1 0

[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