Does not resume from suspend

Please try with the "nv" driver.
--
Matthew Garrett | <email address hidden>

I've attached any information that may be relevant. Please ask for more if needed. As a side note: when resuming, even though the machine apparently has hung, the sysrq reboot magic key works.

Ahh, sorry, a slip of mind there. I am using the 'nv' driver, not 'nvidia'.

Please test 2.6.17-8.22 kernel.

Still an issue. Ironically, hibernate was fixed although I hadn't opened a bug about it :-) Thanks

Still an issue with -10

I could suspend a few times and resuming without video but with the rest of the system working. In the logs there were output about nvidia module exception.

Thanks this bug report and for attaching command output. Some of these commands need to be run with root access in order to get full information required for debugging, so it would it be possible for you to run the following and attach the output?

uname -a

sudo lspci -vv

sudo lspci -vvn

sudo dmidecode

It would also be helpful if you could try to hibernate/suspend and after that fails, restart your system and attach /var/log/kern.log.0 as well.

Thanks again, and sorry to ask you to do things twice!

Resume from suspend doesn't work with 2.6.20-5-generic #2 SMP on Feisty either. I turned off all internal devices from the BIOS to make sure it's not , say the NIC, that causes problems.

Oh. Another thing I noticed (with .17 and .20) : I suspend. I resume. The system resumes temporarily but then crashes. I can tell this because if I hit caps lock all the time the led goes on and off until the kernel crashes and there is no response and that (at least under edgy) if I was playing music before my attempt to hibernate, I get to hear a couple of seconds of music. It never gets to display anything though ('nv' driver).

All my attempts were from GDM.

Marking as confirmed based on available logs.

Vassilis, it will also be useful to have the /var/log/kern.log.0 file from after a crash: Boot, suspend/resume to get the crash, reboot, then attach /var/log/kern.log.0 to this bug report. Thanks!

Please read and try the suggestions contained in :

https://wiki.ubuntu.com/KernelSuspendDebugging

I would like you to try something. Log into X using the nvidia driver. Close any essential applications just in case. Then go into suspend - wait for approx 2 min then hit a key to resume. Even though you get a blank screen and hard drive activity, just give it some time. Once the hard disk light goes off wait for approx. 10 more min. Tell me if the display comes back on within that extra 10 min. I had a similar issue and could show you how to fix it.

Suspend/resume was working fine for me up until a few days ago (dell latitude d820). Now resume sometimes fails with black screen, or the machine reboots. I have noticed an oops in the kernel log file (nvidia module). But with the nv driver, I still can't suspend/resume.

Can you please attach a kernel log containing the "oops"?

Also, if you try the procedure at https://wiki.ubuntu.com/DebuggingKernelSuspend, we might learn about the problem.

Thanks!

Pending upstream fixes might help your problem. Try the daily ISO from http://cdimage.ubuntu.com/daily-live/current on 4/2

actually, suspend/resume has worked the last few times, maybe my problem got fixed with the acpi-support update of yesterday? I haven't changed my config. But the oops is probably still usefull to look at, attaching.

There are several oopses. After the resume failed, I tried a few times with the sysrq keys, and that lead to more oopses it seems.

I'm closing this as fix released for the Feisty kernel, based on Jos' most recent comment; Jos, if you are seeing other errors, please open a new bug report, we'll keep this going for the suspend/resume problem.

It is not fixed (system is current 2007-04-16). I've seen it happen a few times since. Typically if compiz was running during suspend. I'm using nvidia driver 9755. It also happens sometimes when running metacity.

