Me and a lot of people are experiencing X lockups with the only symptom of 2 repeated lines in the log file : tossed event which came in late mieqEnequeue: out-of-order valuator event; dropping. I don't use 3D at all when the failure happens. X is locked but display is not frozen. The cursor can move. No artifacts. X process is eating all the CPU. killall -9 X ; startx # and there you go for another round I attached a Xorg.0.log in https://bugs.freedesktop.org/attachment.cgi?id=14219 I've been having this behavior since some weeks. First appeared with Xorg-server 1.3, continues with 1.4.0.90. You'll find relevant information in my attached Xorg logfile. System is Linux MacGyver 2.6.24-MacGyver #4 PREEMPT Tue Jan 29 16:59:41 EST 2008 i686 Intel(R) Pentium(R) M processor 1.70GHz GenuineIntel GNU/Linux Gentoo, gcc 4.2.2.
this is a sign that the server is stuck in some infinite loop (often this is a graphics driver problem). can you try with a newer version of the driver?
I compiled 1 hour old's xorg-drivers-ati (svn) and the problem still appeared. In case you wondered, I've had the problem with different window managers (fluxbox, sawfish) It seems to appear when there's a certain UI activity. When I let the computer alone, I'm sure I can't get lockups. If I can help, tell me how. Thanks,
(In reply to comment #2) > I compiled 1 hour old's xorg-drivers-ati (svn) and the problem still appeared. > > In case you wondered, I've had the problem with different window managers > (fluxbox, sawfish) > > It seems to appear when there's a certain UI activity. > When I let the computer alone, I'm sure I can't get lockups. > > If I can help, tell me how. any reproducible test case would be much appreciated. I could be a stuck unfreeze.
I can reproduce this. I've read stuff in all the forums blaming the video card / GPU which makes no sense at all to me. I'm currently using Gentoo. I'll attach my Xorg.log and my xorg.conf. My xorg.conf is sorta weird cause I'm running two X servers, one per video card, with each server getting its own mouse and keyboard. The problem started happened after I upgraded to the version of X that auto-detects devices (I turned that off in my xorg.conf due to my weird setup). I'm also using an older evdev driver (1.1.5) because the newer one (1.2+) doesn't work with my setup either (without autodetect enabled, it finds no devices at all!) (see Gentoo Bug #205041) I've notice that the problem occurs whenever I click/drag with the Ctrl modified pressed. Seriously. I've tried to carefully avoid using the Ctrl key and I've been stable for several days, but the moment I select a group of files using Ctrl instead of shift, it will lock up. I'm not making this up! (see Gentoo Bug #207106) Here are the current versions of most of my X packages: $ epm -qa | grep xf86 xf86-input-evdev-1.1.5-r2 xf86-input-keyboard-1.2.2 xf86-input-mouse-1.2.3 xf86-video-apm-1.0.1.5 xf86-video-ark-0.5.0.5 xf86-video-ati-6.5.8.0 xf86-video-chips-1.0.1.3 xf86-video-cirrus-1.0.0.5 xf86-video-cyrix-1.0.0.5 xf86-video-dummy-0.1.0.5 xf86-video-fbdev-0.1.0.5 xf86-video-glint-1.0.1.3 xf86-video-i128-1.1.0.5 xf86-video-i810-1.4.1.3 xf86-video-mga-1.2.1.3 xf86-video-neomagic-1.0.0.5 xf86-video-nv-2.1.6 xf86-video-rendition-4.0.1.3 xf86-video-s3-0.3.5.5 xf86-video-s3virge-1.8.6.5 xf86-video-savage-2.0.2.3 xf86-video-siliconmotion-1.3.1.5 xf86-video-sis-0.8.1.3 xf86-video-sisusb-0.7.1.3 xf86-video-tdfx-1.1.1.3 xf86-video-tga-1.0.0.5 xf86-video-trident-1.2.3 xf86-video-tseng-1.0.0.5 xf86-video-v4l-0.0.1.5 xf86-video-vesa-1.3.0 xf86-video-vga-4.1.0 xf86-video-via-0.1.33.2 xf86-video-vmware-10.12.0.0 xf86-video-voodoo-1.0.0.5 libXxf86dga-1.0.2 libXxf86misc-1.0.1 libXxf86vm-1.0.1 xf86bigfontproto-1.1.2 xf86dgaproto-2.0.3 xf86driproto-2.0.3 xf86miscproto-0.9.2 xf86rushproto-1.1.2 xf86vidmodeproto-2.2.2
Created attachment 14278 [details] Xorg Log after lockup
Created attachment 14279 [details] My xorg.conf
In my case I haven't yet isolated what is causing the bug, but if it's the Ctrl key, then it's definitely not a 100% sure method to get it. I'm currently investigating what could be causing it (from an user point of view). Yesterday X froze and became immortal (along with a scim zombie), until I rebooted.
(In reply to comment #4) > The problem started happened after I upgraded to the version of X that > auto-detects devices (I turned that off in my xorg.conf due to my weird setup). > I'm also using an older evdev driver (1.1.5) because the newer one (1.2+) > doesn't work with my setup either (without autodetect enabled, it finds no > devices at all!) (see Gentoo Bug #205041) You need evdev 1.2 for a server 1.4. evdev 1.15 does all sorts of crazy stuff to enable its own hotplugging and it does not work cooperate with the server on it. Please upgrade to 1.2. I read the bug on gentoo and I now your devices don't work. Using 1.1.5 however isn't a fix, it causes another load of issues. I notice that you don't specify the Option Device in your config for the two devices that fail. Please do so and try agin.
(In reply to comment #7) > In my case I haven't yet isolated what is causing the bug, but if it's the Ctrl > key, then it's definitely not a 100% sure method to get it. > > I'm currently investigating what could be causing it (from an user point of > view). > > Yesterday X froze and became immortal (along with a scim zombie), until I > rebooted. can you please cross-check with #13511, especially if you have the matching commit in your tree?
Indeed Peter, it seems to be the same bug. I can reproduce when I want with the "example" maneuver. I guess I can close it, since #13511 is resolved.
Issue seems to be resolved with current git sources.
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.