From owner-freebsd-current Wed Apr 5 6: 9:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from gatekeeper.radio-do.de (gatekeeper.Radio-do.de [193.101.164.1]) by hub.freebsd.org (Postfix) with ESMTP id 708C537B7C1 for ; Wed, 5 Apr 2000 06:09:20 -0700 (PDT) (envelope-from fn@gatekeeper.radio-do.de) Received: from trinity.radio-do.de (trinity.Radio-do.de [193.101.164.3]) by gatekeeper.radio-do.de (Postfix) with ESMTP id 8F89D97AA; Wed, 5 Apr 2000 15:09:21 +0200 (MET DST) Received: (from fn@localhost) by trinity.radio-do.de (8.9.3/8.9.3) id PAA01275; Wed, 5 Apr 2000 15:09:51 +0200 (CEST) (envelope-from fn@gatekeeper.radio-do.de) Date: Wed, 5 Apr 2000 15:09:51 +0200 From: Frank Nobis To: Jon Hamilton Cc: Maxim Sobolev , current@FreeBSD.ORG Subject: Re: Dangerously looking glitch (4.0-STABLE) Message-ID: <20000405150951.A1142@radio-do.de> References: <38EA2CD6.24636F65@altavista.net> <20000405121329.9EA0C17A@woodstock.monkey.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <20000405121329.9EA0C17A@woodstock.monkey.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Apr 05, 2000 at 07:13:29AM -0500, Jon Hamilton wrote: > > up clean. I think you have a hardware problem somewhere :( That is very likely a hardwre problem. I have a nfs server under 3.4-S here running, It was easy to crash the system with much I/O over nfs on a 100M Ethernet connection. (I did a dump and the machine paniced) The same over a slower 10M ethernet, but it took longer to crash. Now I replaced a very old adaptec 1542cf with a 2940U. I did the same stress test, but got no more panics. Even a load of 80% interrupts didn't kill the machine. Maybe you have a similar problem. -- ~/.signature not found: wellknown error 42 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message