HP Envy 14 doesn't suspend by closing lid

Bug #854404 reported by Ivan Sagalaev
36
This bug affects 6 people
Affects Status Importance Assigned to Milestone
upower (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Laptop doesn't suspend by closing lid. Choosing Suspend from the settings menu (the thing in upper-right corner) does work and opening lid does wake the machine up if suspended this way. The problem didn't manifest itself right after the upgrade to 11.10 beta but appeared after some subsequent update.

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: gnome-settings-daemon 3.1.92-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
Uname: Linux 3.0.0-11-generic x86_64
ApportVersion: 1.23-0ubuntu1
Architecture: amd64
Date: Mon Sep 19 20:57:02 2011
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110330)
SourcePackage: gnome-settings-daemon
UpgradeStatus: Upgraded to oneiric on 2011-09-02 (18 days ago)
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 1.23-0ubuntu3
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: maniac 1486 F.... pulseaudio
 /dev/snd/controlC0: maniac 1486 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xc4500000 irq 45'
   Mixer name : 'IDT 92HD81B1X5'
   Components : 'HDA:111d7605,103c1436,00100402'
   Controls : 14
   Simple ctrls : 9
Card1.Amixer.info:
 Card hw:1 'Generic'/'HD-Audio Generic at 0xc4420000 irq 47'
   Mixer name : 'ATI R6xx HDMI'
   Components : 'HDA:1002aa01,00aa0100,00100200'
   Controls : 4
   Simple ctrls : 1
Card1.Amixer.values:
 Simple mixer control 'IEC958',0
   Capabilities: pswitch pswitch-joined penum
   Playback channels: Mono
   Mono: Playback [on]
DistroRelease: Ubuntu 11.10
HibernationDevice: RESUME=UUID=b63b78fc-9e49-4880-9ff2-0cc35d2bde7f
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
 Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
 Bus 002 Device 003: ID 10f1:1a25 Importek
MachineType: Hewlett-Packard HP ENVY 14 Notebook PC
Package: linux (not installed)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-12-generic root=UUID=1bfc3e46-4eae-4766-9263-5a3bfedeea42 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
RelatedPackageVersions:
 linux-restricted-modules-3.0.0-12-generic N/A
 linux-backports-modules-3.0.0-12-generic N/A
 linux-firmware 1.60
StagingDrivers: mei keucr
Tags: oneiric running-unity staging
Uname: Linux 3.0.0-12-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 11/11/2010
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.23
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 1436
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 59.23
dmi.chassis.asset.tag: CNU112103Y
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnHewlett-Packard:bvrF.23:bd11/11/2010:svnHewlett-Packard:pnHPENVY14NotebookPC:pvr058D120000241910001620100:rvnHewlett-Packard:rn1436:rvr59.23:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.name: HP ENVY 14 Notebook PC
dmi.product.version: 058D120000241910001620100
dmi.sys.vendor: Hewlett-Packard

Revision history for this message
Ivan Sagalaev (isagalaev) wrote :
Revision history for this message
Ivan Sagalaev (isagalaev) wrote :

I'm not really sure if this is related to gnome-settings-daemon at all…

affects: gnome-settings-daemon (Ubuntu) → ubuntu
Revision history for this message
Ivan Sagalaev (isagalaev) wrote :

This behavior is also present during a live CD session meaning it's not caused by user's configuration.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in ubuntu:
status: New → Confirmed
Revision history for this message
Fabio Marconi (fabiomarconi) wrote :

seemsa kernel problem, marking as afecting linux

affects: ubuntu → linux (Ubuntu)
Revision history for this message
Fabio Marconi (fabiomarconi) wrote :

Hello,
can someone reproduce the bug then run in a terminal
apport-collect -p linux 854404
Thanks
Fabio

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Ivan Sagalaev (isagalaev) wrote : AcpiTables.txt

apport information

tags: added: apport-collected staging
description: updated
Revision history for this message
Ivan Sagalaev (isagalaev) wrote : AlsaDevices.txt

apport information

Revision history for this message
Ivan Sagalaev (isagalaev) wrote : AplayDevices.txt

apport information

Revision history for this message
Ivan Sagalaev (isagalaev) wrote : BootDmesg.txt

apport information

Revision history for this message
Ivan Sagalaev (isagalaev) wrote : Card0.Amixer.values.txt

apport information

Revision history for this message
Ivan Sagalaev (isagalaev) wrote : Card0.Codecs.codec.0.txt

apport information

Revision history for this message
Ivan Sagalaev (isagalaev) wrote : Card1.Codecs.codec.0.txt

apport information

Revision history for this message
Ivan Sagalaev (isagalaev) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Ivan Sagalaev (isagalaev) wrote : IwConfig.txt

apport information

Revision history for this message
Ivan Sagalaev (isagalaev) wrote : Lspci.txt

apport information

Revision history for this message
Ivan Sagalaev (isagalaev) wrote : PciMultimedia.txt

apport information

Revision history for this message
Ivan Sagalaev (isagalaev) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Ivan Sagalaev (isagalaev) wrote : ProcEnviron.txt

apport information

Revision history for this message
Ivan Sagalaev (isagalaev) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Ivan Sagalaev (isagalaev) wrote : ProcModules.txt

apport information

Revision history for this message
Ivan Sagalaev (isagalaev) wrote : PulseSinks.txt

