All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thorsten Leemhuis <regressions@leemhuis.info>
To: dod@debian.org, Eric Valette <eric.valette@free.fr>,
	Salvatore Bonaccorso <carnil@debian.org>
Cc: "Sasha Levin" <sashal@kernel.org>,
	"David Airlie" <airlied@linux.ie>,
	"Pan, Xinhui" <Xinhui.Pan@amd.com>,
	LKML <linux-kernel@vger.kernel.org>,
	"amd-gfx list" <amd-gfx@lists.freedesktop.org>,
	"Luben Tuikov" <luben.tuikov@amd.com>,
	"Maling list - DRI developers" <dri-devel@lists.freedesktop.org>,
	"Alex Deucher" <alexander.deucher@amd.com>,
	1005005@bugs.debian.org, "Evan Quan" <evan.quan@amd.com>,
	"Christian König" <christian.koenig@amd.com>,
	"Alex Deucher" <alexdeucher@gmail.com>
Subject: Re: Regression from 3c196f056666 ("drm/amdgpu: always reset the asic in suspend (v2)") on suspend?
Date: Mon, 21 Mar 2022 20:00:28 +0100	[thread overview]
Message-ID: <b3c39447-c02a-a021-8a4f-499aa962980c@leemhuis.info> (raw)
In-Reply-To: <3873010.MHq7AAxBmi@ylum>

On 21.03.22 19:49, Dominique Dumont wrote:
> On Monday, 21 March 2022 09:57:59 CET Thorsten Leemhuis wrote:
>> Dominique/Salvatore/Eric, what's the status of this regression?
>> According to the debian bug tracker the problem is solved with 5.16 and
>> 5.17, but was 5.15 ever fixed?
> 
> I don't think so.
> 
> On kernel side, the commit fixing this issue is
> e55a3aea418269266d84f426b3bd70794d3389c8 . 
> 
> According to the logs of [1] , this commit landed in v5.17-rc3
> 
> HTH
> 
> [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git

And from there it among others got backported to 5.15.22:

https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-5.15.y&id=8a15ac1786c92dce6ecbeb4e4c237f5f80c2c703

https://lwn.net/Articles/884107/

Another indicator that Eric's problem is something else.

Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)

P.S.: As the Linux kernel's regression tracker I'm getting a lot of
reports on my table. I can only look briefly into most of them and lack
knowledge about most of the areas they concern. I thus unfortunately
will sometimes get things wrong or miss something important. I hope
that's not the case here; if you think it is, don't hesitate to tell me
in a public reply, it's in everyone's interest to set the public record
straight.



WARNING: multiple messages have this Message-ID
From: Thorsten Leemhuis <regressions@leemhuis.info>
To: dod@debian.org, Eric Valette <eric.valette@free.fr>,
	Salvatore Bonaccorso <carnil@debian.org>
Cc: "Sasha Levin" <sashal@kernel.org>,
	"David Airlie" <airlied@linux.ie>,
	"Pan, Xinhui" <Xinhui.Pan@amd.com>,
	LKML <linux-kernel@vger.kernel.org>,
	"amd-gfx list" <amd-gfx@lists.freedesktop.org>,
	"Luben Tuikov" <luben.tuikov@amd.com>,
	"Maling list - DRI developers" <dri-devel@lists.freedesktop.org>,
	"Alex Deucher" <alexander.deucher@amd.com>,
	1005005@bugs.debian.org, "Evan Quan" <evan.quan@amd.com>,
	"Christian König" <christian.koenig@amd.com>
Subject: Re: Regression from 3c196f056666 ("drm/amdgpu: always reset the asic in suspend (v2)") on suspend?
Date: Mon, 21 Mar 2022 20:00:28 +0100	[thread overview]
Message-ID: <b3c39447-c02a-a021-8a4f-499aa962980c@leemhuis.info> (raw)
In-Reply-To: <3873010.MHq7AAxBmi@ylum>

On 21.03.22 19:49, Dominique Dumont wrote:
> On Monday, 21 March 2022 09:57:59 CET Thorsten Leemhuis wrote:
>> Dominique/Salvatore/Eric, what's the status of this regression?
>> According to the debian bug tracker the problem is solved with 5.16 and
>> 5.17, but was 5.15 ever fixed?
> 
> I don't think so.
> 
> On kernel side, the commit fixing this issue is
> e55a3aea418269266d84f426b3bd70794d3389c8 . 
> 
> According to the logs of [1] , this commit landed in v5.17-rc3
> 
> HTH
> 
> [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git

And from there it among others got backported to 5.15.22:

https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-5.15.y&id=8a15ac1786c92dce6ecbeb4e4c237f5f80c2c703

https://lwn.net/Articles/884107/

Another indicator that Eric's problem is something else.

Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)

P.S.: As the Linux kernel's regression tracker I'm getting a lot of
reports on my table. I can only look briefly into most of them and lack
knowledge about most of the areas they concern. I thus unfortunately
will sometimes get things wrong or miss something important. I hope
that's not the case here; if you think it is, don't hesitate to tell me
in a public reply, it's in everyone's interest to set the public record
straight.



WARNING: multiple messages have this Message-ID
From: Thorsten Leemhuis <regressions@leemhuis.info>
To: dod@debian.org, Eric Valette <eric.valette@free.fr>,
	Salvatore Bonaccorso <carnil@debian.org>
