Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #89916 > unrolled thread

Bug#1120058: linux-image-6.16.12+deb14+1-amd64: suspend-to-RAM results in hang (AMD Ryzen 5 5625U)

Back to article view | Back to linux.debian.kernel

Contents

  Bug#1120058: linux-image-6.16.12+deb14+1-amd64: suspend-to-RAM results in hang (AMD Ryzen 5 5625U) J. Neuschäfer <j.neuschaefer@gmx.net> - 2025-11-04 17:10 +0100
    Bug#1120058: linux-image-6.16.12+deb14+1-amd64: suspend-to-RAM results in hang (AMD Ryzen 5 5625U) Salvatore Bonaccorso <carnil@debian.org> - 2025-11-05 06:20 +0100
    Processed: Re: Bug#1120058: linux-image-6.16.12+deb14+1-amd64:  suspend-to-RAM results in hang (AMD Ryzen 5 5625U) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2025-11-05 06:20 +0100
    Processed: Re: Bug#1120058: linux-image-6.16.12+deb14+1-amd64:  suspend-to-RAM results in hang (AMD Ryzen 5 5625U) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2025-11-28 21:20 +0100
    Bug#1120058: linux-image-6.16.12+deb14+1-amd64: suspend-to-RAM results in hang (AMD Ryzen 5 5625U) Salvatore Bonaccorso <carnil@debian.org> - 2025-11-28 21:20 +0100
    Bug#1120058: [regression] 0c58a97f919c ("fuse: remove tmp folio for writebacks and internal rb tree") results in suspend-to-RAM hang on AMD Ryzen 5 5625U on test scenario involving podman containers, x2go and openjdk workload Salvatore Bonaccorso <carnil@debian.org> - 2025-12-14 15:30 +0100
    Bug#1120058: marked as done (linux-image-6.16.12+deb14+1-amd64:  suspend-to-RAM results in hang (AMD Ryzen 5 5625U)) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2026-01-23 11:10 +0100

#89916 — Bug#1120058: linux-image-6.16.12+deb14+1-amd64: suspend-to-RAM results in hang (AMD Ryzen 5 5625U)

Package: src:linux
Version: 6.16.12-2
Severity: normal
X-Debbugs-Cc: debian-amd64@lists.debian.org
User: debian-amd64@lists.debian.org
Usertags: amd64

Suspend-to-RAM results in a hang that renders most of userspace
unresponsive on my HP ProBook 445, based on a AMD Ryzen 5 5625U with
Radeon Graphics. Fortunately I was still able to login on a different
TTY and look at htop and dmesg, which showed that systemd-sleep was
stuck in D state. The system was unable to fully enter suspend, or to
resume everything normally. I ran into this issue multiple times with
kernel version 6.16.12, as well as with 6.16.9.
The NVMe storage (PCIe c0a9:0100) may or may not be related to this issue.

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

