XPost: linux.debian.bugs.dist
From: [email protected]

Package: src:linux
Version: 6.1.140-1
Severity: serious
Justification: Policy 11.8.1

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

* What led up to the situation?
Resume from suspend-to-disk keeps screen dark. The system is running, and is accessable via network, but no X11.
* What exactly did you do (or not do) that was effective (or
ineffective)?
acpitool -S; reboot, input of disk encryption password
* What was the outcome of this action?
Two dark monitors, which report no HDMI and (the other) no DisplayPort signal
* What outcome did you expect instead?
My window system was expected, with a X11 windows and mouse.

* Additional, maybe helpful information:
I've a AMD Ryzen 7 5700G system, where the on-chip GPU is used as the only graphic card, and where no additional graphic card is installed.
I saw this in 3 of 3 times, after upgrading to linux-image-6.1.0-37-amd64 kernel. Running the old, saved linux-image-6.1.0-34-amd64 kernel package (kernel 6.1.135-1) - selection via grub - , the situation doesn't occur and the resumes are solid now.
Note that I didn't upgrade or install any other packages in between, only using a different Linux kernel from Debian, and now the situation doesn't occur anymore.


*** End of the template - remove these template lines ***


-- Package-specific info:
** Kernel log: boot messages should be attached

** Model information
sys_vendor: ASUS
product_name: System Product Name
product_version: System Version
chassis_vendor: Default string
chassis_version: Default string
bios_vendor: American Megatrends Inc.
bios_version: 3404
board_vendor: ASUSTeK COMPUTER INC.
board_name: TUF GAMING B550-PLUS (WI-FI)
board_version: Rev X.0x

** PCI devices:
00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne Root Complex [1022:1630]
Subsystem: ASUSTeK Computer Inc. Renoir/Cezanne Root Complex [1043:8809]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-

00:00.2 IOMMU [0806]: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne IOMMU [1022:1631]
Subsystem: ASUSTeK Computer Inc. Renoir/Cezanne IOMMU [1043:8809]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Interrupt: pin A routed to IRQ 255
Capabilities: <access denied>

00:01.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host Bridge [1022:1632]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
IOMMU group: 0

00:02.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host Bridge [1022:1632]
DeviceName: Onboard IGD
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
IOMMU group: 1

00:02.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne PCIe GPP Bridge [1022:1634] (prog-if 00 [Normal decode])
Subsystem: ASUSTeK Computer Inc. Renoir/Cezanne PCIe GPP Bridge [1043:8809]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin ? routed to IRQ 26
IOMMU group: 2
Bus: primary=00, secondary=01, subordinate=05, sec-latency=0
I/O behind bridge: f000-ffff [size=4K] [16-bit]
Memory behind bridge: fcc00000-fcefffff [size=3M] [32-bit]
Prefetchable memory behind bridge: [disabled] [64-bit]
Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
BridgeCtl: Parity- SERR+ NoISA- VGA- VGA16+ MAbort- >Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: <access denied>
Kernel driver in use: pcieport

00:02.2 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne PCIe GPP Bridge [1022:1634] (prog-if 00 [Normal decode])
Subsystem: ASUSTeK Computer Inc. Renoir/Cezanne PCIe GPP Bridge [1043:8809]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin ? routed to IRQ 27
IOMMU group: 3
Bus: primary=00, secondary=06, subordinate=06, sec-latency=0
I/O behind bridge: [disabled] [32-bit]
Memory behind bridge: fcf00000-fcffffff [size=1M] [32-bit]
Prefetchable memory behind bridge: [disabled] [64-bit]
Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
BridgeCtl: Parity- SERR+ NoISA- VGA- VGA16+ MAbort- >Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: <access denied>
Kernel driver in use: pcieport

00:08.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host Bridge [1022:1632]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
IOMMU group: 4

00:08.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Renoir Internal PCIe GPP Bridge to Bus [1022:1635] (prog-if 00 [Normal decode])
Subsystem: ASUSTeK Computer Inc. Renoir Internal PCIe GPP Bridge to Bus [1043:8809]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+

[continued in next message]

--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)

XPost: linux.debian.bugs.dist
From: [email protected]

Control: tags -1 + moreinfo

Hi,

On Sun, Jun 08, 2025 at 01:55:23PM +0200, Klaus Singvogel wrote:

Package: src:linux
Version: 6.1.140-1
Severity: serious
Justification: Policy 11.8.1

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

