<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 07/04/2013 12:24 AM, Peter Teoh
wrote:<br>
</div>
<blockquote
cite="mid:CAHnt0GUKhY1YDuMq6rZYRvFBdF1apMJvaesK1Rb0iafUNRwJEA@mail.gmail.com"
type="cite">any kernel debugging always start with dmesg output,
please provide a snapshot of that. (preferably posting full
listing at <a moz-do-not-send="true" 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 moz-do-not-send="true"
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 moz-do-not-send="true"
href="mailto:Kernelnewbies@kernelnewbies.org">Kernelnewbies@kernelnewbies.org</a><br>
<a moz-do-not-send="true"
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
</blockquote>
Was a hardware problem... <br>
dmesg won't show anything .. We know that the file get corrupted
because why try to exctract the jar file and get an error like (not
a valid zip/jar file).. <br>
<br>
Since we use SoMs, we test the same module(the little board) on
another hardware (the official development kit) and it works without
problems.<br>
<br>
Since is not broken, but out of specification.. it works for some
time then starts to do bad things...<br>
<br>
I enabled mmc debug, got a lot of output but no error.. bad CRC or
something like that.. I think that configuration (since is for
embedded system) is too silent..<br>
<br>
Thanks <br>
Cheers!<br>
</body>
</html>