You are not logged in.
Pages: 1
Topic closed
Hello Community,
Problem is Resume not working after Suspend.
Kernel: x86_64 Linux 4.13.4-1-ARCH
DE: XFCE4
GPU: GeForce GTX 750 Ti
Driver installed for gpu: nvidia-beta
Suspend/Resume works on previous kernel
4.12.3-1
In /etc/default/grub, I saw a resume=UUID=THE_ID so I tried to edit per partitions id by trial and error but still no luck and I'm not sure if this is related, it was just my curiosity.
If anyone had similar issue and resolved the situation, please guide me.
Please also guide me what logs that I should include with this request.
Thank you!
Last edited by pantuts (2017-10-13 08:11:46)
Offline
i think you have to enable ACPI from you motherboard configuration, if it enabled see which state you are,
there are some states for me i have S1 and S3 and my configuration is S3. i wish it helps you.
Offline
Online
i think you have to enable ACPI from you motherboard ...
Yes its enabled, S3.
Offline
I already did this, no luck. Right now I'm trying to install the latest kernel updates.
Offline
Solved, I just installed linux-hardened rather than linux only.
Offline
If it is fixed with 4.13.5 there's a good chance we were talking the same issue though. Did you try
intel_mmu=off
which is a typo in the OP's post, as opposed to
intel_iommu=off
which would be the proper parameter.
Online
If it is fixed with 4.13.5 there's a good chance we were talking the same issue though. Did you try
intel_mmu=off
which is a typo in the OP's post, as opposed to
intel_iommu=off
which would be the proper parameter.
I reopened the issue, seems still not working. I updated to latest stable `4.13.5-1` and this still has suspend/resume issue. Even `intel_iommu=off` does not work.
Offline
Suspend/Resume works on previous kernel
...
saw a resume=UUID=THE_ID
For clarification: do we talk about S3 (suspend) or S4 (hibernate, "suspend to disk") here?
If it's S4, please provide a complete dmesg resp. "sudo journalctl -b" from the failed wake-up boot.
Otherwise elaborate on the symptoms of the failed resume, notbaly whether the resumed machine echos when ping'd (resp. you can ssh into it) and a dmesg resp. "sudo journalctl -b" from a regular boot (before goind STR)
Offline
Suspend/Resume works on previous kernel
...
saw a resume=UUID=THE_IDFor clarification: do we talk about S3 (suspend) or S4 (hibernate, "suspend to disk") here?
If it's S4, please provide a complete dmesg resp. "sudo journalctl -b" from the failed wake-up boot.
Otherwise elaborate on the symptoms of the failed resume, notbaly whether the resumed machine echos when ping'd (resp. you can ssh into it) and a dmesg resp. "sudo journalctl -b" from a regular boot (before goind STR)
BIOS settings is with S3. Your other comment, i really don't understand it. But see here, suspend/resume works well without errors in kernel 4.12.3, 4.12.4+ do not.
Offline
The main question is whether you try to suspend or to hibernate. This has nothing to do with your BIOS.
The "problem" is that you call it "suspend" but then make a reference to a setting that's only relevant for hibernation.
Depending on this, you need to produce the critical kernel messages. Do you imply you do not understand the meaning of "dmesg"??
Offline
I understand dmesg. I meant your howtos.
The Suspend setting is from XFCE4. I'm using pc only so I assume it is suspend not hibernate? I'll try with ping as you said.
I am also wondering why and why only it works 4.12.3 and below kernels. There are also lot of posts regarding this matter.
Offline
Solved. Current installed kernel: 4.13.6-1-hardened even with intel_iommu=on
Offline
That reads strange, would be interesting to find out what the hardened kernel does differently than stock to make suspend work on your machine. Have you compared journal/dmesg outputs between stock and hardened?
Online
That reads strange, would be interesting to find out what the hardened kernel does differently than stock to make suspend work on your machine. Have you compared journal/dmesg outputs between stock and hardened?
I tried logs previously, but all I can see are the logs before and on Suspend. Then the start boot logs since I powered it down everytime I test for resume coz it's not resuming.
Offline
Random guess: try to compare the outputs of "lsmod"
Offline
Random guess: try to compare the outputs of "lsmod"
Seems would be helpful, I'll try that.
Offline
This sounds very similar to https://bbs.archlinux.org/viewtopic.php?pid=1730030 which is left unsolved.
Offline
Same problem here, resume after suspend doesn't work with linux 4.13.
intel_mmu=off doesn't help nor does linux-hardened.
Offline
lod, Welcome to Arch Linux. I assume then that the solution worked for you as well.
Regardless, this thread had been marked solved. As such I'll go ahead and close it. If this is still a problem, feel free to start a new thread and link back to this one if appropriate.
Thanks
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Offline
Pages: 1
Topic closed