<div dir="ltr"><div>Hi Valdis,<br><br></div>Thanks for the info. I have serial logs (using minicom). This is not helping me much as randomly memory is getting crashed and everytime it changes. Even the logs before the crash are varying everytime. <br>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Jul 8, 2013 at 11:49 AM, <span dir="ltr"><<a href="mailto:Valdis.Kletnieks@vt.edu" target="_blank">Valdis.Kletnieks@vt.edu</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Mon, 08 Jul 2013 11:22:16 +0900, manty kuma said:<br>
<br>
> For ex : *CONFIG_SLUB_DEBUG_ON, *CONFIG_DMA_API_DEBUG<br>
<div class="im">> I am just told to use these configs and check. Not sure how to use them<br>
> effectively. Please share if you are aware of these kind of configs and how<br>
> to use them. To have them at one place it would be useful for debugging<br>
> beginners like me.<br>
<br>
</div>Most _DEBUG config options are set-and-forget - you turn them on and<br>
there's no further configuration needed. They enable additional code<br>
that does additional sanity checking and if it finds a problem, it issues<br>
a printk() or a stack dump or similar which shows up in dmesg.<br>
<br>
If you're chasing memory corruption, it may be useful to use netconsole<br>
or a serial console to send out all the printk() output in real time, as<br>
often an error will be detected but the system will panic()/crash/hang<br>
in a way that your local syslog daemon is unable to write the message to<br>
disk. (I'm told that on newer UEFI based systems, you can use pstore in<br>
a similar fashion, but have not tried it myself yet).<br>
<br>
</blockquote></div><br></div>