amd-gfx.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Thorsten Leemhuis <regressions@leemhuis.info>
To: Paul Menzel <pmenzel@molgen.mpg.de>, regressions@lists.linux.dev
Cc: Mario Limonciello <mario.limonciello@amd.com>,
	amd-gfx@lists.freedesktop.org
Subject: Re: Fwd: Re: amd | ASUS ROG Strix G513QY fails to resume from suspend [regression] (#2008)
Date: Tue, 10 May 2022 12:33:00 +0200	[thread overview]
Message-ID: <2192e546-cac7-f802-2297-3461a1cf8e03@leemhuis.info> (raw)
In-Reply-To: <66e1d78c-bf27-80b4-9804-6c9f3a8c5547@molgen.mpg.de>

On 10.05.22 10:37, Paul Menzel wrote:
> Dear Linux regressions folks,
> 
> A user reported a regression [1], which also trickled down to the stable
> series, for example between 5.15.13 and 5.15.14.
> 
> [1]: https://gitlab.freedesktop.org/drm/amd/-/issues/2008

Many thx for forwarding. I'll add it to the tracking to ensure it's not
forgotten:

#regzbot introduced: 887f75cfd0da44c19dd
#regzbot from: spin83
#regzbot title: drm: amdgpu: ASUS ROG Strix G513QY fails to resume from
suspend
#regzbot link: https://gitlab.freedesktop.org/drm/amd/-/issues/2008

Maybe the culprit is actually daf8de0874ab5b74b38a38726fdd3d, the report
is not clear on that, I just picked the newest the reporter mentioned
for now.

See the ticket for details, there were a few replies already. According
to Paul the problems trickled down to the stable series, for example
between 5.15.13 and 5.15.14.

Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
-- 
P.S.: As the Linux kernel's regression tracker I deal with a lot of
reports and sometimes miss something important when writing mails like
this. If that's the case here, don't hesitate to tell me in a public
reply, it's in everyone's interest to set the public record straight.

P.P.S.: This isn't a regression? This issue or a fix for it are already
discussed somewhere else? It was fixed already? You want to clarify when
the regression started to happen? Or point out I got the title or
something else totally wrong? Then just reply -- ideally with also
telling regzbot about it, as explained here:
https://linux-regtracking.leemhuis.info/tracked-regression/

  reply	other threads:[~2022-05-10 12:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <note_1375796@gitlab.freedesktop.org>
2022-05-10  8:37 ` Fwd: Re: amd | ASUS ROG Strix G513QY fails to resume from suspend [regression] (#2008) Paul Menzel
2022-05-10 10:33   ` Thorsten Leemhuis [this message]
2022-05-10 14:20     ` Limonciello, Mario

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=2192e546-cac7-f802-2297-3461a1cf8e03@leemhuis.info \
    --to=regressions@leemhuis.info \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=mario.limonciello@amd.com \
    --cc=pmenzel@molgen.mpg.de \
    --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;
as well as URLs for NNTP newsgroup(s).