From owner-freebsd-current@FreeBSD.ORG Fri Oct 1 13:14:39 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 C06EC16A4CF for ; Fri, 1 Oct 2004 13:14:39 +0000 (GMT) Received: from green.homeunix.org (pcp04368961pcs.nrockv01.md.comcast.net [69.140.212.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id C154643D45 for ; Fri, 1 Oct 2004 13:14:37 +0000 (GMT) (envelope-from green@green.homeunix.org) Received: from green.homeunix.org (green@localhost [127.0.0.1]) by green.homeunix.org (8.13.1/8.13.1) with ESMTP id i91DEWYM005101; Fri, 1 Oct 2004 09:14:32 -0400 (EDT) (envelope-from green@green.homeunix.org) Received: (from green@localhost) by green.homeunix.org (8.13.1/8.13.1/Submit) id i91DEWxK005100; Fri, 1 Oct 2004 09:14:32 -0400 (EDT) (envelope-from green) Date: Fri, 1 Oct 2004 09:14:32 -0400 From: Brian Fundakowski Feldman To: kdulzo@sockpuppet.org Message-ID: <20041001131432.GE997@green.homeunix.org> References: <20040930183822.GA23562@skoda.sockpuppet.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040930183822.GA23562@skoda.sockpuppet.org> User-Agent: Mutt/1.5.6i cc: freebsd-current@freebsd.org Subject: Re: panic: vm_proc_new: upage allocation failed (5.6-BETA6) 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, 01 Oct 2004 13:14:39 -0000 On Thu, Sep 30, 2004 at 02:38:22PM -0400, Kevin M. Dulzo wrote: > PAE still panics on boot, GENERIC still works flawlessly save 4G of RAM. > > (kgdb) where > #0 kdb_enter (msg=???) at /usr/src/sys/kern/subr_kdb.c:241 > #1 0xc039e3c7 in panic (fmt=0xc0564ae2 "vm_proc_new: upage allocation failed") > at /usr/src/sys/kern/kern_shutdown.c:537 > #2 0xc04c1a68 in vm_proc_new (p=0xca86ba80) at /usr/src/sys/vm/vm_glue.c:255 > #3 0xc0396add in proc_init (mem=0xca86ba80, size=448, flags=259) > at /usr/src/sys/kern/kern_proc.c:182 > #4 0xc04d33f5 in slab_zalloc (zone=0xc0a232c0, wait=259) > at /usr/src/sys/vm/uma_core.c:839 > #5 0xc04d4a18 in uma_zone_slab (zone=0xc0a232c0, flags=3) > at /usr/src/sys/vm/uma_core.c:1959 > #6 0xc04d4c2c in uma_zalloc_bucket (zone=0xc0a232c0, flags=3) > at /usr/src/sys/vm/uma_core.c:2062 > #7 0xc04d48c2 in uma_zalloc_arg (zone=0xc0a232c0, udata=0x0, flags=2) > at /usr/src/sys/vm/uma_core.c:1886 > #8 0xc038765f in fork1 (td=0xc05d9fc0, flags=131124, pages=0, > procp=0xc087fd50) at uma.h:274 > #9 0xc038dafd in kthread_create (func=0xc04d14bc , arg=0x0, > newpp=0xc05f2d98, flags=0, pages=0, fmt=0xc0536614 "%s") > at /usr/src/sys/kern/kern_kthread.c:86 > #10 0xc038daa3 in kproc_start (udata=0xc05c7840) > at /usr/src/sys/kern/kern_kthread.c:58 > #11 0xc03761f2 in mi_startup () at /usr/src/sys/kern/init_main.c:210 > #12 0xc024113e in begin () at /usr/src/sys/i386/i386/locore.s:348 Can you try doing "show map kernel_map" (or the address for kernel_map if that doesn't work) in DDB when it panics, or translating that function into gdb-speak and getting the output? The address space seems to be getting fatally full. -- Brian Fundakowski Feldman \'[ FreeBSD ]''''''''''\ <> green@FreeBSD.org \ The Power to Serve! \ Opinions expressed are my own. \,,,,,,,,,,,,,,,,,,,,,,\