On Mon, Jul 31, 2006 at 08:21:30PM +0900, YONETANI Tomokazu wrote: > > Below are the backtrace and dmesg. The core dump is available if needed. > > Yes, if you have leaf account, plus the asf file, which can be generated > according to simon's instruction: > http://leaf.dragonflybsd.org/mailarchive/bugs/2006-07/msg00163.html
Oh, this already contains symbols from acpi driver, which means either the driver is compiled into the kernel, or you already used the asf file to show this backtrace. Hmm, I'm starting to feel that the dump may not be very helpful, since it's showing an array (AcpiGbl_BitRegisterInfo) as a function, and the addresses above that frame doesn't look like valid to me. If you can reproduce the panic while you're on console, the list of function names and the offset below calltrap() in DDB is probably more helpful. > > #6 0xc04b532f in calltrap () at /usr/src/sys/i386/i386/exception.s:774 > > #7 0xff807d10 in ?? () > > #8 0x00000010 in ?? () > > #9 0xff807d10 in ?? () > > #10 0xc18fa694 in ?? () > > #11 0x00000010 in ?? () > > #12 0x00000000 in ?? () > > #13 0x00000001 in ?? () > > #14 0x00000000 in ?? () > > #15 0xc0724b24 in AcpiGbl_BitRegisterInfo () > > ---Type <return> to continue, or q <return> to quit--- > > #16 0xff807d40 in ?? () > > #17 0xc07026b3 in AcpiGetRegister (RegisterId=0, ReturnValue=0x0, Flags=0) > > at > > /usr/src/sys/dev/acpica5/../../contrib/dev/acpica-unix-20050309/hardware/hwregs.c:381
