Thanks Erik. Removing the first instance of the print in
/sys/src/9/pc/devether.c appears to fix it:
/* print("soverflow for f->in\n"); */
There is another another print lower down but I left this there for the moment.
term% time upas/fs -f /imaps/imap.gmail.com/[email protected]
!Adding key: proto=pass server=imap.gmail.com service=imap
[email protected]
password:
!
0.21u 1.04s 35.59r upas/fs -f
/imaps/imap.gmail.com/[email protected]
This was for 595 messages actually.
Many thanks,
James
On Sun, Jul 25, 2010 at 7:52 AM, erik quanstrom <[email protected]> wrote:
>> 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
>
>
