XPost: linux.debian.bugs.dist
From: vesely@tana.it

Package: src:linux
Version: 6.1.140-1
Severity: normal

Dear Maintainer,

On resume, after reading back all saved memory and after displaying the "Suspending console(s) (use no_console_suspend to debug)" message, instead of returning to the previous screen, it stay there and does not seem to react. Switching to and from virtual console, ctrl-alt-f1 + ctrl-alt-f7, results in a damaged screen where only the upper left corner is correct while the rest replicates whatever was on the previous pixel.

Also, it used to thaw hitting any key. Now I must hit the power button.

The log shows:
...
2025-06-09T15:47:57.503014+02:00 pcale avahi-daemon[2584]: Registering new address record for 172.25.197.120 on eth0.IPv4. 2025-06-09T15:47:58.071694+02:00 pcale dhclient[17977]: bound to 172.25.197.120 -- renewal in 37592 seconds.
2025-06-09T15:47:58.123888+02:00 pcale /etc/pm/sleep.d/20_dhcp-lease: run thaw hibernate, rtc=0
2025-06-09T15:47:59.024989+02:00 pcale /home/ale/bin/run-pm-hibernate: /sbin/pm-hibernate returned 0
2025-06-09T15:49:43.244897+02:00 pcale /home/ale/bin/run-pm-hibernate: slock returned 0
2025-06-09T15:50:00.034948+02:00 pcale kernel: [12650.230373] [drm] pstate TEST_DEBUG_DATA: 0x3EFF000F
2025-06-09T15:50:00.034961+02:00 pcale kernel: [12650.231494] [drm] pstate TEST_DEBUG_DATA: 0x3EFF000F
2025-06-09T15:50:00.034962+02:00 pcale kernel: [12650.231942] [drm] pstate TEST_DEBUG_DATA: 0x3EFF000F
...

Here 20_dhcp-lease is a short script to release the IP address before sleeping, and log; run-pm-hibernate is a suid utility to call pm-hibernate (and slock) from the openbox menu.

The pstate message repeats until I reboot. What does it mean?

I have this default, in case it has anything to do with pstate:
ale@pcale:~$ cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_driver acpi-cpufreq

Also, earlier in the log I had a drm warning. Dunno if it's relevant. I paste it below.

