All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Frank van Maarseveen <frankvm@frankvm.com>
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: Thu, 01 Jun 2006 19:34:47 +0200	[thread overview]
Message-ID: <447F2537.1080807@trash.net> (raw)
In-Reply-To: <20060601091124.GA31642@janus>

Frank van Maarseveen wrote:
> ok, now "tc -s -d qdisc show" says (after noticing missing netconsole
> packets):
> 
> qdisc pfifo_fast 0: dev eth0 bands 3 priomap  1 2 2 2 1 2 0 0 1 1 1 1 1 1 1 1
>  Sent 155031 bytes 2067 pkt (dropped 0, overlimits 0 requeues 0) 
>  backlog 0b 0p requeues 0 


Mhh no dropped packets. I tried to reproduce the problem by changing
netconsole to always use the dev_queue_xmit path, but works flawlessly
for me. Please try to find out if the packets are lost before or after
the qdisc by looking at the packet counter.

BTW: You still haven't sent me the packet dump (from the originating
machine).


  reply	other threads:[~2006-06-01 17:34 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
2006-06-01  9:11           ` Frank van Maarseveen
2006-06-01 17:34             ` Patrick McHardy [this message]
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=447F2537.1080807@trash.net \
    --to=kaber@trash.net \
    --cc=frankvm@frankvm.com \
    --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.