March 2023 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1208822] [Build 20230301] openQA test fails in cve-2022-0185 (fsconfig03)
by bugzilla_noreply＠suse.com 28 Mar '23

28 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1208822 https://bugzilla.suse.com/show_bug.cgi?id=1208822#c12 --- Comment #12 from WEI GAO <wegao(a)suse.com> --- (In reply to Petr Vorel from comment #11) > (In reply to WEI GAO from comment #10) > > In my local env, the case will pass with mkfs.exfat installed, BUT in jeos > > env mkfs.exfat can not be installed(caused by can not install exfatprogs). > > I'm sorry, it must be something else. The original report shows mkfs.exfat > installed via exfat-utils: > > The following package is recommended, but will not be installed due to > conflicts or dependency issues: > exfatprogs > > The following 167 NEW packages are going to be installed: > NetworkManager-dns-bind NetworkManager-dns-dnsmasq apparmor-utils attr > babeltrace bc bind bind-utils binutils cpp cpp12 ctags cyrus-sasl > cyrus-sasl-gssapi debuginfod-profile device-mapper dhcp dhcp-client > dhcp-server dnsmasq e2fsprogs ethtool evmctl exfat-utils > (note exfat-utils) > ... > > # fsconfig03; echo "### TEST cve-2022-0185 COMPLETE >>> $?." > ... > tst_supported_fs_types.c:120: TINFO: FUSE does support exfat > tst_supported_fs_types.c:55: TINFO: mkfs.exfat does exist > ... > tst_test.c:1634: TINFO: === Testing on btrfs === > tst_test.c:1093: TINFO: Formatting /dev/loop0 with btrfs opts='' extra > opts='' > fsconfig03.c:72: TPASS: kernel seems to be fine on btrfs > tst_test.c:1634: TINFO: === Testing on exfat === > tst_test.c:1093: TINFO: Formatting /dev/loop0 with exfat opts='' extra > opts='' > fsconfig03.c:38: TBROK: fsopen() failed: ENODEV (19) > > I also verified exfat-utils package locally: > rpm -qlp exfat-utils-1.4.0-1.2.x86_64.rpm > ... > /usr/sbin/mkfs.exfat > ... > => it's not a problem of mkfs.exfat dependency. > > Sometimes some kernel modules are missing, because we test with only > kernel-default-base package. But 1) we run with fuse 2) although exfat is > module (CONFIG_EXFAT_FS=m see > https://openqa.opensuse.org/tests/3172507#step/install_ltp/75), LTP > confirmed the support (thus module was loaded). > > I searched in dmesg. The usual dmesg file in openQA don't contain dmesg > output: > https://openqa.opensuse.org/tests/3172507/file/serial0.txt > > Looking into another file, which contains dmesg > https://openqa.opensuse.org/tests/3172507/file/shutdown_ltp-dmesg.txt > is without "OpenQA::run_ltp.pm: Starting ..." mark in dmesg > https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/ > 63a66f99ef7b274c94ac546d3807c89e5a9a0a9c/tests/kernel/run_ltp.pm#L306-L318 > which helps finding which dmesg part was caused by particular test (but test > is using virtio console). > > There are errors in the end, but because the latest message is btrfs, it > [ 1517.688092] operation not supported error, dev loop0, sector 98310 op > 0x9:(WRITE_ZEROES) flags 0x8000800 phys_seg 0 prio class 2 > [ 1517.688196] operation not supported error, dev loop0, sector 115212 op > 0x9:(WRITE_ZEROES) flags 0x8000800 phys_seg 0 prio class 2 > [ 1517.688300] operation not supported error, dev loop0, sector 131078 op > 0x9:(WRITE_ZEROES) flags 0x8000800 phys_seg 0 prio class 2 > [ 1517.809762] BTRFS: device fsid ea5c84b6-3547-494d-a4b5-599c5c2e7ec3 devid > 1 transid 6 /dev/loop0 scanned by mkfs.btrfs (13689) > > => It would help if you download JeOS image, start it locally with > virt-manager and watch dmesg. Or even start it with strace to see more. Download openSUSE-Tumbleweed-Minimal-VM.x86_64-1.0.0-kvm-and-xen-Snapshot20230326.qcow2 and do some check: kernel config has CONFIG_EXFAT_FS=m but you can not find exfat related modules installed so running system actually not support exfat, that's why LTP case failed on fsopen(exfat) For LTP side, should we also need some fix? Since current LTP case still think exfat is support on system but actually not. ===output from openSUSE-Tumbleweed-Minimal-VM.x86_64-1.0.0-kvm-and-xen-Snapshot20230326.qcow2=== uefi-http-vm:~ # cat /boot/config-6.2.8-1-default | grep FAT # DOS/FAT/EXFAT/NT Filesystems CONFIG_FAT_FS=m CONFIG_VFAT_FS=m CONFIG_FAT_DEFAULT_CODEPAGE=437 CONFIG_FAT_DEFAULT_IOCHARSET="iso8859-1" # CONFIG_FAT_DEFAULT_UTF8 is not set CONFIG_EXFAT_FS=m CONFIG_EXFAT_DEFAULT_IOCHARSET="utf8" # end of DOS/FAT/EXFAT/NT Filesystems uefi-http-vm:~ # uefi-http-vm:~ # uname -r 6.2.8-1-default uefi-http-vm:~ # cat /lib/modules/6.2.8-1-default/modules.builtin | grep fat uefi-http-vm:~ # modprobe exfat modprobe: FATAL: Module exfat not found in directory /lib/modules/6.2.8-1-default uefi-http-vm:~ # cat /proc/filesystems | grep fat vfat uefi-http-vm:~ # cat /proc/filesystems nodev sysfs nodev tmpfs nodev bdev nodev proc nodev cgroup nodev cgroup2 nodev cpuset nodev devtmpfs nodev debugfs nodev tracefs nodev securityfs nodev sockfs nodev bpf nodev pipefs nodev ramfs nodev hugetlbfs nodev devpts nodev autofs nodev mqueue nodev pstore nodev efivarfs btrfs nodev configfs fuseblk nodev fuse nodev fusectl vfat -- 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 27 Mar '23

27 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1209805 http://bugzilla.opensuse.org/show_bug.cgi?id=1209805#c6 Stefan Dirsch <sndirsch(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|X.Org |Kernel Assignee|gfx-bugs(a)suse.de |kernel-bugs(a)opensuse.org Summary|Possible integer underflow |Kernel regression: Possible |in input pipeline of |integer underflow in input |ThinkPad trackpoint. |pipeline of ThinkPad | |trackpoint. QA Contact|gfx-bugs(a)suse.de |qa-bugs(a)suse.de --- Comment #6 from Stefan Dirsch <sndirsch(a)suse.com> --- Thanks. That already helps a lot! Reassigning ... -- 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 27 Mar '23

27 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1209724 https://bugzilla.suse.com/show_bug.cgi?id=1209724#c10 --- Comment #10 from Sarah Kriesch <ada.lovelace(a)gmx.de> --- Thank you! I will test this patch. I did not know about such a gcc version dependency for the kernel and it is looking like that should have really happened for all architectures. I took a look into the submit request (change) by the SUSE Developers. They have removed only "CONFIG_SERIAL_FSL_LPUART_CONSOLE=y" for the x86 config. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1208822] [Build 20230301] openQA test fails in cve-2022-0185 (fsconfig03)
by bugzilla_noreply＠suse.com 27 Mar '23

27 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1208822 Petr Vorel <petr.vorel(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- QA Contact|qa-bugs(a)suse.de |wegao(a)suse.com -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1208822] [Build 20230301] openQA test fails in cve-2022-0185 (fsconfig03)
by bugzilla_noreply＠suse.com 27 Mar '23

27 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1208822 https://bugzilla.suse.com/show_bug.cgi?id=1208822#c11 --- Comment #11 from Petr Vorel <petr.vorel(a)suse.com> --- (In reply to WEI GAO from comment #10) > In my local env, the case will pass with mkfs.exfat installed, BUT in jeos > env mkfs.exfat can not be installed(caused by can not install exfatprogs). I'm sorry, it must be something else. The original report shows mkfs.exfat installed via exfat-utils: The following package is recommended, but will not be installed due to conflicts or dependency issues: exfatprogs The following 167 NEW packages are going to be installed: NetworkManager-dns-bind NetworkManager-dns-dnsmasq apparmor-utils attr babeltrace bc bind bind-utils binutils cpp cpp12 ctags cyrus-sasl cyrus-sasl-gssapi debuginfod-profile device-mapper dhcp dhcp-client dhcp-server dnsmasq e2fsprogs ethtool evmctl exfat-utils (note exfat-utils) ... # fsconfig03; echo "### TEST cve-2022-0185 COMPLETE >>> $?." ... tst_supported_fs_types.c:120: TINFO: FUSE does support exfat tst_supported_fs_types.c:55: TINFO: mkfs.exfat does exist ... tst_test.c:1634: TINFO: === Testing on btrfs === tst_test.c:1093: TINFO: Formatting /dev/loop0 with btrfs opts='' extra opts='' fsconfig03.c:72: TPASS: kernel seems to be fine on btrfs tst_test.c:1634: TINFO: === Testing on exfat === tst_test.c:1093: TINFO: Formatting /dev/loop0 with exfat opts='' extra opts='' fsconfig03.c:38: TBROK: fsopen() failed: ENODEV (19) I also verified exfat-utils package locally: rpm -qlp exfat-utils-1.4.0-1.2.x86_64.rpm ... /usr/sbin/mkfs.exfat ... => it's not a problem of mkfs.exfat dependency. Sometimes some kernel modules are missing, because we test with only kernel-default-base package. But 1) we run with fuse 2) although exfat is module (CONFIG_EXFAT_FS=m see https://openqa.opensuse.org/tests/3172507#step/install_ltp/75), LTP confirmed the support (thus module was loaded). I searched in dmesg. The usual dmesg file in openQA don't contain dmesg output: https://openqa.opensuse.org/tests/3172507/file/serial0.txt Looking into another file, which contains dmesg https://openqa.opensuse.org/tests/3172507/file/shutdown_ltp-dmesg.txt is without "OpenQA::run_ltp.pm: Starting ..." mark in dmesg https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/63a66f99ef7… which helps finding which dmesg part was caused by particular test (but test is using virtio console). There are errors in the end, but because the latest message is btrfs, it [ 1517.688092] operation not supported error, dev loop0, sector 98310 op 0x9:(WRITE_ZEROES) flags 0x8000800 phys_seg 0 prio class 2 [ 1517.688196] operation not supported error, dev loop0, sector 115212 op 0x9:(WRITE_ZEROES) flags 0x8000800 phys_seg 0 prio class 2 [ 1517.688300] operation not supported error, dev loop0, sector 131078 op 0x9:(WRITE_ZEROES) flags 0x8000800 phys_seg 0 prio class 2 [ 1517.809762] BTRFS: device fsid ea5c84b6-3547-494d-a4b5-599c5c2e7ec3 devid 1 transid 6 /dev/loop0 scanned by mkfs.btrfs (13689) => It would help if you download JeOS image, start it locally with virt-manager and watch dmesg. Or even start it with strace to see more. -- 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 27 Mar '23

27 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1209724 https://bugzilla.suse.com/show_bug.cgi?id=1209724#c9 --- Comment #9 from LTC BugProxy <bugproxy(a)us.ibm.com> --- Created attachment 865870 --> https://bugzilla.suse.com/attachment.cgi?id=865870&action=edit a patch to disable -Warray-bounds for gcc-13 same as for gcc-11 and 12 -- 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 27 Mar '23

27 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1209724 https://bugzilla.suse.com/show_bug.cgi?id=1209724#c8 --- Comment #8 from LTC BugProxy <bugproxy(a)us.ibm.com> --- ------- Comment From vasily.gorbik(a)de.ibm.com 2023-03-27 12:21 EDT------- Neither the gcc 13 nor the kernel built with it have been sufficiently tested for any use other than pure development needs. The '-Warray-bounds' warnings are explicitly disabled in the kernel for gcc 11 and 12. It is yet unclear how '-Warray-bounds' will be handled for gcc 13 because it has not been released yet. We do not know if other architectures will have to disable it or if it will only apply to s390. In other words, support for gcc 13 in the kernel has not been settled yet, and it will most likely be changed like the patch attached. The '-Warray-bounds' warning is more problematic for s390 due to the way our architecture-specific lowcore is accessed. The particular build error you encountered stands out from array-bounds warnings, but that is only because the MTK_T7XX driver is using 'ccflags-y += -Werror.' Disabling the '-Warray-bounds' warning also addresses that issue. However, I do not know the reasons for your early adoption of gcc 13. I noticed that there are already gcc 13 build-specific patches available. [ 245s] + patch -s -F0 -E -p1 --no-backup-if-mismatch -i ../patches.kernel.org/6.2.3-662-gcc-plugins-drop-std-gnu-11-to-fix-GCC-13-build.patch If urgent and if desired, you could pick up the attached patch until it is superseded by kernel changes 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 27 Mar '23

