Suspend fails (only) when external monitor is connected

seth · 2025-05-06 16:49:29

From the moment I turned on the monitor again, we're back to resuming from suspend automatically...

The monitor will generate some input, maybe CEC - except you tries a non-Tv, what makes that unlikely.

apr 26 19:58:11 mysystem kernel: input: HDA NVidia HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:01.1/0000:01:00.1/sound/card1/input25
apr 26 19:58:11 mysystem kernel: input: HDA NVidia HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:01.1/0000:01:00.1/sound/card1/input26
apr 26 19:58:11 mysystem kernel: input: HDA NVidia HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:01.1/0000:01:00.1/sound/card1/input27
apr 26 19:58:11 mysystem kernel: input: HDA NVidia HDMI/DP,pcm=9 as /devices/pci0000:00/0000:00:01.1/0000:01:00.1/sound/card1/input28]/code]
Did you at some point disable [code]GPP0	  S4	*enabled   pci:0000:00:01.1
GPP1	  S3	*enabled   pci:0000:00:01.2[/code]
echo GPP0 | sudo tee /proc/acpi/wakeup
echo GPP1 | sudo tee /proc/acpi/wakeup
grep GPP /proc/acpi/wakeup

?

mwohah · 2025-05-06 18:38:45

seth wrote:

The monitor will generate some input, maybe CEC - except you tries a non-Tv, what makes that unlikely.

The monitor does actually support CEC, so not a bad hunch, but it's disabled (I tested enabling and disabling it). It's also happening with another, older, 1080p monitor that doesn't support any fancy new features.

seth wrote:

Did you at some point disable

GPP0	  S4	*enabled   pci:0000:00:01.1
GPP1	  S3	*enabled   pci:0000:00:01.2

Yes, I tried disabling absolutely everything in /proc/acpi/wakeup.

seth · 2025-05-06 20:27:31

Do(es) the monitor(s) also support https://wiki.archlinux.org/title/Displa … (E-)DDC/CI ?
For the TV, how does it behave if you keep it connected and on, but on a different input source (other HDMI device, actual TV)?

Do you have access to an https://en.wikipedia.org/wiki/AV_receiver that you could plug inbetween as "filter"?

mwohah · 2025-05-07 18:20:04

seth wrote:

Do(es) the monitor(s) also support https://wiki.archlinux.org/title/Displa … (E-)DDC/CI ?

Yes, my main one does. I don't ordinarily have ddcutil installed but I can use it to set the brightness of the monitor, for example.

seth wrote:

For the TV, how does it behave if you keep it connected and on, but on a different input source (other HDMI device, actual TV)?

