that's strange, I encountered exactly the same message in my syslog while
doing backups between two Linux machines, it was somewhere around 2.4.15 I
> You can safely comment out the printk. It would be interesting however
> to find out what the other side is running and yell at the vendor.
> > I'm a bit concerned that maybe someone is warming up for a hit or
> > something.
> More likely someone released a new buggy TCP stack to the world.
Is it possible that there are other things which can cause this?
Or does it really mean that Linux has a buggy TCP stack!?
I simply cannot believe this ;-)
Yven Johannes Leist - email@example.com http://www.leist.beldesign.de - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to firstname.lastname@example.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/