June 2022 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1200258] Laptop dual monitor setup / internal LCD "lost" after loggin off KDE
by bugzilla_noreply＠suse.com 08 Jun '22

08 Jun '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1200258 http://bugzilla.opensuse.org/show_bug.cgi?id=1200258#c7 --- Comment #7 from Takashi Iwai <tiwai(a)suse.com> --- Is this a regression from the earlier releases? If yes, which version worked? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1200258] Laptop dual monitor setup / internal LCD "lost" after loggin off KDE
by bugzilla_noreply＠suse.com 08 Jun '22

08 Jun '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1200258 http://bugzilla.opensuse.org/show_bug.cgi?id=1200258#c6 --- Comment #6 from robert spitzenpfeil <rs.opensuse(a)spitzenpfeil.org> --- Created attachment 859475 --> http://bugzilla.opensuse.org/attachment.cgi?id=859475&action=edit xrandr -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1200258] Laptop dual monitor setup / internal LCD "lost" after loggin off KDE
by bugzilla_noreply＠suse.com 08 Jun '22

08 Jun '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1200258 http://bugzilla.opensuse.org/show_bug.cgi?id=1200258#c5 --- Comment #5 from robert spitzenpfeil <rs.opensuse(a)spitzenpfeil.org> --- The output of xrandr always looks the same. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1200259] Kernel Panic in bfq_bic_update_cgroup while fstrim after Update to Kernel 5.3.18-150300.59.68.1
by bugzilla_noreply＠suse.com 07 Jun '22

07 Jun '22

https://bugzilla.suse.com/show_bug.cgi?id=1200259 Jan Kara <jack(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P2 - High Assignee|kernel-bugs(a)opensuse.org |jack(a)suse.com -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1200259] Kernel Panic in bfq_bic_update_cgroup while fstrim after Update to Kernel 5.3.18-150300.59.68.1
by bugzilla_noreply＠suse.com 07 Jun '22

07 Jun '22

https://bugzilla.suse.com/show_bug.cgi?id=1200259 https://bugzilla.suse.com/show_bug.cgi?id=1200259#c6 --- Comment #6 from Jan Kara <jack(a)suse.com> --- Yeah, I've got the report from upstream as well. The good news is that last week, I've debugged it and created a fix which is now in Linus' tree. I'll push it to SLE15-SP3 (from where it propagates to Leap 15.3) tomorrow. I'm sorry for the inconvenience and thanks for the report! -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1200259] New: Kernel Panic after Update to 5.3.18-150300.59.68.1
by bugzilla_noreply＠suse.com 07 Jun '22

