[Vostro 1000] Resume fails after suspend/hibernate

[xeno_phile]

Description: Ubuntu 9.10
Release: 9.10

Laptop - Dell Vostro 1000.
Laptop refuses to come out of suspend/hibernate.
I have to "crash" my machine and then reboot!!
To reproduce the bug, just boot up, suspend/hibernate and try to resume.
This bug was not present in Ubuntu 9.04.

This bug (i certainly believe it to be a bug) is affecting a wide range of laptop makes and models.
This is a thread i started yesterday.
http://ubuntuforums.org/showthread.php?t=1307618

I have attached "lspci -vvnn"
Can't attach "dmesg", it's too big for the terminal window!

[ZAP (michaelzap)]

Same here with a Lenovo Y530 with Intel sound.

[xeno_phile (trevor-jon1)]

zap..have you tried the Bios or acpi=oldboot solution yet (see the Ubuntu thread), if you have, what result did you get?
xeno

[xeno_phile (trevor-jon1)]

My thread has now received a post from a desktop user that is experiencing the same problem that plagues us laptop users.
This issue with suspend/hibernate/resume in 9.10 seems to be quite widespread.
This problem will certainly put users off from adopting 9.10 permanently.
A quick resolution of this issue would be much appreciated by many many loyal users.

xeno_phile.

[gsmayya (gsmayya)]

I use suspend/resume too extensively.
I had been using Karmic from the Alpha 2. I did not had any suspend/resume problems.

But after the kernel upgrade (as mentioned in the bug 449646, kernel version 2.6.31-12), Ubuntu would never recover from a suspend. It would show power light on, but no other sign of life.

