YONETANI Tomokazu <[EMAIL PROTECTED]> wrote:
> Hmm, db_print_backtrace() should print the backtrace, but it may not be
> very useful if you can't use the keyboard and the trace is too deep.
>
>> So I suspect that there is something wrong with the debugging code.
>> Does function tracing work for you?
>
> Yes, with or without ACPI_DEBUG_{LOCKS,MEMMAP}
> (but the message buffer is too short to hold the whole trace).
> http://les.ath.cx/DragonFly/dmesg.boot
>
> Cheers.
Just an update. It seems that after a while it does not return from
Status = WalkState->DescendingCallback (WalkState, Op);
in interpreter/parser/psloop.c:AcpiPsBuildNamedOp.
BTW, is there a way to enable more verbose logging, so that all
ACPI_FUNCTION_TRACE_PTR() calls would give some output. That way
I could avoid adding all those kprintfs.
Johannes
