> Also, I just did a pull from sources which appears to have updated > almost the complete contents of /386. This caused the "soverflow for > fx->in" message to appear. I had to run pull three times to get it to > finish.
maybe my first message wasn't that clear. any ethernet activity can cause this if the input queue can't be drained fast enough. clearly, too much of the cpu is spent in interrupt context receiving packets, and not enough processing them. but delete the print, and tcp congestion avoidance should make up the difference fast enough to keep the remote happy. - erik