The problem also occurs in this case. I guess this makes some sense since if I connect over USB-C to my Linux box and have it set to input source HDMI for another device, it still never stops being registered as monitor in Linux (the monitor just isn't displaying that source right now but it is connected, in other words), but still a good idea to verify it.

seth wrote:

Do you have access to an https://en.wikipedia.org/wiki/AV_receiver that you could plug inbetween as "filter"?

I assume this should ideally be a modern one that has a HDMI in and out so it can filter out the audio. I unfortunately don't have one to test with.

I do have a Dell USB-C dock that has HDMI, DisplayPort and USB-C ports. Not entirely the same as an AV receiver, but I tried it nonetheless because the monitor then isn't directly connected to the laptop any more; the problem also occurs here, though.

Last edited by mwohah (2025-05-07 18:21:34)

seth · 2025-05-07 21:44:14

https://www.reddit.com/r/framework/comm … l_monitor/
https://askubuntu.com/questions/1311948 … 48#1442548

Though…

Something I noticed, but might not be strange, is that if I plug in the monitor after the system is already in sleep, it doesn't wake up.

mwohah · 2025-05-10 18:37:04

seth wrote:

https://www.reddit.com/r/framework/comm … l_monitor/
Though…
Something I noticed, but might not be strange, is that if I plug in the monitor after the system is already in sleep, it doesn't wake up.

I usually leave my laptop lid open when trying suspend, so I tested clamshell as well, but... you guessed it: same result.

seth wrote:

https://askubuntu.com/questions/1311948 … 48#1442548

Hmm, the input auto switching of the monitor also comes back here. Unfortunately something that I already tried disabling and had no effect.

When I just lock my screen, the monitor doesn't 'cancel' the locking and come back online, though, but it was also something interesting to try.

What did trigger me a bit is that I do sometimes have the issue that a disabled laptop/internal monitor doesn't properly disable when logging in using GDM; it remains black, but instead of being turned off the backlight stays on and you see a TTY or terminal underscore in the upper-left corner. It rarely happens and apart from eating power seems relatively harmless. Probably not related to this problem, but I thought I'd mention it for completeness.

I think at this point it's probably best to log a bug somewhere, but I'm still not entirely sure where, I'm not entirely sure it's an NVIDIA driver bug since nouveau without GSP also causes it (could still be something caused by both), it could be a kernel bug, or it could be a BIOS issue. I think this bit is important though:

When the cable is connected before entering sleep, sleep fails when the monitor is turned on hardware-wise.
When the cable is connected before entering sleep, sleep works when the monitor is turned off hardware-wise.
When the cable is connected before entering sleep, sleep fails when the monitor is turned off software-wise (GNOME).
When the cable is disconnected before entering sleep, sleep works.

So... apparently having the monitor connected is okay as long as it didn't have power. If it was on, even if it's not used at all, apparently just having it recognised as connected is enough to trigger the issue. Is the detection of monitors outside actually rendering them handled by the Linux kernel and thus perhaps shared by the NVIDIA driver and nouveau? That would imply a kernel issue is most likely?

seth · 2025-05-10 22:16:34

Cutting power from the monitor is close to pulling the cable (the output probably shows up as "disconnected"?)
The system falls asleep, but is then woken up - that's the firmware/prebootsystem/bios/uefi
Speaking of which, can you actually configure wakeup triggers in the UEFI settings?

Other than that, the outputs are detected by the hardware and then exposed to the OS via the driver.
You could test booting "nomodeset" and I suspect that even then the monitor wakes the system.

It would be interesting to know how windows behaves (ie. is there a way around this at all), but a separate software stack like grml.org might be worth a shot (different kernel, nouveau, you're booting from USB - a lot of things but hardware and firmware change)

mwohah · 2025-05-13 18:39:34

seth wrote:

Speaking of which, can you actually configure wakeup triggers in the UEFI settings?

A few, yes, but mostly unrelated to this, such as automatic boot on lid open, automatic boot on AC connect, and so on. Nothing related to s2idle suspend settings or anything of the sort.

Some Lenovo models have hidden BIOS unlocking shortcuts, but none of those (I tried at least three different types) work for this model - I was hoping to find some way to enable s2idle before this way.

seth wrote:

Other than that, the outputs are detected by the hardware and then exposed to the OS via the driver.
You could test booting "nomodeset" and I suspect that even then the monitor wakes the system.
It would be interesting to know how windows behaves (ie. is there a way around this at all), but a separate software stack like grml.org might be worth a shot (different kernel, nouveau, you're booting from USB - a lot of things but hardware and firmware change)

I tried grml but it fails to suspend entirely, as in: the screen goes black and immediately comes back. The console doesn't log anything out of the ordinary beyond what my Arch system already logs.

I then also tried Xubuntu 25.04 with nouveau, and it indeed has the exact same issue.

frostbittenking · 2025-05-14 07:15:38

Sry no contribution except for I noticed too broken sleep / wakeup on my tuxedo work notebook. Crasht / failed to resume the third time within a week or so
Really frustrating when I have to sysreq reisub and lose time due to all open stuff gone again. Yes saved everything. No lost work but still wasted time. It's annoying. Gonna check the thread on the weekend and try to gather info what's on. Annying. A few months ago the USB thing after resume that USB wasn't detected after reboot now this. Come on Linus don't fail me like that.

seth · 2025-05-14 07:41:06

The OPs problem is that the external output immediately wakes the system, not a crash-on-resume.
Also nvidia? => https://bbs.archlinux.org/viewtopic.php … 0#p2240550

frostbittenking · 2025-05-16 07:00:26

I believe they're all connected. Also not exactly what you describe but with this kernel my tuxedo randomly wakes up when connected to the docking station. I'm betting my ass it's all connected to the same changes in power management or something like that in this kernel.

seth · 2025-05-16 19:47:04

Do you have an nvidia GPU and do you have these problems w/ the 535xx driver?

frostbittenking · 2025-05-17 09:15:21

Neither but it smells to me like this is an issue that isn't specifically to nvidia. Guess I'm going back to hibernation and watch this unfold.

seth · 2025-05-17 11:33:43

After watching it, also post the journal

frostbittenking · 2025-05-17 11:55:13

I will, when it happens again. It's random, sadly.

frostbittenking · 2025-05-27 07:10:13

You mean journalctl right? Well sadly, it's not telling me anything useful. Happened yesterday, happened the day before.
I looks like it's also only happening with docks. It seems it immediately wakes back up when I switch the monitor's input, then when I send the laptop back to sleep, it's borked afterwards (when I wake it up the next day). Blank screen, not reaction. sysrq+k doesn't even work. Only reisub.

seth · 2025-05-27 07:13:55

After the reisub post the complete system journal for the previous boot:

sudo journalctl -b -1 | curl -F 'file=@-' 0x0.st

and also the xorg.0.log.old, https://wiki.archlinux.org/title/Xorg#General
There's probably _something_ … hopefully

frostbittenking · 2025-05-28 18:11:29

Yeah, I checked journalctl exactly as you suggested (I did guess right). It did say nothing. But I need to check Xorg log.
But good news.
I now can exactly reproduce the crash condition reliably (supposedly crash).
Context:
Work day:
1: < work bla blah>
2: end of day - close notebook
3: switch kvm switch for gaming
4: due to the changes in the kernel (afair some improvements for sleep and whatever), now shortly after switching the kvm switch laptop wakes up
5: open laptop, close again, laptop shut up, I'm not working anymore.
5b: laptop goes to sleep again
6: < go gaming>
7: go sleeping
8: next day work: switch kvm switch back to laptop
9: switch monitor input (one sad part one of the monitors needs to be manually switched, .. forgot why I have this setup, doesn't mattter)
10: wake up laptop
11: laptop is now in blank screen not reacting.

Additional info: at the beginning I opened a terminal to perma ping my server, on which I checked pings received with ngrep.
This works until the second sleep invocation (after first wake up when switching the kvm switch in 4/5), it starts pinging again.
AFter the second wakeup the next day, it seems to be dead. Doesn't start pinging my server again, cannot ping it either (I have a static dhcp assigned ip for my laptop).
Maybe this is specific enough, to make somebody's light go on, hey I have this too or whatever.
Might be the stupid odysee g7 monitor.

Last edited by frostbittenking (2025-05-28 18:13:56)

seth · 2025-05-28 22:43:50

2: end of day - close notebook
3: switch kvm switch for gaming

Can you flip that around?

2: end of day - switch kvm switch for gaming
3: close notebook

frostbittenking · 2025-05-29 08:21:26

seth wrote:

2: end of day - close notebook
3: switch kvm switch for gaming
Can you flip that around?
2: end of day - switch kvm switch for gaming
3: close notebook

Sadly no. The whole setup is buggy af anyways. When I do what you suggest the external monitors signal stays blank after switching back. Only way to fix this is disable the externals with xrandr, and even sometimes need to disconnect the kvm switch, switch it back and forth, and even something like have you tried turning it off and on again (close laptop, sleep, open again), connect lvm switch xrandr the externals. Usually when I send it to sleep and switch afterwards back and forth, it reenables all external monitors (that is before kernel 6.12 or whatever broke my setup).

frostbittenking · 2025-05-29 08:25:24

I will try a test without the g7. I suspect the stupid cec, that can't be turned off for this specific model. Cec from this monitor always causes troubles. Even on my windows machine in some games. Sometimes it just looses the signal and goes blank for a few seconds. Reddit and other sources suggests that the g7's cec is at fault here but Samsung thought it would be a good idea to not provide an option to disable it.

frostbittenking · 2025-05-29 12:10:09

It's a workaround but disabling auto-source switching seems to fix it. Looks like switching with the kvm switch now doesn't wake up my laptop anymore, and switch back to the laptop does work too, waking it up without an issue.
Guess I need to wait for a kernel fix, Since it's only a minor inconvenience. Could be it was an issue for far longer and a windows update changed something that my laptop gets woken up by something from the windows signal. No idea. Whatever. Guess that's it for now.

seth · 2025-05-29 14:23:02

cat /proc/acpi/wakeup

can you ignore the monitor trigger?
(correlate the output w/ "lspci" and look for the GPU)

frostbittenking · 2025-05-29 15:48:19

Ah, nice, but if I interpret die output correctly, /proc/acpi/wakeup has no entry for my VGA device.
00:02.0 VGA compatible controller [0300]: Intel Corporation Alder Lake-P GT2 [Iris Xe Graphics] [8086:46a6] (rev 0c)
But there is no entry for a device 00:02.0. Doesn't matter. It works for now. Thanks.

seth · 2025-05-29 16:23:49

Ah, nice, but if I interpret die output correctly, /proc/acpi/wakeup has no entry for my VGA device.

https://askubuntu.com/questions/1395148 … er-suspend ?

Arch Linux

#26 2025-05-06 16:49:29

Re: Suspend fails (only) when external monitor is connected

#27 2025-05-06 18:38:45

Re: Suspend fails (only) when external monitor is connected

#28 2025-05-06 20:27:31

Re: Suspend fails (only) when external monitor is connected

#29 2025-05-07 18:20:04

Re: Suspend fails (only) when external monitor is connected

#30 2025-05-07 21:44:14

Re: Suspend fails (only) when external monitor is connected

#31 2025-05-10 18:37:04

Re: Suspend fails (only) when external monitor is connected

#32 2025-05-10 22:16:34

Re: Suspend fails (only) when external monitor is connected

#33 2025-05-13 18:39:34

Re: Suspend fails (only) when external monitor is connected

#34 2025-05-14 07:15:38

Re: Suspend fails (only) when external monitor is connected

#35 2025-05-14 07:41:06

Re: Suspend fails (only) when external monitor is connected

#36 2025-05-16 07:00:26

Re: Suspend fails (only) when external monitor is connected

#37 2025-05-16 19:47:04

Re: Suspend fails (only) when external monitor is connected

#38 2025-05-17 09:15:21

Re: Suspend fails (only) when external monitor is connected

#39 2025-05-17 11:33:43

Re: Suspend fails (only) when external monitor is connected

#40 2025-05-17 11:55:13

Re: Suspend fails (only) when external monitor is connected

#41 2025-05-27 07:10:13

Re: Suspend fails (only) when external monitor is connected

#42 2025-05-27 07:13:55

Re: Suspend fails (only) when external monitor is connected

#43 2025-05-28 18:11:29

Re: Suspend fails (only) when external monitor is connected

#44 2025-05-28 22:43:50

Re: Suspend fails (only) when external monitor is connected

#45 2025-05-29 08:21:26

Re: Suspend fails (only) when external monitor is connected

#46 2025-05-29 08:25:24

Re: Suspend fails (only) when external monitor is connected

#47 2025-05-29 12:10:09

Re: Suspend fails (only) when external monitor is connected

#48 2025-05-29 14:23:02

Re: Suspend fails (only) when external monitor is connected

#49 2025-05-29 15:48:19

Re: Suspend fails (only) when external monitor is connected

#50 2025-05-29 16:23:49

Re: Suspend fails (only) when external monitor is connected

Board footer