Vassilis, you'll note that I marked this as "fix released" for 2.6.20, based on other comments. If this doesn't match your experience, please do change the 2.6.20 status back to confirmed (yes, normally bad form to confirm one's own bug, but OK in this case, I think!).

If this is fixed in 2.6.20, then it is unlikely that there will be a fix applied to 2.6.17 unless one of the conditions on [1] are met. So, two questions: Was there any data loss as a result of this problem? and Did this work properly in Dapper or any previous release? Thanks!

[1] https://wiki.ubuntu.com/StableReleaseUpdates

Jos, since this is still occurring for you, could you please try the procedure described in [1]? It might also be worth trying Dennis's procedure from comment #20. The more we can pin this down, the more likely we are to being able to find an fix it.

[1] https://wiki.ubuntu.com/DebuggingKernelSuspend

Just had the problem when I came home from work. Black screen on resume, can not switch VT, no magic sysrq, only the power button works. This time it was without any compiz stuff, just plain metacity. I'd say I get some 80% success rate. I don't have time now, but will try to get more info using that procedure later today.

Ok, I tried the acpi debug procedure. The driver that was the 'likely culprit' was serio0 in my case. I looked in the lsmod output and found a driver serio_raw, which I added to the MODULES in acpi-support. This seems to have fixed it, I have tried to suspend/resume more than 10 times, and it worked every time. But I'm not convinced it's solved yet, normally I suspend/resume several times per day, so in the next few days I'll let you know. As a reference for other users my /etc/default/acpi-support: (dell latitude D820)

root@duet-feisty ~ # cat /etc/default/acpi-support

# Comment the next line to disable ACPI suspend to RAM
ACPI_SLEEP=true

# Comment the next line to disable suspend to disk
ACPI_HIBERNATE=true

# Change the following to "standby" to use ACPI S1 sleep, rather than S3.
# This will save less power, but may work on more machines
ACPI_SLEEP_MODE=mem

# Add modules to this list to have them removed before suspend and reloaded
# on resume. An example would be MODULES="em8300 yenta_socket"
#
# Note that network cards and USB controllers will automatically be unloaded
# unless they're listed in MODULES_WHITELIST
MODULES="ehci_hcd uhci_hcd usbcore serio_raw"

# Add modules to this list to leave them in the kernel over suspend/resume
MODULES_WHITELIST=""

# Should we save and restore state using the VESA BIOS Extensions?
SAVE_VBE_STATE=false

# The file that we use to save the vbestate
VBESTATE=/var/lib/acpi-support/vbestate

# Should we attempt to warm-boot the video hardware on resume?
POST_VIDEO=false

# Save and restore video state?
# SAVE_VIDEO_PCI_STATE=true

# Should we switch the screen off with DPMS on suspend?
USE_DPMS=true

# Use Radeontool to switch the screen off? Seems to be needed on some machines
# RADEON_LIGHT=true

# Uncomment the next line to switch away from X and back again after resume.
# This is needed for some hardware, but should be unnecessary on most.
DOUBLE_CONSOLE_SWITCH=true

# Set the following to "platform" if you want to use ACPI to shut down
# your machine on hibernation
HIBERNATE_MODE=shutdown

# Comment this out to disable screen locking on resume
LOCK_SCREEN=true

# Uncomment this line to have DMA disabled before suspend and reenabled
# afterwards
# DISABLE_DMA=true

# Uncomment this line to attempt to reset the drive on resume. This seems
# to be needed for some Sonys
# RESET_DRIVE=true

# Add services to this list to stop them before suspend and restart them in
# the resume process.
STOP_SERVICES=""

# Restart Infra Red services on resume - off by default as it crashes some
# machines
RESTART_IRDA=false

# Switch to laptop-mode on battery power - off by default as it causes odd
# hangs on some machines
ENABLE_LAPTOP_MODE=true

I just had a reboot instead of a resume this morning. Now the driver in question is tty54?? Which device should I blacklist?

[ 1.331819] Magic number: 0:111:333
[ 1.331906] hash matches device tty54

Reconfirming for 2.6.20 based on Jos' recent testing.

Jos, can you attach the /var/log/kern.log.0 or /var/log/kern.log.1, whichever covers the failed resume? Thanks.

Here is the log.

Even though the serio_raw driver was put in the MODULES list in /etc/default/acpi-support, yesterday I managed to make the machine reboot on resume. In the logs was again the serio_raw driver. After the reboot lsmod showed that the driver was loaded, but nothing was using it. (what is this driver used for anyway?). I completely blacklisted this driver now, in about a week's time I can comment more on this.

Sidenote: you often hear a lot of crap about the nvidia drivers and resume, but here is obviously a free driver in the mainline kernel that is giving me grief. It consistently causes (if the debug procedure is correct) my machine not to resume. Can anyone take a look at this driver, to try to fix it? I looked at the source in the kernel, and it's very small, but I don't know nearly enough about kernel programming and suspend/resume to be able to see what it is doing wrong...

Even though the driver is blacklisted in /etc/modprobe.d, the driver is loaded now. It wasn't loaded immediately after boot. What is loading this thing?

Jos:
The open source X nv driver doesn't actually have any code in the kernel. What you saw was a frame buffer driver for nvidia cards but this is almost never actually used. It would be interesting to know if you still have problems suspending and resuming with the vesa driver. If so I suspect your problems do not lie with X...

Sitsofe:
I don't understand. I'm not using nv, I use the nvidia driver, but that is beside the point. I'm having trouble resuming caused by the serio_raw driver.

Jos:
I guess I was wondering whether the nvidia binary driver might be interfering with serio_raw thus causing your issue. If the same problem happened with the nv Xorg driver then that explanation could be completely ruled out.

Still an issue on gutsy.

The 18 month support period for Edgy Eft 6.10 has reached it's end of life. As a result, we are closing the linux-source-2.6.17 Edgy Eft kernel task. However, please note that this report will remain open against the actively developed kernel. Thank you for your continued support and help as we debug this issue.

Hardy Heron 8.04 was recently released. It would be helpful if you could test the new release and verify if this is still an issue - http://www.ubuntu.com/getubuntu/download . You should be able to test your bug using the LiveCD. Please let us know your results. Thanks.

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

this is still a bug in intrepid using the nv driver it just shows a black screen after resuming from suspend, but if I use the nvidia driver it works fine.
intrepid-laptop:~$ uname -a
Linux intrepid-laptop 2.6.27-2-generic #1 SMP Thu Aug 28 17:20:02 UTC 2008 i686 GNU/Linux

The 18 month support period for Feisty Fawn 7.04 has reached it's end of life - http://www.ubuntu.com/news/ubuntu-7.04-end-of-life . As a result we are closing the linux-source-2.6.20 task.

Shawn, is this still an issue with the final Intrepid release which contains a 2.6.27-7 kernel? Thanks.

yes, I just tested it with Intrepid 2.6.27-7 kernel. It is still a bug.

Shawn, since you may have a different laptop than the one on which this problem was originally reported, can you please follow the procedures in [1] and [2] and attach relevant debugging and diagnostic information? Thanks!

[1] https://wiki.ubuntu.com/DebuggingACPI

[2] https://wiki.ubuntu.com/DebuggingKernelSuspend

ok i tested it on the new jaunty

attached info

Assigned to ubuntu-kernel-acpi as per [1]. Tested against 2.6.28-2; also affects 2.6.27.

(Importance not set as I do not have that access.)

[1] https://wiki.ubuntu.com/KernelTeamBugPolicies#Confirmed%20bugs%20are%20assigned%20to%20teams

There have been no updates or activity on this bug for over a year. Does the behavior still occur under Karmic (or under the Lucid beta)?

If so, please run the command

    apport-collect -p linux 60243

in a terminal window.

If anyone is experiencing a similar problem - but not this exact problem - please attempt first to find a bug report that matches the problem you are experiencing; if you find such a report, please attempt to provide any information by the developers, including possibly running "apport-collect -p linux theBugNumber".

If you do not find such a report the behavior your are experiencing, please open a new report as described in https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies

AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: dirk 1464 F.... pulseaudio
 /dev/snd/pcmC0D0p: dirk 1464 F...m pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xc8000000 irq 47'
   Mixer name : 'Realtek ALC883'
   Components : 'HDA:10ec0883,1025160d,00100002 HDA:14f12bfa,10250094,00090000'
   Controls : 23
   Simple ctrls : 13
DistroRelease: Ubuntu 10.10
HibernationDevice: RESUME=UUID=97317377-331b-4f4f-a7f7-bafd81107c46
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100318)
MachineType: Acer, inc. Aspire 5670
Package: linux (not installed)
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-23-generic root=UUID=2c29f010-4c9a-4788-b082-76dcf79412b9 ro quiet splash
ProcEnviron:
 LANG=en_GB.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.35-23.40-generic 2.6.35.7