* What led up to the situation?
Resume from suspend-to-disk keeps screen dark. The system is running, and is accessable via network, but no X11.
* What exactly did you do (or not do) that was effective (or
ineffective)?
acpitool -S; reboot, input of disk encryption password
* What was the outcome of this action?
Two dark monitors, which report no HDMI and (the other) no DisplayPort signal
* What outcome did you expect instead?
My window system was expected, with a X11 windows and mouse.

* Additional, maybe helpful information:
I've a AMD Ryzen 7 5700G system, where the on-chip GPU is used as the only graphic card, and where no additional graphic card is installed.
I saw this in 3 of 3 times, after upgrading to linux-image-6.1.0-37-amd64 kernel. Running the old, saved linux-image-6.1.0-34-amd64 kernel package (kernel 6.1.135-1) - selection via grub - , the situation doesn't occur and the resumes are solid

now. Note that I didn't upgrade or install any other packages in between, only using a different Linux kernel from Debian, and now the situation doesn't occur anymore.

Thanks for your report.

Can you please report here a full boot long once triggering the issue
with the 6.1.140-1 please from boot, to suspend and then resume.

Your system appears to be tainted furthermore with
TAINT_PROPRIETARY_MODULE and out of tree modules, so we need to se as
well what those are.

Regards,
Salvatore

--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)

XPost: linux.debian.bugs.dist
From: [email protected]

Hi Slavatore,


Salvatore Bonaccorso wrote:

Control: tags -1 + moreinfo

Hi,

On Sun, Jun 08, 2025 at 01:55:23PM +0200, Klaus Singvogel wrote:

Thanks for your report.

Can you please report here a full boot long once triggering the issue
with the 6.1.140-1 please from boot, to suspend and then resume.

Please help me, and give a link to a documentation or please describe in short, how can I create the boot log?

I think its done by journalctl, but maybe /var/log provides this information too?

Your system appears to be tainted furthermore with
TAINT_PROPRIETARY_MODULE and out of tree modules, so we need to se as
well what those are.

I only see that the module "wl" reports tainting the kernel.

If my information is correct, I can find all tainting modules by this command:

