From owner-freebsd-current@FreeBSD.ORG Wed Jun 11 01:34:20 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6742237B401 for ; Wed, 11 Jun 2003 01:34:20 -0700 (PDT) Received: from yori.schoko.org (yori.schoko.org [62.109.128.56]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1427943F85 for ; Wed, 11 Jun 2003 01:34:19 -0700 (PDT) (envelope-from nick@schoko.org) Received: from yori.schoko.org (nick@localhost [127.0.0.1]) by yori.schoko.org (8.12.9/8.12.9) with ESMTP id h5B8YGVF039074 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 11 Jun 2003 10:34:16 +0200 (CEST) (envelope-from nick@yori.schoko.org) Received: (from nick@localhost) by yori.schoko.org (8.12.9/8.12.9/Submit) id h5B8YF7C039073; Wed, 11 Jun 2003 10:34:15 +0200 (CEST) Date: Wed, 11 Jun 2003 10:34:15 +0200 From: Markus Wennrich To: Paul Richards Message-ID: <20030611083415.GG21814@yori.schoko.org> References: <20030603210021.GC843@speedy.unibe.ch> <1054591160.1641.17.camel@cf.freebsd-services.com> <20030603221716.GD843@speedy.unibe.ch> <1054594939.1641.52.camel@cf.freebsd-services.com> <20030610120854.GX21814@yori.schoko.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030610120854.GX21814@yori.schoko.org> User-Agent: Mutt/1.5.4i cc: current@freebsd.org Subject: Re: fxp0: device timeout with 5.1BETA2 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jun 2003 08:34:20 -0000 On Tue, Jun 10, 2003 at 02:08:54PM +0200, Markus Wennrich wrote: > > > > > fxp0: device timeout > > > > I get these as well. Is it on irq9 by any chance, along with acpi0 ? > > > > > > No. It's on irc 11 device 8 (as dmesg states). All irqs in bios are > > > set to 11 (factory default). ACPI is disabled. > > > > Ok, well that's a useful data point (for me anyway) since it means > > there's a problem with fxp losing interrupts that's not related to some > > other ACPI problems I've experienced, suggesting that it's therefore a > > fxp driver problem. > > I have the same problem here with a freshly cvsupped 5.1-CURRENT. > The machine has two fxp-NICs and I get device timeouts with both of > them (with acpi enabled or disabled, both the same, no change). See > attached dmesg. Well, I got a little further: Until yesterday, my fxp's both hat "irq 10", shared with the uhci-usb-controller. Everything worked fine. Since the cvsup, fxp0 uses "irq 3" (shared with sio0) and fxp1 "irq 10" (shared with uhci0), which didn't work. If I remove "sio" from my kernel-config, fxp0 works fine. But if I use the fxp1-device (dhclient or ifconfig) the machine freezes immediatly. Then I tried to also remove the usb-support, so the fxp1 has irq 10 soley for itself ... doesn't work. The machine still freezes. (I tried to pinpoint both irq's to irq 3 via device.hints (hint.fxp.1.irq=3) ... didn't worked.) Well ... at least I can use fxp0 if it has its irq soley for itself. But the machine still freezes, if I try to use fxp1. Any ideas what else I could try? I volunteer for debugging ;-) Bye, Markus -- Unix IS user friendly ... it's just selective about who its friends are.