Gigabyte P35-DS3 fails to resume

Bug #350060 reported by andybreuhan
2
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Won't Fix
Medium
Colin Ian King

Bug Description

clean install -> standby

ProblemType: KernelOops
Annotation: This occured during a previous suspend and prevented it from resuming properly.
Architecture: amd64
CurrentDmesg:
 [ 44.124358] r8169: eth0: link up
 [ 44.124364] r8169: eth0: link up
 [ 54.352026] eth0: no IPv6 routers present
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
InterpreterPath: /usr/bin/python2.6
MachineType: Gigabyte Technology Co., Ltd. P35-DS3
NonfreeKernelModules: nvidia
Package: linux-image-2.6.28-11-generic 2.6.28-11.38
ProcAttrCurrent: unconfined
ProcCmdLine: root=UUID=3133f6e4-0b47-4eee-8f98-93e6893c1376 ro quiet splash xforcevesa
ProcCmdline: /usr/bin/python /usr/share/apport/apportcheckresume
ProcEnviron: PATH=(custom, no user)
ProcVersionSignature: Ubuntu 2.6.28-11.38-generic
SourcePackage: linux
StressLog: Error: [Errno 2] No such file or directory: '/var/lib/pm-utils/stress.log'
Tags: resume suspend
Title: [Gigabyte Technology Co., Ltd. P35-DS3] suspend/resume failure [non-free: nvidia]
UserGroups:

Revision history for this message
andybreuhan (spam-andybreuhan) wrote :
Revision history for this message
Colin Ian King (colin-king) wrote :

@andybreuhan:

Looks like a faulty driver is breaking the resume. Please can you follow through the debugging steps as described in: https://wiki.ubuntu.com/DebuggingKernelSuspend

Please attach the dmesg output once you have rebooted the machine so that I can check to see which driver is causing the problem. Thanks!

summary: - System dont come up after Suspend
+ Gigabyte P35-DS3 fails to resume
Changed in linux (Ubuntu):
importance: Undecided → Medium
Changed in linux (Ubuntu):
assignee: nobody → Colin King (colin-king)
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Colin Ian King (colin-king) wrote :

This bug report was marked as Incomplete a while ago and has not had any feedback to provide the requested information. As a result this bug is being closed. Please reopen if this is still an issue in the latest Karmic 9.10 Alpha release http://cdimage.ubuntu.com/releases/karmic/ . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

Changed in linux (Ubuntu):
status: Incomplete → Won't Fix
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.