> >>> The r8152 driver has been broken since (approx) 3.16.xx > >>> when support was added for hardware RX checksums > >>> on newer chip versions. Symptoms include random > >>> segfaults and silent data corruption over NFS. > >>> > >>> The hardware checksum logig does not work on the VER_02 > >>> dongles I have here when used with a slow embedded system CPU. > >>> Google reveals others reporting similar issues on Raspberry Pi. > >>> > >>> So, disable hardware RX checksum support for VER_02, and fix > >>> an obvious coding error for IPV6 checksums in the same function. > >>> > >>> Because this bug results in silent data corruption, > >>> it is a good candidate for back-porting to -stable >= 3.16.xx. > >>> > >>> Signed-off-by: Mark Lord <[email protected]> > >> > >> Applied and queued up for -stable, thanks. > > > > Thanks. Now that this is taken care of, I do wonder if perhaps > > RX checksums ought to be enabled at all for ANY versions of this chip? > > You should really start a dialogue with the developer who has been > making the most, if not all, of the major changes to this driver over > the past few years, Hayes Wang.
Our hw engineer says only VER_01 has the issue about rx checksum. I need more information for checking it. Best Regards, Hayes
