[Asus UX31A] suspend/resume failure

This change was made by a bot.

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.14 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.14-rc7-trusty/

Affects me too, looking for older bugs i found one on 13.03 that looks similar:
Bug #1184262
My working bypass is to issue a "sudo killall NetworkManager" after resuming and this works again (trying just to touch the sleep parameter does nt fix the problem)
I use a Lenovo X220 with i5

Have tested 3.14.0 and 3.11.10 kernels - same problem take place.
In Ubuntu 12.04 with latest kernel (probably it 3.11?) - everything OK.

Plus. Doesn't work sound. Microphone too.

eric aquaronne, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

Sergei Solo, could you please test the latest upstream kernel available (not the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-3.14-rc7

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

Christopher, I have tested 3.14.0 and 3.11.10 kernels - same problem take place.

Tags updated.

p.s. In Ubuntu 12.04 with latest kernel (probably it 3.11?) - everything OK.

Same story, different notebook (mine is a DELL XPS13).

No wireless after suspend/resume, but bluetooth seems ok.

I install all updates available on April 10, bug still exist. I captured video that showing what is going on, you can look:
http://www.youtube.com/watch?v=ZOO-gAbAox4

Only on 36 second it become suspended (suspending took 27 seconds).

Same here, everything was ok with 12.04 (all kernels).

I think this is connected to the iwlwifi module. Maybe there should be an addition to the bug description saying something like "Network manager suspends but is unable to reconnect to Wifi."

Same problem here with 14.04 and ralink rt73 chipset. Worked perfectly with 13.10

Not related with SUSPEND_MODULES="rt73usb" in /etc/pm/config.d/load (already done and doesn't resolve).

sudo rfkill list
1: phy0: Wireless LAN
        Soft blocked: no
        Hard blocked: no

This is duplicate of #1286552, there are 24 people affected and many others duplicates :

    Bug #1290055
    Bug #1293928
    Bug #1294576
    Bug #1295285
    Bug #1309769

And nobody is assigned to ??

Not a isolated problem :

http://ubuntuforums.org/showthread.php?t=2218043
http://ubuntuforums.org/showthread.php?t=2218445

kernel 3.14-1 from http://kernel.ubuntu.com/~kernel-ppa/mainline does'nt resolve the problem

Maybe it's not kernel related, cause actualy with 3.11 on 14.04, the wifi doesn't reconnect after suspend either...

I have an Asus X61SL laptop suffering from the same problem and I solved like this:
First make use 'nmcli nm' to check the stats of the network manager, if its stats is asleep then all you have to do is this : 'sudo nmcli nm sleep false' and it will start working. To make the change permenant add the following script to '/etc/pm/sleep.d':

#!/bin/sh

case "${1}" in
        resume|thaw)
  nmcli nm sleep false
                ;;
esac

The workaround posted by OssNass worked for me too.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1295285/comments/20

Linux machine-name 3.13.0-24-generic #47-Ubuntu SMP Fri May 2 23:30:00 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

      Manufacturer: ASUSTeK Computer Inc.
        Product Name: K52Jc
        Version: 1.0
        Wake-up Type: Power Switch

wifi atheros ath9k

My Dell XPS L502X (RealTek gigabit eth0) is also affected by this bug. After suspend/resume, even

sudo service network-manager restart

can not bring back the LAN connectivity

I was having this same problem on Ubuntu 14.04 and after a couple of days of trying to fix it, I found a file inside /etc/pm/sleep.d/ which is called 99dw1704.
This file handles disabling and enabling the wl module on hibernate and suspend. All I had to do to fix it is to run:
sudo chmod -x /etc/pm/sleep.d/99dw1704 and everything ran fine after this.