From owner-freebsd-current@FreeBSD.ORG Thu Apr 15 19:42:01 2004 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 0BCE716A4CE for ; Thu, 15 Apr 2004 19:42:01 -0700 (PDT) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id DE11843D4C for ; Thu, 15 Apr 2004 19:42:00 -0700 (PDT) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id CB57E72DF0; Thu, 15 Apr 2004 19:42:00 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id C601072DBF; Thu, 15 Apr 2004 19:42:00 -0700 (PDT) Date: Thu, 15 Apr 2004 19:42:00 -0700 (PDT) From: Doug White To: Andrea Campi In-Reply-To: <20040411214300.GA10921@webcom.it> Message-ID: <20040415193930.B914@carver.gumbysoft.com> References: <20040411214300.GA10921@webcom.it> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-current@freebsd.org Subject: Re: panic: bad pte 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: Fri, 16 Apr 2004 02:42:01 -0000 On Sun, 11 Apr 2004, Andrea Campi wrote: > Hi, > > I know this has been mentioned before on the list, and probably I should > know what to make of it, but still... > > I'm getting this panic from time to time (not easy to reproduce, no > apparent pattern): > > TPTE at 0xbfca06ec IS ZERO @ VA 281bb000 > panic: bad pte > at line 2558 in file /usr/src/sys/i386/i386/pmap.c > > > I was silly and just typed c so nothing more to work on I'm afraid. > Basically, what I'm asking is: what's it about? Is it hardware-related, > is it a know problem, or should I wait for it to happen again and look > into getting more details? A pte is a Page Table Entry and has to do with memory mapping. This particular panic is triggered when it discovers a page its trying to remove from a process doesn't appear to exist. This can be caused by bad memory corrupting the page tables, or it could be a bug. Someone wwhos familiar with the pagetable layout may want to investigate the given VA to see whats corrupted. That prson isn't me unfortunately :) Try to capture a crashdump and save it and the debugging kernel somewhere in case someone wants to look at it offline. -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org