Hi,
After booting, my MPC8641 based board keeps printing "Trying 10/HALF"
for ever. I am unable to use the Ethernet, even though there are
interrupts occuring. Based on /proc/interrupts, both tx and rx interrupt
count is increasing, and zero count for enet_error interrupt.
I think this is coming from drivers/net/phy/phy.c during
autonegotiation. However, I am not sure how to take care of this.
Appreciate some pointers.
Thanks
Siva
On Jan 9, 2008, at 13:35, Siva Prasad wrote:
Hi,
After booting, my MPC8641 based board keeps printing =93Trying 10/=20
HALF=94 for ever. I am unable to use the Ethernet, even though there =20=
are interrupts occuring. Based on /proc/interrupts, both tx and rx =20
interrupt count is increasing, and zero count for enet_error =20
interrupt.
I think this is coming from drivers/net/phy/phy.c during =20
autonegotiation. However, I am not sure how to take care of this. =20
Appreciate some pointers.
Hm. That's a bit strange. What kind of PHY are you using? The PHY =20
layer acts like that if auto-negotiation fails and it couldn't =20
establish a link using any other method.
Some things to double-check:
* Are your etsec interrupts correct in your dts. Shouldn't be an =20
issue, but if you copied them from the wrong place, or used an out-of-=20=
date dts, the numbers could be wrong
* Are your PHY interrupts correct in your dts. If the PHY interrupts =20=
are wrong, the PHY Lib might never discover that a link was established
Andy=