Commit 8d4ef88b authored by Satyam Sharma's avatar Satyam Sharma Committed by David S. Miller

[NET] netconsole: Add some useful tips to documentation

Based upon initial work by Keiichi Kii <k-keiichi@bx.jp.nec.com>.

Add some useful general-purpose tips.  Also suggest solution for the frequent
problem of console loglevel set too low numerically (i.e.  for high priority
messages only) on the sender.
Signed-off-by: default avatarSatyam Sharma <satyam@infradead.org>
Acked-by: default avatarKeiichi Kii <k-keiichi@bx.jp.nec.com>
Acked-by: default avatarMatt Mackall <mpm@selenic.com>
Signed-off-by: default avatarAndrew Morton <akpm@linux-foundation.org>
Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
parent 0cc120be
...@@ -44,11 +44,36 @@ WARNING: the default target ethernet setting uses the broadcast ...@@ -44,11 +44,36 @@ WARNING: the default target ethernet setting uses the broadcast
ethernet address to send packets, which can cause increased load on ethernet address to send packets, which can cause increased load on
other systems on the same ethernet segment. other systems on the same ethernet segment.
TIP: some LAN switches may be configured to suppress ethernet broadcasts
so it is advised to explicitly specify the remote agents' MAC addresses
from the config parameters passed to netconsole.
TIP: to find out the MAC address of, say, 10.0.0.2, you may try using:
ping -c 1 10.0.0.2 ; /sbin/arp -n | grep 10.0.0.2
TIP: in case the remote logging agent is on a separate LAN subnet than
the sender, it is suggested to try specifying the MAC address of the
default gateway (you may use /sbin/route -n to find it out) as the
remote MAC address instead.
NOTE: the network device (eth1 in the above case) can run any kind NOTE: the network device (eth1 in the above case) can run any kind
of other network traffic, netconsole is not intrusive. Netconsole of other network traffic, netconsole is not intrusive. Netconsole
might cause slight delays in other traffic if the volume of kernel might cause slight delays in other traffic if the volume of kernel
messages is high, but should have no other impact. messages is high, but should have no other impact.
NOTE: if you find that the remote logging agent is not receiving or
printing all messages from the sender, it is likely that you have set
the "console_loglevel" parameter (on the sender) to only send high
priority messages to the console. You can change this at runtime using:
dmesg -n 8
or by specifying "debug" on the kernel command line at boot, to send
all kernel messages to the console. A specific value for this parameter
can also be set using the "loglevel" kernel boot option. See the
dmesg(8) man page and Documentation/kernel-parameters.txt for details.
Netconsole was designed to be as instantaneous as possible, to Netconsole was designed to be as instantaneous as possible, to
enable the logging of even the most critical kernel bugs. It works enable the logging of even the most critical kernel bugs. It works
from IRQ contexts as well, and does not enable interrupts while from IRQ contexts as well, and does not enable interrupts while
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment