Problem with suspend

[thatstheway]

I can recover from Suspend just fine, as long as I issue the Suspend command from the menu. But if I close the lid, it "wakes" to the black screen mentioned by many others here, and I have to reboot.

Does anyone else have this same problem? Any ideas?

I've got a Toshiba Portege R100 laptop with a Trident CyberBlade XP4m32 graphics card. I'm using the most up-to-date version of the xorg Trident driver.

/var/log/pm-suspend.log says the same thing, whether I use the menu (successful resume) or the lid (failed resume, needing to reboot):

Running hook /usr/lib/pm-utils/sleep.d/00powersave resume suspend:


/usr/lib/pm-utils/sleep.d/00powersave resume suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/00logging resume suspend:

/usr/lib/pm-utils/sleep.d/00logging resume suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/000kernel-change resume suspend:

/usr/lib/pm-utils/sleep.d/000kernel-change resume suspend: success.
Wed Apr 10 09:25:30 PDT 2013: Finished.

cat /proc/cmdline:

BOOT_IMAGE=/boot/vmlinuz-3.5.0-23-generic root=UUID=1ca79722-7698-4d8f-8fb1-dafeec4306ca ro quiet splash vt.handoff=7

lsmod:

Module                  Size  Used by
michael_mic            12541  8 
arc4                   12474  4 
lib80211_crypt_tkip    17276  2 
lib80211_crypt_ccmp    12790  1 
vesafb                 13518  1 
bnep                   17791  2 
bluetooth             189585  7 bnep
parport_pc             32115  0 
ppdev                  12850  0 
snd_intel8x0           33463  2 
snd_ac97_codec        106118  1 snd_intel8x0
ac97_bus               12671  1 snd_ac97_codec
snd_pcm                81124  2 snd_intel8x0,snd_ac97_codec
snd_seq_midi           13133  0 
snd_rawmidi            25426  1 snd_seq_midi
snd_seq_midi_event     14476  1 snd_seq_midi
ipw2200               146213  0 
snd_seq                51594  2 snd_seq_midi,snd_seq_midi_event
snd_timer              28932  2 snd_pcm,snd_seq
libipw                 46733  1 ipw2200
snd_seq_device         14138  3 snd_seq_midi,snd_rawmidi,snd_seq
pcmcia                 39855  0 
joydev                 17394  0 
cfg80211              181041  2 ipw2200,libipw
snd                    62675  11 snd_intel8x0,snd_ac97_codec,snd_pcm,snd_rawmidi,snd_seq,snd_timer,snd_seq_device
yenta_socket           27465  0 
soundcore              14636  1 snd
pcmcia_rsrc            18368  1 yenta_socket
lib80211               14041  4 lib80211_crypt_tkip,lib80211_crypt_ccmp,ipw2200,libipw
snd_page_alloc         14109  2 snd_intel8x0,snd_pcm
pcmcia_core            21512  3 pcmcia,yenta_socket,pcmcia_rsrc
lpc_ich                16993  0 
psmouse                91022  0 
microcode              18396  0 
shpchp                 32326  0 
serio_raw              13032  0 
video                  19070  0 
mac_hid                13078  0 
lp                     17456  0 
parport                40931  3 parport_pc,ppdev,lp
hid_generic            12485  0 
usbhid                 46054  0 
hid                    82511  2 hid_generic,usbhid
e100                   36324  0

sudo lspci -vnn | grep -A10 VGA:

01:00.0 VGA compatible controller [0300]: Trident Microsystems CyberBlade XP4m32 [1023:2100] (rev 91) (prog-if 00 [VGA controller])
    Subsystem: Toshiba America Info Systems Device [1179:0002]
    Flags: bus master, 66MHz, medium devsel, latency 8, IRQ 11
    Memory at f0000000 (32-bit, non-prefetchable) [size=128M]
    Memory at efc00000 (32-bit, non-prefetchable) [size=4M]
    Memory at e0000000 (32-bit, non-prefetchable) [size=128M]
    Memory at dfff8000 (32-bit, non-prefetchable) [size=32K]
    [virtual] Expansion ROM at 54000000 [disabled] [size=256K]
    Capabilities: [80] AGP version 2.0
    Capabilities: [90] Power Management version 2

Millions of thanks for any insight into this!

[Toz]

