X locks up after a random time
Ok, this is a Fujitsu Siemens Esprimo U9200, with Intel graphics, F10 64bit, updated last week. KDE desktop, compiz and all, but I believe it is not related. The symptom: system boots up regularly, I do regular work, and after a random amount of time, X freezes. If compiz is on, all I can do is move the mouse pointer. If compiz is off, even the mouse pointer is frozen. The OS itself is not, I can ssh from a remote machine and read logs. This is not reproducible, it happens too randomly and I can only sit and wait for it to happen. However, it is extremely annoying, since it has a tendency to freeze when I'm in the middle of some work in progress. If I log in remotely and kill -9 the X process, the whole machine locks up and I can only power-cycle it. Don't know a way to restart X short of rebooting, keyboard doesn't respond to ctrl-alt-backspace or anything else. So far, dmesg and /var/log/messages do not show anything related or even suspicious (afaics), while /var/log/Xorg.0.log shows this at the end: = [snip most of the regular log of a working X server] (II) intel(0): EDID for output TMDS-1 (II) intel(0): EDID for output TV [mi] EQ overflowing. The server is probably stuck in an infinite loop. Backtrace: 0: /usr/bin/X(xorg_backtrace+0x26) [0x4e7a26] 1: /usr/bin/X(mieqEnqueue+0x291) [0x4c8591] 2: /usr/bin/X(xf86PostMotionEventP+0xc4) [0x491494] 3: /usr/bin/X(xf86PostMotionEvent+0xa9) [0x491669] 4: /usr/lib64/xorg/modules/input//evdev_drv.so [0x7feeeaf3e126] 5: /usr/bin/X [0x47a765] 6: /usr/bin/X [0x46b307] 7: /lib64/libc.so.6 [0x3522232f90] 8: /lib64/libc.so.6(ioctl+0x7) [0x35222de037] 9: /usr/lib64/libdrm.so.2 [0x7feefd045023] 10: /usr/lib64/libdrm.so.2(drmCommandNone+0x16) [0x7feefd045326] 11: /usr/lib64/xorg/modules/drivers//intel_drv.so [0x7feefcdd0fc8] 12: /usr/bin/X [0x51cdb9] 13: /usr/bin/X [0x4f7311] 14: /usr/bin/X(BlockHandler+0x50) [0x44a320] 15: /usr/bin/X(WaitForSomething+0x161) [0x4e4eb1] 16: /usr/bin/X(Dispatch+0x7f) [0x4465ef] 17: /usr/bin/X(main+0x45d) [0x42cd1d] 18: /lib64/libc.so.6(__libc_start_main+0xe6) [0x352221e576] 19: /usr/bin/X [0x42c0f9] [mi] mieqEnequeue: out-of-order valuator event; dropping. [mi] EQ overflowing. The server is probably stuck in an infinite loop. [the last two lines repeat a lot of times] = So if the server is really in an infinite loop, then something so very Not Good is happening. Now, given that these are Intel open-source drivers driving my graphics card here, I have the following questions: 1) What does the [mi] stand for here? Can anyone decypher the backtrace for me? (I don't mind reading a "too technical" answer) 2) How can I further diagnose the problem and help fixing it? 3) In order to be efficient in diagnosing, does anyone know how to trigger the lockup on purpose? 4) This has been happening since I installed F10 on this machine --- has anyone spotted the problem already? Is there a known bugzilla report that I can add to? 5) Is there a workaround until a fix comes? 6) Can I somehow restart the X server from a remote console (without rebooting the whole machine) to recover clean from this? 7) F10 is out for a while now, how come a bug such as this (X in infinite loop) has not been fixed already? I mean, many people here bragg about the open source drivers being better then closed source when it comes to fixing broken things, so why is an issue such as this still present? // ok, this is a rant, I know, but I really am frustrated by this // Oh yes, lspci -v says this: 00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 03) (prog-if 00 [VGA controller]) Subsystem: Fujitsu Siemens Computers Device 110f Flags: bus master, fast devsel, latency 0, IRQ 16 Memory at fc00 (64-bit, non-prefetchable) [size=1M] Memory at d000 (64-bit, prefetchable) [size=256M] I/O ports at 18f8 [size=8] Capabilities: [90] Message Signalled Interrupts: Mask- 64bit- Count=1/1 Enable- Capabilities: [d0] Power Management version 3 Kernel modules: intelfb 00:02.1 Display controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 03) Subsystem: Fujitsu Siemens Computers Device 110f Flags: bus master, fast devsel, latency 0 Memory at fc10 (64-bit, non-prefetchable) [disabled] [size=1M] Capabilities: [d0] Power Management version 3 There is no /etc/X11/xorg.conf file, default stuff... Help please? Best, :-) Marko -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: X locks up after a random time
On Fri, Jan 2, 2009 at 10:36 PM, Marko Vojinovic wrote: > > Ok, this is a Fujitsu Siemens Esprimo U9200, with Intel graphics, F10 > 64bit, > updated last week. KDE desktop, compiz and all, but I believe it is not > related. > > The symptom: system boots up regularly, I do regular work, and after a > random > amount of time, X freezes. If compiz is on, all I can do is move the mouse > pointer. If compiz is off, even the mouse pointer is frozen. The OS itself > is > not, I can ssh from a remote machine and read logs. This is not > reproducible, > it happens too randomly and I can only sit and wait for it to happen. > However, it is extremely annoying, since it has a tendency to freeze when > I'm > in the middle of some work in progress. > > I have a similar problem on my desktop computer with an Intel card, but only if "Desktop Effects" are on. It does not matter if it is gnome or KDE. Otherwise, the system is pretty stable. But the symptoms are the same. The computer is alive, can be accessed remotely, but X is dead. In my case, with compiz on, the freezing is fast, less than 10 min after activation. You can try using Option "AccelMethod" "XAA" in your xorg.conf to see if there is any difference (I have never tried). -- Paulo Roma Cavalcanti LCG - UFRJ -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: X locks up after a random time
Marko Vojinovic wrote: > Ok, this is a Fujitsu Siemens Esprimo U9200, with Intel graphics, F10 > 64bit, updated last week. KDE desktop, compiz and all, but I believe it is > not related. Interesting, I'd noticed the same thing over the past few days... hmm (Dell Latitude D620 here). In the meantime, I've tried backing down to using kernel-2.6.27.7-134.fc10 (from kernel-2.6.27.9-159.fc10) to see if that makes any difference. -- Rex -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: X locks up after a random time
On Saturday 03 January 2009 01:36:01 Rex Dieter wrote: > Marko Vojinovic wrote: > > Ok, this is a Fujitsu Siemens Esprimo U9200, with Intel graphics, F10 > > 64bit, updated last week. KDE desktop, compiz and all, but I believe it > > is not related. > > Interesting, I'd noticed the same thing over the past few days... hmm (Dell > Latitude D620 here). > > In the meantime, I've tried backing down to using kernel-2.6.27.7-134.fc10 > (from kernel-2.6.27.9-159.fc10) to see if that makes any difference. > This Mandriva laptop has a variation on that. With Desktop Effects on I get random freezes, but I also get times when the mouse can move the cursor around, but neither mouse-clicks or keyboard usage is registered. This has happened throughout, so I don't think that it's kernel-specific, but I do think that it is probably related to what you are both seeing. Anne signature.asc Description: This is a digitally signed message part. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: X locks up after a random time
On Sat, Jan 3, 2009 at 8:25 AM, Anne Wilson wrote: > On Saturday 03 January 2009 01:36:01 Rex Dieter wrote: > > Marko Vojinovic wrote: > > > Ok, this is a Fujitsu Siemens Esprimo U9200, with Intel graphics, F10 > > > 64bit, updated last week. KDE desktop, compiz and all, but I believe it > > > is not related. > > > > Interesting, I'd noticed the same thing over the past few days... hmm > (Dell > > Latitude D620 here). > > > > In the meantime, I've tried backing down to using > kernel-2.6.27.7-134.fc10 > > (from kernel-2.6.27.9-159.fc10) to see if that makes any difference. > > > This Mandriva laptop has a variation on that. With Desktop Effects on I > get > random freezes, but I also get times when the mouse can move the cursor > around, but neither mouse-clicks or keyboard usage is registered. This has > happened throughout, so I don't think that it's kernel-specific, but I do > think that it is probably related to what you are both seeing. > > I was using kernel 134 until yesterday. Therefore it is not because of kernel159. The problem is the new Intel acceleration method that is being used by F10/X (EXA). In fact, I just wanted a transparent terminal in KDE. I do not need all the "Desktop Effects" stuff. I also notice, when I use mplayer with the SLD driver, the video (I mean a movie) stops all the time. Then I changed to opengl, and the window gets garbaged when maximizing/minimizing. Using the ol' good Xv is the only option that works fine for me. For the first time in my life I am not using a nvidia card with the closed driver. I think I am just being unlucky. If a fix does not come soon, I will install one of my nvidia 7600 or 8500 cards, and forget about the Intel onboard card graphics once for all. -- Paulo Roma Cavalcanti LCG - UFRJ -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: X locks up after a random time
Anne Wilson wrote: > This Mandriva laptop has a variation on that. With Desktop Effects on I > get random freezes, but I also get times when the mouse can move the > cursor > around, but neither mouse-clicks or keyboard usage is registered. This > has happened throughout, so I don't think that it's kernel-specific, but I > do think that it is probably related to what you are both seeing. > I think this is the bug I reported on both bugzilla.redhat and bugs.kde. I have never tested with gnome or compiz, only with kde using opengl and xrender. It happens both times and I have Intel graphics on both computers. In my case, I get the "too many open files in system" message on one of the consoles when this happens. I am unable to open programs, unable to save files (hence lose my work), etc, but the mouse and keyboard don't fail, so I can kill X and log back in, but the problem seems to recur sooner than if I had rebooted. My guess is that this is some kind of Intel driver problem, possibly not interacting well with either X or with Desktop Effects. Nevertheless, I will not give up on Intel and do not intend to migrate (regress) back to a vendor that doesn't provide open drivers. I can live without desktop Effects for a while until this gets cleared up (admittedly, it has been a year already that I have monitored the problem, and progress is slow, but the problem has evolved slightly, as formerly not even the mouse and keyboard worked, but since about the fall, it is no longer necessary to pull the plug on the computer to reboot). -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: X locks up after a random time
These are the bugs I reported: https://bugzilla.redhat.com/show_bug.cgi?id=468110 http://bugs.kde.org/show_bug.cgi?id=179081 -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: X locks up after a random time
On Saturday 03 January 2009 17:17:47 Petrus de Calguarium wrote: > These are the bugs I reported: > > https://bugzilla.redhat.com/show_bug.cgi?id=468110 > http://bugs.kde.org/show_bug.cgi?id=179081 Neither of those sound like my problem - I just suddenly discover that my mouse and keyboard are not being read. Sometimes gkrellm shows a total freeze, but I'm fairly sure that there have been other times when normal activity has been occurring behind the scenes. Either way, despite waiting to see whether the problem goes away, the only way out is to power off. This is an ATi X600 graphics card. At first I had the OSS ati driver, then I added flgrx in case I was trying to do something that really needed acceleration. Not being a gamer, I have little experience of using graphics acceleration. Basically, the effects I was trying to use were Dim Inactive Windows and Cover Switch. The system is rock-solid if I don't enable Desktop Effects. Anne signature.asc Description: This is a digitally signed message part. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: X locks up after a random time
On Saturday 03 January 2009 02:36, Rex Dieter wrote: > Marko Vojinovic wrote: > > Ok, this is a Fujitsu Siemens Esprimo U9200, with Intel graphics, F10 > > 64bit, updated last week. KDE desktop, compiz and all, but I believe it > > is not related. > > In the meantime, I've tried backing down to using kernel-2.6.27.7-134.fc10 > (from kernel-2.6.27.9-159.fc10) to see if that makes any difference. I have been having this issue since FC10 came out, throughout several kernel updates, so I believe this is not kernel related. However, F9 has been working on the same hardware and KDE/compiz without hiccups, but this was 32bit install. Since F10 I went 64bit, and I wonder if that might be related... Best, :-) Marko -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: X locks up after a random time
On Saturday 03 January 2009 02:07, Paulo Cavalcanti wrote: > On Fri, Jan 2, 2009 at 10:36 PM, Marko Vojinovic wrote: > > Ok, this is a Fujitsu Siemens Esprimo U9200, with Intel graphics, F10 > > 64bit, > > updated last week. KDE desktop, compiz and all, but I believe it is not > > related. > > > > The symptom: system boots up regularly, I do regular work, and after a > > random > > amount of time, X freezes. If compiz is on, all I can do is move the > > mouse pointer. If compiz is off, even the mouse pointer is frozen. The OS > > itself is > > not, I can ssh from a remote machine and read logs. This is not > > reproducible, > > it happens too randomly and I can only sit and wait for it to happen. > > However, it is extremely annoying, since it has a tendency to freeze when > > I'm > > in the middle of some work in progress. > > You can try using > > Option "AccelMethod" "XAA" > > in your xorg.conf to see if there is any difference (I have never tried). What was the command to generate xorg.conf? I saw it here in some post some time ago, but can't find it now... Also, in which Section of xorg.conf shoud I put the above option? Thanks for helping! :-) Marko -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: X locks up after a random time
On Saturday 03 January 2009 11:25, Anne Wilson wrote: > On Saturday 03 January 2009 01:36:01 Rex Dieter wrote: > > Marko Vojinovic wrote: > > > Ok, this is a Fujitsu Siemens Esprimo U9200, with Intel graphics, F10 > > > 64bit, updated last week. KDE desktop, compiz and all, but I believe it > > > is not related. > > > > Interesting, I'd noticed the same thing over the past few days... hmm > > (Dell Latitude D620 here). > > > > In the meantime, I've tried backing down to using > > kernel-2.6.27.7-134.fc10 (from kernel-2.6.27.9-159.fc10) to see if that > > makes any difference. > > This Mandriva laptop has a variation on that. With Desktop Effects on I > get random freezes, but I also get times when the mouse can move the cursor > around, but neither mouse-clicks or keyboard usage is registered. This has > happened throughout, so I don't think that it's kernel-specific, but I do > think that it is probably related to what you are both seeing. Can you verify the /var/log/Xorg.0.log complaining about infinite loops on that machine (that is, when a lockup occours, using ssh from another machine)? If yes, then I'd bet it is the same issue, and in that case it is also not Fedora-specific, but a general problem. I kinda have a feeling that this is a problem with the interaction between X and Intel drivers (the EXA vs XAA thing or whatever), or possibly a bug in the Intel driver that shows up only in 64bit version. Best, :-) Marko -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: X locks up after a random time
--- On Sat, 1/3/09, Marko Vojinovic wrote: > > You can try using > > > > Option "AccelMethod" "XAA" > > > > in your xorg.conf to see if there is any difference (I > have never tried). > > What was the command to generate xorg.conf? I saw it here > in some post some > time ago, but can't find it now... boot into level 3, login as root # Xorg -configure creates a file /root/xorg.conf.new test it with directions given something like X -??? then if it works, posts mouse pointer in about middle of screen, copy it over to /etc/X11 directory # cp xorg.conf.new /etc/X11/xorg.conf > > Also, in which Section of xorg.conf shoud I put the above > option? This I am not sure, but maybe in the section previous to Monitor section ? > > Thanks for helping! :-) > Marko > > > > -- Regards, Antonio -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: X locks up after a random time
On Sat, Jan 3, 2009 at 7:50 PM, Antonio Olivares wrote: > > > > --- On Sat, 1/3/09, Marko Vojinovic wrote: > > > > You can try using > > > > > > Option "AccelMethod" "XAA" > > > > > > in your xorg.conf to see if there is any difference (I > > have never tried). > > > > What was the command to generate xorg.conf? I saw it here > > in some post some > > time ago, but can't find it now... > boot into level 3, login as root > # Xorg -configure > creates a file /root/xorg.conf.new > test it with directions given something like X -??? > then if it works, posts mouse pointer in about middle of screen, copy it > over to /etc/X11 directory > # cp xorg.conf.new /etc/X11/xorg.conf > > > > Also, in which Section of xorg.conf shoud I put the above > > option? > This I am not sure, but maybe in the section previous to Monitor section ? > > > Section "Device" Identifier "Videocard0" Driver"intel" Option "AccelMethod" "XAA" EndSection -- Paulo Roma Cavalcanti LCG - UFRJ -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: X locks up after a random time
Anne Wilson wrote: > This is an ATi X600 graphics card. At first I had the OSS ati driver, > then I added flgrx in case I was trying to do something that really needed > acceleration. Not being a gamer, I have little experience of using > graphics acceleration. Then what you're seeing is most likely a bug in the fglrx driver. I'd suggest reinstalling your GNU/Linux to be sure to get rid of all traces of it. The X600 actually has working acceleration in the Free Software drivers. Kevin Kofler -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: X locks up after a random time
On Saturday 03 January 2009 23:10:30 Kevin Kofler wrote: > Anne Wilson wrote: > > This is an ATi X600 graphics card. At first I had the OSS ati driver, > > then I added flgrx in case I was trying to do something that really > > needed acceleration. Not being a gamer, I have little experience of > > using graphics acceleration. > > Then what you're seeing is most likely a bug in the fglrx driver. I'd > suggest reinstalling your GNU/Linux to be sure to get rid of all traces of > it. > > The X600 actually has working acceleration in the Free Software drivers. > Just one problem with that, Kevin. I installed the fglrx driver *because* I was seeing this problem. IOW, it was happening with the free driver only installed. Anne signature.asc Description: This is a digitally signed message part. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: X locks up after a random time
On Saturday 03 January 2009 23:10:30 Kevin Kofler wrote: > Anne Wilson wrote: > > This is an ATi X600 graphics card. At first I had the OSS ati driver, > > then I added flgrx in case I was trying to do something that really > > needed acceleration. Not being a gamer, I have little experience of > > using graphics acceleration. > > Then what you're seeing is most likely a bug in the fglrx driver. I'd > suggest reinstalling your GNU/Linux to be sure to get rid of all traces of > it. > > The X600 actually has working acceleration in the Free Software drivers. > I should also mention that my F9 box shows the same problem. I can't check what video card that uses until later today, but again, I use only the free driver. Anne signature.asc Description: This is a digitally signed message part. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: X locks up after a random time
On Sun, Jan 4, 2009 at 12:28 AM, Anne Wilson wrote: > On Saturday 03 January 2009 23:10:30 Kevin Kofler wrote: >> Anne Wilson wrote: >> > This is an ATi X600 graphics card. At first I had the OSS ati driver, >> > then I added flgrx in case I was trying to do something that really >> > needed acceleration. Not being a gamer, I have little experience of >> > using graphics acceleration. >> >> Then what you're seeing is most likely a bug in the fglrx driver. I'd >> suggest reinstalling your GNU/Linux to be sure to get rid of all traces of >> it. >> >> The X600 actually has working acceleration in the Free Software drivers. >> > I should also mention that my F9 box shows the same problem. I can't check > what video card that uses until later today, but again, I use only the free > driver. > I have a T60 laptop with an X1400 ATI card and use the radeon driver with a fully updated F10 system. X server was also randomly crashing. I submitted a bug against the X server/radeon driver at https://bugs.freedesktop.org/show_bug.cgi?id=19300. Was told it is likely a kernel modesetting problem. Setting a nomodeset option for the kernel boot seems to have solved the crash problem (at least the machine has been crash-free longer than usual). As an added bonus, resume after suspend now works correctly (but resume after hibernate still doesn't). I ran F9 on an older Thinkpad T41 with an ATI chip (don't remember the model), and never had any trouble - everything worked, including suspend and hibernate. The F9 live CD works well in the T60 laptop, including suspend and hibernate - so much so that I considered downgrading to F9. Peter -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: X locks up after a random time
On Saturday 03 January 2009 21:18:58 Marko Vojinovic wrote: > On Saturday 03 January 2009 11:25, Anne Wilson wrote: > > On Saturday 03 January 2009 01:36:01 Rex Dieter wrote: > > > Marko Vojinovic wrote: > > > > Ok, this is a Fujitsu Siemens Esprimo U9200, with Intel graphics, F10 > > > > 64bit, updated last week. KDE desktop, compiz and all, but I believe > > > > it is not related. > > > > > > Interesting, I'd noticed the same thing over the past few days... hmm > > > (Dell Latitude D620 here). > > > > > > In the meantime, I've tried backing down to using > > > kernel-2.6.27.7-134.fc10 (from kernel-2.6.27.9-159.fc10) to see if that > > > makes any difference. > > > > This Mandriva laptop has a variation on that. With Desktop Effects on I > > get random freezes, but I also get times when the mouse can move the > > cursor around, but neither mouse-clicks or keyboard usage is registered. > > This has happened throughout, so I don't think that it's kernel-specific, > > but I do think that it is probably related to what you are both seeing. > > Can you verify the /var/log/Xorg.0.log complaining about infinite loops on > that machine (that is, when a lockup occours, using ssh from another > machine)? > > If yes, then I'd bet it is the same issue, and in that case it is also not > Fedora-specific, but a general problem. > > I kinda have a feeling that this is a problem with the interaction between > X and Intel drivers (the EXA vs XAA thing or whatever), or possibly a bug > in the Intel driver that shows up only in 64bit version. > OK - I've enabled Desktop Effects, but selected only Dim Inactive Windows. I'll see how stable this is. If it's still stable later today I'll add a Switcher to them. I will then try to contact the laptop by ssh if a freeze occurs. I'll report back. Anne signature.asc Description: This is a digitally signed message part. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: X locks up after a random time
On Saturday 03 January 2009 21:18:58 Marko Vojinovic wrote: > On Saturday 03 January 2009 11:25, Anne Wilson wrote: > > On Saturday 03 January 2009 01:36:01 Rex Dieter wrote: > > > Marko Vojinovic wrote: > > > > Ok, this is a Fujitsu Siemens Esprimo U9200, with Intel graphics, F10 > > > > 64bit, updated last week. KDE desktop, compiz and all, but I believe > > > > it is not related. > > > > > > Interesting, I'd noticed the same thing over the past few days... hmm > > > (Dell Latitude D620 here). > > > > > > In the meantime, I've tried backing down to using > > > kernel-2.6.27.7-134.fc10 (from kernel-2.6.27.9-159.fc10) to see if that > > > makes any difference. > > > > This Mandriva laptop has a variation on that. With Desktop Effects on I > > get random freezes, but I also get times when the mouse can move the > > cursor around, but neither mouse-clicks or keyboard usage is registered. > > This has happened throughout, so I don't think that it's kernel-specific, > > but I do think that it is probably related to what you are both seeing. > > Can you verify the /var/log/Xorg.0.log complaining about infinite loops on > that machine (that is, when a lockup occours, using ssh from another > machine)? > > If yes, then I'd bet it is the same issue, and in that case it is also not > Fedora-specific, but a general problem. > > I kinda have a feeling that this is a problem with the interaction between > X and Intel drivers (the EXA vs XAA thing or whatever), or possibly a bug > in the Intel driver that shows up only in 64bit version. > Didn't manage to ssh, but I did check the /var/log/Xorg.0.log.old - same result :-) You are quite correct there are dozens of these: [mi] EQ overflowing. The server is probably stuck in an infinite loop. [mi] mieqEnequeue: out-of-order valuator event; dropping. As I told Kevin, this Radeon Mobility X600 showed this problem before I installed flgrx, so it does concern the free driver. I also checked the F9 box that has the same problem. The card there is NV34 (GeForce FX 5500), again using only the free driver. That box was just set up for testing and learning KDE4, so I don't use it much. If you want me to try to capture the same info from /var/log/Xorg.0.log on that box I'll try to get a session there later today, with Desktop Effects enabled. Anne signature.asc Description: This is a digitally signed message part. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: X locks up after a random time
See Als : https://bugzilla.redhat.com/show_bug.cgi?id=464866 : Xorg lockup with i945: "EQ overflowing. The server is probably stuck in an infinite loop." https://bugs.freedesktop.org/show_bug.cgi?id=14633 X freezes with Composite and Mouse Wheel, mouse moves, no... (with Nvidia Proprietary Driver) 2009-01-03 (토), 01:36 +0100, Marko Vojinovic 쓰시길: > Ok, this is a Fujitsu Siemens Esprimo U9200, with Intel graphics, F10 64bit, > updated last week. KDE desktop, compiz and all, but I believe it is not > related. > > The symptom: system boots up regularly, I do regular work, and after a random > amount of time, X freezes. If compiz is on, all I can do is move the mouse > pointer. If compiz is off, even the mouse pointer is frozen. The OS itself is > not, I can ssh from a remote machine and read logs. This is not reproducible, > it happens too randomly and I can only sit and wait for it to happen. > However, it is extremely annoying, since it has a tendency to freeze when I'm > in the middle of some work in progress. > > If I log in remotely and kill -9 the X process, the whole machine locks up > and > I can only power-cycle it. Don't know a way to restart X short of rebooting, > keyboard doesn't respond to ctrl-alt-backspace or anything else. > > So far, dmesg and /var/log/messages do not show anything related or even > suspicious (afaics), while /var/log/Xorg.0.log shows this at the end: > > = > [snip most of the regular log of a working X server] > > (II) intel(0): EDID for output TMDS-1 > (II) intel(0): EDID for output TV > [mi] EQ overflowing. The server is probably stuck in an infinite loop. > > Backtrace: > 0: /usr/bin/X(xorg_backtrace+0x26) [0x4e7a26] > 1: /usr/bin/X(mieqEnqueue+0x291) [0x4c8591] > 2: /usr/bin/X(xf86PostMotionEventP+0xc4) [0x491494] > 3: /usr/bin/X(xf86PostMotionEvent+0xa9) [0x491669] > 4: /usr/lib64/xorg/modules/input//evdev_drv.so [0x7feeeaf3e126] > 5: /usr/bin/X [0x47a765] > 6: /usr/bin/X [0x46b307] > 7: /lib64/libc.so.6 [0x3522232f90] > 8: /lib64/libc.so.6(ioctl+0x7) [0x35222de037] > 9: /usr/lib64/libdrm.so.2 [0x7feefd045023] > 10: /usr/lib64/libdrm.so.2(drmCommandNone+0x16) [0x7feefd045326] > 11: /usr/lib64/xorg/modules/drivers//intel_drv.so [0x7feefcdd0fc8] > 12: /usr/bin/X [0x51cdb9] > 13: /usr/bin/X [0x4f7311] > 14: /usr/bin/X(BlockHandler+0x50) [0x44a320] > 15: /usr/bin/X(WaitForSomething+0x161) [0x4e4eb1] > 16: /usr/bin/X(Dispatch+0x7f) [0x4465ef] > 17: /usr/bin/X(main+0x45d) [0x42cd1d] > 18: /lib64/libc.so.6(__libc_start_main+0xe6) [0x352221e576] > 19: /usr/bin/X [0x42c0f9] > [mi] mieqEnequeue: out-of-order valuator event; dropping. > [mi] EQ overflowing. The server is probably stuck in an infinite loop. > > [the last two lines repeat a lot of times] > = > > So if the server is really in an infinite loop, then something so very Not > Good is happening. Now, given that these are Intel open-source drivers > driving my graphics card here, I have the following questions: > > 1) What does the [mi] stand for here? Can anyone decypher the backtrace for > me? (I don't mind reading a "too technical" answer) > 2) How can I further diagnose the problem and help fixing it? > 3) In order to be efficient in diagnosing, does anyone know how to trigger > the > lockup on purpose? > 4) This has been happening since I installed F10 on this machine --- has > anyone spotted the problem already? Is there a known bugzilla report that I > can add to? > 5) Is there a workaround until a fix comes? > 6) Can I somehow restart the X server from a remote console (without > rebooting > the whole machine) to recover clean from this? > 7) F10 is out for a while now, how come a bug such as this (X in infinite > loop) has not been fixed already? I mean, many people here bragg about the > open source drivers being better then closed source when it comes to fixing > broken things, so why is an issue such as this still present? > // ok, this is a rant, I know, but I really am frustrated by this // > > Oh yes, lspci -v says this: > > 00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 > Integrated Graphics Controller (rev 03) (prog-if 00 [VGA controller]) > Subsystem: Fujitsu Siemens Computers Device 110f > Flags: bus master, fast devsel, latency 0, IRQ 16 > Memory at fc00 (64-bit, non-prefetchable) [size=1M] > Memory at d000 (64-bit, prefetchable) [size=256M] > I/O ports at 18f8 [size=8] > Capabilities: [90] Message Signalled Interrupts: Mask- 64bit- > Count=1/1 Enable- > Capabilities: [d0] Power Management version 3 > Kernel modules: intelfb > > 00:02.1 Display controller: Intel Corporation Mobile GM965/GL960 Integrated > Graphics Controller (rev 03) > Subsystem: Fujitsu Siemens Computers Device 110f > Flags: bus master, fast devsel, latency 0 > Memory at fc10 (64-bit, non-prefetchable) [disabled] [size=1M] > Capabil
Re: X locks up after a random time
On Monday 05 January 2009 09:31:32 Paulo Cavalcanti wrote: > On Mon, Jan 5, 2009 at 2:06 AM, sangu wrote: > > See Als : > > https://bugzilla.redhat.com/show_bug.cgi?id=464866 : Xorg lockup with > > i945: "EQ overflowing. The server is probably stuck in an infinite > > loop." > > Hmm - I wonder if it's worth adding that it's happening on an ATi video as well? > > https://bugs.freedesktop.org/show_bug.cgi?id=14633 X freezes with > > Composite and Mouse Wheel, mouse moves, no... (with Nvidia Proprietary > > Driver) > > > Impressive. It seems that everybody knows about this problem since before > the F10 release. Therefore, it is a plain case of "broken edge". And will be fixed as soon as possible (November 11th). Methinks the priority could do with raising :-) It may not be a release-stopper, but it certainly gives a lot of users a lot of trouble. Anne signature.asc Description: This is a digitally signed message part. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: X locks up after a random time
On Mon, Jan 5, 2009 at 2:06 AM, sangu wrote: > See Als : > https://bugzilla.redhat.com/show_bug.cgi?id=464866 : Xorg lockup with > i945: "EQ overflowing. The server is probably stuck in an infinite > loop." > > https://bugs.freedesktop.org/show_bug.cgi?id=14633 X freezes with > Composite and Mouse Wheel, mouse moves, no... (with Nvidia Proprietary > Driver) > > 2009-01-03 (토), 01:36 +0100, Marko Vojinovic 쓰시길: > > Ok, this is a Fujitsu Siemens Esprimo U9200, with Intel graphics, F10 > 64bit, > > updated last week. KDE desktop, compiz and all, but I believe it is not > > related. > > > > The symptom: system boots up regularly, I do regular work, and after a > random > > amount of time, X freezes. If compiz is on, all I can do is move the > mouse > > pointer. If compiz is off, even the mouse pointer is frozen. The OS > itself is > > not, I can ssh from a remote machine and read logs. This is not > reproducible, > > it happens too randomly and I can only sit and wait for it to happen. > > However, it is extremely annoying, since it has a tendency to freeze when > I'm > > in the middle of some work in progress. > > > > If I log in remotely and kill -9 the X process, the whole machine locks > up and > > I can only power-cycle it. Don't know a way to restart X short of > rebooting, > > keyboard doesn't respond to ctrl-alt-backspace or anything else. > > > > So far, dmesg and /var/log/messages do not show anything related or even > > suspicious (afaics), while /var/log/Xorg.0.log shows this at the end: > > > > = > > [snip most of the regular log of a working X server] > > > > (II) intel(0): EDID for output TMDS-1 > > (II) intel(0): EDID for output TV > > [mi] EQ overflowing. The server is probably stuck in an infinite loop. > > > > Backtrace: > > 0: /usr/bin/X(xorg_backtrace+0x26) [0x4e7a26] > > 1: /usr/bin/X(mieqEnqueue+0x291) [0x4c8591] > > 2: /usr/bin/X(xf86PostMotionEventP+0xc4) [0x491494] > > 3: /usr/bin/X(xf86PostMotionEvent+0xa9) [0x491669] > > 4: /usr/lib64/xorg/modules/input//evdev_drv.so [0x7feeeaf3e126] > > 5: /usr/bin/X [0x47a765] > > 6: /usr/bin/X [0x46b307] > > 7: /lib64/libc.so.6 [0x3522232f90] > > 8: /lib64/libc.so.6(ioctl+0x7) [0x35222de037] > > 9: /usr/lib64/libdrm.so.2 [0x7feefd045023] > > 10: /usr/lib64/libdrm.so.2(drmCommandNone+0x16) [0x7feefd045326] > > 11: /usr/lib64/xorg/modules/drivers//intel_drv.so [0x7feefcdd0fc8] > > 12: /usr/bin/X [0x51cdb9] > > 13: /usr/bin/X [0x4f7311] > > 14: /usr/bin/X(BlockHandler+0x50) [0x44a320] > > 15: /usr/bin/X(WaitForSomething+0x161) [0x4e4eb1] > > 16: /usr/bin/X(Dispatch+0x7f) [0x4465ef] > > 17: /usr/bin/X(main+0x45d) [0x42cd1d] > > 18: /lib64/libc.so.6(__libc_start_main+0xe6) [0x352221e576] > > 19: /usr/bin/X [0x42c0f9] > > [mi] mieqEnequeue: out-of-order valuator event; dropping. > > [mi] EQ overflowing. The server is probably stuck in an infinite loop. > > > > [the last two lines repeat a lot of times] > > = > > > > So if the server is really in an infinite loop, then something so very > Not > > Good is happening. Now, given that these are Intel open-source drivers > > driving my graphics card here, I have the following questions: > > > > 1) What does the [mi] stand for here? Can anyone decypher the backtrace > for > > me? (I don't mind reading a "too technical" answer) > > 2) How can I further diagnose the problem and help fixing it? > > 3) In order to be efficient in diagnosing, does anyone know how to > trigger the > > lockup on purpose? > > 4) This has been happening since I installed F10 on this machine --- has > > anyone spotted the problem already? Is there a known bugzilla report that > I > > can add to? > > 5) Is there a workaround until a fix comes? > > 6) Can I somehow restart the X server from a remote console (without > rebooting > > the whole machine) to recover clean from this? > > 7) F10 is out for a while now, how come a bug such as this (X in infinite > > loop) has not been fixed already? I mean, many people here bragg about > the > > open source drivers being better then closed source when it comes to > fixing > > broken things, so why is an issue such as this still present? > > // ok, this is a rant, I know, but I really am frustrated by this // > > > > Oh yes, lspci -v says this: > > > > 00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 > > Integrated Graphics Controller (rev 03) (prog-if 00 [VGA controller]) > > Subsystem: Fujitsu Siemens Computers Device 110f > > Flags: bus master, fast devsel, latency 0, IRQ 16 > > Memory at fc00 (64-bit, non-prefetchable) [size=1M] > > Memory at d000 (64-bit, prefetchable) [size=256M] > > I/O ports at 18f8 [size=8] > > Capabilities: [90] Message Signalled Interrupts: Mask- 64bit- > > Count=1/1 Enable- > > Capabilities: [d0] Power Management version 3 > > Kernel modules: intelfb > > > > 00:02.1 Display controller: Intel Corporation Mobile GM965/GL960 > Integrated > > Gr
Re: X locks up after a random time
On Monday 05 January 2009 09:31:32 Paulo Cavalcanti wrote: > Impressive. It seems that everybody knows about this problem since before > the F10 release. Therefore, it is a plain case of "broken edge". Paulo, someone on the kde list told me to use EXA acceleration, telling me to add this >> Section "Device" >>Option "UseAtomBIOS" "true" >>Option "AccelMethod" "EXA" >># ... >> EndSection >> >> This works with both the radeon as well as the radeonhd driver but only >> with cards up to an X1950. HD2xxx and above aren't supported yet. He was unsure, and I couldn't ascertain whether my elderly X600 could 'UseAtomBIOS' so I commented that line out. I've using the laptop for 5 hours now with Desktop Effects enabled and without a freeze. If you or anyone else reading is using an ATi card this is worth a try. Perhaps there are similar AccelMethod entries for Intel cards that deal with the problem? Anne signature.asc Description: This is a digitally signed message part. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
