Skip to contentSkip to conversation

netconsole not working on 2.6.17.6

DISCUSSION Benjamin Schindler 2 participants 4 messages Sep 16, 2006 – Oct 4, 2006 1 message not in the archive

lore
Share & tools
lore
#0 lore raw

Hi

I'm unsuccesfully trying to get networking to work - I've got two boxes that can ping each other: 192.168.0.101 and 192.168.0.102 - I load the netconsole module:

modprobe netconsole [email protected]/eth0,[email protected]/00:02:44:34:5d:f6

In dmesg I get:

netconsole: local port 6666
netconsole: local IP 192.168.0.102
netconsole: interface eth0
netconsole: remote port 6666
netconsole: remote IP 192.168.0.101
netconsole: remote ethernet address 00:02:44:34:5d:f6
netconsole: network logging started

I start wireshark/tcpdump whatever - and load a few modules just to produce some kernel messages. However, noething leaves the wire but I get all the messages in dmesg.

What's wrong here?

Thanks
Benjamin Schindler

P.s. please cc me as I'm not subscribed to this list

A message that is not in the archive (sent off-list or not yet received): [email protected]

#2 lore raw
Quoted 4 lines · you
Quoted 3 lines · Benjamin Schindler

Hi

I'm unsuccesfully trying to get networking to work - I've got two boxes

that

Quoted 1 line
Quoted 1 line

can ping each other: 192.168.0.101 and 192.168.0.102 - I load the

netconsole

Quoted 15 lines
Quoted 15 lines

module:

modprobe netconsole [email protected]/eth0,[email protected]/00:02:44:34:5d:f6

In dmesg I get:

netconsole: local port 6666
netconsole: local IP 192.168.0.102
netconsole: interface eth0
netconsole: remote port 6666
netconsole: remote IP 192.168.0.101
netconsole: remote ethernet address 00:02:44:34:5d:f6
netconsole: network logging started

Quoted 1 line
Quoted 1 line

I start wireshark/tcpdump whatever - and load a few modules just to

produce

Quoted 5 lines
Quoted 5 lines

some kernel messages. However, noething leaves the wire but I get all the messages in dmesg.

What's wrong here?

Quoted 8 lines
Quoted 5 lines

Thanks
Benjamin Schindler

P.s. please cc me as I'm not subscribed to this list

Are you pointing to the correct MAC? Have you tried to compile the netconsole as built-in?

Yes, I'm pointing at the correct MAC, but since wireshark doesn't see in the networl, I doubt anything actually is sent.
No, I have not tried to compile netconsole into the kernel because of flexibility. Anyway, I have investiaged further:
I ran this systemtap script:

probe module("netconsole").function("write_msg@drivers/net/netconsole.c") {
printf("WriteMsg called\b")
}

Once this script was run, I rmmod and modprobe'd my wireless-module a few times to generate some dmesg output, but according to systemtap, this function never gets called.
So, either the call to register_console in netconsole fails, is wrong or there is a but in register_console

Thanks
Benjamin Schindler

#3 lore raw
Quoted 48 lines · Benjamin Schindler
Quoted 4 lines · you
Quoted 3 lines · Benjamin Schindler

Hi

I'm unsuccesfully trying to get networking to work - I've got two boxes

that

Quoted 1 line
Quoted 1 line

can ping each other: 192.168.0.101 and 192.168.0.102 - I load the

netconsole

Quoted 15 lines
Quoted 15 lines

module:

modprobe netconsole [email protected]/eth0,[email protected]/00:02:44:34:5d:f6

In dmesg I get:

netconsole: local port 6666
netconsole: local IP 192.168.0.102
netconsole: interface eth0
netconsole: remote port 6666
netconsole: remote IP 192.168.0.101
netconsole: remote ethernet address 00:02:44:34:5d:f6
netconsole: network logging started

Quoted 1 line
Quoted 1 line

I start wireshark/tcpdump whatever - and load a few modules just to

produce

Quoted 5 lines
Quoted 5 lines

some kernel messages. However, noething leaves the wire but I get all the messages in dmesg.

What's wrong here?

Quoted 8 lines
Quoted 5 lines

Thanks
Benjamin Schindler

P.s. please cc me as I'm not subscribed to this list

Are you pointing to the correct MAC? Have you tried to compile the netconsole as built-in?

Yes, I'm pointing at the correct MAC, but since wireshark doesn't see in the networl, I doubt anything actually is sent.
No, I have not tried to compile netconsole into the kernel because of flexibility. Anyway, I have investiaged further:
I ran this systemtap script:

probe module("netconsole").function("write_msg@drivers/net/netconsole.c") {
printf("WriteMsg called\b")
}

Quoted 5 lines

Once this script was run, I rmmod and modprobe'd my wireless-module a few times to generate some dmesg output, but according to systemtap, this function never gets called.
So, either the call to register_console in netconsole fails, is wrong or there is a but in register_console

The usual problem is that the console log level is set too low.

Signature · 1 line
Mathematics is the supreme nostalgia of our time.
#4 lore raw
Quoted 57 lines · Matt Mackall
Quoted 56 lines · Benjamin Schindler
Quoted 5 lines · you
Quoted 4 lines · Benjamin Schindler

Hi

I'm unsuccesfully trying to get networking to work - I've got two boxes

that

Quoted 1 line
Quoted 1 line

can ping each other: 192.168.0.101 and 192.168.0.102 - I load the

netconsole

Quoted 16 lines
Quoted 16 lines

module:

modprobe netconsole [email protected]/eth0,[email protected]/00:02:44:34:5d:
f6

In dmesg I get:

netconsole: local port 6666
netconsole: local IP 192.168.0.102
netconsole: interface eth0
netconsole: remote port 6666
netconsole: remote IP 192.168.0.101
netconsole: remote ethernet address 00:02:44:34:5d:f6
netconsole: network logging started

Quoted 1 line
Quoted 1 line

I start wireshark/tcpdump whatever - and load a few modules just to

produce

Quoted 5 lines
Quoted 5 lines

some kernel messages. However, noething leaves the wire but I get all the messages in dmesg.

What's wrong here?

Quoted 7 lines
Quoted 4 lines

Thanks
Benjamin Schindler

P.s. please cc me as I'm not subscribed to this list

Are you pointing to the correct MAC? Have you tried to compile the netconsole as built-in?

Yes, I'm pointing at the correct MAC, but since wireshark doesn't see in the networl, I doubt anything actually is sent.
No, I have not tried to compile netconsole into the kernel because of flexibility. Anyway, I have investiaged further:
I ran this systemtap script:

probe module("netconsole").function("write_msg@drivers/net/netconsole.c") { printf("WriteMsg called\b")
}

Quoted 7 lines
Quoted 5 lines

Once this script was run, I rmmod and modprobe'd my wireless-module a few times to generate some dmesg output, but according to systemtap, this function never gets called.
So, either the call to register_console in netconsole fails, is wrong or there is a but in register_console

The usual problem is that the console log level is set too low.

I did 'echo 9 4 1 7 > /proc/sys/kernel/printk' and nothing changed. I also tried to set the log level to 9 using sysrq (dmesg confirmed), but I still don't get any messages
Thanks