Cc: "Sasha Levin" <sashal@kernel.org>,
	"David Airlie" <airlied@linux.ie>,
	"Pan, Xinhui" <Xinhui.Pan@amd.com>,
	LKML <linux-kernel@vger.kernel.org>,
	"amd-gfx list" <amd-gfx@lists.freedesktop.org>,
	"Alex Deucher" <alexdeucher@gmail.com>,
	"Luben Tuikov" <luben.tuikov@amd.com>,
	"Maling list - DRI developers" <dri-devel@lists.freedesktop.org>,
	"Alex Deucher" <alexander.deucher@amd.com>,
	1005005@bugs.debian.org, "Evan Quan" <evan.quan@amd.com>,
	"Christian König" <christian.koenig@amd.com>
Subject: Re: Regression from 3c196f056666 ("drm/amdgpu: always reset the asic in suspend (v2)") on suspend?
Date: Mon, 21 Mar 2022 20:00:28 +0100	[thread overview]
Message-ID: <b3c39447-c02a-a021-8a4f-499aa962980c@leemhuis.info> (raw)
In-Reply-To: <3873010.MHq7AAxBmi@ylum>

On 21.03.22 19:49, Dominique Dumont wrote:
> On Monday, 21 March 2022 09:57:59 CET Thorsten Leemhuis wrote:
>> Dominique/Salvatore/Eric, what's the status of this regression?
>> According to the debian bug tracker the problem is solved with 5.16 and
>> 5.17, but was 5.15 ever fixed?
> 
> I don't think so.
> 
> On kernel side, the commit fixing this issue is
> e55a3aea418269266d84f426b3bd70794d3389c8 . 
> 
> According to the logs of [1] , this commit landed in v5.17-rc3
> 
> HTH
> 
> [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git

And from there it among others got backported to 5.15.22:

https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-5.15.y&id=8a15ac1786c92dce6ecbeb4e4c237f5f80c2c703

https://lwn.net/Articles/884107/

Another indicator that Eric's problem is something else.

Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)

P.S.: As the Linux kernel's regression tracker I'm getting a lot of
reports on my table. I can only look briefly into most of them and lack
knowledge about most of the areas they concern. I thus unfortunately
will sometimes get things wrong or miss something important. I hope
that's not the case here; if you think it is, don't hesitate to tell me
in a public reply, it's in everyone's interest to set the public record
straight.



  reply	other threads:[~2022-03-21 19:00 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-12 18:23 Regression from 3c196f056666 ("drm/amdgpu: always reset the asic in suspend (v2)") on suspend? Salvatore Bonaccorso
2022-02-12 18:23 ` Salvatore Bonaccorso
2022-02-12 18:23 ` Salvatore Bonaccorso
2022-02-14 12:17 ` Thorsten Leemhuis
2022-02-14 12:17   ` Thorsten Leemhuis
2022-02-14 12:17   ` Thorsten Leemhuis
2022-02-14 21:52 ` Alex Deucher
2022-02-14 21:52   ` Alex Deucher
2022-02-20 15:48   ` Dominique Dumont
2022-02-20 15:48     ` Dominique Dumont
2022-02-20 18:03     ` Eric Valette
2022-02-20 18:03       ` Eric Valette
2022-02-21 14:16       ` Alex Deucher
2022-02-21 14:16         ` Alex Deucher
2022-03-21  8:57         ` Thorsten Leemhuis
2022-03-21  8:57           ` Thorsten Leemhuis
2022-03-21  8:57           ` Thorsten Leemhuis
2022-03-21 12:07           ` Éric Valette
2022-03-21 12:07             ` Éric Valette
2022-03-21 12:07             ` Éric Valette
2022-03-21 14:30             ` Thorsten Leemhuis
2022-03-21 14:30               ` Thorsten Leemhuis
2022-03-21 14:30               ` Thorsten Leemhuis
2022-03-24 14:39               ` Regression from 3c196f056666 ("drm/amdgpu: always reset the asic in suspend (v2)") on suspend? #forregzbot Thorsten Leemhuis
2022-03-21 18:49           ` Regression from 3c196f056666 ("drm/amdgpu: always reset the asic in suspend (v2)") on suspend? Dominique Dumont
2022-03-21 18:49             ` Dominique Dumont
2022-03-21 18:49             ` Dominique Dumont
2022-03-21 19:00             ` Thorsten Leemhuis [this message]
2022-03-21 19:00               ` Thorsten Leemhuis
2022-03-21 19:00               ` Thorsten Leemhuis
2022-03-21 19:09             ` Bug#1005005: " Diederik de Haas
2022-03-21 19:09               ` Diederik de Haas
2022-03-21 19:09               ` Diederik de Haas
2022-02-15  3:07 ` Quan, Evan
2022-02-15  3:07   ` Quan, Evan
2022-02-15  3:07   ` Quan, Evan
2022-02-24 12:22 Éric Valette
2022-02-24 12:22 ` Éric Valette

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=b3c39447-c02a-a021-8a4f-499aa962980c@leemhuis.info \
    --to=regressions@leemhuis.info \
    --cc=1005005@bugs.debian.org \
    --cc=Xinhui.Pan@amd.com \
    --cc=airlied@linux.ie \
    --cc=alexander.deucher@amd.com \
    --cc=alexdeucher@gmail.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=carnil@debian.org \
    --cc=christian.koenig@amd.com \
    --cc=dod@debian.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=eric.valette@free.fr \
    --cc=evan.quan@amd.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luben.tuikov@amd.com \
    --cc=sashal@kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.