On Mon, Mar 04, 2013 at 11:34:55AM -0500, Dave Anderson wrote: > > crash> bt -a > > PID: 0 TASK: c097b8b0 CPU: 0 COMMAND: "swapper/0" > > bt: WARNING: cannot get stackframe for task > > > > PID: 0 TASK: dc84ca40 CPU: 1 COMMAND: "swapper/1" > > bt: WARNING: cannot get stackframe for task > > Yeah, it appears that the ARM backtrace code presumes that the dumpfile > was taken with the kernel's kdump facility, because it gets the backtrace > starting points from the register values save in the kdump "crash_notes". Right, only the mainline kernel kdump is supported. > So you might try entering "bt -t" or "bt -T". But if the cpus were > sitting in the idle state, there's probably not much to see. > > One thing I do *not* like about the ARM "bt" display is that it > does not show the stack address of each frame. But I think the > ARM maintainers did it that way to simulate the kernel's log > output. Exactly - we try to keep the resulting backtrace match what is printed to the console and to the log. -- Crash-utility mailing list Crash-utility@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/crash-utility