for i in /sys/module/*/taint ; do
od -A n ${i} | grep -q 000012 || echo $i
done

and my only output is:
/sys/module/wl/taint

and for verification the output is:
od -A n /sys/module/wl/taint
047520 005105

------------------------
# modinfo wl
filename: /lib/modules/6.1.0-34-amd64/updates/dkms/wl.ko
license: MIXED/Proprietary
alias: pci:v*d*sv*sd*bc02sc80i*
depends: cfg80211
retpoline: Y
name: wl
vermagic: 6.1.0-34-amd64 SMP preempt mod_unload modversions
sig_id: PKCS#7
signer: DKMS module signing key
sig_key: 76:3E:4B:92:49:EB:7D:A6:E7:B5:AD:15:0B:E4:FA:D1:81:03:04:62 sig_hashalgo: sha256
signature: 71:A0:39:69:7B:EA:AC:3E:44:A8:25:07:B4:48:86:7F:4C:6C:00:D3:
96:08:8E:5F:91:60:A0:82:7B:41:79:36:20:64:5D:66:BB:F8:55:1B:
16:57:BA:70:92:97:9C:C4:F0:95:00:4A:58:71:95:A4:35:DD:85:20:
A6:74:C0:23:99:A6:D4:F6:DA:E7:F5:2B:F4:62:C9:CE:8B:EA:CD:61:
AA:E3:10:B0:41:70:FA:68:B3:32:F2:19:9B:02:77:C3:C3:4F:EC:24:
B3:73:A3:9D:77:6F:31:7D:45:EB:4C:F4:F5:1A:64:B6:01:42:CE:CD:
4D:63:8F:2E:F3:E0:14:C2:5F:B1:FB:B0:5A:AD:D7:EE:6D:D1:0A:34:
DB:46:A7:45:8E:24:0A:96:05:83:50:CF:1D:51:A7:2B:5E:07:2F:25:
8C:B5:6F:12:16:4C:C9:52:24:46:7C:1C:CC:09:39:51:75:F7:44:99:
48:E6:09:92:6C:25:9B:AB:87:DD:A1:46:27:7B:12:FC:61:A7:02:53:
5F:96:43:1D:C7:22:FD:1F:47:52:31:CA:86:41:CC:2E:CA:60:09:1D:
77:4A:F6:0C:42:82:8E:64:0C:0F:03:1B:1E:0D:12:EE:C8:08:23:51:
47:04:EF:E6:27:14:FF:B6:4B:C1:8C:D1:DC:42:C4:48
parm: passivemode:int
parm: wl_txq_thresh:int
parm: oneonly:int
parm: piomode:int
parm: instance_base:int
parm: nompc:int
parm: intf_name:string
------------------------


------------------------
# dmesg | grep -i 'taint'
[ 18.933728] wl: loading out-of-tree module taints kernel.
[ 18.933731] wl: module license 'MIXED/Proprietary' taints kernel.
[ 18.933732] Disabling lock debugging due to kernel taint
[ 18.935832] wl: module verification failed: signature and/or required key missing - tainting kernel
[ 1198.424906] CPU: 3 PID: 13003 Comm: kworker/u64:21 Tainted: P OE 6.1.0-34-amd64 #1 Debian 6.1.135-1
[ 1199.580978] CPU: 6 PID: 101 Comm: kworker/u64:7 Tainted: P W OE 6.1.0-34-amd64 #1 Debian 6.1.135-1
[ 1848.147512] CPU: 2 PID: 14572 Comm: kworker/u64:12 Tainted: P W OE 6.1.0-34-amd64 #1 Debian 6.1.135-1
[ 9157.035962] CPU: 15 PID: 41343 Comm: kworker/u64:21 Tainted: P W OE 6.1.0-34-amd64 #1 Debian 6.1.135-1
------------------------

Thanks.

Best regards,
Klaus.
--
Klaus Singvogel
GnuPG-Key-ID: 1024R/5068792D 1994-06-27

--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)

XPost: linux.debian.bugs.dist
From: [email protected]

Hi Klaus,

On Mon, Jun 09, 2025 at 12:26:37AM +0200, Klaus Singvogel wrote:

Hi,

Salvatore Bonaccorso wrote:

Control: tags -1 + moreinfo

Hi,

On Sun, Jun 08, 2025 at 01:55:23PM +0200, Klaus Singvogel wrote:

Package: src:linux
Version: 6.1.140-1
Severity: serious
Justification: Policy 11.8.1

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

* What led up to the situation?
Resume from suspend-to-disk keeps screen dark. The system is running, and is accessable via network, but no X11.
* What exactly did you do (or not do) that was effective (or
ineffective)?
acpitool -S; reboot, input of disk encryption password
* What was the outcome of this action?
Two dark monitors, which report no HDMI and (the other) no DisplayPort signal
* What outcome did you expect instead?
My window system was expected, with a X11 windows and mouse.

* Additional, maybe helpful information:
I've a AMD Ryzen 7 5700G system, where the on-chip GPU is used as the only graphic card, and where no additional graphic card is installed.
I saw this in 3 of 3 times, after upgrading to linux-image-6.1.0-37-amd64 kernel. Running the old, saved linux-image-6.1.0-34-amd64 kernel package (kernel 6.1.135-1) - selection via grub - , the situation doesn't occur and the resumes are

solid now. Note that I didn't upgrade or install any other packages in between, only using a different Linux kernel from Debian, and now the situation doesn't occur anymore.

Thanks for your report.

Can you please report here a full boot long once triggering the issue
with the 6.1.140-1 please from boot, to suspend and then resume.

Find it attached.

This is very helpful thanks.

While the OOT is not directly related, can you confirm that you get
the same problem if you do not load the OOT wl module?

If yes, the next step would be to report it upstream at https://gitlab.freedesktop.org/drm/amd with the full boot log attached
ot the report there (there are similar, but not identical reports
filled there, but closed).

Regards,
Salvatore

--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)

XPost: linux.debian.bugs.dist
From: [email protected]

Hi Salvatore,

Salvatore Bonaccorso wrote:

While the OOT is not directly related, can you confirm that you get
the same problem if you do not load the OOT wl module?

I blacklisted the wl module, and the kernel no longer reports, that it's tained, but the issue persists.

If yes, the next step would be to report it upstream at https://gitlab.freedesktop.org/drm/amd with the full boot log attached
ot the report there (there are similar, but not identical reports
filled there, but closed).

I filed this report: https://gitlab.freedesktop.org/drm/amd/-/issues/4330

Best regards,
Klaus.
--
Klaus Singvogel
GnuPG-Key-ID: 1024R/5068792D 1994-06-27

--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)

XPost: linux.debian.bugs.dist
From: [email protected]

Hi Klaus,

On Sun, Jun 15, 2025 at 11:54:34PM +0200, Klaus Singvogel wrote:

Hi Salvatore,

Salvatore Bonaccorso wrote:

While the OOT is not directly related, can you confirm that you get
the same problem if you do not load the OOT wl module?

I blacklisted the wl module, and the kernel no longer reports, that it's tained, but the issue persists.

If yes, the next step would be to report it upstream at https://gitlab.freedesktop.org/drm/amd with the full boot log attached
ot the report there (there are similar, but not identical reports
filled there, but closed).

I filed this report: https://gitlab.freedesktop.org/drm/amd/-/issues/4330

Many thanks for that!

Regards,
Salvatore

--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)

XPost: linux.debian.bugs.dist
From: [email protected]

Hello Uwe,

Uwe Kleine-König wrote:

Hello Klaus,

http://deb.debian.org/debian/pool/main/l/linux-signed-amd64/linux-image-6.15-amd64_6.15.2-1%7eexp1_amd64.deb

and then install it using

dpkg -i linux-image-6.15-amd64_6.15.2-1~exp1_amd64.deb

Thanks.

The first installation was aborted, due to the wrong version of linux-base (>= 4.12 was required, but 4.9 was installed).

But after installing linux-base_4.12~bpo12+1_all.deb, the linux kernel 6.15.2 was successfully installed. Yippie.

The issue doesn't occur in kernel 6.15.2.

As a side-effect, I lost my HDMI display with kernel 6.15.2.
According to lxrandr, the display exists and is switched on. But lxrandr could not change anything. Surpisingly, I could move my mouse into the area of the HDMI display (i.e. it didn't stop at the boundary). And therefore my DP monitor was the only
available monitor.

If I had to guess, I would say, that this kernel relies on newer firmware files, that weren't installed. But I don't know.

Thanks for your helpful advice.

Best regards,
Klaus.
--
Klaus Singvogel
GnuPG-Key-ID: 1024R/5068792D 1994-06-27

--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)

XPost: linux.debian.bugs.dist
From: [email protected]

Hello Salvatore,

Klaus Singvogel wrote:

dpkg -i linux-image-6.15-amd64_6.15.2-1~exp1_amd64.deb

Thanks.

The first installation was aborted, due to the wrong version of linux-base (>= 4.12 was required, but 4.9 was installed).

But after installing linux-base_4.12~bpo12+1_all.deb, the linux kernel 6.15.2 was successfully installed. Yippie.

The issue doesn't occur in kernel 6.15.2.

Upstream suggests testing kernel version 6.1.141.
https://gitlab.freedesktop.org/drm/amd/-/issues/4330

Mario thinks that this missing patch might be the cause of the issue:
https://git.kernel.org/torvalds/c/7e7cb7a13c81

Is the 6.1.141 kernel available as a Debian package anywhere, like the 6.15.2 experimental version?

Thanks in advance.

Best regards,
Klaus.
--
Klaus Singvogel
GnuPG-Key-ID: 1024R/5068792D 1994-06-27

--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)

XPost: linux.debian.bugs.dist
From: [email protected]

Hi Klaus,

On Wed, Jun 18, 2025 at 07:54:55PM +0200, Klaus Singvogel wrote:

Hello Salvatore,

Klaus Singvogel wrote:

dpkg -i linux-image-6.15-amd64_6.15.2-1~exp1_amd64.deb

Thanks.

The first installation was aborted, due to the wrong version of linux-base (>= 4.12 was required, but 4.9 was installed).

But after installing linux-base_4.12~bpo12+1_all.deb, the linux kernel 6.15.2 was successfully installed. Yippie.

The issue doesn't occur in kernel 6.15.2.

Upstream suggests testing kernel version 6.1.141.
https://gitlab.freedesktop.org/drm/amd/-/issues/4330

Mario thinks that this missing patch might be the cause of the issue:
https://git.kernel.org/torvalds/c/7e7cb7a13c81
Is the 6.1.141 kernel available as a Debian package anywhere, like
the 6.15.2 experimental version?

No not yet, as it is yet in preparation.

I can do two things for you, 1. provide the 6.1.141 based test package
version and both a test version with only 7e7cb7a13c81073d38a10fa7b450d23712281ec4 applied to confirm that is
the isolated fix.

will come back to you when it's ready to test. Alterantively you can
do the following, with the attached patch (which is the mentioned
commit, follow https://kernel-team.pages.debian.net/kernel-handbook/ch-common-tasks.html#id-1.6.6.4
which uses a helper script to make test packages using single patches
on top quite handy/easy.

Regards,
Salvatore

From 9c40d1f7b75fc93d7ef02acc3a2a712cb057e576 Mon Sep 17 00:00:00 2001
From: Mario Limonciello <[email protected]>
Date: Thu, 22 May 2025 09:13:28 -0500
Subject: [PATCH] Revert "drm/amd: Keep display off while going into S4"

commit 7e7cb7a13c81073d38a10fa7b450d23712281ec4 upstream.

commit 68bfdc8dc0a1a ("drm/amd: Keep display off while going into S4") attempted to keep displays off during the S4 sequence by not resuming
display IP. This however leads to hangs because DRM clients such as the console can try to access registers and cause a hang.

Closes: https://gitlab.freedesktop.org/drm/amd/-/issues/4155
Fixes: 68bfdc8dc0a1a ("drm/amd: Keep display off while going into S4") Reviewed-by: Alex Deucher <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Mario Limonciello <[email protected]>
Signed-off-by: Alex Deucher <[email protected]>
(cherry picked from commit e485502c37b097b0bd773baa7e2741bf7bd2909a)
Cc: [email protected]
Signed-off-by: Greg Kroah-Hartman <[email protected]>
---
drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c | 5 -----
1 file changed, 5 deletions(-)

diff --git a/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c b/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c
index 998dde73ecc6..64f626cc7913 100644
--- a/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c
+++ b/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c
@@ -2897,11 +2897,6 @@ static int dm_resume(void *handle)

return 0;
}
-
- /* leave display off for S4 sequence */
- if (adev->in_s4)
- return 0;
-
/* Recreate dc_state - DC invalidates it when setting power state to S3. */
dc_release_state(dm_state->context);
dm_state->context = dc_create_state(dm->dc);
--
2.50.0

