> -----Original Message----- > From: Joakim Tjernlund [mailto:joakim.tjernl...@transmode.se] > > On Mon, 2015-11-02 at 19:31 +0200, Madalin Bucur wrote: > > + if (unlikely(fd_status & FM_FD_STAT_RX_ERRORS) != 0) { > > + if (net_ratelimit()) > > + netif_warn(priv, hw, net_dev, "FD status = > 0x%08x\n", > > + 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 > enough) 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 > past diagnosing > board HW problems. > > Jocke
Hi Jocke, There are some error counters exported through ethtool (used to be debugfs). FMan HW provides more debug information than we currently export, that will be improved in the future but given the current priority of having a codebase as small and reviewable as possible we had to drop some things from the initial submission. Madalin -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