[  +0.064102] r8169 0000:01:00.0 eth0: Link is Down
[  +0.582946] PM: suspend entry (s2idle)
[Nov 5 08:33] INFO: task systemd-sleep:429260 blocked for more than 120 seconds.
[  +0.000050]       Not tainted 6.16.12+deb14+1-amd64 #1 Debian 6.16.12-2
[  +0.000026] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[  +0.000025] task:systemd-sleep   state:D stack:0     pid:429260 tgid:429260 ppid:1      task_flags:0x400100 flags:0x00004002
[  +0.000014] Call Trace:
[  +0.000005]  <TASK>
[  +0.000011]  __schedule+0x4b0/0xd00
[  +0.000019]  schedule+0x27/0xd0
[  +0.000008]  io_schedule+0x46/0x70
[  +0.000008]  folio_wait_bit_common+0x12b/0x320
[  +0.000014]  ? __pfx_wake_page_function+0x10/0x10
[  +0.000010]  folio_wait_writeback+0x2b/0x80
[  +0.000009]  __filemap_fdatawait_range+0x85/0xf0
[  +0.000023]  filemap_fdatawait_keep_errors+0x1e/0x50
[  +0.000008]  sync_inodes_sb+0x21d/0x2b0
[  +0.000016]  ? __pfx_sync_inodes_one_sb+0x10/0x10
[  +0.000009]  __iterate_supers+0xe5/0x150
[  +0.000011]  ksys_sync+0x43/0xb0
[  +0.000010]  ksys_sync_helper+0x17/0x80
[  +0.000009]  pm_suspend+0x2ba/0x560
[  +0.000008]  state_store+0x6c/0xd0
[  +0.000012]  kernfs_fop_write_iter+0x150/0x200
[  +0.000010]  vfs_write+0x25d/0x450
[  +0.000016]  ksys_write+0x6b/0xe0
[  +0.000008]  do_syscall_64+0x84/0x320
[  +0.000008]  ? get_page_from_freelist+0x39e/0x1c40
[  +0.000021]  ? srso_alias_return_thunk+0x5/0xfbef5
[  +0.000008]  ? __alloc_frozen_pages_noprof+0x176/0x320
[  +0.000009]  ? srso_alias_return_thunk+0x5/0xfbef5
[  +0.000006]  ? mod_memcg_lruvec_state+0x1cb/0x270
[  +0.000013]  ? srso_alias_return_thunk+0x5/0xfbef5
[  +0.000006]  ? __lruvec_stat_mod_folio+0x83/0xd0
[  +0.000008]  ? srso_alias_return_thunk+0x5/0xfbef5
[  +0.000008]  ? srso_alias_return_thunk+0x5/0xfbef5
[  +0.000006]  ? set_ptes.isra.0+0x36/0x80
[  +0.000009]  ? srso_alias_return_thunk+0x5/0xfbef5
[  +0.000007]  ? do_anonymous_page+0xfc/0x9b0
[  +0.000008]  ? srso_alias_return_thunk+0x5/0xfbef5
[  +0.000006]  ? ___pte_offset_map+0x1b/0x180
[  +0.000011]  ? srso_alias_return_thunk+0x5/0xfbef5
[  +0.000006]  ? __handle_mm_fault+0xb2c/0xf70
[  +0.000015]  ? srso_alias_return_thunk+0x5/0xfbef5
[  +0.000006]  ? count_memcg_events+0x167/0x1d0
[  +0.000008]  ? srso_alias_return_thunk+0x5/0xfbef5
[  +0.000006]  ? handle_mm_fault+0x1d7/0x2e0
[  +0.000009]  ? srso_alias_return_thunk+0x5/0xfbef5
[  +0.000007]  ? do_user_addr_fault+0x2c3/0x7f0
[  +0.000011]  ? srso_alias_return_thunk+0x5/0xfbef5
[  +0.000008]  entry_SYSCALL_64_after_hwframe+0x76/0x7e
[  +0.000007] RIP: 0033:0x7fec62099687
[  +0.000049] RSP: 002b:00007ffe4fb80a60 EFLAGS: 00000202 ORIG_RAX: 0000000000000001
[  +0.000008] RAX: ffffffffffffffda RBX: 00007fec61eb0980 RCX: 00007fec62099687
[  +0.000005] RDX: 0000000000000004 RSI: 000055d051b80b50 RDI: 0000000000000007
[  +0.000005] RBP: 000055d051b80b50 R08: 0000000000000000 R09: 0000000000000000
[  +0.000004] R10: 0000000000000000 R11: 0000000000000202 R12: 0000000000000004
[  +0.000004] R13: 000055d051b772a0 R14: 00007fec621efe80 R15: 0000000000000000
[  +0.000012]  </TASK>

** Model information
sys_vendor: HP
product_name: HP ProBook 445 14 inch G9 Notebook PC
product_version: 
chassis_vendor: HP
chassis_version: 
bios_vendor: HP
bios_version: U78 Ver. 01.06.00
board_vendor: HP
board_name: 89C9
board_version: KBC Version 14.1E.00

** Configuration for modprobe:
blacklist microcode
blacklist arkfb
blacklist aty128fb
blacklist atyfb
blacklist radeonfb
blacklist cirrusfb
blacklist cyber2000fb
blacklist kyrofb
blacklist matroxfb_base
blacklist mb862xxfb
blacklist neofb
blacklist pm2fb
blacklist pm3fb
blacklist s3fb
blacklist savagefb
blacklist sisfb
blacklist tdfxfb
blacklist tridentfb
blacklist vt8623fb
options snd_pcsp index=-2
options cx88_alsa index=-2
options snd_atiixp_modem index=-2
options snd_intel8x0m index=-2
options snd_via82xx_modem index=-2
options md_mod start_ro=1
options nbd max_part=15
options bonding max_bonds=0
options dummy numdummies=0
options ifb numifbs=0
options net ifnames=0

