Sean McNeil wrote:
I'm now trying to see if I can monitor and capture what it is doing
via. JTAG. It doesn't look like this is possible, though. All is ok up
until it goes into suspend. I can ctrl-c and see whats going on:
Program received signal SIGINT, Interrupt.
s3c24xx_default_idle () at include/asm/arch/system.h:41
41 for (i = 0; i < 50; i++) {
(gdb) bt
#0 s3c24xx_default_idle () at include/asm/arch/system.h:41
#1 0xc0063278 in default_idle () at include/asm/arch/system.h:56
#2 0xc0062fb8 in cpu_idle () at arch/arm/kernel/process.c:170
#3 0xc0329b2c in rest_init () at init/main.c:453
#4 0xc0008d18 in start_kernel () at init/main.c:648
#5 0x30008034 in ?? ()
(gdb) c
Continuing.
but when it suspends I get
timeout waiting for SYSCOMP & DBGACK, last DBG_STATUS: 0
timeout waiting for SYSCOMP & DBGACK, last DBG_STATUS: 0
timeout waiting for SYSCOMP & DBGACK, last DBG_STATUS: 0
timeout waiting for SYSCOMP & DBGACK, last DBG_STATUS: 0
Program received signal SIGTRAP, Trace/breakpoint trap.
0xffffffec in ?? ()
and then its pretty much dead.
I think this all might be related to printk calls during suspend/resume.
When the unit freezes up I get:
(gdb) c
Continuing.
Program received signal SIGINT, Interrupt.
vprintk (fmt=0xc7c43de8 "\034>??", args=0xc7c43dfc)
at include/asm/thread_info.h:94
94 return (struct thread_info *)(sp & ~(THREAD_SIZE - 1));
(gdb) bt
#0 vprintk (fmt=0xc7c43de8 "\034>??", args=0xc7c43dfc)
at include/asm/thread_info.h:94
#1 0xc00798cc in vprintk (fmt=0xc7c43de8 "\034>??", args=0xc7c43dfc)
at kernel/printk.c:755
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
I don't know if this is legit or not (the debug info). I waited until
the unit wouldn't respond anymore then attached the debugger. Then I did
the "c" and ctrl-c above.