On Wed, 26 Mar 2003 11:50:45 +0800,
"Dong, Edie" <[EMAIL PROTECTED]> wrote:
>Keith:
> It seems the KDBV4.0 backtrace will no longer function before =
>smp_init but it is
> OK in KDB2.5. Do you have any special considerations? It is a good =
>feature no
> matter for I386 or XScale architecture.
Works for me, booting with kdb=early
Entering kdb (current=0xe00000000470c000, pid 0) on processor 0 due to KDB_ENTER()
[0]kdb> bt
Stack traceback for pid 0
0xe00000000470c000 0 0 1 0 R 0xe00000000470c5d0 *swapper
0xe0020000006d1060 start_kernel+0x440
args (0xe0020000005fd4b0, 0x13, 0x1, 0x1, 0x3f0d2208)
kernel .text.init 0xe0020000006d0000 0xe0020000006d0c20 0xe0020000006d1200
0xe002000000008510 start_ap+0x2f0
args (0xe0020000005fd4b0, 0x13)
kernel .text 0xe002000000000000 0xe002000000008220 0xe002000000008530
[0]kdb> cpu
Currently on cpu 0
Available cpus:
