Date: Fri, 21 Oct 2011 16:19:45 -0400 From: John Baldwin <jhb@freebsd.org> To: freebsd-current@freebsd.org Cc: Arnaud Lacombe <lacombar@gmail.com> Subject: Re: ipmi(4)/isa woes Message-ID: <201110211619.45623.jhb@freebsd.org> 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 Tuesday, October 11, 2011 6:53:11 pm Arnaud Lacombe wrote: > Hi, > > On Tue, Oct 11, 2011 at 6:34 PM, Arnaud Lacombe <lacombar@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 Resource 0 is not right and will not work. In this case your BIOS has a buggy SMBIOS / DMI table entry for IPMI. > 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 You can ignore the ipmi1 messages. > However, the driver fails right after with: > > ipmi0: Timed out waiting for GET_DEVICE_ID Are you sure you have working IPMI? The timeouts and the busted DMI table is consistent with a machine where IPMI is available via an optional daughterboard, but the daughterboard isn't installed. -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201110211619.45623.jhb>