This is on linux-2.0, and it appears irregardless of what
options are chosen in the configure script(well, lets just say I've
recompiled this kernel more than 12 times with different options :( ).
I looked in the eexpress.c file and it indicates there that this is
a problem with the driver, but it also says this should be a rare
occurrance -- not every single time. telnet/rlogin sessions work fine
most of the time(Hmm -- maybe we should put a short duration sleep
in the send code and see what it does since tcpdump doesn't give me
any problems recieving packets? -- ideas? suggestions? )
Does anyone have more information on this one? Does anyone
want more information on this one? - email me.
--Darrin
ps - this machine is not on the public net, so getting information may
take me a day or so since I have to get it via floppy-net.
-- FAQ Suggestions: Q: I upgraded without reading release notes, now my system's broke - why? A: What the @!#* did you expect? (this assumes that someone reads the faq, of course ;)