On Tue, Oct 11, 2011 at 3:53 PM, Arnaud Lacombe <lacombar_at_gmail.com> wrote: > Hi, > > On Tue, Oct 11, 2011 at 6:34 PM, Arnaud Lacombe <lacombar_at_gmail.com> 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: <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... :( > > - Arnaud > >> Now, 6 is ENXIO, which match the following resource allocation failure: >> >> if (info.offset == 1) { >> sc->ipmi_io_rid = 0; >> sc->ipmi_io_res[0] = bus_alloc_resource(dev, type, >> &sc->ipmi_io_rid, info.address, info.address + count - 1, >> count, RF_ACTIVE); >> if (sc->ipmi_io_res[0] == NULL) { >> device_printf(dev, "couldn't configure I/O resource\n"); >> return (ENXIO); >> } >> } >> >> 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, -GarrettReceived on Tue Oct 11 2011 - 21:00:56 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:19 UTC