[lkml]   [2001]   [Feb]   [12]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: eepro100.c, kernel 2.4.1

On Thu, Feb 08, 2001 at 03:26:51AM -0800, Ion Badulescu wrote:
> On Thu, 8 Feb 2001 20:15:39 +0900, Augustin Vidovic <> wrote:
> >> eth0: Sending a multicast list set command from a timer routine........."
> >>
> >> If you find such messages, the work-around really did something. Otherwise,
> >> it's the placebo effect...
> >
> > Now, I do not get _any_ message in the logs, which means that the network
> > cards activity is closer to normality than before the patch.
> So your patch did not do you any good. Case closed, as far as the work-around
> is concerned.

I've just checked: "Sending a multicast list set command" is printed only on
high debug levels, so Augustin might not see them.

If "Receiver lock-up workaround activated" message is printed, then the
workaround is really activated.
I doubt that the real reason is that RX bug, but periodic multicast list set
commands may certainly affect the behavior.

Augustin, could you send the output of `lspci' and `eepro100-diag -ee', please?
(The latter may be taken from

Best regards
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:13    [W:0.093 / U:0.396 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site