From: Wichert Akkerman <wichert@wiggy.net>
To: netdev@oss.sgi.com
Cc: tgraf@suug.ch
Subject: ing_filter debug messages
Date: Thu, 30 Dec 2004 17:06:43 +0100 [thread overview]
Message-ID: <20041230160643.GD24603@wiggy.net> (raw)
After upgrading a machine to (unpatched mainline) 2.6.10 my kernel log
is filled with ing_filter (debug?) messages:
Dec 30 16:24:58 thunder kernel: ing_filter: fixed eth1 out eth1
Dec 30 16:24:58 thunder kernel: ing_filter: fixed eth1 out eth1
Dec 30 16:37:08 thunder kernel: ing_filter: fixed eth1 out eth1
Dec 30 16:37:08 thunder kernel: ing_filter: fixed eth1 out eth1
Dec 30 16:49:08 thunder kernel: ing_filter: fixed eth1 out eth1
Dec 30 16:49:08 thunder kernel: ing_filter: fixed eth1 out eth1
Dec 30 17:01:08 thunder kernel: ing_filter: fixed eth1 out eth1
Dec 30 17:01:08 thunder kernel: ing_filter: fixed eth1 out eth1
the messages always come in pairs. eth1 is the externel interface which
has a standard wondershaper configuration attached to it. Relevant bits
of .config are below.
Wichert.
#
# QoS and/or fair queueing
#
CONFIG_NET_SCHED=y
CONFIG_NET_SCH_CLK_JIFFIES=y
# CONFIG_NET_SCH_CLK_GETTIMEOFDAY is not set
# CONFIG_NET_SCH_CLK_CPU is not set
CONFIG_NET_SCH_CBQ=y
CONFIG_NET_SCH_HTB=y
# CONFIG_NET_SCH_HFSC is not set
# CONFIG_NET_SCH_PRIO is not set
# CONFIG_NET_SCH_RED is not set
CONFIG_NET_SCH_SFQ=y
# CONFIG_NET_SCH_TEQL is not set
CONFIG_NET_SCH_TBF=y
# CONFIG_NET_SCH_GRED is not set
# CONFIG_NET_SCH_DSMARK is not set
# CONFIG_NET_SCH_NETEM is not set
CONFIG_NET_SCH_INGRESS=y
CONFIG_NET_QOS=y
CONFIG_NET_ESTIMATOR=y
CONFIG_NET_CLS=y
CONFIG_NET_CLS_TCINDEX=y
CONFIG_NET_CLS_ROUTE4=y
CONFIG_NET_CLS_ROUTE=y
CONFIG_NET_CLS_FW=y
CONFIG_NET_CLS_U32=y
# CONFIG_CLS_U32_PERF is not set
# CONFIG_NET_CLS_IND is not set
CONFIG_NET_CLS_RSVP=y
CONFIG_NET_CLS_RSVP6=y
CONFIG_NET_CLS_ACT=y
CONFIG_NET_ACT_POLICE=y
CONFIG_NET_ACT_GACT=y
CONFIG_GACT_PROB=y
CONFIG_NET_ACT_MIRRED=y
CONFIG_NET_ACT_IPT=y
CONFIG_NET_ACT_PEDIT=y
--
Wichert Akkerman <wichert@wiggy.net> It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
next reply other threads:[~2004-12-30 16:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-30 16:06 Wichert Akkerman [this message]
2004-12-31 5:07 ` ing_filter debug messages jamal
2004-12-31 9:38 ` Wichert Akkerman
2004-12-31 11:11 ` jamal
2004-12-31 11:15 ` Wichert Akkerman
2004-12-31 13:15 ` Wichert Akkerman
2004-12-31 15:03 ` jamal
2004-12-31 15:10 ` jamal
2004-12-31 15:48 ` Wichert Akkerman
2004-12-31 16:48 ` unregister_netdev Annoyance WAS(Re: " jamal
2004-12-31 18:24 ` Andre Tomt
2005-01-02 12:13 ` bert hubert
2005-01-03 14:50 ` jamal
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=20041230160643.GD24603@wiggy.net \
--to=wichert@wiggy.net \
--cc=netdev@oss.sgi.com \
--cc=tgraf@suug.ch \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.