1. 10 7月, 2012 6 次提交
  2. 23 6月, 2012 1 次提交
    • F
      r8169: RxConfig hack for the 8168evl. · eb2dc35d
      françois romieu 提交于
      The 8168evl (RTL_GIGA_MAC_VER_34) based Gigabyte GA-990FXA motherboards
      are very prone to NETDEV watchdog problems without this change. See
      https://bugzilla.kernel.org/show_bug.cgi?id=42899 for instance.
      
      I don't know why it *works*. It's depressingly effective though.
      
      For the record:
      - the problem may go along IOMMU (AMD-Vi) errors but it really looks
        like a red herring.
      - the patch sets the RX_MULTI_EN bit. If the 8168c doc is any guide,
        the chipset now fetches several Rx descriptors at a time.
      - long ago the driver ignored the RX_MULTI_EN bit.
        e542a226 changed the RxConfig
        settings. Whatever the problem it's now labeled a regression.
      - Realtek's own driver can identify two different 8168evl devices
        (CFG_METHOD_16 and CFG_METHOD_17) where the r8169 driver only
        sees one. It sucks.
      Signed-off-by: NFrancois Romieu <romieu@fr.zoreil.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      eb2dc35d
  3. 11 6月, 2012 1 次提交
    • F
      r8169: avoid NAPI scheduling delay. · 7dbb4918
      françois romieu 提交于
      While reworking the r8169 driver a few months ago to perform the
      smallest amount of work in the irq handler, I took care of avoiding
      any irq mask register operation in the slow work dedicated user
      context thread. The slow work thread scheduled an extra round of NAPI
      work which would ultimately set the irq mask register as required,
      thus keeping such irq mask operations in the NAPI handler.
      It would eventually race with the irq handler and delay NAPI execution
      for - assuming no further irq - a whole ksoftirqd period. Mildly a
      problem for rare link changes or corner case PCI events.
      
      The race was always lost after the last bh disabling lock had been
      removed from the work thread and people started wondering where those
      pesky "NOHZ: local_softirq_pending 08" messages came from.
      
      Actually the irq mask register _can_ be set up directly in the slow
      work thread.
      Signed-off-by: NFrancois Romieu <romieu@fr.zoreil.com>
      Reported-by: NDave Jones <davej@redhat.com>
      Tested-by: NMarc Dionne <marc.c.dionne@gmail.com>
      Cc: Thomas Gleixner <tglx@linutronix.de>
      Cc: Hayes Wang <hayeswang@realtek.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      7dbb4918
  4. 02 6月, 2012 1 次提交
  5. 09 5月, 2012 1 次提交
  6. 17 4月, 2012 7 次提交
  7. 04 4月, 2012 2 次提交
  8. 29 3月, 2012 1 次提交
  9. 28 3月, 2012 1 次提交
  10. 12 3月, 2012 1 次提交
  11. 11 3月, 2012 8 次提交
  12. 07 3月, 2012 1 次提交
    • F
      r8169: runtime resume before shutdown. · 2a15cd2f
      françois romieu 提交于
      With runtime PM, if the ethernet cable is disconnected, the device is
      transitioned to D3 state to conserve energy. If the system is shutdown
      in this state, any register accesses in rtl_shutdown are dropped on
      the floor. As the device was programmed by .runtime_suspend() to wake
      on link changes, it is thus brought back up as soon as the link recovers.
      
      Resuming every suspended device through the driver core would slow things
      down and it is not clear how many devices really need it now.
      
      Original report and D0 transition patch by Sameer Nanda. Patch has been
      changed to comply with advices by Rafael J. Wysocki and the PM folks.
      Reported-by: NSameer Nanda <snanda@chromium.org>
      Signed-off-by: NFrancois Romieu <romieu@fr.zoreil.com>
      Cc: Rafael J. Wysocki <rjw@sisk.pl>
      Cc: Hayes Wang <hayeswang@realtek.com>
      Cc: Alan Stern <stern@rowland.harvard.edu>
      Acked-by: NRafael J. Wysocki <rjw@sisk.pl>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      2a15cd2f
  13. 06 3月, 2012 2 次提交
  14. 03 3月, 2012 1 次提交
  15. 24 2月, 2012 2 次提交
  16. 01 2月, 2012 1 次提交
  17. 31 1月, 2012 3 次提交