David Woodhouse aaa0062ecf 8139cp: Do not re-enable RX interrupts in cp_tx_timeout() ... If an RX interrupt was already received but NAPI has not yet run when the RX timeout happens, we end up in cp_tx_timeout() with RX interrupts already disabled. Blindly re-enabling them will cause an IRQ storm. (This is made particularly horrid by the fact that cp_interrupt() always returns that it's handled the interrupt, even when it hasn't actually done anything. If it didn't do that, the core IRQ code would have detected the storm and handled it, I'd have had a clear smoking gun backtrace instead of just a spontaneously resetting router, and I'd have at *least* two days of my life back. Changing the return value of cp_interrupt() will be argued about under separate cover.) Unconditionally leave RX interrupts disabled after the reset, and schedule NAPI to check the receive ring and re-enable them. Signed-off-by: David Woodhouse <David.Woodhouse@intel.com> Signed-off-by: David S. Miller <davem@davemloft.net>		2015-09-23 14:47:12 -07:00
..
8139cp.c	8139cp: Do not re-enable RX interrupts in cp_tx_timeout()	2015-09-23 14:47:12 -07:00
8139too.c	8139too: Add netif_napi_del in the driver	2014-12-22 16:31:58 -05:00
atp.c
atp.h	net: ethernet: realtek: atp: checkpatch errors and warnings corrected	2014-10-29 14:52:06 -04:00
Kconfig	drivers/net: remove all references to obsolete Ethernet-HOWTO	2015-06-23 06:50:35 -07:00
Makefile
r8169.c	r8169: Fix sleeping function called during get_stats64, v2	2015-09-10 10:06:11 -07:00