Just for fun I have just installed a 2.0.27 kernel instead of the 2.1.29 I have
been using so far, and voila - the errors are gone. The kernels have been
configured the same way and the hardware is unchanged so the difference must
be somewhere in the networking code.
Could someone please help me clarify what behaviour is correct before I go
bug-hunting? If there is any reason to believe that the problems described
above have been solved in 2.0.pre-30 and 2.1.pre-30 I'd be more than happy to
try them on for a size :-)
Cheers,
Mikkel
-------------------------------------------------------------------------
Mikkel Lauritsen - mila@it.dtu.dk
Institute of Information Technology
Technical University of Denmark