Bug 218481 - Kernel 6.7 on Zephyrus shattered video on primary display
Summary: Kernel 6.7 on Zephyrus shattered video on primary display
Status: NEW
Alias: None
Product: Linux
Classification: Unclassified
Component: Kernel (show other bugs)
Hardware: AMD Linux
: P3 blocking
Assignee: Virtual assignee for kernel bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-02-11 15:13 UTC by Alexei
Modified: 2024-02-25 09:49 UTC (History)
1 user (show)

See Also:
Kernel Version:
Subsystem:
Regression: No
Bisected commit-id:


Attachments
dmesg (100.65 KB, text/plain)
2024-02-11 15:13 UTC, Alexei
Details

Description Alexei 2024-02-11 15:13:03 UTC
Created attachment 305855 [details]
dmesg

Updating Linux kernel to 6.7.0 brings an issue with build in display. 

Product: ROG Zephyrus GA502IV
Video: VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [Radeon RX Vega 6 (Ryzen 4000/5000 Mobile Series)] (rev c6)

How to reproduce:
- update to kernel 6.7.0
- reboot

How to fix:
- install 6.6.X kernel
- reboot

Tested kernels that work:
- Fedora 6.6.X
- ArchLinux mainline kernel 6.6.X
- G14 kernel 6.6.X
- LQX kernel 6.6.X
- XanMod kernel 6.6.X

Updating any of the mentioned kernel to 6.7 does reproduce this bug.
Also found the same issue on Fedora forum
https://discussion.fedoraproject.org/t/update-resulting-in-corrupted-or-garbled-video-on-zephyrus-display/103388/3

And in Discord's g14 bug report
https://discord.com/channels/725125934759411753/1194725185807450213

Unfortunately I can't find an option to add a photo. But fedora link has an example how it looks like.
Comment 1 The Linux kernel's regression tracker (Thorsten Leemhuis) 2024-02-12 05:57:22 UTC
(In reply to Alexei from comment #0)
>
> Product: ROG Zephyrus GA502IV
> Video: VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI]
> Renoir [Radeon RX Vega 6 (Ryzen 4000/5000 Mobile Series)] (rev c6)

Those systems also contain a Nvidia GPU, hence allow me to ask: do you use any out-of-tree drivers from Nvidia (as it seems to be the case for the user that opened the Fedora post you pointed to).

If that's the case you are on your own. If not, you want to report the problem here: https://gitlab.freedesktop.org/drm/amd/-/issues ; in that case please drop a link here.
Comment 2 Alexei 2024-02-12 08:33:10 UTC
(In reply to The Linux kernel's regression tracker (Thorsten Leemhuis) from comment #1)
> (In reply to Alexei from comment #0)
> >
> > Product: ROG Zephyrus GA502IV
> > Video: VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI]
> > Renoir [Radeon RX Vega 6 (Ryzen 4000/5000 Mobile Series)] (rev c6)
> 
> Those systems also contain a Nvidia GPU, hence allow me to ask: do you use
> any out-of-tree drivers from Nvidia (as it seems to be the case for the user
> that opened the Fedora post you pointed to).
> 
> If that's the case you are on your own. If not, you want to report the
> problem here: https://gitlab.freedesktop.org/drm/amd/-/issues ; in that case
> please drop a link here.

Thanks for the reply. 
Yes, my system has nvidia discrete GPU. But to make sure that this is not Nvidia related bug, I disabled nvidia driver and than even uninstalled dkms modules and packages. 

I was struggling where to open this bug, here or in drm/amd issues, decided to open here because it doesn't look like admgpu bug, I switch the kernel to reproduce the issue, I don't change admgpu driver's version. Are you sure I need to move it to drm/adm?
Comment 3 The Linux kernel's regression tracker (Thorsten Leemhuis) 2024-02-12 08:45:38 UTC
(In reply to Alexei from comment #2)
> I switch the kernel to
> reproduce the issue, I don't change admgpu driver's version

You did not change mesa's amdgpu driver, but if you switched the kernel, then you are running a different "version" of the kernel's amdgpu driver :-) 

That being said: https://gitlab.freedesktop.org/drm/amd/-/issues might nevertheless turn out to be the the wrong place; but given the current state of things it's the best place to report this.

Note You need to log in before you can comment on or make changes to this bug.