Return to BSD News archive
Newsgroups: comp.unix.bsd.freebsd.misc Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.cs.su.oz.au!metro!metro!munnari.OZ.AU!spool.mu.edu!howland.reston.ans.net!plug.news.pipex.net!pipex!tank.news.pipex.net!pipex!newsfeed.internetmci.com!in2.uu.net!news.thepoint.net!news1!not-for-mail From: root@dyson.iquest.net (John S. Dyson) Subject: Re: Signal 11 X-Nntp-Posting-Host: dyson.iquest.net Message-ID: <4o7hcp$8hk@dyson.iquest.net> Sender: news@iquest.net (News Admin) Organization: John S. Dyson's Machine References: <nD356D43A@longacre.demon.co.uk> Date: Sat, 25 May 1996 17:52:25 GMT Lines: 26 In article <nD356D43A@longacre.demon.co.uk>, Michael Searle <searle@longacre.demon.co.uk> wrote: > >Does processes exiting on signal 11 always mean bad hardware (probably >memory or mainboard), or can they be caused by other things (like buggy >executables)? > If it is code that has been running on other, idential configs, most of the time it is bad hardware. There are sometimes other causes (like corrupted binaries, or strange kernel problems), but those are less common. > >Also - I did a lmbench, mostly seemed OK but > >*Local* Communications bandwidths in megabytes/second >----------------------------------------------------- >Host OS Pipe TCP File Mmap Bcopy Bcopy Mem Mem > reread reread (libc) (hand) read write >longacre FreeBSD 2.1.0 23 0.2 4.1 55.8 0 0 73 83 > That is an anomoly due to an artifact of the way some of the buffering in FreeBSD is configured using the loopback device. I believe that the -current ports version of lmbench has that fixed. I seem to remember that the summary results also appear screwed up (even on LM's web site), so beware!!! :-). John