From: "Luis R. Rodriguez" <mcgrof@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: netdev@vger.kernel.org
Subject: Using netconsole and getting double prints
Date: Thu, 5 Nov 2009 16:54:14 -0800 [thread overview]
Message-ID: <43e72e890911051654i19c18bf3nd397662ed79712c4@mail.gmail.com> (raw)
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}/
exit 0
I capture my data with netcat script (I call it netlog):
#!/bin/bash
echo "You should now run in another window: tail -f $HOME/log"
while true; do
/bin/nc -u -l -p 6666 >> $HOME/log
done
This also just doesn't work if I run the nc manually without a redirect:
while true; do /bin/nc -u -l -p 6666; done
Any ideas?
Luis
next reply other threads:[~2009-11-06 0:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-06 0:54 Luis R. Rodriguez [this message]
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
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=43e72e890911051654i19c18bf3nd397662ed79712c4@mail.gmail.com \
--to=mcgrof@gmail.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 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®