1. 10 7月, 2014 1 次提交
  2. 14 5月, 2014 1 次提交
  3. 15 3月, 2014 1 次提交
  4. 13 3月, 2014 1 次提交
  5. 12 3月, 2014 1 次提交
  6. 25 2月, 2014 1 次提交
    • K
      r8169: initialize rtl8169_stats seqlock · 340fea3d
      Kyle McMartin 提交于
      Boris reports he's seeing:
      > [    9.195943] INFO: trying to register non-static key.
      > [    9.196031] the code is fine but needs lockdep annotation.
      > [    9.196031] turning off the locking correctness validator.
      > [    9.196031] CPU: 1 PID: 933 Comm: modprobe Not tainted 3.14.0-rc4+ #1
      with the r8169 driver.
      
      These are occuring because the seqcount embedded in u64_stats_sync on
      32-bit SMP is uninitialized which is making lockdep unhappy.
      Signed-off-by: NKyle McMartin <kyle@redhat.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      340fea3d
  7. 17 1月, 2014 1 次提交
  8. 30 11月, 2013 1 次提交
  9. 22 10月, 2013 1 次提交
  10. 12 9月, 2013 1 次提交
  11. 23 8月, 2013 1 次提交
  12. 21 8月, 2013 2 次提交
  13. 03 8月, 2013 1 次提交
  14. 25 7月, 2013 1 次提交
  15. 11 7月, 2013 1 次提交
  16. 20 5月, 2013 1 次提交
  17. 30 4月, 2013 1 次提交
  18. 20 4月, 2013 2 次提交
  19. 08 4月, 2013 8 次提交
  20. 05 4月, 2013 1 次提交
  21. 01 3月, 2013 1 次提交
  22. 09 2月, 2013 2 次提交
  23. 28 1月, 2013 1 次提交
  24. 24 1月, 2013 1 次提交
    • T
      r8169: remove the obsolete and incorrect AMD workaround · 5d0feaff
      Timo Teräs 提交于
      This was introduced in commit 6dccd16b "r8169: merge with version
      6.001.00 of Realtek's r8169 driver". I did not find the version
      6.001.00 online, but in 6.002.00 or any later r8169 from Realtek
      this hunk is no longer present.
      
      Also commit 05af2142 "r8169: fix Ethernet Hangup for RTL8110SC
      rev d" claims to have fixed this issue otherwise.
      
      The magic compare mask of 0xfffe000 is dubious as it masks
      parts of the Reserved part, and parts of the VLAN tag. But this
      does not make much sense as the VLAN tag parts are perfectly
      valid there. In matter of fact this seems to be triggered with
      any VLAN tagged packet as RxVlanTag bit is matched. I would
      suspect 0xfffe0000 was intended to test reserved part only.
      
      Finally, this hunk is evil as it can cause more packets to be
      handled than what was NAPI quota causing net/core/dev.c:
      net_rx_action(): WARN_ON_ONCE(work > weight) to trigger, and
      mess up the NAPI state causing device to hang.
      
      As result, any system using VLANs and having high receive
      traffic (so that NAPI poll budget limits rtl_rx) would result
      in device hang.
      Signed-off-by: NTimo Teräs <timo.teras@iki.fi>
      Acked-by: NFrancois Romieu <romieu@fr.zoreil.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      5d0feaff
  25. 17 1月, 2013 1 次提交
  26. 09 1月, 2013 1 次提交
  27. 09 12月, 2012 1 次提交
  28. 04 12月, 2012 1 次提交
  29. 12 11月, 2012 2 次提交