Hi... On Thu, Apr 23, 2009 at 2:29 PM, amit mehta <ami...@gmail.com> wrote: > Thanks for your replies, i just wanted to know how to debug > such kernel OOPS, Forget about this particular OOPS, i just wanted to know > how you proceed further when you get something similar. As Ramesh told, > 'ksymoops' can be > helpful.
AFAIK, ksymoops is no longer needed since you already see symbols in the oops message itself. Therefore, the tasks left are locating the offending instructions that (might) cause the trouble. The hex numbers are the offset of the function currently executed by the processor. regards, Mulyadi. -- To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to ecar...@nl.linux.org Please read the FAQ at http://kernelnewbies.org/FAQ
