Open ysalmon opened 8 years ago
I take bake the hypothesis about Steam et al. as today the problem appeared without it having run.
An update on this problem :
I realize that since I opened this issue, I have got a new machine ; lspci
is now
00:00.0 Host bridge: Intel Corporation Sky Lake Host Bridge/DRAM Registers (rev 07)
00:01.0 PCI bridge: Intel Corporation Sky Lake PCIe Controller (x16) (rev 07)
00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI Controller (rev 31)
00:14.2 Signal processing controller: Intel Corporation Sunrise Point-H Thermal subsystem (rev 31)
00:16.0 Communication controller: Intel Corporation Sunrise Point-H CSME HECI #1 (rev 31)
00:16.3 Serial controller: Intel Corporation Sunrise Point-H KT Redirection (rev 31)
00:17.0 RAID bus controller: Intel Corporation SATA Controller [RAID mode] (rev 31)
00:1c.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #1 (rev f1)
00:1f.0 ISA bridge: Intel Corporation Sunrise Point-H LPC Controller (rev 31)
00:1f.2 Memory controller: Intel Corporation Sunrise Point-H PMC (rev 31)
00:1f.3 Audio device: Intel Corporation Sunrise Point-H HD Audio (rev 31)
00:1f.4 SMBus: Intel Corporation Sunrise Point-H SMBus (rev 31)
00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (2) I219-LM (rev 31)
01:00.0 VGA compatible controller: NVIDIA Corporation GM107GL [Quadro K620] (rev a2)
01:00.1 Audio device: NVIDIA Corporation Device 0fbc (rev a1)
02:00.0 PCI bridge: Texas Instruments XIO2001 PCI Express-to-PCI Bridge
Hello, sometimes, when I boot my computer after having hibernated, TuxOnIce 4.4.0-31 proceeds to restore the RAM in its former state, but instead of proceeding to the X session, the monitor goes to sleep mode (other devices, like my USB mouse, also become unpowered). When this happens, I cannot do anything else than powering the computer off then on again (Alt-SysReq REISUB does not work, presumably because the USB keyboard is also not powered).
This happened today, and, to be sure, I tried to resume from this image 3 more times, and the behaviour was exactly the same.
This has been happening more frequently than in the past, so I tried with an earlier version (4.4.0-24), and it also happens with it.
It might be the case that this behaviour is triggered or aggravated when a Steam game has been run during the session (or even just the Steam client). Indeed, I have been using this more frequently for a month or two.
I would like to attach logs, but for a reason I do not know,
/var/log/pm-suspend.log
et al. only contain information about what was done in March.lspci
is