From owner-freebsd-current@FreeBSD.ORG Fri Jun 18 22:19:27 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 4D7BC16A4CE for ; Fri, 18 Jun 2004 22:19:27 +0000 (GMT) Received: from ns1.xcllnt.net (209-128-86-226.BAYAREA.NET [209.128.86.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id D762543D31 for ; Fri, 18 Jun 2004 22:19:26 +0000 (GMT) (envelope-from marcel@xcllnt.net) Received: from ns1.xcllnt.net (localhost [127.0.0.1]) by ns1.xcllnt.net (8.12.11/8.12.11) with ESMTP id i5IMJPXJ069140; Fri, 18 Jun 2004 15:19:25 -0700 (PDT) (envelope-from marcel@ns1.xcllnt.net) Received: (from marcel@localhost) by ns1.xcllnt.net (8.12.11/8.12.11/Submit) id i5IMJP6e069139; Fri, 18 Jun 2004 15:19:25 -0700 (PDT) (envelope-from marcel) Date: Fri, 18 Jun 2004 15:19:25 -0700 From: Marcel Moolenaar To: Steve Kargl Message-ID: <20040618221925.GA68814@ns1.xcllnt.net> References: <20040618213843.GA77071@troutmask.apl.washington.edu> <20040618215453.GA77157@troutmask.apl.washington.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040618215453.GA77157@troutmask.apl.washington.edu> User-Agent: Mutt/1.5.5.1i cc: freebsd-current@freebsd.org Subject: Re: GEOM panic in today's -current 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, 18 Jun 2004 22:19:27 -0000 On Fri, Jun 18, 2004 at 02:54:53PM -0700, Steve Kargl wrote: > On Fri, Jun 18, 2004 at 02:38:43PM -0700, Steve Kargl wrote: > > I'll get whatever info someone wants or needs. > > Here, a handwritten trace of the boot-time panic > > > > db> trace > > free() > > g_slice_free > > g_slice_spoiled() > > g_bsd_taste() > > g_new_provider_event() > > one_event() > > g_run_events() > > g_event_procbody() > > fork_exit() > > fork_trampoline > > > > More info. If I set hint.acpi.0.disabled="1", then the > new kernel boots. So, the problem may actually lie in > ACPI. FYI: reboot -d is broken when the dump device is on an ATA disk. I don't have the details here, but it's trying to do an unlock for an uninitialize/non-existent mutex. It may be related. It may not be... -- Marcel Moolenaar USPA: A-39004 marcel@xcllnt.net