From owner-freebsd-stable@FreeBSD.ORG Fri Jul 18 03:32:10 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 025F737B401; Fri, 18 Jul 2003 03:32:10 -0700 (PDT) Received: from mta06-svc.ntlworld.com (mta06-svc.ntlworld.com [62.253.162.46]) by mx1.FreeBSD.org (Postfix) with ESMTP id A9A5943F3F; Fri, 18 Jul 2003 03:32:08 -0700 (PDT) (envelope-from scott@fishballoon.org) Received: from llama.fishballoon.org ([81.104.195.199]) by mta06-svc.ntlworld.comESMTP <20030718103207.ZVHH16215.mta06-svc.ntlworld.com@llama.fishballoon.org>; Fri, 18 Jul 2003 11:32:07 +0100 Received: from scott by llama.fishballoon.org with local (Exim 4.20) id 19dSWJ-0001Wz-8y; Fri, 18 Jul 2003 11:31:23 +0100 Date: Fri, 18 Jul 2003 11:31:23 +0100 From: Scott Mitchell To: Josef Karthauser , freebsd-stable@freebsd.org Message-ID: <20030718103123.GB5243@llama.fishballoon.org> References: <20030616210235.GB691@tuatara.fishballoon.org> <20030717184648.GB851@genius.tao.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030717184648.GB851@genius.tao.org.uk> User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 4.8-RELEASE i386 Sender: Scott Mitchell Subject: Re: Weird USB lockup with Linksys USB100TX NIC X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Jul 2003 10:32:10 -0000 On Thu, Jul 17, 2003 at 07:46:48PM +0100, Josef Karthauser wrote: > On Mon, Jun 16, 2003 at 10:02:35PM +0100, Scott Mitchell wrote: > > So I have one of these, that I bought cheap on eBay. It was working just > > fine on my main -STABLE workstation (Abit KG7 motherboard), up until last > > Friday when I moved it onto the VIA EPIA-M machine I'm building. The NIC > > was detected OK as aue0, then the machine locked up running dhclient. It > > turns out that it wasn't really hung, but apparently spinning in the kernel > > on behalf of ifconfig. I say apparently, because the only thing I could > > figure out was that I had an ifconfig process consuming vast amounts of CPU > > in a wait on 'usbdly', before I got fed up waiting ~20s for keypresses to > > respond and rebooted. > > > > I've since discovered that I can reproduce this on demand by booting single > > user and doing an 'ifconfig down aue0'. This will take at least a minute > > to complete and leaves the machine almost totally unresponsive afterwards. > > I'll often get a bunch of 'usb error on rx: IOERROR' kernel messages while > > ifconfig is running. The NIC seems to still work OK otherwise. > > > > That's the network card that I use. Try plugging it into a 10 base > connection (instead of 100 base) and watch it work. I could never work > out why it hung my machine in 100 base mode. Josef, you're a lifesaver. Plugged it into my old, dumb 10Mbit hub and it works just fine. It certainly doesn't like the 10/100 switch that everything else is plugged into though. Thinking back, the point where it 'stopped working' might well be the time that I retired the old hub... the new switch arrived at the same time as the Mini-ITX box, and the Linksys card never wanted to work with that combination. I wonder if it's an autonegotiation problem? This switch is just a cheapy unmanaged DLink thing, so there's not much I can try here... maybe I'll take it into the office and see what the Catalyst switches think about it. This card is supposed to sit between my cable modem and new firewall/router box. Fortunately the modem (Terayon TJ210) appears to only have a 10BaseT port so I should be OK there. Many thanks, Scott