https://bugzilla.suse.com/show_bug.cgi?id=1221734 https://bugzilla.suse.com/show_bug.cgi?id=1221734#c1 Takashi Iwai changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |owinebar@gmail.com, | |tiwai@suse.com Flags| |needinfo?(owinebar@gmail.co | |m) --- Comment #1 from Takashi Iwai --- You should be still able to use the old Leap 15.4 kernel on your Leap 15.5 system. Could you try to install the old Leap 15.4 kernel and identify which kernel version started showing the problem? The Leap 15.4 (update) packages should be available at http://download.opensuse.org/update/leap/15.4/sle/ And, if you figure out the working / non-working kernel versions, please give the dmesg outputs from both (with debugging options) to compare. -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1221734 https://bugzilla.suse.com/show_bug.cgi?id=1221734#c3 Lynn Winebarger changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(owinebar@gmail.co | |m) | --- Comment #3 from Lynn Winebarger --- Created attachment 873705 --> https://bugzilla.suse.com/attachment.cgi?id=873705&action=edit /var/log/messages with first kenerl version exhibiting rtl8723be fail after waking from suspend, 5.14.21-150400-24.74 /var/log/messages with last kernel not exhibiting an rtl8723 "Init MAC failed" message after invoking "systemctl shutdown" and then waking the laptop up. Note left module parameters at defaults, other than debug_level and debug_mask. -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1221734 https://bugzilla.suse.com/show_bug.cgi?id=1221734#c5 --- Comment #5 from Takashi Iwai --- Thanks! Interestingly, through a quick glance, there is no obvious changes in the relevant code (either in Realtek WiFi driver or wireless net code). Is the problem reproducible reliably, and can switching the kernel between those versions confirm the first bad kernel? If yes, you can try the following: - Rename the first broken kernel modules: cd /lib/modules/5.14.21-150400.24.74-default/ mv kernel kernel.dist - Copy the last good working kernel modules to there: cp -a /lib/modules/5.14.21-150400.24.69-default/kernel /lib/modules/5.14.21-150400.24.74-default/ depmod -a 5.14.21-150400.24.74-default dracut -f --kver 5.14.21-150400.24.74-default Then retest 5.14.21-150400.24.74-default. There can be some hiccups, but the only interesting thing is the test of this bug. If the bug still appears after this, it means that the code built in the kernel got some bugs. OTOH, if this "fixes" the issue on *-74, it means some of the copied modules received the fix. Then you can go back to the original modules, and try to copy some of them, and identify which module are affected. -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1221734 https://bugzilla.suse.com/show_bug.cgi?id=1221734#c7 Takashi Iwai changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #7 from Takashi Iwai --- OK, then let's close. If any new fact appears, feel free to reopen. Thanks. -- You are receiving this mail because: You are on the CC list for the bug.