** PCI devices:
00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne Root Complex [1022:1630]
	Subsystem: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne Root Complex [1022:1630]
	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: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne IOMMU [1022:1631]
	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:01.2 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne PCIe GPP Bridge [1022:1634] (prog-if 00 [Normal decode])
	Subsystem: Advanced Micro Devices, Inc. [AMD] Device [1022:1453]
	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
	Interrupt: pin ? routed to IRQ 35
	IOMMU group: 1
	Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
	I/O behind bridge: 2000-2fff [size=4K] [16-bit]
	Memory behind bridge: fb700000-fb7fffff [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:01.3 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne PCIe GPP Bridge [1022:1634] (prog-if 00 [Normal decode])
	Subsystem: Advanced Micro Devices, Inc. [AMD] Device [1022:1453]
	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
	Interrupt: pin ? routed to IRQ 36
	IOMMU group: 2
	Bus: primary=00, secondary=02, subordinate=02, sec-latency=0
	I/O behind bridge: [disabled] [32-bit]
	Memory behind bridge: fb000000-fb1fffff [size=2M] [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.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: 3

00:02.4 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne PCIe GPP Bridge [1022:1634] (prog-if 00 [Normal decode])
	Subsystem: Advanced Micro Devices, Inc. [AMD] Device [1022:1453]
	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
	Interrupt: pin ? routed to IRQ 37
	IOMMU group: 4
	Bus: primary=00, secondary=03, subordinate=03, sec-latency=0
	I/O behind bridge: [disabled] [32-bit]
	Memory behind bridge: fb600000-fb6fffff [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: 5

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: Advanced Micro Devices, Inc. [AMD] Renoir Internal PCIe GPP Bridge to Bus [1022:1635]
	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
	Interrupt: pin A routed to IRQ 38
	IOMMU group: 6
	Bus: primary=00, secondary=04, subordinate=04, sec-latency=0
	I/O behind bridge: 1000-1fff [size=4K] [16-bit]
	Memory behind bridge: fb200000-fb5fffff [size=4M] [32-bit]
	Prefetchable memory behind bridge: 860000000-8701fffff [size=258M] [32-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:14.0 SMBus [0c05]: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller [1022:790b] (rev 51)
	Subsystem: Hewlett-Packard Company Device [103c:89c9]
	Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	IOMMU group: 7
	Kernel modules: i2c_piix4, sp5100_tco

00:14.3 ISA bridge [0601]: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge [1022:790e] (rev 51)
	Subsystem: Hewlett-Packard Company Device [103c:89c9]
	Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	IOMMU group: 7

00:18.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 0 [1022:166a]
	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: 8

00:18.1 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 1 [1022:166b]
	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: 8

00:18.2 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 2 [1022:166c]
	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: 8

00:18.3 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 3 [1022:166d]
	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: 8
	Kernel driver in use: k10temp
	Kernel modules: k10temp

00:18.4 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 4 [1022:166e]
	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: 8

00:18.5 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 5 [1022:166f]
	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: 8

00:18.6 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 6 [1022:1670]
	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: 8

00:18.7 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 7 [1022:1671]
	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: 8

01:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 15)
	Subsystem: Hewlett-Packard Company Device [103c:89c9]
	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 72
	IOMMU group: 9
	Region 0: I/O ports at 2000 [size=256]
	Region 2: Memory at fb704000 (64-bit, non-prefetchable) [size=4K]
	Region 4: Memory at fb700000 (64-bit, non-prefetchable) [size=16K]
	Capabilities: <access denied>
	Kernel driver in use: r8169
	Kernel modules: r8169

02:00.0 Network controller [0280]: Qualcomm Technologies, Inc QCNFA765 Wireless Network Adapter [17cb:1103] (rev 01)
	Subsystem: Foxconn International, Inc. Device [105b:e0c4]
	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
	Interrupt: pin ? routed to IRQ 81
	IOMMU group: 10
	Region 0: Memory at fb000000 (64-bit, non-prefetchable) [size=2M]
	Capabilities: <access denied>
	Kernel driver in use: ath11k_pci
	Kernel modules: ath11k_pci

03:00.0 Non-Volatile memory controller [0108]: Micron/Crucial Technology P5 NVMe PCIe SSD[SlashP5] [c0a9:5412] (prog-if 02 [NVM Express])
	Subsystem: Micron/Crucial Technology Device [c0a9:0100]
	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
	Interrupt: pin A routed to IRQ 39
	IOMMU group: 11
	Region 0: Memory at fb600000 (64-bit, non-prefetchable) [size=16K]
	Capabilities: <access denied>
	Kernel driver in use: nvme
	Kernel modules: nvme

04:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Barcelo [1002:15e7] (rev c2) (prog-if 00 [VGA controller])
	DeviceName: Onboard IGD
	Subsystem: Hewlett-Packard Company Device [103c:89c9]
	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
	Interrupt: pin A routed to IRQ 50
	IOMMU group: 12
	Region 0: Memory at 860000000 (64-bit, prefetchable) [size=256M]
	Region 2: Memory at 870000000 (64-bit, prefetchable) [size=2M]
	Region 4: I/O ports at 1000 [size=256]
	Region 5: Memory at fb500000 (32-bit, non-prefetchable) [size=512K]
	Capabilities: <access denied>
	Kernel driver in use: amdgpu
	Kernel modules: amdgpu

04:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Renoir/Cezanne HDMI/DP Audio Controller [1002:1637]
	Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Renoir/Cezanne HDMI/DP Audio Controller [1002:1637]
	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
	Interrupt: pin B routed to IRQ 79
	IOMMU group: 13
	Region 0: Memory at fb5c8000 (32-bit, non-prefetchable) [size=16K]
	Capabilities: <access denied>
	Kernel driver in use: snd_hda_intel
	Kernel modules: snd_hda_intel

04:00.2 Encryption controller [1080]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2/FireFlight/Renoir/Cezanne Platform Security Processor [1022:15df]
	Subsystem: Advanced Micro Devices, Inc. [AMD] Raven/Raven2/FireFlight/Renoir/Cezanne Platform Security Processor [1022:15df]
	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
	Interrupt: pin C routed to IRQ 75
	IOMMU group: 14
	Region 2: Memory at fb400000 (32-bit, non-prefetchable) [size=1M]
	Region 5: Memory at fb5cc000 (32-bit, non-prefetchable) [size=8K]
	Capabilities: <access denied>
	Kernel driver in use: ccp
	Kernel modules: ccp

04:00.3 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne USB 3.1 [1022:1639] (prog-if 30 [XHCI])
	Subsystem: Hewlett-Packard Company Device [103c:89c9]
	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 D routed to IRQ 41
	IOMMU group: 15
	Region 0: Memory at fb200000 (64-bit, non-prefetchable) [size=1M]
	Capabilities: <access denied>
	Kernel driver in use: xhci_hcd
	Kernel modules: xhci_pci

04:00.4 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne USB 3.1 [1022:1639] (prog-if 30 [XHCI])
	Subsystem: Hewlett-Packard Company Device [103c:89c9]
	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 A routed to IRQ 50
	IOMMU group: 16
	Region 0: Memory at fb300000 (64-bit, non-prefetchable) [size=1M]
	Capabilities: <access denied>
	Kernel driver in use: xhci_hcd
	Kernel modules: xhci_pci

04:00.5 Multimedia controller [0480]: Advanced Micro Devices, Inc. [AMD] Audio Coprocessor [1022:15e2] (rev 01)
	Subsystem: Hewlett-Packard Company Device [103c:89c9]
	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 B routed to IRQ 78
	IOMMU group: 17
	Region 0: Memory at fb580000 (32-bit, non-prefetchable) [size=256K]
	Capabilities: <access denied>
	Kernel modules: snd_pci_acp3x, snd_rn_pci_acp3x, snd_pci_acp5x, snd_pci_acp6x, snd_acp_pci, snd_rpl_pci_acp6x, snd_pci_ps, snd_sof_amd_rembrandt

04:00.6 Audio device [0403]: Advanced Micro Devices, Inc. [AMD] Family 17h/19h/1ah HD Audio Controller [1022:15e3]
	Subsystem: Hewlett-Packard Company Device [103c:89c9]
	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
	Interrupt: pin C routed to IRQ 80
	IOMMU group: 18
	Region 0: Memory at fb5c0000 (32-bit, non-prefetchable) [size=32K]
	Capabilities: <access denied>
	Kernel driver in use: snd_hda_intel
	Kernel modules: snd_hda_intel


** USB devices:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 0489:e0d6 Foxconn / Hon Hai 
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002: ID 04f2:b73b Chicony Electronics Co., Ltd HP HD Camera
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub


-- System Information:
Debian Release: forky/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.16.9+deb14-amd64 (SMP w/12 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages linux-image-6.16.12+deb14+1-amd64 depends on:
ii  initramfs-tools [linux-initramfs-tool]  0.150
ii  kmod                                    34.2-2
ii  linux-base                              4.14

Versions of packages linux-image-6.16.12+deb14+1-amd64 recommends:
ii  apparmor  4.1.0-1

Versions of packages linux-image-6.16.12+deb14+1-amd64 suggests:
pn  debian-kernel-handbook  <none>
ii  extlinux                3:6.04~git20190206.bf6db5b4+dfsg1-3.2
ii  firmware-linux-free     20241210-2
ii  grub-efi-amd64          2.12-9
pn  linux-doc-6.16          <none>

Versions of packages linux-image-6.16.12+deb14+1-amd64 is related to:
ii  firmware-amd-graphics      20250808-1
ii  firmware-atheros           20250808-1
pn  firmware-bnx2              <none>
pn  firmware-bnx2x             <none>
pn  firmware-brcm80211         <none>
pn  firmware-cavium            <none>
pn  firmware-cirrus            <none>
pn  firmware-intel-graphics    <none>
pn  firmware-intel-misc        <none>
pn  firmware-intel-sound       <none>
pn  firmware-ipw2x00           <none>
pn  firmware-ivtv              <none>
pn  firmware-iwlwifi           <none>
pn  firmware-libertas          <none>
pn  firmware-marvell-prestera  <none>
pn  firmware-mediatek          <none>
pn  firmware-misc-nonfree      <none>
pn  firmware-myricom           <none>
pn  firmware-netronome         <none>
pn  firmware-netxen            <none>
pn  firmware-nvidia-graphics   <none>
pn  firmware-qcom-soc          <none>
pn  firmware-qlogic            <none>
ii  firmware-realtek           20250808-1
pn  firmware-samsung           <none>
pn  firmware-siano             <none>
pn  firmware-ti-connectivity   <none>
pn  xen-hypervisor             <none>

-- no debconf information

[toc] | [next] | [standalone]

#89917

Control: tags -1 + moreinfo

Hi,

On Tue, Nov 04, 2025 at 05:05:27PM +0100, J. Neusch??fer wrote:
> Package: src:linux
> Version: 6.16.12-2
> Severity: normal
> X-Debbugs-Cc: debian-amd64@lists.debian.org
> User: debian-amd64@lists.debian.org
> Usertags: amd64
> 
> Suspend-to-RAM results in a hang that renders most of userspace
> unresponsive on my HP ProBook 445, based on a AMD Ryzen 5 5625U with
> Radeon Graphics. Fortunately I was still able to login on a different
> TTY and look at htop and dmesg, which showed that systemd-sleep was
> stuck in D state. The system was unable to fully enter suspend, or to
> resume everything normally. I ran into this issue multiple times with
> kernel version 6.16.12, as well as with 6.16.9.
> The NVMe storage (PCIe c0a9:0100) may or may not be related to this issue.

Can you please provide the full kernel log along so we have the full
context?

Please try as well the recent uploaded 6.17.7-1 version uploaded to
unstable.

Can you additionally pin point a earlier version which works which
might give a range where you could start bisecting? (though I assume
it is not always reproducible).

Regards,
Salvatore

[toc] | [prev] | [next] | [standalone]

#89918 — Processed: Re: Bug#1120058: linux-image-6.16.12+deb14+1-amd64: suspend-to-RAM results in hang (AMD Ryzen 5 5625U)

Processing control commands:

> tags -1 + moreinfo
Bug #1120058 [src:linux] linux-image-6.16.12+deb14+1-amd64: suspend-to-RAM results in hang (AMD Ryzen 5 5625U)
Added tag(s) moreinfo.

-- 
1120058: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1120058
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [next] | [standalone]

#90322 — Processed: Re: Bug#1120058: linux-image-6.16.12+deb14+1-amd64: suspend-to-RAM results in hang (AMD Ryzen 5 5625U)

Processing control commands:

> found -1 6.17.8-1
Bug #1120058 [src:linux] linux-image-6.16.12+deb14+1-amd64: suspend-to-RAM results in hang (AMD Ryzen 5 5625U)
Marked as found in versions linux/6.17.8-1.

-- 
1120058: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1120058
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [next] | [standalone]

#90323

Control: found -1 6.17.8-1

Hi,

On Fri, Nov 28, 2025 at 11:50:48AM +0100, J. Neuschäfer wrote:
> On Wed, Nov 05, 2025 at 06:09:43AM +0100, Salvatore Bonaccorso wrote:
> > Control: tags -1 + moreinfo
> > 
> > Hi,
> > 
> > On Tue, Nov 04, 2025 at 05:05:27PM +0100, J. Neusch??fer wrote:
> > > Package: src:linux
> > > Version: 6.16.12-2
> > > Severity: normal
> > > X-Debbugs-Cc: debian-amd64@lists.debian.org
> > > User: debian-amd64@lists.debian.org
> > > Usertags: amd64
> > > 
> > > Suspend-to-RAM results in a hang that renders most of userspace
> > > unresponsive on my HP ProBook 445, based on a AMD Ryzen 5 5625U with
> > > Radeon Graphics. Fortunately I was still able to login on a different
> > > TTY and look at htop and dmesg, which showed that systemd-sleep was
> > > stuck in D state. The system was unable to fully enter suspend, or to
> > > resume everything normally. I ran into this issue multiple times with
> > > kernel version 6.16.12, as well as with 6.16.9.
> > > The NVMe storage (PCIe c0a9:0100) may or may not be related to this issue.
> > 
> > Can you please provide the full kernel log along so we have the full
> > context?
> 
> Sorry for the delay, it took me a while to test the different versions.

No problem at all, testing takes time (and us replying in most cases
as well :-))

> > Please try as well the recent uploaded 6.17.7-1 version uploaded to
> > unstable.
> 
> I've tested with 6.17.8+deb14-amd64, which has since been released, and
> the same issue persists. I'm attaching dmesg logs for 6.16 and 6.17, in
> which the bug is triggered.

Ack, I updated the metadata of the bug.

> > Can you additionally pin point a earlier version which works which
> > might give a range where you could start bisecting? (though I assume
> > it is not always reproducible).
> 
> I've been running 6.12.48+deb13-amd64 in the meantime, and it's been
> very stable, I haven't seen this issue.

Ok we have then likely a lower bound of 6.12 and an upper range bound
of 6.16 where the issue appears.

> I can reproduce the bug fairly reliably on 6.16/17 by running a specific
> podman container plus x2go (not entirely sure which parts of this is
> necessary).

Okay if you have a very reliable way to reproduce it, would you be
open to make "your hands bit dirty" and do some bisecting on the
issue?

The best thing would be to get a more closer range first via
installing Debian packages. I would suggest to fetch linux image
packages from https://snapshot.debian.org/ (rember, just keep them
using for testing, then switch away from them and uninstall not needed
ones again, in process of testing you might need to deinstall multiple
of those used for testing depending on how much space you have in
/boot).

For instance you can try first each first version uploaded from the
next major series, before the first 6.16.y upload to unstable we had
the following versions in experimental:

6.16.3-1
6.16.3-1~bpo13+1
6.16.1-1~exp1
6.16-1~exp1
6.16~rc7-1~exp1
6.15.6-1~exp1
6.15.5-1~exp1
6.15.4-1~exp1
6.15.3-1~exp1
6.15.2-1~exp1
6.15.1-1~exp1
6.15-1~exp1
6.15~rc7-1~exp1
6.14.6-1~exp1
6.14.5-1~exp1
6.14.3-1~exp1
6.13.11-1~exp1
6.13.10-1~exp1
6.13.9-1~exp1
6.13.8-1~exp1
6.13.7-1~exp1
6.13.6-1~exp1
6.13.5-1~exp1
6.13.4-1~exp1
6.13.3-1~exp1
6.13.2-1~exp1
6.13~rc7-1~exp1
6.13~rc6-1~exp1

Ideally we find the two major upstream versions which behave correctly
and the next major one which exposes the problem.

Now assume we have indication the problem appears between upstream
6.13 and 6.14. Then we can proceed as follows, and bisect the changes
between 6.13 and 6.14. The probecure is as follows:

    git clone https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
    cd linux-stable
    git checkout v6.13
    cp /boot/config-$(uname -r) .config
    yes '' | make localmodconfig
    make savedefconfig
    mv defconfig arch/x86/configs/my_defconfig

    # test 6.13 to ensure this is "good"
    make my_defconfig
    make -j $(nproc) bindeb-pkg
    ... install the resulting .deb package and confirm it successfully boots / problem does not exist

    # test 6.14 to ensure this is "bad"
    git checkout v6.14
    make my_defconfig
    make -j $(nproc) bindeb-pkg
    ... install the resulting .deb package and confirm it fails to boot / problem exists

With that confirmed, the bisection can start:

    git bisect start
    git bisect good v6.13
    git bisect bad v6.14

In each bisection step git checks out a state between the oldest
known-bad and the newest known-good commit. In each step test using:

    make my_defconfig
    make -j $(nproc) bindeb-pkg
    ... install, try to boot / verify if problem exists

and if the problem is hit run:

    git bisect bad

and if the problem doesn't trigger run:

    git bisect good

. Please pay attention to always select the just built kernel for
booting, it won't always be the default kernel picked up by grub.

Iterate until git announces to have identified the first bad commit.

Then provide the output of

    git bisect log

In the course of the bisection you might have to uninstall previous
kernels again to not exhaust the disk space in /boot. Also in the end
uninstall all self-built kernels again.

This should lead us in the ideal case to a breaking commit introducing
the problem.

Please let me know if you encounter any unclarity where it needs a
better outline of the steps.

If you are not too entusiastic to do these experiments, I right now
see it as only way to narrow it down to a kernel change if you are
able to consistently reproduce it with a given kernel version but not
with the 6.12.y series one (on the same system without other changes).

Regards,
Salvatore

[toc] | [prev] | [next] | [standalone]

#90457 — Bug#1120058: [regression] 0c58a97f919c ("fuse: remove tmp folio for writebacks and internal rb tree") results in suspend-to-RAM hang on AMD Ryzen 5 5625U on test scenario involving podman containers, x2go and openjdk workload

Hi Joanne,

In Debian J. Neuschäfer reported an issue where after 0c58a97f919c
("fuse: remove tmp folio for writebacks and internal rb tree") a
specific, but admittely not very minimal workload, involving podman
contains, x2goserver and a openjdk application restults in
suspend-to-ram hang.

The report is at https://bugs.debian.org/1120058 and information on
bisection and the test setup follows:

On Sun, Nov 30, 2025 at 02:11:13PM +0100, J. Neuschäfer wrote:
> On Fri, Nov 28, 2025 at 09:10:25PM +0100, Salvatore Bonaccorso wrote:
> > Control: found -1 6.17.8-1
> > 
> > Hi,
> > 
> > On Fri, Nov 28, 2025 at 11:50:48AM +0100, J. Neuschäfer wrote:
> > > On Wed, Nov 05, 2025 at 06:09:43AM +0100, Salvatore Bonaccorso wrote:
> [...]
> > > I can reproduce the bug fairly reliably on 6.16/17 by running a specific
> > > podman container plus x2go (not entirely sure which parts of this is
> > > necessary).
> > 
> > Okay if you have a very reliable way to reproduce it, would you be
> > open to make "your hands bit dirty" and do some bisecting on the
> > issue?
> 
> Thank you for your detailed instructions! I've already started and completed
> the git bisect run in the meantime. I had to restart a few times due to
> mistakes, but I was able to identify the following upstream commit as the
> commit that introduced the issue:
> 
> https://git.kernel.org/linus/0c58a97f919c24fe4245015f4375a39ff05665b6
> 
>     fuse: remove tmp folio for writebacks and internal rb tree
> 
> The relevant commit history is as follows:
> 
>   *   2619a6d413f4c3 Merge tag 'fuse-update-6.16' of git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/fuse  <-- bad
>   |\  
>   | * dabb9039102879 fuse: increase readdir buffer size
>   | * 467e245d47e666 readdir: supply dir_context.count as readdir buffer size hint
>   | * c31f91c6af96a5 fuse: don't allow signals to interrupt getdents copying
>   | * f3cb8bd908c72e fuse: support large folios for writeback
>   | * 906354c87f4917 fuse: support large folios for readahead
>   | * ff7c3ee4842d87 fuse: support large folios for queued writes
>   | * c91440c89fbd9d fuse: support large folios for stores
>   | * cacc0645bcad3e fuse: support large folios for symlinks
>   | * 351a24eb48209b fuse: support large folios for folio reads
>   | * d60a6015e1a284 fuse: support large folios for writethrough writes
>   | * 63c69ad3d18a80 fuse: refactor fuse_fill_write_pages()
>   | * 3568a956932621 fuse: support large folios for retrieves
>   | * 394244b24fdd09 fuse: support copying large folios
>   | * f09222980d7751 fs: fuse: add dev id to /dev/fuse fdinfo
>   | * 18ee43c398af0b docs: filesystems: add fuse-passthrough.rst
>   | * 767c4b82715ad3 MAINTAINERS: update filter of FUSE documentation
>   | * 69efbff69f89c9 fuse: fix race between concurrent setattrs from multiple nodes
>   | * 0c58a97f919c24 fuse: remove tmp folio for writebacks and internal rb tree              <-- first bad commit
>   | * 0c4f8ed498cea1 mm: skip folio reclaim in legacy memcg contexts for deadlockable mappings
>   | * 4fea593e625cd5 fuse: optimize over-io-uring request expiration check
>   | * 03a3617f92c2a7 fuse: use boolean bit-fields in struct fuse_copy_state
>   | * a5c4983bb90759 fuse: Convert 'write' to a bit-field in struct fuse_copy_state
>   | * 2396356a945bb0 fuse: add more control over cache invalidation behaviour
>   | * faa794dd2e17e7 fuse: Move prefaulting out of hot write path
>   | * 0486b1832dc386 fuse: change 'unsigned' to 'unsigned int'
>   *   0fb34422b5c223 Merge tag 'vfs-6.16-rc1.netfs' of git://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs   <-- good
> 
> The first and last commits shown are merge commits done by Linus Torvalds. The
> fuse-update branch was based on v6.15-rc1, under which I can't run my test due
> to an unrelated bug, so I ended up merging in 0fb34422b5c223 to test the
> commits within the fuse-update branch. e.g.:
> 
>   git reset --hard 394244b24fdd09 && git merge 0fb34422b5c223 && make clean && make
> 
> 
> I have also verified that the issue still happens on v6.18-rc7 but I wasn't
> able to revert 0c58a97f919 on top of this release, because a trivial revert
> is not possible.
> 
> My test case consists of a few parts:
> 
>  - A podman container based on the "debian:13" image (which points to
>    docker.io/library/debian via /etc/containers/registries.conf.d/shortnames.conf),
>    where I installed x2goserver and a openjdk-21-based application; It runs the
>    OpenSSH server and port 22 is exposed as localhost:2001
>  - x2goclient to start a desktop session in the container
> 
> Source code: https://codeberg.org/neuschaefer/re-workspace
> 
> I suspect, but haven't verified, that the X server in the container somehow
> uses the FUSE-emulated filesystem in the container to create a file that is
> used with mmap (perhaps to create shared pages as frame buffers).
> 
> 
> Raw bisect notes:
> 
> good:
> - v6.12.48+deb13-amd64
> - v6.12.59
> - v6.12
> - v6.14
> - v6.15-1304-g14418ddcc2c205
> - v6.15-10380-gec71f661a572
> - v6.15-10888-gb509c16e1d7cba
> - v6.15-rc7-357-g8e86e73626527e
> - v6.15-10933-g4c3b7df7844340
> - v6.15-10954-gd00a83477e7a8f
> - v6.15-rc7-366-g438e22801b1958 (CONFIG_X86_5LEVEL=y)
> - v6.15-rc4-126-g07212d16adc7a0
> - v6.15-10958-gdf7b9b4f6bfeb1    <-- first parent, 5LEVEL doesn't exist
> - v6.15-rc4-00127-g4d62121ce9b5
> - v6.15-rc7-375-g61374cc145f4a5  <-- second parent, `X86_5LEVEL=y`
> - v6.15-rc7-375-g61374cc145f4a5  <-- second parent, `X86_5LEVEL=n`
> - v6.15-11061-g7f9039c524a351: "first bad", actually good. merge of df7b9b4f6bfeb1 61374cc145f4a5
> - v6.15-11093-g0fb34422b5c223
> - v6.15-rc1-7-g0c4f8ed498cea1 + merge = v6.15-11101-gaec20ffad33068
> 
> testing:
> - v6.18-rc7 + revert: doesn't apply
> 
> weird (ssh doesn't work):
> - v6.15-rc1-1-g0486b1832dc386
> - v6.15-rc1-10-g767c4b82715ad3
> - v6.15-rc1-13-g394244b24fdd09: folio stuff
> - v6.15-rc1-22-gf3cb8bd908c72e
> - v6.15-rc1-23-gc31f91c6af96a5
> - next-20251128
> 
> bad:
> - v6.15-rc1-8-g0c58a97f919c24 + merge = v6.15-11102-gdfc4869c8ef1f0  first bad commit
> - v6.15-rc1-9-g69efbff69f89c9 + merge = v6.15-11103-ga7b103c57680ce
> - v6.15-rc1-11-g18ee43c398af0b + merge = v6.15-11105-g4ad0d4fa61974c
> - v6.15-rc1-13-g394244b24fdd09 + merge = v6.15-11107-g37da056b3b873b
> - v6.15-11119-g2619a6d413f4c3: merge of 0fb34422b5c223 (last good) dabb9039102879 (fuse branch)
> - v6.15-11165-gfd1f8473503e5b: confirmed bad
> - v6.15-11401-g69352bd52b2667
> - v6.15-12422-g2c7e4a2663a1ab
> - regulator-fix-v6.16-rc2-372-g5c00eca95a9a20
> - v6.16.12
> - v6.16.12 again
> - v6.16.12+deb14+1-amd64
> - v6.18-rc7

Would that ring some bells to you which make this tackable?

Regards,
Salvatore

[toc] | [prev] | [next] | [standalone]

#90929 — Bug#1120058: marked as done (linux-image-6.16.12+deb14+1-amd64: suspend-to-RAM results in hang (AMD Ryzen 5 5625U))

[Multipart message — attachments visible in raw view] — view raw

Your message dated Fri, 23 Jan 2026 09:58:29 +0000
with message-id <E1vjDvx-0000000DV6B-41Ty@fasolo.debian.org>
and subject line Bug#1120058: fixed in linux 6.19~rc6-1~exp1
has caused the Debian Bug report #1120058,
regarding linux-image-6.16.12+deb14+1-amd64: suspend-to-RAM results in hang (AMD Ryzen 5 5625U)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
1120058: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1120058
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web