The Digital CSC has told me that the crashes are caused by a hardware
problem. I'm in the process of trying to get a new motherboard now...
Drew
##############################################################################
# Andrew Gallatin, Computer Project Manager #
# Institute of Statistics and Decision Sciences #
# Box 90251, Duke University, Durham, NC 27708-0251 #
##############################################################################
My original posting:
We recently purchased a used 3000/500 & its having problems running
Xdec under 3.2c. We're using the integrated HX graphics controller
( fb0 at tc0; slot 8 1280X1024 ) running at 66Hz talking to a VRT19-DA.
The xdm login prompt comes up & everything looks fine. You can login
for 1 minute to a few hours. At some point, a mesh will appear,
overlaying the screen with little white dots. Soon after this, any
operation that refreshes a large portion of the screen will cause the
X server to crash.
No errors are logged via syslog, or via the uerf facility. The most
information I've got is from running Xdec with the -core option. It
leaves a core file that shows this when dbx is run on it:
# dbx /usr/bin/X11/Xdec /core
dbx version 3.11.8
Type 'help' for help.
Core file created by program "Xdec"
warning: /usr/bin/X11/Xdec has no symbol table -- very little is supported witho
ut it
signal Segmentation fault at >*[sfbScreenMalloc, 0x30000013310] ldl r
7, 8(r19)
(dbx) dump
sfbScreenMalloc(0x3ff816f5c9c, 0x0, 0x3ff8170f1d8, 0x1400137a0, 0x12a) [0x300000
13310]
(dbx) where
> 0 sfbScreenMalloc(0x3ff816f5c9c, 0x0, 0x3ff8170f1d8, 0x1400137a0, 0x12a) [0x3
0000013310]
1 sfbCreatePixmap(0x1400137a0, 0x93, 0x3ff00000015, 0x100000008, 0x3ff816f5a3
8) [0x3000001357c]
2 (unknown)(0x1400b7ec0, 0x11ffff388, 0x140085a80, 0x0, 0x3ff81721cc8) [0x3ff
81723918]
3 (unknown)(0x11ffff710, 0x11ffff710, 0x0, 0x0, 0x3ff816f5bf0) [0x3ff81721d78]
4 (unknown)(0x11ffff630, 0x11ffff5f8, 0x11ffff630, 0x4, 0x11ffff710) [0x3ff81
6f5c98]
5 (unknown)(0x11ffff730, 0x11ffff6f8, 0x11ffff730, 0x4, 0x11ffff710) [0x3ff81
6f5b78]
6 miValidateTree(0x1400078c0, 0x1400b7d80, 0x4, 0x3ffffd, 0x140085a80) [0x3ff
816f61ac]
7 MapWindow(0x3ff00000000, 0x14001b600, 0x1400b7ec0, 0x0, 0x1400078c0) [0x3ff
816c9920]
8 ProcMapWindow(0x14001b600, 0x1, 0xda330101, 0x2900000001, 0x3ff00000000) [0
x3ff8168e390]
9 Dispatch(0x3ffc086b3e8, 0x3ffc086d0e8, 0x3ff00000001, 0x64c086d0e8, 0x601ff
ff003b) [0x3ff8168d924]
10 dix_main(0x5, 0x1400099e0, 0x120006cbc, 0x0, 0x1200080f8) [0x3ff816a70a4]
(dbx)
Also, the /var/X11/xdm/xdm-errors file is littered with messages like:
XIO: fatal IO error 32 (Broken pipe) on X server ":0.0"
after 426 requests (425 known processed) with 0 events remaining.
The connection was probably broken by a server shutdown or KillClient.
error (pid 891): IO Error in XOpenDisplay
error (pid 494): Display :0 cannot be opened
If anybody else has seen anything like this, please drop me a line.
Thanks,
Drew
##############################################################################
# Andrew Gallatin, Computer Project Manager #
# Institute of Statistics and Decision Sciences #
# Box 90251, Duke University, Durham, NC 27708-0251 #
##############################################################################
Received on Tue Nov 21 1995 - 21:05:44 NZDT