Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!nntp.coast.net!howland.erols.net!news.mathworks.com!fu-berlin.de!irz401!orion.sax.de!uriah.heep!news From: j@uriah.heep.sax.de (J Wunsch) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: FreeBSD hangs Date: 5 Oct 1996 19:32:37 GMT Organization: Private BSD site, Dresden Lines: 22 Message-ID: <536d4l$ba@uriah.heep.sax.de> References: <FRODEF.96Oct1160443@dslab5.cs.uit.no> Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) NNTP-Posting-Host: localhost.heep.sax.de Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: knews 0.9.6 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E frodef@dslab5.cs.uit.no (Frode Vatvedt Fjeld) wrote: > I discovered a file /var/crash/minfree once (it held the string > "2048"), but I have no idea what that means. It tells savecore(8) to leave at least 2 MB of free space when trying to save a kernel coredump. > I compiled my own kernel, and all devices appear to work well. It's an > all SCSI-system (NCR 53C810 on motherboard, no IDE-drivers compiled > in), otherwise it's a very standard PC configuration. 80 ... 90 % of all `sudden freezes' on SCSI systems are due to improper termination or poor cabling. That's the point where i would start looking first. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)