Re: FS_ENET ERROR(s) 0x12 at second NFS RPC port lookup (100005/1)

["Remi Lefevre" <rlefevre@gmail.com>]

Scott Wood  wrote:
>>
>> [    5.573391] fs_enet: eth0 FS_ENET ERROR(s) 0x12
>
> This is a transmit error; more detail can be found in the buffer descript=
or.
>
> Check your pin and clock configuration.

Thanks Scott,

Errors encountered are "Underrun" errors (from bd).
A "do_restart" in the driver is then tried, but this has no effect.

I'm pretty confident about my pin configuration as:
- I have exactly the same behavior on other FCC devices
- They work fine in U-Boot TFTP transfers
- FCC2 pins for example are identical to ep8248e ones included in the kerne=
l

I also think that cpm2_clk_setup calls are correct (and commenting them to =
keep
the configuration set by U-Boot leads to the same results).

Concerning clocks, they are identical to U-Boot ones:
Bus clock =3D 82.944 MHz

[    0.000000] time_init: decrementer frequency =3D 20.736000 MHz
[    0.000000] time_init: processor frequency   =3D 414.720000 MHz
[    0.000000] clocksource: timebase mult[c0e6b75] shift[22] registered
[    0.000000] clockevent: decrementer mult[54e] shift[16] cpu[0]
[    0.000351] cpm-brg clock frequency =3D 36.288000 MHz
[    0.554442] Calibrating delay loop... 41.34 BogoMIPS (lpj=3D82688)

CPM clock-frequency is not defined in the DTS, neither filled by U-Boot,
but it doesn't seem to be needed, does it ?

I'm a little confused, and find strange that the first UDP request complete=
s
correctly, as well as latter ARP ones.

R=E9mi