| View previous topic :: View next topic |
| Author |
Message |
skiwarz
Apprentice
Joined: 23 Feb 2014
Posts: 267
|
 Posted: Sun Dec 23, 2018 12:42 pm Post subject: No USB signal when resuming from suspend |
 |
|
When I am in my desktop environment, suspend/resume works normally (aside from a few nvidia glitches).
However, when I am on one of the tty terminals before running X: I can execute pm-suspend to put my machine in standby, but when I resume (by pressing a key, moving the mouse, or pressing the power button), I get no video signal, and none of my usb ports work. My keyboard and mouse receive no power (none of the lights work) nor can they input anything. I'm also unable to ssh into my machine. Due to this, I'm kind of in a black hole. I don't know what's going on because I can't see into my machine.
I found a few forum posts that said to set a kernel command line option of "usbcore.autosuspend=-1". I did this but it has no effect (I set it in grub defaults as well as in the kernel config).
Changing USB ports has no effect. All of them are disabled.
/var/log/pm-suspend.log shows:
| Code: | Sun Dec 23 05:08:35 EST 2018: performing suspend
Initial commandline parameters:
Blacklisting 01grub.
Blacklisting 90clock.
Sun Dec 23 05:20:23 EST 2018: Running hooks for suspend.
Running hook /usr/lib64/pm-utils/sleep.d/00logging suspend suspend:
Linux skrix3 4.14.90-gentoo #2 SMP Sun Dec 23 04:46:52 EST 2018 x86_64 Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz GenuineIntel GNU/Linux
Module Size Used by
nvidia_drm 40960 0
nvidia_modeset 1003520 1 nvidia_drm
nvidia 16740352 1 nvidia_modeset
x86_pkg_temp_thermal 16384 0
efivarfs 16384 1
total used free shared buff/cache available
Mem: 16362048 677700 15103856 976 580492 15527704
Swap: 2097148 0 2097148
/usr/lib64/pm-utils/sleep.d/00logging suspend suspend: success.
Running hook /usr/lib64/pm-utils/sleep.d/00powersave suspend suspend:
Blacklisting 01grub.
Blacklisting 90clock.
/usr/lib64/pm-utils/sleep.d/00powersave suspend suspend: success.
Running hook /usr/lib64/pm-utils/sleep.d/01grub suspend suspend:
/usr/lib64/pm-utils/sleep.d/01grub suspend suspend: disabled.
Running hook /usr/lib64/pm-utils/sleep.d/50unload_alx suspend suspend:
/usr/lib64/pm-utils/sleep.d/50unload_alx suspend suspend: success.
Running hook /usr/lib64/pm-utils/sleep.d/75modules suspend suspend:
/usr/lib64/pm-utils/sleep.d/75modules suspend suspend: success.
Running hook /usr/lib64/pm-utils/sleep.d/90clock suspend suspend:
/usr/lib64/pm-utils/sleep.d/90clock suspend suspend: disabled.
Running hook /usr/lib64/pm-utils/sleep.d/94cpufreq suspend suspend:
/usr/lib64/pm-utils/sleep.d/94cpufreq suspend suspend: success.
Running hook /usr/lib64/pm-utils/sleep.d/95led suspend suspend:
/usr/lib64/pm-utils/sleep.d/95led suspend suspend: not applicable.
Running hook /usr/lib64/pm-utils/sleep.d/98video-quirk-db-handler suspend suspend:
nVidia binary video drive detected, not using quirks.
/usr/lib64/pm-utils/sleep.d/98video-quirk-db-handler suspend suspend: success.
Running hook /usr/lib64/pm-utils/sleep.d/99video suspend suspend:
kernel.acpi_video_flags = 0
/usr/lib64/pm-utils/sleep.d/99video suspend suspend: success.
|
Anyone have any ideas? |
|
| Back to top |
|
 |
