Return to BSD News archive
Xref: sserve comp.os.386bsd.bugs:1019 comp.os.386bsd.questions:3451 comp.windows.x.i386unix:2261 comp.os.386bsd.apps:261
Path: sserve!newshost.anu.edu.au!munnari.oz.au!constellation!osuunx.ucc.okstate.edu!moe.ksu.ksu.edu!ux1.cso.uiuc.edu!howland.reston.ans.net!paladin.american.edu!news.univie.ac.at!email.tuwien.ac.at!email.tuwien.ac.at!not-for-mail
From: mbirgmei@email.tuwien.ac.at (Martin BIRGMEIER)
Newsgroups: comp.os.386bsd.bugs,comp.os.386bsd.questions,comp.windows.x.i386unix,comp.os.386bsd.apps
Subject: XFree86 1.3 crashes under 386BSD
Date: 30 Jun 1993 12:30:49 +0200
Organization: Technical University Vienna / Austria
Lines: 57
Message-ID: <20rq0p$iev@email.tuwien.ac.at>
NNTP-Posting-Host: email.tuwien.ac.at
Hello all,
with so many new goodies arriving lateley, I started to gain some hope
again... anyway, a few months ago when XFree86-1.2 came out, I built
that server from source, and when run it would crash after usually only
a few minutes. Then I tried the precompiled version which exhibited
exactly the same behaviour. There was a short discussion on the
relevant newsgroups pointing out that the most likely problem was in
386BSD itself, but no solution came up, and I had to revert to version 1.1.
Ok, now with patchkit-0.2.4 installed and codrv enabled (I already had
an older version installed before), I thought I should try the
precompiled binaries for XFree86-1.3. Sadly enough, the same behavior
resulted, and I am back to 1.1 again. But I still keep wondering just
what is wrong with either 386BSD, my hardware setup, my software setup,
or else. It seems that some people are running the server happily on
their boxes, doesn't it? Some of the many changes between 1.1 and 1.2
must have exposed a bug - somewhere, and I'd so much *like to know*!
Here is some relevant information from SuperProbe:
First video: Super-VGA
Chipset: Tseng ET4000
RAMDAC: AT&T 20C491/492 15/16/24-bit DAC
The 1.1 server itself reports
XFree86 Version 1.1 / X Window System
(protocol Version 11, revision 0, vendor release 5000)
Configured drivers:
VGA256 (256 colour SVGA):
et4000, et3000, pvga1, gvga, ati, tvga8900
VGA256: et4000 (mem: 1024k numclocks: 16)
VGA256: clocks: 25 28 33 37 40 45 32 38 51 57 65 73 80 90 64 76
VGA256: SpeedUp mode selected (Flags=0x3f)
Text save failed
Text restore failed
where the last two lines obviously come from the new version of codrv
I installed with patchkit-0.2.4.
One more hint for those who might know the solution: I can trigger a
crash most easily if I run xlock with one of the modes which draw lines,
e.g. swarm or qix. Since the precompiled XFree86-1.3 binary has no
symbols, I can't get a full stack traceback; only the fact that abort()
was called can be deduced from the core. So most likely some signal
like bus error et al must have occured.
Solutions to this problem would be most appreciated!
- Martin
P.S. Other setup: 486DX50, 16M mem, 1542B + 300M SCSI, MSoft mouse,
etherlink II
P.P.S. No, it's neither the internal nor the external cache on my
motherboard - the server crashes with or without enabling any
or both of the two.