Bug#1053825: Screensaver with only blank does not work after suspend
Am Mo den 1. Jan 2024 um 13:06 schrieb Bastian Blank: > I just realized that this system is in an unsupported state. Bookworm > and later is not longer supported without merged-/usr, see > https://www.debian.org/releases/stable/amd64/release-notes/ch-information.en.html#a-merged-usr-is-now-required > > Please reinstall from scratch and report back if it is still broken. It is not possible to reinstall all the systems that are not supported only cause the stupidity of systemd evangelists to understand a proper setup system! That even does not have any efect to kernel behavior except that kernel is not able to find stuff under /usr! > Maybe please also describe how you got into this state, where /lib is > not a symlink to /usr/lib. I installed the system. Regards Klaus -- Klaus Ethgen http://www.ethgen.ch/ pub 4096R/4E20AF1C 2011-05-16Klaus Ethgen Fingerprint: 85D4 CA42 952C 949B 1753 62B3 79D0 B06F 4E20 AF1C signature.asc Description: PGP signature
Processed: Re: Bug#1053825: Screensaver with only blank does not work after suspend
Processing control commands: > severity -1 normal Bug #1053825 [src:linux] Screensaver with only blank does not work after suspend Severity set to 'normal' from 'serious' -- 1053825: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053825 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1053825: Screensaver with only blank does not work after suspend
Control: severity -1 normal Hi Klaus On Thu, Oct 12, 2023 at 06:57:20AM +0100, Klaus Ethgen wrote: > -- System Information: > Debian Release: trixie/sid > merged-usr: no I just realized that this system is in an unsupported state. Bookworm and later is not longer supported without merged-/usr, see https://www.debian.org/releases/stable/amd64/release-notes/ch-information.en.html#a-merged-usr-is-now-required Please reinstall from scratch and report back if it is still broken. Maybe please also describe how you got into this state, where /lib is not a symlink to /usr/lib. Bastian
Bug#1053825: Screensaver with only blank does not work after suspend
Hi Salvatore, Thanks for helping keeping the bug alive. Am Mi den 27. Dez 2023 um 21:24 schrieb Salvatore Bonaccorso: > > That would take many time to recompile kernel, test it for several hours > > and try again. > > I do realize, but given we have nobody else reporting similar > behaviour we need to rely on you bisecting the breaking change so it > might be reported upstream. But that said, in meanwhile we have > 6.6.8-1 uploaded to unstable. It would be great if you can report back > if that version resolves the issue. Unfortunately it is not fixed. But the bug did show up after longer sleep only. > If it's still reproducibe, check first that it's as well reproducible > with an untained kernel because othwerise an upstream report might not > be accepted. > > Can you check that? It is reproducible with an untainted kernel but not easily. I have no way to reliable trigger the bug but it happens always after longer sleeps. With the new (6.6.8) kernel I see also two further "bugs": - Drawing on the screen sometimes create artefacts for lines that stay on the screen for some time. Maybe that is related as I think it happens on AMDGPU... - The second bug is not related. I connect a logitech MX Anywhere 3 via bluetooth. With that the rate of the mouse wheel did switch to a very unusable low rate. I can switch the wheel to high speed but when I go back to the working kernel, that is unusable fast. Also with the broken kernel, even with high speed, it delay the mouse wheel somewhat. As there are many stacks in between, I have no idea, which part of the stack produces that error. Maybe you might help? Regards Klaus -- Klaus Ethgen http://www.ethgen.ch/ pub 4096R/4E20AF1C 2011-05-16Klaus Ethgen Fingerprint: 85D4 CA42 952C 949B 1753 62B3 79D0 B06F 4E20 AF1C signature.asc Description: PGP signature
Bug#1053825: Screensaver with only blank does not work after suspend
Hi Salvatore, Am Mi den 27. Dez 2023 um 21:24 schrieb Salvatore Bonaccorso: > I do realize, but given we have nobody else reporting similar > behaviour we need to rely on you bisecting the breaking change so it > might be reported upstream. But that said, in meanwhile we have > 6.6.8-1 uploaded to unstable. It would be great if you can report back > if that version resolves the issue. I already installed the kernel and test it. As a site note, it does not work with dkms anymore as the header links are in /usr/lib/modules where no kernel is able to find them. However, I will keep an eye on it and see if the bug is fixed (as I did with the kernels in between.) Give me some time as the bug is not that relyable. > If it's still reproducibe, check first that it's as well reproducible > with an untained kernel because othwerise an upstream report might not > be accepted. On that system I use untained kernel (I did not on a different system with nvidia, but there I use my own kernel and the bug is related to amd GPU.) Regards Klaus -- Klaus Ethgen http://www.ethgen.ch/ pub 4096R/4E20AF1C 2011-05-16Klaus Ethgen Fingerprint: 85D4 CA42 952C 949B 1753 62B3 79D0 B06F 4E20 AF1C signature.asc Description: PGP signature
Bug#1053825: Screensaver with only blank does not work after suspend
Hi Klaus, On Sat, Oct 21, 2023 at 08:34:55AM +0100, Klaus Ethgen wrote: > Hi, > > Am Do den 19. Okt 2023 um 20:46 schrieb Salvatore Bonaccorso: > > On Thu, Oct 12, 2023 at 06:57:20AM +0100, Klaus Ethgen wrote: > > > Package: src:linux > > > Version: 6.5.6-1 > > > Severity: critical > > > Tags: security > > > X-Debbugs-Cc: Debian Security Team > > > > > > It is not fully clear for me, where exactly this bug happens. First I > > > was thinking about xscreensaver but that package got not updated for > > > ages. The bug happens with updates from kernel 6.4.0 to 6.5.0. > > > > So you are saying this happens solely after switching from 6.4.y > > series to 6.5.y series. Thus I assume 6.5.3-1 in testing as well > > exposes the issue. > > Might be but I cannot test that due to the other AMD display related > bug. > > > > I use xscreensaver with fvwm3 on my amd laptop. xscreensaver is set up > > > to only blank the screen. > > I first thought, that it does not happen with fvwm2 but I also see it > with fvwm2 but not that often. > > > > When I lock the screen and press a key or moving the mouse, everything > > > is fine. But when I go to suspend too ram after locking and waking up > > > the laptop, the password dialog gets showed as usual but I can see the > > > full desktop content with probably sensitive material on in. Although, I > > > cannot interact with the desktop, it is a security break to reveal the > > > content without authenticating. > > > > > > It might be related, when I have a PSI chat window on the screen but on > > > different desktop, it gets moved to the current one. That definitively > > > also came with the new kernel. > > > > Can you please attach as well the kernel log once you triggered the > > behaviour? Anything suspicious logged? > > I could. But there is no hint and no unusual log entry. > > > Next, can you bisect the kernel between a good known upstream version > > and 6.5.6? Can you as well test 6.5.7 upstream to see if it fixes the > > issue? > > That would take many time to recompile kernel, test it for several hours > and try again. I do realize, but given we have nobody else reporting similar behaviour we need to rely on you bisecting the breaking change so it might be reported upstream. But that said, in meanwhile we have 6.6.8-1 uploaded to unstable. It would be great if you can report back if that version resolves the issue. If it's still reproducibe, check first that it's as well reproducible with an untained kernel because othwerise an upstream report might not be accepted. Can you check that? Regards, Salvatore
Bug#1053825: Screensaver with only blank does not work after suspend
Hi, Am Do den 19. Okt 2023 um 20:46 schrieb Salvatore Bonaccorso: > Can you please attach as well the kernel log once you triggered the > behaviour? Anything suspicious logged? Here is the log of one sleep and wakeup where I had the issue: [130045.885692] r8169 :01:00.0 eth0: Link is Down [130046.577482] PM: suspend entry (s2idle) [130046.577610] Filesystems sync: 0.000 seconds [130046.577999] (NULL device *): firmware: direct-loading firmware ath11k/WCN6855/hw2.1/regdb.bin [130046.578143] (NULL device *): firmware: direct-loading firmware ath11k/WCN6855/hw2.1/m3.bin [130046.578406] (NULL device *): firmware: direct-loading firmware regulatory.db [130046.578415] (NULL device *): firmware: direct-loading firmware regulatory.db.p7s [130046.582058] (NULL device *): firmware: direct-loading firmware ath11k/WCN6855/hw2.1/amss.bin [130046.582223] (NULL device *): firmware: direct-loading firmware ath11k/WCN6855/hw2.1/board-2.bin [130046.638817] Freezing user space processes [130046.640672] Freezing user space processes completed (elapsed 0.001 seconds) [130046.640680] OOM killer disabled. [130046.640682] Freezing remaining freezable tasks [130046.642003] Freezing remaining freezable tasks completed (elapsed 0.001 seconds) [130046.642010] printk: Suspending console(s) (use no_console_suspend to debug) [130046.644003] wlan0: deauthenticating from xx:xx:xx:xx:xx:xx by local choice (Reason: 3=DEAUTH_LEAVING) [130046.833356] ACPI: EC: interrupt blocked [130048.458201] ACPI: EC: interrupt unblocked [130048.646436] [drm] PCIE GART of 1024M enabled (table at 0x00F43FC0). [130048.646479] amdgpu :04:00.0: amdgpu: SMU is resuming... [130048.650454] amdgpu :04:00.0: amdgpu: SMU is resumed successfully! [130048.660496] nvme nvme0: Shutdown timeout set to 10 seconds [130048.665582] nvme nvme0: 16/0/0 default/read/poll queues [130048.758856] [drm] VCN decode and encode initialized successfully(under DPG Mode). [130048.758941] [drm] JPEG decode initialized successfully. [130048.758949] amdgpu :04:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0 [130048.758954] amdgpu :04:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0 [130048.758957] amdgpu :04:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0 [130048.758960] amdgpu :04:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 5 on hub 0 [130048.758962] amdgpu :04:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 6 on hub 0 [130048.758964] amdgpu :04:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 7 on hub 0 [130048.758966] amdgpu :04:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 8 on hub 0 [130048.758969] amdgpu :04:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 9 on hub 0 [130048.758971] amdgpu :04:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 10 on hub 0 [130048.758974] amdgpu :04:00.0: amdgpu: ring kiq_0.2.1.0 uses VM inv eng 11 on hub 0 [130048.758976] amdgpu :04:00.0: amdgpu: ring sdma0 uses VM inv eng 12 on hub 0 [130048.758978] amdgpu :04:00.0: amdgpu: ring vcn_dec_0 uses VM inv eng 0 on hub 8 [130048.758981] amdgpu :04:00.0: amdgpu: ring vcn_enc_0.0 uses VM inv eng 1 on hub 8 [130048.758983] amdgpu :04:00.0: amdgpu: ring vcn_enc_0.1 uses VM inv eng 4 on hub 8 [130048.758985] amdgpu :04:00.0: amdgpu: ring jpeg_dec uses VM inv eng 5 on hub 8 [130048.768693] r8169 :01:00.0 eth0: Link is Down [130048.778010] OOM killer enabled. [130048.778015] Restarting tasks ... done. [130048.781711] random: crng reseeded on system resumption [130048.797062] PM: suspend exit Unlike I seen before, fvwm2 is also affected. Also it is not that relyable to reproduce. Some times it needs extendet sleeping time and in the other moment it happens directly after going to sleep. It looks like the display is drawed in the wrong direction, first the blacking out from the screensaver and afterwards the content of my desktop gets drawed above it. And when it happens, it is pretty slow (for that machine). It takes about one or two seconds. Note also that there is no S3 on that system available. The system only went to S2. Regards Klaus -- Klaus Ethgen http://www.ethgen.ch/ pub 4096R/4E20AF1C 2011-05-16Klaus Ethgen Fingerprint: 85D4 CA42 952C 949B 1753 62B3 79D0 B06F 4E20 AF1C signature.asc Description: PGP signature
Bug#1053825: Screensaver with only blank does not work after suspend
Hi, Am Do den 19. Okt 2023 um 20:46 schrieb Salvatore Bonaccorso: > On Thu, Oct 12, 2023 at 06:57:20AM +0100, Klaus Ethgen wrote: > > Package: src:linux > > Version: 6.5.6-1 > > Severity: critical > > Tags: security > > X-Debbugs-Cc: Debian Security Team > > > > It is not fully clear for me, where exactly this bug happens. First I > > was thinking about xscreensaver but that package got not updated for > > ages. The bug happens with updates from kernel 6.4.0 to 6.5.0. > > So you are saying this happens solely after switching from 6.4.y > series to 6.5.y series. Thus I assume 6.5.3-1 in testing as well > exposes the issue. Might be but I cannot test that due to the other AMD display related bug. > > I use xscreensaver with fvwm3 on my amd laptop. xscreensaver is set up > > to only blank the screen. I first thought, that it does not happen with fvwm2 but I also see it with fvwm2 but not that often. > > When I lock the screen and press a key or moving the mouse, everything > > is fine. But when I go to suspend too ram after locking and waking up > > the laptop, the password dialog gets showed as usual but I can see the > > full desktop content with probably sensitive material on in. Although, I > > cannot interact with the desktop, it is a security break to reveal the > > content without authenticating. > > > > It might be related, when I have a PSI chat window on the screen but on > > different desktop, it gets moved to the current one. That definitively > > also came with the new kernel. > > Can you please attach as well the kernel log once you triggered the > behaviour? Anything suspicious logged? I could. But there is no hint and no unusual log entry. > Next, can you bisect the kernel between a good known upstream version > and 6.5.6? Can you as well test 6.5.7 upstream to see if it fixes the > issue? That would take many time to recompile kernel, test it for several hours and try again. Even worse, there is another AMD related bug that makes testing impossible. > Currently there is nothing which sound similar in the kernel > regression tracking status, TTBOMK. There was many changes in AMD display code. Some of them already was broken for systems (laptops) with internal display (eDP). The mentioned bug was fixed between linux-image-6.5.0-1-amd64 and linux-image-6.5.0-2-amd64. (It broke between linux-image-6.4.0-4-amd64 and linux-image-6.5.0-1-amd64.) So, this is the history in upstream versions: 6.4.13: Works well 6.5.3: Two bugs, this bug and another related to scaling. 6.5.6: Bug related to scaling fixed and this bug fully visible. I believe that it is related to eDP. So, maybe that limit's the possible problem. I have a work laptop that shows only this bug on AMD system but not the scaling one (As it has no 4K resolution). But I cannot use that one for testing. Maybe another data point: Both laptops are from Lenovo. My private one is a T14GEN3 and the one for work is a Z16. Regards Klaus -- Klaus Ethgen http://www.ethgen.ch/ pub 4096R/4E20AF1C 2011-05-16Klaus Ethgen Fingerprint: 85D4 CA42 952C 949B 1753 62B3 79D0 B06F 4E20 AF1C signature.asc Description: PGP signature
Bug#1053825: Screensaver with only blank does not work after suspend
Hi, On Thu, Oct 12, 2023 at 06:57:20AM +0100, Klaus Ethgen wrote: > Package: src:linux > Version: 6.5.6-1 > Severity: critical > Tags: security > X-Debbugs-Cc: Debian Security Team > > It is not fully clear for me, where exactly this bug happens. First I > was thinking about xscreensaver but that package got not updated for > ages. The bug happens with updates from kernel 6.4.0 to 6.5.0. So you are saying this happens solely after switching from 6.4.y series to 6.5.y series. Thus I assume 6.5.3-1 in testing as well exposes the issue. > I use xscreensaver with fvwm3 on my amd laptop. xscreensaver is set up > to only blank the screen. > > When I lock the screen and press a key or moving the mouse, everything > is fine. But when I go to suspend too ram after locking and waking up > the laptop, the password dialog gets showed as usual but I can see the > full desktop content with probably sensitive material on in. Although, I > cannot interact with the desktop, it is a security break to reveal the > content without authenticating. > > It might be related, when I have a PSI chat window on the screen but on > different desktop, it gets moved to the current one. That definitively > also came with the new kernel. Can you please attach as well the kernel log once you triggered the behaviour? Anything suspicious logged? Next, can you bisect the kernel between a good known upstream version and 6.5.6? Can you as well test 6.5.7 upstream to see if it fixes the issue? Currently there is nothing which sound similar in the kernel regression tracking status, TTBOMK. Regards, Salvatore
Bug#1053825: Screensaver with only blank does not work after suspend
Package: src:linux
Version: 6.5.6-1
Severity: critical
Tags: security
X-Debbugs-Cc: Debian Security Team
It is not fully clear for me, where exactly this bug happens. First I
was thinking about xscreensaver but that package got not updated for
ages. The bug happens with updates from kernel 6.4.0 to 6.5.0.
I use xscreensaver with fvwm3 on my amd laptop. xscreensaver is set up
to only blank the screen.
When I lock the screen and press a key or moving the mouse, everything
is fine. But when I go to suspend too ram after locking and waking up
the laptop, the password dialog gets showed as usual but I can see the
full desktop content with probably sensitive material on in. Although, I
cannot interact with the desktop, it is a security break to reveal the
content without authenticating.
It might be related, when I have a PSI chat window on the screen but on
different desktop, it gets moved to the current one. That definitively
also came with the new kernel.
-- Package-specific info:
** Version:
Linux version 6.5.0-2-amd64 (debian-kernel@lists.debian.org) (gcc-13 (Debian
13.2.0-5) 13.2.0, GNU ld (GNU Binutils for Debian) 2.41) #1 SMP PREEMPT_DYNAMIC
Debian 6.5.6-1 (2023-10-07)
** Command line:
BOOT_IMAGE=/root/boot/vmlinuz-6.5.0-2-amd64
root=UUID=b4992631-80af-4a02-b8f8-ecd8f2a51c95 ro rootflags=subvol=root quiet
** Tainted: WOE (12800)
* kernel issued warning
* externally-built ("out-of-tree") module was loaded
* unsigned module was loaded
** Kernel log:
Unable to read kernel log; any relevant messages should be attached
** Model information
sys_vendor: LENOVO
product_name: 21CGS0LE00
product_version: ThinkPad T14 Gen 3
chassis_vendor: LENOVO
chassis_version: None
bios_vendor: LENOVO
bios_version: R23ET62W (1.32 )
board_vendor: LENOVO
board_name: 21CGS0LE00
board_version: ThinkPad
** Loaded modules:
uhid
tun
ctr
ccm
michael_mic
vboxnetadp(OE)
vboxnetflt(OE)
cmac
algif_hash
bnep
rfcomm
vboxdrv(OE)
uinput
nf_tables
nfnetlink
nls_ascii
nls_cp437
vfat
fat
msr
twofish_generic
twofish_avx_x86_64
twofish_x86_64_3way
twofish_x86_64
twofish_common
xts
ecb
algif_skcipher
af_alg
blowfish_generic
blowfish_x86_64
blowfish_common
essiv
authenc
crypto_null
dm_crypt
dm_mod
btusb
btrtl
btbcm
btintel
btmtk
bluetooth
sha3_generic
jitterentropy_rng
drbg
ansi_cprng
ecdh_generic
ecc
crc16
uvcvideo
videobuf2_vmalloc
uvc
videobuf2_memops
videobuf2_v4l2
videodev
videobuf2_common
mc
qrtr_mhi
joydev
snd_acp6x_pdm_dma
snd_soc_dmic
snd_soc_acp6x_mach
intel_rapl_msr
snd_soc_core
snd_compress
hid_multitouch
intel_rapl_common
hid_generic
qrtr
ath11k_pci
edac_mce_amd
snd_ctl_led
ath11k
kvm_amd
snd_hda_codec_realtek
qmi_helpers
snd_hda_codec_generic
snd_hda_codec_hdmi
kvm
mac80211
snd_hda_intel
snd_intel_dspcfg
snd_intel_sdw_acpi
snd_hda_codec
thinkpad_acpi
snd_hda_core
irqbypass
ucsi_acpi
snd_pci_acp6x
typec_ucsi
nvram
think_lmi
crc32_pclmul
snd_hwdep
libarc4
ghash_clmulni_intel
rapl
efi_pstore
firmware_attributes_class
wmi_bmof
roles
ledtrig_audio
typec
battery
ac
platform_profile
snd_pcm_oss
i2c_hid_acpi
i2c_hid
snd_mixer_oss
xhci_pci
cfg80211
snd_pcm
hid
xhci_hcd
r8169
snd_timer
snd_pci_acp5x
realtek
usbcore
snd_rn_pci_acp3x
snd
snd_acp_config
rfkill
mdio_devres
snd_soc_acpi
soundcore
ccp
mhi
snd_pci_acp3x
usb_common
amd_pmc
button
acpi_tad
libphy
sp5100_tco
watchdog
k10temp
i2c_piix4
efivarfs
btrfs
blake2b_generic
libcrc32c
crc32c_generic
xor
raid6_pq
amdgpu
i2c_algo_bit
drm_ttm_helper
ttm
drm_suballoc_helper
amdxcp
drm_buddy
gpu_sched
drm_display_helper
drm_kms_helper
crc32c_intel
nvme
drm
nvme_core
aesni_intel
t10_pi
psmouse
crypto_simd
cryptd
evdev
cec
serio_raw
crc64_rocksoft
crc64
crc_t10dif
rc_core
crct10dif_generic
crct10dif_pclmul
crct10dif_common
video
fan
wmi
sha512_ssse3
sha512_generic
** PCI devices:
00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h-19h
PCIe Root Complex [1022:14b5] (rev 01)
Subsystem: Lenovo Device [17aa:50b6]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR-
00:01.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h-19h
PCIe Dummy Host Bridge [1022:14b7] (rev 01)
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities:
Kernel driver in use: pcieport
00:02.2 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Family 17h-19h
PCIe GPP Bridge [1022:14ba] (prog-if 00 [Normal decode])
Subsystem: Lenovo Device [17aa:50b6]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbor
