On Tue, Dec 08, 2009 at 10:08:36AM -0800, Pyun YongHyeon wrote: > On Tue, Dec 08, 2009 at 10:52:07AM +0900, Yoshiaki Kasahara wrote: > > On Fri, 4 Dec 2009 10:43:01 -0800, > > Pyun YongHyeon <[email protected]> said: > > > > >> before I replaced vge(4). I guess the system froze while initializing > > >> vge(4), but I'm not really sure actually. > > > > > > Yes, that's also possible. But I can't explain how the patch can > > > freeze the box. Another user also reported the similar vge(4) issue > > > in private mail and tried the same patch and he could successfully > > > boot with patched vge(4). Unfortunately the issue does not seem to > > > fix his issue. I'm still working on it. > > > > > >> > > >> What can I do to narrow the cause of problems? Is it useful to build > > >> kernel with options KDB and DDB? > > >> > > > > > > Yes. > > > > Ok, now I'm ready to boot a DDB enabled kernel to try kernel debugging > > on my PC. I can't read email during debugging my PC under current > > configuration, so could you please tell me any specific instructions > > to collect information you need? I'm reading the Handbook now, but I'm > > not very sure... > > > > Sorry, another user also reported similar problem in my patch. I > have to look closely before doing any further testing. Since I've > ordered the controller I would get access to hardware in near > future. I'll let you know when I have a working patch. >
FYI: I received ordered hardware and fixed the patch to make it work again. Try the patch at the following URL. http://people.freebsd.org/~yongari/vge/vge.busdma.diff2 The TCP/UDP bulk Tx performance seem to be really poor(less than 700Mbps) and vge(4) generates too many interrupts(more than 40k interrupts/s). Rx performance looks reasonable(about 928Mbps) though. I'll have to see what triggers its poor Tx performance after fixing TCP connection stall issue. _______________________________________________ [email protected] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[email protected]"
