*BSD News Article 74350


Return to BSD News archive

Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!news.hawaii.edu!ames!agate!howland.reston.ans.net!newsfeed.internetmci.com!news.kei.com!news.texas.net!news.sprintlink.net!news-fw-6.sprintlink.net!news.sprintlink.net!news-fw-12.sprintlink.net!news.sprintlink.net!news-fw-22.sprintlink.net!news.sprintlink.net!news-ana-7.sprintlink.net!news.sprintlink.net!news-ana-24.sprintlink.net!mayumi.iphil.net!map
From: map@marikit.iphil.net (Miguel A.L. Paraz)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Help with coredumps under FreeBSD 2.1.5R
Date: 21 Jul 1996 10:14:37 GMT
Organization: IPhil Communications
Lines: 46
Message-ID: <slrn4v49er.l0e.map@marikit.iphil.net>
Reply-To: map@iphil.net
NNTP-Posting-Host: marikit.iphil.net
X-Newsreader: slrn (0.8.8.2 UNIX)

Hello,

I've had problems with my FreeBSD system, with the following configuration:

64 MB RAM
ASUS Motherboard
Adaptec 2940 "WIDE" (not sure of the exact type)
2 2.1 GB Seagate SCSI disks
1 1.05 GB HP SCSI disk
3C509 Ethernet card

It was mainly running INN (Usenet) and Squid (WWW cache).

When it was running 2.1.0R, it tended to crash once or twice every day --
couldn't get the exact message, something like kernel overwriting a certain 
page.

I brought it up to 2.1.5R.  I downloaded the bin components twice --
the first time, doing pings caused it to "buffer overflow", which I think
was related to the 3C509.  On time it even dumped core at the end of the
extraction procedure.  Then, I finally it got it to install.

I tried to compile a new kernel, and it immediately gave me a signal 11.
I tried to gcc a trivial C program -- "int main () {}" -- and it led to the
same thing.

In frustration, as I had to get it up and running ASAP, I ran Linux 1.2.13 
on it.  No problems so far.

The only thing I have left to do is try the new boot.flp to do the install.
I see from the MD5 signatures that it has also changed.  I hope this is it.

I really want to run FreeBSD on this.  Any suggestions on what could be 
wrong?  I was thinking it was hardware (especially from the sig 11 FAQ),
but how come it works perfectly (so far) under Linux?

Thanks very much in advance.  I'd appreciate a cc: to e-mail since the
machine in question is the news server!

-- 
miguel a.l. paraz <map@iphil.net> / iphil communications / PGP keyID 0x43F0D011