Regression: No
RelatedPackageVersions: linux-firmware 1.38
Reproducible: Yes
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
Tags: maverick kernel-power suspend resume needs-upstream-testing
Uname: Linux 2.6.35-23-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 08/09/06
dmi.bios.vendor: Acer
dmi.bios.version: v1.3234
dmi.board.name: Bodensee
dmi.board.vendor: Acer, Inc.
dmi.board.version: Not Applicable
dmi.chassis.type: 1
dmi.chassis.vendor: , Inc.
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnAcer:bvrv1.3234:bd08/09/06:svnAcer,inc.:pnAspire5670:pvrNotApplicable:rvnAcer,Inc.:rnBodensee:rvrNotApplicable:cvn,Inc.:ct1:cvrN/A:
dmi.product.name: Aspire 5670
dmi.product.version: Not Applicable
dmi.sys.vendor: Acer, inc.

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

Vassilis Pandis, thank you for reporting this and helping make Ubuntu better. Gutsy reached EOL on April 18th, 2009.
Please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We were wondering if this is still an issue in a supported release? If so, could you please provide the information following https://wiki.ubuntu.com/DebuggingKernelSuspendHibernateResume ? As well, can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ . However, note you can only test Suspend, not Hibernate, when using a LiveCD. If the issue remains, run the following command in the development release from a Terminal (Applications->Accessories->Terminal) as it will automatically gather and attach updated debug information to this report.

apport-collect -p linux <BUGNUMBER>

Additionally, if you could try to reproduce this with the upstream mainline kernel that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.

Please let us know your results. Thanks in advance.

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]