Problem resuming from suspend after update to 3.13.0-39-generic

[Rehan Khamaruddin]

I have to push the power button twice to resume from suspend. On the first push, the computer wakes up and then immediately goes back to sleep. It actually wakes up and gives me the login screen on the second push. This problem started after the last kernel update and subsequent reboot. Please let me know if any additional information is needed.

Thanks.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-39-generic 3.13.0-39.66
ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8
Uname: Linux 3.13.0-39-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.5
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: rehan 4179 F.... pulseaudio
 /dev/snd/controlC0: rehan 4179 F.... pulseaudio
CurrentDesktop: Unity
Date: Thu Oct 30 19:27:29 2014
HibernationDevice: RESUME=UUID=796bfa06-20c4-4486-b4b3-6ea3ed8e0a7b
InstallationDate: Installed on 2012-11-12 (717 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328)
MachineType: To be filled by O.E.M. To be filled by O.E.M.
ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-39-generic root=UUID=6cbf5176-699e-40cd-8119-3e1802a1e70a ro quiet splash
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-39-generic N/A
 linux-backports-modules-3.13.0-39-generic N/A
 linux-firmware 1.127.7
RfKill:
 1: hci0: Bluetooth
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
UpgradeStatus: Upgraded to trusty on 2014-04-18 (195 days ago)
dmi.bios.date: 04/07/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2501
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: M5A99FX PRO R2.0
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2501:bd04/07/2014:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A99FXPROR2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: To be filled by O.E.M.

[Brad Figg (brad-figg)]

This change was made by a bot.

[Rehan Khamaruddin (rsk02)]

Including pm-suspend.log for completeness.

[penalvch (penalvch)]

