How to troubleshoot if 'suspend' not working

rng · 07-16-2017, 11:26 AM

I have recently updated from Debian Stable 8 to 9 and it is otherwise working very well. However, the suspend function in not working.

It seems to go to sleep in the usual manner with disk activity ceasing and CPU LED turn blinking from constant on mode. But when I press a key to wake it up, even though the disk activity restarts and LED turns persistently on, there is only a flicker of activity on screen. After that screen remains black and nothing appears (not even mouse cursor). I have to hard reboot to start up computer again.

The system also has a NVIDIA graphics card.

Earlier there was a swap partition declared in /etc/fstab and a /etc/initramfs-tools/conf.d/resume file (with uuid of same swap partition). Since suspend was not working, I removed swap entry in /etc/fstab and removed resume file. I now load the swap partitions by swapon command from rc-local service. I have swap working as seen by following outputs:

Code:

root@debian:/home/abcd# free 
              total        used        free      shared  buff/cache   available
Mem:        4107832      633248     2399924       73792     1074660     3020824
Swap:      12141232           0    12141232

root@debian:/home/abcd# swapon -s 
Filename                                Type            Size    Used    Priority
/dev/sda7                               partition       3999740 0       -1
/dev/sda15                              partition       4052988 0       -2
/dev/sda19                              partition       4088504 0       -3

But even now suspend is not working.

There was never a resume entry on grub linux (kernel) line.

Where could be the problem and how can I correct it?

pan64 · 07-16-2017, 11:30 AM

I would try Ctrl-Alt-F1 or similar, probably that helps. Also you can try to log in on your console and restart your display manager, it is much faster than a reboot. You may need to check your logs too.

rng · 07-16-2017, 12:05 PM

With Ctrl-Alt-F1, I got a message that:

Code:

Fatal server error: No screens found

and I was given a login prompt. After login I tried 'startx', but it did not work:

Code:

xinit: unable to connect X server: connection refused.

pan64 · 07-17-2017, 12:22 AM

you need not start X again, just check the logs. Probably you can switch back by Ctrl-Alt-F7 (or F2 or ??)

hazel · 07-17-2017, 01:18 AM

It's worth doing a quick check to see if you have a console at all or if it's just a video problem. When you put the caps lock down, does the caps lock light come on? Can you reboot with ctrl-alt-del?

If the answer to these questions is "yes", it's a video problem. You could try suspending with the various video quirks listed in the pm-utils database. I must admit I've tried them all singly on my laptop (which has a similar problem) and none of them worked. So far I haven't had the patience to try all the possible combinations.

rng · 07-17-2017, 09:35 AM

The Caps and Num key were working, though control-alt-delete did not work when the screen was black following waking up from suspend. Control-alt-F1 gave me a terminal but control-alt-F7 brought back the black screen. I went back to terminal by control-alt-f1 and gave command 'sudo reboot'. At that time, the original graphics screen (from which suspend was called) came back for a few seconds and then the system rebooted. I believe this means video problem. Should I remove NVIDIA driver and use nouveau instead?

Quote:

@pan64 : you need not start X again, just check the logs.

Sorry to ask a basic question. Which log files should I check?

pan64 · 07-17-2017, 10:18 AM

ok, so yes, you can try nouveau instead of nvidia.
you can go into /var/log and check messages, syslog, Xorg.0.log. Also you can go into users' home and check .xsession-errors.
On console you can restart your display manager (as root) and you do not need to reboot.

hazel · 07-17-2017, 10:18 AM

Right! It's video and, specifically, it's X. Your svga driver works. I wish I could say the same for my laptop!

The logs for X are in /var/log; unlike the other logs, they're not cumulative. Instead each session starts a new file. The current one is called Xorg.0.log. The previous one is Xorg.0.log.old. Those are the only ones that are saved. I suggest you use your console to save the current log under another name and post it here.