--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)

XPost: linux.debian.bugs.dist
From: [email protected]

Hi Klaus,

On Thu, Jun 19, 2025 at 08:35:22AM +0200, Salvatore Bonaccorso wrote:

Hi Klaus,

On Wed, Jun 18, 2025 at 07:54:55PM +0200, Klaus Singvogel wrote:

Hello Salvatore,

Klaus Singvogel wrote:

dpkg -i linux-image-6.15-amd64_6.15.2-1~exp1_amd64.deb

Thanks.

The first installation was aborted, due to the wrong version of linux-base (>= 4.12 was required, but 4.9 was installed).

But after installing linux-base_4.12~bpo12+1_all.deb, the linux kernel 6.15.2 was successfully installed. Yippie.

The issue doesn't occur in kernel 6.15.2.

Upstream suggests testing kernel version 6.1.141.
https://gitlab.freedesktop.org/drm/amd/-/issues/4330

Mario thinks that this missing patch might be the cause of the issue:
https://git.kernel.org/torvalds/c/7e7cb7a13c81
Is the 6.1.141 kernel available as a Debian package anywhere, like
the 6.15.2 experimental version?

No not yet, as it is yet in preparation.

I can do two things for you, 1. provide the 6.1.141 based test package version and both a test version with only 7e7cb7a13c81073d38a10fa7b450d23712281ec4 applied to confirm that is
the isolated fix.

