I see a similar problem on the MPC8349E MDS (V1.1 CPUs) in that the first ping or tftpboot command often doesn't work in u-boot 1.1.3 or (much less often) Wind River Linux kernel 2.6.14. The problem seems least severe on a node-to-node gigabit connection and most severe on a public 100BT network. I haven't been able to isolate the cause, but the severity seems dependent on the driver characteristics of the equipment that the 8349 is communicating with. In my case I also see very erratic ping times to the NFS server (dependent on how Kudzu configured its e1000 driver). The 8349 sometimes slows to a crawl and fills the logs with watchdog messages when it mounts NFS partitions and hits the INIT phase of boot-up. This is all with out-of-the box software from Motorola and Wind River. Maybe we will have better luck with the V3.0 CPUs? I wish I could use 2.6.18, but I'm stuck at 2.6.14. Regards, Gary
________________________________ From: [EMAIL PROTECTED] on behalf of SIP COP 009 Sent: Thu 2/22/2007 9:14 PM To: [email protected] Cc: [EMAIL PROTECTED] Subject: Gianfar on 8347 sometimes get stuck at startup We have the our own MPC8349 based board which has 2 GigEs. It is pretty much modelled similar to the 8349ADS EVAL boards, infact we have zero changes. The issue that we are seeing - Sometimes at startup, we have send 2 TX packets to kind-of-kickstart the TSEC Tranmission. If we send only packet it does not get to the other side. This does not happen always. The TSEC Registers dont really show any errors nor does the Marvell PHY show any errors. The kernel that we are using is 2.6.11. Anybody seen this before or something similar ? Any pointers will be appreciated. We cannot move to any other kernel verision right now. Thanks! ashutosh
_______________________________________________ Linuxppc-embedded mailing list [email protected] https://ozlabs.org/mailman/listinfo/linuxppc-embedded
