Well, well. I, too, just built and installed 2.4.0
on one of the machines on my internal home net and
now (coincidentally?) another machine on my net is
griping about strange networking errors - I'm seeing
zillions of these:
eth1: bogus packet size: 0, status=0x1 nxpg=0x14.
eth1: bogus packet size: 0, status=0x1 nxpg=0x15.
eth1: bogus packet size: 0, status=0x1 nxpg=0x19.
eth1: bogus packet size: 0, status=0x1 nxpg=0x1a.
eth1: bogus packet size: 0, status=0x1 nxpg=0x1c.
eth1: bogus packet size: 0, status=0x1 nxpg=0x2a.
eth1: bogus packet size: 0, status=0x1 nxpg=0x2b.
Anything network related is suffering periodic stalls
and freezeups. Maybe 2.4.0 is still not ready for
PrimeTime despite its very long gestation...
**********************************************************
To unsubscribe from this list, send mail to
[EMAIL PROTECTED] with the following text in the
*body* (*not* the subject line) of the letter:
unsubscribe gnhlug
**********************************************************
