You are not logged in.
Pages: 1
I'm having a bit of trouble with suspending to disk, this applies to all methods. (kernel, uswsusp, tuxonice)
Basically when I initiate hibernation the screen goes black with a blinking cursor and stays like that. Only If I do something like unplugging a usb or trying to login from another terminal it actually starts to work. Why is this? This doesn't happen always sometimes it immediately works sometimes it needs some push.
Also, resume sometimes hangs the computer right after it finishies loading. Not really sure but could be because of the hooks order?
HOOKS="v86d fbsplash base udev autodetect sata uresume filesystems usbinput"
I wanted to initiate fbsplash as soon as possible, could this be why? (solved by putting fbsplash after uresume)
My system is:
Acer aspire 5739
linux-ck kernel with nvidia-beta-all package and uswsuso-fbsplash
I tried searching here and google, didn't help. Thanks.
Edit:I forgot to mention that I use kde, which has a problem with power button. Kde doesnt work with it and the system just waits kinda frozen, I had to use a different method for shutting down. Maybe somehow this is related.
Last edited by Kaan (2011-10-14 20:53:59)
Offline
...
Didn't think adding an important information more than an hour later was rapid posting...
Last edited by Kaan (2011-10-14 14:09:34)
Offline
Kaan,
please do not post in such rapid succession. Use the "Edit" button if you only want to add some information to a recent post of yours.
To know or not to know ...
... the questions remain forever.
Offline
It seems power button issue is fixed in 4.8;
Offline
I applied the patch and the power button issue was resolved but waiting on blinking cursor screen is still happening. It is pretty random and I didn't notice in anything in the logs. It generally happens when I want to hibernate and if I go into another terminal and try to login the process starts.
Edit: I found the cause of the problem;
INFO: task jbd2/sda2-8:225 blocked for more than 120 seconds.
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Haven't been able to find any solution on google, and I guess trying to login somehow lets this process contiune. I'm going to disable the message, there is nothing else I can do.
Last edited by Kaan (2011-10-16 23:56:29)
Offline
Pages: 1