From owner-freebsd-hackers Mon Feb 19 17:51:47 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id RAA10497 for hackers-outgoing; Mon, 19 Feb 1996 17:51:47 -0800 (PST) Received: from Root.COM (implode.Root.COM [198.145.90.17]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id RAA10492 for ; Mon, 19 Feb 1996 17:51:45 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by Root.COM (8.6.12/8.6.5) with SMTP id RAA02642; Mon, 19 Feb 1996 17:49:23 -0800 Message-Id: <199602200149.RAA02642@Root.COM> X-Authentication-Warning: implode.Root.COM: Host localhost didn't use HELO protocol To: Archie Cobbs cc: jgreco@brasil.moneng.mei.com (Joe Greco), bugs@freebsd.netcom.com, hackers@freebsd.org Subject: Re: Web server locks up... but not quite. (?) (fwd) In-reply-to: Your message of "Mon, 19 Feb 1996 16:14:27 PST." <199602200014.QAA10682@bubba.tribe.com> From: David Greenman Reply-To: davidg@Root.COM Date: Mon, 19 Feb 1996 17:49:23 -0800 Sender: owner-hackers@freebsd.org Precedence: bulk > >> > > I've seen similar hangs occasionally under both 2.0.5R and 2.1.0R and one >> > > additional "thing" I've noticed is that processes that are completely >> > > in-core appear to keep running (i.e. I had a "vmstat 1" running for a few > >Ah... I've seen something similar on some small memory (4M) machines I've >been trying to get running. I get lots of sig 11 (and sometimes >sig 4, illegal instruction, etc.) and thought it was hardware, >but swapping motherboards, cpu's, and memory didn't help. > >Going from 4MB to 5MB reduces, but doesn't eliminate, the problems. It may still be hardware. If you're using IDE, some really cheap IDE controllers have been known to cause problems. If your motherboards aren't configured correctly for the right amount of wait states for RAM, etc, then this can and will cause problems. The list goes on. I'm not saying for certain that it's not a software bug (this WAS a problem in early FreeBSD releases), but we do extensive pre-release testing (looking specifically for this problem) on 4MB and 5MB machines and didn't/haven't seen the problem. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project