any kernel debugging always start with dmesg output, please provide a snapshot of that. (preferably posting full listing at <a href="http://pastebin.com">pastebin.com</a>).<br><br><div class="gmail_quote">On Tue, Jun 25, 2013 at 4:08 AM, Daniel Hilst Selli <span dir="ltr"><<a href="mailto:danielhilst@gmail.com" target="_blank">danielhilst@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I'm working on an embedded project based on var-som-am35 from TI. [1]<br>
<br>
I experiencing a lot of corruption from files and even the entire<br>
filesystem... is there any guide on how debug filesystems corruption?<br>
<br>
We already tryied vfat and ext3 fs.. changed media, changed machines...<br>
The filesystem runs on mmc card, or on usb flash drive... There is a<br>
java aplication running on top of this filesystem, which uses JMS, that<br>
is very I/O agressive..<br>
<br>
Cheers,<br>
<br>
_______________________________________________<br>
Kernelnewbies mailing list<br>
<a href="mailto:Kernelnewbies@kernelnewbies.org">Kernelnewbies@kernelnewbies.org</a><br>
<a href="http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies" target="_blank">http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies</a><br>
</blockquote></div><br><br clear="all"><div><br></div>-- <br>Regards,<br>Peter Teoh