From owner-freebsd-current@FreeBSD.ORG Mon Sep 21 09:14:11 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6AC5A1065670 for ; Mon, 21 Sep 2009 09:14:11 +0000 (UTC) (envelope-from gary.jennejohn@freenet.de) Received: from mout7.freenet.de (mout7.freenet.de [IPv6:2001:748:100:40::2:9]) by mx1.freebsd.org (Postfix) with ESMTP id 0875D8FC12 for ; Mon, 21 Sep 2009 09:14:11 +0000 (UTC) Received: from [195.4.92.10] (helo=0.mx.freenet.de) by mout7.freenet.de with esmtpa (ID gary.jennejohn@freenet.de) (port 25) (Exim 4.69 #92) id 1MpeyH-0001x8-A0; Mon, 21 Sep 2009 11:14:09 +0200 Received: from tfea6.t.pppool.de ([89.55.254.166]:27255 helo=ernst.jennejohn.org) by 0.mx.freenet.de with esmtpa (ID gary.jennejohn@freenet.de) (port 25) (Exim 4.69 #94) id 1MpeyH-0001oD-3S; Mon, 21 Sep 2009 11:14:09 +0200 Date: Mon, 21 Sep 2009 11:14:07 +0200 From: Gary Jennejohn To: "David E. Cross" Message-ID: <20090921111407.248d068c@ernst.jennejohn.org> In-Reply-To: <1253500439.24101.8.camel@kagome> References: <1253500439.24101.8.camel@kagome> X-Mailer: Claws Mail 3.7.2 (GTK+ 2.16.2; amd64-portbld-freebsd8.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: psm0: unable to allocation IRQ (solution, well workaround) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: gary.jennejohn@freenet.de List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Sep 2009 09:14:11 -0000 On Sun, 20 Sep 2009 22:33:59 -0400 "David E. Cross" wrote: > I recently stumbled across this bug, and I have a solution to my > specific case. > > The problem is the following: > acpi_ibm0: irq 12 on acpi0 > > > _IF_, I put "device acpi_ibm" into the kernel config, disaster, psm0 is > unable to attach. > > If I "acpi_ibm_load="YES"" in /boot/loader.conf, I then get the > following: > acpi_ibm0: on acpi0 > > Note the lack of "irq12" > > Which then frees up: > > psm0: irq 12 on atkbdc0 > > > Now, psm0 maps its IRQ as RF_SHAREABLE, so it _should_ work regardless, > right? > > I'd regard this as a fairly serious bug. > > I'm really at a loss of where to track it down more, looking at the > acpi_ibm code, its pretty opaque as to how resource allocations are done > and why this would ever map irq 12 (well, at least to me). > I would guess (note - guess) that it's a matter of ordering in the kernel. When acpi_ibm is in the kernel it gets probed and attached before psm by the ACPI code and wins the race for irq allocation. If it's loaded as a module then psm has already gotten irq 12 so acpi_ibm is not assigned an irq. --- Gary Jennejohn