On Mon, 2015-11-02 at 19:31 +0200, Madalin Bucur wrote:
quoted hunk ↗ jump to hunk
+ if (unlikely(fd_status & FM_FD_STAT_RX_ERRORS) !=3D 0) {
+ if (net_ratelimit())
+ netif_warn(priv, hw, net_dev, "FD status =3D 0x%0=
8x\n",
quoted hunk ↗ jump to hunk
+ fd_status & FM_FD_STAT_RX_ERRORS);
+
+ percpu_stats->rx_errors++;
+ goto _release_frame;
+ }
I cannot find any detailed error accounting(maybe I am not looking hard eno=
ugh) but I
would appreciate if both TX and RX errors where better accounted(rx_length_=
errors, rx_frame_errors,
rx_crc_errors, rx_fifo_errors etc.). This has helped me many times in the p=
ast diagnosing
board HW problems.
Jocke=