HP DV5 - Can't suspend, get a Lock Screen instad of suspend

Bug #501323 reported by Zeilloc
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Won't Fix
Low
Unassigned

Bug Description

Binary package hint: gnome-power-manager

Hello,
I have a laptop hp dv5 1010ef.
I am a bit confused because I don't manage to suspend it (RAM).

When I click on "Suspend" ("Mise en veille" cause I am french), I get my screen locked and the computer doesn't seem to be "standby" at all (the leds are still colored).

And yet, I have done this :
- open terminal
- type: sudo gconf-editor
- navigate to /apps/gnome-power-manager/locks
- disable lock_on_hibernate
- disable lock_on_suspend

What this problem could be (I don't know, gdm ? acpi ? pm-utils ?) ?
Don't hesitate to ask me to give you the results of the command line you want.

$ apt-cache policy gnome-power-manager
gnome-power-manager:
  Installé : 2.28.1-0ubuntu1
  Candidat : 2.28.1-0ubuntu1
 Table de version :
 *** 2.28.1-0ubuntu1 0
        500 http://fr.archive.ubuntu.com karmic/main Packages
        100 /var/lib/dpkg/status

Revision history for this message
Zeilloc (zeilloc) wrote :
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thanks for taking the time to report this bug and helping to make Ubuntu better. Could you please open a terminal and execute: apport-collect 501323 ? It will attach the necessary information to this report. Also you can submit more information for it by looking to https://wiki.ubuntu.com/DebuggingGNOMEPowerManager , Thanks in advance.

Changed in gnome-power-manager (Ubuntu):
status: New → Incomplete
importance: Undecided → Low
Revision history for this message
Zeilloc (zeilloc) wrote :

I have done :
------------------------------------------------------------------------------------------------------------------
$ apport-collect 501323
Logging into Launchpad... You have to allow "Change anything" privileges.
Downloading bug information...
The authorization page:
   (https://edge.launchpad.net/+authorize-token?oauth_token=P5xH0pQczmvLsc1BgmZv)
should be opening in your browser. After you have authorized
this program to access Launchpad on your behalf you should come
back here and press <Enter> to finish the authentication process.

Bug title: HP DV5 - Can't suspend, get a Lock Screen instad of suspend
Collecting apport information for source package gnome-power-manager...
Uploading additional information to Launchpad bug...
   short text data...
Error connecting to Launchpad: HTTP Error 401: Unauthorized
You have to allow "Change anything" privileges.
You can reset the credentials by removing the file "~/.cache/apport/launchpad.credentials."
------------------------------------------------------------------------------------------------------------------
I am not sure it's OK.

What do you want me to do with this page https://wiki.ubuntu.com/DebuggingGNOMEPowerManager ?
For which command line do you want the result ?

Revision history for this message
Paul Dufresne (paulduf) wrote :

As I understand the results you got from 'apport-collect 501323' , a new window or tab should have opened in your browser executing this, or you could copy the link to the authorization page; but you did not seems to have given the permission to apport-collect to run on this web page.

I suggest you retry 'apport-collect 501323' but take time to authorize apport in the web page, before continuing.

Also, https://wiki.ubuntu.com/DebuggingGNOMEPowerManager seems to suggest that you try:
dbus-send --system --print-reply --dest="org.freedesktop.Hal" /org/freedesktop/Hal/devices/computer org.freedesktop.Hal.Device.SystemPowerManagement.Suspend int32:0

at the $ prompt of Accessoires/Terminal... If it does the same problem that way, that would suggest that this is a kernel bug rather than a gnome-power-manager bug. Maybe I will mark this bug to the kernel too, so that apport-collect also collect information for a kernel bug if that becomes one.

Revision history for this message
Zeilloc (zeilloc) wrote : apport-collect data

Architecture: i386
DistroRelease: Ubuntu 9.10
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
NonfreeKernelModules: nvidia
Package: gnome-power-manager 2.28.1-0ubuntu1
PackageArchitecture: i386
ProcEnviron:
 PATH=(custom, no user)
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-17.54-generic
Uname: Linux 2.6.31-17-generic i686
UserGroups:

Revision history for this message
Zeilloc (zeilloc) wrote : Dependencies.txt
Revision history for this message
Zeilloc (zeilloc) wrote : DevkitPower.txt
Revision history for this message
Zeilloc (zeilloc) wrote : GConfNonDefault.txt
Revision history for this message
Zeilloc (zeilloc) wrote : XsessionErrors.txt
Revision history for this message
Zeilloc (zeilloc) wrote : gnome-power-bugreport.txt
Changed in gnome-power-manager (Ubuntu):
status: Incomplete → New
tags: added: apport-collected
Revision history for this message
Zeilloc (zeilloc) wrote :

OK apport-collect worked this time. The problem was that I did not give the "Change anything" (but something less) rights to the application.

Concerning...
----------------------------------------------------------------------
$ dbus-send --system --print-reply --dest="org.freedesktop.Hal" /org/freedesktop/Hal/devices/computer org.freedesktop.Hal.Device.SystemPowerManagement.Suspend int32:0
method return sender=:1.1 -> dest=:1.123 reply_serial=2
   int32 0
----------------------------------------------------------------------
I still have the save issue.

Another idea or command-line to execute ?

Revision history for this message
Paul Dufresne (paulduf) wrote :

It could be link to relatively old bug #301353, which suggest (from http://bugzilla.kernel.org/show_bug.cgi?id=12113#c13) that bios update from HP (F21) solves the problem.

Can you determinate the BIOS version you have?
maybe 'dmidecode' command can help you.

A message on HP forum from May 29, 2009: HP: Please fix the dv5 BIOS!
http://h30434.www3.hp.com/t5/Hardware/HP-Please-fix-the-dv5-BIOS/m-p/71945

From http://h10025.www1.hp.com/ewfrf/wc/softwareCategory?sw_lang=17&lc=en&dlc=en&cc=us&lang=en&product=3755994
There seems to be a firmware update for some Hard Disks of this model, which is different than a BIOS update, but maybe usefull. Ah... maybe not, that seems to fix something else:
- Fixes an issue where following error message is displayed after powering ON the laptop: 1720 - SMART Hard Drive detects imminent failure (Failing attr: 0¤).

Changed in gnome-power-manager (Ubuntu):
status: New → Incomplete
Paul Dufresne (paulduf)
affects: gnome-power-manager (Ubuntu) → linux (Ubuntu)
Revision history for this message
Paul Dufresne (paulduf) wrote :

BTW, it could be a bit like on my computer... when I hibernate, computer did seems to shut down, but it looks like an event wakes it up less than 1 second after, and then it does resume, and show the lock screen which is normal after a successfull resume as far as I know.

Since I have changed the package of this bug to 'linux' kernel, you will need to rerun 'apport-collect 501323' AFTER logging in after a 'failed' suspend-to-disk would give better log files.

Note that a web page describing some test you can do is at:
https://wiki.ubuntu.com/DebuggingKernelSuspend
which suggest also: http://lxr.linux.no/#linux+v2.6.32/Documentation/power/basic-pm-debugging.txt

Revision history for this message
Zeilloc (zeilloc) wrote :

Ok. Here are some information about my BIOS.
---------------------------------------------------------
sudo dmidecode | grep BIOS
SMBIOS 2.4 present.
BIOS Information
  BIOS is upgradeable
  BIOS shadowing is allowed
  BIOS ROM is socketed
 BIOS Revision: 15.20
---------------------------------------------------------
It's perhaps a stupid idea, but the fact that I can suspend to RAM while I'm in Windows 7 don't show us that my BIOS allows to suspend ?

I'm going to make a "apport-collect" just after this message, after I-ve tied to suspend my computer (and got a lock screen).

Do you want me to update my BIOS ?
http://h10025.www1.hp.com/ewfrf/wc/softwareDownloadIndex?softwareitem=ob-75233-1&lc=fr&dlc=en&cc=en&lang=en&os=4062&product=3755994

Revision history for this message
Zeilloc (zeilloc) wrote : apport-collect data

Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
   Subdevices: 2/2
   Subdevice #0: subdevice #0
   Subdevice #1: subdevice #1
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: zeilloc 1887 F.... pulseaudio
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xdf300000 irq 22'
   Mixer name : 'Nvidia MCP78 HDMI'
   Components : 'HDA:111d76b2,103c3603,00100302 HDA:10de0006,10de0101,00100000'
   Controls : 39
   Simple ctrls : 23
DistroRelease: Ubuntu 9.10
HibernationDevice: RESUME=UUID=4d9fa164-7f95-464f-a7b2-ccef14857603
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
MachineType: Hewlett-Packard HP Pavilion dv5 Notebook PC
NonfreeKernelModules: nvidia
Package: linux (not installed)
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-17-generic root=UUID=1257db60-9fbe-4a1c-aad6-9303cbff6640 ro quiet splash noacpi
ProcEnviron:
 PATH=(custom, no user)
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-17.54-generic
RelatedPackageVersions:
 linux-backports-modules-2.6.31-17-generic N/A
 linux-firmware 1.25
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
Uname: Linux 2.6.31-17-generic i686
UserGroups:

dmi.bios.date: 01/23/2009
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.14
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 3603
dmi.board.vendor: Quanta
dmi.board.version: 02.22
dmi.chassis.type: 10
dmi.chassis.vendor: Quanta
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnHewlett-Packard:bvrF.14:bd01/23/2009:svnHewlett-Packard:pnHPPaviliondv5NotebookPC:pvrRev1:rvnQuanta:rn3603:rvr02.22:cvnQuanta:ct10:cvrN/A:
dmi.product.name: HP Pavilion dv5 Notebook PC
dmi.product.version: Rev 1
dmi.sys.vendor: Hewlett-Packard

Revision history for this message
Zeilloc (zeilloc) wrote : AlsaDevices.txt
Revision history for this message
Zeilloc (zeilloc) wrote : AplayDevices.txt
Revision history for this message
Zeilloc (zeilloc) wrote : BootDmesg.txt
Revision history for this message
Zeilloc (zeilloc) wrote : CRDA.txt
Revision history for this message
Zeilloc (zeilloc) wrote : Card0.Amixer.values.txt
Revision history for this message
Zeilloc (zeilloc) wrote : Card0.Codecs.codec.0.txt
Revision history for this message
Zeilloc (zeilloc) wrote : Card0.Codecs.codec.2.txt
Revision history for this message
Zeilloc (zeilloc) wrote : CurrentDmesg.txt
Revision history for this message
Zeilloc (zeilloc) wrote : IwConfig.txt
Revision history for this message
Zeilloc (zeilloc) wrote : Lspci.txt
Revision history for this message
Zeilloc (zeilloc) wrote : Lsusb.txt
Revision history for this message
Zeilloc (zeilloc) wrote : PciMultimedia.txt
Revision history for this message
Zeilloc (zeilloc) wrote : ProcCpuinfo.txt
Revision history for this message
Zeilloc (zeilloc) wrote : ProcInterrupts.txt
Revision history for this message
Zeilloc (zeilloc) wrote : ProcModules.txt
Revision history for this message
Zeilloc (zeilloc) wrote : UdevDb.txt
Revision history for this message
Zeilloc (zeilloc) wrote : UdevLog.txt
Revision history for this message
Zeilloc (zeilloc) wrote : WifiSyslog.txt
Revision history for this message
Zeilloc (zeilloc) wrote : XsessionErrors.txt
Changed in linux (Ubuntu):
status: Incomplete → New
Revision history for this message
Zeilloc (zeilloc) wrote :

From apport-collect, we can read : "dmi.bios.version: F.14"
I am far form the F21...

Revision history for this message
Paul Dufresne (paulduf) wrote :

I see from your BootDmesg.txt file:
[ 0.000000] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-2.6.31-17-generic root=UUID=1257db60-9fbe-4a1c-aad6-9303cbff6640 ro quiet splash noacpi

The noacpi option here is not the default as far as I know, you did add it?
From http://www.kernel.org/doc/Documentation/kernel-parameters.txt :
 acpi= [HW,ACPI,X86]
   Advanced Configuration and Power Interface
   Format: { force | off | ht | strict | noirq | rsdt }
   force -- enable ACPI if default was off
   off -- disable ACPI if default was on
   noirq -- do not use ACPI for IRQ routing
   ht -- run only enough ACPI to enable Hyper Threading
   strict -- Be less tolerant of platforms that are not
    strictly ACPI specification compliant.
   rsdt -- prefer RSDT over (default) XSDT

   See also Documentation/power/pm.txt, pci=noacpi

Well, I am not a developer, just a bug triager. But it looks like you are saying by this noacpi option, not to use Advanced Configuration and Power Interface (ACPI) which seems likely not to help suspending.

Now that we are using Grub2 rather than plain old grub, I think I am a bit lost as to where it must be changed. But I guess you can test different values by pressing 'e' to edit the command in grub menu before doing Enter.

Also, although it does make sense for me to update BIOS, it can be risky (especially if current goes out during the procedure)... so you have to know and accept the risk.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Paul Dufresne (paulduf) wrote :

I suggest you first try to use 'e' to edit the command line in Grub menu when you boot first.
Then if you want to do permanent change:
Oh, reading about Grub2 at: http://doc.ubuntu-fr.org/grub-pc (I speak french too ^^), then I think that the file to be edited is:
gksudo gedit /etc/default/grub
Then edit the line GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" and remove the 'noacpi' if it is there.
Then type 'sudo update-grub' in the terminal to update the Grub menu for real.

Revision history for this message
Zeilloc (zeilloc) wrote :

I edited the grub.cfg file and /etc/default/grub file, and removed the "noacpi".
(I added it after reading smthing that suggested to do it)

But I still have the problem...

Could I do smthg else ?

Revision history for this message
Paul Dufresne (paulduf) wrote :

you did the 'sudo update-grub'? Then rebooted?
I would probably try with 'acpi=strict' if I were you.

Did you, or do you intend to update the BIOS?

Revision history for this message
Paul Dufresne (paulduf) wrote :

Just for testing 'acpi=strict' it is easier to just type 'e' after booting in Grub, then edit the line with 'e', then do Ctrl-X to boot with the temporarily modified version.

Revision history for this message
Zeilloc (zeilloc) wrote :

OK I tried "acpi=strict" by taping "e" just after booting, but still have the same problem.

I'll probably update my BIOS soon and will give you news.

Revision history for this message
Brad Figg (brad-figg) wrote : Unsupported series, setting status to "Won't Fix".

This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: Incomplete → Won't Fix
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.