Bug 197921 - X server crashes when laptop lid is closed
Summary: X server crashes when laptop lid is closed
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-server
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Adam Jackson
QA Contact:
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-07-07 12:15 UTC by Karsten Hopp
Modified: 2008-08-02 23:40 UTC (History)
1 user (show)

(edit)
Clone Of:
(edit)
Last Closed: 2007-05-26 19:09:26 UTC


Attachments (Terms of Use)
log of crashed X server (48.07 KB, text/plain)
2006-07-07 12:15 UTC, Karsten Hopp
no flags Details

Description Karsten Hopp 2006-07-07 12:15:56 UTC
Description of problem:
When I close the lid of my laptop (r128), the X server aborts with the following
error:
Backtrace:
0: X(xf86SigHandler+0x81) [0x80c6141]
1: [0x628420]
2: /lib/libc.so.6 [0x2b048e]
3: /lib/libc.so.6(__strtoul_internal+0x3f) [0x2afe47]
4: X [0x80b4750]
5: X(xf86HandlePMEvents+0x3b) [0x80dddfb]
6: X(xf86Wakeup+0x153) [0x80c7603]
7: X(WakeupHandler+0x59) [0x808b059]
8: X(WaitForSomething+0x1b9) [0x8197f69]
9: X(Dispatch+0x8d) [0x8086e7d]
10: X(main+0x485) [0x806e995]
11: /lib/libc.so.6(__libc_start_main+0xdc) [0x299794]
12: X [0x806dcd1]

Fatal server error:
Caught signal 11.  Server aborting


Version-Release number of selected component (if applicable):
xorg-x11-drv-ati-6.6.1-4
xorg-x11-server-Xorg-1.1.0-24


How reproducible:
everytime

Comment 1 Karsten Hopp 2006-07-07 12:15:56 UTC
Created attachment 132046 [details]
log of crashed X server

Comment 2 Adam Jackson 2006-08-04 23:04:54 UTC
Yow.  The ACPI event parser is astonishingly bad.  I'll look into this.

Comment 3 Adam Jackson 2006-09-21 22:58:51 UTC
assign to me for visibility...

Comment 4 Adam Jackson 2006-09-22 00:30:54 UTC
Try something for me.  ssh into the machine with the r128, run:

nc -U /var/run/acpid.socket

and close the lid.  I want to see the message we're getting from the kernel
that's causing the crash.

Comment 5 Adam Jackson 2006-10-31 22:49:14 UTC
Karsten, had a chance to try this yet?

Comment 6 Oleg Drokin 2006-11-03 16:47:58 UTC
I am not original requestior, but here it is for my laptop (i9xx based
videocard, bbut crash is everywhere)
[green@orc ~]$ nc -U /var/run/acpid.socket 
video VID 00000080 00000000
video VID 00000080 00000000
button/lid LID 00000080 00000001
video VID 00000080 00000000
video VID 00000080 00000000
button/lid LID 00000080 00000002

he problems seems to be invalid strtok in lnx_acpi.c
The problem is more fully discussed at
https://bugs.freedesktop.org/show_bug.cgi?id=8776 but the patch there, while
fixing the crash, just causes my X server to always blank display, so that even
when I open the lid and I have acpid workaround (in /etc/acpi/events/video.conf)
the display does not turn on (but in console that workaround works), so I was
forced to use that Option "NoPM" for now. OF course the screen does not turn on
by itself now, but with acpid event it is better than X server crash.
(also, though this is probably not relevant for this bug, the original FC6
workaround turns on display on any video even, for example on lid CLOSE, which
is very bad idea of course.
I replaced the event/action with this, which only turns on the lcd when the lid
is opened (at least on my laptop:
event=button/lid LID 00000080 .{7}[02468ace]
action=/usr/sbin/vbetool dpms on
)

Comment 7 Oleg Drokin 2006-11-05 17:04:32 UTC
I forgot to add that this actually happens with recently released fedora core6
and from my understanding, this should happen on any laptop out there when you
close the lid, so I am shocked you are not flooded with bugreports about this
already.
Unfortunatelly Iam unable to change the Version field.

Comment 8 Adam Jackson 2007-01-30 00:11:34 UTC
This ought to be fixed in rawhide, as of xorg-x11-server 1.1.1-55 and later. 
Please test, and reopen if this is still an issue in FC7.

Comment 9 Adam Jackson 2007-05-26 19:09:26 UTC
Mass closure: This bug has been in NEEDINFO for over six weeks with no
additional information provided, and is therefore being closed.  If this bug is
still an issue for you, please supply the requested information, and reopen the bug.


Note You need to log in before you can comment on or make changes to this bug.