dv1550se: upower never registers lid-open event though ACPI does

Bug #1073029 reported by S. Christian Collins
18
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

I can check the reported state of my laptop lid's status (open or closed) via two methods:
  1) cat /proc/acpi/button/lid/LID/state
  2) upower --dump

Whether the lid is closed or open is not always reported identically between these two methods. On my laptop, after closing and opening the lid, "upower --dump" will report the lid as closed, while "/proc/acpi/button/lid/LID/state" correctly says the lid is open.

Using acpi_listen, my laptop generates lid events when the lid closes, but not when it opens. I compared this to another laptop and the second laptop generates laptop lid events both when opening and closing the lid.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-32-generic 3.2.0-32.51
ProcVersionSignature: Ubuntu 3.2.0-32.51-generic 3.2.30
Uname: Linux 3.2.0-32-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu14
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: chris 2049 F.... pulseaudio
Card0.Amixer.info:
 Card hw:0 'ICH6'/'Intel ICH6 with Cx20468-31 at irq 17'
   Mixer name : 'Conexant Cx20468-31'
   Components : 'AC97a:43585430'
   Controls : 23
   Simple ctrls : 16
Date: Mon Oct 29 23:23:16 2012
HibernationDevice: RESUME=UUID=93ca6641-5047-45e2-b14a-453fbe249e5f
InstallationMedia: Kubuntu 11.04 "Natty Narwhal" - Release i386 (20110427)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: Hewlett-Packard HP Pavilion dv1000 (EP347UA#ABA)
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcEnviron:
 LANGUAGE=en_US
 TERM=xterm
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-32-generic root=UUID=2b67964c-26a9-4422-89dd-1593528a0ffc ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.2.0-32-generic N/A
 linux-backports-modules-3.2.0-32-generic N/A
 linux-firmware 1.79.1
SourcePackage: linux
UpgradeStatus: Upgraded to precise on 2012-05-01 (181 days ago)
dmi.bios.date: 03/23/2006
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.22
dmi.board.name: 308F
dmi.board.vendor: Quanta
dmi.board.version: 46.13
dmi.chassis.type: 10
dmi.chassis.vendor: Quanta
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnHewlett-Packard:bvrF.22:bd03/23/2006:svnHewlett-Packard:pnHPPaviliondv1000(EP347UA#ABA):pvrRev1:rvnQuanta:rn308F:rvr46.13:cvnQuanta:ct10:cvrN/A:
dmi.product.name: HP Pavilion dv1000 (EP347UA#ABA)
dmi.product.version: Rev 1
dmi.sys.vendor: Hewlett-Packard

Revision history for this message
S. Christian Collins (s-chriscollins) wrote :
Brad Figg (brad-figg)
Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.7 kernel[0] (Not a kernel in the daily directory) and install both the linux-image and linux-image-extra .deb packages.

Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. Please only remove that one tag and leave the other tags. 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 in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

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

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.7-rc4-raring/

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
tags: added: needs-upstream-testing
Revision history for this message
S. Christian Collins (s-chriscollins) wrote :

I tested using the 3.7-rc4 mainline kernel and the bug still persists. I have updated the tags and bug status accordingly.

tags: added: kernel-bug-exists-upstream
removed: needs-upstream-testing
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
penalvch (penalvch) wrote :

S. Christian Collins, could you please provide the full computer model as noted on the sticker?

description: updated
tags: added: lucid
tags: added: needs-full-computer-model needs-upstream-testing regression-potential
tags: added: kernel-bug-exists-upstream-v3.7-rc4
removed: kernel-bug-exists-upstream
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
S. Christian Collins (s-chriscollins) wrote :

Shoot, I thought that was the full computer model (HP Pavilion dv1550se). Unfortunately, I no longer own this laptop, so I am unable to investigate further.

Revision history for this message
penalvch (penalvch) wrote :

S. Christian Collins, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1073029/comments/5 regarding you no longer having the hardware. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.

Changed in linux (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.