Date: Wed, 2 Nov 2005 21:41:53 GMT From: Mike <perrimd@pace.k12.mi.us> To: freebsd-gnats-submit@FreeBSD.org Subject: usb/88408: axe0 read PHY failed Message-ID: <200511022141.jA2LfrxX078127@www.freebsd.org> Resent-Message-ID: <200511022150.jA2LoApq079347@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 88408
>Category: usb
>Synopsis: axe0 read PHY failed
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: freebsd-usb
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Wed Nov 02 21:50:09 GMT 2005
>Closed-Date:
>Last-Modified:
>Originator: Mike
>Release: FreeBSD 5.4-RELEASE #1
>Organization:
PACE
>Environment:
FreeBSD minimiller.pace.k12.mi.us 5.4-RELEASE FreeBSD 5.4-RELEASE #1: Fri Jul 1 16:38:21
EDT 2005 root@tunnel.pace.k12.mi.us:/usr/obj/usr/src/sys/5.4 i386
>Description:
The axe interface when using a USB Netgear FA120 will get multiple read PHY failed and then become inoperative. Unloading if_axe.ko and then reloading brings the adapter back up.
The OS is running on a VIA ML1000 mini itx motherboard. Unit boots from flash so root is read only.
I have the same problem on the via CL1000 also. I have tried other FA120s and have ruled out bad adpater hardware.
>How-To-Repeat:
Unknown cause ??? Seems to be random. If if_axe.ko is buit into the kernel the unit will not completely boot. Maybe this is somehow related ?
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200511022141.jA2LfrxX078127>