Other people can help you with the question of nouveau versus nvidia, but I don't remember seeing anyone express much enthusiasm for nouveau.

rng · 07-17-2017, 12:33 PM

I removed NVIDIA driver and now nouveau has taken over. However, it is still not waking up from suspend.

Quote:

On console you can restart your display manager (as root) and you do not need to reboot.

How do I do this? I tried command 'sddm' and it only produced a blank screen. I had to hard reboot. I have actually installed 'nodm' package so that it logs in as a user without asking (so no login screen appears).

rng · 07-17-2017, 09:53 PM

I deleted .xsessions-errors file and then suspended. It did not wake up properly and I rebooted. Following is the newly created .xsession-errors file:

Code:

Xsession: X session started for auser at Tue Jul 18 08:19:15 IST 2017
dbus-update-activation-environment: setting DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
dbus-update-activation-environment: setting DISPLAY=:0
localuser:auser being added to access control list
dbus-update-activation-environment: setting GTK_MODULES=gail:atk-bridge
gpgconf: warning: can not open config file /home/auser/.gnupg/gpg-agent.conf: No such file or directory
dbus-update-activation-environment: setting QT_ACCESSIBILITY=1
dbus-update-activation-environment: setting QT_LINUX_ACCESSIBILITY_ALWAYS_ON=1
OpenGL version: 3.
dbus-update-activation-environment: setting NODM_X_TIMEOUT=300
dbus-update-activation-environment: setting NODM_FIRST_VT=7
dbus-update-activation-environment: setting LANGUAGE=en_IN:en
dbus-update-activation-environment: setting USER=auser
dbus-update-activation-environment: setting HOME=/home/auser
dbus-update-activation-environment: setting GTK_MODULES=gail:atk-bridge
dbus-update-activation-environment: setting QT_LINUX_ACCESSIBILITY_ALWAYS_ON=1
dbus-update-activation-environment: setting DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
dbus-update-activation-environment: setting LOGNAME=auser
dbus-update-activation-environment: setting JOURNAL_STREAM=8:14704
dbus-update-activation-environment: setting NODM_OPTIONS=
dbus-update-activation-environment: setting USERNAME=auser
dbus-update-activation-environment: setting WINDOWPATH=7
dbus-update-activation-environment: setting PATH=/home/auser/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
dbus-update-activation-environment: setting INVOCATION_ID=cfa8092d2a9d4af3828df3559baf2569
dbus-update-activation-environment: setting XDG_RUNTIME_DIR=/run/user/1000
dbus-update-activation-environment: setting DISPLAY=:0
dbus-update-activation-environment: setting LANG=en_IN
dbus-update-activation-environment: setting SHELL=/bin/bash
dbus-update-activation-environment: setting QT_ACCESSIBILITY=1
dbus-update-activation-environment: setting NODM_ENABLED=true
dbus-update-activation-environment: setting GPG_AGENT_INFO=/run/user/1000/gnupg/S.gpg-agent:0:1
dbus-update-activation-environment: setting PWD=/home/auser
** Message: main.vala:102: Session is LXDE
** Message: main.vala:103: DE is LXDE
** Message: main.vala:134: log directory: /home/auser/.cache/lxsession/LXDE
** Message: main.vala:135: log path: /home/auser/.cache/lxsession/LXDE/run.log

pan64 · 07-18-2017, 02:02 AM

this file contains no related info.
You need to check your display manager, you can do something like this:
ps -ef | grep dm
You need to find a process like gdm, lightdm or similar and if you found you may try:
service gdm (or lightdm) restart.

rng · 07-18-2017, 10:44 AM

I followed above suggestions and found that 'nodm' was being used. I was able to get back desktop using command "systemctl restart nodm". On logging out of this desktop, I was returned to original desktop.

What does it mean? Can I correct it so that I can get normal waking up from suspend situation?

pan64 · 07-18-2017, 11:51 AM

I would still check /var/log for related error messages (for example Xorg.0.log), it looks like video driver problem, but need to know more....

