FC3test1: X / display hangs after overnight inactivity

Kyrre Ness Sjobak kyrre at solution-forge.net
Fri Oct 1 12:58:00 UTC 2004


Hmm.. i have seen a similar problem on FC2 (nvidia geforce 2 MX pci).
Somtimes (_very_ rarely) my display seems to just freeze. I can still
svitch to vt1 and hit control-alt-delete, but whatever app was on screen
when it froze, is stuck until the big red "COMPAQ" logo of the BIOS
shows up (not the VGA bios, that is invisible).

Also saw it with fc1 and a vodoo 3 card - but then it was more likely to
turn black or freze with static (like if you have switched to a vt and
then back again) - sometimes a svitch to a vt would fix it, sometimes i
had to shutdown blindly, sometimes ssh worked, and once the whole box
hanged firmly (so that i had to pull its plug). All those where PCI
cards.

Nothing that screams "hardware malfuncion"?

While we are at it - why are "select screensavers randomly" selected by
default? And why also all the GL-ones? Having a standard, not
resource-eating (not everybody has a GL-accelerated card/drivers, and
what about laptops? High CPU usage kills batterytime... Or even
thin-clients? Ever saw a GL screensaver running on a thin client? Ever
saw cpu-load of a thin-client-server which runs 10 GL screensavers at
once and trying to send them over the network?).

How many here agrees that having one boring default screensaver would be
the best?

Kyrre

fre, 01.10.2004 kl. 11.35 skrev Banibrata Dutta:
> 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.




More information about the fedora-test-list mailing list