* When will unwind_backtrace end?
@ 2012-10-12 6:53 Richard Zhao
0 siblings, 0 replies; only message in thread
From: Richard Zhao @ 2012-10-12 6:53 UTC (permalink / raw)
To: linux-arm-kernel
Hi there,
kernel 3.0.35, memory begin from 0x80000000, which happens to be same
as virtual address.
When enable CONFIG_LOCKDEP, it keep printing
unwind: Unknown symbol address 80008040
unwind: Index not found 80008040
unwind: Unknown symbol address 80008040
unwind: Index not found 80008040
unwind: Unknown symbol address 80008040
unwind: Index not found 80008040
unwind: Unknown symbol address 80008040
I did some investigation. It looks like:
unwind_frame didn't fail at:
if (!kernel_text_address(frame->pc))
return -URC_FAILURE;
When it backtrace to 0x80008040, it took it as kernel text address.
But it's a physical address, which point to
"1: b __enable_mmu" in stext.
Is it a known issue?
Thanks
Richard
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2012-10-12 6:53 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-10-12 6:53 When will unwind_backtrace end? Richard Zhao
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).