will come back to you when it's ready to test. Alterantively you can
do the following, with the attached patch (which is the mentioned
commit, follow https://kernel-team.pages.debian.net/kernel-handbook/ch-common-tasks.html#id-1.6.6.4
which uses a helper script to make test packages using single patches
on top quite handy/easy.

I have built 6.1.140-1 with the single patch on top in https://people.debian.org/~carnil/tmp/linux/1107511/

Along I generated a sha256 sum file for the files and signed it with
the gpg for me in the Debian keyring, as we cannot provide signed
packages.

With the disclaimer that they are test-packages, it would be great if
you can test this.

Rgards,
Salvatore

--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)

XPost: linux.debian.bugs.dist
From: [email protected]

Hi Salvatore,

Salvatore Bonaccorso wrote:

I have built 6.1.140-1 with the single patch on top in https://people.debian.org/~carnil/tmp/linux/1107511/

Along I generated a sha256 sum file for the files and signed it with
the gpg for me in the Debian keyring, as we cannot provide signed
packages.

With the disclaimer that they are test-packages, it would be great if
you can test this.

I would like to sincerely thank you, Salvatore Bonaccorso, for kindly providing the 6.1.140 kernel, including the patch, as a Debian test package.

After testing this kernel twice, I can confirm that the issue did not occur anymore.

Thank you for your great help, and making the testing so easy for me.

Best regards,
Klaus.
--
Klaus Singvogel
GnuPG-Key-ID: 1024R/5068792D 1994-06-27

--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)