*BSD News Article 64741


Return to BSD News archive

#! rnews 2035 bsd
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.rmit.EDU.AU!news.unimelb.EDU.AU!munnari.OZ.AU!news.ecn.uoknor.edu!news.ysu.edu!usenet.ins.cwru.edu!magnus.acs.ohio-state.edu!math.ohio-state.edu!howland.reston.ans.net!newsfeed.internetmci.com!battery.awod.com!usenet
From: lam@awod.com (Ken Lam)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: FreeBSD news server bombing
Date: 20 Mar 1996 20:30:50 GMT
Organization: A World Of Difference, Inc.
Lines: 33
Message-ID: <4ipptq$3k8@battery.awod.com>
References: <4iofsa$fbg@apakabar.cc.columbia.edu>
NNTP-Posting-Host: tsunami.awod.com
Mime-Version: 1.0
Content-Type: Text/Plain; charset=US-ASCII
X-Newsreader: WinVN 0.99.7

>I guess the question is - does anyone know for certain:
>        1) If the 2940 driver has a problem with the new BIOS.

In general, I have a 2940 with 1.21 Bios, crashes just about
once a day.  I just received the 1.16 bios which I will be
putting in the system (which is a news server).  Have no
problems with my other 1.16 BIOS 2940s (including other news
and web servers).

>        2) If the 3c509 is really still "buggy".

Nope.  I have been running the 509 in my machine with no problems
since 2.0.5.  I believe that they were going to change the
docs in the handbook and FAQ with regards to that (plus the LINT
config file).  Check with the hackers maillist or the doc maillist.

>        3) I shouldn't be messing with a 486 PCI MB.

Yup. Probably for less than $100, you can get a P5-75 and with
a little work, recompiling some pieces of code with the Pentium
optimized compiler, gain that extra performance.  BTW, I don't
believe that that 486/PCI combo gets the full benefits of PCI.

>And for the news admin who have a rock solid FreeBSD news server.
>        4) What should I do about awk crashing!?!? Have you seen
>        this behavior? WTF!?!?! 

Well, I'm running 2.1.0R on a P5-90/64MB which other than having
problems with the 1.2x ROMs is lovely.  Have you debug'd the core
file?  Where did it crash?

-k