27 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1209724 https://bugzilla.suse.com/show_bug.cgi?id=1209724#c7 --- Comment #7 from Sarah Kriesch <ada.lovelace(a)gmx.de> --- If you create an openSUSE account and login into our Open Build System, you can receive this (unreleased) gcc version as a package from here: https://build.opensuse.org/package/binaries/openSUSE:Factory:zSystems/gcc13… -- 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 27 Mar '23

27 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1209724 https://bugzilla.suse.com/show_bug.cgi?id=1209724#c6 --- Comment #6 from Sarah Kriesch <ada.lovelace(a)gmx.de> --- (In reply to LTC BugProxy from comment #5) > ------- Comment From vasily.gorbik(a)de.ibm.com 2023-03-27 09:58 EDT------- > are you trying to use unreleased gcc 13 for the build? Yes. But we do not receive such error messages for the other architectures with that. -- You are receiving this mail because: You are the assignee for the bug.

1 0

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

27 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1209526 https://bugzilla.suse.com/show_bug.cgi?id=1209526#c8 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(jiivee(a)iki.fi) --- Comment #8 from Takashi Iwai <tiwai(a)suse.com> --- Another test kernel is being built for the revised fix patch in OBS home:tiwai:bsc1209526-3 repo. Please try it once after the build finishes. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1208822] [Build 20230301] openQA test fails in cve-2022-0185 (fsconfig03)
by bugzilla_noreply＠suse.com 27 Mar '23

27 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1208822 https://bugzilla.suse.com/show_bug.cgi?id=1208822#c10 --- Comment #10 from WEI GAO <wegao(a)suse.com> --- (In reply to Petr Vorel from comment #9) > (In reply to WEI GAO from comment #8) > > After check openqa > > log(https://openqa.opensuse.org/tests/3172507/ > > logfile?filename=serial_terminal.txt) i found a following conflict which > > maybe related with > > exfat. > > > > The following package is recommended, but will not be installed due to > > conflicts or dependency issues: > > exfatprogs > > exfat-utils is installed instead, maybe it would work with exfatprogs. > > But because the same issue is on Tumbleweed DVD, it will be likely something > else. > https://openqa.opensuse.org/tests/3194220/file/serial_terminal.txt In my local env, the case will pass with mkfs.exfat installed, BUT in jeos env mkfs.exfat can not be installed(caused by can not install exfatprogs). In LTP logic (function has_kernel_support) if not find mkfs.exfat, it will check FUSE support or not and continue it, then error happen, need further investigation. ===OK log on my local env=== uname -r 5.14.21-150400.24.41-default localhost:/home/ltp/testcases/kernel/syscalls/fsconfig # rpm -qf /usr/sbin/mkfs.exfat exfatprogs-1.0.4-3.3.1.x86_64 localhost:/home/ltp/testcases/kernel/syscalls/fsconfig # ./fsconfig03 ... tst_test.c:1094: TINFO: Formatting /dev/loop1 with exfat opts='' extra opts='' fsconfig03.c:73: TPASS: kernel seems to be fine on exfat ... -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1208822] [Build 20230301] openQA test fails in cve-2022-0185 (fsconfig03)
by bugzilla_noreply＠suse.com 27 Mar '23

27 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1208822 https://bugzilla.suse.com/show_bug.cgi?id=1208822#c9 Petr Vorel <petr.vorel(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Group| |novellonly --- Comment #9 from Petr Vorel <petr.vorel(a)suse.com> --- (In reply to WEI GAO from comment #8) > After check openqa > log(https://openqa.opensuse.org/tests/3172507/ > logfile?filename=serial_terminal.txt) i found a following conflict which > maybe related with > exfat. > > The following package is recommended, but will not be installed due to > conflicts or dependency issues: > exfatprogs exfat-utils is installed instead, maybe it would work with exfatprogs. But because the same issue is on Tumbleweed DVD, it will be likely something else. https://openqa.opensuse.org/tests/3194220/file/serial_terminal.txt -- 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 27 Mar '23

27 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1209724 https://bugzilla.suse.com/show_bug.cgi?id=1209724#c5 --- Comment #5 from LTC BugProxy <bugproxy(a)us.ibm.com> --- ------- Comment From vasily.gorbik(a)de.ibm.com 2023-03-27 09:58 EDT------- Looking at "last built kernel available under: https://download.opensuse.org/ports/zsystems/tumbleweed/repo/oss/s390x/kern…" It seems 6.2.6 has been built with gcc 12.2.1. Looking at the failed build logs for 6.2.8: [ 62s] [160/168] cumulate gcc13-13.0.1+git6669-1.1 [ 62s] [161/168] cumulate gcc13-PIE-13.0.1+git6669-1.1 are you trying to use unreleased gcc 13 for the build? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1208822] [Build 20230301] openQA test fails in cve-2022-0185 (fsconfig03)
by bugzilla_noreply＠suse.com 27 Mar '23

27 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1208822 https://bugzilla.suse.com/show_bug.cgi?id=1208822#c8 --- Comment #8 from WEI GAO <wegao(a)suse.com> --- After check openqa log(https://openqa.opensuse.org/tests/3172507/logfile?filename=serial_termi… i found a following conflict which maybe related with exfat. The following package is recommended, but will not be installed due to conflicts or dependency issues: exfatprogs -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1208938] New: Boot fails with kernel 6.2.1-1-default
by bugzilla_noreply＠suse.com 27 Mar '23

27 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1208938 Bug ID: 1208938 Summary: Boot fails with kernel 6.2.1-1-default Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: martti.laaksonen(a)sci.fi QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 865281 --> http://bugzilla.opensuse.org/attachment.cgi?id=865281&action=edit kernel-6.2.1-1-default netconsole amdgpu crash After updating my TW system this morning (zypper ref; zypper dup) the system won't boot anymore with the latest kernel 6.2.1-1-default. The boot seems to start normally then the display goes to power save mode and the system seems to hang altogether. I wasn't even able to ssh to the system which to me suggests that it was really hung. Booting with the previous kernel 6.1.2-1-default works just fine. I managed to setup netconsole and with that I was able to see that it crashed when initializing(?) amdgpu. netconsole log is attached. -- You are receiving this mail because: You are the assignee for the bug.

1 10

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

27 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1209724 LTC BugProxy <bugproxy(a)us.ibm.com> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugzilla.linux.ibm. | |com/show_bug.cgi?id=202082 -- 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 26 Mar '23

26 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1200983 https://bugzilla.suse.com/show_bug.cgi?id=1200983#c15 --- Comment #15 from Michael Hirmke <opensuse(a)mike.franken.de> --- Still exists with kernel 6.2.8-1. -- You are receiving this mail because: You are the assignee for the bug.

1 0

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

25 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1209727 Bug ID: 1209727 Summary: [Build 20230324] kernel crash when loading vboxdrv Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/3190867/modules/add_ box_virtualbox/steps/11 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: openQA Blocker: Yes ## Observation [ 98.595418][ T7512] vboxdrv: loading out-of-tree module taints kernel. [ 98.608875][ T7512] vboxdrv: fAsync=0 offMin=0x7c4 offMax=0x6644 [ 98.709791][ T7512] BUG: kernel NULL pointer dereference, address: 0000000000000004 [ 98.710446][ T7512] #PF: supervisor read access in kernel mode [ 98.710927][ T7512] #PF: error_code(0x0000) - not-present page [ 98.711399][ T7512] PGD 0 P4D 0 [ 98.711730][ T7512] Oops: 0000 [#1] PREEMPT SMP NOPTI [ 98.712159][ T7512] CPU: 2 PID: 7512 Comm: modprobe Tainted: G O 6.2.8-1-default #1 openSUSE Tumbleweed 3fa4abf6558707e35b8fd19fc1aa28b27d42fac2 [ 98.713279][ T7512] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.15.0-0-g2dd4b9b-rebuilt.opensuse.org 04/01/2014 [ 98.714356][ T7512] RIP: 0010:VBoxHost_RTSpinlockAcquire+0xa/0x40 [vboxdrv] [ 98.714950][ T7512] Code: ca 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 0f 1f 44 00 00 55 48 89 e5 53 <f6> 47 04 02 48 89 fb 48 8d 7f 10 74 13 e8 a4 ce bf ca 48 89 43 08 [ 98.717019][ T7512] RSP: 0018:ffffb65e00eb7c98 EFLAGS: 00010246 [ 98.717791][ T7512] RAX: 0000000000000000 RBX: ffffffffc0ead3a0 RCX: 000000000000f5f5 [ 98.718810][ T7512] RDX: ffffb65e00eb7c28 RSI: 0000000000000001 RDI: 0000000000000000 [ 98.719727][ T7512] RBP: ffffb65e00eb7ca0 R08: 0000000000000002 R09: ffff9894f72a0000 [ 98.720629][ T7512] R10: 0000000000002e80 R11: 0000000000000000 R12: 0000000000000001 [ 98.721342][ T7512] R13: 0000000000000000 R14: ffff9894f72a0000 R15: ffff9894f72a3080 [ 98.722053][ T7512] FS: 00007fbc445d4740(0000) GS:ffff9895fbd00000(0000) knlGS:0000000000000000 [ 98.722875][ T7512] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 98.723561][ T7512] CR2: 0000000000000004 CR3: 0000000107988006 CR4: 0000000000770ee0 [ 98.724305][ T7512] PKRU: 55555554 [ 98.724876][ T7512] Call Trace: [ 98.725325][ T7512] <TASK> [ 98.725712][ T7512] supdrvTscDeltaThreadStartMeasurement+0x1e/0x70 [vboxdrv 766e4c1d1431265a84068a584196871589742fde] [ 98.726541][ T7512] supdrvGipCreate+0x597/0xcc0 [vboxdrv 766e4c1d1431265a84068a584196871589742fde] [ 98.727289][ T7512] supdrvInitDevExt+0x145/0x320 [vboxdrv 766e4c1d1431265a84068a584196871589742fde] [ 98.728030][ T7512] VBoxDrvLinuxInit+0x87/0xff0 [vboxdrv 766e4c1d1431265a84068a584196871589742fde] [ 98.728781][ T7512] ? __pfx_init_module+0x10/0x10 [vboxdrv 766e4c1d1431265a84068a584196871589742fde] [ 98.729532][ T7512] do_one_initcall+0x46/0x220 [ 98.730047][ T7512] ? kmalloc_trace+0x26/0x90 [ 98.730564][ T7512] do_init_module+0x4a/0x210 [ 98.731370][ T7512] __do_sys_finit_module+0xac/0x120 [ 98.731915][ T7512] do_syscall_64+0x5b/0x80 [ 98.732404][ T7512] ? exc_page_fault+0x66/0x150 [ 98.732898][ T7512] entry_SYSCALL_64_after_hwframe+0x72/0xdc [ 98.733454][ T7512] RIP: 0033:0x7fbc43f11f5d [ 98.733925][ T7512] Code: 5d c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 7b 7e 0d 00 f7 d8 64 89 01 48 [ 98.735464][ T7512] RSP: 002b:00007fff553578b8 EFLAGS: 00000246 ORIG_RAX: 0000000000000139 [ 98.736159][ T7512] RAX: ffffffffffffffda RBX: 0000560ae6debe50 RCX: 00007fbc43f11f5d [ 98.736820][ T7512] RDX: 0000000000000000 RSI: 0000560ae6560c3a RDI: 0000000000000003 [ 98.737475][ T7512] RBP: 0000560ae6560c3a R08: 0000000000000000 R09: 0000560ae6debed0 [ 98.738132][ T7512] R10: 0000560ae6dec180 R11: 0000000000000246 R12: 0000000000040000 [ 98.738788][ T7512] R13: 0000000000000000 R14: 0000560ae6deab20 R15: 0000000000000000 [ 98.739447][ T7512] </TASK> [ 98.739838][ T7512] Modules linked in: vboxdrv(O+) algif_hash af_alg ebtable_filter ebtable_nat ebtable_broute ebtables ip6table_filter ip6table_nat ip6table_mangle ip6table_raw ip6table_security ip6_tables iptable_filter iptable_nat iptable_mangle iptable_raw iptable_security bpfilter af_packet nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_ct rfkill nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nf_tables nfnetlink qrtr intel_rapl_msr intel_rapl_common snd_hda_codec_generic ledtrig_audio snd_hda_intel snd_intel_dspcfg ppdev snd_intel_sdw_acpi kvm_amd ccp snd_hda_codec snd_hda_core snd_hwdep snd_pcm virtio_net snd_timer net_failover hid_generic kvm snd parport_pc tiny_power_button usbhid irqbypass pcspkr failover parport soundcore button i2c_piix4 joydev fuse efi_pstore configfs dmi_sysfs ip_tables x_tables crct10dif_pclmul crc32_pclmul polyval_clmulni polyval_generic gf128mul ghash_clmulni_intel [ 98.739880][ T7512] sha512_ssse3 xhci_pci sr_mod xhci_pci_renesas cdrom xhci_hcd aesni_intel ata_generic crypto_simd virtio_blk cryptd usbcore bochs drm_vram_helper drm_ttm_helper virtio_scsi ttm ata_piix floppy serio_raw btrfs blake2b_generic xor raid6_pq libcrc32c crc32c_intel sg dm_multipath dm_mod scsi_dh_rdac scsi_dh_emc scsi_dh_alua qemu_fw_cfg virtio_rng [ 98.748869][ T7512] CR2: 0000000000000004 [ 98.749362][ T7512] ---[ end trace 0000000000000000 ]--- [ 98.749918][ T7512] RIP: 0010:VBoxHost_RTSpinlockAcquire+0xa/0x40 [vboxdrv] [ 98.750584][ T7512] Code: ca 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 0f 1f 44 00 00 55 48 89 e5 53 <f6> 47 04 02 48 89 fb 48 8d 7f 10 74 13 e8 a4 ce bf ca 48 89 43 08 [ 98.752169][ T7512] RSP: 0018:ffffb65e00eb7c98 EFLAGS: 00010246 [ 98.752756][ T7512] RAX: 0000000000000000 RBX: ffffffffc0ead3a0 RCX: 000000000000f5f5 [ 98.753438][ T7512] RDX: ffffb65e00eb7c28 RSI: 0000000000000001 RDI: 0000000000000000 [ 98.754133][ T7512] RBP: ffffb65e00eb7ca0 R08: 0000000000000002 R09: ffff9894f72a0000 [ 98.754817][ T7512] R10: 0000000000002e80 R11: 0000000000000000 R12: 0000000000000001 [ 98.755492][ T7512] R13: 0000000000000000 R14: ffff9894f72a0000 R15: ffff9894f72a3080 [ 98.756175][ T7512] FS: 00007fbc445d4740(0000) GS:ffff9895fbd00000(0000) knlGS:0000000000000000 [ 98.756912][ T7512] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 98.757513][ T7512] CR2: 0000000000000004 CR3: 0000000107988006 CR4: 0000000000770ee0 [ 98.758193][ T7512] PKRU: 55555554 [ 98.758638][ T7512] note: modprobe[7512] exited with irqs disabled openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-extra_tests_vagrant@64bit fails in [add_box_virtualbox](https://openqa.opensuse.org/tests/3190867/modules/add_b… ## Test suite description Maintainer: dancermak. Test vagrant, vagrant plugins and the vagrant boxes ## Reproducible Fails since (at least) Build [20230324](https://openqa.opensuse.org/tests/3190231) ## Expected result Last good: [20230322](https://openqa.opensuse.org/tests/3189046) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=opensus… -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1209680] ata1.00: exception Emask 0x40 SAct 0x3f0 SErr 0xd0800 action 0x6 frozen
by bugzilla_noreply＠suse.com 25 Mar '23

