FC3test1: X / display hangs after overnight inactivity

[Jim Cornette]

Banibrata Dutta wrote:
> Hi,
> 
> Anybody has noticed the problem of Xserver (or display driver) hanging
> in FC3-test1 ? I've filed a bug in bugzilla # 132968 (
> http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=132968 ).
> 
> pciscan reports the display adaptor as:
> pci bus 0x000 cardnum 0x02 function 0x00: vendor 0x8086 device 0x2572
>  Intel Corp. 82865G Integrated Graphics Device
> 
> to summarize here's the problem:
>  if i leave the Xserver running (WM being either GNOME / KDE based)
> overnight, 9/10 time i'd find that the display as hung, i.e. a thin
> raster band (in 16/256 colors) at the bottom of the screen. in this
> state CTRL-BACKSPACE, ALT-CTRL-Fn or even ALT-CTRL-DEL doesn't work,
> basically i cannot do anything using the console keyboard. if i telnet
> into this system from some other system, i am allowed in, after which
> if i try killing all X processes including gdm etc., the status
> doesn't change, i.e. the raster band stays and keyboard remains
> non-responsive. i've tried switching to runlevel 3, stopping X and
> going back to runlevel 5, without any good. only option left at this
> point is to reboot the system, or poweroff & poweron.
> 
> thanks & regards,
> banibrata dutta.
> 

Oh No! not both the cards now! (815 and 865G)

Anyway, I had this problem before the CVS releases and presently had 
tried running X overnight and with screensavers running and cycling 
every few ninutes. It worked on the one back from the present version of 
X. I did not try any version post fc3t2 installation CDs though.

If this is the same error that I experienced with the pre-CVS builds, X 
process dies out and leaves whatever mess caused the crash on the 
display. It is possible to ctl-alt-Fn to a terminal and perform tasks 
without the aid of a display. You should also be able to ssh into the 
box and check logs, stop services, etc.

If interested in screensavers that might tickle the error into 
repeatability, try noof and StarWars. They triggered the previous errors 
immediately.

To get the display back to normal, all I found worked was a system reset.

Jim
-- 
You had mail, but the super-user read it, and deleted it!