2025-06-09T15:47:50.942302+02:00 pcale kernel: [12516.715362] ------------[ cut here ]------------
2025-06-09T15:47:50.942303+02:00 pcale kernel: [12516.715363] amdgpu 0000:09:00.0: drm_WARN_ON_ONCE(!dev->mode_config.poll_enabled) 2025-06-09T15:47:50.942304+02:00 pcale kernel: [12516.715393] WARNING: CPU: 2 PID: 17736 at drivers/gpu/drm/drm_probe_helper.c:252 drm_kms_helper_poll_enable+0x116/0x130 [drm_kms_helper] 2025-06-09T15:47:50.942306+02:00 pcale kernel: [12516.715412] Modules linked in: nls_ascii nls_cp437 vfat fat xt_conntrack xt_MASQUERADE nf_conntrack_netlink xfrm_user xfrm_algo iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xt_addrtype iptable_filter ip_tables x_tables br_netfilter bridge stp llc overlay bnep bluetooth jitterentropy_rng drbg ansi_cprng ecdh_generic ecc autofs4 cpufreq_userspace cpufreq_ondemand cpufreq_powersave cpufreq_conservative binfmt_misc nf_tables libcrc32c nfnetlink f2fs crc32_generic lz4hc_compress lz4_compress zstd_compress parport_pc ppdev lp parport intel_rapl_msr intel_rapl_common edac_mce_amd amdgpu kvm irqbypass pktcdvd ghash_clmulni_intel sha512_ssse3 sha512_generic sha256_ssse3 gpu_sched sha1_ssse3 drm_buddy drm_display_helper aesni_intel snd_hda_codec_realtek snd_hda_codec_hdmi snd_hda_codec_generic crypto_simd cryptd snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi cec snd_hda_codec evdev rc_core rapl snd_hda_core drm_ttm_helper tt
m eeepc_wmi snd_hwdep drm_kms_helper snd_pcm
2025-06-09T15:47:50.942371+02:00 pcale kernel: [12516.715489] snd_timer asus_wmi battery snd platform_profile drm soundcore sparse_keymap ledtrig_audio rfkill i2c_algo_bit pcspkr wmi_bmof ccp serio_raw sp5100_tco watchdog k10temp button acpi_cpufreq ext4 crc16 mbcache jbd2 crc32c_generic hid_generic usbhid uas sr_mod sg hid usb_storage cdrom sd_mod ahci libahci nvme xhci_pci libata nvme_core xhci_hcd r8169 realtek t10_pi crc32_pclmul mdio_devres crc32c_intel psmouse scsi_mod usbcore libphy crc64_rocksoft crc64 crc_t10dif crct10dif_generic i2c_piix4 crct10dif_pclmul crct10dif_common usb_common scsi_common video wmi gpio_amdpt gpio_generic
2025-06-09T15:47:50.942372+02:00 pcale kernel: [12516.715551] CPU: 2 PID: 17736 Comm: kworker/u64:15 Tainted: G W 6.1.0-37-amd64 #1 Debian 6.1.140-1
2025-06-09T15:47:50.942373+02:00 pcale kernel: [12516.715555] Hardware name: System manufacturer System Product Name/PRIME B450M-A, BIOS 3211 08/10/2021 2025-06-09T15:47:50.942374+02:00 pcale kernel: [12516.715557] Workqueue: events_unbound async_run_entry_fn
2025-06-09T15:47:50.942375+02:00 pcale kernel: [12516.715562] RIP: 0010:drm_kms_helper_poll_enable+0x116/0x130 [drm_kms_helper] 2025-06-09T15:47:50.942378+02:00 pcale kernel: [12516.715577] Code: 48 8b 5f 50 48 85 db 75 03 48 8b 1f e8 13 e6 97 e9 48 c7 c1 c8 57 b8 c0 48 89 da 48 c7 c7 3a 6b b8 c0 48 89 c6 e8 0a 6a 33 e9 <0f> 0b e9 39 ff ff ff e8 0e cc cc e9 66 66 2e 0f 1f 84 00 00 00 00
2025-06-09T15:47:50.942379+02:00 pcale kernel: [12516.715579] RSP: 0018:ffffa47640ce7d90 EFLAGS: 00010286
2025-06-09T15:47:50.942380+02:00 pcale kernel: [12516.715582] RAX: 0000000000000000 RBX: ffff98ba413ca880 RCX: ffff98bd6f2995e0 2025-06-09T15:47:50.942381+02:00 pcale kernel: [12516.715583] RDX: 0000000000000000 RSI: 0000000000000046 RDI: 0000000000000001 2025-06-09T15:47:50.942381+02:00 pcale kernel: [12516.715585] RBP: ffff98ba44f80010 R08: ffffffffacd81a60 R09: ffff98be6f2d5abc 2025-06-09T15:47:50.942382+02:00 pcale kernel: [12516.715587] R10: ffffffffffffffff R11: 000000002d2d2d2d R12: ffff98ba44f80000 2025-06-09T15:47:50.942382+02:00 pcale kernel: [12516.715588] R13: 0000000000000001 R14: ffff98ba44f98500 R15: ffff98ba4141f150 2025-06-09T15:47:50.942383+02:00 pcale kernel: [12516.715590] FS: 0000000000000000(0000) GS:ffff98bd60a80000(0000) knlGS:0000000000000000 2025-06-09T15:47:50.942384+02:00 pcale kernel: [12516.715592] CS: 0010 DS:

