On 07/04/2013 12:24 AM, Peter Teoh wrote:
any kernel debugging always start with dmesg output, please provide a snapshot of that.   (preferably posting full listing at pastebin.com).

On Tue, Jun 25, 2013 at 4:08 AM, Daniel Hilst Selli <danielhilst@gmail.com> wrote:
I'm working on an embedded project based on var-som-am35 from TI. [1]

I experiencing a lot of corruption from files and even the entire
filesystem... is there any guide on how debug filesystems corruption?

We already tryied vfat and ext3 fs.. changed media, changed machines...
The filesystem runs on mmc card, or on usb flash drive... There is a
java aplication running on top of this filesystem, which uses JMS, that
is very I/O agressive..

Cheers,

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies



--
Regards,
Peter Teoh
Was a hardware problem...
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)..

Since we use SoMs, we test the same module(the little board) on another hardware (the official development kit) and it works without problems.

Since is not broken, but out of specification.. it works for some time then starts to do bad things...

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..

Thanks
Cheers!