On Fri, Oct 1, 2010 at 17:52, Tushar Dadlani <tush726@xxxxxxxxx> wrote: > Hi, > What is the best way to debug a kernel oops message? Same thing like you debug casual user space program. You need to focus on the EIP it pointed. It should be pointing the last instruction that might cause the problem. use gdb to trace that. You might also need to pay attention on stack trace, that is the function call chain. More than often, the root cause is not in the last code it executes, but somewhere in function call chain...so you need to work on some logic here. All in all, you better compile your kernel with debug info..or use existing debug info package from your distro repository if you're using stock prebuilt kernel from your distro. -- regards, Mulyadi Santosa Freelance Linux trainer and consultant blog: the-hydra.blogspot.com training: mulyaditraining.blogspot.com -- To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx Please read the FAQ at http://kernelnewbies.org/FAQ
