[Bug 1183424] New: Screen corrupted after update to kernel 5.11.2
http://bugzilla.opensuse.org/show_bug.cgi?id=1183424 Bug ID: 1183424 Summary: Screen corrupted after update to kernel 5.11.2 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-bugs@opensuse.org Reporter: jebaer@t-online.de QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Created attachment 847119 --> http://bugzilla.opensuse.org/attachment.cgi?id=847119&action=edit photography of corrupted screen APU: Ryzen 5 Pro 4650G, mainboard: Gigabyte Aorus Pro (B550 chipset), no further grapcics-card Machine runs fine with kernel 5.16.2, after update to kernel 5.11.2 it still boots up and seems to work, grub-menue is still shown as usual, but from then on the screen is corrupted, hardly readable, as well with kde as lxde as cl. Strange thing is that screenshots made in this state via kde-tool show a normal desktop. Similar issue is described for ubuntu in: https://gitlab.freedesktop.org/drm/amd/-/issues/1514 -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1183424 Jens Behrje <jebaer@t-online.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P2 - High -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1183424 http://bugzilla.opensuse.org/show_bug.cgi?id=1183424#c1 --- Comment #1 from Jens Behrje <jebaer@t-online.de> --- Forgot to mention: there's never been any other display attached to the computer nor an additional graphics card, but in /var/log/ besides Xorg.0.log I find a Xorg.1.log file which refers to kernel 5.11.2 -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1183424 http://bugzilla.opensuse.org/show_bug.cgi?id=1183424#c2 Takashi Iwai <tiwai@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jebaer@t-online.de, | |tiwai@suse.com Flags| |needinfo?(jebaer@t-online.d | |e) --- Comment #2 from Takashi Iwai <tiwai@suse.com> --- Could you check whether the recent upstream (5.12-rc) still shows the same problem? You can install the kernel from OBS Kernel:HEAD repo. Also, the kernel from the latest drm-tip tree is found in OBS home:tiwai:kernel:drm-tip repo (it's kernel-vanilll package). If both still show the same bug, try to boot 5.11.x and 5.10.x kernels with drm.debug=0x1e option, and get the kernel logs (dmesg outputs). Attach those to Bugzilla. -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1183424 http://bugzilla.opensuse.org/show_bug.cgi?id=1183424#c3 --- Comment #3 from Jens Behrje <jebaer@t-online.de> --- Created attachment 847159 --> http://bugzilla.opensuse.org/attachment.cgi?id=847159&action=edit output from dmesg for kernel 5.10 Here is the outpot from dmesg for 5.10 kernel booted with parameter drm.debug=0x1e -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1183424 http://bugzilla.opensuse.org/show_bug.cgi?id=1183424#c4 --- Comment #4 from Jens Behrje <jebaer@t-online.de> --- Created attachment 847160 --> http://bugzilla.opensuse.org/attachment.cgi?id=847160&action=edit output from dmesg for kernel 5.11 Hopefully this is the output from dmesg for kernel 5.11 booted with parameter drm.debug=0x1e. Not quite easy while more guessing than seeing (and not really knowing) what I was doing ;-) -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1183424 http://bugzilla.opensuse.org/show_bug.cgi?id=1183424#c5 --- Comment #5 from Takashi Iwai <tiwai@suse.com> --- Thanks for the logs. But it seems that drm.debug=0x1e boot option wasn't passed properly. This is usually done by editing the option in GRUB menu (entering by 'e', and boot with 'ctrl-X'). Without the drm debug option, the only significant error message wrt amdgpu is amdgpu 0000:08:00.0: amdgpu: Unsupported power profile mode 0 on RENOIR But, this one isn't always a fatal error and this was even downgraded to a debug message in the recent upstream code. -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1183424 http://bugzilla.opensuse.org/show_bug.cgi?id=1183424#c6 --- Comment #6 from Jens Behrje <jebaer@t-online.de> --- Grub-menue offered to boot with F10 and I did so. Maybe a mistake? Unfortunately I'm quite unexperienced in these things, so please wait amd give me one more try. Btw: Thank you very much for your support! -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1183424 http://bugzilla.opensuse.org/show_bug.cgi?id=1183424#c7 --- Comment #7 from Jens Behrje <jebaer@t-online.de> --- Created attachment 847165 --> http://bugzilla.opensuse.org/attachment.cgi?id=847165&action=edit 2nd output from dmesg for kernel 5.10 Here we go again: second try dmesg for kernel 5.10 with boot-parameter drm.debug=01xe -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1183424 http://bugzilla.opensuse.org/show_bug.cgi?id=1183424#c8 --- Comment #8 from Jens Behrje <jebaer@t-online.de> --- Created attachment 847167 --> http://bugzilla.opensuse.org/attachment.cgi?id=847167&action=edit 2nd try dmesg output for kernel 5.11 And the second try for kernel 5.11 -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1183424 http://bugzilla.opensuse.org/show_bug.cgi?id=1183424#c9 --- Comment #9 from Jens Behrje <jebaer@t-online.de> --- Created attachment 847173 --> http://bugzilla.opensuse.org/attachment.cgi?id=847173&action=edit dmesg output for kernel 5.10 Shame on me, I'm so sorry! Tapping around on a qwertz-keyboard where qwerty-layout was needed :-( Here is my third approach delivering the desired output from dmesg for kernel 5.10 booted with parameter drm.debug=0x1e -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1183424 http://bugzilla.opensuse.org/show_bug.cgi?id=1183424#c10 --- Comment #10 from Jens Behrje <jebaer@t-online.de> --- Created attachment 847174 --> http://bugzilla.opensuse.org/attachment.cgi?id=847174&action=edit dmesg output for kernel 5.11 Third approach for dmesg output from kernel 5.11 booted with parameter drm.debug=0x1e -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1183424 http://bugzilla.opensuse.org/show_bug.cgi?id=1183424#c11 --- Comment #11 from Jens Behrje <jebaer@t-online.de> --- Tonight there was a giant update for tumbleweed (nearly 3 GB) including a step from kernel 5.11.2 to 5.11.4, which (in my case) took hours to download, but it didn't change anything with my odd screen. -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1183424 http://bugzilla.opensuse.org/show_bug.cgi?id=1183424#c12 --- Comment #12 from Jens Behrje <jebaer@t-online.de> --- Meanwhile I had the chance to try kernel-default-5.12.rc2-1.1 from OBS Kernel:HEAD repo and kernel-vanilla-5.12.rc2-7.1 from home:tiwai:kernel:drm-tip repo but none of them changed the situation on my screen. Please let me lead your attention once more to https://gitlab.freedesktop.org/drm/amd/-/issues/1514 where a solution seems to be found for the issue reported there. Of course it's a different distro and I have no clue, whether situations are comparable. -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1183424 http://bugzilla.opensuse.org/show_bug.cgi?id=1183424#c13 --- Comment #13 from Takashi Iwai <tiwai@suse.com> --- Thanks, that's helpful. Now I'm building 5.11.x kernel with the two upstream fix patches in OBS home:tiwai:bsc1183424 repo. Please give it a try later. -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1183424 http://bugzilla.opensuse.org/show_bug.cgi?id=1183424#c14 --- Comment #14 from Jens Behrje <jebaer@t-online.de> --- Wonderful! kernel-default-5.11.6-1.1 from home:tiwai:bsc1183424 seems to work fine :-) Takashi Iwai, you are my hero ;-) -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1183424 http://bugzilla.opensuse.org/show_bug.cgi?id=1183424#c15 Takashi Iwai <tiwai@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(jebaer@t-online.d | |e) | --- Comment #15 from Takashi Iwai <tiwai@suse.com> --- Thanks for confirmation. Then I'll push those two fixes forward to Tumbleweed kernel (stable git branch). Also it'd be appreciated if you comment in the upstream bug tracker, too. -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1183424 http://bugzilla.opensuse.org/show_bug.cgi?id=1183424#c16 --- Comment #16 from Jens Behrje <jebaer@t-online.de> --- Done. Thanks for your support and patience! -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1183424 http://bugzilla.opensuse.org/show_bug.cgi?id=1183424#c17 Takashi Iwai <tiwai@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #17 from Takashi Iwai <tiwai@suse.com> --- Thanks. The fixes were pushed to stable git branch, so it'll reach to TW kernel some time later. You can keep using my patched kernel until then. Let's close the bug. -- You are receiving this mail because: You are the assignee for the bug.
participants (1)
-
bugzilla_noreply＠suse.com