Topic: tcp_v4_rebuild_header() error - can I help?

[Steve Hiner]

I have brought this up before but I thought I'd ask what I could do to help diagnose the problem.  On a very regular basis I get the following error message on the console:

tcp_v4_rebuild_header(): not valid sock addrs: saddr=00000000 rcv_saddr=00000000

I know it is technically harmless but I think it might have social consequences for me.  Usually through the course of one day I will have enough errors that the console has scrolled completely off screen.  I am concerned that my users will think something is wrong with the server or that they won't realize that they can just switch consoles or hit the cursor keys to use the console functions.  I thought I might have found a way around it by switching to the second console hoping that the errors would just appear on the first console but, as you probably know, they appear on the active console so that didn't work.  I have considered just removing the monitor so they won't ever see the message - what they don't know can't concern them.

Is there any way I can help debug this for you?  Is there a debug mode I can enable to give me more output so we can find out why it is happening?  This is a highly reproducible problem on my system so I wouldn't think it would be too hard to find - I am not used to debugging under Linux so I'm just not sure what to do to find the problem.

Steve

[Bengt Norhager]

Hi Steve!

I have had a similar problem with a ICL network interface card. I solved the problem by replace the card with a 3Com NIC. If you specify what kind of network interface card you have and driver you are using, maybe someone have the ansver for you. You can also have a hardware conflict, IRQ and IO address. Make shure that no other hardware are using the same IRQ and IO address as your network interface card by using the setup program or if you have a mainboard with built in network interface card, use the bios setup to change IRQ and IO address.

Bengt