[Asus A8N-SLI SE (4Gb RAM)] suspend/resume failure [non-free: nvidia]

Bug #347150 reported by ksg
44
This bug affects 8 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Won't Fix
Medium
Unassigned

Bug Description

Computer does not go into suspend mode properly.
Selecting suspend causes hard disks and screens to power off but the fans still run.
The system will then not wake-up from this state and I have to hit the reset button on the case or dis/re-connect the power.

FYI: Same system does also freeze from time to time (freeze = become totally unresponsive, screen will stop updating and system will not respond to mouse & keyboard), seems to happen most often when using the update manager - but also happens sometime when viewing flash things in firefox. So it may be the graphics card or the network drivers. I, perhaps, have an uncommon setup with the nvidia card: I am using xinerama across 1 analogue and 1 DVI screen.

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 System Product Name
NonfreeKernelModules: nvidia
Package: linux-image-2.6.28-11-generic 2.6.28-11.36
ProcAttrCurrent: unconfined
ProcCmdLine: root=UUID=4c2755c9-b0aa-45e5-873b-6c56c082b579 ro xforcevesa quiet splash
ProcCmdline: /usr/bin/python /usr/share/apport/apportcheckresume
ProcEnviron: PATH=(custom, no user)
ProcVersionSignature: Ubuntu 2.6.28-11.36-generic
SourcePackage: linux
StressLog: Error: [Errno 2] No such file or directory: '/var/lib/pm-utils/stress.log'
Tags: resume suspend
Title: [System manufacturer System Product Name] suspend/resume failure [non-free: nvidia]
UserGroups:

Revision history for this message
ksg (keith-groves) wrote :
affects: ubuntu → linux (Ubuntu)
Revision history for this message
ksg (keith-groves) wrote :

The "FYI" about the system freezing is probably the issue being tracked in bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/157777 - from reading around that it appears to be the combination of dual-core amd64 + nvidia + network causing the problem.

Revision history for this message
StarkRG (starkrg) wrote :

I am having a similar problem (though no freezes as I can recall), system seems to go down to sleep fine, disks spin down, but fans and power supply stay on at full power (as opposed to the minimum amount of power required for sleep mode).

I'm using a single core AMD64 on an A8N-SLI (though I don't know the exact model) with a single nVidia video card and am using the onboard NIC. I only have 1GB of RAM.

I can provide any logs or test results that might be useful in fixing this problem.

Revision history for this message
MichalR (rehak-michal) wrote :

I am having the same issue with Asus a8n-sli Deluxe in Jaunty.

Revision history for this message
MichalR (rehak-michal) wrote :

I have made the suspend to work on Asus a8n-sli Deluxe by setting the USB Legacy option in the bios to Disabled.

Revision history for this message
Adolfo R. Brandes (arbrandes) wrote :

I can confirm MichalR's prognosis: disabling USB Legacy support makes suspend work on an Asus A8N-SLI Premium, under Ubuntu Jaunty 9.04 amd64. Thanks!

Revision history for this message
Steve Conklin (sconklin) wrote :

ksg,

Does this bios workaround also work for you? Multiple causes can lead to the same symptoms and I
would like to know whether the fix works for your model also.

Thanks

Steve Conklin (sconklin)
Changed in linux (Ubuntu):
assignee: nobody → Steve Conklin (sconklin)
Steve Conklin (sconklin)
Changed in linux (Ubuntu):
status: New → In Progress
importance: Undecided → Medium
Revision history for this message
ksg (keith-groves) wrote : Re: [Bug 347150] Re: [Asus A8N-SLI SE (4Gb RAM)] suspend/resume failure [non-free: nvidia]

I was hoping that I wouldn't be needed for testing this workaround...
my boot menus require me to use my usb keyboard which only works for
the boot menus if the usb legacy bios setting is on.

Will let you know later.

 - ksg

