Date: Tue, 11 Oct 2011 16:00:55 -0700 From: Garrett Cooper <yanegomi@gmail.com> To: Arnaud Lacombe <lacombar@gmail.com> Cc: FreeBSD-Current <freebsd-current@freebsd.org> Subject: Re: ipmi(4)/isa woes Message-ID: <CAGH67wRvTiaBAwxWajSr86-2cUtXkPvFwqwwwEoeAjUaxh%2B=zg@mail.gmail.com> In-Reply-To: <CACqU3MWGscjDT=ONbZfXGjNMM75YWUb_406Wh4PsxEBh_ymj6w@mail.gmail.com> References: <CACqU3MU4YekO2c%2BVvty_9aWmM2L5xthDtAXNeH%2BW9LUf6kxTWg@mail.gmail.com> <CACqU3MWGscjDT=ONbZfXGjNMM75YWUb_406Wh4PsxEBh_ymj6w@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Oct 11, 2011 at 3:53 PM, Arnaud Lacombe <lacombar@gmail.com> wrote:
> Hi,
>
> On Tue, Oct 11, 2011 at 6:34 PM, Arnaud Lacombe <lacombar@gmail.com> 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: <IPMI System Interface> 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: <IPMI System Interface> port 0xca2,0xca3 on acpi0
> ipmi0: KCS mode found at io 0xca2 on acpi
> ipmi1: <IPMI System Interface> on isa0
> device_attach: ipmi1 attach returned 16
> pmtimer0 on isa0
> ipmi1: <IPMI System Interface> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAGH67wRvTiaBAwxWajSr86-2cUtXkPvFwqwwwEoeAjUaxh%2B=zg>