January 2023 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1206758] xhci_hcd periodically not ready on resume
by bugzilla_noreply＠suse.com 09 Jan '23

09 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206758 https://bugzilla.suse.com/show_bug.cgi?id=1206758#c17 --- Comment #17 from Pablo Sanchez <pablo(a)blueoakdb.com> --- Hi, With 6.1.3-1, the problem is not as bad: As before, if I connect my phone before resuming, the laptop won't recognize the device. With 6.1.3-1, if I reconnect it when the laptop is up, it'll be recognized. Previously, in this state, the only solution was a reboot. We're making progress! :) -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1180649] amdgpu: [drm] Failed to updateMST allocation table forpipe idx:1
by bugzilla_noreply＠suse.com 09 Jan '23

09 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1180649 Alexander Bergmann <abergmann(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(abergmann(a)suse.co | |m) | -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1190256] Keyboard not working after cold-boot on ASUS Zenbook 14 UM425UA with Tumbleweed 20210904
by bugzilla_noreply＠suse.com 09 Jan '23

09 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1190256 https://bugzilla.suse.com/show_bug.cgi?id=1190256#c89 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution|--- |FIXED --- Comment #89 from Jiri Slaby <jslaby(a)suse.com> --- As per comment 88. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206925] WiFi does not work after update
by bugzilla_noreply＠suse.com 09 Jan '23

09 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1206925 http://bugzilla.opensuse.org/show_bug.cgi?id=1206925#c2 --- Comment #2 from Wojciech Rosiak <opensuse(a)wolli.com> --- This issue seems to be fixed in the latest kernel 6.1.3-1.1. It work fine :-) -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206848] khugepaged at 100% CPU
by bugzilla_noreply＠suse.com 09 Jan '23

09 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206848 https://bugzilla.suse.com/show_bug.cgi?id=1206848#c9 --- Comment #9 from Martin Koller <kollix(a)aon.at> --- Created attachment 863934 --> https://bugzilla.suse.com/attachment.cgi?id=863934&action=edit trace-cmd logfile as requested. The 100% cpu was here less than a minute -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206943] New: mkinitrd with self-build nonmodular kernel, building initrd for kernel-default kernel, fails to include mdraid modules
by bugzilla_noreply＠suse.com 09 Jan '23

09 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206943 Bug ID: 1206943 Summary: mkinitrd with self-build nonmodular kernel, building initrd for kernel-default kernel, fails to include mdraid modules 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: patrick.schaaf(a)yalwa.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I'm happy to see this report closed right away as exotic, but thought I'd report anyway... I'm used to run tumbleweed, for quite a few years and very happily, on production machines (host + kvm virtual machines), using my own, almost-nomodular kernel builds. On the host side, that includes initrds, built the normal way with mkinitrd + dracut and no customization needed. Good. Now I ran into an issue when, for a different reported issue, I got asked to try + reproduce with actual tumbleweed kernel-default. So I installed that, mkinitrd ran normally - and it failed to boot properly. The system (host) where that happened, uses RAID1 (md raid) disks (and LVM on top) for boot + root. What I found is that mkinitrd, apparently because the currently running kernel (my own) has MD drivers built in (not loaded as modules), fails to include the drivers/md modules into the initrd. If I change "instmods '=drivers/md'" to "hostonly='' instmods '=drivers/md'", in 90mdraid/module-setup.sh, I get it to include the modules + get a working boot. If I revert that change + rebuild the initrd again while the suse kernel-default is running (with raid1.ko in lsmod), again I get a working initrd with the modules included. Hope this report helps someone who may stumble across the same issue, even if no change results from it. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1206380] intel pseudoraid C220 fails after upgrade to 6.0.12
by bugzilla_noreply＠suse.com 09 Jan '23

09 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206380 https://bugzilla.suse.com/show_bug.cgi?id=1206380#c3 --- Comment #3 from Dmitry Markov <werwolf131313(a)gmail.com> --- (In reply to Takashi Iwai from comment #2) > Could you verify whether the problem persists with 6.1.x TW kernel? it was ugly for me to do this, but this situation was the last straw for my patience and I transferred all my services to another server and put this one in the closet. I want to ask for forgiveness. I promise that in the next few days I will find another disk for testing and check the situation with the new kernel on this disk and unsubscribe here. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206848] New: khugepaged at 100% CPU
by bugzilla_noreply＠suse.com 08 Jan '23

08 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1206848 Bug ID: 1206848 Summary: khugepaged at 100% CPU Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: 64bit OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: kollix(a)aon.at QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Since recent update to 6.1.0-1-default I often see khugepaged staying at 100% CPU for a long time (some minutes). Operating System: openSUSE Tumbleweed 20221225 KDE Plasma Version: 5.26.4 KDE Frameworks Version: 5.101.0 Qt Version: 5.15.7 Kernel Version: 6.1.0-1-default (64-bit) Graphics Platform: X11 Processors: 4 �� Intel�� Core�� i5-6300U CPU @ 2.40GHz Memory: 15,5 GiB of RAM Graphics Processor: Mesa Intel�� HD Graphics 520 Manufacturer: HP Product Name: HP ProBook 650 G2 -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1206848] khugepaged at 100% CPU
by bugzilla_noreply＠suse.com 08 Jan '23

08 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206848 https://bugzilla.suse.com/show_bug.cgi?id=1206848#c7 --- Comment #7 from Vlastimil Babka <vbabka(a)suse.com> --- Besides the compaction isolated counter, the migrate failure counter grows at same high speed. Yet the compaction scanner counters move much slowly, which would suggest isolations and migrations being retried excessively without scanning, but I don't see how that's possible. Tracepoints could indeed help. Please install trace-cmd and run (while the problem is occuring) as root: trace-cmd record -e compaction:* -e migrate:* (wait for e.g. a minute, check khugepaged keeps using 100% cpu during the time, and then stop by ctrl+c) this should produce a file trace.dat, please upload (e.g. compressed). Thanks! -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206408] New: Kernel panic after upgrading from to kernel 6.0.10 (or 6.0.12) from 6.0.8
by bugzilla_noreply＠suse.com 08 Jan '23

08 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1206408 Bug ID: 1206408 Summary: Kernel panic after upgrading from to kernel 6.0.10 (or 6.0.12) from 6.0.8 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: rainer.klute(a)gmx.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- After upgrading from kernel 6.0.8 to 6.0.10, the system no longer boots. Instead, it stops relatively early in the boot process with the shift lock LED blinking. No error message is shown on the screen. The last message it shows is regarding the IBM trackpoint device on my Lenovo Thinkpad P50 notebook. Same behaviour with kernel 6.0.12. Luckily, I can still boot the 6.0.8 kernel, but I am stuck with that on this particular machine. -- You are receiving this mail because: You are the assignee for the bug.

1 13