2009/8/18 Steve Conklin <email address hidden>:
> ksg,
>
> Does this bios workaround also work for you? Multiple causes can lead to the same symptoms and I
> would like to know whether the fix works for your model also.
>
> Thanks
>
> --
> [Asus A8N-SLI SE (4Gb RAM)] suspend/resume failure [non-free: nvidia]
> https://bugs.launchpad.net/bugs/347150
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “linux” package in Ubuntu: New
>
> Bug description:
> Computer does not go into suspend mode properly.
> Selecting suspend causes hard disks and screens to power off but the fans still run.
> The system will then not wake-up from this state and I have to hit the reset button on the case or dis/re-connect the power.
>
> FYI: Same system does also freeze from time to time (freeze = become totally unresponsive, screen will stop updating and system will not respond to mouse & keyboard), seems to happen most often when using the update manager - but also happens sometime when viewing flash things in firefox.  So it may be the graphics card or the network drivers.  I, perhaps, have an uncommon setup with the nvidia card: I am using xinerama across 1 analogue and 1 DVI screen.
>
> 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 System Product Name
> NonfreeKernelModules: nvidia
> Package: linux-image-2.6.28-11-generic 2.6.28-11.36
> ProcAttrCurrent: unconfined
> ProcCmdLine: root=UUID=4c2755c9-b0aa-45e5-873b-6c56c082b579 ro xforcevesa quiet splash
> ProcCmdline: /usr/bin/python /usr/share/apport/apportcheckresume
> ProcEnviron: PATH=(custom, no user)
> ProcVersionSignature: Ubuntu 2.6.28-11.36-generic
> SourcePackage: linux
> StressLog: Error: [Errno 2] No such file or directory: '/var/lib/pm-utils/stress.log'
> Tags: resume suspend
> Title: [System manufacturer System Product Name] suspend/resume failure [non-free: nvidia]
> UserGroups:
>

Revision history for this message
ksg (keith-groves) wrote :

Sadly changing the bios setting doesn't solve the probklem for me. My system has the same problem regardless of the legacy usb devices setting being on or off.

Revision history for this message
MichalR (rehak-michal) wrote :

Just guessing but, did you disconnected all usb devices and cables? On one machine I had to disconnect everything from the usb ports, only then suspend started to work.

Revision history for this message
Heiko Ettelbrück (hbrucky) wrote :

I guess this might be related to the issue described here: http://bugzilla.kernel.org/show_bug.cgi?id=9528

Although it's rather old, it seems like there was no final solution, that's why it still occurs even in Jaunty (where I found it, and solved it using the minimal patch attached to the kernel bug with a custom built kernel) and Karmic (to which I just upgraded and where I found the issue still existing).

It would be great if either that patch could be added to the standard Karmic kernel (at least as a short-term solution) and if someone with better contacts to the (vanilla) kernel guys could try to get it into the vanilla kernel (to avoid increasing the number of patches Ubuntu applies to the vanilla kernel).

Thanks and best regards
Heiko

Revision history for this message
Heiko Ettelbrück (hbrucky) wrote :

Addition:
If you'd like to quickly test whether the solution provided by the patch mentioned above helps on your machine, boot with kernel parameter "acpi_sleep=old_ordering" and try going to standby (ACPI S3) again (as described in the kernel bug). I use that workaround on my A8N-SLI Premium for now and it worked with Jaunty as well as it works now with Karmic.

Steve Conklin (sconklin)
Changed in linux (Ubuntu):
assignee: Steve Conklin (sconklin) → nobody
Revision history for this message
graydo64 (personal) wrote :

Thanks Heiko Ettelbruck - adding the kernel parameter allowed me to suspend to ram running karmic with the nVidia 190.42 driver with a GeForce 6600GT and a8n sli delux.

Revision history for this message
Uwe (uwe-hermes) wrote :

This also solved the problem on my installation, karmic, A8n-SLI Premium 2GB RAM, single core AMD64 processor and GeForce 6600GT graphics board.
For all the newbies like me, the kernel parameter in Heiko's solution is added to the # kopt line in the /boot/grub/menu.lst file.
Any chance this patch can be implemented by default? What are other effects of this setting?

Revision history for this message
altima (timashkov) wrote :

and what about GRUB2? where do I add "acpi_sleep=old_ordering" in GRUB2 where there's no menu.lst?

Revision history for this message
altima (timashkov) wrote :

in grub2 editing /etc/default/grub helps. add acpi_sleep=old_ordering to GRUB_CMDLINE_LINUX_DEFAULT line

Revision history for this message
Tomasz (tomasz-wiszkowski) wrote :

hi,

I too have A8n-SLI board. I just checked the old_ordering acpi setting, but it did not help. The machine hangs up right before entering S3 and i'm left with just blinking cursor; my boot cmd line:

BOOT_IMAGE=/vmlinuz-2.6.32-24-generic root=/dev/mapper/Master-root ro quiet acpi_sleep=old_ordering

i thought this may be the same issue as #145112, but then it's not limited to nvidia gl drivers (it happens with open drivers, too), besides my system works pretty stable. the closest one i see is #157777, but it's been marked invalid for some time now.

please kindly let me know what / how should i collect to help fixing the issue

best regards,
tomek

Revision history for this message
Tomasz (tomasz-wiszkowski) wrote :

ok, forget it; i'm not sure what i did, but i don't see the problem any longer.

Changed in linux (Ubuntu):
status: In Progress → Confirmed
Revision history for this message
Brad Figg (brad-figg) wrote : Unsupported series, setting status to "Won't Fix".

This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

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