8.10 Suspend & Hibernate Problems Latitude D630

[adempewolff]

Hello, I just recently upgraded to 8.10, and have gotten most the bugs worked out but cannot for the life of me get it to suspend (to RAM) or hibernate (to disk) correctly, which is a very important OS feature to me.

I've looked around and found that many people have problems with this and that it often has to do with proprietary drivers, but after troubleshooting and researching for a while I realized that the bugs seemed to vary so much between different hardware and such that I should just create my own topic.

The problems:

When I suspend to RAM and then try to resume, I hear it access the hdd, the power light is on and steady but the screen remains completely black (backlight is off) and I must force the computer to power down and restart.

Hibernate also doesn't work but it is not as important to me, and I haven't paid attention to the actual symptoms yet.

What I have tried doing:

My laptop has an Nvidia video card (for which I enabled the NVIDIA accelerated graphics graphics driver version 180) which I have read could cause problems, so I added the following section to my /etc/x11/xorg.conf
Section "Device"
Identifier "nVidia Corporation G80 [Quadro NVS 135M]"
BusID "PCI:1:0:0"
Driver "nvidia"
Option "NoLogo" "True"
Option "NvAGP" "1"
EndSection

I also blacklisted "intel_agp"

Neither of these worked.

I then tried running this test https://wiki.ubuntu.com/KernelTeam/SuspendResumeTesting

It displayed the problem on the first test, but as far as I can tell it did not automatically generate a bug report.

What I think this might mean is that the system is resuming just the videocard isn't or something.

If anyone has suggestions or can tell me what I would need to do to shed more light on the problem that would be very much appreciated

[austin.lund]

I have exactly the same computer with the same problem. But I don't run the nvidia drivers, I use the xorg-video-nv driver.

Also, I've had the problem with 9.04 and now with 9.10.

Trying pm-suspend in single user mode (without X of course) give the same results. I've tried numerous quirk settings, but they all give the same.

I'm really at a loss as to how to debug this one.

[austin.lund]

Just out of interest, what firmware are you running.

Mine is:

$ hal-device | grep system.firmware.version
system.firmware.version = 'A13' (string)

I did have the motherboard changed. So perhaps that's when things stopped working. HAL seems to treat systems with <A12 differently to systems with >= A12

[dro0g]

I'm on a D630 with an Intel card rather than Nvidia and I'm no longer able to use suspend/resume either. The laptop goes to sleep OK but on resume sometimes it locks up right away, sometimes I get the caps and scroll lock blinking kernel error thing and sometimes it works OK for a minute and then hangs with a kernel error.

[adempewolff]

My problems were fixed when I upgraded to 9.04, way back when. I then upgraded my RAM and suspend to RAM stopped working, but a clean install of 9.10 got that working again. I'm using A16--the newest firmware. Honestly there are so many things that can cause suspend to RAM not to work, I doubt my problem had the same cause as yours. If it stopped working after a mobo switch though, my best advice would be to try a clean install on a new partition and see if works there. For some reason, the suspend program does not like hardware changes. Good luck!

[austin.lund]

The laptop goes to sleep OK but on resume sometimes it locks up right away, sometimes I get the caps and scroll lock blinking kernel error thing and sometimes it works OK for a minute and then hangs with a kernel error.

That sounds more like a kernel issue. I assume you still have your screen after resume?

I'm using A16--the newest firmware.

I could only find A15 and upgraded to it. Where is A16 (not that I expect it to fix the problem).

What would be really good is info on how to debug this like dumping info about the current screen state, etc. As I can do this in single user mode, the problem seems to have little to do with the X drivers. Also, as I'm able to interact with the shell, I'm probably in a better position than most to extra useful info.

[adempewolff]

It is on the Dell Support Site, just enter your service tag or select the D630 and under drivers and downloads you will find the windows bios flash utility. If I remember correctly they haven't put it up for the linux flash yet, so, if you don't dual boot, you might have to wait. I can forward you the conversation I had with tech support if you want about flashing the bios using ubuntu.

This is the master thread for debugging suspend resume threads, and has been updated extensively since I had my problems: https://wiki.ubuntu.com/DebuggingKernelSuspendHibernateResume

Debugging Resume issues is really hard if the crash is early in the resume process because there are very few non-volitable memory resources available--this makes a "dump" to the hdd impossible. Back when I was debugging my issues the standard procedure for debugging kernel problems on resume was to have it dump problems to the rtc (real time clock) chip on the systemboard. here is the wiki page on this process, I'm not sure how up to date it is: https://wiki.ubuntu.com/DebuggingKernelSuspend#%22resume-trace%22%20debugging%20procedure%20for%20finding%2 0buggy%20drivers

Remember to reset your RTC after doing this or you will get some really funky things going on...

Good Luck!

[austin.lund]

if you don't dual boot, you might have to wait.

I don't have a copy of windows which I can use for that. I've always updated using the linux flash loader.


Debugging Resume issues is really hard if the crash is early in the resume process ...

I don't have a crash (panic) and I can interact with the system (luckily) but cannot see anything. dro0g should certainly have a look at that though.

[adempewolff]

I don't have a copy of windows which I can use for that. I've always updated using the linux flash loader.

hmm... http://linux.dell.com/repo/firmware/bios-hdrs/ does seem to still be missing the A16 firmware... maybe try emailing them and complaining. I've heard rumours that wine will run the dell bios flashes but personally I would would let a truck run over my laptop before trusting wine to flash a bios. I don't really know how important A16 is, so, it might not be worth the trouble trying to figure out how to upgrade.



