https://bugzilla.suse.com/show_bug.cgi?id=1183872 https://bugzilla.suse.com/show_bug.cgi?id=1183872#c12 --- Comment #12 from Takashi Iwai <tiwai@suse.com> --- (In reply to Imnotgivingmy nametoamachine from comment #11)

(In reply to Takashi Iwai from comment #10)

...

It's being rebuilt now. I didn't notice that the automatic update stopped working...

Thank you very much Takashi! I tested with (drm-tip) kernel-vanilla-5.12.rc4-2.1.ga3c6ee1 but sadly the bug was still present.

I then went ahead and tested with kernel-vanilla-5.12.rc5-1.1.g5fe2d5c because I notice it was available too, you know just to make sure the bug was indeed still present and all... But the bug doesn't happen with 5.12.rc5-vanilla...

Just what the fuck? Was the bug really fixed in exactly the week I reported the bug but without finding an useful log or call trace? And why the bug didn't happened on ubuntu? To be honest despite the bug looking like it's fixed on 5.12.rc5 it's now more annoying not knowing why or how it was fixed haha

I'm legit going to read all the commits between 5.12.rc4 and 5.12.rc5

That aside what should the status of this bug be? Is it "Resolved" as soon as there is a patch coming up in a future stable version or it's Resolved until that patch finally reaches a stable kernel in opensuse?

You need to really make sure that it's fixed in 5.12-rc5 code itself. For example, 5.12-rc5 kernel you've tested also contains the kernel configuration change to make CONFIG_SND_HDA_INTEL_HDMI_SILENT_STREAM=n. This might be the cause, too. And, if that's the case, you could work around in other kernels by passing snd_hda_codec_hdmi.enable_silent_stream=0 boot option, too. -- You are receiving this mail because: You are the assignee for the bug.