Module                  Size  Used by
michael_mic            12541  8 
arc4                   12474  4 
lib80211_crypt_tkip    17276  2 
lib80211_crypt_ccmp    12790  1 
vesafb                 13518  1 
bnep                   17791  2 
bluetooth             189585  7 bnep
parport_pc             32115  0 
ppdev                  12850  0 
snd_intel8x0           33463  2 
snd_ac97_codec        106118  1 snd_intel8x0
ac97_bus               12671  1 snd_ac97_codec
snd_pcm                81124  2 snd_intel8x0,snd_ac97_codec
snd_seq_midi           13133  0 
snd_rawmidi            25426  1 snd_seq_midi
snd_seq_midi_event     14476  1 snd_seq_midi
ipw2200               146213  0 
snd_seq                51594  2 snd_seq_midi,snd_seq_midi_event
snd_timer              28932  2 snd_pcm,snd_seq
libipw                 46733  1 ipw2200
snd_seq_device         14138  3 snd_seq_midi,snd_rawmidi,snd_seq
pcmcia                 39855  0 
joydev                 17394  0 
cfg80211              181041  2 ipw2200,libipw
snd                    62675  11 snd_intel8x0,snd_ac97_codec,snd_pcm,snd_rawmidi,snd_seq,snd_timer,snd_seq_device
yenta_socket           27465  0 
soundcore              14636  1 snd
pcmcia_rsrc            18368  1 yenta_socket
lib80211               14041  4 lib80211_crypt_tkip,lib80211_crypt_ccmp,ipw2200,libipw
snd_page_alloc         14109  2 snd_intel8x0,snd_pcm
pcmcia_core            21512  3 pcmcia,yenta_socket,pcmcia_rsrc
lpc_ich                16993  0 
psmouse                91022  0 
microcode              18396  0 
shpchp                 32326  0 
serio_raw              13032  0 
video                  19070  0 
mac_hid                13078  0 
lp                     17456  0 
parport                40931  3 parport_pc,ppdev,lp
hid_generic            12485  0 
usbhid                 46054  0 
hid                    82511  2 hid_generic,usbhid
e100                   36324  0

I'm not seeing the trident driver loaded. Are you sure its being used? Can you post back your /var/log/Xorg.0.log file:

pastebinit /var/log/Xorg.0.log

sudo lspci -vnn | grep -A10 VGA:

01:00.0 VGA compatible controller [0300]: Trident Microsystems CyberBlade XP4m32 [1023:2100] (rev 91) (prog-if 00 [VGA controller])
    Subsystem: Toshiba America Info Systems Device [1179:0002]
    Flags: bus master, 66MHz, medium devsel, latency 8, IRQ 11
    Memory at f0000000 (32-bit, non-prefetchable) [size=128M]
    Memory at efc00000 (32-bit, non-prefetchable) [size=4M]
    Memory at e0000000 (32-bit, non-prefetchable) [size=128M]
    Memory at dfff8000 (32-bit, non-prefetchable) [size=32K]
    [virtual] Expansion ROM at 54000000 [disabled] [size=256K]
    Capabilities: [80] AGP version 2.0
    Capabilities: [90] Power Management version 2

Some info was cut off. Try instead:

sudo lspci -vnn |grep -A15 VGA

[thatstheway]

from sudo lspci -vnn |grep -A15 VGA:

01:00.0 VGA compatible controller [0300]: Trident Microsystems CyberBlade XP4m32 [1023:2100] (rev 91) (prog-if 00 [VGA controller])
    Subsystem: Toshiba America Info Systems Device [1179:0002]
    Flags: bus master, 66MHz, medium devsel, latency 8, IRQ 11
    Memory at f0000000 (32-bit, non-prefetchable) [size=128M]
    Memory at efc00000 (32-bit, non-prefetchable) [size=4M]
    Memory at e0000000 (32-bit, non-prefetchable) [size=128M]
    Memory at dfff8000 (32-bit, non-prefetchable) [size=32K]
    [virtual] Expansion ROM at 54000000 [disabled] [size=256K]
    Capabilities: [80] AGP version 2.0
    Capabilities: [90] Power Management version 2

02:08.0 Ethernet controller [0200]: Intel Corporation 82801DB PRO/100 VE (MOB) Ethernet Controller [8086:103d] (rev 83)
    Subsystem: Toshiba America Info Systems Device [1179:0001]
    Flags: bus master, medium devsel, latency 64, IRQ 11
    Memory at dfdff000 (32-bit, non-prefetchable) [size=4K]
    I/O ports at cf40 [size=64]

[thatstheway]

And Toz, re: the Trident driver being installed, in case you still wanted the /var/log/Xorg.0.log file, it's:

http://paste.ubuntu.com/5697112/

[Toz]

Whats interesting about that log file is that in each instance, the log file is showing that the suspend/resume cycle was completed. Can you do the following:

1. Delete the existing log file (it will get recreated automatically).

sudo rm /var/log/pm-suspend.log

2. Suspend using the suspend menu item and resume.

3. Close the lid. Wait 5 minutes. Open the lid.

At this point, does it sound like the computer has resumed? Are lights flashing again? Do you have brightness function keys? Can you try restoring brightness? Can you go to the first console (Ctrl+Alt+F1) and get a command prompt?

4. Once you've recovered, post back /var/log/pm-suspend.log and lets see what it says.

[thatstheway]

Here are the results of the test in post #9:

http://paste.ubuntu.com/5697150/

And Toz, after closing the lid and waiting for the computer to suspend, it "looks" like it's about to wake up after I hit the power key, but goes to a black screen. Brightness keys have no effect. Ctrl-Alt-F1 does not bring up the terminal. The sequence Ctl-Alt-T, sudo reboot does not reboot the machine. space bar, trackpad, trackpad clicks, mouse clicks, all have no effect.

[thatstheway]

The results of the test in post #9, that is. [sorry, I can't figure out how to delete posts. "Edit Post" says Edit/Delete in the rollover, but I can't see the Delete option.]

[Toz]

I think that suspend/resume is working in both instances. From your log file:

Wed Apr 10 18:38:36 PDT 2013: Running hooks for suspend.
.....
Wed Apr 10 18:38:40 PDT 2013: performing suspend
Wed Apr 10 18:38:53 PDT 2013: Awake.
Wed Apr 10 18:38:53 PDT 2013: Running hooks for resume
.....
Wed Apr 10 18:38:55 PDT 2013: Finished.
.....
.....
Wed Apr 10 18:39:14 PDT 2013: Running hooks for suspend.
.....
Wed Apr 10 18:39:17 PDT 2013: performing suspend
Wed Apr 10 18:40:11 PDT 2013: Awake.
Wed Apr 10 18:40:11 PDT 2013: Running hooks for resume
.....
Wed Apr 10 18:40:13 PDT 2013: Finished.

I believe the issue is that when you close the lid and re-open it, the screen isn't coming back.

As a first step, lets get some brightness values.
First, clear out the log file:

sudo rm /var/log/pm-suspend.log

Then, create the file /etc/pm/sleep.d/000brightness:

gksudo gedit /etc/pm/sleep.d/000brightness

...with the following content:

#!/bin/bash
case "$1" in
	hibernate|suspend)
		for file in /sys/class/backlight/*; do echo $file; cat $file/brightness; cat $file/max_brightness; done
		;;
	thaw|resume)
		for file in /sys/class/backlight/*; do echo $file; cat $file/brightness; cat $file/max_brightness; done
                ;;
        *)
                ;;
esac

...save the file and make the file executable:

sudo chmod +x /etc/pm/sleep.d/000brightness

Then, close the lid, recover the computer, and post back /var/log/pm-suspend.log.

[thatstheway]

Ok I'll try not to figure out why, but things have changed. When I closed the lid before, the power light would change from steady green to pulsing red, as it did when I issued the command from the menu. But after those changes, it remains steady green, and when I open the lid again and press any key, the xscreensaver log-on comes up, something I've never seen before. (possibly because it was too dark and I wasn't expecting this?) I can then log on, and resume!

Here's the suspend log:

http://paste.ubuntu.com/5697303/

Did it really suspend? Hm, I just tried the suspend command from the menu and it didn't work. It looked like it was going to suspend, the wireless signal cleared out, but then the signal came back and it didn't suspend. I cleared the log, tried it from the menu, and this is what the log now says:

http://paste.ubuntu.com/5697315/

[Toz]

Sorry, typo in the script. Try this version of the script instead:

#!/bin/bash
case "$1" in
	hibernate|suspend)
		for file in /sys/class/backlight/*; do echo $file; cat $file/brightness; cat $file/max_brightness; done
		;;
	thaw|resume)
		for file in /sys/class/backlight/*; do echo $file; cat $file/brightness; cat $file/max_brightness; done
                ;;
        *)
                ;;
esac