On Fri, Feb 13, 2009 at 02:17:16AM +0900, Hiroharu Tamaru wrote:
> Hi, I'm back with the results.
> And to make it short, everything works now.
> Thank you, Hans and Pyun, and all others who looked into this for me.
> 

Great! Andrew, would you commit the patch?

> Some notes inline:
> 

[...]
> OK, the patch usb2_ethernet.patch2 in
> <20090212043033.gc6...@michelle.cdnetworks.co.kr> worked, and now the
> ue0/AXE interface is working fine.
> 
> Though I have only tested in 100BaseTX/full-duplex mode,
> ping -f over a 100Mbps switch run without any packet loss
> (sysctl net.inet.icmp.icmplim=0, of course), and the interface
> statics shows no errors too:
> 
> Name    Mtu Network       Address              Ipkts Ierrs    Opkts Oerrs  
> Coll
> ue0    1500 <Link#4>      00:90:cc:xx:xx:xx    32634     0    32192    0     0
> ue0    1500 192.168.1.0   192.168.1.3          32553     -    32190    -     -
> 
> 
> Also, 
> At Thu, 12 Feb 2009 12:51:00 +0900, Hiroharu Tamaru wrote:
> > I also have em0/em1 interfaces, and I am switching with ue0
> > when I test AXE.
> > 
> > It turned out that although I 'ifconfig em0 inet delete
> > down' those unused interfaces, the arp table entries remain.
> > 'arp -nda' shows 'delete: cannot locate 192.168.1.1' and the
> > like for every entry in the table, and they are infact not
> > deleted.  Deletion fails both when em0 is up and down.
> 
> This symptom was solved after I have brought my userland in
> sync with the kernel.
> 
> So here I am, with all my USB2 problems solved!
> Thank you all for this quick assistance!
> 
> And finally, I'd appreciate if you could send me or the list
> the 'commit done' message on this ethernet patch and the
> mountroot delay patch, so that I can mark to forget about
> patching the kernel as I cvsup it.  Thanks.
> 

Will do.

Thanks for testing!
_______________________________________________
freebsd-usb@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"

Reply via email to