Geoffrey Bugniot gmail.com> writes:
>
> Scott Wood freescale.com> writes:
>
> Could you have bad memory timings (or bad memory)? Usually when I see
> things like this, it's because memory is getting corrupted.
>
OK, I've found the problem and you were right Scott. RAM chip and 60x BUS
were
Scott Wood freescale.com> writes:
>
> On 07/23/2012 10:34 AM, Geoffrey Bugniot wrote:
> > I got something like that :
> > [ 148.891584] Kernel panic - not syncing: Attempted to kill init!
>
> Was there anything before this?
>
No, that's the complete dump.
> > [ 148.897503] Call Trace:
> >
On 07/23/2012 10:34 AM, Geoffrey Bugniot wrote:
> Hi,
>
> I've ported on a custom board U-Boot and Linux 2.6.39.4. It seems to work
> well until the kernel is begin to manipulate "data/file" with a size larger
> than about 5 Mo. I suppose that's a VM management problem, but I'm not
> sure.
>
> In
Hi,
I've ported on a custom board U-Boot and Linux 2.6.39.4. It seems to work
well until the kernel is begin to manipulate "data/file" with a size larger
than about 5 Mo. I suppose that's a VM management problem, but I'm not
sure.
In fact, when I use "cp file1 file2" with file1 >= 5/6 Mo, the ker
