Bug 473759

Sorry, at "Actual Results:" I meant X became frozen, so I needed to cold restart the machine. This is why I set the "Severity" urgent.

Maybe I have a similar problem like this https://bugzilla.redhat.com/show_bug.cgi?id=464866
I have seen the message "[mi] EQ overflowing. The server is probably stuck in an infinite loop." in the X log (the logs got overwritten).
In a few days I will try to provide more details by reproducing the fault.

Andras, please, file a separate bug for your issue. Thank you.

----------------------

Thanks for the bug report.  We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue.

Please attach your X server config file (/etc/X11/xorg.conf, if available) and X server log file (/var/log/Xorg.*.log) to the bug report as individual uncompressed file attachments using the bugzilla file attachment link below.

Could you please also try to run without any /etc/X11/xorg.conf (if you have one) whatsoever and let X11 autodetect your display and video card? Attach to this bug /var/log/Xorg.0.log from this attempt as well, please.

We will review this issue again once you've had a chance to attach this information.

Thanks in advance.

Screen: built-in LCD panel. (I will use single headed X for these tests with the built-in LCD.)

Using nomodeset, with own Xorg.conf is stable.
Note: cc. every other startup the screen flickers (there are horizontal vibrating lines on the screen; when the screen is dark this is not visible). Switching to text mode (CTRL-ALT-Fx) and back resolves this issue.

Using nomodeset, with autogenerate Xorg.conf is also seems to be stable.

I will attach the logs right now.

Let me know, if you need tests / logs with the rhgb kernel option.

Created attachment 325775 [details]
own xorg.conf

Created attachment 325776 [details]
Xorg.0.log

There will be no Xorg.0.log.old (would be the same as this file / overwritten).

Created attachment 325777 [details]
Xorg.1.log

Created attachment 325778 [details]
Xorg.1.log.old

Created attachment 325779 [details]
Xorg.2.log

Created attachment 325780 [details]
Xorg.2.log.old

Created attachment 325781 [details]
Xorg.3.log

Created attachment 325782 [details]
Xorg.3.log.old

Created attachment 325783 [details]
Xorg.4.log

Created attachment 325784 [details]
Xorg.4.log.old

Created attachment 325785 [details]
Xorg.5.log

Created attachment 325786 [details]
Xorg.5.log.old

Created attachment 325787 [details]
Xorg.6.log

Created attachment 325788 [details]
Xorg.6.log.old

Created attachment 325789 [details]
Xorg.7.log

Created attachment 325791 [details]
Xorg.7.log.old

Created attachment 325793 [details]
Xorg.8.log

# ls -ltr /var/log/Xorg.[0-9].log*
-rw-r--r-- 1 root root  6511 2008-07-12 10:05 /var/log/Xorg.7.log.old
-rw-r--r-- 1 root root  6511 2008-07-12 10:05 /var/log/Xorg.6.log.old
-rw-r--r-- 1 root root  6511 2008-07-13 11:47 /var/log/Xorg.8.log
-rw-r--r-- 1 root root  6511 2008-07-13 11:47 /var/log/Xorg.7.log
-rw-r--r-- 1 root root  6511 2008-07-13 11:47 /var/log/Xorg.6.log
-rw-r--r-- 1 root root 24859 2008-11-16 10:22 /var/log/Xorg.1.log.old
-rw-r--r-- 1 root root 24859 2008-11-16 10:22 /var/log/Xorg.5.log.old
-rw-r--r-- 1 root root 24859 2008-11-16 10:22 /var/log/Xorg.4.log.old
-rw-r--r-- 1 root root 24859 2008-11-16 10:22 /var/log/Xorg.3.log.old
-rw-r--r-- 1 root root 24859 2008-11-16 10:22 /var/log/Xorg.2.log.old
-rw-r--r-- 1 root root 24859 2008-11-16 10:22 /var/log/Xorg.3.log
-rw-r--r-- 1 root root 24859 2008-11-16 10:22 /var/log/Xorg.2.log
-rw-r--r-- 1 root root 24859 2008-11-16 10:22 /var/log/Xorg.1.log
-rw-r--r-- 1 root root 24859 2008-11-16 10:22 /var/log/Xorg.5.log
-rw-r--r-- 1 root root 24859 2008-11-16 10:22 /var/log/Xorg.4.log
-rw-r--r-- 1 root root 59831 2008-12-05 04:42 /var/log/Xorg.0.log.old
-rw-r--r-- 1 root root 74200 2008-12-05 04:44 /var/log/Xorg.0.log

# grep -i overflow /var/log/Xorg.[0-9].log*
[empty]
Somehow, those logs, which contained the "EQ overflowing" got overwritten.

Created attachment 325796 [details]
Xorg.0.log with autogenerated xorg.conf

With no xorg.conf the screen freeze (X hang) still happens.
See, the attached Xorg log, which now has some traces.

Created attachment 325880 [details]
no xorg.conf X still hangs after a while

Created attachment 325881 [details]
recent Xorg.0.log

This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '10'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 10's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 10 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.