[CLEVO CO. W240EU/W250EUQ/W270EUQ] suspend/resume failure

[David Leal]

My laptop sometimes fails to come back from suspend. I will suspend it by closing the lid, and the power light on the side of the laptop will start blinking indicating it's suspended. After sometime the light will have stopped blinking, and upon opening the lid, the computer won't resume. I have to press the power button for a few seconds to get it to power up.

One time I had to remove the battery, because the laptop refused to power up after I put it on suspend.

On the next power up after a failed resume, I always get the Ubuntu "An error happened" dialog.

This originally happened on Saucy. I upgraded to Trusty in the hopes that the problem would be gone, but it's still there as well.

ProblemType: KernelOops
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-5-generic 3.13.0-5.20
ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0
Uname: Linux 3.13.0-5-generic i686
Annotation: This occured during a previous suspend and prevented it from resuming properly.
ApportVersion: 2.13.2-0ubuntu2
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: david 1356 F.... pulseaudio
Date: Tue Jan 28 22:21:25 2014
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
InstallationDate: Installed on 2013-08-19 (162 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424)
InterpreterPath: /usr/bin/python3.3
MachineType: CLEVO CO. W240EU/W250EUQ/W270EUQ
ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-5-generic root=UUID=fa95b2e7-43a7-4c3f-b083-956b3e8b3f53 ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-5-generic N/A
 linux-backports-modules-3.13.0-5-generic N/A
 linux-firmware 1.122
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
Title: [CLEVO CO. W240EU/W250EUQ/W270EUQ] suspend/resume failure
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 02/26/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.5
dmi.board.asset.tag: Tag 12345
dmi.board.name: W240EU/W250EUQ/W270EUQ
dmi.board.vendor: CLEVO CO.
dmi.board.version: V3.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd02/26/2013:svnCLEVOCO.:pnW240EU/W250EUQ/W270EUQ:pvrNotApplicable:rvnCLEVOCO.:rnW240EU/W250EUQ/W270EUQ:rvrV3.0:cvnNoEnclosure:ct10:cvrN/A:
dmi.product.name: W240EU/W250EUQ/W270EUQ
dmi.product.version: Not Applicable
dmi.sys.vendor: CLEVO CO.

[Brad Figg (brad-figg)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

  With the recent release of this Ubuntu release, would like to confirm if this bug is still present. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

    sudo apt-get update
    sudo apt-get dist-upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

 Thank you for your help, we really do appreciate it.

[David Leal (dgleal)]

I haven't experienced this bug lately, so I'm tentatively confirming it's fixed. I'll reopen if I later find I'm mistaken.