25 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1209680 http://bugzilla.opensuse.org/show_bug.cgi?id=1209680#c8 --- Comment #8 from Takashi Iwai <tiwai(a)suse.com> --- (In reply to John Shand from comment #7) > (In reply to Takashi Iwai from comment #5) > > Possibly a problem of SSD with TRIM. Other Crucial SSD models have the > > workarounds, and this one might need the similar fix. > > > > Try to boot with a boot option > > libata.force=noncqtrim > > i haven't made that change as of yet as it hasn't happened again so far If it matters, that may happen after TRIM operation. You can try to trigger it manually. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1209680] ata1.00: exception Emask 0x40 SAct 0x3f0 SErr 0xd0800 action 0x6 frozen
by bugzilla_noreply＠suse.com 25 Mar '23

25 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1209680 http://bugzilla.opensuse.org/show_bug.cgi?id=1209680#c7 --- Comment #7 from John Shand <jshand2013(a)gmail.com> --- (In reply to Takashi Iwai from comment #5) > Possibly a problem of SSD with TRIM. Other Crucial SSD models have the > workarounds, and this one might need the similar fix. > > Try to boot with a boot option > libata.force=noncqtrim i haven't made that change as of yet as it hasn't happened again so far -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1209680] ata1.00: exception Emask 0x40 SAct 0x3f0 SErr 0xd0800 action 0x6 frozen
by bugzilla_noreply＠suse.com 25 Mar '23

25 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1209680 http://bugzilla.opensuse.org/show_bug.cgi?id=1209680#c6 --- Comment #6 from John Shand <jshand2013(a)gmail.com> --- this issue only happened when all packages were upgraded. i think this to be a once off issue. i shall keep an eye on it. however, haven't seen the issue since then -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1209702] New: glusterd fails to start: fatal glibc error
by bugzilla_noreply＠suse.com 24 Mar '23

