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_at_xcllnt.netReceived on Fri Jun 18 2004 - 20:19:27 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:58 UTC