rng · 07-18-2017, 12:55 PM

Following is the last part of Xorg.0.log file before suspending:

Code:

[    25.154] (II) NOUVEAU(0): Modeline "1280x800"x0.0  106.50  1280 1360 1488 1696  800 803 809 838 -hsync +vsync (62.8 kHz e)
[    25.154] (II) NOUVEAU(0): Modeline "1440x900"x0.0  106.50  1440 1520 1672 1904  900 903 909 934 -hsync +vsync (55.9 kHz e)
[    25.154] (II) NOUVEAU(0): Modeline "1440x900"x0.0  136.75  1440 1536 1688 1936  900 903 909 942 -hsync +vsync (70.6 kHz e)
[    25.196] (II) NOUVEAU(0): EDID vendor "SAM", prod id 1596
[    25.196] (II) NOUVEAU(0): Using hsync ranges from config file
[    25.196] (II) NOUVEAU(0): Using vrefresh ranges from config file
[    25.196] (II) NOUVEAU(0): Printing DDC gathered Modelines:
[    25.196] (II) NOUVEAU(0): Modeline "1600x900"x0.0  108.00  1600 1624 1704 1800  900 901 904 1000 +hsync +vsync (60.0 kHz eP)
[    25.196] (II) NOUVEAU(0): Modeline "800x600"x0.0   40.00  800 840 968 1056  600 601 605 628 +hsync +vsync (37.9 kHz e)
[    25.196] (II) NOUVEAU(0): Modeline "800x600"x0.0   36.00  800 824 896 1024  600 601 603 625 +hsync +vsync (35.2 kHz e)
[    25.196] (II) NOUVEAU(0): Modeline "640x480"x0.0   31.50  640 656 720 840  480 481 484 500 -hsync -vsync (37.5 kHz e)
[    25.196] (II) NOUVEAU(0): Modeline "640x480"x0.0   31.50  640 664 704 832  480 489 492 520 -hsync -vsync (37.9 kHz e)
[    25.196] (II) NOUVEAU(0): Modeline "640x480"x0.0   30.24  640 704 768 864  480 483 486 525 -hsync -vsync (35.0 kHz e)
[    25.196] (II) NOUVEAU(0): Modeline "640x480"x0.0   25.18  640 656 752 800  480 490 492 525 -hsync -vsync (31.5 kHz e)
[    25.196] (II) NOUVEAU(0): Modeline "720x400"x0.0   28.32  720 738 846 900  400 412 414 449 -hsync +vsync (31.5 kHz e)
[    25.196] (II) NOUVEAU(0): Modeline "1024x768"x0.0   78.75  1024 1040 1136 1312  768 769 772 800 +hsync +vsync (60.0 kHz e)
[    25.196] (II) NOUVEAU(0): Modeline "1024x768"x0.0   75.00  1024 1048 1184 1328  768 771 777 806 -hsync -vsync (56.5 kHz e)
[    25.196] (II) NOUVEAU(0): Modeline "1024x768"x0.0   65.00  1024 1048 1184 1344  768 771 777 806 -hsync -vsync (48.4 kHz e)
[    25.196] (II) NOUVEAU(0): Modeline "832x624"x0.0   57.28  832 864 928 1152  624 625 628 667 -hsync -vsync (49.7 kHz e)
[    25.196] (II) NOUVEAU(0): Modeline "800x600"x0.0   49.50  800 816 896 1056  600 601 604 625 +hsync +vsync (46.9 kHz e)
[    25.196] (II) NOUVEAU(0): Modeline "800x600"x0.0   50.00  800 856 976 1040  600 637 643 666 +hsync +vsync (48.1 kHz e)
[    25.196] (II) NOUVEAU(0): Modeline "1152x864"x0.0  108.00  1152 1216 1344 1600  864 865 868 900 +hsync +vsync (67.5 kHz e)
[    25.196] (II) NOUVEAU(0): Modeline "1280x800"x0.0   83.50  1280 1352 1480 1680  800 803 809 831 -hsync +vsync (49.7 kHz e)
[    25.196] (II) NOUVEAU(0): Modeline "1280x800"x0.0  106.50  1280 1360 1488 1696  800 803 809 838 -hsync +vsync (62.8 kHz e)
[    25.196] (II) NOUVEAU(0): Modeline "1440x900"x0.0  106.50  1440 1520 1672 1904  900 903 909 934 -hsync +vsync (55.9 kHz e)
[    25.196] (II) NOUVEAU(0): Modeline "1440x900"x0.0  136.75  1440 1536 1688 1936  900 903 909 942 -hsync +vsync (70.6 kHz e)

