From owner-freebsd-stable@FreeBSD.ORG Wed Apr 13 18:25:58 2005 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 2B05416A4D3 for ; Wed, 13 Apr 2005 18:25:58 +0000 (GMT) Received: from ns1.onsitepcs.net (ns1.onsitepcs.net [71.32.223.153]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9E6B343D31 for ; Wed, 13 Apr 2005 18:25:57 +0000 (GMT) (envelope-from jaimie@onsitepcs.net) Received: from ns1.onsitepcs.net (localhost.localdomain [127.0.0.1]) by ns1.onsitepcs.net (8.13.1/8.13.1) with ESMTP id j3DBQsJw014139 for ; Wed, 13 Apr 2005 11:26:54 GMT Received: from localhost (localhost [[UNIX: localhost]]) by ns1.onsitepcs.net (8.13.1/8.13.1/Submit) id j3DBQrOY014138 for freebsd-stable@freebsd.org; Wed, 13 Apr 2005 11:26:53 GMT X-Authentication-Warning: ns1.onsitepcs.net: jaimie set sender to jaimie@onsitepcs.net using -f From: Jaimie Garner Organization: Onsite PCS inc. To: freebsd-stable@freebsd.org Date: Wed, 13 Apr 2005 11:26:53 +0000 User-Agent: KMail/1.7.1 References: <200504130550.27484.jaimie@onsitepcs.net> <20050413161556.GA82955@slackbox.xs4all.nl> In-Reply-To: <20050413161556.GA82955@slackbox.xs4all.nl> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200504131126.53450.jaimie@onsitepcs.net> Subject: Re: Problems with 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: Wed, 13 Apr 2005 18:25:58 -0000 How about disable USB altogether since it is not used on this machine. Thanks for the info On Wednesday 13 April 2005 16:15, Roland Smith wrote: > On Wed, Apr 13, 2005 at 05:50:27AM +0000, Jaimie Garner wrote: > > This just started happing this evening not sure what is up. The nic > > is a Linksys LNE 100 V 4.something I forget now. I had some weird > > errors a while back when I first installed 5.3-RELEASE but i disabled > > ACPI and they seemed to work fine. > > > > Here is some info > > dc0: port 0x1000-0x10ff mem > > 0xfc001000-0xfc0013ff irq 9 at device 12.0 on pci0on pci0 > > miibus0: on dc0i0 > > ukphy0: on miibus0 > > ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > > dc0: Ethernet address: 00:03:6d:16:09:1e > > dc0: if_start running deferred for Giant > > dc0: [GIANT-LOCKED] > > > > This looks odd especaly this: > > Interrupt storm detected on "irq9: dc0 ohci0"; throttling interrupt > > source > > Looks like the USB bus (ohci0) and your network card are sharing an > interrupt line. My guess would be that a USB device generates too much > interrupts causing the kernel to throttle them. This then screws up the > network. > > According to polling(4), the dc driver supports polling instead of using > an interrupt line. You could try rebuilding the kernel with polling > support and see if the problem goes away. > > Or you could disable ohci0 in the bios, or plug the offending USB device > into another port. > > Or you could try to force the dc triver to use another interrupt > line. See the acpi manual page and google for 'irq routing freebsd'. I > _think_ you should do the following: 'ps -xa|grep irq' will show which > irq's are free. Let's say that irq 10 is still free. Now you'd have to > find the pci address of the network card with 'pciconf -l -v|grep dc0'. > Let's say you get something like 'dc0@pci0:11:0' You can now tune the > interrupt by setting the following in /boot/device.hints: > > hw.acpi.pci.link.0.11.0.irq=10 > > HTH, > > Roland -- Jaimie Garner Onsite PCS inc. 323 SE RIverside AV Grants Pass, OR 97526 541.471.1343 866.471.1343 jaimie@onsitepcs.net www.onistepcs.net