I don't have a crash (panic) and I can interact with the system (luckily) but cannot see anything. dro0g should certainly have a look at that though.

Hmm, in that case I'd say browse through the master thread on debugging resume problems and create a bug report.

You say you are able to interact with it, do you mean it is just in single user mode or that it just didn't restart X or what? Have you tried pressing ctrl-alt-F5 (or something like that) to switch to any active X sessions?

[austin.lund]

Hmm, in that case I'd say browse through the master thread on debugging resume problems and create a bug report.


I filed a bug yesterday, but I might have put it in the wrong package.

https://bugs.launchpad.net/ubuntu/+source/hal-info/+bug/487391


You say you are able to interact with it, do you mean it is just in single user mode or that it just didn't restart X or what? Have you tried pressing ctrl-alt-F5 (or something like that) to switch to any active X sessions?

Rebooted into single user mode, so minimal apps running and it does not work. I'm planning on getting that working first before playing with X. I've tried many different quirk settings for pm-suspend. I've tried switching VCs hitting enter lots of times and fiddling with vbetool after resuming. Nothing seems to work, but then again, I'm not entirely sure what is wrong.

[adempewolff]

ah, I see so it is just your monitor that is not turning on. you could try fooling around with the SysRq magic key to dump memory, processes, etc. to your log files and see whats wrong. But if the kernel isn't hanging or anything-the monitor just isn't turning on-you might already have everything you need in the log files.

Anyway, if you are really serious about debugging it, the best way to make sure your bug report contains all the neccesary information is to just methodically follow the steps at https://wiki.ubuntu.com/DebuggingKernelSuspendHibernateResume.

I also would continue to recommend making a small new partition--if you have the space--and trying a fresh installation of 9.04 or 9.10 onto it(I'd recommend 9.10, I think it has better support for the intel graphics cards). If it works, then back up all your data and reinstall the main os.

[austin.lund]

you might already have everything you need in the log files.

The log files shed no light on it. I think I might need more debugging info. /var/log/pm-suspend.log shows total success. So does /var/log/syslog.


Anyway, if you are really serious about debugging it, the best way to make sure your bug report contains all the neccesary information is to just methodically follow the steps at https://wiki.ubuntu.com/DebuggingKernelSuspendHibernateResume.

The only thing I saw on that page that relates to this is under "Debugging Suspend". Hibernate seems to be fine.

... trying a fresh installation of 9.04 or 9.10 onto it(I'd recommend 9.10, I think it has better support for the intel graphics cards).

Oh. I may not have said it above. This is 9.10. I've tested it with the standard 2.6.31 kernel and a RC 2.6.32 kernel (packaged as 2.6.32-999.200911201641).

What I might do however is a fresh install of 8.04 or the like on a small partition as this version did work for me, just to make sure it still does.

[austin.lund]

Interestingly, if I suspend and resume with an external monitor, it all works swimmingly (that is it with the console displaying onto an external monitor after suspending and then resuming the console is displayed back onto that external monitor).

[adempewolff]

Is that monitor plugged in through a cable, or through a docking station? Because docking stations often have their own video cards.

[austin.lund]

Is that monitor plugged in through a cable, or through a docking station? Because docking stations often have their own video cards.

Docking station.

[adempewolff]

I'd check to see if that docking station has its own video card then. If it does, you would know for sure that it was your video card causing the problem. What driver are you using for your laptop's video card by the way?

[austin.lund]

I'd check to see if that docking station has its own video card then. If it does, you would know for sure that it was your video card causing the problem. What driver are you using for your laptop's video card by the way?

For single user mode, no special driver (VGA legacy as far as I can see). When using X I'm using the xorg-video-nv driver.

I have a builtin video card:
01:00.0 VGA compatible controller: nVidia Corporation Quadro NVS 135M (rev a1)

I'm pretty sure that the docking station does have a video card, but I cannot find that out for sure. The only reason I have that impression is that the bios setting is such that if there is a video card in the docked station then it should use that by default, and on boot that is exactly what happens. But dmidecode doesn't show anything more and lspci doesn't show anything more either. I'm not sure how to know exactly.

[squirrelpie]

Almost identical problem on Vostro 1500 with Suspend on cover close suspending but not coming out of suspension on re-open- nothing on the screen although disk had spun up and had to reboot. Unit has Nvidia 128 card that I had never installed drivers for because unit displayed adequately with Ubuntu drivers. Downloaded and installed the rec Nvidia driver (185) in the Hardware Driver list and unit now displays properly from Suspend when cover opens, only screen was dimmed and had to brighten with Fn keys. Don't use hibernate so don't know if that works

[adempewolff]

We have the same graphics card. I had thought earlier that you mentioned that you had the integrated intel chipset. Make sure you are using the nvidia-glx-185 binary driver (unsupported), which adds a lot of functionality to the xorg-video-nv driver.

[austin.lund]

We have the same graphics card. I had thought earlier that you mentioned that you had the integrated intel chipset. Make sure you are using the nvidia-glx-185 binary driver (unsupported), which adds a lot of functionality to the xorg-video-nv driver.

Already have:

lund@lund-laptop:~$ dpkg -l | grep nvidia-glx
ii nvidia-glx-185 185.18.36-0ubuntu9 NVIDIA binary Xorg driver
lund@lund-laptop:~$ lsmod | grep nvidia
nvidia 10316904 0

The module is loaded in single user mode as well. (10MB binary blob kernel mode code! Always a bit suspect).