In LTSP 4.2.1, the i810 X.org 6.9.0 crashes every time the user visits
http://nadaguide.com (and a few other sites) in Firefox 1.5 with
the latest Flash. As the page loads, the screen goes black with colored
lines. Then, the console shows up, but the keyboard is completely frozen.
The X client is Fedora Core 5. Only certain i810 terminals are affected; they
* Dell L500c P3-500Mhz with 180MB RAM
* HP Pavilion 4535 P2-400MHz with 192MB RAM
Resolution is just 1024x800.
Here's the X.org log file (before the crash, since the system freezes) from the
I have already tried setting X_VIDEORAM = 4096 (in lts.conf) and activating 64MB
network swap, but nothing helps.
The problem persists. Reducing Firefox memory usage through about:config seemed to help with some sites, but other sites such as http://www.sat-gps-locate.com/ still cause crashes.
Sorry, the http://www.sat-gps-locate.com/ was fixed by changing the X_VIDEORAM = 8192, but nevertheless, X.org should be *bulletproof* with default settings.
BTW, I am now running Fedora Core 6, Firefox 2, and Flash 7 r69.
I see this bug in x86_64 FC6 running FF 22.214.171.124.i386 when loading up overstock.com. More information:
Build Identifier: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:126.96.36.199)
Gecko/20070313 Fedora/188.8.131.52-5.fc6 Firefox/184.108.40.206
Using the i810 XServer (diskless Dell Optiplex GX110) and loading a
console. If I switch to virtual terminal while rendering occurs the crash does
not occur, however reloading/navigating to the next page render will then cause
a crash. Switching to another workspace during render still crashes.
Steps to Reproduce:
1. Load Firefox
2. Open overstock.com
Back to console screen with "Please also check the logfile at /tmp/mnt/xorg.log
for additional information. xserver failed, press <enter> to continue" - As I
am in a terminal-server environment (LTSP.org), the console is completely
locked and I cannot get to xorg.log
This bug occurred in FC5 and FF 220.127.116.11 too, also sometimes in OOo and Thunderbird when loading lots of large images.
I assume it has to do with the amount of memory reported by the BIOS. For me, specifically setting X_VIDEORAM to values (4096, 8192) does not solve the problem.
No problem here on any of these sites with FF 18.104.22.168 and xf86-video-i810-2.3.2 on a Dell D400 with Gentoo Linux and Xorg 7.2 / xorg-server-22.214.171.124-r6
on Jul 26, 2016 at 12:11:07.
(provided by the Example extension).