07 Jun '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1200259 Bug ID: 1200259 Summary: Kernel Panic after Update to 5.3.18-150300.59.68.1 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: x86-64 OS: openSUSE Leap 15.3 Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: fgruener(a)web.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 859446 --> http://bugzilla.opensuse.org/attachment.cgi?id=859446&action=edit dmesg from crash>log After upgrading the default kernel ("kernel-default") provided via regular update from the official OpenSuse Leap 15.3 (Upstream SLES) repository from 5.3.18-150300.59.63.1-default to the newest Leap Standard Kernel 5.3.18-150300.59.68.1-default, I encountered already several Kernel Panics. This could happened within an one day period 2 to 3 times, but also last time it took 2 to 3 days, until it reoccurs. An possibility to reproduce the issue step by step, I have not yet found, only be using my PC. crash>log unveiled a null pointer execption. Please see dmesg attachted. Enabling KDUMP unveiled the following backtrace: crash> bt PID: 23800 TASK: ffff8d1b32ae8000 CPU: 0 COMMAND: "fstrim" #0 [ffffb2134512f790] machine_kexec at ffffffffa7e6fe01 #1 [ffffb2134512f7e8] __crash_kexec at ffffffffa7f595fd #2 [ffffb2134512f8b0] crash_kexec at ffffffffa7f5a4bd #3 [ffffb2134512f8c8] oops_end at ffffffffa7e36d3f #4 [ffffb2134512f8e8] no_context at ffffffffa7e82bbf #5 [ffffb2134512f950] do_page_fault at ffffffffa7e83e40 #6 [ffffb2134512f980] page_fault at ffffffffa880130e [exception RIP: bfq_bio_bfqg+37] RIP: ffffffffa8277b55 RSP: ffffb2134512fa30 RFLAGS: 00010002 RAX: 000000000000001f RBX: 0000000000000000 RCX: 0000000000000000 RDX: ffff8d1b8f614e00 RSI: ffff8d1b7fd47200 RDI: ffff8d1b7fd47200 RBP: ffff8d1887ff0800 R8: ffff8d199aeb54b8 R9: ffff8d199aeb5488 R10: 0000000000000000 R11: ffff8d1ab7742e00 R12: ffff8d17c7744640 R13: ffff8d1887ff0800 R14: ffff8d1b7fd47200 R15: ffff8d1b8d91a894 ORIG_RAX: ffffffffffffffff CS: 0010 SS: 0018 #7 [ffffb2134512fa40] bfq_bic_update_cgroup at ffffffffa8277e78 #8 [ffffb2134512fa78] bfq_bio_merge at ffffffffa826ee9f #9 [ffffb2134512fad0] blk_mq_submit_bio at ffffffffa8248769 #10 [ffffb2134512fb58] submit_bio_noacct at ffffffffa823c343 #11 [ffffb2134512fbe8] submit_bio at ffffffffa823c3db #12 [ffffb2134512fc38] submit_bio_wait at ffffffffa8234cc4 #13 [ffffb2134512fc78] blkdev_issue_discard at ffffffffa8243d20 #14 [ffffb2134512fd08] ext4_trim_fs at ffffffffc079a7ea [ext4] #15 [ffffb2134512fe10] ext4_ioctl at ffffffffc0790ef6 [ext4] #16 [ffffb2134512fef8] ksys_ioctl at ffffffffa80fadc2 #17 [ffffb2134512ff30] __x64_sys_ioctl at ffffffffa80fadf6 #18 [ffffb2134512ff38] do_syscall_64 at ffffffffa7e0538b #19 [ffffb2134512ff50] entry_SYSCALL_64_after_hwframe at ffffffffa880008c RIP: 00007f73ecd54c47 RSP: 00007ffc4e041c08 RFLAGS: 00000246 RAX: ffffffffffffffda RBX: 000055764b87c310 RCX: 00007f73ecd54c47 RDX: 00007ffc4e041c20 RSI: 00000000c0185879 RDI: 0000000000000003 RBP: 000055764b8788c0 R8: 000055764b87c310 R9: 0000000000000002 R10: 0000000000000000 R11: 0000000000000246 R12: 00007ffc4e041d00 R13: 000055764b8788c0 R14: 0000000000000003 R15: 000055764b87a890 ORIG_RAX: 0000000000000010 CS: 0033 SS: 002b According to the logfiles of the changed items of the last patch, there was a patch added to address: - bfq: Update cgroup information before merging bio (bsc#1197926). Searching in the internet "bfq_bic_update_cgroup+0x28/0x1b0 core dump opensuse" I also found: https://lkml.kernel.org/linux-block/20220330124255.24581-2-jack@suse.cz/T/ There at least in the same stack changes have been done in the same area. @@ -2457,10 +2457,17 @@ static bool bfq_bio_merge(struct request_queue *q, struct bio *bio, + bfq_bic_update_cgroup(bic, bio); Maybe bio is not fully initialized? Maybe my refernece is wrong, but it is remarkable, that at least the kernel post contains a change in the same stack. As this is my first post, I am not quite sure what other information might be helpfull here. Please ask, if you will need further information. Thanks already for taking this issue into account. And for your openSuse. Best regards cyp -- You are receiving this mail because: You are the assignee for the bug.

1 6

[Bug 1200232] New: GpuWatchdog segfault 5.18.1-1-default
by bugzilla_noreply＠suse.com 07 Jun '22

