eepro100 -- Sending a multicast list set command from a timer routine

eepro100 -- Sending a multicast list set command from a timer routine

[Miles Bader]

Starting with 2.5.44 I'm getting tons of messages like the following
printed on the console:

   eth0: Sending a multicast list set command from a timer routine, m=0, j=50143, l=49360.

Here's the associated code in drivers/net/eepro100.c:

	if (sp->rx_mode < 0  ||
		(sp->rx_bug  && jiffies - sp->last_rx_time > 2*HZ)) {
		/* We haven't received a packet in a Long Time.  We
		   might have been bitten by the receiver hang bug.
		   This can be cleared by sending a set multicast list
		   command. */
		if (netif_msg_rx_err(sp))
			printk(KERN_DEBUG "%s: Sending a ...", ...);
		set_rx_mode(dev);
        }

The behavior I'm seeing seems to match the above code: it prints a
message about every 2 seconds if I'm not using the network.  On this
machine, I'm quite often not using the network, so this repetitive
message is quite annoying.

In 2.5.44, the test used to decide whether to print a message changed,
which I guess is why I'm suddenly seeing all these messages:

   -		if (speedo_debug > 3)
   +		if (netif_msg_rx_err(sp))

So I guess either the test used to print the message, or the test used
to do the reset should be changed (probably the former).

Thanks,

-Miles
-- 
We live, as we dream -- alone....

Re: eepro100 -- Sending a multicast list set command from a timer routine

[Adam Kropelin]

On Mon, Oct 21, 2002 at 05:56:35PM +0900, Miles Bader wrote:
> Starting with 2.5.44 I'm getting tons of messages like the following
> printed on the console:
> 
>    eth0: Sending a multicast list set command from a timer routine, m=0, j=50143, l=49360.

Same here... 

--Adam

Re: eepro100 -- Sending a multicast list set command from a timer routine

[Tim Hockin]

> On Mon, Oct 21, 2002 at 05:56:35PM +0900, Miles Bader wrote:
> > Starting with 2.5.44 I'm getting tons of messages like the following
> > printed on the console:
> > 
> >    eth0: Sending a multicast list set command from a timer routine, m=0, j=50143, l=49360.
> 
> Same here... 

A change to use the new netif_msg_xxx interface must have gone in.  Shortly
there will be a patch which cleans up the randomish messages it spews out.
Nothing to worry about.

Tim