From owner-freebsd-current Wed Apr 5 15:26:36 2000 Delivered-To: freebsd-current@freebsd.org Received: from mailgw02.execpc.com (mailgw02.execpc.com [169.207.3.78]) by hub.freebsd.org (Postfix) with ESMTP id A5E8337BF2F for ; Wed, 5 Apr 2000 15:26:29 -0700 (PDT) (envelope-from hamilton@pobox.com) Received: from woodstock.monkey.net (minbar-1-15.mdm.mke.execpc.com [169.207.135.15]) by mailgw02.execpc.com (8.9.1) id RAA20759; Wed, 5 Apr 2000 17:26:00 -0500 Received: from pobox.com (localhost [127.0.0.1]) by woodstock.monkey.net (Postfix) with ESMTP id ADBDF173; Wed, 5 Apr 2000 17:28:18 -0500 (CDT) X-Mailer: exmh version 2.1.1 10/16/1999 To: Maxim Sobolev Cc: Frank Nobis , current@FreeBSD.ORG Subject: Re: Dangerously looking glitch (4.0-STABLE) In-reply-to: Your message of "Wed, 05 Apr 2000 16:27:17 +0300." <38EB3F35.EF0E287A@altavista.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 05 Apr 2000 17:28:18 -0500 From: Jon Hamilton Message-Id: <20000405222818.ADBDF173@woodstock.monkey.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <38EB3F35.EF0E287A@altavista.net>, Maxim Sobolev wrote: } Frank Nobis wrote: } } > 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. } } It is unlikely, because I've never seen this problem previously when 3.[01234 } ] } was installed on this hardware. Hardware does fail over time; just because it performed OK in the past doesn't mean that something hasn't gone bad since. I suppose it could be a problem with one of the drivers for your particular setup; is it feasable for you to try booting an older version (even from floppy) of FreeBSD and try the test again? -- Jon Hamilton hamilton@pobox.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message