Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 30 Mar 2012 17:14:36 -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:  <201203301714.37323.jhb@freebsd.org>
In-Reply-To: <1333137834.4450.0.camel@powernoodle-l7.corp.yahoo.com>
References:  <1333039719.3948.3.camel@powernoodle-l7.corp.yahoo.com> <201203301229.45069.jhb@freebsd.org> <1333137834.4450.0.camel@powernoodle-l7.corp.yahoo.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Friday, March 30, 2012 4:03:54 pm Sean Bruno wrote:
> On Fri, 2012-03-30 at 09:29 -0700, John Baldwin wrote:
> > On Thursday, March 29, 2012 12:48:39 pm Sean Bruno wrote:
> > > Noting a failure to attach to the onboard IPMI controller with this dell
> > > R815.  Not sure what to start poking at and thought I'd though this over
> > > here for comment.
> > > 
> > > -bash-4.2$ dmesg |grep ipmi
> > > ipmi0: KCS mode found at io 0xca8 on acpi
> > > ipmi1: <IPMI System Interface> on isa0
> > > device_attach: ipmi1 attach returned 16
> > > ipmi1: <IPMI System Interface> on isa0
> > > device_attach: ipmi1 attach returned 16
> > > ipmi0: Timed out waiting for GET_DEVICE_ID
> > > 
> > > 
> > > -bash-4.2$ sysctl -a|grep ipmi
> > > device          ipmi            # IPMI
> > > hw.ipmi.on: 1
> > > dev.ipmi.0.%desc: IPMI System Interface
> > > dev.ipmi.0.%driver: ipmi
> > > dev.ipmi.0.%location: handle=\_SB_.PCI0.ISA_.NIPM
> > > dev.ipmi.0.%pnpinfo: _HID=IPI0001 _UID=5
> > > dev.ipmi.0.%parent: acpi0
> > 
> > Can you get dmidecode output?
> > 
> 
> 
> http://people.freebsd.org/~sbruno/dmidecode_r815.txt

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?

-- 
John Baldwin



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201203301714.37323.jhb>