[Asus P5K-E] suspend/resume failure

Bug #349102 reported by Squall
38
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Hallo,
ich glaube es handelt sich um ein wichtiges Problem.

Danke.

ProblemType: KernelOops
Annotation: This occured during a previous suspend and prevented it from resuming properly.
Architecture: amd64
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
InterpreterPath: /usr/bin/python2.6
MachineType: System manufacturer P5K-E
NonfreeKernelModules: nvidia
Package: linux-image-2.6.28-11-generic 2.6.28-11.37
ProcAttrCurrent: unconfined
ProcCmdLine: root=UUID=4bb22b4f-13c6-4084-90af-0d8e1e70586c ro quiet splash
ProcCmdline: /usr/bin/python /usr/share/apport/apportcheckresume
ProcEnviron: PATH=(custom, no user)
ProcVersionSignature: Ubuntu 2.6.28-11.37-generic
SourcePackage: linux
StressLog: Error: [Errno 2] No such file or directory: '/var/lib/pm-utils/stress.log'
Tags: resume suspend
Title: [System manufacturer P5K-E] suspend/resume failure [non-free: nvidia]
UserGroups:

Revision history for this message
Squall (squallleonheart7) wrote :
Kees Cook (kees)
security vulnerability: yes → no
visibility: private → public
Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

*This is an automated response*

Could you please take a look the triage and debugging guide at https://wiki.ubuntu.com/DebuggingKernelSuspendHibernateResume, specifically the Information Gathering section. Please provide any answers to the additional questions outlined there. Thanks.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Oleg Yermakov (epushiron) wrote :

  Okay, I run exactly the same motherboard (Asus P5K-E), and have the same problems.

1) I run the latest BIOS (1301 beta),
2) I have disabled the non-free nvidia driver (now there's no non-free drivers at all),

  The problem still reproduces. It reproduces every time, from bying this M/B.

  The problem is: it doesn't go to standby; instead it switches to empty text-mode screen (nvidia driver) OR shuts down monitor (nv driver), then hangs.

Will collect some additional info now.

BTW, you can edit header to:
[Asus P5K-E] suspend/resume failure

Revision history for this message
Olivier Six (olivier-six-amnesix) wrote : Re: [Bug 349102] Re: [System manufacturer P5K-E] suspend/resume failure [non-free: nvidia]

The funny thing is : yesterday I installed nvidia 1.80 driver, and the
problem disappeared at once.

Oleg Yermakov wrote:
> Okay, I run exactly the same motherboard (Asus P5K-E), and have the
> same problems.
>
> 1) I run the latest BIOS (1301 beta),
> 2) I have disabled the non-free nvidia driver (now there's no non-free drivers at all),
>
> The problem still reproduces. It reproduces every time, from bying
> this M/B.
>
> The problem is: it doesn't go to standby; instead it switches to empty
> text-mode screen (nvidia driver) OR shuts down monitor (nv driver), then
> hangs.
>
> Will collect some additional info now.
>
> BTW, you can edit header to:
> [Asus P5K-E] suspend/resume failure
>

summary: - [System manufacturer P5K-E] suspend/resume failure [non-free: nvidia]
+ [Asus P5K-E] suspend/resume failure
Revision history for this message
Oleg Yermakov (epushiron) wrote :

nvidia-180 was already installed when I reported this problem :-(

I read the
https://wiki.ubuntu.com/DebuggingKernelSuspendHibernateResume document, and I can say:
1) Caps lock doesn't blink.
2) Suspending from text mode doesn't work, because screen turns off at the end of the process. So I suspended via SSH. dm-suspend says nothing, /var/log/messages said nothing, /var/log/syslog said some info, but I don't think it's relevant (see attachment.
3) I tried to suspend without X started, no luck.
4) I disabled «ACPI 2.0 support» in BIOS, no luck.

Next, I followed the https://wiki.ubuntu.com/DebuggingKernelSuspend doc:
I got the line containing
   Magic number: 5:460:72
But nothing with word «hash» after it.
Manual said «If you get a device number rather than name, lspci and /sys/devices/pci* are your friends.» , but I don't see how to match it to my number. lspci and ls -R /sys/devices/pci0000\:00/ are attached, though I don't think they are relevant.

What can I do now to diagnose this problem?
 .. Feci quod potui ..

Revision history for this message
Oleg Yermakov (epushiron) wrote :
Revision history for this message
Oleg Yermakov (epushiron) wrote :
Revision history for this message
Oleg Yermakov (epushiron) wrote :

This bug is still «Incomplete»
What additional info is required?

Changed in linux (Ubuntu):
status: Incomplete → New
Revision history for this message
walterav (walterav) wrote :

Asus p5k-e wifi/ap bios 1202, Ati hd2600xt

Fixed!
Ubuntu 9.10 alpha3 AMD64:
Sleep:
From a live cd, after pressing "suspend" from the quit "Shut down menu" with a couple of Firefox tabs open, the system sleeps fine. All harddisks go down, monitor goes to sleep, etc etc, blinking power-led on chassis shows that it is sleeping fine.
Wake:
After half an hour I turned on the machine with the power-button, screen wakes, audio is back, "tested without extra ati/AMD drivers".
BUG "network manager applet" died when woke up, so no network, went to terminal typed :
sudo -s
ifconfig eth0 up
dhclient eth0
Right now I'm typing this comment from the suspended machine.

Ubuntu 9.04 i386:
hang: blinking cursor on blackscreen when using suspend/hibernate! The system will not even go to sleep and needs a reset! "Harddisk screen etc stays on"

Revision history for this message
walterav (walterav) wrote :

Asus P5k-e wifi/ap bios 1202, Core2Quad Q6600, ati hd2600xt

Fixed!
ubuntu 9.10 beta AMD64:Works! + "ati driver from 'hardware and drivers' option"

It sleeps and wakes fine, even Restart after sleep/wake works at the moment.

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Marking this fixed per the previous comments. Thanks.

Changed in linux (Ubuntu):
status: New → Fix Released
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.