Date: Sun, 20 Aug 2006 10:30:18 GMT From: =?ISO-8859-1?Q?Oddbj=F8rn_Steffensen?= <oddbjorn@tricknology.org> To: freebsd-usb@FreeBSD.org Subject: Re: usb/88408: axe0 read PHY failed Message-ID: <200608201030.k7KAUIZY062969@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR usb/88408; it has been noted by GNATS. From: =?ISO-8859-1?Q?Oddbj=F8rn_Steffensen?= <oddbjorn@tricknology.org> To: bug-followup@FreeBSD.org, perrimd@pace.k12.mi.us Cc: Subject: Re: usb/88408: axe0 read PHY failed Date: Sun, 20 Aug 2006 12:24:17 +0200 I had the same problem on an EPIA-based box running a recent RELENG_6 equipped with both a D-Link and an SMC USB Ethernet adapter (both using the axe driver). The symptoms were identical; after a period of time one of the interfaces locked up, spewing read PHY failed messages. Tried to limit it by forcing the interfaces to 10baseT/UTP, and this made them recover automatically: Aug 20 11:33:09 epia kernel: axe0: link state changed to DOWN Aug 20 11:33:09 epia kernel: axe0: read PHY failed Aug 20 11:33:09 epia kernel: axe0: read PHY failed Aug 20 11:33:09 epia kernel: axe0: link state changed to UP Aug 20 11:33:09 epia kernel: axe0: read PHY failed Aug 20 11:33:09 epia kernel: axe0: read PHY failed Aug 20 11:33:09 epia kernel: axe0: link state changed to DOWN Aug 20 11:33:09 epia kernel: axe0: read PHY failed Aug 20 11:33:09 epia kernel: axe0: link state changed to UP However, forcing the interface to full-duplex made the problem go away, even at 100baseTX and heavy load. The driver could perhaps handle duplex mismatches a bit more gracefully?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200608201030.k7KAUIZY062969>