From owner-freebsd-current@FreeBSD.ORG Fri Oct 17 14:00:42 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 E88B516A4B3 for ; Fri, 17 Oct 2003 14:00:42 -0700 (PDT) Received: from pit.databus.com (p70-227.acedsl.com [66.114.70.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id EE9B043FD7 for ; Fri, 17 Oct 2003 14:00:41 -0700 (PDT) (envelope-from barney@pit.databus.com) Received: from pit.databus.com (localhost [127.0.0.1]) by pit.databus.com (8.12.9p2/8.12.9) with ESMTP id h9HL0fYL022942; Fri, 17 Oct 2003 17:00:41 -0400 (EDT) (envelope-from barney@pit.databus.com) Received: (from barney@localhost) by pit.databus.com (8.12.9p2/8.12.9/Submit) id h9HL0fGn022941; Fri, 17 Oct 2003 17:00:41 -0400 (EDT) (envelope-from barney) Date: Fri, 17 Oct 2003 17:00:41 -0400 From: Barney Wolff To: Peter Wemm Message-ID: <20031017210041.GA22128@pit.databus.com> References: <20031017103459.GA8418@stack.nl> <20031017165157.276E22A8D5@canning.wemm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20031017165157.276E22A8D5@canning.wemm.org> User-Agent: Mutt/1.4.1i X-Scanned-By: MIMEDefang 2.37 cc: freebsd-current@freebsd.org Subject: Re: panic: pmap_enter: attempted pmap_enter on 4MB page 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, 17 Oct 2003 21:00:43 -0000 On Fri, Oct 17, 2003 at 09:51:57AM -0700, Peter Wemm wrote: > > AHA! origpte being 0xd0d0d0d0 means that something really came unstuck > because that is the fill pattern that userland malloc(3) uses. The > 4MB page thing is a red herring, it just happens that PG_PS (0x80) is > a set bit in the fill pattern. > > Now to find the source. :-( Are you getting this repeatably? If somebody > is able to (relatively) easily provoke this, there are a few things I'd > like to try (shotgun diagnostics, but its better than nothing). I also have a dual-athlon system that gets this panic on current. The problem shows up first as sig 10 & 11 on builds (world/kernel/ports) and eventual panic on pmap_enter on 4mb page. I KNOW it's not hardware, because a -current kernel from 9/24/03 is rock-solid (hours of port builds, make -j16 buildworld) and so is RELENG_5_1. The current kernel from yesterday did not even get through installworld without a sig11. I'm pretty sure it's not ata, because my system has scsi disks, and only an idle ata cdrom. I have pentiumpro as my cputype, because I also use this system to build for my laptop - is that a conceivable clue? But for experiments we can set it to anything. It's not in production, so if you want to try stuff, I'm willing to give you a login or take direction. Right now it's running RELENG_5_1 but I also have yesterday's -head on there and a local cvs on another system updated twice a day. -- Barney Wolff http://www.databus.com/bwresume.pdf I'm available by contract or FT, in the NYC metro area or via the 'Net.