From: Diederik de Haas <didi.debian@cknow.org>
To: Eric Valette <eric.valette@free.fr>,
Salvatore Bonaccorso <carnil@debian.org>,
Thorsten Leemhuis <regressions@leemhuis.info>,
Sasha Levin <sashal@kernel.org>
Cc: "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>,
dod@debian.org
Subject: Re: Bug#1005005: Regression from 3c196f056666 ("drm/amdgpu: always reset the asic in suspend (v2)") on suspend?
Date: Mon, 21 Mar 2022 20:09:19 +0100 [thread overview]
Message-ID: <4421935.LvFx2qVVIh@prancing-pony> (raw)
In-Reply-To: <3873010.MHq7AAxBmi@ylum>
[-- Attachment #1: Type: text/plain, Size: 902 bytes --]
On maandag 21 maart 2022 19:49:56 CET 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
It was included in 5.15.22, but the newest 5.15 kernel uploaded to Debian was
5.15.15, so their is no fixed 5.15 in Debian.
It was also included in 5.16.8 and the earlier version in Debian which had
that commit was 5.16.10 (uploaded 2022-02-18 to Unstable). Current version in
Unstable is 5.16.14. Testing/Bookworm now had 5.16.12.
In Experimental, on 2022-02-12, 5.17-rc3 was uploaded.
HTH,
Diederik
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
WARNING: multiple messages have this Message-ID
From: Diederik de Haas <didi.debian@cknow.org>
To: Eric Valette <eric.valette@free.fr>,
Salvatore Bonaccorso <carnil@debian.org>,
Thorsten Leemhuis <regressions@leemhuis.info>,
Sasha Levin <sashal@kernel.org>
Cc: "David Airlie" <airlied@linux.ie>,
"Pan, Xinhui" <Xinhui.Pan@amd.com>,
LKML <linux-kernel@vger.kernel.org>,
"Maling list - DRI developers" <dri-devel@lists.freedesktop.org>,
"Alex Deucher" <alexdeucher@gmail.com>,
"Luben Tuikov" <luben.tuikov@amd.com>,
"amd-gfx list" <amd-gfx@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>,
dod@debian.org
Subject: Re: Bug#1005005: Regression from 3c196f056666 ("drm/amdgpu: always reset the asic in suspend (v2)") on suspend?
Date: Mon, 21 Mar 2022 20:09:19 +0100 [thread overview]
Message-ID: <4421935.LvFx2qVVIh@prancing-pony> (raw)
In-Reply-To: <3873010.MHq7AAxBmi@ylum>
[-- Attachment #1: Type: text/plain, Size: 902 bytes --]
On maandag 21 maart 2022 19:49:56 CET 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
It was included in 5.15.22, but the newest 5.15 kernel uploaded to Debian was
5.15.15, so their is no fixed 5.15 in Debian.
It was also included in 5.16.8 and the earlier version in Debian which had
that commit was 5.16.10 (uploaded 2022-02-18 to Unstable). Current version in
Unstable is 5.16.14. Testing/Bookworm now had 5.16.12.
In Experimental, on 2022-02-12, 5.17-rc3 was uploaded.
HTH,
Diederik
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
WARNING: multiple messages have this Message-ID
From: Diederik de Haas <didi.debian@cknow.org>
To: Eric Valette <eric.valette@free.fr>,
Salvatore Bonaccorso <carnil@debian.org>,
Thorsten Leemhuis <regressions@leemhuis.info>,
Sasha Levin <sashal@kernel.org>
Cc: "David Airlie" <airlied@linux.ie>,
"Pan, Xinhui" <Xinhui.Pan@amd.com>,
LKML <linux-kernel@vger.kernel.org>,
"Maling list - DRI developers" <dri-devel@lists.freedesktop.org>,
"Luben Tuikov" <luben.tuikov@amd.com>,
"amd-gfx list" <amd-gfx@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>,
dod@debian.org
Subject: Re: Bug#1005005: Regression from 3c196f056666 ("drm/amdgpu: always reset the asic in suspend (v2)") on suspend?
Date: Mon, 21 Mar 2022 20:09:19 +0100 [thread overview]
Message-ID: <4421935.LvFx2qVVIh@prancing-pony> (raw)
In-Reply-To: <3873010.MHq7AAxBmi@ylum>
[-- Attachment #1: Type: text/plain, Size: 902 bytes --]
On maandag 21 maart 2022 19:49:56 CET 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
It was included in 5.15.22, but the newest 5.15 kernel uploaded to Debian was
5.15.15, so their is no fixed 5.15 in Debian.
It was also included in 5.16.8 and the earlier version in Debian which had
that commit was 5.16.10 (uploaded 2022-02-18 to Unstable). Current version in
Unstable is 5.16.14. Testing/Bookworm now had 5.16.12.
In Experimental, on 2022-02-12, 5.17-rc3 was uploaded.
HTH,
Diederik
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2022-03-21 19:11 UTC|newest]
Thread overview: 36+ 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
2022-03-21 19:00 ` Thorsten Leemhuis
2022-03-21 19:00 ` Thorsten Leemhuis
2022-03-21 19:09 ` Diederik de Haas [this message]
2022-03-21 19:09 ` Bug#1005005: " 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
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=4421935.LvFx2qVVIh@prancing-pony \
--to=didi.debian@cknow.org \
--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=regressions@leemhuis.info \
--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.