[Asus K55VM] It does not suspend after upgrading to 14.04

Bug #1335795 reported by Nisarg Jhaveri
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

I recently upgraded to Ubuntu 14.04 from 13.10
After that my laptop does not suspend.
The laptop has NVIDIA GEFORCE GT 630M Graphic card, with nouveau. It seems to fails when suspending.

nisarg@nisarg:~$ cat /proc/version_signature
Ubuntu 3.13.0-30.54-generic 3.13.11.2

Here is the syslog.

Jun 30 14:52:22 nisarg kernel: [10157.974142] PM: Syncing filesystems ... done.
Jun 30 14:52:22 nisarg kernel: [10158.308806] PM: Preparing system for mem sleep
Jun 30 14:52:27 nisarg kernel: [10158.558616] Freezing user space processes ... (elapsed 0.001 seconds) done.
Jun 30 14:52:27 nisarg kernel: [10158.560394] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
Jun 30 14:52:27 nisarg kernel: [10158.561577] PM: Entering mem sleep
Jun 30 14:52:27 nisarg kernel: [10158.561870] Suspending console(s) (use no_console_suspend to debug)
Jun 30 14:52:27 nisarg kernel: [10158.562061] sd 0:0:0:0: [sda] Synchronizing SCSI cache
Jun 30 14:52:27 nisarg kernel: [10158.562117] sd 0:0:0:0: [sda] Stopping disk
Jun 30 14:52:27 nisarg kernel: [10158.580826] nouveau [ DRM] suspending display...
Jun 30 14:52:27 nisarg kernel: [10158.580828] nouveau [ DRM] unpinning framebuffer(s)...
Jun 30 14:52:27 nisarg kernel: [10158.580831] nouveau [ DRM] evicting buffers...
Jun 30 14:52:27 nisarg kernel: [10158.580832] nouveau [ DRM] waiting for kernel channels to go idle...
Jun 30 14:52:27 nisarg kernel: [10158.580876] nouveau [ DRM] suspending client object trees...
Jun 30 14:52:27 nisarg kernel: [10158.581164] nouveau [ DRM] suspending kernel object tree...
Jun 30 14:52:27 nisarg kernel: [10160.580652] nouveau E[ PDISP][0000:01:00.0][0xc000857c][ffff8802225fd700] fini timeout, 0xc2071008
Jun 30 14:52:27 nisarg kernel: [10160.580654] nouveau E[ PDISP][0000:01:00.0][0xc000857c][ffff8802225fd700] failed suspend, -16
Jun 30 14:52:27 nisarg kernel: [10160.580655] nouveau E[ DRM] 0xd1500000:0xd15c7c00 suspend failed with -16
Jun 30 14:52:27 nisarg kernel: [10160.580696] nouveau E[ DRM] 0xdddddddd:0xd1500000 suspend failed with -16
Jun 30 14:52:27 nisarg kernel: [10160.580797] nouveau E[ DRM] 0xffffffff:0xdddddddd suspend failed with -16
Jun 30 14:52:27 nisarg kernel: [10160.581459] nouveau E[ DRM] 0xffffffff:0xffffffff suspend failed with -16
Jun 30 14:52:27 nisarg kernel: [10160.581559] nouveau [ DRM] resuming display...
Jun 30 14:52:27 nisarg kernel: [10160.581578] nouveau E[ DRM] bo ffff8801f711e800 pinned elsewhere: 0x00000002 vs 0x00000004
Jun 30 14:52:27 nisarg kernel: [10160.581579] [drm:drm_helper_resume_force_mode] *ERROR* failed to set mode on crtc ffff8800befd1000
Jun 30 14:52:27 nisarg kernel: [10160.595633] pci_pm_suspend(): nouveau_pmops_suspend+0x0/0xb0 [nouveau] returns -16
Jun 30 14:52:27 nisarg kernel: [10160.595638] dpm_run_callback(): pci_pm_suspend+0x0/0x150 returns -16
Jun 30 14:52:27 nisarg kernel: [10160.595642] PM: Device 0000:01:00.0 failed to suspend async: error -16
Jun 30 14:52:27 nisarg kernel: [10160.595703] PM: Some devices failed to suspend, or early wake event detected

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-30-generic 3.13.0-30.54
ProcVersionSignature: Ubuntu 3.13.0-30.54-generic 3.13.11.2
Uname: Linux 3.13.0-30-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: nisarg 3437 F.... pulseaudio
                      nisarg 19771 F.... pulseaudio
CRDA:
 country IN:
  (2402 - 2482 @ 40), (N/A, 20)
  (5170 - 5250 @ 40), (N/A, 20)
  (5250 - 5330 @ 40), (N/A, 20), DFS
  (5735 - 5835 @ 40), (N/A, 20)
CurrentDesktop: Unity
Date: Mon Jun 30 15:05:58 2014
HibernationDevice: RESUME=UUID=8d9c6f2d-29cc-443a-8864-b5bdc278d3f5
InstallationDate: Installed on 2014-01-08 (172 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
MachineType: ASUSTeK COMPUTER INC. K55VM
ProcFB:
 0 inteldrmfb
 1 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-30-generic root=UUID=33430ee0-8da8-4984-9369-153bf9f4aa34 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-30-generic N/A
 linux-backports-modules-3.13.0-30-generic N/A
 linux-firmware 1.127.4
SourcePackage: linux
UpgradeStatus: Upgraded to trusty on 2014-06-29 (1 days ago)
dmi.bios.date: 09/11/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: K55VM.211
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: K55VM
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrK55VM.211:bd09/11/2012:svnASUSTeKCOMPUTERINC.:pnK55VM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK55VM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: K55VM
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

Revision history for this message
Nisarg Jhaveri (nisargjhaveri) wrote :
Revision history for this message
Brad Figg (brad-figg) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
penalvch (penalvch) wrote : Re: It does not suspend after upgrading to 14.04

Nisarg Jhaveri, 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. For example:
kernel-fixed-upstream-3.16-rc3

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.

tags: added: latest-bios-211 regression-release
Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
summary: - It does not suspend after upgrading to 14.04
+ [Asus K55VM] It does not suspend after upgrading to 14.04
Revision history for this message
Nisarg Jhaveri (nisargjhaveri) wrote :

I tested this on mainline kernel 3.14.1

It seems to be working perfectly.

Now, I want to know that by when, if any, update to that version of kernel will be provided as stable official version?
Because as far as I understand, using kernel like this is not safe enough, As I am not an Ubuntu Developer and I don't want to run into more major problems!

Thank you

tags: added: kernel-fixed-upstream kernel-fixed-upstream-3.14.1
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
penalvch (penalvch) wrote :

Nisarg Jhaveri, the next step is to fully reverse commit bisect the kernel in order to identify the fix commit. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection#How_do_I_reverse_bisect_the_upstream_kernel.3F ?

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
tags: added: needs-reverse-bisect
Revision history for this message
Nisarg Jhaveri (nisargjhaveri) wrote :

Hello Christopher,

I saw the mapping of Ubuntu kernels to upstream kernel, but couldn't find Ubuntu kernel 3.13.0-30.54.
So, I tested assuming Ubuntu 3.13.0-29.52 is the current kernel, which is v3.13.11.2 in upstream

I got that the bug is first fixed in v3.14-rc1-trusty.

I cannot go further with commit by commit reverse bisecting, as I don't have that much time and confidence. Sorry for that.

Still, I would like if I can help fixing this bug in some other way(easier way :P)

Thanks

Revision history for this message
penalvch (penalvch) wrote :

Christian Gonzalez, please do not mark this bug a duplicate of any other or vice versa.

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.