TuxOnIce, device resume from suspend takes way too long
Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
TuxOnIce, device resume from suspend takes way too long
Greetings,
I am having trouble with a rather peculiar timeout during resume from suspension and I was wondering if any of you have encountered the error or might have some leads as to what causes the problem.
I am using Gentoo Linux with TuxOnIce patched kernel. While both hibernation and suspension works as advertised, there is a rather irritating timeout while trying to resume from suspension. Each and every time it takes about 60s for notebook to resume back to X session again, no matter what the conditions are (i.e. USB deviced plugged in, etc.)
EDIT: Mainly all features including variety of TuxOnIce patches and CPU scaling etc. are build-in the kernel. Here is the list of modules that were loaded during the attempts:
Hi there! How do you suspend your PC? Via command or from X Server Environment? Maybe you could try (if you have it) by suspending with the "s2ram" application by entering the following:
Code:
s2ram --force
Just to see if there is some problem with the default procedure.
Hi there! How do you suspend your PC? Via command or from X Server Environment? Maybe you could try (if you have it) by suspending with the "s2ram" application by entering the following:
Code:
s2ram --force
Just to see if there is some problem with the default procedure.
Hello, thank you for your reply!
I have tried a variety of ways of suspending a computer, such as s2ram, or via (q)dbus call with no change in result like at all.
It would appear that --force argument bears has no effect on the time required for a resume of devices.
No matter what userspace application is used the end-result it always the same, which makes me believe that the problem is not in the choice and configuration of userspace application, rather than in the kernel itself.
I have Google'd some older posts stating that nvidia binary drivers interfere with suspend/hibernate capability. Unlike those cases I can perform these actions, it just takes a bit longer. Do you think the drivers are responsible?
[140635.569794] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[140635.772329] ata1.00: configured for UDMA/100
[140693.803932] r8169 0000:03:00.0: eth0: unable to apply firmware patch
[140693.808865] r8169 0000:03:00.0: eth0: link down
It seems that the problem is in some patch that the kernel is trying to apply to an interface's firmware in eth0. The kernel spends approximately 60 seconds here. Check if that interface works properly or maybe it may be needing some firmware files (wireless are the most common).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
.