skiwarz
Apprentice
Joined: 23 Feb 2014
Posts: 267
|
| Posted: Sun Dec 23, 2018 5:54 pm Post subject: |
|
|
Upon further inspection, it looks like pm-utils isn't even being invoked yet on resume. The system seems to hang before it gets there. My /var/log/pm-suspend.log only shows entries for the suspend operation, not the resume.
Still a mystery, but this is one more clue I suppose. |
|
| Back to top |
|
|
Hu
Administrator
Joined: 06 Mar 2007
Posts: 23093
|
| Posted: Sun Dec 23, 2018 6:07 pm Post subject: |
|
|
| Does the machine respond to ping? Is your network connection via wireless or wired Ethernet? Is the network card built-in or attached via USB? If you attach a keyboard via PS/2, does it respond after resume? Does the system hang if you suspend from an untainted kernel? Does the system hang if you suspend from a text console, with no X environment running? |
|
| Back to top |
|
|
skiwarz
Apprentice
Joined: 23 Feb 2014
Posts: 267
|
| Posted: Sun Dec 23, 2018 6:16 pm Post subject: |
|
|
| Hu wrote: | | Does the machine respond to ping? Is your network connection via wireless or wired Ethernet? Is the network card built-in or attached via USB? If you attach a keyboard via PS/2, does it respond after resume? Does the system hang if you suspend from an untainted kernel? Does the system hang if you suspend from a text console, with no X environment running? |
Does not respond to ping. It is connected via wired ethernet on a built-in card.
Unfortunately I don't have a PS/2 keyboard
I did try booting on sysrescuecd and suspending from there, and it works fine.
When I am in an X environment, suspend/resume works (albeit slowly). The issue I'm having is when I'm purely on a text console. When X is NOT running, I cannot resume from suspend. |
|
| Back to top |
|
|
Hu
Administrator
Joined: 06 Mar 2007
Posts: 23093
|
| Posted: Sun Dec 23, 2018 7:51 pm Post subject: |
|
|
Sorry, I missed that this was a text-only problem. Usually suspend problems affect graphics mode first, and sometimes also include text mode.
Instead of systemrescueCD, what if you use your regular environment, but without tainting the kernel by loading the proprietary nVidia driver? |
|
| Back to top |
|
|
skiwarz
Apprentice
Joined: 23 Feb 2014
Posts: 267
|
| Posted: Sun Dec 23, 2018 9:00 pm Post subject: |
|
|
| Is there a quick way to prevent the nvidia driver module from loading? I've tried adding a blacklist file to /etc/modprobe.d and removing it from /etc/conf.d/modules. Or do I just need to uninstall it temporarily? |
|
| Back to top |
|
|
skiwarz
Apprentice
Joined: 23 Feb 2014
Posts: 267
|
| Posted: Sun Dec 23, 2018 9:21 pm Post subject: |
|
|
| Hu wrote: | Sorry, I missed that this was a text-only problem. Usually suspend problems affect graphics mode first, and sometimes also include text mode.
Instead of systemrescueCD, what if you use your regular environment, but without tainting the kernel by loading the proprietary nVidia driver? |
I got the kernel to load without the nvidia module. grep says nothing about the kernel being tainted anymore....
Still no luck.
Running "pm-suspend" gave me an unresponsive black screen with a blinking cursor, and never suspended all the way.
When I ran 'echo "mem" >> /sys/power/state' it suspended all the way, but resuming gave me the same result as before. No USB, no display, no network. Nothing.
At this point, it has to be a kernel issue, right? If another gentoo-based distro can suspend properly, and I can suspend fully on my install when I have X running, then I must have a kernel issue. Or could be udev maybe? |
|
| Back to top |
|
|
Hu
Administrator
Joined: 06 Mar 2007
Posts: 23093
|
| Posted: Sun Dec 23, 2018 11:19 pm Post subject: |
|
|
| Yes, it is a kernel issue. The only remaining question, now settled, was whether the nVidia kernel module contributed to it. From your description, the nVidia module does not contribute. You could try comparing the working rescue kernel with your kernel configuration. Check both for which options are different (of which there will likely be many) and whether the kernel version matters. |
|
| Back to top |
|
|
|
Kernel & Hardware
