Date: Mon, 2 Apr 2012 08:49:58 -0400 From: John Baldwin <jhb@freebsd.org> To: Sean Bruno <seanbru@yahoo-inc.com> Cc: "freebsd-stable@freebsd.org" <freebsd-stable@freebsd.org> Subject: Re: [stable-ish 9] Dell R815 ipmi(4) attach failure Message-ID: <201204020849.58087.jhb@freebsd.org> In-Reply-To: <1333143034.4450.1.camel@powernoodle-l7.corp.yahoo.com> References: <1333039719.3948.3.camel@powernoodle-l7.corp.yahoo.com> <201203301714.37323.jhb@freebsd.org> <1333143034.4450.1.camel@powernoodle-l7.corp.yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Friday, March 30, 2012 5:30:34 pm Sean Bruno wrote: > > > This is the relevant bits: > > > > Handle 0x2600, DMI type 38, 18 bytes > > IPMI Device Information > > Interface Type: KCS (Keyboard Control Style) > > Specification Version: 2.0 > > I2C Slave Address: 0x10 > > NV Storage Device: Not Present > > Base Address: 0x0000000000000CA8 (I/O) > > Register Spacing: 32-bit Boundaries > > > > Note the '32-bit' boundaries. I think ACPI doesn't support that for its > > attachment (well, it does if they specify each port as a separate thing in > > _CRS). Can you get acpidump -d output? > > > > Aye, here ya go. > > http://people.freebsd.org/~sbruno/acpidump_r815.txt Hmm, that actually looks correct. Try sabotaging the ACPI attach just for testing (i.e. add a 'return (ENXIO)' to the top of the probe routine in ipmi_acpi.c) just to see if that makes a difference. If not, then I think the BMC is just broken or your BIOS is lying. -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201204020849.58087.jhb>