Hibernation problems with compaq presario

Bug #35410 reported by Steve Frécinaux
24
This bug affects 1 person
Affects Status Importance Assigned to Milestone
pm-utils (Ubuntu)
Invalid
Medium
Unassigned
Declined for Intrepid by Steve Langasek
Declined for Jaunty by Steve Langasek

Bug Description

There are a few issues with the hibernation, that happen with my Compaq Presario serie 900 (the precise model is 915EA)

Here are the problems:
1/ Hibernate works only once. It means that once you have returned from hibernation, you can't hibernate anymore.

2/ Sound is not restored, everything is muted.

3/ More important, the kernel modules relative to network are not loaded when returning for hibernation. Those modules are 8139too, pcmcia and ndiswrapper. Network interfaces are also not brang up, including lo.

Revision history for this message
Steve Frécinaux (nud) wrote :

Forgot to say that sleep does not work, you can't return from it and you have to remove the battery and the plug to get back your system running. Otherwise when pushing the power button it just shows up a blank screen.

Revision history for this message
Paul Sladen (sladen) wrote :

Hello Steve, thanks for your report - is this with 5.10 or Dapper?

The hibernate-only-once is probably caused by a crash coming out of hibernate. Could you check:

  /var/log/syslog

and see if you can see it? This may highlight the other problems.

Changed in acpi-support:
status: Unconfirmed → Needs Info
Revision history for this message
Steve Frécinaux (nud) wrote :

Sorry, it is on dapper. I'll check asap, and give you feedback this evening.

Revision history for this message
Steve Frécinaux (nud) wrote : /var/log/syslog

Here is the syslog, containing the whole hibernation process, from clicking on "hibernate" till when I plugged the wi-fi pcmcia card in.

Hope that'll help.

(btw when returning from hibernation the display is not the good one: I have to push on ctrl+alt+f7 to get my session back)

Revision history for this message
Tormod Volden (tormodvolden) wrote : syslog after resuming from hibernation

Confirming this on a Presario 701EA (savage TwisterK video card, 256 MB RAM, RTL-8139C nic).
Up to date dapper (kernel 2.6.15-23-k7). After resume, "scheduling while atomic: hibernate.sh" messages appear in syslog.

I also noticed (but this might be caused by the oops):
- sound was muted
- network was down. I had to remove 8139cp module that for some reason was loaded and load the 8139too module, then ifdown and ifup.
- woke up to screen with a brown and black vertical stripes. Had to switch ctrl-alt-f7 to get X and the screenlock. The virtual text consoles are broken (a multicoloured woven carpet-like image).

Revision history for this message
Tormod Volden (tormodvolden) wrote : lspci -vv output

Is more info needed?

Revision history for this message
Tormod Volden (tormodvolden) wrote :

I now tried using the 386 kernel, and after 4 retries (due to bug #36944) it resumed fine, with sound, network, consoles working.

> 1/ Hibernate works only once

BTW, I have kind of the opposite problem. Bug #36944 will always kick in on the first hibernation/resume after a fresh boot. Only after second (or third/etc) cancelled-resume-boot, it will resume successfully.

Revision history for this message
Tormod Volden (tormodvolden) wrote :

Steve, which kernel are you using (uname -r)?

Changed in acpi-support:
status: Needs Info → Confirmed
Revision history for this message
Steve Frécinaux (nud) wrote :

Sorry I completely forgot this topic.
My kernel version is 2.6.15-25-k7 and I still have the issue.

Revision history for this message
Tormod Volden (tormodvolden) wrote :

My Presario 701EA now works fine, with Ubuntu 6.06 and dapper-updates, as long as I use "Blank screen" as screen saver. But I am not using pcmcia cards and not ndiswrapper and proprietary drivers.

Revision history for this message
Tormod Volden (tormodvolden) wrote :

Now testing Edgy (~Beta):
Coming back from hibernation, the screen is funny. First the X server didn't repaint the screen (only under the mouse pointer). I then switched to the virtual consoles, they are all borked with lines and colours (I can see the ubuntu logo from usplash in between).
After switching back to vt-7, the X server seems to be fine. But vt1-6 are lost. Nothing suspicious in dmesg, kern.log or Xorg.0.log.

Revision history for this message
Tormod Volden (tormodvolden) wrote :

I tried to sleep, and after wake-up, the text consoles were gray. I could refresh them by pushing enter and letting the login-prompting write out the white-on-black letters again.

After that I got so courageous I tried glxinfo, which worked fine. Then tried glxgears and it hung hard. This looks like bug #43007 and bug #37218. Actually glxgears gives just a black window even after a fresh reboot, gonna file another bug for that.

Revision history for this message
Tormod Volden (tormodvolden) wrote :

The glxgears black window was fixed in bug #46314. The DRI hang after hibernation is #43007.

I have now disabled DRI and this problem is still the same: the consoles are borked after hibernation.

Revision history for this message
Tormod Volden (tormodvolden) wrote :

The borked consoles were a result of bug #38500 (together with bug #40503) in my case. I'll follow up on my problems there, and leave this bug for Steve's problems.

Revision history for this message
Sergio Zanchetta (primes2h) wrote :

I have a Compaq presario 2136EA laptop.

Same problem for me with network when I resume from hibernation.

In Gutsy, eth0 interface in network manager is completely missing.

I have artefacts in window border (windows shadows) using compiz too but I think it's better I open another bug report for this.

Revision history for this message
Steve Langasek (vorlon) wrote :

Hello,

Is anyone still seeing this specific problem in intrepid or jaunty?

Martin, you nominated this bug for intrepid and jaunty, but there are no comments from you even indicating that you are experiencing this bug; the last comment here is over a year old, and without seeing some details I would have to assume that any bugs you're seeing in the later versions of Ubuntu are different than this one.

Revision history for this message
Marco Diaz (zethabyte) wrote :

I have a Compaq Presario CQ50 130LA and I have this problem ...

after to hibernate I don't have network.

Revision history for this message
papukaija (papukaija) wrote :

I'm using Intrepid and I have similar problems with my compaq presario 5011EA (with memery upgraded to 320MB). After hibernation the network doesn't work; I need to restart the system to get it working. I haven't tested, but normally reloading the rt2500 kernel module (included since Intrepid in the kernel) should start networking.

papukaija (papukaija)
affects: acpi-support (Ubuntu) → pm-utils (Ubuntu)
Revision history for this message
papukaija (papukaija) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue for you. Can you try with the latest Ubuntu release? Thanks in advance.

Changed in pm-utils (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
papukaija (papukaija) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in pm-utils (Ubuntu):
status: Incomplete → Invalid
Revision history for this message
papukaija (papukaija) wrote :

If you reopen this bug, then please execute the following command, as it will automatically gather debugging information, in a terminal (Applications->Accessories->Terminal):

apport-collect 35410

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.