On Mon, Apr 24, 2017 at 05:13:45PM +0100, Robert Swindells wrote: > > Patrick Welche <[email protected]> wrote: > >The "file corruption" problem seems to be a problem with re(4): > > [snip] > > >Instead of using > > > >re0 at pci3 dev 0 function 0: RealTek 8168/8111 PCIe Gigabit Ethernet (rev. > >0x07) > >re0: interrupting at msi3 vec 0 > >rgephy0 at re0 phy 7: RTL8169S/8110S/8211 1000BASE-T media interface, rev. 5 > > > >(with ip4csum etc enabled) > > > >I tried a USB wireless dongle, and the same cvs checkout over urtwm0 > >appears to be fine. (No change of kernel, no reboot.) > > Are you using IPv4 or IPv6 ? > > I don't have any suggestions on a fix, just that re(4) only seems to > have hardware acceleration for IPv4 so you will get a different path > through the network stack for the two protocols.
IPv4 I'll try -current next, given that Jared added a RTKQ_IM_HW quirk for precisely this model... Cheers, Patrick
