Path: utzoo!mnetor!uunet!husc6!mit-eddie!bbn!rochester!PT.CS.CMU.EDU!andrew.cmu.edu!dc44+ From: dc44+@andrew.cmu.edu (Donna Converse) Newsgroups: comp.windows.x Subject: Xqdss server - Ultrix 2.2 Message-ID: Date: 24 Mar 88 20:18:19 GMT Organization: Carnegie Mellon University Lines: 62 If you have installed the Xqdss server on a micro-vax II with a GPX display under Ultrix 2.2, please read and respond. You may reply directly; also please send a copy to "converse@morgul.psc.edu". I will post a summary of replies and send a bug report to mit in about a week. I have installed X version 11 release 2, and fixes 1 through 11. I ftp'd the sources directly from mit and the checksums matched. I followed most defaults during build and installation, including the flags allowing both TCP connections and Unix domain connections. The man page for Xqdss says: "You need to make sure your kernel is configured with DMA_BUFSIZ set to 10 in sys/data/qd_data.c, or things won't work right." The value of DMA_BUFSIZ has been changed from (1024 * 3) to (1024 * 10) and I am running with this new kernel. My server, Xqdss, intermittently fails and appears to take down the the entire machine when it goes. The failure occurs upon startup or after the server has received a HUP (hangup) signal. The failure has occurred when the server is started manually, when the server has been sent a HUP signal manually, when the server is started by init through a ttys entry, when the server receives a HUP signal after I logout, and when I have started the server inside dbx. The failure rate is high; perhaps 30% to 50% of the time that the server is started or receives HUP it will fail. When the server receives a HUP due to a logout, the display flashes entirely white, then entirely black, and then either the familiar server grey stipple background and xterm window appear, or the server has failed. When the server has failed, the screen is black, my machine does not respond to ping across the net, and the machine itself does not indicate hardware error. I have no other way to determine the state of the machine, as I do not have any direct connect ttys, and after doing a restart and a boot, savecore does not find a kernel core file to save. The server doesn't drop core. There are no messages other than startup messages in /usr/adm/X0msgs. I never see messages on the console screen just before failure. This behavior is consistent whether I am running the server through init, manually, or in dbx. I have compiled the entire server code with -O, then with no flags, and finally with -g, but this doesn't change the problem. Here is my ttys entry (split into two lines here): ttyv0 "/usr/bin/X11/xterm -L -geometry 80x24+195+275 -display perlis:0" \ xterm on secure window="/usr/bin/X11/X perlis:0" I have also invoked X with an argument of "0" alone, and an argument of ":0". Both work, but the intermittent failure of the server still occurs. I don't understand whether an argument of "perlis:0" versus "0" will have a different effect. Would it force the server to use TCP connections in the first case and Unix domain connections in the second, or does it make no difference? The display always has a black, unused band about an inch wide on the left hand side, and an unused band of about a third of an inch on the right hand side. It is a similar problem to the qvss server, but I haven't yet tried to correct it. Has anyone found any unitialized pointers being used in the qdss server? I would appreciate your help. I will be writing an X driver for our CGM (Computer Graphics Metafile) translator. Internet: converse@morgul.psc.edu Bitnet: converse@cpwpsca Snail: Donna Converse * Pittsburgh Supercomputing Center * Mellon Institute 4400 Fifth Avenue * Pittsburgh PA 15213 * 412-268-5126