RE: Realtek 8139 driver (8139too.c) TX Timeout doesn't allow interrupt handler to disable receive interrupts at high bi-directional traffic

Francois Romieu [mailto:[EMAIL PROTECTED] wrote: > Afaics your change may disable the Rx irq right after the poll routine > enabled it again. It will not always work either. > > The (slow) timeout watchdog could grab the poll handler and hack the > irq mask depending on whether poll was schedul

RE: Realtek 8139 driver (8139too.c) TX Timeout doesn't allow interrupt handler to disable receive interrupts at high bi-directional traffic

Francois Romieu [mailto:[EMAIL PROTECTED] wrote: > Afaics your change may disable the Rx irq right after the poll > routine enabled it again. It will not always work either. > > The (slow) timeout watchdog could grab the poll handler and hack > the irq mask depending on whether poll was schedul

Realtek 8139 driver (8139too.c) TX Timeout doesn't allow interrupt handler to disable receive interrupts at high bi-directional traffic

Hi All I found an issue with Realtek 8139 driver (2.6.10 branch) at high bi-directional traffic. On transmit timeout, driver's timeout callback re-enables the receive interrupt. On the next receive interrupt, the ISR disables the receive interrupt "only" when the receive poll task is not active. B

Linux-2.6.10 - Realtek 8139 driver (8139too.c) TX Timeout doesn't allow interrupt handler to disable receive interrupts at high bi-directional traffic

Hi All I found an issue with Realtek 8139 driver (2.6.10 branch) at high bi-directional traffic. On transmit timeout, driver's timeout callback re-enables the receive interrupt. On the next receive interrupt, the ISR disables the receive interrupt "only" when the receive poll task is not active. B