From owner-freebsd-current@FreeBSD.ORG Sat Mar 6 16:04:57 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 513E416A4CE for ; Sat, 6 Mar 2004 16:04:57 -0800 (PST) Received: from oahu.WURLDLINK.NET (oahu.wurldlink.net [66.193.144.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id E9EED43D1D for ; Sat, 6 Mar 2004 16:04:56 -0800 (PST) (envelope-from vince@oahu.WURLDLINK.NET) Received: from oahu.WURLDLINK.NET (vince@localhost.WURLDLINK.NET [127.0.0.1]) by oahu.WURLDLINK.NET (8.12.9/8.12.9) with ESMTP id i2704AqQ070241; Sat, 6 Mar 2004 14:04:10 -1000 (HST) Received: from localhost (vince@localhost)i27049K6070238; Sat, 6 Mar 2004 14:04:09 -1000 (HST) Date: Sat, 6 Mar 2004 14:04:09 -1000 (HST) From: Vincent Poy To: Sam Leffler In-Reply-To: Message-ID: <20040306140230.R8264-100000@oahu.WURLDLINK.NET> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-current@freebsd.org cc: Andrew Gallatin Subject: Re: reproducable "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: Sun, 07 Mar 2004 00:04:57 -0000 On Sat, 6 Mar 2004, Sam Leffler wrote: > On Mar 5, 2004, at 8:22 AM, Andrew Gallatin wrote: > > > > > Andrew Gallatin writes: > >> > >> I can reproducably panic -current with the above message by allocating > >> a lot of memory in 4MB chunks in an out-of-tree os-bypass network > >> driver. > >> > > > > After upgrading to this morning's -current, I can no longer > > reproduce this problem. Very, very strange. > > I've been getting this panic off+on for >9 months but haven't been able > to characterize it and/or narrow down the cause. I mostly see it on an > NFS server. I'm still getting this when a script executes at 4AM but it works fine when I manually execute it within 10 minutes after reboot... panic: kmem_malloc (4096): kmem_map too small: 377487360 total allocated at line 341 in file /usr/src/sys/vm/vm_kern.c cpuid=0; Debugger("panic") Stopped at Debugger+0x46: xchgl %ebx, in_Debugger.0 db> I've tried everything else suggested but those panic as soon as the memory size shows up in the boot sequence. Cheers, Vince - vince@WURLDLINK.NET - Vice President ________ __ ____ Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] WurldLink Corporation / / / / | / | __] ] San Francisco - Honolulu - Hong Kong / / / / / |/ / | __] ] HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[____] Almighty1@IRC - oahu.DAL.NET Hawaii's DALnet IRC Network Server Admin