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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majo...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This is the first report I've seen of that. Recommend investigating with
wireshark.
> 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
That really shouldn't make any difference.
--
http://selenic.com : development and support for Mercurial and Linux
Matt, did you really mean wireshark? I'm a wireless guy so wireshark
to me is this:
The prints have nothing to do with protocols though. I can get a
double print on a simple hello world driver.
Luis
> The prints have nothing to do with protocols though. I can get a
> double print on a simple hello world driver.
Are you saying you get these double prints on the *local* machine? Are
the messages logged dmesg doubled too?
--
http://selenic.com : development and support for Mercurial and Linux
Without a MAC address netconsole broadcasts the messages.
So I'd guess the receiving system has multiple NICs and
receives the message multiple times.
> I think the intention behind this is for you to check if they are double
> prints on your end or double sends on the other end.
Ah yeah, good point :)
Sniffed and saw the issue. My local router was echo'ing the message,
solution was to simply add the destination mac address on netconsole
module parameters passed.
Luis