apport information

Revision history for this message
Ivan Sagalaev (isagalaev) wrote : PulseSources.txt

apport information

Revision history for this message
Ivan Sagalaev (isagalaev) wrote : RfKill.txt

apport information

Revision history for this message
Ivan Sagalaev (isagalaev) wrote : UdevDb.txt

apport information

Revision history for this message
Ivan Sagalaev (isagalaev) wrote : UdevLog.txt

apport information

Revision history for this message
Ivan Sagalaev (isagalaev) wrote : WifiSyslog.txt

apport information

Revision history for this message
Ivan Sagalaev (isagalaev) wrote :

apport-collect attached this bunch of files. To reproduce the bug I closed the lid, waited for about 10 seconds and when it didn't go to sleep, opened the lid again and run apport-collect. I can also collect the information after successful suspend from the menu if needed.

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the release candidate kernel versus the daily build. Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag(Only that one tag, please leave the others). 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.

If this bug is fixed by the mainline kernel, please add the following tag 'kernel-fixed-upstream-KERNEL-VERSION'. For example, if kernel version 3.1-rc9 fixed and issue, the tag would be: 'kernel-fixed-upstream-v3.1-rc9'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Thanks in advance.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
tags: added: needs-upstream-testing
Revision history for this message
Ivan Sagalaev (isagalaev) wrote :

I'll try to test it though my kernel-fiddling-fu is rusty since I was doing it last time on FreeBSD 2.4 :-)

Revision history for this message
Ivan Sagalaev (isagalaev) wrote :

Running the new kernel:

maniac@maniac-envy:~$ uname -a
Linux maniac-envy 3.1.0-030100rc10-generic #201110200610 SMP Thu Oct 20 10:11:32 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux

The behavior is the same.

I also looked into /var/log and it appears three files consistently have new messages upon *opening* the lid, but nothing on closing:

auth.log:

Oct 21 11:18:24 maniac-envy su[3099]: Successful su for maniac by root
Oct 21 11:18:24 maniac-envy su[3099]: + ??? root:maniac
Oct 21 11:18:24 maniac-envy su[3099]: pam_unix(su:session): session opened for user maniac by (uid=0)
Oct 21 11:18:25 maniac-envy su[3099]: pam_unix(su:session): session closed for user maniac

syslog and kern.log:

Oct 21 11:18:24 maniac-envy kernel: [ 390.672734] [drm:ironlake_update_pch_refclk] *ERROR* enabling SSC on PCH

Another small observation is that the screen itself switches off in the closed state but it's probably a purely hardware switch…

Revision history for this message
Ivan Sagalaev (isagalaev) wrote :

I also changed Gnome settings for closing lid from "Suspend" to "Hibernate" and the behavior is the same: nothing happens upon closing the lid.

tags: added: kernel-bug-exists-upstream
removed: needs-upstream-testing
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report at bugzilla.kernel.org? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug.

If you are comfortable with opening a bug upstream, It would be great if you can report back the upstream bug number in this bug report. That will allow us to link this bug to the upstream report.

Revision history for this message
BDenis (borenko) wrote :

It's not kernel bug, it's upower.
Upower saw your hybrid graphic and become crazy. It think that your notebook docked and disable lid switch.
Upower bug: https://bugs.freedesktop.org/show_bug.cgi?id=36818

Revision history for this message
Ivan Sagalaev (isagalaev) wrote :

Denis, thanks! This indeed makes more sense.

affects: linux (Ubuntu) → upower (Ubuntu)
Revision history for this message
BDenis (borenko) wrote :
Revision history for this message
BDenis (borenko) wrote :

To check that patch work try in console:
upower -d|grep is-docked
if there is no external display attached to notebook you must see:
is-docked: no

Revision history for this message
Ivan Sagalaev (isagalaev) wrote :

Denis, would it be hard for you to rebuild the test package with version 0.9.13-1-test1 ? The way it is now — the same version as the system package — it's not uninstallable.

Revision history for this message
BDenis (borenko) wrote :

try dpkg -i

Revision history for this message
BDenis (borenko) wrote :
Revision history for this message
Ivan Sagalaev (isagalaev) wrote :

I confirm this version (0.9.13-1test1) does indeed fix the problem. Thanks!

Revision history for this message
Ryan (ryansully) wrote :

Is this still an issue in Precise?
I discovered that this patch still isn't in the latest source of upower in Precise.

Revision history for this message
Ivan Sagalaev (isagalaev) wrote :

Thanks for reminding of this. It is indeed fixed in Precise with upower 0.9.15-1. It might have been fixed in a different way. What's the proper resolution for this bug then?

Revision history for this message
fyksen (fredrik-fyksen) wrote :

This is still an issue in Precise. Is there a fix/workaround for this yet?

Revision history for this message
Ivan Sagalaev (isagalaev) wrote :

For me this does work out of the box. Make sure you have "Suspend" set for "Lid closed" in System settings/Power. It remember it has been reset to "Do nothing" at some point during upgrades.

Revision history for this message
Logan Rosen (logan) wrote :

Marking this as Fix Released per Ivan. If another person is still having an issue with this, please file a new bug using ubuntu-bug upower.

Changed in upower (Ubuntu):
status: Confirmed → Fix Released
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.