Lenovo Thinkpad T61p - Takes a long time to resume from suspend
I am running Ubuntu 8.04 Hardy Heron on a Thinkpad T61p model 6459CTO. I am able to suspend the system to RAM, and it takes a few seconds longer than I might like, but not much longer than I would expect. When I attempt to resume, the monitor lights up and blinks a cursor in the upper left-hand corner. This takes between 5 and 20 seconds (approximately). Then the screen will turn off and on again, and it will briefly flash several messages, the most eye-catching of which contains "COMRESET failed." (I do not get these messages every single time I resume, only most of the time.) After half a second, X will start, and I will get the GNOME password prompt to unlock the computer. This prompt appears in a rough and incomplete form for up to 5 seconds before fully rendering and letting me enter my password and start working again. The entire resume process is unpleasantly long, and I think that it is due to some software problem, because resume is much faster in Windows XP Professional SP2 on the same computer.
I have spent the last several days Googling and searching forums for the solution to this problem. The only useful thing I found was here. That post suggests that I change the power management policy for my hard drive to "max_performance." I was confused, however, because my /sys/class/scsi_host/ directory contains not only host0 but host1 through host4. Only host0, host1, and host2 contain "link_power_management_policy" files, and all of these files are already set to "max_performance." I was unable to find out more about the purpose or use of these files, and I did not want to risk the stability of my system by messing with important system files that I did not understand. So I have not actually done anything to my system in an effort to fix this problem. Here is the relevant portion of my /var/log/syslog, which contains the messages that appear during resume: Code:
Jul 9 11:29:58 deimos gnome-power-manager: (abe) Resuming computer Is the problem my hard drive power management or something else? How do I go about correcting this problem? |
did you look at this, seems to be fine.
http://thinkwiki.org/wiki/Install_Ub...a_T61p#Suspend |
Thanks
Sorry for not responding sooner. I'll be out of state this whole week, and I don't have that computer with me. But I'll try that when I get back and tell you how it went. Thanks for the link.
|
Ubuntu Lenovo power quirks
I went to this page, on which the link you gave was based, because the article on Thinkwiki was about a T61p type 6460, and mine is a 6459. A user commenting on that bug report page submitted a patch to use for a 6459. It just comments out the 6459 section of /usr/share/hal/fdi/information/10freedesktop/20-video-quirk-pm-lenovo.fdi. After doing that, my resume time is about 10 seconds consistently. The same process takes about 5 seconds in Windows XP on the same machine, so I'm not sure I would say that the problem is solved, but it is better now than it was before. Thanks for your help.
|
Quote:
|
It's back from the dead
So my computer was working better for about a day. Then, without me making any changes, it just went back to not working. Sort of.
Now it usually takes between 22 and 24 seconds to resume from suspend-to-RAM. The only exception seems to be when it has been sleeping for a fairly short period. When the suspend is less than about 1.5 minutes (I haven't tested longer than that yet), the resume process takes between 7 and 12 seconds. In the tests that I did where it took a long time to wake up, I left it suspended for approximately half an hour. It seems like, instead of just commenting out the entry for my type of computer in /usr/share/hal/fdi/information/10freedesktop/20-video-quirk-pm-lenovo.fdi, I should be able to edit it so that it says the right thing. Does anyone know how to do that? Edit: One other thing I should mention. Sometimes, when the computer is waking up, it emits several (probably 5 or 6) system beeps in quick succession just before it finishes waking up. This has been happening since before I started trying to fix this problem. |
All times are GMT -5. The time now is 08:30 PM. |