Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!nntp.coast.net!news.kei.com!newsfeed.internetmci.com!in2.uu.net!EU.net!usenet2.news.uk.psi.net!uknet!dispatch.news.demon.net!demon!jraynard.demon.co.uk!not-for-mail From: james@jraynard.demon.co.uk (James Raynard) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: Signal 11 Date: 25 May 1996 22:51:54 -0000 Organization: A FreeBSD Box Lines: 25 Message-ID: <4o82ua$br6@jraynard.demon.co.uk> References: <nD356D43A@longacre.demon.co.uk> <4o5bp9$gel@jraynard.demon.co.uk> <nD3E85F90@longacre.demon.co.uk> NNTP-Posting-Host: localhost.demon.co.uk X-NNTP-Posting-Host: jraynard.demon.co.uk In article <nD3E85F90@longacre.demon.co.uk>, Michael Searle <searle@longacre.demon.co.uk> wrote: >james@jraynard.demon.co.uk (James Raynard) wrote: >> They can also be caused by running out of swap, which certainly sounds >> like a possible explanation for the problems you described. How much >> swap do you have? > >64 megs. Once the signal 11 was when I ran out of swap, but not the other >times - with only 16 megs of RAM, it usually becomes too slow to use before >I get near using all the swap. Hmm. Maybe it is hardware-related then (I assume you're running the release version and not -current, where strange things can sometimes happen). The best thing I can suggest is playing around with BIOS settings - trying less aggressive caching, adding a wait state, that kind of thing. Make sure you write your current settings down on a piece of paper first, though! -- James Raynard, Edinburgh, Scotland jraynard@dial.pipex.com james@jraynard.demon.co.uk