I see some rc version of 2.6.32 being talking about the suspend/resume problems (http://lwn.net/Articles/360238/).

Am not sure why no importance or status is still being updated?

thx
~gururaj

[Derek (derek-a-mumaw)]

unfortunately, I have the same issue. I have a Hp Tc1100. As much as I would like to stay with 9.10, I need to have Suspend/Resume working. I'll probably downgrade until the issue is fixed.

[Hendrik (joker-x)]

I can confirm (unfortunately) that this is also an issue with my HP EliteBook 6930p: Resume from suspend doesn't work after upgrading to Karmic, but did work under Jaunty.

[Mahngiel (mahngiel)]

Have replaced the Ubuntu kernel with TuxOnIce's kernel, hibernates just fine!

sudo add-apt-repository ppa:tuxonice/ppa

sudo aptitude update

sudo aptitude safe-upgrade

[Mahngiel (mahngiel)]

update:

negatory on that.

[Hendrik (joker-x)]

I wanted to add that suspend-to-disk works for me (including resuming), only resuming from suspend-to-RAM fails.
(A minor annoyance with suspend-to-disk is that I get an ugly blinking green line on my screen, instead of whatever splash screen is supposed to appear during the suspending process.)

[xeno_phile (trevor-jon1)]

Update.......
I can now resume from suspend properly, below is the list of actions that i had to take to achieve this.
remove xserver-xorg-video-radeon
remove xserver-xorg-video-ati
Then visited these two links and chose the correct files for my architecture.
https://launchpad.net/ubuntu/jaunty/...g-video-radeon
https://launchpad.net/ubuntu/jaunty/...xorg-video-ati
Installed the new "Jaunty" files, and my system is running as it should.
One can only assume the "Karmic" files are broken somewhere, until the "Karmic" files are repaired i have to prevent the "Jaunty" files from being updated.
My thanks go to
 "lamaistres" http://ubuntuforums.org/member.php?u=61667
 for providing the solution.

xeno_phile

[gsmayya (gsmayya)]

Hi,

Am not sure how to fix for the suspend for video-intel. Jaunty's intel drivers were also broken, so am not sure about risking to that. :)

Just a happy news for me is hibernate is working fine now. I tried it three or four times. Is working. Am not sure of any particular updates which caused this to work fine.

Suspend seems to be broken in upstream itself. Atleast Fedora 12 also failed to resume from suspend.

thx
~gururaj

[xeno_phile (trevor-jon1)]

Hi gsmayya,
To be prefectly honest i dont think the problem lies with the drivers, even though down grading seems to have worked in my case.
The reason i say that is because Fedora 12 works perfectly on my machine. Suspend/Hibernate and Resume work "out of the box".
Surely the drivers used by Ubuntu and Fedora would be the same?

I do know that kernel mode switching is supposed to solve alot of the suspend/resume problems, but i'm not sure the Intel drivers are compatible yet....alot of work has been done on the drivers for the ATI chip set.

be lucky
xeno_phile

[PeggySue (peter-peterwpaintings)]

This bug is still present in Lucid 10.04 alpha 1, kernel 2.6.32-7 on Dell Vostro 1000, AMD 64 X2.
What information is required by the developers to be able to take some action?

[xeno_phile (trevor-jon1)]

PeggySue...."What information is required by the developers to be able to take some action?".......That is the $64,000 question!!
As users, all we can do is follow the bug reporting guidelines, and hope someone from the triage team tries to debug the the problem.
I have had several issues with Karmic, and have now abandoned Ubuntu altogether.
I am running Fedora12. Works out of the box for me.

[PeggySue (peter-peterwpaintings)]

Xeno,

You must be psychic! At this very moment I am installing Fedora 12 on my lap top and just switched on the desktop while I'm waiting.

I have had no end of problems with grub 2 on my dual disk, multi partition system so had reverted to grub 1 until the bugs were fixed.

Ubuntu's last 9.10 updates contained a new kernel which I installed. I chose to the installers grub config file thinking it would just update the grub 2 files; a bad mistake. Now it can't see Grub1 so I think it wrote over the MBR!!! I should have backed it up, as I have on the desktop, but I didn't. The MBR already pointed to my 9.10 partition so I thought the stage 2 files would know the kernel location and it wouldn't need to update the MBR for the new kernel.

Ubuntu spends too much time on innovation and not enough on getting the foundations to work. 10.04 is billed as being the low innovation version but there is not much sign of getting the fundamentals right yet. Still 4 months to go!

[Rafael Gattringer (rafael.gattringer)]

Although this is getting really off topic here, this bug is an example that Ubuntu has to be more conservative in critical areas like graphic and network drivers, booting, suspend/resume and other basic features. An idea might be a "stable" basic layer and on top an optional innovation layer? A state of art but "broken" innovation will not pay off. After all stability is THE core strength of linux, not necessarily innovation. I will not change my distro, but rather downgrade or stay at 9.04.

[xeno_phile (trevor-jon1)]

PiggySue.....I am psychic...how did you guess!!
I hope Fedora 12 works for you as well as it works for me.
Rafeal.....what you gonna do when support ends for 9.04.

xeno

[Mahngiel (mahngiel)]

Well, here's a bit of good news:

I'm using Ubuntu Studio's kernel 2.6.31.9-rt, and I have achieved constant hibernation success. The kernel information can be found [url="https://help.ubuntu.com/community/What%20Is%20Ubuntu%20Studio#Ubuntu%20Studio%20vs.%20Ubuntu"]here[/url].

My system is by no stretch of the imagination up-to date. It's a 5 year old HP Pavillion laptop, though the processor is 3ghz, the video card has only 56mb of memory, and my ram is 512.

BTW, You can change kernels and still use your own version of whatever the hell you're using.

[Tom Mercelis (tom-mercelis)]

I can hibernate fine, but suspend makes the screen and keyboard become "mostly" unresponsive.
To be more precise: I can shutdown/reboot the notebook by pressing alt-printscreen-b, but shift nor numlock lights can be toggled. I can login with SSH, but Xorg wont react. Running some x commands just hang: x11vnc & xset for instance.

i'm using the fglrx driver, i'll test whether using the open source driver changes anything, but meanwhile: anyone any other hints?

[Tom Mercelis (tom-mercelis)]

I tested the radeonhd driver (the 1.2.5-1 version in ubuntu 9.10). This doesn't make suspend work either. The system becomes unresponsive after wake-up from suspend to ram.

[Jason Barnett (tamagotono-deactivatedaccount)]

I have had a similar problem on my sony VGN-FW139E using the fglrx driver. I have just found that I can successfully suspend and resume if I unload the "video" module prior to suspending. After resuming, everything seems to work fine except being able to adjust the screen brightness, as this is a function of the "video" module. Simply reloading the module restores this ability.

BEFORE SUSPEND: sudo rmmod video
AFTER RESUME: sudo modprobe -i video

[Tom Mercelis (tom-mercelis)]

In the process of testing fglrx versions and radeonhd, I found that the good old "radeon" does suspend to ram and wakes up correctly afterwards.

[Tom Mercelis (tom-mercelis)]

I can suspend to ram and wake up again without problem (and without removing the video module).
My configuration: Ubuntu Karmic, kernel 2.6.31-17-generic.
What did I do:
first I purged the old version of the fglrx driver and installed the recent version (9.12, released December 17th 2009) of fglrx. I have to stress that I purged (not just uninstalled) the old version and removed the /etc/ati directory afterwards: first I just upgraded from 9.x to 9.12, and after reboot the screen stayed black (even blacklight was out) as soon as X started (I could switch back to text console and there everything worked fine, but in the X vt screen went black and backlight off).
I also reset the xorg.conf file by making a new one with "X -configure", copied the resulting file to /etc/X11/xorg.conf
Then I installed the new drivers ("sh ati-driver-installer-9-12-x86.x86_64.run --buildandinstallpkg Ubuntu/karmic").
So basicly, for me this problem is solved.

[Jason Barnett (tamagotono-deactivatedaccount)]

If removing the video module works for anyone else, here is the "proper" method of automating it.

add the following line to /etc/pm/config.d/unload_modules (you may have to create it)

SUSPEND_MODULES="video"

Everything should work after that.

[Jeremy Foshee (jeremyfoshee)]

Hi xeno_phile,

This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 468850

Also, if you could test the latest upstream kernel available 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. Please let us know your results.

Thanks in advance.

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

[Ingo Reimann (ubuntu-i-reimann)]

Hi there,

i just upgraded from karmic to lucid and the problem arose, which i did not have before:

Suspend-to-ram suspends the (desktop)computer - ATI 4850/ RV770 with fglrx 8.72.11. After wakeup, the system comes up, the display is initialised, but i only see a cursor and some garbage. The system seems to be responsible as SysRq works but i also have no network. After reboot firefox complains about offline mode.

I would like to include the "rmmod video" solution, but there is no video module:

root@hal:~# lsmod | grep vid
hwmon_vid 3130 1 it87
videodev 40486 1 cpia
v4l1_compat 15495 1 videodev
v4l2_compat_ioctl32 12020 1 videodev

One thing to mention - Xorg.0.log complains about a missing acpid.socket, with in fact is there. Maybe we have an upstart problem?
Open ACPI failed (/var/run/acpid.socket) (No such file or directory)

root@hal:~# ls -la /var/run/acpid.socket
srw-rw-rw- 1 root root 0 2010-05-02 08:20 /var/run/acpid.socket

Just my 5 cents.

best wishes,

Ingo

[PeggySue (peter-peterwpaintings)]

The bug has been fixed for me with the full 10.04 release.
My Dell Vostro 1000 with AMD64 and Dell wireless now suspends from the menu or a lid closure are resumes correctly even if left overnight.
This is great. It makes a big difference. Thanks.

[Hendrik (joker-x)]

Contrary to PeggySue's experience, I still have the problem after upgrading to Lucid. (As stated above, waking up from suspend-to-disk works, but not from suspend-to-RAM. I'm using an HP EliteBook 6930p.)

[Jeremy Foshee (jeremyfoshee)]

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 development release http://cdimage.ubuntu.com/daily-live/current/ . 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.]