24 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1209702 Bug ID: 1209702 Summary: glusterd fails to start: fatal glibc error 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: M.Traxler(a)gsi.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- When I start the freshly installed glusterfs with systemctl start glusterd I get the following message in the systemd-journal: Mar 24 15:54:49 l10 systemd[1]: Starting GlusterFS, a clustered file-system server... Mar 24 15:54:49 l10 glusterd[19648]: Fatal glibc error: malloc.c:2593 (sysmalloc): assertion failed: (old_top == initial_top (av) && old_size == 0) || ((unsigned long) (old_size) >= MINSIZE && prev_inuse (old_top) && ((unsigned long) old_end & (pagesize - 1)) == 0) Mar 24 15:54:49 l10 systemd[1]: Started Process Core Dump (PID 19649/UID 0). Mar 24 15:54:49 l10 systemd-coredump[19650]: [ -- You are receiving this mail because: You are the assignee for the bug.

1 5

[Bug 1209006] New: Document how to secureboot-sign manually built kernel modules on TW kernel >= 6.2.1
by bugzilla_noreply＠suse.com 24 Mar '23

24 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1209006 Bug ID: 1209006 Summary: Document how to secureboot-sign manually built kernel modules on TW kernel >= 6.2.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: sndirsch(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Now that we added lockdown patches to our kernel with version 6.2.1 breaking nvidia driver packages it would be time to let our users/developers know how to secureboot-sign manually-built kernel modules (vmware, nvidia, etc.). You can see that there is a need in this mail thread on opensuse-factory ML. :-( https://lists.opensuse.org/archives/list/factory@lists.opensuse.org/thread/… Documentation for vmware, that doesn't work for TW 6.2.1 kernels https://kb.vmware.com/s/article/2146460 (well, there is missing a -addext "extendedKeyUsage=codeSigning needed already for Leap kernels; so this seems to be outdated anyway) Things that are working for Leap >= 15.2 are: flavor=default privkey=$(mktemp /tmp/MOK.priv.XXXXXX) pubkeydir=/var/lib/nvidia-pubkeys pubkey=$pubkeydir/MOK-nvidia-driver-G06-525.89.02-7.1-$flavor.der # make sure creation of pubkey doesn't fail later test -d pubkeydir || mkdir -p $pubkeydir # Create a key pair (private key, public key) openssl req -new -x509 -newkey rsa:2048 \ -keyout $privkey \ -outform DER -out $pubkey -days 1000 \ -subj "/CN=Local build for nvidia-driver-G06 525.89.02 on $(date+"%Y-%m-%d")/" \ -addext "extendedKeyUsage=codeSigning" \ -nodes # Install the public key to MOK mokutil --import $pubkey --root-pw kver=6.2.1-1-default # Sign the Nvidia modules (weak-updates appears to be broken) for i in /lib/modules/$kver/updates/nvidia*.ko; do /lib/modules/$kver/build/scripts/sign-file sha256 $privkey $pubkey $i done # cleanup: private key no longer needed rm -f $privkey With the TW kernel this results in # dmesg -c > /dev/null # modprobe nvidia modprobe: ERROR: could not insert 'nvidia': Operation not permitted # dmesg [ 58.707747] lockdown_is_locked_down: 2 callbacks suppressed [ 58.707751] Lockdown: modprobe: unsigned module loading is restricted; see man kernel_lockdown.7 # modinfo nvidia filename: /lib/modules/6.2.1-1-default/updates/nvidia.ko firmware: nvidia/525.89.02/gsp_tu10x.bin firmware: nvidia/525.89.02/gsp_ad10x.bin alias: char-major-195-* version: 525.89.02 [...] Takashi asked me to look into our kernel-install-tools. I had a quick look, but I need to say I don't understand them. 1) It works with one file /path/to/certificate for both private and public key? How is this possible? We want to remove private key right after signing but keep public key on the system. 2) There is only a tool (sbtool-sign-kernel) to sign the kernel image, not the kernel modules? Or how is this supposed to work? 3) Signing of modules in KMPs is apparently not being done by the tools in this package, so maybe these are not the right tools at all? -- You are receiving this mail because: You are the assignee for the bug.

1 9

[Bug 1209702] glusterd fails to start: fatal glibc error
by bugzilla_noreply＠suse.com 24 Mar '23

24 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1209702 https://bugzilla.suse.com/show_bug.cgi?id=1209702#c3 --- Comment #3 from Marcus Meissner <meissner(a)suse.com> --- looks like a memory corruption, heap overflow or similar. try to use valgrind or something -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1209680] ata1.00: exception Emask 0x40 SAct 0x3f0 SErr 0xd0800 action 0x6 frozen
by bugzilla_noreply＠suse.com 24 Mar '23

24 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1209680 https://bugzilla.suse.com/show_bug.cgi?id=1209680#c5 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tiwai(a)suse.com --- Comment #5 from Takashi Iwai <tiwai(a)suse.com> --- Possibly a problem of SSD with TRIM. Other Crucial SSD models have the workarounds, and this one might need the similar fix. Try to boot with a boot option libata.force=noncqtrim -- You are receiving this mail because: You are the assignee for the bug.

1 0

[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 24 Mar '23

24 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1209620 https://bugzilla.suse.com/show_bug.cgi?id=1209620#c1 Paulo Alcantara <palcantara(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |samba-maintainers(a)SuSE.de --- Comment #1 from Paulo Alcantara <palcantara(a)suse.com> --- Hi Rick, Thanks for the report. Could provide verbose logs and network traces from both working (6.1.8-1) and non-working (6.2.6-1) kernels as follows # umount any existing shares modprobe dns_resolver modprobe cifs dmesg --clear echo 'module cifs +p' > /sys/kernel/debug/dynamic_debug/control echo 'file fs/cifs/* +p' > /sys/kernel/debug/dynamic_debug/control echo 1 > /proc/fs/cifs/cifsFYI echo 1 > /sys/module/dns_resolver/parameters/debug tcpdump -s 0 -w trace.pcap port 445 & pid=$! sleep 3 mount -t cifs //169.254.8.252/NAS ~/Mount/NAS -o ... sleep 3 kill $pid dmesg > trace.log echo '----------' >> trace.log cat /proc/fs/cifs/dfscache >> trace.log and then send trace.log and trace.pcap files for both kernels. Please, also share - full mount options - server type, version and configuration -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1208239] Driver for Intel Alder Lake-UP3 GT2 [UHD Graphics] -- HDMI not properly recognized
by bugzilla_noreply＠suse.com 24 Mar '23

24 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1208239 http://bugzilla.opensuse.org/show_bug.cgi?id=1208239#c18 Patrik Jakobsson <patrik.jakobsson(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #18 from Patrik Jakobsson <patrik.jakobsson(a)suse.com> --- Hi Luca, Again, sorry for they late reply. From your logs I can see that the Intel driver is properly loaded. I'm not sure if the benchmarking numbers are sane or not since I don't have a similar system to compare with. intel-gpu-top shows an idle GPU but perhaps that is because you didn't have a GPU load running when capturing the output. Since this bug is about HDMI not being properly recognized I think you should file a separate bug for the performance issues. The reason HDMI was not properly recognized at first was that 15.4 didn't support ADL-P. And the problem with 15.5 was a bad cable. I think we can close this bug. Please reopen if you feel differently. -- 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 24 Mar '23

24 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1206843 https://bugzilla.suse.com/show_bug.cgi?id=1206843#c7 Christian Goll <cgoll(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(cgoll(a)suse.com) | --- Comment #7 from Christian Goll <cgoll(a)suse.com> --- Suspending and resuming works now fine, with and without attached docking station. Problems just show up, if the docking station is removed, when the laptop is suspended. Wakeup works, but I can't then suspend it. I used the 5.14.21-150500.95.g8e77d94-default -- 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 24 Mar '23

24 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1206843 https://bugzilla.suse.com/show_bug.cgi?id=1206843#c6 --- Comment #6 from Takashi Iwai <tiwai(a)suse.com> --- Any chance to test the latest SLE15-SP5 kernel? If the problem persists with it, we'll have to take a deeper look. In general, it's known that AMD platforms had some unresolvable issues on SLE15-SP4/Leap-15.4, while SP5/15.5 can work better. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1209680] ata1.00: exception Emask 0x40 SAct 0x3f0 SErr 0xd0800 action 0x6 frozen
by bugzilla_noreply＠suse.com 24 Mar '23

24 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1209680 Andreas Stieger <Andreas.Stieger(a)gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Other |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 24 Mar '23

24 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1206843 https://bugzilla.suse.com/show_bug.cgi?id=1206843#c5 --- Comment #5 from Christian Goll <cgoll(a)suse.com> --- Still not perfect, especially if suspended when connected to a do a docking station, disconnect and then wake up. But this may be a fringe case. So in overall, much better. -- 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 24 Mar '23

24 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1206843 https://bugzilla.suse.com/show_bug.cgi?id=1206843#c4 --- Comment #4 from Takashi Iwai <tiwai(a)suse.com> --- Any update on this? -- You are receiving this mail because: You are the assignee for the bug.

1 0

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

23 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1209499 Stefan Dirsch <sndirsch(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P3 - Medium |P5 - None Status|IN_PROGRESS |NEW -- You are receiving this mail because: You are the assignee for the bug.

1 0

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

23 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1209499 http://bugzilla.opensuse.org/show_bug.cgi?id=1209499#c11 Stefan Dirsch <sndirsch(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium Status|NEW |IN_PROGRESS --- Comment #11 from Stefan Dirsch <sndirsch(a)suse.com> --- Thanks for updating the ticket, Adrian. @Felix Not sure where is the context for your comment#9 here. Did you post to the wrong ticket? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1207728] New: qgroup rescan paused every startup or reboot
by bugzilla_noreply＠suse.com 23 Mar '23

23 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1207728 Bug ID: 1207728 Summary: qgroup rescan paused every startup or reboot 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: jshand2013(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- after the release of kernel 6.1.8, upon each startup and reboot i get a message: btrfs info : qgroup rescan paused. to get passed this point i have to run sudo btrfs quota rescan / each time to complete the rescan process so it gets to be BTRFS info (device sda2): qgroup scan completed (inconsistency flag cleared) -- You are receiving this mail because: You are the assignee for the bug.

1 16

[Bug 1169099] [Build 20200405][aarch64] crash: cannot determine VA_BITS_ACTUAL: please use /proc/kcore
by bugzilla_noreply＠suse.com 22 Mar '23

22 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1169099 https://bugzilla.suse.com/show_bug.cgi?id=1169099#c42 --- Comment #42 from Maintenance Automation <maint-coord+maintenance-robot(a)suse.de> --- SUSE-RU-2023:0874-1: An update that has five recommended fixes can now be installed. Category: recommended (moderate) Bug References: 1169099, 1183965, 1185209, 1187634, 1206328 Sources used: openSUSE Leap 15.4 (src): crash-7.2.9-150200.18.17.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 on the CC list for the bug. You are the assignee for the bug.

1 0

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

22 Mar '23

1 0

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

22 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1209526 https://bugzilla.suse.com/show_bug.cgi?id=1209526#c1 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jiivee(a)iki.fi, | |tiwai(a)suse.com Flags| |needinfo?(jiivee(a)iki.fi) --- Comment #1 from Takashi Iwai <tiwai(a)suse.com> --- Please check whether the problem persists with 6.3-rc kernel, e.g. in OBS Kernel:HEAD repo. If yes, we should report it to the upstream. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1209522] New: i915 pipe state doesn't match! WARNING: CPU: 1 PID: 4367 at drivers/gpu/drm/i915/display/intel_modeset_verify.c:219 intel_modeset_verify_crtc+0x3c5/0x3f0 [i915]
by bugzilla_noreply＠suse.com 22 Mar '23

22 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1209522 Bug ID: 1209522 Summary: i915 pipe state doesn't match! WARNING: CPU: 1 PID: 4367 at drivers/gpu/drm/i915/display/intel_modeset_verify.c:21 9 intel_modeset_verify_crtc+0x3c5/0x3f0 [i915] 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: mpdesouza(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hi! it happens from time to time, but now I finally was able to configure journald to catch it. It usually happens on high load. I don't have a reproducer and either a step by step about how to trigger this problem. I'm currently using a Dell Docking station, using two additional monitors. Please let me know if you need more info! Mar 20 11:53:20 daedalus kernel: i915 0000:00:02.0: [drm] *ERROR* [CRTC:98:pipe A] mismatch in infoframes.enable (expected 0x0000000> Mar 20 11:53:20 daedalus kernel: i915 0000:00:02.0: [drm] *ERROR* mismatch in vsc dp sdp Mar 20 11:53:20 daedalus kernel: i915 0000:00:02.0: [drm] *ERROR* expected: Mar 20 11:53:20 daedalus kernel: i915 0000:00:02.0: DP SDP: VSC, revision 0, length 0 Mar 20 11:53:20 daedalus kernel: i915 0000:00:02.0: pixelformat: RGB Mar 20 11:53:20 daedalus kernel: i915 0000:00:02.0: colorimetry: sRGB Mar 20 11:53:20 daedalus kernel: i915 0000:00:02.0: bpc: 0 Mar 20 11:53:20 daedalus kernel: i915 0000:00:02.0: dynamic range: VESA range Mar 20 11:53:20 daedalus kernel: i915 0000:00:02.0: content type: Not defined Mar 20 11:53:20 daedalus kernel: i915 0000:00:02.0: [drm] *ERROR* found: Mar 20 11:53:20 daedalus kernel: i915 0000:00:02.0: DP SDP: VSC, revision 2, length 8 Mar 20 11:53:20 daedalus kernel: i915 0000:00:02.0: pixelformat: RGB Mar 20 11:53:20 daedalus kernel: i915 0000:00:02.0: colorimetry: sRGB Mar 20 11:53:20 daedalus kernel: i915 0000:00:02.0: bpc: 0 Mar 20 11:53:20 daedalus kernel: i915 0000:00:02.0: dynamic range: VESA range Mar 20 11:53:20 daedalus kernel: i915 0000:00:02.0: content type: Not defined Mar 20 11:53:20 daedalus kernel: ------------[ cut here ]------------ Mar 20 11:53:20 daedalus kernel: pipe state doesn't match! Mar 20 11:53:20 daedalus kernel: WARNING: CPU: 1 PID: 4367 at drivers/gpu/drm/i915/display/intel_modeset_verify.c:219 intel_modeset_> Mar 20 11:53:20 daedalus kernel: Modules linked in: usbhid ccm uinput rfcomm snd_seq_dummy snd_hrtimer snd_seq snd_seq_device af_pac> Mar 20 11:53:20 daedalus kernel: iTCO_vendor_support processor_thermal_device snd_pcm processor_thermal_rfim processor_thermal_mbox> Mar 20 11:53:20 daedalus kernel: ghash_clmulni_intel rc_core video sha512_ssse3 rtsx_pci_sdmmc xhci_pci xhci_pci_renesas mmc_core x> Mar 20 11:53:20 daedalus kernel: CPU: 1 PID: 4367 Comm: gnome-shell Not tainted 6.2.6-1-default #1 openSUSE Tumbleweed 7d732c069aa49> Mar 20 11:53:20 daedalus kernel: Hardware name: Dell Inc. Latitude 5320/074GF2, BIOS 1.24.3 10/27/2022 Mar 20 11:53:20 daedalus kernel: RIP: 0010:intel_modeset_verify_crtc+0x3c5/0x3f0 [i915] Mar 20 11:53:20 daedalus kernel: Code: 4c 8b 04 24 e9 f9 fd ff ff 48 c7 c7 d0 fb 12 c1 e8 30 32 08 f2 0f 0b 4c 8b 04 24 0f b6 44 24 > Mar 20 11:53:20 daedalus kernel: RSP: 0018:ffff9c92c0b27b10 EFLAGS: 00010286 Mar 20 11:53:20 daedalus kernel: RAX: 0000000000000000 RBX: ffff88d1194602a8 RCX: 0000000000000027 Mar 20 11:53:20 daedalus kernel: RDX: ffff88d3bf6624c8 RSI: 0000000000000001 RDI: ffff88d3bf6624c0 Mar 20 11:53:20 daedalus kernel: RBP: ffff88d0d2efc000 R08: 0000000000000000 R09: ffff9c92c0b279b8 Mar 20 11:53:20 daedalus kernel: R10: 0000000000000003 R11: ffff88d3cf742b28 R12: ffff88d044966000 Mar 20 11:53:20 daedalus kernel: R13: ffff88d119410000 R14: ffff88d119460000 R15: ffff88d1194602b0 Mar 20 11:53:20 daedalus kernel: FS: 00007ff58c8145c0(0000) GS:ffff88d3bf640000(0000) knlGS:0000000000000000 Mar 20 11:53:20 daedalus kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Mar 20 11:53:20 daedalus kernel: CR2: 000055c4e0ae7eb0 CR3: 000000010670c003 CR4: 0000000000770ee0 Mar 20 11:53:20 daedalus kernel: PKRU: 55555554 Mar 20 11:53:20 daedalus kernel: Call Trace: Mar 20 11:53:20 daedalus kernel: <TASK> Mar 20 11:53:20 daedalus kernel: intel_atomic_commit_tail+0x958/0xea0 [i915 3266444b8651c009ef6c700725f41e4a26b9ad4d] Mar 20 11:53:20 daedalus kernel: intel_atomic_commit+0x34f/0x390 [i915 3266444b8651c009ef6c700725f41e4a26b9ad4d] Mar 20 11:53:20 daedalus kernel: drm_atomic_commit+0x93/0xc0 Mar 20 11:53:20 daedalus kernel: ? __pfx___drm_printfn_info+0x10/0x10 Mar 20 11:53:20 daedalus kernel: drm_mode_atomic_ioctl+0x93d/0xb30 Mar 20 11:53:20 daedalus kernel: ? __pfx_drm_mode_atomic_ioctl+0x10/0x10 Mar 20 11:53:20 daedalus kernel: drm_ioctl_kernel+0xbe/0x160 Mar 20 11:53:20 daedalus kernel: drm_ioctl+0x221/0x420 Mar 20 11:53:20 daedalus kernel: ? __pfx_drm_mode_atomic_ioctl+0x10/0x10 Mar 20 11:53:20 daedalus kernel: ? __x64_sys_ioctl+0xa8/0xd0 Mar 20 11:53:20 daedalus kernel: __x64_sys_ioctl+0x8d/0xd0 Mar 20 11:53:20 daedalus kernel: do_syscall_64+0x58/0x80 Mar 20 11:53:20 daedalus kernel: ? do_syscall_64+0x67/0x80 Mar 20 11:53:20 daedalus kernel: ? __irq_exit_rcu+0x3b/0xe0 Mar 20 11:53:20 daedalus kernel: entry_SYSCALL_64_after_hwframe+0x72/0xdc Mar 20 11:53:20 daedalus kernel: RIP: 0033:0x7ff58f90dabf Mar 20 11:53:20 daedalus kernel: Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 > Mar 20 11:53:20 daedalus kernel: RSP: 002b:00007ffe71826070 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 Mar 20 11:53:20 daedalus kernel: RAX: ffffffffffffffda RBX: 0000563ddd5149b0 RCX: 00007ff58f90dabf Mar 20 11:53:20 daedalus kernel: RDX: 00007ffe71826110 RSI: 00000000c03864bc RDI: 000000000000000a Mar 20 11:53:20 daedalus kernel: RBP: 00007ffe71826110 R08: 0000000000000007 R09: 000000000000002f Mar 20 11:53:20 daedalus kernel: R10: 000000000000002a R11: 0000000000000246 R12: 00000000c03864bc Mar 20 11:53:20 daedalus kernel: R13: 000000000000000a R14: 0000563ddb928440 R15: 0000563ddabad830 Mar 20 11:53:20 daedalus kernel: </TASK> Mar 20 11:53:20 daedalus kernel: ---[ end trace 0000000000000000 ]--- -- You are receiving this mail because: You are the assignee for the bug.

1 3

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

21 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1209436 https://bugzilla.suse.com/show_bug.cgi?id=1209436#c54 Marcus Meissner <meissner(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo? | --- Comment #54 from Marcus Meissner <meissner(a)suse.com> --- The old kernel was retracted, you can still use that. (deinstall the released buggy one). The new kernel currently enters QA, will be released in the next days. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1190261] New: Kernel scriptlets: XXX: Only call mokutil if UEFI and shim are used
by bugzilla_noreply＠suse.com 21 Mar '23

21 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1190261 Bug ID: 1190261 Summary: Kernel scriptlets: XXX: Only call mokutil if UEFI and shim are used 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: martin.wilck(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Spin-off from bug 1189841. From https://github.com/openSUSE/suse-module-tools/pull/33: @mwilck: so why not test this? e.g. like this: if [ "$(mokutil --sb-state 2>/dev/null)" = "SecureBoot enabled" ]; then ... fi @hramrach: ??? The part that github displays as context for this comment does not look relevant @hramrach hramrach 21 hours ago Member Right, if you refer to XXX: Only call mokutil if UEFI and shim are used then I have no opinion on that. Should be probably handled in a separate bug and the implications of any possible check discussed to death. @hramrach hramrach 21 hours ago Member Actually, there is the problem that on arm64 you suddenly get from no shim to shim on SP update without any warning so this is really hairy to get right. Really deserves a separate bug. -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 1209540] New: Kernel update hangs on boot
by bugzilla_noreply＠suse.com 21 Mar '23

21 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1209540 Bug ID: 1209540 Summary: Kernel update hangs on boot Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: x86-64 OS: openSUSE Leap 15.4 Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: bugz57(a)top.geek.nz QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 865704 --> http://bugzilla.opensuse.org/attachment.cgi?id=865704&action=edit console output when hanging The kernel update a few days ago to kernel-default-5.14.21-150400.24.49.3.x86_64 hangs on boot, after the grub menu has been and gone. I have photos of the console output when booting the recovery version of the kernel. At that point console output just stops. Keyboard numlock/capslock do nothing, but sysrq sequences work (r e i s u b) and allow to reboot however cleanly. I had recently fiddled with the bios but can't find any settings that make this kernel boot. There is no change to USB devices connected. There was no change to any hardware. There is an nvidia graphics card but no nvidia driver nor nv are loaded; the card is unused. In any case, the previous kernel kernel-default-5.14.21-150400.24.46.1.x86_64 boots OK with any bios setting and with all USB devices connected. In 4 years no kernel has ever hung on boot on this box. -- You are receiving this mail because: You are the assignee for the bug.

1 8

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

21 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1209436 Jeffrey Cheung <jcheung(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P2 - High CC| |jcheung(a)suse.com -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1208728] New: Thinkpad X1 Carbon Gen 10 won't enter S3 sleep on kernel 6
by bugzilla_noreply＠suse.com 21 Mar '23

21 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1208728 Bug ID: 1208728 Summary: Thinkpad X1 Carbon Gen 10 won't enter S3 sleep on kernel 6 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: victorfuga(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Starting with kernel 6, my thinkpad x1 carbon will not enter s3 sleep even when set as the default sleep option. Checked a few distros and noted it was working using kernel 5.19 "LTS" in manjaro. Currently running Tumbleweed snapshot 20230226, sleep mode is set to "Linux" in the bios. Checked on lid close, sleep button in KDE, and Fn + 4 key combo. $ cat /sys/power/mem_sleep s2idle [deep] $ sudo journalctl | grep "PM: suspend" | tail -2 2�� 27 18:29:09 reisen kernel: PM: suspend entry (s2idle) 2�� 27 18:29:11 reisen kernel: PM: suspend exit -- You are receiving this mail because: You are the assignee for the bug.

1 6

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

20 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1200983 https://bugzilla.suse.com/show_bug.cgi?id=1200983#c14 --- Comment #14 from Michael Hirmke <opensuse(a)mike.franken.de> --- (In reply to Takashi Iwai from comment #13) > (In reply to Michael Hirmke from comment #12) > > (In reply to Stefan Dirsch from comment #10) > > > Thanks for testing. Indeed this makes it a kernel issue. You could also test > > > the mouse on the Linux console via 'evtest /dev/input/eventXX', but this is > > > a bit complicated to figure out the right device. So I only wanted to > > > mention keyboard here. > > > > Keyboard and mouse both have problems one the console, too. > > The keyboard vanishes after a few seconds and returns, as soon as a key is > > pressed, but the first keypress is not shown. The mouse never works on the > > console - no events are shown. > > What do you mean "vanishes" here? It means that the /dev/input/event* device > is gone? no, there is no mouse pointer and the keyboard light is off. > > The point to check here is whether the device file persists and can > read/write from a user-space (no matter whether it's processed or not). Or > is the (USB?) audio device itself disappears and reappears automatically. Because the keyboard also has problems, this isn't easy to debug. What exactly would you like me to test? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1207915] amdgpu 0000:00:01.0: amdgpu: GPU fault detected: 147 0x00422002 for process sddm-greeter pid 2186 thread sddm-greet:cs0 pid 2193
by bugzilla_noreply＠suse.com 20 Mar '23

20 Mar '23

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

1 0

[Bug 1208756] Goodix GDIX1003/GT9110P i2c device is Unsupported
by bugzilla_noreply＠suse.com 20 Mar '23

20 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1208756 https://bugzilla.suse.com/show_bug.cgi?id=1208756#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> --- Could you give hwinfo output? Also the output of acpidump. GDX10003 seems to be a new chip, so you'll likely need to do trial-and-error approach with the customized kernel. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1207915] amdgpu 0000:00:01.0: amdgpu: GPU fault detected: 147 0x00422002 for process sddm-greeter pid 2186 thread sddm-greet:cs0 pid 2193
by bugzilla_noreply＠suse.com 20 Mar '23

20 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1207915 https://bugzilla.suse.com/show_bug.cgi?id=1207915#c3 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jshand2013(a)gmail.com, | |tiwai(a)suse.com Flags| |needinfo?(jshand2013@gmail. | |com) --- Comment #3 from Takashi Iwai <tiwai(a)suse.com> --- Sounds like a one-off issue. Is the problem reproduced? If not, let's close. -- 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 20 Mar '23

20 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1200983 https://bugzilla.suse.com/show_bug.cgi?id=1200983#c13 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tiwai(a)suse.com --- Comment #13 from Takashi Iwai <tiwai(a)suse.com> --- (In reply to Michael Hirmke from comment #12) > (In reply to Stefan Dirsch from comment #10) > > Thanks for testing. Indeed this makes it a kernel issue. You could also test > > the mouse on the Linux console via 'evtest /dev/input/eventXX', but this is > > a bit complicated to figure out the right device. So I only wanted to > > mention keyboard here. > > Keyboard and mouse both have problems one the console, too. > The keyboard vanishes after a few seconds and returns, as soon as a key is > pressed, but the first keypress is not shown. The mouse never works on the > console - no events are shown. What do you mean "vanishes" here? It means that the /dev/input/event* device is gone? The point to check here is whether the device file persists and can read/write from a user-space (no matter whether it's processed or not). Or is the (USB?) audio device itself disappears and reappears automatically. -- You are receiving this mail because: You are the assignee for the bug.

1 0

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

20 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1209197 https://bugzilla.suse.com/show_bug.cgi?id=1209197#c2 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sddrossy(a)aol.com, | |tiwai(a)suse.com Flags| |needinfo?(sddrossy(a)aol.com) --- Comment #2 from Takashi Iwai <tiwai(a)suse.com> --- Seems to be a problem of nouveau. Could you report rather to the upstream, gitlab.freedesktop.org Issues? -- 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 20 Mar '23

20 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1209436 https://bugzilla.suse.com/show_bug.cgi?id=1209436#c48 Christian Kurtsiefer <christian.kurtsiefer(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |christian.kurtsiefer@gmail. | |com --- Comment #48 from Christian Kurtsiefer <christian.kurtsiefer(a)gmail.com> --- Thanks for highliting this. Confirm the boot hangs on kernel 5.14.21-150400.24.49-default after update, but machine boots into 5.14.21-150400.24.46-default. Hardware used is ThinkpadX230 iwth i915 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1207837] amdgpu: externals displays don't work when booting with plugged in docking station
by bugzilla_noreply＠suse.com 20 Mar '23

20 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1207837 https://bugzilla.suse.com/show_bug.cgi?id=1207837#c21 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #21 from Takashi Iwai <tiwai(a)suse.com> --- OK, thanks for the update. I close this as fixed now. Feel free to reopen if the problem still persists with the latest 6.2.x kernel. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1208728] Thinkpad X1 Carbon Gen 10 won't enter S3 sleep on kernel 6
by bugzilla_noreply＠suse.com 20 Mar '23

20 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1208728 https://bugzilla.suse.com/show_bug.cgi?id=1208728#c7 --- Comment #7 from Takashi Iwai <tiwai(a)suse.com> --- Hm, if the problem persists with the latest 6.2.x kernel (and better to check with 6.3-rc kernel in OBS Kernel:HEAD), we should report it to the upstream. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1207900] Thinkpad P16 Gen 1 freezes when put into Dockingstation
by bugzilla_noreply＠suse.com 20 Mar '23

20 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1207900 Petr Vorel <petr.vorel(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugzilla.suse.com/s | |how_bug.cgi?id=1209441 -- You are receiving this mail because: You are the assignee for the bug.

1 0

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

20 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1206224 http://bugzilla.opensuse.org/show_bug.cgi?id=1206224#c49 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution|--- |FIXED --- Comment #49 from Takashi Iwai <tiwai(a)suse.com> --- OK, thanks for the info. Then let's close this bug now. If a similar problem still happens with another model, please open a new bug report. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1209457] NFSv4 broken after kernel update (5.14.21-150400.24.46-default to 5.14.21-150400.24.49)
by bugzilla_noreply＠suse.com 20 Mar '23

20 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1209457 https://bugzilla.suse.com/show_bug.cgi?id=1209457#c3 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tiwai(a)suse.com Assignee|kernel-bugs(a)opensuse.org |nfbrown(a)suse.com --- Comment #3 from Takashi Iwai <tiwai(a)suse.com> --- There has been only one patch (and one kABI workaround) between *.46 and *.49 about the NFS (96398e7b719c and 931f6bd42dd5). Neil, could you check? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1209457] NFSv4 broken after kernel update (5.14.21-150400.24.46-default to 5.14.21-150400.24.49)
by bugzilla_noreply＠suse.com 19 Mar '23

19 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1209457 https://bugzilla.suse.com/show_bug.cgi?id=1209457#c2 Peter VARGA <office(a)vargapeter.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |office(a)vargapeter.net --- Comment #2 from Peter VARGA <office(a)vargapeter.net> --- Completely unreliable behaviour. Files are not created properly on the NFS drive, or, even they do exist, the client doesn't see them. I had to restore the snapshot. This is not really a supporting situation for paying license. The whole system became very unstable. It looks to me the update has been withdrawn from the update list. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1209457] New: NFSv4 broken after kernel update (5.14.21-150400.24.46-default to 5.14.21-150400.24.49)
by bugzilla_noreply＠suse.com 19 Mar '23

19 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1209457 Bug ID: 1209457 Summary: NFSv4 broken after kernel update (5.14.21-150400.24.46-default to 5.14.21-150400.24.49) Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: x86-64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: wied(a)x42.info QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I am using rdiff-backup to backup all important files for about 10 years now. Target is an NFSv4 mount. Again in 5.14.21-150400.24.49-default this does not work properly any more: read and writes seam to be affected. When booting back to 5.14.21-150400.24.46-default everything works fine again which eliminates all reasons related to python or rdiff-backup itself. My kernel is set to preempt=full. Unfortunately the error happens quite discretely: no error messages in dmesg or journal appear. In some 15.x version NFSv4 too was broken by some kernel update once: directory listings (which in my case contain about 15k entries) suddenly where truncated. I hope this isn't some recursion? -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1209467] New: NFSv4 client code broken after kernel update (5.14.21-150400.24.46-default to 5.14.21-150400.24.49
by bugzilla_noreply＠suse.com 19 Mar '23

19 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1209467 Bug ID: 1209467 Summary: NFSv4 client code broken after kernel update (5.14.21-150400.24.46-default to 5.14.21-150400.24.49 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: x86-64 OS: All Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: avuzel(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- duplicate of Bug 1209457, please delete Bug 1209457 I am using rdiff-backup to backup all important files for about 10 years now. Target is an NFSv4 mount. Again in 5.14.21-150400.24.49-default this does not work properly any more: read and writes seam to be affected. When booting back to 5.14.21-150400.24.46-default everything works fine again which eliminates all reasons related to python or rdiff-backup itself. My kernel is set to preempt=full. Unfortunately the error happens quite discretely: no error messages in dmesg or journal appear. In some 15.x version NFSv4 client code too was broken by some kernel update once: directory listings (which in my case contain about 15k entries) suddenly where truncated. I hope this isn't some recursion? -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1209464] Leap 15.4 image 5.14.21-150400.24.49-default hangs during startup of HP laptop
by bugzilla_noreply＠suse.com 19 Mar '23

19 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1209464 http://bugzilla.opensuse.org/show_bug.cgi?id=1209464#c1 hui <sturm-fr(a)web.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from hui <sturm-fr(a)web.de> --- Already reported several times. Search shows this is a dup *** This bug has been marked as a duplicate of bug 1209436 *** -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1209464] Leap 15.4 image 5.14.21-150400.24.49-default hangs during startup of HP laptop
by bugzilla_noreply＠suse.com 19 Mar '23

19 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1209464 Andreas Stieger <Andreas.Stieger(a)gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Bootloader |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 1209296] New: Missing backlight control on Dell Vostro 3700
by bugzilla_noreply＠suse.com 19 Mar '23

19 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1209296 Bug ID: 1209296 Summary: Missing backlight control on Dell Vostro 3700 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: eh(a)eggbird.eu QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 865548 --> http://bugzilla.opensuse.org/attachment.cgi?id=865548&action=edit output of dmesg on kernels before 6.2.1 and WITH the kernel parameter acpi_backlight=native /sys/class/backlight contained nv_backlight. Starting with 6.2.1 AND the same parameter /sys/class/backlight remains empty. After removing the kernel parameter the directory contains acpi_video0. The backlight parameter in /sys/class/backlight/acpi_video0 responds to the function keys to increase/decrease the backlight, but the "real" backlight does not respond. I've just (15 March) installed 6.2.4-1-default but the problem remains. -- You are receiving this mail because: You are the assignee for the bug.

1 16

[Bug 1209449] New: Wifi not working with most recent version of kernel-firmware-realtek-20230313-1.1 (with workaround)
by bugzilla_noreply＠suse.com 19 Mar '23

19 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1209449 Bug ID: 1209449 Summary: Wifi not working with most recent version of kernel-firmware-realtek-20230313-1.1 (with workaround) 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: Hans.Aschauer(a)web.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- After updating my openSuse Tumbleweed on 2023-03-18, I found that my Wifi card was no longer found. I traced it down to a problem with loading the firmware file: # dmesg | grep rtw [ 5.092426] rtw89_8852be 0000:03:00.0: Direct firmware load for rtw89/rtw8852b_fw.bin failed with error -2 [ 5.092431] rtw89_8852be 0000:03:00.0: failed to early request firmware: -2 [ 5.093334] rtw89_8852be 0000:03:00.0: enabling device (0000 -> 0003) [ 5.106477] rtw89_8852be 0000:03:00.0: no suitable firmware found [ 5.106855] rtw89_8852be 0000:03:00.0: failed to recognize firmware [ 5.107068] rtw89_8852be 0000:03:00.0: failed to setup chip information [ 5.109638] rtw89_8852be: probe of 0000:03:00.0 failed with error -2 Booting from a btrfs snapshot from before the update left me with a working Wifi. I noticed that in the update, the firmware file has been modified (snapshot 5 is the one with the working Wifi): From snapshot 5: # cd /.snapshots/5/snapshot/lib/firmware/rtw89/ # sha256sum rtw8852* ... 147ece8abea92576a7cdb888f174422abb3b1265371c016e16093400934b9858 rtw8852b_fw.bin.xz ... # From not working system after update: # sha256sum /lib/firmware/rtw89/rtw8852* ... 0a1b68c540e5670c4e651802c7ecbd01bd045e98a4d36903aee494abde94b69f /lib/firmware/rtw89/rtw8852b_fw.bin.xz ... I could work around the problem by copying the "old" version of the firmware file over the "new" version and reloading the rtl89 modules: # rmmod rtw89_8852be rtw89_8852b rtw89_pci rtw89_core # modprobe rtw89_8852be # dmesg | grep rtw [...} [ 2041.634894] rtw89_8852be 0000:03:00.0: Direct firmware load for rtw89/rtw8852b_fw.bin failed with error -2 [ 2041.634900] rtw89_8852be 0000:03:00.0: failed to early request firmware: -2 [ 2041.645334] rtw89_8852be 0000:03:00.0: Firmware version 0.27.32.1, cmd version 0, type 1 [ 2041.645339] rtw89_8852be 0000:03:00.0: Firmware version 0.27.32.1, cmd version 0, type 3 [ 2041.958866] rtw89_8852be 0000:03:00.0: chip rfe_type is 1 [ 2041.991533] rtw89_8852be 0000:03:00.0 wlp3s0: renamed from wlan0 After the reload, the Wifi was detected by NetworkManager, and I got a working connection immediately. ---- Some details about my system: ThinkPad E14 Gen4 AMD (21EB0040GE) # uname -a Linux thinkpad-E14.site 6.2.4-1-default #1 SMP PREEMPT_DYNAMIC Sat Mar 11 10:13:47 UTC 2023 (0532a55) x86_64 x86_64 x86_64 GNU/Linux # rpm -qa | grep kernel-default kernel-default-6.2.4-1.1.x86_64 # zypper info kernel-firmware-realtek Loading repository data... Reading installed packages... Information for package kernel-firmware-realtek: ------------------------------------------------ Repository : Haupt-Repository (OSS) Name : kernel-firmware-realtek Version : 20230313-1.1 Arch : noarch Vendor : openSUSE Installed Size : 1.6 MiB Installed : Yes Status : up-to-date Source package : kernel-firmware-20230313-1.1.src Upstream URL : https://git.kernel.org/cgit/linux/kernel/git/firmware/linux-firmware.git/ Summary : Kernel firmware files for Realtek wireless drivers Description : This package contains compressed kernel firmware files for Realtek wireless drivers. # hwinfo --network 42: None 00.0: 10701 Ethernet [Created at net.126] Unique ID: Mqes.ndpeucax6V1 Parent ID: hAO_.0Y9Hsjl5nJ7 SysFS ID: /class/net/wlp3s0 SysFS Device Link: /devices/pci0000:00/0000:00:02.3/0000:03:00.0 Hardware Class: network interface Model: "Ethernet network interface" Driver: "rtw89_8852be" Driver Modules: "rtw89_8852be" Device File: wlp3s0 HW Address: f4:6a:dd:xx:yy:zz Permanent HW Address: f4:6a:dd:xx:yy:zz Link detected: yes Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #1 (Ethernet controller) [... ethernet and loopback snipped ...] # lspci 00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne Root Complex 00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne IOMMU 00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host Bridge 00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host Bridge 00:02.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne PCIe GPP Bridge 00:02.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne PCIe GPP Bridge 00:02.3 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne PCIe GPP Bridge 00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host Bridge 00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir Internal PCIe GPP Bridge to Bus 00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 51) 00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 51) 00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 0 00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 1 00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 2 00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 3 00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 4 00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 5 00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 6 00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 7 01:00.0 Non-Volatile memory controller: Micron Technology Inc Device 5411 (rev 01) 02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15) 03:00.0 Network controller: Realtek Semiconductor Co., Ltd. Device b852 04:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Barcelo (rev c2) 04:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Renoir Radeon High Definition Audio Controller 04:00.2 Encryption controller: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) Platform Security Processor 04:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne USB 3.1 04:00.4 USB controller: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne USB 3.1 04:00.5 Multimedia controller: Advanced Micro Devices, Inc. [AMD] ACP/ACP3X/ACP6x Audio Coprocessor (rev 01) 04:00.6 Audio device: Advanced Micro Devices, Inc. [AMD] Family 17h/19h HD Audio Controller -- You are receiving this mail because: You are the assignee for the bug.

1 2

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

18 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1209436 https://bugzilla.suse.com/show_bug.cgi?id=1209436#c40 --- Comment #40 from Bob Goddard <opensuse(a)1.opensuse.bgcomp.co.uk> --- (In reply to Darren Davis from comment #39) > Alternative work around for those affected by the bug is to blacklist the > i915 kernel module on the grub boot line. Yeah, sure. Another workaround is just to switch it off and put in into the closet. -- 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 18 Mar '23

18 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1209436 https://bugzilla.suse.com/show_bug.cgi?id=1209436#c39 Darren Davis <ddavis(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?, SHIP_STOPPER?, | |CCB_Review? --- Comment #39 from Darren Davis <ddavis(a)suse.com> --- Alternative work around for those affected by the bug is to blacklist the i915 kernel module on the grub boot line. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206977] New: On boot hangs on fbo:switching to i915 from EFI VGA
by bugzilla_noreply＠suse.com 18 Mar '23

18 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1206977 Bug ID: 1206977 Summary: On boot hangs on fbo:switching to i915 from EFI VGA Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: x86-64 OS: openSUSE Leap 15.4 Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: nsnospam3(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- HW: ASUS Prime Z790-P with iCore5 CPU with integrated GPU, M2 NVMe SSD Installation was not possible without grub linux parameter nomodeset. Of course with this parameter only the basic resolution of 1024x768 is available. Every successive boot hangs on log entry fbo:switching to i915 from EFI VGA. As I could not find any solution I tried first to install Windows 10. Worked without any Problem Intel drivers were installed properly and I got full resolution of 2560x1440. I tried openSUSE-Tumbleweed-GNOME-Live-x86_64-Current.iso starting form USB. Worked as expected with full resolution. I tried to install openSUSE-Tumbleweed-DVD-x86_64-Current.iso. Didn't hang and I could start the installation. I interromped the installation to try Leap 15.4 again first getting the updated version i.e. openSUSE-Leap-15.4-CR-DVD-x86_64-Build31.38-Media.iso. No chance, without nomodeset parameter no installation possible. I'll install tumbleweed now, but this is not exactly what I wanted. -- You are receiving this mail because: You are the assignee for the bug.

1 6

[Bug 1209452] New: Latest Leap update kernel no longer boots without "nomodeset"
by bugzilla_noreply＠suse.com 18 Mar '23

18 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1209452 Bug ID: 1209452 Summary: Latest Leap update kernel no longer boots without "nomodeset" Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: seife(a)novell.slipkontur.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 865646 --> http://bugzilla.opensuse.org/attachment.cgi?id=865646&action=edit journalctl -b -1, the log of a broken boot, probably in the end I just power cycled. I updated my home server to find that it no longer boots. it just stops with a blank screen where I normally would expect it to switch video mode to 1024x768. Adding "nomodeset" fixes the boot. The machine is a FUJITSU ESPRIMO P757, Intel(R) Core(TM) i3-6100 CPU @ 3.70GHz Actually checking the log with "journalctl -b -1" shows that it actually is booting but not working correctly (it also has no network when booted without nomodeset). Attaching this log. It shows a few backtraces related to i915. -- You are receiving this mail because: You are the assignee for the bug.

1 1

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

18 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1209436 https://bugzilla.suse.com/show_bug.cgi?id=1209436#c29 --- Comment #29 from Marcus Meissner <meissner(a)suse.com> --- I am marking the kernel as retracted. (not removing it). this will make it not selectable for update or installation. -- 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 18 Mar '23

18 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1209436 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo? | -- 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 17 Mar '23

17 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1209436 Jiri Kosina <jkosina(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mschnitzer(a)suse.com Flags| |needinfo?(mschnitzer(a)suse.c | |om) -- 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 17 Mar '23

17 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1209436 Jiri Kosina <jkosina(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |meissner(a)suse.com Flags| |needinfo?(meissner(a)suse.com | |) -- 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 17 Mar '23

17 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1209436 https://bugzilla.suse.com/show_bug.cgi?id=1209436#c21 --- Comment #21 from Brad Bendily <brad.bendily(a)suse.com> --- (In reply to Takashi Iwai from comment #15) > Could you check the kernel in OBS home:tiwai:bsc1209436 repo? > http://download.opensuse.org/repositories/home:/tiwai:/bsc1209436/pool/ > > It seems that a backport of i915 upstream fix caused the problem. The > kernel above reverted it on top of the latest SLE15-SP4 git branch. I confirm this kernel resolved the issue for me too. -- 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 17 Mar '23

17 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1209436 https://bugzilla.suse.com/show_bug.cgi?id=1209436#c20 --- Comment #20 from Matthias Pfafferodt <syntron(a)web.de> --- (In reply to Takashi Iwai from comment #15) > Could you check the kernel in OBS home:tiwai:bsc1209436 repo? > http://download.opensuse.org/repositories/home:/tiwai:/bsc1209436/pool/ > > It seems that a backport of i915 upstream fix caused the problem. The > kernel above reverted it on top of the latest SLE15-SP4 git branch. I can also confirm that this kernel works! -- 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 17 Mar '23

17 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1209436 https://bugzilla.suse.com/show_bug.cgi?id=1209436#c19 --- Comment #19 from E. Choroba <choroba(a)matfyz.cz> --- > Could you check the kernel in OBS home:tiwai:bsc1209436 repo? Yes, it seems to boot without problems. -- 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 17 Mar '23

17 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1209436 Vlastimil Babka <vbabka(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |vbabka(a)suse.com -- 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 17 Mar '23

17 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1209436 Jiri Kosina <jkosina(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jkosina(a)suse.com -- 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 17 Mar '23

17 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1209436 https://bugzilla.suse.com/show_bug.cgi?id=1209436#c15 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tiwai(a)suse.com Flags| |needinfo? --- Comment #15 from Takashi Iwai <tiwai(a)suse.com> --- Could you check the kernel in OBS home:tiwai:bsc1209436 repo? http://download.opensuse.org/repositories/home:/tiwai:/bsc1209436/pool/ It seems that a backport of i915 upstream fix caused the problem. The kernel above reverted it on top of the latest SLE15-SP4 git branch. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1209440] New: After Kernel Update to 5.14.21-150400.24.49-default, boot fails hard
by bugzilla_noreply＠suse.com 17 Mar '23

17 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1209440 Bug ID: 1209440 Summary: After Kernel Update to 5.14.21-150400.24.49-default, boot fails hard 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: thomi.schmid(a)swissonline.ch 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: I have updated the Leap 15.4 kernel today, 17.03.2023, ca. 17:00 on 2 machines (desktop with Intel Core i5-6400, laptop with Intel Core i3-1005G1) from "5.14.21-150400.24.46-default" to "5.14.21-150400.24.49-default". Download and install went OK, but after the restart, the PCs stopped booting after GRUB having the new kernel selected and after showing the first initial kernel message "x86/cpu: SGX disabled by BIOS" There they hung hard, i.e. not reaction on keyboard, no blinking keyboard LEDs. Both PC needed to be turned off and on again to restart, where the same problem occurred again. Both PCs could then be restarted again with no error using the previous kernel "5.14.21-150400.24.46-default". Reproducible: Always Steps to Reproduce: 1.Install kernel 5.14.21-150400.24.49-default using YaST Online Update 2.Reboot PC 3.Select kernel 5.14.21-150400.24.49-default in GRUB 4.Boot selected kernel 5.14.21-150400.24.49-default Actual Results: PC hangs after first kernel message on screen Keyboard "dead": No keyboard LEDs (NumLock), no LEDs blinking Expected Results: PC should have booted successfully using kernel 5.14.21-150400.24.49-default Happend on 2 different PCs (older desktop, laptop) Happens everytime PC is "dead" and needs power off/on to restart -> Ctrl-Alt-Del is not working -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 1209440] After Kernel Update to 5.14.21-150400.24.49-default, boot fails hard
by bugzilla_noreply＠suse.com 17 Mar '23

17 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1209440 https://bugzilla.suse.com/show_bug.cgi?id=1209440#c4 Reimar Imhof <tuxuser(a)quantentunnel.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tuxuser(a)quantentunnel.de --- Comment #4 from Reimar Imhof <tuxuser(a)quantentunnel.de> --- Same problem here with Lenovo ideapad 3 using intel iris internal graphics. The notebook boots well using kernel 6.2.6 from download.opensuse.org/repositories/Kernel:/stable:/Backport/standard/ -- You are receiving this mail because: You are the assignee for the bug.

1 0

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

17 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1206224 https://bugzilla.suse.com/show_bug.cgi?id=1206224#c48 --- Comment #48 from Maintenance Automation <maint-coord+maintenance-robot(a)suse.de> --- SUSE-SU-2023:0796-1: An update that solves eight vulnerabilities and has 85 fixes can now be installed. Category: security (important) Bug References: 1166486, 1177529, 1203331, 1203332, 1204993, 1205544, 1206224, 1206232, 1206459, 1206640, 1206876, 1206877, 1206878, 1206880, 1206881, 1206882, 1206883, 1206884, 1206885, 1206886, 1206889, 1206894, 1207051, 1207270, 1207328, 1207588, 1207589, 1207590, 1207591, 1207592, 1207593, 1207594, 1207603, 1207605, 1207606, 1207607, 1207608, 1207609, 1207610, 1207613, 1207615, 1207617, 1207618, 1207619, 1207620, 1207621, 1207623, 1207624, 1207625, 1207626, 1207628, 1207630, 1207631, 1207632, 1207634, 1207635, 1207636, 1207638, 1207639, 1207641, 1207642, 1207643, 1207644, 1207645, 1207646, 1207647, 1207648, 1207651, 1207653, 1207770, 1207773, 1207845, 1207875, 1208149, 1208153, 1208183, 1208212, 1208290, 1208420, 1208428, 1208429, 1208449, 1208534, 1208541, 1208570, 1208607, 1208628, 1208700, 1208741, 1208759, 1208784, 1208787, 1209188 CVE References: CVE-2022-36280, CVE-2022-38096, CVE-2023-0045, CVE-2023-0461, CVE-2023-0597, CVE-2023-22995, CVE-2023-23559, CVE-2023-26545 Sources used: openSUSE Leap Micro 5.3 (src): kernel-default-base-5.14.21-150400.24.49.3.150400.24.19.3 openSUSE Leap 15.4 (src): kernel-obs-qa-5.14.21-150400.24.49.2, kernel-default-base-5.14.21-150400.24.49.3.150400.24.19.3, kernel-syms-5.14.21-150400.24.49.4, kernel-source-5.14.21-150400.24.49.4, kernel-obs-build-5.14.21-150400.24.49.3 SUSE Linux Enterprise Micro for Rancher 5.3 (src): kernel-default-base-5.14.21-150400.24.49.3.150400.24.19.3 SUSE Linux Enterprise Micro 5.3 (src): kernel-default-base-5.14.21-150400.24.49.3.150400.24.19.3 Basesystem Module 15-SP4 (src): kernel-source-5.14.21-150400.24.49.4, kernel-default-base-5.14.21-150400.24.49.3.150400.24.19.3 Development Tools Module 15-SP4 (src): kernel-syms-5.14.21-150400.24.49.4, kernel-source-5.14.21-150400.24.49.4, kernel-obs-build-5.14.21-150400.24.49.3 SUSE Linux Enterprise Live Patching 15-SP4 (src): kernel-livepatch-SLE15-SP4_Update_9-1-150400.9.3.3 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 1207948] Lenovo T14s Gen3 AMD resume from hibernation ends in kernel panic
by bugzilla_noreply＠suse.com 17 Mar '23

17 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1207948 https://bugzilla.suse.com/show_bug.cgi?id=1207948#c37 --- Comment #37 from Martin Jambor <mjambor(a)suse.com> --- The script is something that I was looking for and works great, 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 17 Mar '23

17 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1209436 https://bugzilla.suse.com/show_bug.cgi?id=1209436#c3 John Carrick Smith <jcarricksmith(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jcarricksmith(a)gmail.com --- Comment #3 from John Carrick Smith <jcarricksmith(a)gmail.com> --- Same experience as Comment #1 although I do not know if it is the switch to i915 at the time of hang. Fan comes on strong during hang. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1209221] Leap 15.4, Leap 15.5 and Tumbleweed are not working without attached power supply
by bugzilla_noreply＠suse.com 17 Mar '23

17 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1209221 http://bugzilla.opensuse.org/show_bug.cgi?id=1209221#c9 --- Comment #9 from Volker Hilgert <v.hilgert(a)gmx.net> --- Created attachment 865627 --> http://bugzilla.opensuse.org/attachment.cgi?id=865627&action=edit System starts (Kubuntu, Linux Mint Cinnamon, Fedora KDE) -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1207900] Thinkpad P16 Gen 1 freezes when put into Dockingstation
by bugzilla_noreply＠suse.com 17 Mar '23

17 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1207900 https://bugzilla.suse.com/show_bug.cgi?id=1207900#c20 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #20 from Takashi Iwai <tiwai(a)suse.com> --- The AMDGPU problem is a completely different issue and we shouldn't mix in a single bug report. Please open another bug report, and let's close this one as fixed. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1207900] Thinkpad P16 Gen 1 freezes when put into Dockingstation
by bugzilla_noreply＠suse.com 17 Mar '23

17 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1207900 https://bugzilla.suse.com/show_bug.cgi?id=1207900#c19 --- Comment #19 from Michael Vetter <mvetter(a)suse.com> --- > And, if you boot with pcie_aspm=off, does the boot still hang? I did not test the old kernels with this. Should I now? > If I understand correctly, the original issue has been addressed with 6.2.1 > kernel? Then the tests with older kernels are rather redundant... That's right. The freezing stops with 6.2.1. 6.2.2 doesn't boot at all. And 6.2.4 is fine like 6.2.1. But I still can't work "normally". Every time I plug my laptop out of the docking station that will mean that I have to reboot the machine when I want to plug it in again. Since it will not recognize the external monitor otherwise. Every time the laptop goes go suspend, it will not detect the external monitor as well. And it even looks like it this will also happen if it just blanks the screen. By default after 5 min GNOME blanks the screen. And sometimes I had problems that after I return to the computer I had to force reboot. So yes the freezing doesn't happen anymore. But still its quite unusable. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1207900] Thinkpad P16 Gen 1 freezes when put into Dockingstation
by bugzilla_noreply＠suse.com 17 Mar '23

17 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1207900 https://bugzilla.suse.com/show_bug.cgi?id=1207900#c18 --- Comment #18 from Takashi Iwai <tiwai(a)suse.com> --- And, if you boot with pcie_aspm=off, does the boot still hang? If I understand correctly, the original issue has been addressed with 6.2.1 kernel? Then the tests with older kernels are rather redundant... -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1207900] Thinkpad P16 Gen 1 freezes when put into Dockingstation
by bugzilla_noreply＠suse.com 17 Mar '23

17 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1207900 https://bugzilla.suse.com/show_bug.cgi?id=1207900#c17 --- Comment #17 from Michael Vetter <mvetter(a)suse.com> --- Yes I have. I also enabled it at first to see the difference. But all reported tests were with disabled secure boot (I also left it disabled for now). And the boot process started but didn't finish (that's what I meant with doesn't boot). -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1207900] Thinkpad P16 Gen 1 freezes when put into Dockingstation
by bugzilla_noreply＠suse.com 17 Mar '23

17 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1207900 https://bugzilla.suse.com/show_bug.cgi?id=1207900#c16 --- Comment #16 from Takashi Iwai <tiwai(a)suse.com> --- You have disabled Secure Boot, right? Otherwise the unofficial kernels won't boot. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1207900] Thinkpad P16 Gen 1 freezes when put into Dockingstation
by bugzilla_noreply＠suse.com 17 Mar '23

17 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1207900 https://bugzilla.suse.com/show_bug.cgi?id=1207900#c15 Michael Vetter <mvetter(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(mvetter(a)suse.com) | --- Comment #15 from Michael Vetter <mvetter(a)suse.com> --- Thanks for the explanation. 6.0.12-1.1.ga6c4f4e: does not boot at all. I see `16.604928][T1003] spi-nor spi0.0: unrecognized JEDEC id bytes: 3c f0 30 09 6f 00` 5.19.12-1.1.g95fa5b8: does not boot at all. All I see after a while is a blinking cursor. I also updated to 6.2.4-1.1 now and with this I have the same behaviour like with 6.2.1-1, meaning it boots and I can use the laptop. However when I disconnect from docking station and then reconnect it doesn't detect the external monitor anymore. Any more information I can provide that would be helpful? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1207900] Thinkpad P16 Gen 1 freezes when put into Dockingstation
by bugzilla_noreply＠suse.com 17 Mar '23

17 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1207900 https://bugzilla.suse.com/show_bug.cgi?id=1207900#c14 --- Comment #14 from Takashi Iwai <tiwai(a)suse.com> --- /etc/zypp/zypp.conf should be with simply a few more entries like: multiversion.kernels = latest,latest-1,latest-2,latest-3,running It's for allowing to install more kernel packages than default (= 2). Then just download kernel-default.rpm from the OBS download URL, e.g. http://download.opensuse.org/repositories/home:/tiwai:/kernel:/6.0/standard… And install it directly with zypper install --oldpackage option, e.g. % zypper in --oldpackage kernel-default-6.0.12-1.1.ga6c4f4e.x86_64.rpm Boot with that kernel and retest. If the test is done and the kernel is no longer needed, uninstall it % zypper rm kernel-default-6.0.12-1.1.ga6c4f4e -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1207900] Thinkpad P16 Gen 1 freezes when put into Dockingstation
by bugzilla_noreply＠suse.com 17 Mar '23

17 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1207900 https://bugzilla.suse.com/show_bug.cgi?id=1207900#c13 --- Comment #13 from Michael Vetter <mvetter(a)suse.com> --- (In reply to Takashi Iwai from comment #5) > Then could you check a few old kernels to see whether it's a recent > regression or not? Some kernel packages are found in my OBS repo like OBS > home:tiwai:kernel:6.0, home:tiwai:kernel:5.19, ... What's the proper way to do this? I assume: 1) Edit /etc/zypp/zypp.conf like: `multiversion.kernels = latest,latest-1,6.2.1-1-default,running` since 6.2.1 is the only Kernel that works more or less for me and I should keep a working one. 2) `zypper ar -f obs://home:tiwai:kernel:6.0 kernel6`, `zypper dup --from kernel6` to get the kernel-default (etc) packages from there? 3) reboot and select that kernel -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1209296] Missing backlight control on Dell Vostro 3700
by bugzilla_noreply＠suse.com 17 Mar '23

17 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1209296 https://bugzilla.suse.com/show_bug.cgi?id=1209296#c13 --- Comment #13 from Takashi Iwai <tiwai(a)suse.com> --- OK, thanks. Now I posted a regression report to the upstream: https://lore.kernel.org/r/87wn3f8zj7.wl-tiwai@suse.de -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205149] %kernel_module_package_buildreqs needs to require suse-kernel-rpm-scriptlets
by bugzilla_noreply＠suse.com 16 Mar '23

16 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1205149 https://bugzilla.suse.com/show_bug.cgi?id=1205149#c61 --- Comment #61 from Maintenance Automation <maint-coord+maintenance-robot(a)suse.de> --- SUSE-SU-2023:0779-1: An update that solves 21 vulnerabilities and has 12 fixes can now be installed. Category: security (important) Bug References: 1186449, 1203331, 1203332, 1203693, 1204502, 1204760, 1205149, 1206351, 1206677, 1206784, 1207034, 1207051, 1207134, 1207186, 1207237, 1207497, 1207508, 1207560, 1207773, 1207795, 1207845, 1207875, 1207878, 1208212, 1208599, 1208700, 1208741, 1208776, 1208816, 1208837, 1208845, 1208971, 1209008 CVE References: CVE-2022-3606, CVE-2022-36280, CVE-2022-38096, CVE-2022-47929, CVE-2023-0045, CVE-2023-0179, CVE-2023-0266, CVE-2023-0590, CVE-2023-0597, CVE-2023-1076, CVE-2023-1095, CVE-2023-1118, CVE-2023-1195, CVE-2023-22995, CVE-2023-22998, CVE-2023-23000, CVE-2023-23004, CVE-2023-23006, CVE-2023-23559, CVE-2023-25012, CVE-2023-26545 Sources used: SUSE Real Time Module 15-SP3 (src): kernel-syms-rt-5.3.18-150300.121.1, kernel-source-rt-5.3.18-150300.121.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 1209334] usb 2-2: BOGUS control dir, pipe 80000480 doesn't match bRequestType 40
by bugzilla_noreply＠suse.com 16 Mar '23

16 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1209334 https://bugzilla.suse.com/show_bug.cgi?id=1209334#c2 Oliver Neukum <oneukum(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS Flags|needinfo?(oneukum(a)suse.com) | --- Comment #2 from Oliver Neukum <oneukum(a)suse.com> --- (In reply to Jiri Slaby from comment #1) > Maybe something for Oliver: should that usb_rcvctrlpipe() be *snd* instead? Yes, it should. I have submitted a patch upstream. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1209334] usb 2-2: BOGUS control dir, pipe 80000480 doesn't match bRequestType 40
by bugzilla_noreply＠suse.com 16 Mar '23

16 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1209334 https://bugzilla.suse.com/show_bug.cgi?id=1209334#c1 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jslaby(a)suse.com, | |oneukum(a)suse.com Flags| |needinfo?(oneukum(a)suse.com) --- Comment #1 from Jiri Slaby <jslaby(a)suse.com> --- Maybe something for Oliver: should that usb_rcvctrlpipe() be *snd* instead? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1209155] New: Terminal width on hi res laptop is 1/3 what it should be
by bugzilla_noreply＠suse.com 15 Mar '23

15 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1209155 Bug ID: 1209155 Summary: Terminal width on hi res laptop is 1/3 what it should be Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: erbenton(a)comcast.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- During boot and when using Ctrl-Alt Fx to get to a terminal the lines wrap at about one third of the screen width. Plus the text is impossibly tiny, I'm guessing at about 4 point or so. My laptop is hi res ASUS Zenbook at 3840 x 2160. Most things on my hi res laptop (on the desktop) are handled very badly as far as size goes, but this is the most egregious. It seems nothing is really ready for this hi-res although I have not tried gnome or wayland. openSUSE Tumbleweed 20230225 (x86_64) on kernel 6.1.12-1-default -- You are receiving this mail because: You are the assignee for the bug.

1 9

[Bug 1209334] New: usb 2-2: BOGUS control dir, pipe 80000480 doesn't match bRequestType 40
by bugzilla_noreply＠suse.com 15 Mar '23

15 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1209334 Bug ID: 1209334 Summary: usb 2-2: BOGUS control dir, pipe 80000480 doesn't match bRequestType 40 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: kkaempf(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- When plugging an "EasyCAP" video grabber into the USB port, I get a kernel crash > lsusb Bus 002 Device 004: ID 1b71:3002 Fushicai USBTV007 Video Grabber [EasyCAP] > uname -a Linux yoga 6.2.2-1-default #1 SMP PREEMPT_DYNAMIC Thu Mar 9 06:06:13 UTC 2023 (44ca817) x86_64 x86_64 x86_64 GNU/Linux Crash: M�r 15 17:53:52 yoga kernel: ------------[ cut here ]------------ M�r 15 17:53:52 yoga kernel: usb 2-2: BOGUS control dir, pipe 80000480 doesn't match bRequestType 40 M�r 15 17:53:52 yoga kernel: WARNING: CPU: 6 PID: 6022 at drivers/usb/core/urb.c:411 usb_submit_urb+0x5bc/0x6a0 [usbcore] M�r 15 17:53:52 yoga kernel: Modules linked in: usbtv ccm rfcomm snd_seq_dummy snd_hrtimer snd_seq snd_seq_device nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_ct nft_chain_nat af_packet nf_tables ebtable_nat ebtable_broute ip6table_nat ip6table_mangle ip6table_raw ip6table_security iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 iptable_mangle iptable_raw iptable_security ip_set nfnetlink ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter bpfilter cmac algif_hash qrtr algif_skcipher af_alg bnep snd_sof_amd_rembrandt snd_sof_amd_renoir snd_sof_amd_acp snd_sof_pci rtw89_8852ae snd_sof_xtensa_dsp rtw89_8852a snd_sof snd_hda_codec_realtek rtw89_pci snd_hda_codec_generic snd_sof_utils ledtrig_audio snd_soc_core btusb rtw89_core snd_hda_codec_hdmi btrtl uvcvideo btbcm intel_rapl_msr snd_hda_intel btintel videobuf2_vmalloc intel_rapl_common videobuf2_memops snd_intel_dspcfg btmtk nls_iso8859_1 M�r 15 17:53:52 yoga kernel: snd_intel_sdw_acpi snd_compress videobuf2_v4l2 mac80211 snd_pcm_dmaengine nls_cp437 bluetooth videodev hid_sensor_als edac_mce_amd snd_pci_ps hid_sensor_trigger snd_hda_codec snd_rpl_pci_acp6x hid_sensor_iio_common industrialio_triggered_buffer kvm_amd snd_acp_pci vfat fat libarc4 kfifo_buf snd_hda_core xfs ecdh_generic videobuf2_common snd_pci_acp6x kvm snd_pci_acp5x industrialio snd_hwdep mc irqbypass wmi_bmof cfg80211 snd_pcm snd_timer ideapad_laptop snd_rn_pci_acp3x snd_acp_config pcspkr sparse_keymap efi_pstore snd snd_soc_acpi platform_profile soundcore k10temp i2c_piix4 snd_pci_acp3x rfkill tiny_power_button acpi_cpufreq button ac joydev nfsd auth_rpcgss nfs_acl lockd grace sunrpc fuse configfs dmi_sysfs ip_tables x_tables usbhid amdgpu drm_ttm_helper ttm crct10dif_pclmul crc32_pclmul polyval_clmulni polyval_generic iommu_v2 gf128mul drm_buddy gpu_sched drm_display_helper hid_sensor_custom xhci_pci xhci_pci_renesas ghash_clmulni_intel xhci_hcd M�r 15 17:53:52 yoga kernel: hid_sensor_hub ucsi_acpi cec nvme video typec_ucsi sha512_ssse3 hid_multitouch hid_generic aesni_intel crypto_simd usbcore cryptd roles nvme_core ccp rc_core typec sp5100_tco battery i2c_hid_acpi wmi i2c_hid serio_raw btrfs blake2b_generic xor raid6_pq libcrc32c crc32c_intel sg br_netfilter bridge stp llc dm_multipath dm_mod scsi_dh_rdac scsi_dh_emc scsi_dh_alua msr efivarfs M�r 15 17:53:52 yoga kernel: CPU: 6 PID: 6022 Comm: vlc Not tainted 6.2.2-1-default #1 openSUSE Tumbleweed d96a51c172c54c631a431306c0e33b18c609861e M�r 15 17:53:52 yoga kernel: Hardware name: LENOVO 82MS/LNVNB161216, BIOS GZCN31WW 09/06/2022 M�r 15 17:53:52 yoga kernel: RIP: 0010:usb_submit_urb+0x5bc/0x6a0 [usbcore] M�r 15 17:53:52 yoga kernel: Code: 48 89 54 24 18 44 89 44 24 0c e8 cf d8 01 ee 44 8b 44 24 0c 89 d9 48 8b 54 24 18 48 89 c6 48 c7 c7 f0 28 a7 c0 e8 8c 41 3b ee <0f> 0b 4c 8b 5c 24 10 e9 d6 fc ff ff 80 3d 2d b8 03 00 00 0f 84 97 M�r 15 17:53:52 yoga kernel: RSP: 0018:ffffc13103a3fb70 EFLAGS: 00010282 M�r 15 17:53:52 yoga kernel: RAX: 0000000000000000 RBX: 0000000080000480 RCX: 0000000000000027 M�r 15 17:53:52 yoga kernel: RDX: ffff9bc61ffa24c8 RSI: 0000000000000001 RDI: ffff9bc61ffa24c0 M�r 15 17:53:52 yoga kernel: RBP: 0000000000000001 R08: 0000000000000000 R09: ffffc13103a3fa28 M�r 15 17:53:52 yoga kernel: R10: 0000000000000003 R11: ffff9bc62e2c36a8 R12: ffff9bc3a810c800 M�r 15 17:53:52 yoga kernel: R13: ffff9bc39091b200 R14: 0000000000000000 R15: ffff9bc4b5a6b920 M�r 15 17:53:52 yoga kernel: FS: 00007f458442e6c0(0000) GS:ffff9bc61ff80000(0000) knlGS:0000000000000000 M�r 15 17:53:52 yoga kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 M�r 15 17:53:52 yoga kernel: CR2: 00007f458403d6b0 CR3: 00000001511da000 CR4: 0000000000750ee0 M�r 15 17:53:52 yoga kernel: PKRU: 55555554 M�r 15 17:53:52 yoga kernel: Call Trace: M�r 15 17:53:52 yoga kernel: <TASK> M�r 15 17:53:52 yoga kernel: usb_start_wait_urb+0x65/0x160 [usbcore cda7e5b80fc3b65f4686797e94206150c1e36d1b] M�r 15 17:53:52 yoga kernel: usb_control_msg+0xe3/0x150 [usbcore cda7e5b80fc3b65f4686797e94206150c1e36d1b] M�r 15 17:53:52 yoga kernel: usbtv_set_regs+0x5e/0x80 [usbtv 0eedda8de1e0455659d90ac752b1532709e8ce78] M�r 15 17:53:52 yoga kernel: usbtv_s_input+0x5c/0x60 [usbtv 0eedda8de1e0455659d90ac752b1532709e8ce78] M�r 15 17:53:52 yoga kernel: __video_do_ioctl+0x19c/0x3e0 [videodev 32832d43872282873540ce4201d574e88c8821db] M�r 15 17:53:52 yoga kernel: ? __check_object_size+0x4a/0x200 M�r 15 17:53:52 yoga kernel: video_usercopy+0x327/0x710 [videodev 32832d43872282873540ce4201d574e88c8821db] M�r 15 17:53:52 yoga kernel: ? __pfx___video_do_ioctl+0x10/0x10 [videodev 32832d43872282873540ce4201d574e88c8821db] M�r 15 17:53:52 yoga kernel: v4l2_ioctl+0x49/0x50 [videodev 32832d43872282873540ce4201d574e88c8821db] M�r 15 17:53:52 yoga kernel: __x64_sys_ioctl+0x90/0xd0 M�r 15 17:53:52 yoga kernel: do_syscall_64+0x5b/0x80 M�r 15 17:53:52 yoga kernel: ? __x64_sys_ioctl+0xa8/0xd0 M�r 15 17:53:52 yoga kernel: ? syscall_exit_to_user_mode+0x17/0x40 M�r 15 17:53:52 yoga kernel: ? do_syscall_64+0x67/0x80 M�r 15 17:53:52 yoga kernel: ? do_syscall_64+0x67/0x80 M�r 15 17:53:52 yoga kernel: ? exit_to_user_mode_prepare+0x166/0x1f0 M�r 15 17:53:52 yoga kernel: ? syscall_exit_to_user_mode+0x17/0x40 M�r 15 17:53:52 yoga kernel: ? do_syscall_64+0x67/0x80 M�r 15 17:53:52 yoga kernel: ? exc_page_fault+0x66/0x150 M�r 15 17:53:52 yoga kernel: entry_SYSCALL_64_after_hwframe+0x72/0xdc M�r 15 17:53:52 yoga kernel: RIP: 0033:0x7f45b8391b4d M�r 15 17:53:52 yoga kernel: Code: 5d c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 8b 82 0d 00 f7 d8 64 89 01 48 M�r 15 17:53:52 yoga kernel: RSP: 002b:00007f458442cd78 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 M�r 15 17:53:52 yoga kernel: RAX: ffffffffffffffda RBX: 00000000c0045627 RCX: 00007f45b8391b4d M�r 15 17:53:52 yoga kernel: RDX: 00007f458442d2e0 RSI: 00000000c0045627 RDI: 000000000000001f M�r 15 17:53:52 yoga kernel: RBP: 0000000000000000 R08: 0000000000000001 R09: 00000000c0045627 M�r 15 17:53:52 yoga kernel: R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 M�r 15 17:53:52 yoga kernel: R13: 00000000c0045627 R14: 00007f458442d2e0 R15: 000000000000001f M�r 15 17:53:52 yoga kernel: </TASK> M�r 15 17:53:52 yoga kernel: ---[ end trace 0000000000000000 ]--- -- You are receiving this mail because: You are the assignee for the bug.

1 0

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

15 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1202353 http://bugzilla.opensuse.org/show_bug.cgi?id=1202353#c38 --- Comment #38 from OBSbugzilla Bot <bwiedemann+obsbugzillabot(a)suse.com> --- This is an autogenerated message for OBS integration: This bug (1202353) was mentioned in https://build.opensuse.org/request/show/1072149 Factory / suse-module-tools -- You are receiving this mail because: You are the assignee for the bug.

1 0

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

15 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1207948 https://bugzilla.suse.com/show_bug.cgi?id=1207948#c36 --- Comment #36 from Richard Weinberger <richard(a)nod.at> --- (In reply to Takashi Iwai from comment #34) > And, a simple workaround for this is just to unload and reload at > hibernation/resume. You can put a script like below to > /usr/lib/systemd/system-sleep directory (with exec bit set). I can confirm that this workaround works here too. Thanks! -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1209294] New Thinkpad T14s GPU reset/crash with openSUSE Tumbleweed
by bugzilla_noreply＠suse.com 15 Mar '23

15 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1209294 http://bugzilla.opensuse.org/show_bug.cgi?id=1209294#c3 --- Comment #3 from Takashi Iwai <tiwai(a)suse.com> --- You can report it the upstream beforehand, too. But certainly they'll ask for testing with a cutting-edge kernel, even newer than 6.3-rc :) -- You are receiving this mail because: You are the assignee for the bug.

1 0