Hi list, Hello Thomas, Follow up to [1] from March 2015:
Using a Readynas 102 with mainline kernel 4.2 I still see a bunch of error messages in dmesg during network transfer: mvneta d0074000.ethernet eth0: bad rx status 0f830000 (overrun error), size=1008 mvneta d0074000.ethernet eth0: bad rx status 0f830000 (overrun error), size=440 The amount of errors have decreased a lot from hundreds in natisbad kernel 4.0.5 (flooding syslog) down to just a few in my own build of mainline 4.2. kernel config I used was config-4.0.5.rn102 from [2] , mvneta is built into kernel (not module). eth0 link is up continuous at 1000 MB/s , I never see dropped links while these errors occur. My home LAN consists of gigabit cables (cat 5) and gigabit switches. I never encounter internal transmission errors other than those with the RN102 marvell driver. As Michael Langer has mentioned in [1], 3.17 of natisbad was not affected, I confirmed that with the same kernel image from [2]. System OS in use is Debian/Jessie, original Marvell u-boot from nand (September 2013) Any patches/ideas I could try to get rid of transmission errors completely? [1] https://www.marc.info/?l=linux-netdev&m=142573659929563 [2] http://natisbad.org/nas-kernels/ -- 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
