[Dell Inc. Latitude D830] suspend/resume failure [non-free: nvidia]

Bug #337047 reported by Bin Dong
36
This bug affects 5 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

failed on suspend/resume

ProblemType: KernelOops
Annotation: This occured during a previous suspend and prevented it from resuming properly.
Architecture: i386
DistroRelease: /usr/bin/lsb_release:81: DeprecationWarning: the sets module is deprecated import sets Ubuntu 9.04
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
InterpreterPath: /usr/bin/python2.6
MachineType: Dell Inc. Latitude D830
NonfreeKernelModules: nvidia
Package: linux-image-2.6.28-8-generic 2.6.28-8.26
ProcAttrCurrent: unconfined
ProcCmdLine: User Name=UUID=ee2aad91-54cb-404d-ac9f-25e27fce2151 ro locale=zh_CN quiet splash
ProcCmdline: /usr/bin/python /usr/share/apport/apportcheckresume
ProcEnviron: PATH=(custom, no user)
ProcVersionSignature: Ubuntu 2.6.28-8.26-generic
SourcePackage: linux
StressLog: Error: [Errno 2] No such file or directory: '/var/lib/pm-utils/stress.log'
Tags: resume suspend
Title: [Dell Inc. Latitude D830] suspend/resume failure [non-free: nvidia]
UserGroups:

Revision history for this message
Bin Dong (dongbin-cn) wrote :
Revision history for this message
Andy Whitcroft (apw) wrote :

Did you recently have a suspend failure, this could have been some time before the report was triggered and offered to you. If you did, did the machine break while going to sleep, or while coming back from sleep? Is this reproducible say over 10 cycles. Has suspend ever worked in the past, if so which kernel release (cat /proc/version_signature)? Please include any information as to the circumstances leading up to this failure, for example did your battery run out? Did the machine lock up, did any messages come out? If it is reproducible could you try the suspend from VT1, press ctrl-alt-F1, login, and run pm-suspend there. If you could test and report back here that would be helpful.

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

This is a major issue now. Nearly no successful resumes on my D830 anymore.

Revision history for this message
arjanw (arjan-waardenburg) wrote :

Could you test with acpi_osi=Linux appended to the kernel options ? This fixed it for me, running bios A14.

Revision history for this message
Bin Dong (dongbin-cn) wrote :

It works on my D830 now! Great jobs, Ubuntu team. Should I change the status of the bug?

Revision history for this message
Paul Gear (paulgear) wrote :

I am experiencing the same problem. It worked almost perfectly (95% of the time at least) on 8.04, but 8.10 and 9.04 beta have been woeful. It doesn't even pass the first test of /usr/share/checkbox/scripts/suspend_test --full as described at https://wiki.ubuntu.com/KernelTeam/SuspendResumeTesting

I will test with acpi_osi=Linux and report back here.

Revision history for this message
Paul Gear (paulgear) wrote :

Note also that there is no indication that apport is logging the resume failure as a bug on reboot after the suspend_test failure.

Revision history for this message
sjd512 (steve-ton80) wrote :

arjanw's comment: Adding acpi_osi=Linux to the kernel options and updating to bios A14.
This fixed the issue for me. Thanks!

I intended to test with the old bios but I had switched to grub2 and edited the wrong file.
Didn't notice until after the bios update. So I can not confirm if the kernel option by itself is enough.

Revision history for this message
Carl Ådahl (carl-adahl) wrote :

For me, on bios A11, the kernel option itself didn't help. Failed to resume on second test (AC connected). Will try again now that I have A14.

Revision history for this message
Paul Gear (paulgear) wrote :

I've suspended/resumed about 15 times since i added acpi_osi=Linux to the kernel options, and it has only failed twice. That is a big improvement. One failure to resume occurred when i plugged in the power and removed the battery while it was suspended (i do this quite often to keep the battery cool, which i'm told extends its life).

Can anyone provide a link to the latest BIOS and instructions about checking the current version?

Revision history for this message
sjd512 (steve-ton80) wrote :

An update on my issues:

acpi_osi=Linux: X comes back after resume but I am plagued with long iowait times when starting apps, the system is basically unusable and I have to reboot. Anyone else notice this?

acpi_osi=s3_mode: resume usually works but does lock up sometimes, no iowait issues.

I used to have 8.04 32bit using the 177 NVIDIA drives with no resume issues.
When I updated to 180 NVIDIA resume no longer worked.

I am currently using NVIDIA 180 drivers with 9.04 64bit on an ext3 partition.

Revision history for this message
sjd512 (steve-ton80) wrote :

One more comment.

Looks like my issues with acpi_osi=s3_mode is resume on lid close. resume from the menu seems to work with no iowait issues.

Revision history for this message
dirk (dirk-kuijsten) wrote :

I had the high iowait problem after resume from suspend with Ubuntu 10.04/Lucid (64-bit) on the Latitude D830.
Standard kernel version: 2.6.32-22-generic
Using acpi_osi=Linux didn't work for me, on none of these Bios versions: A11, A15 and A14.
Before suspend:
sudo dd if=/dev/sda1 of=/dev/null bs=4096 count=100k
would result in about 58MB/s
after resume: result would be only 1MB/s or less

But kernel version 2.6.34 seems to work ok now, without using the acpi_osi setting. Full version: 2.6.34-020634-generic
Downloaded from (64-bit):
http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.34-lucid/

Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . 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.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: kj-expired
Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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