All of lore.kernel.org
 help / color / mirror / Atom feed
From: Frank van Maarseveen <frankvm@frankvm.com>
To: Patrick McHardy <kaber@trash.net>
Cc: linux-kernel@vger.kernel.org,
	Kernel Netdev Mailing List <netdev@vger.kernel.org>
Subject: Re: 2.6.17-rc4: netfilter LOG messages truncated via NETCONSOLE
Date: Wed, 31 May 2006 20:20:19 +0200	[thread overview]
Message-ID: <20060531182019.GA26456@janus> (raw)
In-Reply-To: <447DD66C.30605@trash.net>

On Wed, May 31, 2006 at 07:46:20PM +0200, Patrick McHardy wrote:
> Frank van Maarseveen wrote:
> > On Wed, May 31, 2006 at 06:36:35PM +0200, Patrick McHardy wrote:
> > 
> >>The messages might get dropped when the output queue is full.
> >>Does one of the drop counters shown by "ip -s link list"
> >>and "tc -s -d qdisc show" increase (the other counts might also
> >>give some clues)? Otherwise please apply the attached patch
> >>(should fix tcpdump, last patch was incomplete) and post a dump.
> > 
> > 
> > No visible improvement with the new patch.
> 
> Does this mean tcpdump doesn't show any packets?

tcpdump output is consistent with what the netconsole receiver sees: 9
packets are still missing. I know there are 9 because 2.6.13.2 shows them.

The two patches behaved identically for me.

> 
> > ip -s link doesn't show any
> > dropped packets so far with any patch and I don't use traffic control
> > that I'm aware of. But I'm not sure what to make of "tc" output, maybe
> > because CONFIG_SHAPER is not set:
> > 
> > 	# tc -s -d qdisc show
> > 	RTNETLINK answers: Invalid argument
> > 	Dump terminated
> 
> Thats because you're missing CONFIG_NET_SCHED. Please enable it and
> try the tc command again, without it we can't see whether the qdisc
> (which is present even without CONFIG_NET_SCHED) just dropped the
> packets.

I'll try that tomorrow.

-- 
Frank

  reply	other threads:[~2006-05-31 18:20 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-31  9:46 2.6.17-rc4: netfilter LOG messages truncated via NETCONSOLE Frank van Maarseveen
2006-05-31 14:57 ` Patrick McHardy
2006-05-31 16:06   ` Frank van Maarseveen
2006-05-31 16:36     ` Patrick McHardy
2006-05-31 17:29       ` Frank van Maarseveen
2006-05-31 17:46         ` Patrick McHardy
2006-05-31 18:20           ` Frank van Maarseveen [this message]
2006-06-01  9:11           ` Frank van Maarseveen
2006-06-01 17:34             ` Patrick McHardy
2006-06-02 12:35               ` Frank van Maarseveen
2006-06-02 14:02                 ` 2.6.17-rc4: netfilter LOG messages truncated via NETCONSOLE (2) Frank van Maarseveen
2006-06-02 14:16                   ` Patrick McHardy
2006-06-02 14:39                     ` Frank van Maarseveen

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=20060531182019.GA26456@janus \
    --to=frankvm@frankvm.com \
    --cc=kaber@trash.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    /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.