Ubuntu freezes/crash after wake when upgraded to 13.10 [closed]

Back on 13.04 it didn't occurred. I've upgraded to 13.10, systems apparently working fine, but, when I put it to sleep(using or not using extended monitor) and try to wake up, I see the screen(both), without lock-screen, but completely freeze, Neither tty open, nor the keyboard works.

So, only option remains is to force shut-down. Any clue how to investigate the cause or fix it? Thanks in advance, any info that'll help you could ask!

Ubuntu 13.10 x64 - not a fresh install/upgraded - with Unity
Dell Vostro 3550
AMD Proprietary Drivers - 13.11 / Hybrid with Intel 

--------------------- EDIT ------------------------

The fix has gone, i cant wake from suspend again, and, every time i shutdown/power up, i got like 9 windows from "report problem". this is the error:

enter image description here


Solution 1:

Actually there is a bug which you can find in Launchpad.net

Best thing is that there is also a patch through which you can solve this issue.

Follow these steps hope it works for you also:

  • Open terminal and execute these steps:

    sudo cp /etc/default/grub /etc/default/grub_back
    

    taking the backup of original /etc/default/grub file, in case some error occurs we can get back to original state

    sudo gedit /etc/default/grub
    

    opening the file in gedit to make the changes.

    Once file opened replace following line :

    GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
    

    to the line:

    GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pcie_aspm=force"
    

    Save the file Ctrl+S and close Ctrl+Q

Note: The next line to the line mentioned above should be GRUB_CMDLINE_LINUX="" not GRUB_CMDLINE_LINUX="acpi_osi=Linux"

  • Now execute following command to update the grub

    sudo update-grub
    
  • Re-start your system once.

Note: If you have trouble in brightness also and above method doesn't fix it then you can test by adding these lines in place I mentioned above.

2. GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nomodeset"

or

3. GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi_backlight=vendor pcie_aspm=force"

or

4. GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi_backlight=vendor"

or

5. GRUB_CMDLINE_LINUX_DEFAULT="pcie_aspm=force"

or

6. GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci=nomsi"

Note: You have to do a sudo update-grub and a system restart every time you change the grub file

Different system would need different options, if any of the option works, I request to mention that in the comment.

Reply if something goes wrong..

Solution 2:

In my system (Samsung Chronos 7 with hybrid graphics, using fglrx drivers because the open source ones makes the system not bootable (1)), the suspend/resume if successful only if made from a virtual console. So I had to add the file(2):

-rwxr-xr-x 1 root root 152 Dec  7 12:09 /etc/pm/sleep.d/01_switchvt

with the contents:

#!/bin/sh

# Switch to a VC before suspending and back after resume

case "$1" in
        resume|thaw)
            chvt 7
        ;;
        suspend|hibernate)
            chvt 1
        ;;
esac

You could need this instead or in addition to Saurav solutions.


Footnotes:

(1) Update: I now can use open-source drivers. It was an overheating problem.

(2) Step-by-step:

  1. edit/create the file

    gksudo gedit /etc/pm/sleep.d/01_switchvt

  2. copy and paste the content above

  3. save and exit
  4. make it executable:

    chmod 755 /etc/pm/sleep.d/01_switchvt

Solution 3:

When I installed fglrx on Saucy for my Radeon 6870, I experienced the same problem. I tried Saurav Kumar's method, but none of those boot parameters worked. From here, though, I found and tried adding "nomodeset" as a parameter, and I was able to resume from suspend normally.

Solution 4:

Replacement of the Grub line with GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nomodeset" was not enough for me.

At restart my screen resolution was downgraded and wakeup from suspend was still not working.

I had to change the video card driver from the "nouveau" (open source) to the NVidia (proprietary).

Altogether, it now works.