Date: Sat, 14 Mar 2015 03:15:42 -0400 From: Brett Wynkoop <freebsd-arm@wynn.com> To: Tim Kientzle <tim@kientzle.com> Cc: freebsd-arm <freebsd-arm@freebsd.org> Subject: Re: BeagleBone slow inbound net I/O Message-ID: <20150314031542.439cdee3@ivory.wynn.com> In-Reply-To: <89CEBFCA-6B94-4F48-8DFD-790E4667632D@kientzle.com> References: <20150311165115.32327c5a@ivory.wynn.com> <89CEBFCA-6B94-4F48-8DFD-790E4667632D@kientzle.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 13 Mar 2015 23:02:25 -0700 Tim Kientzle <tim@kientzle.com> wrote: > > > On Mar 11, 2015, at 1:51 PM, Brett Wynkoop <freebsd-arm@wynn.com> > > wrote: > > > > Have I managed to find a network driver issue? Any ideas how to > > gather more information to help get to the bottom of things? > > > > $ sysctl dev.cpsw > > This will dump detailed statistics from the Ethernet hardware and > driver. > > Tim > After a short time while doing nfs i/o [wynkoop@beaglebone ~]$ sysctl dev.cpsw | grep -i error dev.cpsw.0.stats.RxCrcErrors: 40 dev.cpsw.0.stats.RxAlignErrors: 32 dev.cpsw.0.stats.CarrierSenseErrors: 0 [wynkoop@beaglebone ~]$ sysctl dev.cpsw | grep -i error dev.cpsw.0.stats.RxCrcErrors: 40 dev.cpsw.0.stats.RxAlignErrors: 32 dev.cpsw.0.stats.CarrierSenseErrors: 0 [wynkoop@beaglebone ~]$ sysctl dev.cpsw | grep -i error dev.cpsw.0.stats.RxCrcErrors: 40 dev.cpsw.0.stats.RxAlignErrors: 32 dev.cpsw.0.stats.CarrierSenseErrors: 0 [wynkoop@beaglebone ~]$ sysctl dev.cpsw | grep -i error dev.cpsw.0.stats.RxCrcErrors: 40 dev.cpsw.0.stats.RxAlignErrors: 32 dev.cpsw.0.stats.CarrierSenseErrors: 0 [wynkoop@beaglebone ~]$ sysctl dev.cpsw | grep -i error dev.cpsw.0.stats.RxCrcErrors: 40 dev.cpsw.0.stats.RxAlignErrors: 32 dev.cpsw.0.stats.CarrierSenseErrors: 0 [wynkoop@beaglebone ~]$ sysctl dev.cpsw | grep -i error dev.cpsw.0.stats.RxCrcErrors: 43 dev.cpsw.0.stats.RxAlignErrors: 32 dev.cpsw.0.stats.CarrierSenseErrors: 0 [wynkoop@beaglebone ~]$ sysctl dev.cpsw | grep -i error dev.cpsw.0.stats.RxCrcErrors: 43 dev.cpsw.0.stats.RxAlignErrors: 32 dev.cpsw.0.stats.CarrierSenseErrors: 0 [wynkoop@beaglebone ~]$ sysctl dev.cpsw | grep -i error dev.cpsw.0.stats.RxCrcErrors: 54 dev.cpsw.0.stats.RxAlignErrors: 36 dev.cpsw.0.stats.CarrierSenseErrors: 0 [wynkoop@beaglebone ~]$ sysctl dev.cpsw | grep -i error dev.cpsw.0.stats.RxCrcErrors: 59 dev.cpsw.0.stats.RxAlignErrors: 40 dev.cpsw.0.stats.CarrierSenseErrors: 0 [wynkoop@beaglebone ~]$ sysctl dev.cpsw | grep -i error dev.cpsw.0.stats.RxCrcErrors: 64 dev.cpsw.0.stats.RxAlignErrors: 48 dev.cpsw.0.stats.CarrierSenseErrors: 0 [wynkoop@beaglebone ~]$ sysctl dev.cpsw | grep -i error dev.cpsw.0.stats.RxCrcErrors: 66 dev.cpsw.0.stats.RxAlignErrors: 50 dev.cpsw.0.stats.CarrierSenseErrors: 0 [wynkoop@beaglebone ~]$ sysctl dev.cpsw | grep -i error dev.cpsw.0.stats.RxCrcErrors: 67 dev.cpsw.0.stats.RxAlignErrors: 53 dev.cpsw.0.stats.CarrierSenseErrors: 0 [wynkoop@beaglebone ~]$ sysctl dev.cpsw | grep -i error dev.cpsw.0.stats.RxCrcErrors: 67 dev.cpsw.0.stats.RxAlignErrors: 53 dev.cpsw.0.stats.CarrierSenseErrors: 0 .... [wynkoop@beaglebone ~]$ sysctl dev.cpsw | grep -i error dev.cpsw.0.stats.RxCrcErrors: 172 dev.cpsw.0.stats.RxAlignErrors: 141 dev.cpsw.0.stats.CarrierSenseErrors: 0 [wynkoop@beaglebone ~]$ ..... [wynkoop@beaglebone ~]$ sysctl dev.cpsw | grep -i error dev.cpsw.0.stats.RxCrcErrors: 262 dev.cpsw.0.stats.RxAlignErrors: 231 dev.cpsw.0.stats.CarrierSenseErrors: 0 [wynkoop@beaglebone ~]$ So we can see climbing errors. I am not sure how this compares to the results of others. The above was during the first few minutes of a buildworld from an nfs share. At the same time on the console: Mar 14 03:07:47 beaglebone amd[1163]: mountd rpc failed: RPC: Can't decode result Mar 14 03:11:48 beaglebone amd[1399]: mountd rpc failed: RPC: Can't decode result which makes sense with the above errors I think. -Brett -- wynkoop@wynn.com http://prd4.wynn.com/wynkoop/pgp-keys.txt 917-642-6925 929-272-0000 Amendment VIII Excessive bail shall not be required, nor excessive fines imposed, nor cruel and unusual punishments inflicted.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20150314031542.439cdee3>