From owner-freebsd-current Wed Jun 19 21:49:54 2002 Delivered-To: freebsd-current@freebsd.org Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by hub.freebsd.org (Postfix) with ESMTP id EFD1937B404 for ; Wed, 19 Jun 2002 21:49:45 -0700 (PDT) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) by troutmask.apl.washington.edu (8.12.3/8.12.3) with ESMTP id g5K4njQ9018907 for ; Wed, 19 Jun 2002 21:49:45 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.12.3/8.12.3/Submit) id g5K4njMD018906 for freebsd-current@freebsd.org; Wed, 19 Jun 2002 21:49:45 -0700 (PDT) Date: Wed, 19 Jun 2002 21:49:45 -0700 From: Steve Kargl To: freebsd-current@freebsd.org Subject: vm related kernel panics Message-ID: <20020619214945.A18873@troutmask.apl.washington.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I got 2 panics from -current sources of today. The back traces are: panic 1: vm_page_insert vm_page_alloc vm_page_grab pmap_new_proc vm_forkproc fork1 fork syscall syscal panic 2: panic mtx_init fork1 fork syscal syscall I would provide more information except I seem to have some problems reading my vmcore.0 files with either gdb or gdb52. -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message