From owner-freebsd-usb@FreeBSD.ORG Sun Aug 20 10:30:18 2006 Return-Path: X-Original-To: freebsd-usb@hub.freebsd.org Delivered-To: freebsd-usb@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ADDAC16A4E0 for ; Sun, 20 Aug 2006 10:30:18 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7572C43D49 for ; Sun, 20 Aug 2006 10:30:18 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k7KAUIo1062971 for ; Sun, 20 Aug 2006 10:30:18 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k7KAUIZY062969; Sun, 20 Aug 2006 10:30:18 GMT (envelope-from gnats) Date: Sun, 20 Aug 2006 10:30:18 GMT Message-Id: <200608201030.k7KAUIZY062969@freefall.freebsd.org> To: freebsd-usb@FreeBSD.org From: =?ISO-8859-1?Q?Oddbj=F8rn_Steffensen?= Cc: Subject: Re: usb/88408: axe0 read PHY failed X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: =?ISO-8859-1?Q?Oddbj=F8rn_Steffensen?= List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Aug 2006 10:30:18 -0000 The following reply was made to PR usb/88408; it has been noted by GNATS. From: =?ISO-8859-1?Q?Oddbj=F8rn_Steffensen?= 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?