Ubuntu
linux package

[Gateway GT5628] suspend/resume failure

Bug #1292987 reported by nvsoar
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Triaged
Medium
Unassigned

Bug Description

Trusty Tahr -14Mar2014 version, installed ~1800 14Mar14; zone -7
On keystroke following suspend - hard drive spins up; monitor remains in standby; no apparent response to keyboard or mouse.

ProblemType: KernelOops
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-17-generic 3.13.0-17.37
ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6
Uname: Linux 3.13.0-17-generic i686
Annotation: This occured during a previous suspend and prevented it from resuming properly.
ApportVersion: 2.13.3-0ubuntu1
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: w8 1877 F.... pulseaudio
 /dev/snd/controlC0: w8 1877 F.... pulseaudio
Date: Sat Mar 15 15:07:03 2014
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
HibernationDevice: RESUME=UUID=520a728e-0b85-43bb-8f87-6ae5f3197efb
InstallationDate: Installed on 2014-03-15 (0 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha i386 (20140314)
InterpreterPath: /usr/bin/python3.4
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.
MachineType: Gateway GT5628
ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-17-generic root=UUID=d635174c-dca4-4f81-a321-f6979a923261 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-17-generic N/A
 linux-backports-modules-3.13.0-17-generic N/A
 linux-firmware 1.126
RfKill:

SourcePackage: linux
Title: [Gateway GT5628] suspend/resume failure
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 02/10/2008
dmi.bios.vendor: Intel Corp.
dmi.bios.version: DPP3510J.15A.0304.2008.0210.1950
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: DG33SXG2
dmi.board.vendor: Intel Corporation
dmi.board.version: AAD94468-403
dmi.chassis.type: 3
dmi.modalias: dmi:bvnIntelCorp.:bvrDPP3510J.15A.0304.2008.0210.1950:bd02/10/2008:svnGateway:pnGT5628:pvr:rvnIntelCorporation:rnDG33SXG2:rvrAAD94468-403:cvn:ct3:cvr:
dmi.product.name: GT5628
dmi.sys.vendor: Gateway

Revision history for this message
nvsoar (nvsoar) 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-rc7-trusty/

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

Tested kernel v3.14-rc7-trusty with Trusty 18Mar version downloaded, installed and updated ~2000 18Mar14; Zone -7.

Suspend resume failed to complete; fans came on, monitor came out of sleep state, no mouse arrow, no keyboard response. Could get a terminal via ctl+alt+f2 - could enter user name; no request for password followed.

For info - same behavior noted with saucy on this machine; both operating systems are located on an external hard drive.

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug.

Please follow the instructions on the wiki page[0]. The first step is to email the appropriate mailing list. If no response is received, then a bug may be opened on bugzilla.kernel.org.

Once this bug is reported upstream, please add the tag: 'kernel-bug-reported-upstream'.

[0] https://wiki.ubuntu.com/Bugs/Upstream/kernel

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

Other bug subscribers

Remote bug watches

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