1. 22 8月, 2013 1 次提交
  2. 21 5月, 2013 3 次提交
  3. 25 4月, 2013 1 次提交
  4. 19 4月, 2013 5 次提交
  5. 16 2月, 2013 1 次提交
    • S
      igb: increase timeout for ethtool offline self-test · 4507dc9f
      Stefan Assmann 提交于
      On several machines with i350 adapters the ethtool offline self-test sometimes
      fails. This happens because link auto negotiation may take longer than the
      timeout of 4 seconds. Increasing the timeout by 1 seconds resolves the issue.
      
      Output from a failing i350 offline self-test:
      while [ 1 ]; do ethtool -t eth2 offline; done
      The test result is PASS
      The test extra info:
      Register test  (offline)         0
      Eeprom test    (offline)         0
      Interrupt test (offline)         0
      Loopback test  (offline)         0
      Link test   (on/offline)         0
      
      The test result is FAIL
      The test extra info:
      Register test  (offline)         0
      Eeprom test    (offline)         0
      Interrupt test (offline)         0
      Loopback test  (offline)         0
      Link test   (on/offline)         1
      
      The test result is PASS
      The test extra info:
      Register test  (offline)         0
      Eeprom test    (offline)         0
      Interrupt test (offline)         0
      Loopback test  (offline)         0
      Link test   (on/offline)         0
      Signed-off-by: NStefan Assmann <sassmann@kpanic.de>
      Tested-by: NAaron Brown <aaron.f.brown@intel.com>
      Signed-off-by: NJeff Kirsher <jeffrey.t.kirsher@intel.com>
      4507dc9f
  6. 19 1月, 2013 1 次提交
  7. 18 1月, 2013 3 次提交
  8. 01 12月, 2012 1 次提交
  9. 22 11月, 2012 1 次提交
  10. 14 11月, 2012 2 次提交
  11. 01 11月, 2012 1 次提交
  12. 19 10月, 2012 3 次提交
  13. 17 9月, 2012 3 次提交
  14. 05 9月, 2012 2 次提交
  15. 21 8月, 2012 1 次提交
  16. 07 8月, 2012 1 次提交
    • S
      igb: add delay to allow igb loopback test to succeed on 8086:10c9 · 119b0e03
      Stefan Assmann 提交于
      Some 8086:10c9 NICs have a problem completing the ethtool loopback test.
      The result looks like this:
      
      ethtool -t eth1
      The test result is FAIL
      The test extra info:
      Register test  (offline)         0
      Eeprom test    (offline)         0
      Interrupt test (offline)         0
      Loopback test  (offline)         13
      Link test   (on/offline)         0
      
      A bisect clearly points to commit a95a0744.
      However that seems to only trigger the bug. While adding some printk the
      problem disappeared, so this might be a timing issue. After some trial and
      error I discovered that adding a small delay just before igb_write_phy_reg()
      in igb_integrated_phy_loopback() allows the loopback test to succeed.
      I was unable to figure out the root cause so far but I expect it to be
      somewhere in the following executing path
      igb_integrated_phy_loopback
      ->igb_write_phy_reg_igp
        ->igb_write_phy_reg_mdic
          ->igb_acquire_phy_82575
            ->igb_acquire_swfw_sync_82575
      
      The problem could only be observed on 8086:10c9 NICs so far and not all
      of them show the behaviour. I did not restrict the workaround to this
      type of NIC as it should do no harm to other igb NICs.
      
      With the patch below the loopback test succeeded 500 times in a row
      using a NIC that would otherwise fail.
      Signed-off-by: NStefan Assmann <sassmann@kpanic.de>
      Tested-by: NAaron Brown <aaron.f.brown@intel.com>
      Signed-off-by: NPeter P Waskiewicz Jr <peter.p.waskiewicz.jr@intel.com>
      119b0e03
  17. 04 8月, 2012 2 次提交
  18. 20 6月, 2012 2 次提交
  19. 13 5月, 2012 1 次提交
  20. 10 5月, 2012 1 次提交
  21. 13 3月, 2012 1 次提交
  22. 20 1月, 2012 1 次提交
  23. 06 1月, 2012 1 次提交
  24. 03 1月, 2012 1 次提交