From owner-freebsd-stable@FreeBSD.ORG Mon Jun 16 14:03:20 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 7816837B401 for ; Mon, 16 Jun 2003 14:03:20 -0700 (PDT) Received: from mta05-svc.ntlworld.com (mta05-svc.ntlworld.com [62.253.162.45]) by mx1.FreeBSD.org (Postfix) with ESMTP id 66F8C43F85 for ; Mon, 16 Jun 2003 14:03:19 -0700 (PDT) (envelope-from scott@fishballoon.org) Received: from fishballoon.org ([81.104.195.199]) by mta05-svc.ntlworld.com (InterMail vM.4.01.03.37 201-229-121-137-20020806) with ESMTP id <20030616210318.TIGC19142.mta05-svc.ntlworld.com@fishballoon.org> for ; Mon, 16 Jun 2003 22:03:18 +0100 Received: from tuatara.fishballoon.org (tuatara [192.168.1.6]) by fishballoon.org (8.12.8p1/8.12.8) with ESMTP id h5GL2Z4o000204 for ; Mon, 16 Jun 2003 22:02:35 +0100 (BST) (envelope-from scott@tuatara.fishballoon.org) Received: (from scott@localhost) by tuatara.fishballoon.org (8.12.9/8.12.9/Submit) id h5GL2ZF4001473 for freebsd-stable@freebsd.org; Mon, 16 Jun 2003 22:02:35 +0100 (BST) (envelope-from scott) Date: Mon, 16 Jun 2003 22:02:35 +0100 From: Scott Mitchell To: freebsd-stable@freebsd.org Message-ID: <20030616210235.GB691@tuatara.fishballoon.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4i X-Operating-System: FreeBSD 4.8-STABLE i386 Subject: 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: Mon, 16 Jun 2003 21:03:20 -0000 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. I get the same behaviour on the VIA and Abit boards (remember it used to work on this one), with 4.8R, -STABLE and 5.1R. It's tempting to assume that the hardware has just gone bad, except that it still works on three different Win2K machines, one of which is also my -STABLE workstation. I know there's not much to go on, but if anyone has any idea what might have caused this, or how to work around it, or where to start looking to debug it myself, I'd love to hear it. If the hardware is bad, then I'll give it to a Windows user and move on, but it seems odd that it mostly works, and just can't be shut down cleanly. Scott -- =========================================================================== Scott Mitchell | PGP Key ID | "Eagles may soar, but weasels Cambridge, England | 0x54B171B9 | don't get sucked into jet engines" scott at fishballoon.org | 0xAA775B8B | -- Anon