Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 30 Jul 2006 23:25:21 +0000 (UTC)
From:      Bill Paul <wpaul@FreeBSD.org>
To:        src-committers@FreeBSD.org, cvs-src@FreeBSD.org, cvs-all@FreeBSD.org
Subject:   cvs commit: src/sys/pci if_rlreg.h src/sys/dev/re if_re.c
Message-ID:  <200607302325.k6UNPLvw023548@repoman.freebsd.org>

next in thread | raw e-mail | index | archive | help
wpaul       2006-07-30 23:25:21 UTC

  FreeBSD src repository

  Modified files:
    sys/pci              if_rlreg.h 
    sys/dev/re           if_re.c 
  Log:
  Fix the following bugs in re(4)
  
  - Correct the PCI ID for the 8169SC/8110SC in the device list (I added
    the macro for it to if_rlreg.h before, but forgot to use it.)
  
  - Remove the extra interrupt spinlock I added previously. After giving it
    some more thought, it's not really needed.
  
  - Work around a hardware bug in some versions of the 8169. When sending
    very small IP datagrams with checksum offload enabled, a conflict can
    occur between the TX autopadding feature and the hardware checksumming
    that can corrupt the outbound packet. This is the reason that checksum
    offload sometimes breaks NFS: if you're using NFS over UDP, and you're
    very unlucky, you might find yourself doing a fragmented NFS write where
    the last fragment is smaller than the minimum ethernet frame size (60
    bytes). (It's rare, but if you keep NFS running long enough it'll
    happen.) If checksum offload is enabled, the chip will have to both
    autopad the fragment and calculate its checksum header. This confuses
    some revs of the 8169, causing the packet that appears on the wire
    to be corrupted. (The IP addresses and the checksum field are mangled.)
    This will cause the NFS write to fail. Unfortunately, when NFS retries,
    it sends the same write request over and over again, and it keeps
    failing, so NFS stays wedged.
  
    (A simple way to provoke the failure is to connect the failing system
    to a network with a known good machine and do "ping -s 1473 <badhost>"
    from the good system. The ping will fail.)
  
    Someone had previously worked around this using the heavy-handed
    approahch of just disabling checksum offload. The correct fix is to
    manually pad short frames where the TCP/IP stack has requested
    checksum offloading. This allows us to have checksum offload turned
    on by default but still let NFS work right.
  
  - Not a bug, but change the ID strings for devices with hardware rev
    0x30000000 and 0x38000000 to both be 8168B/8111B. According to RealTek,
    they're both the same device, but 0x30000000 is an earlier silicon spin.
  
  Revision  Changes    Path
  1.70      +32 -21    src/sys/dev/re/if_re.c
  1.59      +19 -19    src/sys/pci/if_rlreg.h



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200607302325.k6UNPLvw023548>