After waking up > black screen > control-alt-F1 : Only following 2 lines were added to Xorg.0.log file:

Code:

[   124.684] (II) AIGLX: Suspending AIGLX clients for VT switch
[   124.684] (II) NOUVEAU(0): NVLeaveVT is called.

Edit:
Other suspicious entries (marked as <<<<) in this file (at start):

Code:

...
[    14.533] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.    <<<<<<<<<<<<<<<<
[    14.533] 	Entry deleted from font path.
...
...
[    14.591] (II) LoadModule: "glx"
[    14.592] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[    14.773] (II) Module glx: vendor="X.Org Foundation"
[    14.773] 	compiled for 1.19.2, module version = 1.0.0
[    14.773] 	ABI class: X.Org Server Extension, version 10.0
[    14.773] (==) Matched nouveau as autoconfigured driver 0
[    14.773] (==) Matched nv as autoconfigured driver 1
[    14.773] (==) Matched nouveau as autoconfigured driver 2
[    14.773] (==) Matched nv as autoconfigured driver 3
[    14.773] (==) Matched modesetting as autoconfigured driver 4
[    14.773] (==) Matched fbdev as autoconfigured driver 5
[    14.773] (==) Matched vesa as autoconfigured driver 6
[    14.773] (==) Assigned the driver to the xf86ConfigLayout
[    14.773] (II) LoadModule: "nouveau"
[    14.775] (II) Loading /usr/lib/xorg/modules/drivers/nouveau_drv.so
[    14.821] (II) Module nouveau: vendor="X.Org Foundation"
[    14.821] 	compiled for 1.19.3, module version = 1.0.13
[    14.821] 	Module class: X.Org Video Driver
[    14.821] 	ABI class: X.Org Video Driver, version 23.0
[    14.821] (II) LoadModule: "nv"
[    14.821] (WW) Warning, couldn't open module nv    <<<<<<<<<<<<<<<<
[    14.821] (II) UnloadModule: "nv"
[    14.821] (II) Unloading nv
[    14.821] (EE) Failed to load module "nv" (module does not exist, 0)    <<<<<<<<<<<<<<<<
[    14.821] (II) LoadModule: "modesetting"
...
...
[    14.886] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[    14.886] (II) FBDEV: driver for framebuffer: fbdev
[    14.886] (II) VESA: driver for VESA chipsets: vesa
[    14.887] (II) [drm] nouveau interface version: 1.3.1
[    14.887] (WW) Falling back to old probe method for modesetting    <<<<<<<<<<<<<<<<
[    14.887] (WW) Falling back to old probe method for fbdev    <<<<<<<<<<<<<<<<
[    14.887] (II) Loading sub module "fbdevhw"
[    14.887] (II) LoadModule: "fbdevhw"
[    14.888] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[    14.902] (II) Module fbdevhw: vendor="X.Org Foundation"
[    14.902] 	compiled for 1.19.2, module version = 0.0.2
[    14.902] 	ABI class: X.Org Video Driver, version 23.0
[    14.902] (WW) Falling back to old probe method for vesa    <<<<<<<<<<<<<<<<
[    14.902] (II) Loading sub module "dri2"
[    14.902] (II) LoadModule: "dri2"
[    14.902] (II) Module "dri2" already built-in
...
...
[    18.063] (II) Using input driver 'libinput' for 'Power Button'
[    18.063] (**) Power Button: always reports core events
[    18.063] (**) Option "Device" "/dev/input/event3"
[    18.063] (**) Option "_source" "server/udev"
[    18.063] (II) input device 'Power Button', /dev/input/event3 is tagged by udev as: Keyboard
[    18.064] (II) input device 'Power Button', /dev/input/event3 is a keyboard
[    18.084] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input3/event3"
[    18.084] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[    18.084] (**) Option "xkb_model" "pc105"
[    18.084] (**) Option "xkb_layout" "us"
[    18.084] (II) input device 'Power Button', /dev/input/event3 is tagged by udev as: Keyboard
[    18.084] (II) input device 'Power Button', /dev/input/event3 is a keyboard
[    18.085] (II) config/udev: Adding input device Power Button (/dev/input/event2)
[    18.085] (**) Power Button: Applying InputClass "libinput keyboard catchall"
[    18.085] (II) Using input driver 'libinput' for 'Power Button'
[    18.085] (**) Power Button: always reports core events
[    18.085] (**) Option "Device" "/dev/input/event2"
[    18.085] (**) Option "_source" "server/udev"
[    18.085] (II) input device 'Power Button', /dev/input/event2 is tagged by udev as: Keyboard
[    18.085] (II) input device 'Power Button', /dev/input/event2 is a keyboard
[    18.100] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input2/event2"
[    18.100] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 7)
[    18.100] (**) Option "xkb_model" "pc105"
[    18.100] (**) Option "xkb_layout" "us"
[    18.100] (II) input device 'Power Button', /dev/input/event2 is tagged by udev as: Keyboard
[    18.100] (II) input device 'Power Button', /dev/input/event2 is a keyboard
[    18.101] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=7 (/dev/input/event10)
[    18.101] (II) No input driver specified, ignoring this device.    <<<<<<<<<<<<<<<<
[    18.101] (II) This device may have been added with another device file.   
[    18.102] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=8 (/dev/input/event11)
[    18.102] (II) No input driver specified, ignoring this device.    <<<<<<<<<<<<<<<<
[    18.102] (II) This device may have been added with another device file.
[    18.102] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=9 (/dev/input/event12)
[    18.102] (II) No input driver specified, ignoring this device.    <<<<<<<<<<<<<<<<
[    18.102] (II) This device may have been added with another device file.
[    18.102] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=3 (/dev/input/event9)
[    18.102] (II) No input driver specified, ignoring this device.    <<<<<<<<<<<<<<<<
[    18.102] (II) This device may have been added with another device file.
[    18.103] (II) config/udev: Adding input device Microsoft  Microsoft Basic Optical Mouse v2.0  (/dev/input/event1)
[    18.103] (**) Microsoft  Microsoft Basic Optical Mouse v2.0 : Applying InputClass "libinput pointer catchall"
[    18.103] (II) Using input driver 'libinput' for 'Microsoft  Microsoft Basic Optical Mouse v2.0 '
[    18.103] (**) Microsoft  Microsoft Basic Optical Mouse v2.0 : always reports core events
[    18.103] (**) Option "Device" "/dev/input/event1"
[    18.103] (**) Option "_source" "server/udev"
[    18.160] (II) input device 'Microsoft  Microsoft Basic Optical Mouse v2.0 ', /dev/input/event1 is tagged by udev as: Mouse
[    18.160] (II) input device 'Microsoft  Microsoft Basic Optical Mouse v2.0 ', /dev/input/event1 is a pointer caps
[    18.200] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.3/1-1.3:1.0/0003:045E:00CB.0001/input/input1/event1"
[    18.200] (II) XINPUT: Adding extended input device "Microsoft  Microsoft Basic Optical Mouse v2.0 " (type: MOUSE, id 8)
[    18.200] (**) Option "AccelerationScheme" "none"
[    18.200] (**) Microsoft  Microsoft Basic Optical Mouse v2.0 : (accel) selected scheme none/0
[    18.200] (**) Microsoft  Microsoft Basic Optical Mouse v2.0 : (accel) acceleration factor: 2.000
[    18.200] (**) Microsoft  Microsoft Basic Optical Mouse v2.0 : (accel) acceleration threshold: 4
[    18.260] (II) input device 'Microsoft  Microsoft Basic Optical Mouse v2.0 ', /dev/input/event1 is tagged by udev as: Mouse
[    18.260] (II) input device 'Microsoft  Microsoft Basic Optical Mouse v2.0 ', /dev/input/event1 is a pointer caps
[    18.261] (II) config/udev: Adding input device Microsoft  Microsoft Basic Optical Mouse v2.0  (/dev/input/mouse0)
[    18.261] (II) No input driver specified, ignoring this device.    <<<<<<<<<<<<<<<<
[    18.261] (II) This device may have been added with another device file.
[    18.261] (II) config/udev: Adding input device HDA Digital PCBeep (/dev/input/event5)
[    18.261] (II) No input driver specified, ignoring this device.    <<<<<<<<<<<<<<<<
[    18.261] (II) This device may have been added with another device file.
[    18.261] (II) config/udev: Adding input device HDA Intel PCH Rear Mic (/dev/input/event6)
[    18.262] (II) No input driver specified, ignoring this device.    <<<<<<<<<<<<<<<<
[    18.262] (II) This device may have been added with another device file.
[    18.262] (II) config/udev: Adding input device HDA Intel PCH Line (/dev/input/event7)
[    18.262] (II) No input driver specified, ignoring this device.    <<<<<<<<<<<<<<<<
[    18.262] (II) This device may have been added with another device file.
[    18.262] (II) config/udev: Adding input device HDA Intel PCH Line Out (/dev/input/event8)
[    18.262] (II) No input driver specified, ignoring this device.    <<<<<<<<<<<<<<<<
[    18.262] (II) This device may have been added with another device file.
[    18.263] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event0)
[    18.263] (**) AT Translated Set 2 keyboard: Applying InputClass "libinput keyboard catchall"
[    18.263] (II) Using input driver 'libinput' for 'AT Translated Set 2 keyboard'
[    18.263] (**) AT Translated Set 2 keyboard: always reports core events
[    18.263] (**) Option "Device" "/dev/input/event0"
[    18.263] (**) Option "_source" "server/udev"
[    18.263] (II) input device 'AT Translated Set 2 keyboard', /dev/input/event0 is tagged by udev as: Keyboard
[    18.263] (II) input device 'AT Translated Set 2 keyboard', /dev/input/event0 is a keyboard
[    18.292] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio0/input/input0/event0"
[    18.292] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD, id 9)
[    18.292] (**) Option "xkb_model" "pc105"
[    18.292] (**) Option "xkb_layout" "us"
[    18.292] (II) input device 'AT Translated Set 2 keyboard', /dev/input/event0 is tagged by udev as: Keyboard
[    18.292] (II) input device 'AT Translated Set 2 keyboard', /dev/input/event0 is a keyboard
[    18.293] (II) config/udev: Adding input device PC Speaker (/dev/input/event4)
[    18.293] (II) No input driver specified, ignoring this device.    <<<<<<<<<<<<<<<<
[    18.293] (II) This device may have been added with another device file.
[    21.003] (II) NOUVEAU(0): EDID vendor "SAM", prod id 1596
...
...

I may mention that I can see videos all right on this system (including sound) using vlc application.

What does all this mean?

pan64 · 07-19-2017, 12:19 AM

yes, in that log file error messages started with (EE)
I would make a normal boot, and save that log (before suspend) and compare to this one.