From owner-freebsd-current@FreeBSD.ORG Mon Jun 14 03:16:22 2004 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 32D2816A4CE; Mon, 14 Jun 2004 03:16:22 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7694B43D48; Mon, 14 Jun 2004 03:16:21 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.12.11/8.12.11) with ESMTP id i5E3DXhn043730; Sun, 13 Jun 2004 21:13:33 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Sun, 13 Jun 2004 21:13:39 -0600 (MDT) Message-Id: <20040613.211339.81010369.imp@bsdimp.com> To: jhb@freebsd.org From: "M. Warner Losh" In-Reply-To: <200406041517.54827.jhb@FreeBSD.org> References: <200406041112.i54BC4b0029823@k9.a1.asic.gov.au> <200406041517.54827.jhb@FreeBSD.org> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org cc: tonymaher@optushome.com.au Subject: Re: fire up xmms, wi0 loses its mind 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: Mon, 14 Jun 2004 03:16:22 -0000 In message: <200406041517.54827.jhb@FreeBSD.org> John Baldwin writes: : On Friday 04 June 2004 07:12 am, Tony Maher wrote: : > John Baldwin wrote: : > > Probably acpi_pci_link.c as it exposes a bug in our link code (it doesn't : > > use a good algorithm for picking an IRQ to route interrupts to) : > : > Yes it is the problem. : > I have cvsupped to *default date=2004.05.28.17.30.00 : > Run (in effect) make world, network (and usb mouse) work fine. : > Installed acpi_pci_link.c v1.15 (instead of v1.14), make kernel, reboot : > fxp0 (and usb mouse) fail to work. : > : > So now what is the solution? : : I'm working on fixing the acpi_pci_link.c driver to (among other things) use a : better algorithm to pick IRQs so that it won't use IRQs used by ISA devices : for example. Or any interrupt that's configured for non-level operation... Warner