Using the method outlined in the wiki, I found that the problem seems to be fixed in 3.16.0-031600-generic. I haven't tested all the way forward till 3.18 or back to 3.13. Is this sufficient?
> Date: Sun, 2 Nov 2014 17:29:53 +0000
> From: <email address hidden>
> To: <email address hidden>
> Subject: [Bug 1387922] Re: Problem resuming from suspend after update to 3.13.0-39-generic
>
> Rehan Khamaruddin, the next step is to fully commit bisect the kernel in
> order to identify the offending commit. Could you please do this
> following https://wiki.ubuntu.com/Kernel/KernelBisection ?
>
> ** Tags added: kernel-bug-exists-upstream-3.18-rc2 needs-bisect
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1387922
>
> Title:
> Problem resuming from suspend after update to 3.13.0-39-generic
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1387922/+subscriptions
Using the method outlined in the wiki, I found that the problem seems to be fixed in 3.16.0- 031600- generic. I haven't tested all the way forward till 3.18 or back to 3.13. Is this sufficient?
> Date: Sun, 2 Nov 2014 17:29:53 +0000 /wiki.ubuntu. com/Kernel/ KernelBisection ? bug-exists- upstream- 3.18-rc2 needs-bisect /bugs.launchpad .net/bugs/ 1387922 /bugs.launchpad .net/ubuntu/ +source/ linux/+ bug/1387922/ +subscriptions
> From: <email address hidden>
> To: <email address hidden>
> Subject: [Bug 1387922] Re: Problem resuming from suspend after update to 3.13.0-39-generic
>
> Rehan Khamaruddin, the next step is to fully commit bisect the kernel in
> order to identify the offending commit. Could you please do this
> following https:/
>
> ** Tags added: kernel-
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> Problem resuming from suspend after update to 3.13.0-39-generic
>
> To manage notifications about this bug go to:
> https:/