1) Yes, this is the custom board. Same I could not see on replicated on freescale (t1040qds) board.

2) We saw the same in two boards.

3) We are using mac-4 for tftp.Other ports are unused .

4) We are using freescale SDK 1.4.

5) Currently I am seeing this issue while tftp only. Other application where eth port is not used is not showing error. We tested DDR with walkimg 1 algo but it does not show any error. I will recheck the DDR error registers after crash and update you.

Attachments

Just now I checked your Kernel configuration file, it is very different with the default configuration file, especially missing QMAN, BMAN configurations, actually the function "portal_isr" is BMAN Portal interrupt handler.

I suggest you perform the modification based on the default Kernel configuration.

You could get Kernel configuration file(.config) in the source code folder "build_t1042rdb_release/tmp/work/t1042rdb-fsl-linux/linux-qoriq-sdk/3.8-r11.1/git" with the following command.

I am attaching the two config files here taken from "build_t1042rdb_release/tmp/work/t1042rdb-fsl-linux/linux-qoriq-sdk/3.8-r11.1/git" folder.

1) config_t1040.config -> this is what we are using.

2) config_t1042.config -> default file.

We modified config_t1040.config to set default baudrate to 9600 and enabled marvell phy support as our board has Marvell PHY instead of realtek PHY as in t1040qds board. Do you find anything wrong in these files?

Please check whether the following could help you to do further investigation for this problem.

1. Under u-boot, use tftp to download the testing file and compute the md5sum values, then repeat and check whether the problem will occur. If the transcending problem also can be reproduced in u-boot, probably the hardware problem needs to be considered about.

2. Please try to use other network application, for example netperf, I attached netperf related user manual to you. Please check whether Kernel call trace could occur, and at the same place.

If the Kernel call trace happens at the same place every time, I think probably the hardware unstable or DDR configuration problem could be excluded.