mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Rodrigo Siqueira Jordao <Rodrigo.Siqueira@amd.com>
To: Alex Deucher <alexdeucher@gmail.com>,
	Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com>,
	"Mahfooz, Hamza" <Hamza.Mahfooz@amd.com>
Cc: Linux regressions mailing list <regressions@lists.linux.dev>,
	"Deucher, Alexander" <alexander.deucher@amd.com>,
	amd-gfx list <amd-gfx@lists.freedesktop.org>,
	dri-devel <dri-devel@lists.freedesktop.org>,
	Linux List Kernel Mailing <linux-kernel@vger.kernel.org>
Subject: Re: 6.10/bisected/regression - commits bc87d666c05 and 6d4279cb99ac cause appearing green flashing bar on top of screen on Radeon 6900XT and 120Hz
Date: Sat, 29 Jun 2024 10:46:45 -0600	[thread overview]
Message-ID: <ea465a40-f673-42b1-8b1c-a2efb20cd562@amd.com> (raw)
In-Reply-To: <CADnq5_PDSkr4hOHJmb1J30UC0a7sXsm5-TPkEmjzffMK_A+7ug@mail.gmail.com>



On 6/28/24 9:19 AM, Alex Deucher wrote:
> On Fri, Jun 21, 2024 at 6:45 AM Mikhail Gavrilov
> <mikhail.v.gavrilov@gmail.com> wrote:
>>
>> On Fri, Jun 21, 2024 at 12:56 PM Linux regression tracking (Thorsten
>> Leemhuis) <regressions@leemhuis.info> wrote:
>>> Hmmm, I might have missed something, but it looks like nothing happened
>>> here since then. What's the status? Is the issue still happening?
>>
>> Yes. Tested on e5b3efbe1ab1.
>>
>> I spotted that the problem disappears after forcing the TV to sleep
>> (activate screensaver <Super> + <L>) and then wake it up by pressing
>> any button and entering a password.
>> Hope this information can't help figure out how to fix it.
> 
> @Siqueira, Rodrigo @Mahfooz, Hamza any ideas?
> 
> Alex

Hi Mikhail,

I'm trying to reproduce this issue, but until now, I've been unable to 
reproduce it. I tried some different scenarios with the following 
components:

1. Displays: I tried with one and two displays
  - 4k@120 - DP && 4k@60 - HDMI
  - 4k@244 Oled - DP
2. GPU: 7900XTX
3. OSes:
  - ArchLinux kernel 6.9.6, Gnome (no changes)
  - Ubuntu 22 + latest amd-staging-drm-next + latest firmware, Gnome

Anyway, I could not reproduce the issue with the below components. I may 
be missing something that will trigger this bug; in this sense, could 
you describe the following:
- The display resolution and refresh rate.
- Are you able to reproduce this issue with DP and HDMI?
- Could you provide the firmware information: sudo cat 
/sys/kernel/debug/dri/0/amdgpu_firmware_info

Also, could you conduct the below tests and report the results:

- Test 1: Just revert the fallback patch (drm/amd/display: Add fallback 
configuration for set DRR in DCN10) and see if it solves the issue.
- Test 2: Try the latest amd-staging-drm-next 
(https://gitlab.freedesktop.org/agd5f/linux) and see if the issue is gone.
- Test 3: In the kernel that you see the issue, could you install the 
latest firmware and see if it fix the issue? Check: 
https://gitlab.freedesktop.org/drm/firmware P.S.: Don't forget to update 
the initramfs or something similar in your system.

Thanks
Siqueira

  reply	other threads:[~2024-06-29 16:46 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-26 14:06 Mikhail Gavrilov
2024-06-05 12:04 ` Mikhail Gavrilov
2024-06-07 12:29   ` Linux regression tracking (Thorsten Leemhuis)
2024-06-10 22:05     ` Mikhail Gavrilov
2024-06-07 13:39 ` Alex Deucher
2024-06-09 21:19   ` Mikhail Gavrilov
2024-06-21  7:56     ` Linux regression tracking (Thorsten Leemhuis)
2024-06-21 10:44       ` Mikhail Gavrilov
2024-06-28 15:19         ` Alex Deucher
2024-06-29 16:46           ` Rodrigo Siqueira Jordao [this message]
2024-06-29 23:18             ` Mikhail Gavrilov
2024-07-09 12:41               ` Linux regression tracking (Thorsten Leemhuis)
2024-07-09 14:57                 ` Rodrigo Siqueira Jordao
2024-07-09 14:48               ` Rodrigo Siqueira Jordao
2024-07-10  7:01                 ` Mikhail Gavrilov
2024-07-10  7:03                   ` Mikhail Gavrilov
2024-07-16 17:10                     ` Alex Deucher
2024-07-17  6:28                       ` Mikhail Gavrilov
2024-07-23  4:24                       ` Eric Biggers

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ea465a40-f673-42b1-8b1c-a2efb20cd562@amd.com \
    --to=rodrigo.siqueira@amd.com \
    --cc=Hamza.Mahfooz@amd.com \
    --cc=alexander.deucher@amd.com \
    --cc=alexdeucher@gmail.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikhail.v.gavrilov@gmail.com \
    --cc=regressions@lists.linux.dev \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®