Diagnosing stalled black screen at resume

Hi,

My newly laptop pavilion 15-ecxx works fine with Qubes OS 4.1. It runs in UEFI mode only (no legacy available), has a nvidia GTX 1650 GPU, but freezes (after suspend) on resume.

Suspend seems to trigger well (blinking power led, no more leds on NIC nor SSD activity led, screen lit off), but resume fails (erratic : sometimes the lock screen of Xfce prompts, but no way to interact with it, most of the times the screen light on but remains black. SSD led usually blinks anew, as well as one of the NIC led too, but the machine is not up on the network anew).

With Suspend/resume troubleshooting | Qubes OS I tested adding mem_sleep_default=deep in grub.cfg, it did not change the results. I’ve also checked the `Xfce power manager’ tool, set all parameters to ‘suspend’ for the moment.

In How to troubleshoot wake from suspend I looked into journalctl but found nothing more relevant … though in dmesg (dom0) I noticed a snd_hda_intel 0000:01:00.1: can't change power state from D3cold to D0 (config space inaccessible) error message : it may be related to suspend, but I haven’t been successful investigating it until now :worried:.

Did not find any hint in Suspend issues on ThinkPad E495 nor in Suspend resume issues (gen1 thinkpad x1 yoga), maybe did I miss some solution in the forum ?

Anyhow, as there’s no /var/log/syslog in Qubes OS, I’d like any help to know what is the best place to investigate/try options :

  • dmesg
  • journalctl
  • UEFI
  • /var/log/lightdm/lightdm.log
    ?

Suspension problem is an old problem in Qubes OS. Usually old thinkpad laptops are better at suspension.

I am also having a hard time trying to troubleshoot the resuming problems on my machine. The following may be helpful.

  1. Your cpu model is important for troubleshooting.
  2. Check out whether your laptop supports a S3 sleep or a S0 sleep, and make a decision on which type of sleep you want.
  3. If S0, it does not seem Qubes OS will support this quickly.
  4. If S3 (the standard suspension), then there are several places to see the log files:
  • dom0 journalctl -r to see the dom0 kernel log
  • dom0 qube manager log to see the hypervisor log - both dom0 kernel log and hypervisor log are important; comparing the logs may prove to be very useful.
  • if you successfully resumed but some of your VM malfunctions, you can see the VM log in qube manager as well
  • I am not sure which additional logs are helpful; I don’t think that every laptop has a BIOS log - thinkpad BIOS, for example does not seem to have logging files
  1. When you are reading the logs, pay attention to the time. Find out which lines are before suspension and which lines are after resuming.
  2. There are many ways of interacting. Ctrl-Alt-F2, for example, can skip some of the problems if problem happens in Xorg. You can try to find out whether it is the whole computer that is down, or only your screen has some problems.
    How to troubleshoot wake from suspend - #10 by alzer89
    This has mentioned one way to try to distinguish whether it is screen or the whole system is down. There may be other methods, for example playing music when suspending; doing a lot of calculation (to make CPU busy) when suspending and observe the fan to see whether the CPU is idle or busy; while true;do sudo sh -c "echo -e '\a' >> /dev/console"; sleep 1;done in dom0 if you cannot even play music.

The current suspend/resume trouble shooting documentation does not seem to be up to date.

Talking of snd_hda_intel, is your audio working?