Amit, I suggest you to read the "oops messages" part of the document shown in the link of the previous mail. Oops messages give crucial clues in order to debug the crashes. Find out the crash point from the oops output, then trace it via objdump. Other utilities, including jtag, *at most* do not work sanely. Thus, you have to be patient and intuitive while debugging :) BTW, please keep in mind that printk() affects the timing of the crash so it should not be used ASAP.
HTH. On 19 Haz 2011, at 18:22, Amit Nagal <[email protected]> wrote: > On Sun, Jun 19, 2011 at 5:31 PM, Metin KAYA <[email protected]> wrote: >> - Enable CONFIG_KALLSYMS in kernel configuration. >> - And the rest is here: http://www.xml.com/ldd/chapter/book/ch04.html >> Regards. >> > > Thanx for all the replies and facts . Actually my main concern is > regarding identifying kernel panics and system hangs > on embedded arm targets where i have access to only one serial port > used primarily for reporting debug messages . > > Also wrt x86 , i tried to use gdb - kgdb interface using 2 PCs , but > communication used to break too often . > > Then i tried ftrace which i found quite convinient to use on x86 till > now except sometimes when ftrace takes too much time to print > complete trace on console in case of crash . > > Can crash utility be used for arm targets as well ? > > Regards > Amit Nagal _______________________________________________ Kernelnewbies mailing list [email protected] http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
