Ok,... We have reverted to `dhcp-multi' and the problem still persists.
So it has to be some time earlier than that. We're currently investigating/bisecting in the hope of finding out the problem. One thing that we know for sure is gpxe 1.0.1 doesn't have that problem. It was released on 6/29. It doesn't matter which link speed we used, it always breaks with tg3. We have tried 1000/100. Same result. Move the cable to the 3com card -- fine again. And as tg3 doesn't seem to be changed for a while, the problem lies in another module. On Fri, 05 Nov 2010 23:03 -0400, "Joshua Oreman" <oremanj at MIT.EDU> wrote: > On Fri, Nov 5, 2010 at 10:59 PM, Huan Truong <hnt7438 at truman.edu> wrote: > > I'm using iPXE now and it is very apparent that iPXE tg3 implementation > > is very slow. > > > > It takes me about 30 seconds to fetch my vmlinuz kernel image from > > Ubuntu 10.10 on a 1Gbps connection compared to gPXE (1.0.1)'s > > implementation that takes about 1 second. > > > > It prints out a bunch of hashes and sometimes a dot ################... > > while gPXE doesn't. > > > > I wonder if that's a regression or something. > > > > I can help with debugging the problem if that's a regression as I have > > the hardware here, but if that's something that the devs already know, > > then there's no sense in doing it. > > I also noticed this yesterday, as well as some "transmit timed out" > errors. Have there been any recent changes that might be relevant? > > Josh > > > _______________________________________________ > > ipxe-devel mailing list > > ipxe-devel at lists.ipxe.org > > https://lists.ipxe.org/mailman/listinfo/ipxe-devel > > >
