Debugging techniques inside kernel

[Valdis.Kletnieks at vt.edu]

On Mon, 08 Jul 2013 08:18:02 -0700, Anand Arumugam said:

> Try using strace and see if all of the different crashes have the same or similar looking call stack.

strace is userspace, and *highly* unlikely to track down random memory
corruption inside the kernel.  Random kernel corruption usually means that something
*else* stomped on the memory - which in turn means that the syscall that
finally trips over the corrupt memory is probably not the one that did it.

Not saying it can't possibly do so, but it's not where I'd start.

Might want to run memtest86+ or similar, help rule out dodgy memory.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 865 bytes
Desc: not available
Url : http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20130708/78a650ab/attachment.bin