From owner-freebsd-current Tue Sep 17 14:11:38 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 12FD337B401; Tue, 17 Sep 2002 14:11:37 -0700 (PDT) Received: from albatross.prod.itd.earthlink.net (albatross.mail.pas.earthlink.net [207.217.120.120]) by mx1.FreeBSD.org (Postfix) with ESMTP id ACDC943E6A; Tue, 17 Sep 2002 14:11:36 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from pool0465.cvx22-bradley.dialup.earthlink.net ([209.179.199.210] helo=mindspring.com) by albatross.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 17rPd4-0003AE-00; Tue, 17 Sep 2002 14:11:31 -0700 Message-ID: <3D879A09.39991A3D@mindspring.com> Date: Tue, 17 Sep 2002 14:09:29 -0700 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Martin Blapp Cc: Nate Lawson , current@freebsd.org, peter@freebsd.org Subject: Re: Crashdumps available for download ... please help References: <20020917222622.U52781-100000@levais.imp.ch> 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 Martin Blapp wrote: > If you don't beleave it or not. I've taken out again (I've already > switched them once) one bank of 512M ram and since then I've not > had any panics anymore. > > Can a ram error occur after a system has been fine one month ? No. This is the TLB problem we all keep talking about. Bosko had some code that might have worked around the problem (as opposed to fixing it). Ask if he'll send you the patches (you must be running -current). I just got the most recent IA-32 manuals from Intel in the mail, and they still don't seem to be aware of the issue. Without actually recreating a copy of the GPD (it's just 8K, anyway), you really can't fix the problem; you have to do strange things to CR3 and CR4 to fix it, since there is a chicken-and-egg problem once you are in protected mode. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message