Unrecoverable crash from sleeping, on HP 6735b with Ubuntu 9.04

[Victor Marin]

Binary package hint: gnome-power-manager

I have had a whole crash when trying to wake up the laptop.

But the real problem it's that it does not work even restarting the laptop, as if I push the start/stop button of the laptop (even if I disconnect the power wire and then connect it again, then push the power button of the laptop), it restarts Ubuntu but, when it is about to get into the initial desktop screen, it freezes, again and once again, all the times I try to start Ubuntu.

All the times, the following messages do appear:
Setting Advanced Power Management level to 0xfe (254)

It tries several times, then the whole thing freezes with a black screen with some fuzzy Ubuntu names and logos.

Simply I can't get into Ubuntu anymore.

[Victor Marin (vms368)]

The 2 fuzzy Ubuntu logos and other lines in the black screen that it appear each time I try to start Ubuntu, it are the same ones that it appeared the first time it crashed when waking up after sleeping.

It seems that the crashed waking-up configuration has been saved as the default session.

Pls help.. because I can't start Ubuntu at all.

The Hardware: HP 6735b, AMD TurionX2 ZM80, 2Gb RAM, 160Gb hard drive.
Software: Ubuntu 9.04 i386.

[Scott Howard (showard314)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems like this may be an x.org error, but more information is required. For starters, the issue that you reported is one that should be reproducible with the live environment of the Desktop CD of the development release - Karmic Koala. It would help us greatly if you could test with it so we can work on getting it fixed in the next release of Ubuntu. You can find out more about the development release at http://www.ubuntu.com/testing/. Thanks again and we appreciate your help.

[Victor Marin (vms368)]

Thanks for your response, as well.

I have downloaded the alpha 2 version of Ubuntu 9.10 and I've burned it into a cd.

It starts the live session Ok. Then, I have arranged for the laptop to go to the bed within 6 minutes (the shortest time possible)... But, it does not want to sleep; It seems the Karmic Koala has insomnia on live session or in my laptop.

Now (jokes apart), when I had this problem with Ubuntu 9.04 I installed Kubuntu 9.04. It works much better than previous versions of the KDE4 environment (KDE4 it's now very stable, almost as much as Gnome).

However, I noticed that there are 4 blocked updates which are: linux-headers-generic - 2.6.28.11.15 (i386), linux-restricted-modules-generic - 2.6.28.11.15 (i386), linux-generic - 2.6.28.11.15 (i386) and linux-image-generic - 2.6.28.11.15 (i386).

Then, I made a:
sudo aptitude update
sudo aptitude full-upgrade
to install such blocked updates... AND, when I restarted the laptop it happened the same thing than it happened with Ubuntu when trying to wake up. The laptop restarted with Kubuntu until the point of the initial screen, then the same fuzzy Kubuntu names and logos appeared in a black screen and... Nothing else, again and again.

I then re-installed Kubuntu and now I just overlook the blocked updates.

So it happened the same thing with the 2 environments, although in different situations.

I don't know if Ubuntu installed all the updates, although I didn't see blocked updates in Ubuntu.

[Scott Howard (showard314)]

Nice detective work. We should use the liveCD for all debugging from now on. Let's try the Ubuntu versions first.
The bug only appears with: linux-headers-generic - 2.6.28.11.15 (i386), linux-restricted-modules-generic - 2.6.28.11.15 (i386), linux-generic - 2.6.28.11.15 (i386) and linux-image-generic - 2.6.28.11.15 (i386), so it may be a kernel bug.

Here are some additional debugging steps (from https://wiki.ubuntu.com/DebuggingGNOMEPowerManager):
1) In one terminal type:
killall gnome-power-manager
gnome-power-manager --verbose --no-daemon
2) In another terminal, type:
gnome-power-cmd.sh suspend
3) report the output here

and the output of:
1) run in a terminal: dbus-monitor --session "type='signal',interface='org.freedesktop.PowerManagement'"
2) wait until your computer tries to sleep
3) post the output from dbus-monitor

And finally:
Could you please attach the resulting log files of:
/usr/share/gnome-power-manager/gnome-power-bugreport &> gpm.log

[Victor Marin (vms368)]

I am writing this by using the Ubuntu 9.10 Alpha 2 liveCD.

Concerning the different steps to follow for debugging:

Step 1) in one terminal: No output.
Step 2) in another terminal: The output is somehow confusing, not because some phrases are in Spanish -my first language- but, because gnome-power-cmd.sh it is not there and it can't be installed:

ubuntu@ubuntu:~$ gnome-power-cmd.sh suspend
The program 'gnome-power-cmd.sh' is currently not installed. You can install it by typing:
sudo apt-get install gnome-power-manager
bash: gnome-power-cmd.sh: command not found
ubuntu@ubuntu:~$ sudo apt-get install gnome-power-manager
Leyendo lista de paquetes... Hecho
Creando árbol de dependencias
Leyendo la información de estado... Hecho
gnome-power-manager ya está en su versión más reciente.
0 actualizados, 0 se instalarán, 0 para eliminar y 0 no actualizados.
ubuntu@ubuntu:~$ sudo apt-get install gnome-power-cmd.sh
Leyendo lista de paquetes... Hecho
Creando árbol de dependencias
Leyendo la información de estado... Hecho
E: No se pudo encontrar el paquete gnome-power-cmd.sh
ubuntu@ubuntu:~$

Regarding the output of dbus-monitor, I waited for some 10 minutes but the computer does not try to sleep. I tried twice.

Otherwise, I attach you the gnome-power-bugreport file (I didn't find the gpm.log).

[Scott Howard (showard314)]

I'm assigning this to the linux package and removing GPM since the bug exists in both KDE and GNOME, and only exists with a specific kernel version.

[Victor Marin (vms368)]

Ok, thanks for the message.

[Victor Marin (vms368)]

Just to comment you that I went back to Ubuntu 9.04.

Again, everything was going just fine until a security update has arrived, with new kernel 2.6.28-14, linux-restricted-modules-generic - 2.6.28.11.14, etc. And once restarting, the same quoted black screen came up.

There is the same problem with this version of kernel, as well.

Fortunately, if at Grub I choose to start with the "old" kernel 2.6.28-13 everything goes Ok (I am writing this from such version of the kernel).

Rgds,
Victor

[Jeremy Foshee (jeremyfoshee)]

Hi 836v,

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 390827

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.]

[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 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.]