[ASUSTEK P5Q-PRO] suspend/resume problem

Bug #324805 reported by Bogdan Butnaru
6
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Won't Fix
Undecided
Andy Whitcroft

Bug Description

Not sure if this will work, but I'll try.

I suspended my computer last night, and this morning when I started it I only got a blank screen. (Keyboard LEDs weren't working, either.)

I did a hard reboot and upon login I received a bug report; in a while I got a dialog saying the report was damaged and couldn't be processed, so I don't know if it'll attach anything here.

ProblemType: KernelOops
Architecture: amd64
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/share/apport/apportcheckresume
FlagFile: suspend
InterpreterPath: /usr/bin/python2.5
NonfreeKernelModules: nvidia
OopsText: Suspend/Resume or hibernate problem

Originator: Steve Conklin <email address hidden>
Package: linux-image-2.6.28-6-generic 2.6.28-6.17
ProcAttrCurrent: unconfined
ProcCmdLine: User Name=UUID=f345b250-3225-489c-a2a5-5c7a2b21a0fd ro vga=892
ProcCmdline: /usr/bin/python /usr/share/apport/apportcheckresume
ProcEnviron: PATH=(custom, no user)
ProcVersionSignature: Ubuntu 2.6.28-6.17-generic
SourcePackage: linux
StressLog: Error: [Errno 2] No such file or directory: '/var/lib/pm-utils/stress.log'
Tags: suspend resume hibernate
Title: Suspend/Resume or hibernate problem
UserGroups:

Revision history for this message
Bogdan Butnaru (bogdanb) wrote :
Revision history for this message
Leann Ogasawara (leannogasawara) wrote : Re: ASUSTEK P5Q-PRO Suspend/Resume or hibernate problem

Hi Bogdan,

I notice you have an Nvidia graphics card. Is this reproducible every time you try to resume? I'm also curious if you have tested with the open nv driver? However with the nv driver you may experience bug 324895 but it would be good to know.

Changed in linux:
status: New → Incomplete
Revision history for this message
Bogdan Butnaru (bogdanb) wrote :

Hi Leann!

No, it's not reproducible. It only happened that one time, suspend works correctly in general. I left the report open in case it was caused by some transient bug and the logs might help finding it. Otherwise it can be safely closed.

Revision history for this message
Andy Whitcroft (apw) wrote :

As this is a one off and not reproducible, and as we have very little information we may as well close this one off for now.

Changed in linux:
assignee: nobody → apw
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.