From owner-freebsd-current Thu Jun 20 10:36:16 2002 Delivered-To: freebsd-current@freebsd.org Received: from mail.chesapeake.net (chesapeake.net [205.130.220.14]) by hub.freebsd.org (Postfix) with ESMTP id A21D737B403 for ; Thu, 20 Jun 2002 10:36:07 -0700 (PDT) Received: from localhost (jroberson@localhost) by mail.chesapeake.net (8.11.6/8.11.6) with ESMTP id g5KHa0S80285; Thu, 20 Jun 2002 13:36:00 -0400 (EDT) (envelope-from jroberson@chesapeake.net) Date: Thu, 20 Jun 2002 13:36:00 -0400 (EDT) From: Jeff Roberson To: sgk@troutmask.apl.washington.edu Cc: freebsd-current@freebsd.org Subject: Re: vm related kernel panics In-Reply-To: Message-ID: <20020620133339.I78902-100000@mail.chesapeake.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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. > I'm not sure what's wrong with gdb, but those two panics were my fault. They were fixed by rev 1.80 of vm_kern.c Jeff To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message