Rehan Khamaruddin, thank you for reporting this and helping make Ubuntu better. Could you please test the latest upstream kernel available from the very top line at the top of the page (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 exactly shown as:
kernel-fixed-upstream-3.18-rc1

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.

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

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.

[Rehan Khamaruddin (rsk02)]

I have tried the kernels from this folder (amd64): http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.13.11.10-trusty/

I can reproduce the problem with the new mainline kernel also. Please let me know if this is the version that you wanted me to test. If it is, I shall go ahead and tag it as outlined by you before.

Thanks,

Rehan Khamaruddin

> Date: Sat, 1 Nov 2014 03:19:22 +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, thank you for reporting this and helping make Ubuntu better. Could you please test the latest upstream kernel available from the very top line at the top of the page (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 exactly shown as:
> kernel-fixed-upstream-3.18-rc1
>
> 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.
>
> If the mainline kernel does not fix this bug, please add the following tags:
> kernel-bug-exists-upstream
> kernel-bug-exists-upstream-VERSION-NUMBER
>
> 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.
>
> ** Tags added: latest-bios-2501
>
> ** Changed in: linux (Ubuntu)
> Importance: Undecided => Medium
>
> ** Changed in: linux (Ubuntu)
> Status: Confirmed => Incomplete
>
> ** Tags added: regresion-update
>
> --
> 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

[penalvch (penalvch)]

Rehan Khamaruddin, latest mainline kernel is 3.18-rc2. Did you test that? If that does not allow a testable scenario, please test 3.18-rc1.

[Rehan Khamaruddin (rsk02)]

There doesn't seem to be a build for trusty. Modules don't compile with 3.18. Shall I test with 3.15? That seems to be the latest for trusty.

Thanks.

On Nov 1, 2014 10:05 PM, "Christopher M. Penalver" <email address hidden> wrote:
Rehan Khamaruddin, latest mainline kernel is 3.18-rc2. Did you test
that? If that does not allow a testable scenario, please test 3.18-rc1.

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

[penalvch (penalvch)]

Rehan Khamaruddin, 3.18-rc2 is known to fail to boot into for many. Hence, did you actually test 3.18-rc1?

[Rehan Khamaruddin (rsk02)]

I tried booting both rc1 and rc2. Testing is inconclusive because I could not proceed beyond the login screen. I did test suspend from the login screen but could not get video on resume. However, the computer did not go to sleep again. I am not sure if this is reliable. Please advise on how to proceed.

Thanks for your patience.

Rehan Khamaruddin

> Date: Sun, 2 Nov 2014 05:29:13 +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, 3.18-rc2 is known to fail to boot into for many.
> Hence, did you actually test 3.18-rc1?
>
> --
> 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

[penalvch (penalvch)]

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 ?

[Rehan Khamaruddin (rsk02)]

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

[penalvch (penalvch)]

Rehan Khamaruddin, just to clarify, if you test the later mainline kernel version 3.16.0-031600-generic the problem is not reproducible?

[Rehan Khamaruddin (rsk02)]

Yes, the suspend/resume issue is not reproducible with 3.16.0-031600-generic.

On Nov 3, 2014 3:00 PM, "Christopher M. Penalver" <email address hidden> wrote:
Rehan Khamaruddin, just to clarify, if you test the later mainline
kernel version 3.16.0-031600-generic the problem is not reproducible?

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

[penalvch (penalvch)]

Rehan Khamaruddin, then you may be falling into a broke/fix/broke scenario with kernel versions.

In order to further narrow this down, could you please test for this in http://cdimage.ubuntu.com/daily-live/current/ (live environment is fine) and advise to the results?

[Rehan Khamaruddin (rsk02)]

I tried the live image (on usb) and it does not exhibit the issue I encountered with suspend in the production release. Please let me know if you need anything else tested. Note that the testing was cursory. I did not let it sit overnight as I did with the dev kernels.

Thanks.

> Date: Mon, 3 Nov 2014 23:21:49 +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, then you may be falling into a broke/fix/broke
> scenario with kernel versions.
>
> In order to further narrow this down, could you please test for this in
> http://cdimage.ubuntu.com/daily-live/current/ (live environment is fine)
> and advise to the results?
>
> --
> 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

[penalvch (penalvch)]

Rehan Khamaruddin, it would be best to attempt the exact reproduction scenario before it would be considered fixed.

[Rehan Khamaruddin (rsk02)]

Christopher, I have tested the exact scenario and it appears that 3.16 does not exhibit the issue. Let me know what to do next.

Thanks.

Rehan Khamaruddin

> Date: Wed, 5 Nov 2014 12:53:28 +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, it would be best to attempt the exact reproduction
> scenario before it would be considered fixed.
>
> --
> 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

[penalvch (penalvch)]

Rehan Khamaruddin, the next step is to fully reverse commit bisect from kernel 3.13 to 3.16 in order to identify the last bad commit, followed immediately by the first good one. Once this commit has been identified, then it may be reviewed as a candidate for backporting into your release.

Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection#How_do_I_reverse_bisect_the_upstream_kernel.3F ?

Please note, finding adjacent kernel versions is not fully commit bisecting.

Thank you for your understanding.

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

[Rehan Khamaruddin (rsk02)]

This is taking time. I hope to get back to you when done or if I have questions. Thanks.

> Date: Thu, 6 Nov 2014 16:47:03 +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 reverse commit bisect from
> kernel 3.13 to 3.16 in order to identify the last bad commit, followed
> immediately by the first good one. Once this commit has been identified,
> then it may be reviewed as a candidate for backporting into your
> release.
>
> Could you please do this following
> https://wiki.ubuntu.com/Kernel/KernelBisection#How_do_I_reverse_bisect_the_upstream_kernel.3F
> ?
>
> Please note, finding adjacent kernel versions is not fully commit
> bisecting.
>
> Thank you for your understanding.
>
> Helpful bug reporting tips:
> https://wiki.ubuntu.com/ReportingBugs
>
> --
> 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

[Rehan Khamaruddin (rsk02)]

Christopher,

I have found some more quirks along the way. The problem was reproducible going back all the way to linux-image-3.13.0-32-generic but it doesn't happen immediately as it does with linux-image-3.13.0-39-generic. Also, do I need to map this back and test the mainline also? I haven't been able to put in as much time as I had anticipated so it is going slow. Please advise.

Thanks.

Rehan Khamaruddin

> Date: Sun, 9 Nov 2014 20:03:40 +0000
> From: <email address hidden>
> To: <email address hidden>
> Subject: RE: [Bug 1387922] Re: Problem resuming from suspend after update to 3.13.0-39-generic
>
> This is taking time. I hope to get back to you when done or if I have
> questions. Thanks.
>
> > Date: Thu, 6 Nov 2014 16:47:03 +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 reverse commit bisect from
> > kernel 3.13 to 3.16 in order to identify the last bad commit, followed
> > immediately by the first good one. Once this commit has been identified,
> > then it may be reviewed as a candidate for backporting into your
> > release.
> >
> > Could you please do this following
> > https://wiki.ubuntu.com/Kernel/KernelBisection#How_do_I_reverse_bisect_the_upstream_kernel.3F
> > ?
> >
> > Please note, finding adjacent kernel versions is not fully commit
> > bisecting.
> >
> > Thank you for your understanding.
> >
> > Helpful bug reporting tips:
> > https://wiki.ubuntu.com/ReportingBugs
> >
> > --
> > 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
>
> --
> 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

[Rehan Khamaruddin (rsk02)]

To explain a bit further, I don't remember encountering this issue before linux-image-3.13.0-39-generic. Could it be that the issue is with some other package installed along with the kernel, perhaps, firmware? I am unable to reproduce the problem with 3.16. Please note that I am not a developer or even an expert Linux user and could be way off the track here.

Thanks.

> Date: Sat, 15 Nov 2014 21:04:05 +0000
> From: <email address hidden>
> To: <email address hidden>
> Subject: RE: [Bug 1387922] Re: Problem resuming from suspend after update to 3.13.0-39-generic
>
> Christopher,
>
> I have found some more quirks along the way. The problem was
> reproducible going back all the way to linux-image-3.13.0-32-generic but
> it doesn't happen immediately as it does with linux-
> image-3.13.0-39-generic. Also, do I need to map this back and test the
> mainline also? I haven't been able to put in as much time as I had
> anticipated so it is going slow. Please advise.
>
> Thanks.
>
> Rehan Khamaruddin
>
> > Date: Sun, 9 Nov 2014 20:03:40 +0000
> > From: <email address hidden>
> > To: <email address hidden>
> > Subject: RE: [Bug 1387922] Re: Problem resuming from suspend after update to 3.13.0-39-generic
> >
> > This is taking time. I hope to get back to you when done or if I have
> > questions. Thanks.
> >
> > > Date: Thu, 6 Nov 2014 16:47:03 +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 reverse commit bisect from
> > > kernel 3.13 to 3.16 in order to identify the last bad commit, followed
> > > immediately by the first good one. Once this commit has been identified,
> > > then it may be reviewed as a candidate for backporting into your
> > > release.
> > >
> > > Could you please do this following
> > > https://wiki.ubuntu.com/Kernel/KernelBisection#How_do_I_reverse_bisect_the_upstream_kernel.3F
> > > ?
> > >
> > > Please note, finding adjacent kernel versions is not fully commit
> > > bisecting.
> > >
> > > Thank you for your understanding.
> > >
> > > Helpful bug reporting tips:
> > > https://wiki.ubuntu.com/ReportingBugs
> > >
> > > --
> > > 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
> >
> > --
> > 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
>
> --
> 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 ...

[Rehan Khamaruddin (rsk02)]

Well, I got nowhere by tracing it backwards. In the meanwhile, the linux-image-generic-lts-utopic pacakage has appeared and it solves my problem. I guess this bug report can be closed now.

[penalvch (penalvch)]

Rehan Khamaruddin, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1387922/comments/22 regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.