07 Jun '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1200232 Bug ID: 1200232 Summary: GpuWatchdog segfault 5.18.1-1-default Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: sndanailov(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- While playing "The Talos Principle" randomly the game freezes and my guess is, this might have something to do with it. I wasn't sure if it's an issue with Nvidia or the kernel, but it was logged as "kernel:". My desktop environment is: Xfce 4.16 My GPU is: NVIDIA GeForce GTX 760 Installed Nvidia packages: kernel-firmware-nvidia libnvidia-egl-wayland1 nvidia-computeG05 nvidia-computeG05-32bit nvidia-gfxG05-kmp-default nvidia-glG05 nvidia-glG05-32bit x11-video-nvidiaG05 x11-video-nvidiaG05-32bit Logged segfault: Jun 04 15:53:18 PC kernel: GpuWatchdog[2480]: segfault at 0 ip 00007f5d1285a31f sp 00007f5d07c793a0 error 6 in libcef.so[7f5d0e61f000+6f5e000] Jun 04 15:53:18 PC kernel: Code: 89 de e8 74 30 8e fe 80 7d cf 00 79 09 48 8b 7d b8 e8 e5 d5 d1 02 41 8b 84 24 e0 00 00 00 89 45 b8 48 8d 7d b8 e8 e1 51 dc fb <c7> 04 25 00 00 00 00 37 13 00 00 48 83 c4 38 5b 41 5c 41 5d 41 5e -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1200236] New: Bluetooth on Intel AX210 not working with Kernel 5.14
by bugzilla_noreply＠suse.com 07 Jun '22

07 Jun '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1200236 Bug ID: 1200236 Summary: Bluetooth on Intel AX210 not working with Kernel 5.14 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: severin.stampler(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Bluetooth on Intel AX210 is not working with the default kernel and firmware (5.14.21, openSUSE Leap 15.4). I tried several other newer kernel versions, all have the same problem. dmesg output shows "Failed to load Intel firmware ..." (see below), but firmware is installed. Cold or warm reboot doesn't seem to make a difference (like suggested here: https://bugzilla.kernel.org/show_bug.cgi?id=213829) dmesg | grep -i bluetooth [ 4.233063] Bluetooth: Core ver 2.22 [ 4.233084] NET: Registered PF_BLUETOOTH protocol family [ 4.233085] Bluetooth: HCI device and connection manager initialized [ 4.233089] Bluetooth: HCI socket layer initialized [ 4.233091] Bluetooth: L2CAP socket layer initialized [ 4.233093] Bluetooth: SCO socket layer initialized [ 4.239235] Bluetooth: hci0: Device revision is 0 [ 4.239237] Bluetooth: hci0: Secure boot is enabled [ 4.239238] Bluetooth: hci0: OTP lock is enabled [ 4.239238] Bluetooth: hci0: API lock is enabled [ 4.239238] Bluetooth: hci0: Debug lock is disabled [ 4.239239] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [ 4.239240] Bluetooth: hci0: Bootloader timestamp 2019.40 buildtype 1 build 38 [ 4.239257] Bluetooth: hci0: Failed to load Intel firmware file intel/ibt-0041-0041.sfi (-2) [ 4.240279] Bluetooth: hci0: Failed to read MSFT supported features (-56) [ 4.330250] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 4.330251] Bluetooth: BNEP filters: protocol multicast [ 4.330253] Bluetooth: BNEP socket layer initialized [ 5.221888] thinkpad_acpi: rfkill switch tpacpi_bluetooth_sw: radio is unblocked lsusb | grep -i blue Bus 003 Device 006: ID 8087:0032 Intel Corp. AX210 Bluetooth -- You are receiving this mail because: You are the assignee for the bug.

1 13

[Bug 1199958] No more i8k in dell_smm_hwmon in kernel 5.18
by bugzilla_noreply＠suse.com 07 Jun '22

07 Jun '22

https://bugzilla.suse.com/show_bug.cgi?id=1199958 https://bugzilla.suse.com/show_bug.cgi?id=1199958#c4 --- Comment #4 from Takashi Iwai <tiwai(a)suse.com> --- I see why this was disabled in our config. The type was changed from tristate to bool, so now this has to be CONFIG_I8K=y instead of CONFIG_I8K=m. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1200232] GpuWatchdog segfault 5.18.1-1-default
by bugzilla_noreply＠suse.com 07 Jun '22

07 Jun '22

https://bugzilla.suse.com/show_bug.cgi?id=1200232 https://bugzilla.suse.com/show_bug.cgi?id=1200232#c2 --- Comment #2 from Stefan Dirsch <sndirsch(a)suse.com> --- Haven't heard about such an issue yet. Not sure where GpuWatchdog is coming from. Never heard before either ... -- You are receiving this mail because: You are the assignee for the bug.

1 0