mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Miles Bader <miles@lsi.nec.co.jp>
To: "Andrey V.Savochkin" <saw@saw.sw.com.sg>
Cc: linux-kernel@vger.kernel.org
Subject: eepro100 -- Sending a multicast list set command from a timer routine
Date: 21 Oct 2002 17:56:35 +0900	[thread overview]
Message-ID: <buo4rbgw4os.fsf@mcspd15.ucom.lsi.nec.co.jp> (raw)

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....

             reply	other threads:[~2002-10-21  8:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-21  8:56 Miles Bader [this message]
2002-10-21 12:03 ` Adam Kropelin
2002-10-21 16:43   ` Tim Hockin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=buo4rbgw4os.fsf@mcspd15.ucom.lsi.nec.co.jp \
    --to=miles@lsi.nec.co.jp \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miles@gnu.org \
    --cc=saw@saw.sw.com.sg \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®