[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: u.kleine-koenig@baylibre.com

Control: tag -1 + moreinfo

Hello Alessandro,

On Tue, Jun 10, 2025 at 09:07:34AM +0200, Alessandro Vesely wrote:

On resume, after reading back all saved memory and after displaying the "Suspending console(s) (use no_console_suspend to debug)" message, instead of returning to the previous screen, it stay there and does not seem to react. Switching to and from virtual console, ctrl-alt-f1 + ctrl-alt-f7, results in a
damaged screen where only the upper left corner is correct while the rest replicates whatever was on the previous pixel.

There is a (maybe) similar bug report at
https://bugs.debian.org/1106668. I asked the reporter of that bug to
check for a BIOS update and if that doesn't help follow https://docs.kernel.org/power/basic-pm-debugging.html to debug the
issue. That would be helpful here, too. So can you please check these
and follow up with your findings?

Best regards
Uwe

-----BEGIN PGP SIGNATURE-----

iQEzBAABCgAdFiEEP4GsaTp6HlmJrf7Tj4D7WH0S/k4FAmhJ7SMACgkQj4D7WH0S /k6grQf/bemvK+q2aYX17uLOrgjE8GWxh8kK1LnMvmVSwkGRmFkWsqm1FZ8dT1Hl LoWk6X+3OhllupCD3gbbTkrDhpxM06hevFZPcjrMjvfyZOwBmmArg6U17+BgT62a zT9GtnejikUlCUylnNOx+MbQAAhy5KHBuyoSbbLM0afj/au8EcL1dDQeDYgSOBaT fKucVYzH6RxZ7nulcJYHgNKGSu+mATHVkMOHCO9xXOr4ipoFGPGDIHqkuOC2kuTs Dx0z2z4fYKQH3XrSEyuohLBn1V49lKyGfUhJ4cRpCnNqt1vudyjbOQNC9EH4Ow2l 688u0mBGrrQNxMImNS75bedZ7zRM0w==
=+t7X
-----END PGP SIGNATURE-----

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

XPost: linux.debian.bugs.dist
From: vesely@tana.it

Hi Uwe,

On Wed 11/Jun/2025 22:55:04 +0200 Uwe Kleine-König wrote:

On Tue, Jun 10, 2025 at 09:07:34AM +0200, Alessandro Vesely wrote:

On resume, after reading back all saved memory and after displaying the
"Suspending console(s) (use no_console_suspend to debug)" message, instead of
returning to the previous screen, it stay there and does not seem to react. >> Switching to and from virtual console, ctrl-alt-f1 + ctrl-alt-f7, results in a
damaged screen where only the upper left corner is correct while the rest
replicates whatever was on the previous pixel.

There is a (maybe) similar bug report at
https://bugs.debian.org/1106668.

This seems different from bug 1106668. When the "Suspending console(s)" message is displayed, besides ctrl-alt-fX, Caps and Num Locks' leds work properly. The network works, I can login with ssh.

I asked the reporter of that bug to check for a BIOS update

My BIOS doesn't seem to be overly old:

Vendor: American Megatrends Inc.
Version: 3211
Release Date: 08/10/2021

I couldn't find which/ where more recent versions exist.

and if that doesn't help follow https://docs.kernel.org/power/basic-pm-debugging.html to debug the
issue. That would be helpful here, too. So can you please check these
and follow up with your findings?

All three modes, reboot, platform and shutdown, fail in the same way described above. That is, the screen is unusable after a circuitous restore.

The freezer test works fine.

All the other tests, devices, platform, processors and core, resume to a black screen. Blindly typed commands are accepted and executed. The sequence ctrl-alt-f1 + ctrl-alt-f7 (which I called "circuitous") restores the screen to a normal state. The test_resume option, after resetting pm_test to none, behaves the same way.

Probably the system works also after a real restore, except that the screen is so broken as to make it unusable.


Best
Ale

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

XPost: linux.debian.bugs.dist
From: vesely@tana.it

Hi Uwe,

On Wed 18/Jun/2025 22:26:03 +0200 Uwe Kleine-König wrote:

So can you please check if that problem also happens with 6.12 or better still on 6.15, please?
(Note that 6.12.31 has another amdgpu bug, so please make sure to test
at least 6.12.32 (that is, take the kernel package from testing and not backports, or wait until backports are updated accordingly);
experimental has 6.15.)

I found that before installing linux-image-6.1.0-37-amd64 I ran linux-image-6.1.0-34-amd64, which worked:

ale@pcale:~/tmp$ dpkg -l linux-image\* |tail -6
rc linux-image-6.1.0-34-amd64 6.1.135-1 amd64 Linux 6.1 for 64-bit PCs (signed)
un linux-image-6.1.0-34-amd64-unsigned <none> <none> (no description available)
ii linux-image-6.1.0-37-amd64 6.1.140-1 amd64 Linux 6.1 for 64-bit PCs (signed)
un linux-image-6.1.0-37-amd64-unsigned <none> <none> (no description available)
ii linux-image-amd64 6.1.140-1 amd64 Linux for 64-bit PCs (meta-package)
un linux-image-generic <none> <none> (no description available)

I'm unclear about the relationship among Devuan/ Debian 6.1.0-37, 6.1.140-1 numbering and the 6.15 or 6.12 used by kernel.org. I get the following:

ale@pcale:~/tmp$ uname -a
Linux pcale 6.1.0-37-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.140-1 (2025-05-22) x86_64 GNU/Linux

and

ale@pcale:~/tmp$ dpkg -s linux-image-6.1.0-37-amd64
Package: linux-image-6.1.0-37-amd64
Status: install ok installed
Priority: optional
Section: kernel
Installed-Size: 399275
Maintainer: Debian Kernel Team <debian-kernel@lists.debian.org>
Architecture: amd64
Source: linux-signed-amd64 (6.1.140+1)
Version: 6.1.140-1
Replaces: linux-image-6.1.0-37-amd64-unsigned
Depends: kmod, linux-base (>= 4.3~), initramfs-tools (>= 0.120+deb8u2) | linux-initramfs-tool
Recommends: firmware-linux-free, apparmor
Suggests: linux-doc-6.1, debian-kernel-handbook, grub-pc | grub-efi-amd64 | extlinux
Breaks: fwupdate (<< 12-7), initramfs-tools (<< 0.120+deb8u2), wireless-regdb (<< 2019.06.03-1~)
Conflicts: linux-image-6.1.0-37-amd64-unsigned
Description: Linux 6.1 for 64-bit PCs (signed)
The Linux kernel 6.1 and modules for use on PCs with AMD64, Intel 64 or
VIA Nano processors.
.
The kernel image and modules are signed for use with Secure Boot. Built-Using: linux (= 6.1.140-1)
Homepage: https://www.kernel.org/


On the Devuan repository there is also a linux-image-6.1.0-36-amd64, which looks like the one before what I have now. I find also a linux-image-6.12.12+bpo-amd64, which as an installed size about 1/3 of and linux-image-6.1.0-37-amd64. I wonder what's
the difference. I paste both descriptions below. Would you please shed some light on what should I install?


ale@pcale:~/tmp$ apt-cache show linux-image-6.12.12+bpo-amd64
Package: linux-image-6.12.12+bpo-amd64
Version: 6.12.12-1~bpo12+1
Installed-Size: 105221
Maintainer: Debian Kernel Team <debian-kernel@lists.debian.org>
Architecture: amd64
Replaces: linux-image-6.12.12+bpo-amd64-unsigned
Depends: kmod, linux-base (>= 4.3~), initramfs-tools (>= 0.120+deb8u2) | linux-initramfs-tool
Conflicts: linux-image-6.12.12+bpo-amd64-unsigned
Breaks: fwupdate (<< 12-7), initramfs-tools (<< 0.120+deb8u2), wireless-regdb (<< 2019.06.03-1~)
Homepage: https://www.kernel.org/
Built-Using: linux (= 6.12.12-1~bpo12+1)
Recommends: apparmor
Description-en: Linux 6.12 for 64-bit PCs (signed)
The Linux kernel 6.12 and modules for use on PCs with AMD64, Intel 64 or
VIA Nano processors.
.
The kernel image is signed for use with Secure Boot.
Description-md5: 224c8e7ad16235c8d318cebf70217775
Source: linux-signed-amd64 (6.12.12+1~bpo12+1)
Suggests: firmware-linux-free, linux-doc-6.12, debian-kernel-handbook, grub-pc | grub-efi-amd64 | extlinux
Section: kernel
Priority: optional
Filename: pool/DEBIAN/main/l/linux-signed-amd64/linux-image-6.12.12+bpo-amd64_6.12.12-1~bpo12+1_amd64.deb
Size: 104999700
SHA256: 9690bbafdd63cae33cf54d63e040e017f402fcc4b4ebc678438ef133ed736bc7




ale@pcale:~/tmp$ apt-cache show linux-image-6.1.0-37-amd64
Package: linux-image-6.1.0-37-amd64
Version: 6.1.140-1
Installed-Size: 399275
Maintainer: Debian Kernel Team <debian-kernel@lists.debian.org>
Architecture: amd64
Replaces: linux-image-6.1.0-37-amd64-unsigned
Depends: kmod, linux-base (>= 4.3~), initramfs-tools (>= 0.120+deb8u2) | linux-initramfs-tool
Conflicts: linux-image-6.1.0-37-amd64-unsigned
Breaks: fwupdate (<< 12-7), initramfs-tools (<< 0.120+deb8u2), wireless-regdb (<< 2019.06.03-1~)
Homepage: https://www.kernel.org/
Built-Using: linux (= 6.1.140-1)
Recommends: firmware-linux-free, apparmor
Description-en: Linux 6.1 for 64-bit PCs (signed)
The Linux kernel 6.1 and modules for use on PCs with AMD64, Intel 64 or
VIA Nano processors.
.
The kernel image and modules are signed for use with Secure Boot. Description-md5: eaf7b81be84ec12eb25fe90a4bac0f60
Source: linux-signed-amd64 (6.1.140+1)
Suggests: linux-doc-6.1, debian-kernel-handbook, grub-pc | grub-efi-amd64 | extlinux
Section: kernel
Priority: optional
Filename: pool/DEBIAN-SECURITY/updates/main/l/linux-signed-amd64/linux-image-6.1.0-37-amd64_6.1.140-1_amd64.deb

[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: vesely@tana.it

Hi Uwe,

On Thu 26/Jun/2025 17:59:20 +0200 Uwe Kleine-König wrote:

;...]

I'm unclear about the relationship among Devuan/ Debian 6.1.0-37,
6.1.140-1 numbering and the 6.15 or 6.12 used by kernel.org. I get
the following:

I don't know if Devuan does their own kernel packaging,

They don't. The --print-uris option talls me, for example:

root@pcale:# apt-get install --print-uris linux-image-amd64-dbg
... 'http://deb.devuan.org/merged/pool/DEBIAN-SECURITY/updates/main/l/linux/linux-image-6.1.0-37-amd64-dbg_6.1.140-1_amd64.deb' linux-image-6.1.0-37-amd64-dbg_6.1.140-1_amd64.deb 853916720
'http://deb.devuan.org/merged/pool/DEBIAN-SECURITY/updates/main/l/linux/linux-image-amd64-dbg_6.1.140-1_amd64.deb' linux-image-amd64-dbg_6.1.140-1_amd64.deb 1300

But then:

root@pcale:# curl --head http://deb.devuan.org/merged/pool/DEBIAN-SECURITY/updates/main/l/linux/
HTTP/1.1 302 Found
Date: Fri, 27 Jun 2025 12:44:01 GMT
Server: Apache/2.4.62 (Debian)
Location: http://deb.debian.org/debian-security/pool/updates/main/l/linux/ Content-Type: text/html; charset=iso-8859-1

but for Debian it's as follows:
[...]

Thank you so much for clarifying. It's quite obscure.

Try installing http://deb.debian.org/debian/pool/main/l/linux-signed-amd64/linux-image-6.15-amd64_6.15.3-1~exp1_amd64.deb
. The MD5 sum should be c41ea7cd2bf35dc2ef13b6502df9dac0.

I haven't been able to find what Devuan package points there. I tried to install it directly, but got the following error:

root@pcale:# dpkg -i linux-image-6.15-amd64_6.15.3-1~exp1_amd64.deb
dpkg: regarding linux-image-6.15-amd64_6.15.3-1~exp1_amd64.deb containing linux-image-6.15-amd64, pre-dependency problem:
linux-image-6.15-amd64 pre-depends on linux-base (>= 4.12~)
linux-base is installed, but is version 4.9.

dpkg: error processing archive linux-image-6.15-amd64_6.15.3-1~exp1_amd64.deb (--install):
pre-dependency problem - not installing linux-image-6.15-amd64
Errors were encountered while processing:
linux-image-6.15-amd64_6.15.3-1~exp1_amd64.deb


I got more errors when trying to install linux-base 4.12. Then I didn't insist because something sounds wrong: If I'm trying to install a previous version of the kernel, how come it depends to a subsequent version of linux-base? In fact, I cannot find
6.15 in the cache:

root@pcale:# apt-cache search linux-image| grep 6.15
root@pcale:#

The highest I can find with apt-cache is a 6.12.27 backport:

root@pcale:# apt-get install --print-uris linux-image-6.12.27+bpo-rt-amd64
... 'http://deb.devuan.org/merged/pool/DEBIAN/main/l/linux-signed-amd64/linux-image-6.12.27%2bbpo-rt-amd64_6.12.27-1%7ebpo12%2b1_amd64.deb' linux-image-6.12.27+bpo-rt-amd64_6.12.27-1~bpo12+1_amd64.deb 107428604

Which is redirected to an URL in the same directory as the 6.15 you suggested: Location: http://deb.debian.org/debian/pool/main/l/linux-signed-amd64/linux-image-6.12.27+bpo-rt-amd64_6.12.27-1~bpo12+1_amd64.deb


Thinking again, maybe it would be more productive to try and install the latest kernel, in case the problem is fixed there.

What you think?


Best
Ale

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