Bug#1005005: Regression from 3c196f056666 ("drm/amdgpu: always reset the asic in suspend (v2)") on suspend?

2022-03-21 Thread Diederik de Haas
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

Bug#1005005: Regression from 3c196f056666 ("drm/amdgpu: always reset the asic in suspend (v2)") on suspend?

2022-03-21 Thread Thorsten Leemhuis
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 th

Bug#1005005: Regression from 3c196f056666 ("drm/amdgpu: always reset the asic in suspend (v2)") on suspend?

2022-03-21 Thread Dominique Dumont
Hi 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

Bug#913310: nfs-common: Systemd does not correctly read /etc/default/nfs-common

2022-03-21 Thread Marco Gaiarin
Mandi! Ben Hutchings In chel di` si favelave... > What is the actual problem you are trying to solve? digging harder on my email folders... in october 2018 i was trying to make NFSv4 work in a Samba/AD/Kerberos environment. Probably after that i've found a way to circumvent the need, probably

Bug#1005005: Regression from 3c196f056666 ("drm/amdgpu: always reset the asic in suspend (v2)") on suspend?

2022-03-21 Thread Thorsten Leemhuis
On 21.03.22 13:07, Éric Valette wrote: > My problem has never been fixed. > > The proposed patch has been applied to 5.15. I do not remerber which version > 28 maybe. > > I still have à RIP in pm_suspend. Did not test the Last two 15 versions. > > I can leave with 5.10 est using own compiled ker

Bug#1005005: Regression from 3c196f056666 ("drm/amdgpu: always reset the asic in suspend (v2)") on suspend?

2022-03-21 Thread Éric Valette
My problem has never been fixed. The proposed patch has been applied to 5.15. I do not remerber which version 28 maybe. I still have à RIP in pm_suspend. Did not test the Last two 15 versions. I can leave with 5.10 est using own compiled kernels. Thanks for asking. 21 mars 2022 09:58:01 Thorst

linux-signed-i386_5.10.103+1~bpo10+1_source.changes ACCEPTED into buster-backports->backports-policy, buster-backports

2022-03-21 Thread Debian FTP Masters
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 08 Mar 2022 14:48:28 +0100 Source: linux-signed-i386 Architecture: source Version: 5.10.103+1~bpo10+1 Distribution: buster-backports Urgency: high Maintainer: Debian Kernel Team Changed-By: Ben Hutchings Changes

linux-signed-amd64_5.10.103+1~bpo10+1_source.changes ACCEPTED into buster-backports->backports-policy, buster-backports

2022-03-21 Thread Debian FTP Masters
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 08 Mar 2022 14:48:28 +0100 Source: linux-signed-amd64 Architecture: source Version: 5.10.103+1~bpo10+1 Distribution: buster-backports Urgency: high Maintainer: Debian Kernel Team Changed-By: Ben Hutchings Change

linux-signed-arm64_5.10.103+1~bpo10+1_source.changes ACCEPTED into buster-backports->backports-policy, buster-backports

2022-03-21 Thread Debian FTP Masters
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 08 Mar 2022 14:48:28 +0100 Source: linux-signed-arm64 Architecture: source Version: 5.10.103+1~bpo10+1 Distribution: buster-backports Urgency: high Maintainer: Debian Kernel Team Changed-By: Ben Hutchings Change

Bug#1005005: Regression from 3c196f056666 ("drm/amdgpu: always reset the asic in suspend (v2)") on suspend?

2022-03-21 Thread Thorsten Leemhuis
Hi, this is your Linux kernel regression tracker. Top-posting for once, to make this easily accessible to everyone. 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? Ciao, Thorsten