From owner-freebsd-current@FreeBSD.ORG  Sat Oct 11 11:47:57 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 3541716A4B3
	for <freebsd-current@freebsd.org>;
	Sat, 11 Oct 2003 11:47:57 -0700 (PDT)
Received: from ebb.errno.com (ebb.errno.com [66.127.85.87])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 82F5C43FAF
	for <freebsd-current@freebsd.org>;
	Sat, 11 Oct 2003 11:47:56 -0700 (PDT)	(envelope-from sam@errno.com)
Received: from 66.127.85.91 ([66.127.85.91])	(authenticated bits=0)
	by ebb.errno.com (8.12.9/8.12.9) with ESMTP id h9BIlt0x041824
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO)
	for <freebsd-current@freebsd.org>;
	Sat, 11 Oct 2003 11:47:56 -0700 (PDT)	(envelope-from sam@errno.com)
From: Sam Leffler <sam@errno.com>
Organization: Errno Consulting
To: freebsd-current@freebsd.org
Date: Sat, 11 Oct 2003 11:49:00 -0700
User-Agent: KMail/1.5.3
MIME-Version: 1.0
Content-Type: text/plain;
  charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200310111149.00829.sam@errno.com>
Subject: 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
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 11 Oct 2003 18:47:57 -0000

I've been getting this panic a lot in the past week.  Unfortunately it's on my 
file server so I can't use gdb to get more details than what ddb provides 
(the kernel is on the machine that's panic'd).  This is a UP x86 box.  The 
stack trace is:

pmap_enter
kmem_malloc
page_alloc
slab_zalloc
uma_zone_slab
uma_zalloc_bucket
uma_zalloc_arg
uma_zalloc_arg
ffs_vget
ufs_lookup
ufs_vnoperate
vfs_cache_lookup
ufs_voperate
lookup
nfs_namei
nfsrv_lookup
nfssvc_nfsd
nfssvc

Contact me for more details. This really needs to be fixed.

	Sam