From owner-freebsd-current@FreeBSD.ORG Tue Oct 11 23:00:56 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 87F53106564A for ; Tue, 11 Oct 2011 23:00:56 +0000 (UTC) (envelope-from yanegomi@gmail.com) Received: from mail-qw0-f54.google.com (mail-qw0-f54.google.com [209.85.216.54]) by mx1.freebsd.org (Postfix) with ESMTP id 4929A8FC1A for ; Tue, 11 Oct 2011 23:00:56 +0000 (UTC) Received: by qadz30 with SMTP id z30so121276qad.13 for ; Tue, 11 Oct 2011 16:00:55 -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 :cc:content-type:content-transfer-encoding; bh=FhArGtevypuB4RKhnHPmqvhernJXD388M4YdRMV3HjA=; b=sPXqYkVYo0+GjcIRUctqkMgU8lLEf7lysSQKyAgYcZ74BagjttD8l7rLqHdIXazeRV 9f47Jv15GbIcDdXQ4w13IvvRTxy9YSYMJpQiDhCJcHrL6cLXK8x9oD6VfK8hQ0J6/o9i DG2nWnv9/S6m0IZni752TLX8N2j+2kt3mY2OU= MIME-Version: 1.0 Received: by 10.224.213.2 with SMTP id gu2mr12333060qab.85.1318374055539; Tue, 11 Oct 2011 16:00:55 -0700 (PDT) Received: by 10.224.74.82 with HTTP; Tue, 11 Oct 2011 16:00:55 -0700 (PDT) In-Reply-To: References: Date: Tue, 11 Oct 2011 16:00:55 -0700 Message-ID: From: Garrett Cooper To: Arnaud Lacombe Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: FreeBSD-Current 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 23:00:56 -0000 On Tue, Oct 11, 2011 at 3:53 PM, Arnaud Lacombe wrote: > Hi, > > On Tue, Oct 11, 2011 at 6:34 PM, Arnaud Lacombe wrot= e: >> 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... :( > > =A0- 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 configur= e 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 ? You might need to define a hint to use the KCS interface via device.hints. I don't remember the incantation exactly, but I think it was required for some Dells. ipmi(4) should have more info. Failing that, a BMC upgrade/downgrade might be required (some vendors don't test out BMC firmware upgrades really well, esp. in FreeBSD). HTH, -Garrett