<html><head><meta content="text/html; charset=iso-8859-1" http-equiv="Content-Type"></head><body><div><div style="font-family: Calibri,sans-serif; font-size: 11pt;">Try using strace and see if all of the different crashes have the same or similar looking call stack.<br><br>Here's a link on how to use it in case you didn't know already: http://stackoverflow.com/questions/174942/how-to-use-strace<br></div></div><hr><span style="font-family: Tahoma,sans-serif; font-size: 10pt; font-weight: bold;">From: </span><span style="font-family: Tahoma,sans-serif; font-size: 10pt;">manty kuma</span><br><span style="font-family: Tahoma,sans-serif; font-size: 10pt; font-weight: bold;">Sent: </span><span style="font-family: Tahoma,sans-serif; font-size: 10pt;">7/7/2013 8:06 PM</span><br><span style="font-family: Tahoma,sans-serif; font-size: 10pt; font-weight: bold;">To: </span><span style="font-family: Tahoma,sans-serif; font-size: 10pt;">Valdis Kletnieks</span><br><span style="font-family: Tahoma,sans-serif; font-size: 10pt; font-weight: bold;">Cc: </span><span style="font-family: Tahoma,sans-serif; font-size: 10pt;">kernelnewbies@kernelnewbies.org</span><br><span style="font-family: Tahoma,sans-serif; font-size: 10pt; font-weight: bold;">Subject: </span><span style="font-family: Tahoma,sans-serif; font-size: 10pt;">Re: Debugging techniques inside kernel</span><br><br><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 style="margin: 0px 0px 0px 0.8ex; padding-left: 1ex; border-left-color: rgb(204, 204, 204); border-left-width: 1px; border-left-style: solid;" class="gmail_quote">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>
</body></html>