Created attachment 62870 [details] Xorg.0.log after crash Hello! After some days xorg usually crashes with a segmentation fault. I'm now restarting xorg with this script to catch the errors: [9:38] brief:~% cat bin/restart-x #!/bin/sh while true; do startx cp /var/log/Xorg.0.log ~/Xorg.0.log-crash-$(date +%s) sleep 1 done This happens around once every 2 days and seems not directly related to suspending the machine, as it happens when viewing or typing. Attached is the Xorg.0.log and dmesg. Kernel is 3.3.8-1-ARCH. Cheers, Nico
Created attachment 62871 [details] dmesg at the time of crash
[ 63430.639] Backtrace: [ 63430.639] 0: /usr/bin/X (xorg_backtrace+0x36) [0x55db86] [ 63430.639] 1: /usr/bin/X (0x400000+0x1615b9) [0x5615b9] [ 63430.639] 2: /lib/libpthread.so.0 (0x7f1ec2e61000+0xf140) [0x7f1ec2e70140] [ 63430.639] 3: /usr/lib/xorg/modules/input/synaptics_drv.so (0x7f1ebdd25000+0x26e8) [0x7f1ebdd276e8] [ 63430.639] 4: /usr/bin/X (BasicComputeAcceleration+0x7) [0x450d77] [ 63430.639] 5: /usr/bin/X (0x400000+0x51628) [0x451628] [ 63430.639] 6: /usr/bin/X (0x400000+0x48505) [0x448505] [ 63430.639] 7: /usr/bin/X (GetPointerEvents+0xbc) [0x44971c] [ 63430.640] 8: /usr/bin/X (QueuePointerEvents+0x1d) [0x449bdd] [ 63430.640] 9: /usr/bin/X (xf86PostMotionEvent+0xc0) [0x47d710] [ 63430.640] 10: /usr/lib/xorg/modules/input/synaptics_drv.so (0x7f1ebdd25000+0x4d35) [0x7f1ebdd29d35] [ 63430.640] 11: /usr/lib/xorg/modules/input/synaptics_drv.so (0x7f1ebdd25000+0x6db2) [0x7f1ebdd2bdb2] [ 63430.640] 12: /usr/bin/X (0x400000+0x6e017) [0x46e017] [ 63430.640] 13: /usr/bin/X (0x400000+0x91e88) [0x491e88] [ 63430.640] 14: /lib/libpthread.so.0 (0x7f1ec2e61000+0xf140) [0x7f1ec2e70140] [ 63430.640] 15: /lib/libc.so.6 (__select+0x13) [0x7f1ec1dd5e23] [ 63430.640] 16: /usr/bin/X (WaitForSomething+0x190) [0x55b050] [ 63430.640] 17: /usr/bin/X (0x400000+0x33d41) [0x433d41] [ 63430.640] 18: /usr/bin/X (0x400000+0x23205) [0x423205] [ 63430.640] 19: /lib/libc.so.6 (__libc_start_main+0xf5) [0x7f1ec1d19455] [ 63430.641] 20: /usr/bin/X (0x400000+0x234dd) [0x4234dd] [ 63430.641]
Comment on attachment 62870 [details] Xorg.0.log after crash Please choose the correct mime type next time.
Created attachment 62937 [details] Xorg.0.log after crash - 2 Another crash today
please install synaptics 1.6.2, a few of the patches in there may fix this issue.
I'm already on 1.6.2: [17:49] brief:~# pacman -Q | grep synap xf86-input-synaptics 1.6.2-1 [10:51] brief:~#
both of your logs show a module version of 1.6.1 though, did you restart X after upgrading?
Also happens with 1.6.2, attaching new crash log file.
Created attachment 63172 [details] Latest crash with 1.6.2
Any progress here? I've now rather often crashing xorg: [17:47] brief:~% ls -ltrh Xorg.0.log* -rw------- 1 nico nico 35K Apr 19 19:58 Xorg.0.log -rw------- 1 nico nico 348K May 4 08:39 Xorg.0.log.2 -rw------- 1 nico nico 334K May 5 13:54 Xorg.0.log3 -rw------- 1 nico nico 256K Jun 11 09:34 Xorg.0.log-crash-1339400088 -rw------- 1 nico nico 83K Jun 11 09:41 Xorg.0.log-crash-dmesg-1339400088 -rw------- 1 nico nico 429K Jun 12 13:42 Xorg.0.log-crash-1339501338 -rw------- 1 nico nico 556K Jun 16 15:35 Xorg.0.log-crash-1339853719 -rw------- 1 nico nico 1.5M Jun 17 02:23 Xorg.0.log-crash-1339892597 -rw------- 1 nico nico 534K Jun 18 13:13 Xorg.0.log-crash-1340017986 -rw------- 1 nico nico 1.4M Jun 19 11:09 Xorg.0.log-crash-1340096963 -rw------- 1 nico nico 1.4M Jun 20 09:29 Xorg.0.log-crash-1340177393 -rw------- 1 nico nico 350K Jun 21 11:42 Xorg.0.log-crash-1340271725 -rw------- 1 nico nico 35K Jun 26 09:17 Xorg.0.log-crash-1340695074 -rw------- 1 nico nico 6.8M Jun 28 09:59 Xorg.0.log-crash-1340870367 -rw------- 1 nico nico 6.8M Jun 29 10:19 Xorg.0.log-crash-1340957974 -rw------- 1 nico nico 6.8M Jul 1 17:04 Xorg.0.log-crash-1341155071 -rw------- 1 nico nico 6.8M Jul 3 08:26 Xorg.0.log-crash-1341296799 -rw------- 1 nico nico 5.7M Jul 4 12:29 Xorg.0.log-crash-1341397770 -rw------- 1 nico nico 3.1M Jul 5 17:26 Xorg.0.log-crash-1341501989 -rw------- 1 nico nico 57K Jul 5 17:36 Xorg.0.log-crash-1341502587 -rw------- 1 nico nico 1.7M Jul 6 15:51 Xorg.0.log-crash-1341582690 -rw------- 1 nico nico 1.7M Jul 7 09:50 Xorg.0.log-crash-1341647431 -rw------- 1 nico nico 1.8M Jul 9 10:25 Xorg.0.log-crash-1341822346 [17:47] brief:~% The deltas between the crashes are around one day: [17:49] brief:~% lasttime=0; while read time; do diff=$((time-lasttime)); echo $diff; lasttime=$time; done < xorg-crash-times 1339400088 101250 352381 38878 125389 78977 80430 94332 423349 175293 87607 197097 141728 100971 104219 598 80103 64741 174915 And it seems to be related to closing the lid. On lid close the following script is executed: [17:51] brief:~% cat bin/acpi-lid-close #!/bin/sh if grep -q closed /proc/acpi/button/lid/*/state; then sleep 3 su nico -c "DISPLAY=:0.0 xset dpms force off" fi [17:51] brief:~%
I have crashes on a Thinkpad T410s running Ubuntu 12.04 with maybe the same reason (BasicComputeAcceleration). See https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1032612
I'm not sure the two crashes nico posted are the same, the one with XIChangeDeviceProperty in the backtrace is likely #52496. Nico, let's stick to the BasicComputeAcceleration crash in this patch and focus on the other one in #52496
Ok, I can't reproduce this here and I don't know what the trigger is. I need both of you to install this xorg.conf.d snippet: $ cat /etc/X11/xorg.conf.d/99-synaptics-dontgrab.conf Section "InputClass" Identifier "Don't grab synaptics" MatchDriver "synaptics" Option "GrabEventDevice" "off" EndSection Then restart the server, install evemu [1] and set up evemu-record in a screen session, piping the output into a file. sudo evemu-record /dev/input/event4 > $HOME/synaptics.events (make sure you use the right device file) Leave it running until you see the crash. That will make the file grow very big, but you can work around this by restarting evemu-record regularly. It's likely that only the last few events will trigger it anyway, so when you actually get a recording, see if you can trigger the crash again with evemu-play /dev/input/event4 < $home/synaptics.events. If so, attach the file here and also the output of evemu-describe /dev/input/event4. [1] http://people.freedesktop.org/~whot/evemu/
Thanks Peter! I'll go into vacation on Friday and probably wont manage to do this before. If it's not solved when I come back, I'll instantly set this up.
@Peter Can you please elaborate on what you mean with "right device file"? # for f in /dev/input/event*; do echo $f && evemu-describe $f | head -n 1; done /dev/input/event0 N: Lid Switch /dev/input/event1 N: Sleep Button /dev/input/event10 N: HDA Intel HDMI/DP,pcm=3 /dev/input/event11 N: SynPS/2 Synaptics TouchPad /dev/input/event12 N: TPPS/2 IBM TrackPoint /dev/input/event2 N: Power Button /dev/input/event3 N: AT Translated Set 2 keyboard /dev/input/event4 N: HID 413c:3010 /dev/input/event5 N: Video Bus /dev/input/event6 N: Integrated Camera /dev/input/event7 N: ThinkPad Extra Buttons /dev/input/event8 N: HDA Intel HDMI/DP,pcm=8 /dev/input/event9 N: HDA Intel HDMI/DP,pcm=7 event4 doesn't produce any output when using the touchpad. The touchpad device file seems to be /dev/input/mouse1, but that seems not to be handled by evemu (evemu-play of a recorded file doesn't do anything).
The synaptics device, event 11 in the list above. Note that pointer devices have both a mouse and an event file, we ignore the former and only use the latter anyways.
After installing an update including the fix for https://bugs.freedesktop.org/show_bug.cgi?id=52496 I didn't yet have any crash nomore for several weeks (with many standby/wakeup cycles) now. Not sure if the bug described here is still valid, maybe it was just a side effect of the other bug.
Thanks for letting us know. I'll close this bug for now, please reopen it if it occurs again.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.