On Fri, Oct 1, 2010 at 3:52 AM, Tushar Dadlani <tush726@xxxxxxxxx> wrote: > Hi, > What is the best way to debug a kernel oops message? I see some call > trace , and some memory addresses , but I am not able to figure out > the main reason for my module to fail. Most useful data that I have found is the code data that is sprayed. Have a look at below thread. It might help http://kerneltrap.org/mailarchive/linux-kernel-newbies/2009/9/2/6373273/thread > > Regards, > > -- > Tushar Dadlani > Manipal Institute of Technology > +919986292434 > > -- > To unsubscribe from this list: send an email with > "unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx > Please read the FAQ at http://kernelnewbies.org/FAQ > > -- Thanks - Manish ================================== [$\*.^ -- I miss being one of them ================================== -- To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx Please read the FAQ at http://kernelnewbies.org/FAQ
