From owner-freebsd-current@FreeBSD.ORG Tue Oct 11 22:53:13 2011 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 2008B106566B for ; Tue, 11 Oct 2011 22:53:13 +0000 (UTC) (envelope-from lacombar@gmail.com) Received: from mail-ww0-f50.google.com (mail-ww0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id A9E418FC22 for ; Tue, 11 Oct 2011 22:53:12 +0000 (UTC) Received: by wwe3 with SMTP id 3so128543wwe.31 for ; Tue, 11 Oct 2011 15:53:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=dCEt5AG8GIhRe+5mZFaLi8FIWOPz9WHFlNufe8vq44k=; b=FlxPOTJ1oxivOqeM/NnmZugAkAZL/Sq1ZAd44/Os2Yqi9FzMQVKqyq2+KoAAGMtEJF S2crscOoga3M3ZASVg3nm40yDmfNdo1xJPNaS1HOHwVhcQmuWp0EGn3yjiQwyWVWhrnw eDoxdx+9/cdmgaH3DNMSBZlSVVbzafXsHkVPU= MIME-Version: 1.0 Received: by 10.227.29.161 with SMTP id q33mr64101wbc.49.1318373591645; Tue, 11 Oct 2011 15:53:11 -0700 (PDT) Received: by 10.180.103.33 with HTTP; Tue, 11 Oct 2011 15:53:11 -0700 (PDT) In-Reply-To: References: Date: Tue, 11 Oct 2011 18:53:11 -0400 Message-ID: From: Arnaud Lacombe To: FreeBSD-Current Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: ipmi(4)/isa woes X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Tue, 11 Oct 2011 22:53:13 -0000 Hi, On Tue, Oct 11, 2011 at 6:34 PM, Arnaud Lacombe wrote: > Hi folks, > > I've got a machine where ipmi(4) seem to be unable to fully attach. > 10-current kernel complains the following way: > > ipmi0: at iomem 0-0x1 on isa0 > ipmi0: KCS mode found at mem 0x0 alignment 0x1 on isa > ipmi0: couldn't configure I/O resource > device_attach: ipmi0 attach returned 6 > Actually, I can bypass this issue by enabling acpi(4): ipmi0: port 0xca2,0xca3 on acpi0 ipmi0: KCS mode found at io 0xca2 on acpi ipmi1: on isa0 device_attach: ipmi1 attach returned 16 pmtimer0 on isa0 ipmi1: on isa0 device_attach: ipmi1 attach returned 16 However, the driver fails right after with: ipmi0: Timed out waiting for GET_DEVICE_ID and thus never complete its startup... :( - Arnaud > Now, 6 is ENXIO, which match the following resource allocation failure: > > =A0if (info.offset =3D=3D 1) { > =A0 =A0 =A0 =A0 =A0sc->ipmi_io_rid =3D 0; > =A0 =A0 =A0 =A0 =A0sc->ipmi_io_res[0] =3D bus_alloc_resource(dev, type, > =A0 =A0 =A0 =A0 =A0 =A0 =A0&sc->ipmi_io_rid, info.address, info.address += count - 1, > =A0 =A0 =A0 =A0 =A0 =A0 =A0count, RF_ACTIVE); > =A0 =A0 =A0 =A0 =A0if (sc->ipmi_io_res[0] =3D=3D NULL) { > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0device_printf(dev, "couldn't configure= I/O resource\n"); > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0return (ENXIO); > =A0 =A0 =A0 =A0 =A0} > =A0} > > Has anyone encountered this issue ? > > Thanks, > =A0- Arnaud >