On Mon, Apr 10, 2017 at 7:22 AM, tedheadster <tedheads...@gmail.com> wrote: > On Sat, Apr 8, 2017 at 6:23 AM, Francois Romieu <rom...@fr.zoreil.com> wrote: >> David Miller <da...@davemloft.net> : >> [...] >>> One theory is that the interrupt masking isn't working properly >>> and interrupts are still arriving and hitting the NAPI state even >>> when we are actively polling NAPI. >>> >>> And this problem was masked by the locking done here. >> >> Yes. >> >> Ville, can you rule out irq sharing between the 8139 and some other >> device ? It's a candidate for unexpected interrupt handler invocation >> with older pc, even with properly working hardware. >> > > Eric, > If napi_complete_done() calls could affect drivers on older > hardware, I can test the following: > > drivers/net/ethernet/3com/typhoon.c > drivers/net/ethernet/amd/pcnet32.c > drivers/net/ethernet/broadcom/tg3.c > drivers/net/ethernet/dec/tulip/interrupt.c > drivers/net/ethernet/intel/e100.c > drivers/net/ethernet/intel/e1000/e1000_main.c > drivers/net/ethernet/smsc/epic100.c > drivers/net/ethernet/via/via-rhine.c
That would be great, thanks Matthew.
