[lkml]   [2001]   [Sep]   [27]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [patch] netconsole - log kernel messages over the network. 2.4.10.
Hi All,

Ingo was not aware of the sourceforge project, and suggested me to
resend my reply to lkml. Does the patch work for you guys? Do I do
something wrong? That would be more than possible. :-)

----- Forwarded message from Ookhoi <> -----

To: Ingo Molnar <>

Hi Ingo,

> this is the first public release of the 'netconsole patch', a debugging
> patch that implements kernel-level network logging via UDP packets.

Is this different from the netconsole project on sourceforge? The last
message on that lists seemes to be from july, and you didn't cc it.

> the kernel patch (against 2.4.10 or 2.4.9-ac), and a simple user-space
> tool to display netconsole messages can be found at:

Can you also make older patches available for testing? The current
netconsole-2.4.10-B1 doesn't seem to work for me on plain 2.4.10 or
2.4.9-ac15 patched with Rik his latest vm patch. The patch applies fine,
but I can't load the module:

cuddle:~# uname -a
Linux cuddle 2.4.9-ac15 #1 Thu Sep 27 13:54:51 CEST 2001 i686 unknown
cuddle:~# insmod netconsole dev=eth0 target_ip=0x0a604875 source_port=6666 target_port=5555
Using /lib/modules/2.4.9-ac15/kernel/drivers/net/netconsole.o
/lib/modules/2.4.9-ac15/kernel/drivers/net/netconsole.o: init_module: Operation not permitted
Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters

The same message for plain 2.4.10, and the same when I use the script
netconsole-server included in netconsole-client-20010927. I also tried
it with the target_eth_byte0 thingies, with the mac address from the
local nic.

Target ip address is (I hope 0x0a604875 is oke)

> sample startup of the netconsole on the server:
> insmod netconsole dev=eth1 target_ip=0x0a000701 \
> source_port=6666 \
> target_port=6666 \
> target_eth_byte0=0x00 \
> target_eth_byte1=0x90\
> target_eth_byte2=0x27 \
> target_eth_byte3=0x8C \
> target_eth_byte4=0xA0 \
> target_eth_byte5=0xA8
> and on the client:
> # ./netconsole-client -server -client -port 6666
> [ console startup...]
> netconsole: network logging started up successfully!
> SysRq : Loglevel set to 9
> more about features and limitations can be found under:
> Documentation/networking/netlogging.txt
> reports, comments, suggestions welcome.

Somebody more or less asked this already, but, will things like SysRq
work in the future? That would be great. :-) Thnx!


----- End forwarded message -----
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:03    [W:0.098 / U:1.124 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site