Page 1 of 3 123 LastLast
Results 1 to 10 of 25

Thread: Problem with suspend

  1. #1
    Join Date
    Mar 2013
    Beans
    62

    Problem with suspend

    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):

    Code:
    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:

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

    Code:
    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:

    Code:
    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!














    Last edited by Toz; April 12th, 2013 at 02:44 AM.

  2. #2
    Join Date
    Mar 2013
    Beans
    62

    Diagnosing Sleep Disorders

    I'm having a problem with Suspend, which works fine if I issue the command using the gear menu or the terminal, but when I close the lid (I'm on a laptop) to Suspend, when I touch the power button to resume, it goes to a black screen and I have to reboot.

    So I'm trying out s2ram, part of uswusp, and I tried to make it the default action on "Suspend," with these steps (per http://askubuntu.com/questions/75357...thod-to-s2disk):

    Created a file /etc/pm/config.d/module
    containing:
    Code:
    SLEEP_MODULE=uswsusp
    But how do I verify that s2ram is being used when I close the lid? Are there any logs that can tell me this info?


    Also, why would I get different results from issuing the Suspend command from the menu or the terminal vs closing the laptop lid?

    Thanks!

  3. #3
    Join Date
    Jun 2005
    Location
    Toronto, Canada
    Beans
    Hidden!
    Distro
    Xubuntu 16.04 Xenial Xerus

    Re: Diagnosing Sleep Disorders

    Post back the complete contents of your /var/log/pm-suspend.log file - it should say in there.

    In a terminal window:
    Code:
    pastebinit /var/log/pm-suspend.log
    ...and post back the link that is generated.

    Is this the same issue as you posted here? If so, I'll move that post here so that everything is in one place.

  4. #4
    Join Date
    Mar 2013
    Beans
    62

    Re: Diagnosing Sleep Disorders

    Hi, yes, it's the same issue. I was asking slightly different things, but yes, it makes sense to consolidate them, thanks much. Resulting link from pastebinit /var/log/pm-suspend.log:

    http://paste.ubuntu.com/5697086/

    Appreciate your help on this!

  5. #5
    Join Date
    Mar 2013
    Beans
    62

    Re: Diagnosing Sleep Disorders

    Much better data! Looking through this but much is over my head. At least I'm getting actual errors:

    Having NetworkManager wake interfaces back up...Failed

  6. #6
    Join Date
    Jun 2005
    Location
    Toronto, Canada
    Beans
    Hidden!
    Distro
    Xubuntu 16.04 Xenial Xerus

    Re: Diagnosing Sleep Disorders

    Quote Originally Posted by thatstheway View Post
    Code:
    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:
    Code:
    pastebinit /var/log/Xorg.0.log
    sudo lspci -vnn | grep -A10 VGA:

    Code:
    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:
    Code:
    sudo lspci -vnn |grep -A15 VGA

  7. #7
    Join Date
    Mar 2013
    Beans
    62

    Re: Diagnosing Sleep Disorders

    This is suspicious:
    Code:
    Running hook /usr/lib/pm-utils/sleep.d/99video resume suspend: Function not supported

  8. #8
    Join Date
    Mar 2013
    Beans
    62

    Re: Diagnosing Sleep Disorders

    from sudo lspci -vnn |grep -A15 VGA:
    Code:
    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]

  9. #9
    Join Date
    Jun 2005
    Location
    Toronto, Canada
    Beans
    Hidden!
    Distro
    Xubuntu 16.04 Xenial Xerus

    Re: Diagnosing Sleep Disorders

    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).
    Code:
    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.

  10. #10
    Join Date
    Mar 2013
    Beans
    62

    Re: Diagnosing Sleep Disorders

    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/

Page 1 of 3 123 LastLast

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •