Bug 24970

Created attachment 31022 [details]
dmesg log

Created attachment 31023 [details]
Dependencies

Created attachment 31024 [details]
glxinfo

Created attachment 31025 [details]
lspci

Created attachment 31026 [details]
monitors

Created attachment 31027 [details]
pcidisplay

Created attachment 31028 [details]
proccpuinfo

Created attachment 31029 [details]
procinterrupts

Created attachment 31030 [details]
procmodules

Created attachment 31031 [details]
xorg conf

Created attachment 31032 [details]
xorg log

Created attachment 31033 [details]
xorg log old

Using the ppa:x-edgers reposirory does not solve the bug either

Seems that disabling modesetting via grub works as workaround with little side effects.

Will you please boot the system and do the following test?
   1. kill the process which is using /proc/acpi/event(use the command of "lsof
/proc/acpi/event" to get the process id)
   2. cat /proc/acpi/event > event_log
   3. close and reopen the LID twice and then press the "CTRL+C" 
   4. attach the output of event_log

It will be great if you can attach the output of acpidump on your box.
   The acpidump can be obtained by using the pmtools-20071116, which can be
downloaded in:
    http://www.lesswatts.org/projects/acpi/utilities.php

thanks.
   Yakui

Hi, I experience same issue so I tried what you asked but everytime I kill the process using /proc/acpi/event here's what I got :

----
stan@stan-laptop:~$ sudo lsof /proc/acpi/event
lsof: WARNING: can't stat() fuse.gvfs-fuse-daemon file system /home/stan/.gvfs
      Output information may be incomplete.
COMMAND  PID USER   FD   TYPE DEVICE SIZE/OFF       NODE NAME
acpid   2212 root    3r   REG    0,3        0 4026531937 /proc/acpi/event
stan@stan-laptop:~$ sudo kill 9 2212
stan@stan-laptop:~$ sudo lsof /proc/acpi/event
lsof: WARNING: can't stat() fuse.gvfs-fuse-daemon file system /home/stan/.gvfs
      Output information may be incomplete.
COMMAND  PID USER   FD   TYPE DEVICE SIZE/OFF       NODE NAME
acpid   2363 root    3r   REG    0,3        0 4026531937 /proc/acpi/event
----

So cat won't work :
----
stan@stan-laptop:~$ sudo cat /proc/acpi/event > event_log
cat: /proc/acpi/event: Périphérique ou ressource occupé
----

Did I miss something ???

Thanks

Stan


(In reply to comment #15)
> Will you please boot the system and do the following test?
>    1. kill the process which is using /proc/acpi/event(use the command of "lsof
> /proc/acpi/event" to get the process id)
>    2. cat /proc/acpi/event > event_log
>    3. close and reopen the LID twice and then press the "CTRL+C" 
>    4. attach the output of event_log
> 
> It will be great if you can attach the output of acpidump on your box.
>    The acpidump can be obtained by using the pmtools-20071116, which can be
> downloaded in:
>     http://www.lesswatts.org/projects/acpi/utilities.php
> 
> thanks.
>    Yakui
> 

 ----
> 
> So cat won't work :
> ----
> stan@stan-laptop:~$ sudo cat /proc/acpi/event > event_log
> cat: /proc/acpi/event: Périphérique ou ressource occupé
> ----
> 
> Did I miss something ???

Sorry for the late response.
   Maybe on some distributions the acpid process can't be killed.

Can you try the latest kernel(2.6.34-rc1) and see whether the issue still exist?

Thanks.
> 
> Thanks
> 
> Stan
> 
> 
> (In reply to comment #15)
> > Will you please boot the system and do the following test?
> >    1. kill the process which is using /proc/acpi/event(use the command of "lsof
> > /proc/acpi/event" to get the process id)
> >    2. cat /proc/acpi/event > event_log
> >    3. close and reopen the LID twice and then press the "CTRL+C" 
> >    4. attach the output of event_log
> > 
> > It will be great if you can attach the output of acpidump on your box.
> >    The acpidump can be obtained by using the pmtools-20071116, which can be
> > downloaded in:
> >     http://www.lesswatts.org/projects/acpi/utilities.php
> > 
> > thanks.
> >    Yakui
> > 
> 

I also have this issue with a Thinkpad G40 (852GM), it still seems to be there with 2.6.34-rc3.

Whilst I don't have /proc/acpi/event support compiled, I can SSH into the laptop and do:-

# evtest /dev/input/event1
Input driver version is 1.0.0
Input device ID: bus 0x19 vendor 0x0 product 0x5 version 0x0
Input device name: "Lid Switch"
Supported events:
  Event type 0 (Sync)
  Event type 5 (?)
    Event code 0 (?)
Testing ... (interrupt to exit)
Event: time 1266880934.477757, type 5 (?), code 0 (?), value 1
Event: time 1266880934.477760, -------------- Report Sync ------------
Write failed: Broken pipe
... the laptop dies before a "lid open" event is issued.

Also whilst playing music I can close the lid (I don't trigger any action with the lid switch), it keeps on playing until I open the lid again.

I had similar problems with the non-KMS driver for some time, not precisely sure which version fixed it but could try and work it out if it's useful.

Laptop info:-
http://jamie.lentin.co.uk/hardware/g40/lsusb.txt
http://jamie.lentin.co.uk/hardware/g40/lspci.txt
http://jamie.lentin.co.uk/hardware/g40/dmidecode.txt
http://jamie.lentin.co.uk/hardware/g40/acpidump.txt
http://jamie.lentin.co.uk/hardware/g40/kernel_config.txt
http://jamie.lentin.co.uk/hardware/g40/xorg.conf

Thanks!

I have met similar issue with Dell Vostro 1015.

00:02.0 0300: 8086:2a42 (rev 07) (prog-if 00 [VGA controller])
	Subsystem: 1028:0402
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin A routed to IRQ 32
	Region 0: Memory at f6c00000 (64-bit, non-prefetchable) [size=4M]
	Region 2: Memory at e0000000 (64-bit, prefetchable) [size=256M]
	Region 4: I/O ports at efe8 [size=8]
	Expansion ROM at <unassigned> [disabled]
	Capabilities: <access denied>
	Kernel driver in use: i915
	Kernel modules: i915

I am running Arch Linux x86_64:
$ uname -a
Linux del-arch 2.6.33-ARCH #1 SMP PREEMPT Sun Apr 4 10:27:30 CEST 2010 x86_64 Intel(R) Core(TM)2 Duo CPU T6670 @ 2.20GHz GenuineIntel GNU/Linux
$ pacman -Q xf86-video-intel-newest xorg-server
xf86-video-intel-newest 2.11.0-2
xorg-server 1.7.6-3

The workaround with "xrandr" doesn't work for me: when I open the lid I see black screen however I can switch to console using CTRL+ALT+Fx. After that when I issue the script with xrandr it says: 

X Error of failed request:  BadMatch (invalid parameter attributes)
  Major opcode of failed request:  150 (RANDR)
  Minor opcode of failed request:  7 (RRSetScreenSize)
  Serial number of failed request:  26
  Current serial number in output stream:  27

Please disregard my comment about not working trick with xrandr.  I performed some debugging and saw that it didn't work due to the fact that lid state in /proc wasn't updated immediately. I added sleep to script and it worked.

This one should be fixed now; we don't use lid state anymore, though we do try to reset modes at lid open time.