From owner-freebsd-bugs Sun Oct 10 12:58:29 1999 Delivered-To: freebsd-bugs@freebsd.org Received: from implode.root.com (root.com [209.102.106.178]) by hub.freebsd.org (Postfix) with ESMTP id 0374A14D58 for ; Sun, 10 Oct 1999 12:58:13 -0700 (PDT) (envelope-from dg@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.8/8.8.5) with ESMTP id MAA11927; Sun, 10 Oct 1999 12:57:45 -0700 (PDT) Message-Id: <199910101957.MAA11927@implode.root.com> To: David Gilbert Cc: freebsd-bugs@FreeBSD.ORG Subject: Re: kern/14141: 3.3-RELEASE crashing often In-reply-to: Your message of "Sun, 10 Oct 1999 12:20:01 PDT." <199910101920.MAA81395@freefall.freebsd.org> From: David Greenman Reply-To: dg@root.com Date: Sun, 10 Oct 1999 12:57:45 -0700 Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > 948 fpp = newfdp->fd_ofiles; > 949 for (i = newfdp->fd_lastfile; i-- >= 0; fpp++) > 950 if (*fpp != NULL) > 951 (*fpp)->f_count++; > 952 return (newfdp); > 953 } ... > > Then I thought about it... and fpp itself should not become NULL in > this case... it's being incremented from some valid pointer value. > > Ideas? Smells like a hardware problem. I had a lot of problems with AMD chips when I did reliability testing with them. One of the problems turned out to be a real bug in the chip (it only worked reliably with 32MB or less of RAM). They are also very sensitive to heat...you might verify that the heat sink is properly installed and that the fan is working. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project - http://www.freebsd.org Creator of high-performance Internet servers - http://www.terasolutions.com Pave the road of life with opportunities. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message