From owner-freebsd-current@FreeBSD.ORG Thu Nov 13 11:58:44 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B36B716A4CF for ; Thu, 13 Nov 2003 11:58:44 -0800 (PST) Received: from cpc2-cove3-6-0-cust88.brhm.cable.ntl.com (cpc2-cove3-6-0-cust88.brhm.cable.ntl.com [81.107.10.88]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1C19F43FBD for ; Thu, 13 Nov 2003 11:58:43 -0800 (PST) (envelope-from ianjhart@ntlworld.com) Received: from gamma.private.lan (gamma.private.lan [192.168.0.12]) ESMTP id hADJwD1V068189; Thu, 13 Nov 2003 19:58:13 GMT (envelope-from ianjhart@ntlworld.com) From: ian j hart To: Peter Risdon , "Jaco H. van Tonder" Date: Thu, 13 Nov 2003 19:58:12 +0000 User-Agent: KMail/1.5.4 References: <3FB20370.7060807@circlesquared.com> <099401c3a939$322ac680$3635a8c0@jaco> <3FB29C5C.6090803@circlesquared.com> In-Reply-To: <3FB29C5C.6090803@circlesquared.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200311131958.12823.ianjhart@ntlworld.com> cc: freebsd-current@freebsd.org Subject: Re: Intel 865 probs X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Nov 2003 19:58:44 -0000 On Wednesday 12 November 2003 8:47 pm, Peter Risdon wrote: > Jaco, > > Thanks for this. > > Jaco H. van Tonder wrote: > >For what its worth, I had a lot of problems on the I865P board, and It > >boiled down to memory corruption. > >The machine had lots of "random" crashes, meanng that they were not > > occuring when I do something specific. > >The machine startted to panic as soon as the load got high. > >I took out the memory, and placed it into another slot and the machine is > >cruising along happily now. > > I played with the memory slots as soon as the problems started, and > found memtest would sometimes throw up huge numbers of errors, and > sometimes none at all. FWIW slot 1 was the worst. But I suspect, no more > than that, some other problem as well. I've seen this behavior from memtest. Using the menu to restart usually fixes. The bogus errors are easy to spot. > > >The other questions is what is the date of the -CURRENT tree that is > > giving this problems? I can recall quite a few problems, which were > > fixed, that could cause this problem. > > Nov 10. I ran cvsup at about 9:00am GMT. > > Peter Risdon. > > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" -- ian j hart http://ars.userfriendly.org/cartoons/?id=20031016