Return to BSD News archive
Path: sserve!manuel.anu.edu.au!munnari.oz.au!spool.mu.edu!uwm.edu!wupost!usc!news.service.uci.edu!pal-r32-a07b.slip.nts.uci.edu!swallace
From: swallace@pal-r32-a07b.slip.nts.uci.edu (Steven Wallace)
Subject: XFree86 1.2 BUG/Problem
Nntp-Posting-Host: pal-r32-a07b.slip.nts.uci.edu
Message-ID: <2B9827D1.19654@news.service.uci.edu>
Newsgroups: comp.unix.bsd
Organization: University of California, Irvine
Lines: 39
Date: 6 Mar 93 04:25:53 GMT
I just recently upgraded from X386 1.2E to XFree86 1.2. I'm having problems
with this new server, however. When I am running an intensive X application,
the server will die for no particular reason and send me back to the console.
Here is an error directed output of what happens:
-------------------------------------
XFree86 Version 1.2 / X Window System
(protocol Version 11, revision 0, vendor release 5000)
Configured drivers:
VGA256 (256 colour SVGA):
et4000, et3000, pvga1, gvga, ati, tvga8900c, tvga9000
Mouse: type: MouseSystems, device: /dev/ttyd0, baudrate: 1200
FontPath set to "/usr/X386/lib/X11/fonts/misc/,/usr/X386/lib/X11/fonts/Type1/,/usr/X386/lib/X11/fonts/Speedo/,/usr/X386/lib/X11/fonts/75dpi/"
VGA256: et4000 (mem: 1024k numclocks: 16)
VGA256: clocks: 25.2 28.3 32.5 36.0 40.0 44.9 31.5 37.5
VGA256: clocks: 50.3 56.6 64.9 72.0 80.0 89.8 63.0 75.0
VGA256: Mode "1152x900": mode clock = 81.0, clock used = 80.0
VGA256: Mode "1024x768": mode clock = 81.0, clock used = 80.0
VGA256: Mode "896x672": mode clock = 57.0, clock used = 56.6
VGA256: Mode "768x576": mode clock = 41.0, clock used = 40.0
VGA256: Virtual resolution set to 1152x900
Caught signal 11. Server aborting
xterm: fatal IO error 32 (Broken pipe) or KillClient on X server ":0.0"
XIO: fatal IO error 32 (Broken pipe) on X server ":0.0"
after 1279 requests (1278 known processed) with 0 events remaining.
The connection was probably broken by a server shutdown or KillClient.
xinit: connection to X server lost.
xterm: fatal IO error 32 (Broken pipe) or KillClient on X server ":0.0"
Cannot execute KBDFORCEASCII ioctl: Inappropriate ioctl for device
------------------------------------
Can anyone explain or give me a reason why the server will just
randomly die? It can be quite annoying. It sometimes will give me problems
right away or will take a long time (via the number of requests).
Also, is there any way to communicate locally instead via unix sockets
(the FAQ gives a benchmark listing of local and socket comms)?
Thanks.