[Compaq Evo Evo N610c] suspend/resume failure

Bug #1302972 reported by Urs Fleisch
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Suspend to RAM does not work on the Compaq Evo N610c with Lubuntu 14.04, it worked without problems with Lubuntu 12.04.

ProblemType: KernelOops
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-22-generic 3.13.0-22.44
ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8
Uname: Linux 3.13.0-22-generic i686
Annotation: This occured during a previous suspend and prevented it from resuming properly.
ApportVersion: 2.14.1-0ubuntu1
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: urs 1625 F.... lxpanel
CRDA: Error: [Errno 2] No such file or directory: 'iw'
Date: Sat Apr 5 08:39:47 2014
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
HibernationDevice: RESUME=UUID=53f12ff2-57b3-4ce0-b302-536297221d0a
InstallationDate: Installed on 2014-04-04 (0 days ago)
InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Daily i386 (20140403)
InterpreterPath: /usr/bin/python3.4
Lsusb:
 Bus 001 Device 002: ID 13b1:0020 Linksys WUSB54GC v1 802.11g Adapter [Ralink RT73]
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: Compaq Evo Evo N610c
PccardctlIdent:
 Socket 0:
   no product info available
 Socket 1:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
 Socket 1:
   no card
ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-22-generic root=UUID=6a24771a-325a-4568-b12d-cb7f14a87875 ro nomodeset quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-22-generic N/A
 linux-backports-modules-3.13.0-22-generic N/A
 linux-firmware 1.127
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
Title: [Compaq Evo Evo N610c] suspend/resume failure
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 05/27/2004
dmi.bios.vendor: Compaq
dmi.bios.version: 68P4F Ver. F.1B
dmi.board.name: 07F4
dmi.board.vendor: Compaq
dmi.board.version: KBC Version .
dmi.chassis.asset.tag: CNU33805XC
dmi.chassis.type: 10
dmi.chassis.vendor: Compaq
dmi.modalias: dmi:bvnCompaq:bvr68P4FVer.F.1B:bd05/27/2004:svnCompaq:pnEvoEvoN610c:pvr:rvnCompaq:rn07F4:rvrKBCVersion.:cvnCompaq:ct10:cvr:
dmi.product.name: Evo Evo N610c
dmi.sys.vendor: Compaq

Revision history for this message
Urs Fleisch (ufleisch) 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
Joseph Salisbury (jsalisbury) wrote :

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

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
Urs Fleisch (ufleisch) wrote :

Thanks for this fast feedback! After installing today's updates (linux-image-generic:i386 3.13.0.23.27 among others) and testing suspend to RAM and to disk, both worked. The only thing I changed besides the updates was removing the "nomodeset" kernel parameter. I cannot say if it was this parameter or the kernel update or anything else, but it works now. Thanks anyway for your help.

Revision history for this message
penalvch (penalvch) wrote :

Urs Fleisch, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1302972/comments/4 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.

Changed in linux (Ubuntu):
status: Incomplete → Invalid
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.