Bug 71280

Summary: [aue] aue0 device (linksys usb100tx) doesn't work in 100basetx, and doesn't reliably select media
Product: Base System Reporter: Josef Karthauser <joe>
Component: usbAssignee: freebsd-usb (Nobody) <usb>
Status: Open ---    
Severity: Affects Only Me    
Priority: Normal    
Version: 6.0-CURRENT   
Hardware: Any   
OS: Any   

Description Josef Karthauser 2004-09-02 10:40:24 UTC 
	The aue0 device I have, a linksys usb100tx, doesn't work
	in 100basetx mode.  If it is plugged into a 100base network
	the device freezes and any network activity, or just issueing
	an ifconfig command ends up with:

	aue0: MII read timed out
	aue0: MII read timed out
	aue0: MII read timed out
	aue0: MII read timed out
	aue0: MII read timed out
	aue0: usb error on rx: IOERROR
	aue0: usb error on rx: IOERROR
	aue0: usb error on rx: IOERROR
	aue0: usb error on rx: IOERROR
	aue0: usb error on rx: IOERROR
	aue0: usb error on rx: IOERROR
	aue0: MII read timed out
	aue0: usb error on rx: IOERROR
	aue0: usb error on rx: IOERROR
	aue0: usb error on rx: IOERROR
	aue0: usb error on rx: IOERROR
	aue0: MII read timed out

	Additionally issuing an 'ifconfig aue0 media 10baset/utp'
	isn't always reliable.  The device doesn't appear to care
	too much about the media that you tell it about, once it
	has made it's mind up what kind of network it is plugged
	into.

Fix: 

The only work around at the moment is to unplug the ethernet,
	boot the machine and then issue an 'ifconfig aue0 media
	10baset/utp' by hand before plugging the cable in.  The device
	has an orange light for a 10base network and a gree light
	for a 100base network.  If having issued the ifconfig command 
	you get a green light then the machine need to be rebooted and
	everything done again.  If you get an orange light then the
	device correctly thinks that it is in 10base mode and you can
	issue a dhclient command or set the ip address.
How-To-Repeat: 	Boot up a machine with this device plugged in and plug it
	into a switched 100tx network.
Comment 1 Mark Linimon freebsd_committer freebsd_triage 2004-10-08 06:36:20 UTC 
Responsible Changed
From-To: freebsd-i386->freebsd-bugs

This does not sound i386-specific.
Comment 2 Mark Linimon freebsd_committer freebsd_triage 2005-11-12 17:09:53 UTC 
State Changed
From-To: open->feedback

Is this still a problem in 6.0-RELEASE?
Comment 3 cwf-ml 2006-11-03 21:12:56 UTC 
This is not a followup per se, but I see this problem with 6.1-RELEASE-p6.

The only difference to the original error description is that when I
plug the device in after the system has completed booting, it works 
normally. Problem occurs only when the device is plugged in while booting.

It happens with both cold and warm boot and with both half- and full
duplex connection.

My hardware is a "Teledat Fast Ethernet USB".
Comment 4 Mark Linimon freebsd_committer freebsd_triage 2007-06-30 09:29:32 UTC 
State Changed
From-To: feedback->open

Reassign to usb team, while noting that feedback was received some time ago.
Comment 5 Mark Linimon freebsd_committer freebsd_triage 2007-06-30 09:29:32 UTC 
Responsible Changed
From-To: freebsd-bugs->freebsd-usb
Comment 6 Eitan Adler freebsd_committer freebsd_triage 2017-12-31 08:01:10 UTC 
For bugs matching the following criteria:

Status: In Progress Changed: (is less than) 2014-06-01

Reset to default assignee and clear in-progress tags.

Mail being skipped