Date: Tue, 15 Jun 2010 12:49:12 -0700 From: Pyun YongHyeon <pyunyh@gmail.com> To: Hans Petter Selasky <hselasky@c2i.net> Cc: freebsd-net@freebsd.org, Sergey Perevalov <perevalov84@gmail.com> Subject: Re: [axe][ue0] Device send packets but any host in network can not receive any packet from it. Message-ID: <20100615194912.GJ4257@michelle.cdnetworks.com> In-Reply-To: <201006150706.03039.hselasky@c2i.net> References: <4BE44E2D.6060907@gmail.com> <4C148135.7080704@gmail.com> <20100614211155.GB4257@michelle.cdnetworks.com> <201006150706.03039.hselasky@c2i.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Jun 15, 2010 at 07:06:02AM +0200, Hans Petter Selasky wrote: > On Monday 14 June 2010 23:11:55 Pyun YongHyeon wrote: > > On Sun, Jun 13, 2010 at 11:56:53AM +0500, Sergey Perevalov wrote: > > > On 04.06.2010 02:46, Pyun YongHyeon wrote: > > > >On Thu, Jun 03, 2010 at 06:51:00PM +0500, Perevalov Sergey wrote: > > > >>On 02.06.2010 03:24, Pyun YongHyeon wrote: > > > >>>On Tue, Jun 01, 2010 at 11:31:13PM +0500, Perevalov Sergey wrote: > > > >>>>Hi! > > > >>>>I tried it with crossover cable but results was the same bad. Then > > > >>>> set debug flag hw.usb.axe.debug: to 15, and started ping -f from > > > >>>> ue0. And in /var/log/messages I found these strings: > > > >>>> > > > >>>>Jun 1 22:28:34 laptop kernel: axe_bulk_read_callback:842: bulk read > > > >>>>error, USB_ERR_CANCELLED > > > >>>>Jun 1 22:28:35 laptop kernel: axe_bulk_write_callback:870: transfer > > > >>>>complete > > > >>>>Jun 1 22:29:12 laptop kernel: axe_bulk_write_callback:941: transfer > > > >>>>error, USB_ERR_TIMEOUT > > > >>>>Jun 1 22:29:51 laptop last message repeated 4 times > > > >>>>Jun 1 22:31:40 laptop last message repeated 11 times > > > >>>> > > > >>>>Then i googled it and found this > > > >>>>http://www.mail-archive.com/freebsd-usb@freebsd.org/msg04388.html > > > >>>>the problem is described definitely like mine. > > > >>>>I read all thread and found the patch usb2_ethernet.patch2, but I > > > >>>> havn't found > > > >>>>sys/dev/usb2/ethernet/usb2_ethernet.c file for patch. > > > >>>> > > > >>>>how can I try to apply this patch to my system? > > > >>>>http://www.mail-archive.com/freebsd-usb@freebsd.org/msg04403.html > > > >>> > > > >>>I believe the bug in the thread was fixed long time ago. > > > >>>If you're using 8.0-RELEASE, try latest stable/8 or > > > >>>8.1-PRERELEASE and see whether axe(4) works or not. > > > >> > > > >>I have just finished testing device on my updated freebsd: > > > >>FreeBSD homeserv 8.1-PRERELEASE FreeBSD 8.1-PRERELEASE #0: Thu Jun 3 > > > >>17:22:44 UTC 2010 user@homeserv:/usr/obj/usr/src/sys/GENERIC i386 > > > >>And it still shows the same problem when I try to ping -f any host from > > > >>ue0: > > > >> > > > >>Jun 3 18:29:40 homeserv kernel: ue0: link state changed to UP > > > >>Jun 3 18:29:42 homeserv kernel: axe_bulk_write_callback: transfer > > > >>complete > > > >>Jun 3 18:29:42 homeserv last message repeated 21 times > > > >>Jun 3 18:29:52 homeserv kernel: axe_bulk_write_callback: transfer > > > >>error, USB_ERR_TIMEOUT > > > > > > > >I don't see abnormal things in axe(4). Maybe Hans can help(CCed). > > > > > > > >>Jun 3 18:30:21 homeserv last message repeated 3 times > > > > > > Hi, Pyun! > > > I would send this device to you for solve this problem, if you do not > > > mind. Because, I can't use it in my FreeBSD system. > > > So, if you interested send me in private message your address and I will > > > send it as soon as possible. > > > > Thanks for the offer. I already have two variants of AX88178 based > > controller and both work fine without problems. I vaguely guess > > it could be related with ehci(4) as I don't see offending code in > > axe(4). Of course, this does not necessary mean axe(4) is bug free > > but I couldn't find clue yet. > > Hans, can you see other possible cause of the issue? > > > > Hi, > > I think it is a protocol issue. Maybe they created a new USB protocol ? > Hmm, it seems that AX88178 requires some special GPIO magic for RealTek PHY before accessing the PHY. I guess the magic in axe(4) is for Marvell PHY so it may/may not work for other AX88178 controllers. I also vaguely remember AX88178 with ET1101 PHY works on my box but it does not work well on other user's box. I thought it could be related with ehci(4) controller at that time but now I guess it came from missing GPIO magic in axe(4) for the specific PHY. It seems ASIX now requires login to get data sheet so I have no programming information for GPIO. My old data sheet for AX88178 didn't even mention GPIO handling. It seems Vendor's linux driver contains some magic for GPIO handling so I'll see what can I get from that. > --HPS
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100615194912.GJ4257>