All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: Using netconsole and getting double prints
Date: Fri, 06 Nov 2009 17:38:20 +0100	[thread overview]
Message-ID: <4AF450FC.3020205@trash.net> (raw)
In-Reply-To: <43e72e890911051654i19c18bf3nd397662ed79712c4@mail.gmail.com>

Luis R. Rodriguez wrote:
> I'm getting double prints when using netconsole. This used to happen
> to me and then I just enable debugging log level manually (dmesg -n 8)
> but now no matter what I try I always get double prints.
> 
> For example:
> 
> [   23.425448] console [netcon0] enabled
> [   23.425567] netconsole: network logging started
> [   23.425448] console [netcon0] enabled
> [   23.425567] netconsole: network logging started
> [   32.856073] eth0: no IPv6 routers present
> [   32.856073] eth0: no IPv6 routers present
> [   66.307342] kmemleak: 6 new suspected memory leaks (see
> /sys/kernel/debug/kmemleak)
> [   66.307342] kmemleak: 6 new suspected memory leaks (see
> /sys/kernel/debug/kmemleak)
> 
> Instead of dmesg -8 I'm now using ignore_loglevel as a kernel
> parameter but I still get double prints. This also happens if I use
> "debug" as a kernel parameter instead.
> 
> The netconsole is set up on the dev box as follows through an /etc/rc.local
> 
> dhclient eth0
> IP=192.168.2
> # sudo dmesg -n 8
> modprobe netconsole netconsole=@/eth0,6666@${IP}/

Without a MAC address netconsole broadcasts the messages.
So I'd guess the receiving system has multiple NICs and
receives the message multiple times.

      parent reply	other threads:[~2009-11-06 16:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-06  0:54 Using netconsole and getting double prints Luis R. Rodriguez
2009-11-06  5:17 ` Matt Mackall
2009-11-06 16:32   ` Luis R. Rodriguez
2009-11-06 16:43     ` Matt Mackall
     [not found]     ` <4AF452B8.7080306@googlemail.com>
2009-11-06 17:14       ` Luis R. Rodriguez
2009-11-17  0:18         ` Luis R. Rodriguez
2009-11-06 16:38 ` Patrick McHardy [this message]

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=4AF450FC.3020205@trash.net \
    --to=kaber@trash.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mcgrof@gmail.com \
    --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.