I was just actually about to post about this. I have yet to find a fix; however, it seems its after the multiplex code and can be found here
<link> http://fxr.watson.org/fxr/source/pc/devether.c?v=PLAN9#L202 </link> I am not running venti; I am only running fossil. I don't think that is related in light of the fact we are running both options and its happening on both. I get the behavior after i put in my aescbc key before rio. I also get a whole bunch of download failed and see faces freaking out as its trying to interact with my GMail. I only get this on updating or downloading my emails on first boot. I am going to continue to look into it. james toy On Tue, Aug 18, 2009 at 10:49 AM, erik quanstrom<quans...@quanstro.net> wrote: >> > it sounds like the interrupt handler takes long enough that >> > there is no time to process the incoming frames. >> > >> > i wonder, are you running venti? >> >> >> I am, and venti took a long time to start at boot this time around. I >> suppose I should just run fossil in vmware. > > well, there are a couple of things that should be done > - the ethernet driver bug should be fixed > - venti should be shown how to use a pipe instead of tcp. > > but, i think if you configure a proper loopback using > loopbackmedium rather than going through your virtual > ethernet controller, that might just fix the problem. > > - erik > >
