As mentioned in my previous posts I've been having serious issues on resuming from suspend. This fails after about 3 or 4 suspends, pretty systematically. I haven't been able to determine if happens only when I suspend by shutting the lid or on both shut lid and manual suspend (i.e. from the menu). In any case I'd like to document the symptoms here to see if anyone has some advice. I am currently using the non-edgers drivers but I think I'm going to switch to edgers to see if it fixes the problem.
I seem to be having two different kinds of resume failures.
1. The much more common one is the following. I will resume from suspend but rather than getting a password-prompt-screen I am dumped straight into the running X session. The latter however is either already frozen or freezes very quickly. I can still switch to the console though and the machine is responsive. When I check the log files I find the following every time I try to go back into X (ctrl-alt-F7):
Oct 31 21:02:38 sliver acpid: client 1107[0:0] has disconnected
Oct 31 21:02:38 sliver acpid: client connected from 1107[0:0]
Oct 31 21:02:38 sliver acpid: 1 client rule loaded
Oct 31 21:02:38 sliver kernel: [ 3699.062830] [drm:drm_mode_getfb] *ERROR* invalid framebuffer id
The xorg.log also yields something but i'm not sure if this happens when I switch back to X or to the console from X:
[ 3329.534] (II) Open ACPI successful (/var/run/acpid.socket)
[ 3329.534] (II) AIGLX: Resuming AIGLX clients after VT switch
[ 3329.535] (EE) intel(0): Couldn't create pixmap for fbcon
[ 3329.672] (II) intel(0): EDID vendor "APP", prod id 40159
[ 3329.672] (II) intel(0): Printing DDC gathered Modelines:
[ 3329.672] (II) intel(0): Modeline "1440x900"x0.0 91.54 1440 1504 1546 1652 900 903 909 926 -hsync -vsync (55.4 kHz)
[ 3329.886] (--) bcm5974: touchpad found
[ 3333.172] (II) AIGLX: Suspending AIGLX clients for VT switch
If, from the console I "restart lightdm" then X successfully restarts and I can continue using the machine.
2. Case (1) above is by far the more frequent case but there has been at least one time when my machine resumes as above, straight to X rather than to a password-prompt-screen, but unlike case (1) the machine is totally unresponsive and will not switch to a terminal. In this case I had to hard reboot and then checked the post reboot logs. In this case I found the pm-suspend log ends with the lines:
/etc/pm/sleep.d/novatel_3g_suspend resume suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/99video resume suspend:
So it looked like it froze on the 99video script. Looking around the other logs however I see that many other logs end on wireless related activity and (as I've posted about earlier) I've had some very strange wireless issues where the wireless driver can basically block any process trying to access anything network related. I have a feeling this is what is at play here so I'm somewhat less concerned by this kind of freeze.
If anyone has any feedback on what might be causing freeze (1) or how to better debug it please let me know. It seems to be an issue with the framebuffer but I'm quite ignorant of the driver setup on this machine (as I benefited from dfacto's work and just used his script). I'm planning to re-install the xorg-edgers drivers to see if this helps avoid this problem but if anyone has some better or alternate advice please let me know. It does seem that this machine really doesn't want to work under linux as I seem to have one problem after another but I'm not giving up (yet :->).