From owner-freebsd-current Thu Aug 22 2:35:40 2002 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 0AADF37B400; Thu, 22 Aug 2002 02:35:37 -0700 (PDT) Received: from falcon.mail.pas.earthlink.net (falcon.mail.pas.earthlink.net [207.217.120.74]) by mx1.FreeBSD.org (Postfix) with ESMTP id A3B1043E3B; Thu, 22 Aug 2002 02:35:36 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from pool0003.cvx40-bradley.dialup.earthlink.net ([216.244.42.3] helo=mindspring.com) by falcon.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 17hoN9-0002EB-00; Thu, 22 Aug 2002 02:35:24 -0700 Message-ID: <3D64B005.6657A3B5@mindspring.com> Date: Thu, 22 Aug 2002 02:33:57 -0700 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Soeren Schmidt Cc: Martin Blapp , Don Lewis , marks@ripe.net, ktsin@acm.org, freebsd-current@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: Memory corruption in CURRENT References: <200208220909.g7M99NcS077303@freebsd.dk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Soeren Schmidt wrote: > It seems Martin Blapp wrote: > > I suspect all the SIG4 and SIG11 problems we see are due > > memory corruption in CURRENT. > .... > > > The file is correct after a reboot, so the corruption was limited to the > > > copy cached in RAM. > > > > Thats memory corruption. I'm also not able anymore > > to make 10 buildworlds (without -j, that triggers > > panics in pmap code). > > > > Bye the way, I'm experiencing this since about 4-5 months. > > > > All hackers, please help to track this down. > > Hmm, I haven't seen this at all, but I've just started buildworld loops on > two machines here, but I normally do at least a couble buildworlds a day > and I havn't notice problems like the above (but plenty of bad commits etc). > > However, this kind of problem in most cases spells bad HW to me, > ie subspec RAM, poor powersupply, badly cooled CPU, overclocking etc etc... Try: options DISABLE_PSE options DISABLE_PG_G -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message