Date: Fri, 18 Jun 2004 15:19:25 -0700 From: Marcel Moolenaar <marcel@xcllnt.net> To: Steve Kargl <sgk@troutmask.apl.washington.edu> Cc: freebsd-current@freebsd.org Subject: Re: GEOM panic in today's -current Message-ID: <20040618221925.GA68814@ns1.xcllnt.net> In-Reply-To: <20040618215453.GA77157@troutmask.apl.washington.edu> References: <20040618213843.GA77071@troutmask.apl.washington.edu> <20040618215453.GA77157@troutmask.apl.washington.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040618221925.GA68814>