IPMI is broken on Intel S1200RP Board

venom

unread,

Apr 9, 2014, 4:56:27 AM4/9/14

to

Hello

I have a problem on Intel S1200RP Board

# uname -a
FreeBSD anonymous.orb 10.0-RELEASE FreeBSD 10.0-RELEASE #0 r260789: Thu Jan
16 22:34:59 UTC 2014 ro...@snap.freebsd.org:/usr/obj/usr/src/sys/GENERIC
amd64
# dmidecode -t 38
# dmidecode 2.12
SMBIOS 2.7 present.

Handle 0x0090, DMI type 38, 16 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: 0x0000000000000CA2 (I/O)
# kldload ipmi
# ipmitool sel list
Could not open device at /dev/ipmi0 or /dev/ipmi/0 or /dev/ipmidev/0: No
such file or directory
Get SEL Info command failed
# grep ipmi /boot/device.hints | wc -l
0

But IPMI work on Linux host
part of dmesg output
--------------------------------------------------------------------------------------
[ 1374.180289] ipmi message handler version 39.2
[ 1374.181442] IPMI Watchdog: driver initialized
[ 1380.685919] Copyright (C) 2004 MontaVista Software - IPMI Powerdown via
sys_reboot.
[ 1384.000797] IPMI System Interface driver.
[ 1384.000941] ipmi_si: probing via SMBIOS
[ 1384.001027] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
[ 1384.001143] ipmi_si: Adding SMBIOS-specified kcs state machine
[ 1384.001311] ipmi_si: probing via SPMI
[ 1384.001400] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
[ 1384.001493] ipmi_si: Adding SPMI-specified kcs state machine duplicate
interface
[ 1384.001661] ipmi_si: Trying SMBIOS-specified kcs state machine at i/o
address 0xca2, slave address 0x20, irq 0
[ 1384.141050] ipmi_si ipmi_si.0: Found new BMC (man_id: 0x000157, prod_id:
0x0065, dev_id: 0x21)
[ 1384.142999] IPMI poweroff: ATCA Detect mfg 0x157 prod 0x65
[ 1384.143097] IPMI poweroff: Found a chassis style poweroff function
[ 1384.146161] ipmi_si ipmi_si.0: IPMI kcs interface initialized
[ 1401.695688] ipmi device interface
--------------------------------------------------------------------------------------

# uname -rm
3.2.0-4-amd64 x86_64
# ipmitool sel
SEL Information
Version : 1.5 (v1.5, v2 compliant)
Entries : 312
Free Space : 59886 bytes
Percent Used : 7%
Last Add Time : 04/09/2014 06:26:42
Last Del Time : Not Available
Overflow : false
Supported Cmds : 'Partial Add' 'Reserve' 'Get Alloc Info'
# of Alloc Units : 3639
Alloc Unit Size : 18
# Free Units : 3327
Largest Free Blk : 3327
Max Record Size : 12

What strings need add to the file /boot/device.hints for enable access to
IPMI ?

--
Vladimir Laskov
_______________________________________________
freebsd...@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hacke...@freebsd.org"

venom

unread,

Apr 9, 2014, 5:15:15 AM4/9/14

to

# grep ipmi /boot/device.hints
hint.ipmi.0.at="isa"
hint.ipmi.0.mode="KCS"

# ipmitool sel
SEL Information
Version : 1.5 (v1.5, v2 compliant)

Entries : 472
Free Space : 57006 bytes
Percent Used : 11%
Last Add Time : 04/09/2014 13:09:22

Last Del Time : Not Available
Overflow : false
Supported Cmds : 'Partial Add' 'Reserve' 'Get Alloc Info'
# of Alloc Units : 3639
Alloc Unit Size : 18

# Free Units : 3167
Largest Free Blk : 3167
Max Record Size : 12

Access to IPMI is enabled,
thanks

--
Vladimir Laskov

Sean Bruno

unread,

Apr 10, 2014, 3:07:27 PM4/10/14

to

From your error report, I expect that the ipmi driver failed to attach
at startup. Can you do a verbose boot and post the dmesg for me to
review please?

sean

signature.asc

venom

unread,

Apr 10, 2014, 11:43:12 PM4/10/14

to

dmesg output is attached
procedure "kldload ipmi" is at end of file

venom

unread,

Apr 10, 2014, 11:47:15 PM4/10/14

to

ppc1: cannot reserve I/O port range
pcib0: allocated type 4 (0x60-0x60) for rid 0 of atkbdc0
pcib0: allocated type 4 (0x64-0x64) for rid 1 of atkbdc0
atkbdc0: AT keyboard controller not found
pcib0: allocated type 4 (0x3f0-0x3f5) for rid 0 of fdc0
pcib0: allocated type 4 (0x3f7-0x3f7) for rid 1 of fdc0
ppc0: cannot reserve I/O port range
pci0: driver added
found-> vendor=0x8086, dev=0x8c22, revid=0x05
domain=0, bus=0, slot=31, func=3
class=0c-05-00, hdrtype=0x00, mfdev=0
cmdreg=0x0143, statreg=0x0280, cachelnsz=0 (dwords)
lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns)
intpin=c, irq=18
pci0:0:31:3: reprobing on driver added
found-> vendor=0x8086, dev=0x8c24, revid=0x05
domain=0, bus=0, slot=31, func=6
class=11-80-00, hdrtype=0x00, mfdev=0
cmdreg=0x0006, statreg=0x0010, cachelnsz=0 (dwords)
lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns)
intpin=c, irq=18
powerspec 3 supports D0 D3 current D0
MSI supports 1 message
pci0:0:31:6: reprobing on driver added
pci1: driver added
pci2: driver added
pci0: driver added
found-> vendor=0x8086, dev=0x8c22, revid=0x05
domain=0, bus=0, slot=31, func=3
class=0c-05-00, hdrtype=0x00, mfdev=0
cmdreg=0x0143, statreg=0x0280, cachelnsz=0 (dwords)
lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns)
intpin=c, irq=18
pci0:0:31:3: reprobing on driver added
found-> vendor=0x8086, dev=0x8c24, revid=0x05
domain=0, bus=0, slot=31, func=6
class=11-80-00, hdrtype=0x00, mfdev=0
cmdreg=0x0006, statreg=0x0010, cachelnsz=0 (dwords)
lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns)
intpin=c, irq=18
powerspec 3 supports D0 D3 current D0
MSI supports 1 message
pci0:0:31:6: reprobing on driver added
pci1: driver added
pci2: driver added

Sean Bruno

unread,

Apr 11, 2014, 12:08:59 PM4/11/14

to

I don't see an attach here, so I assume that something is "new" in the
acpi tables on this board. Can you dump the ACPI table somewhere
"acpidump -dt > intel_s1200rp.dsdt" and post it somewhere we can look at
it?

freebsd.org mailing lists will strip attachments in most cases, so a
pastebin or other link would be best.

sean

signature.asc

Vladimir Laskov

unread,

Apr 11, 2014, 2:42:52 PM4/11/14

to

links
https://bitbucket.org/weec/docs/downloads/dmesg_verbose_boot.log
https://bitbucket.org/weec/docs/downloads/intel_s1200rp.dsdt

Sean Bruno

unread,

Apr 11, 2014, 3:12:41 PM4/11/14

to

On Fri, 2014-04-11 at 22:42 +0400, Vladimir Laskov wrote:
>
>
> links
> https://bitbucket.org/weec/docs/downloads/dmesg_verbose_boot.log
> https://bitbucket.org/weec/docs/downloads/intel_s1200rp.dsdt
>
>

Wanted to xpost this over to freebsd-acpi too. Since it looks to me
that the IPMI driver isn't getting invoked, I assume that its because of
a variance in ACPI parsing of the relevant IPMI section.

sean

signature.asc

John Baldwin

unread,

Apr 11, 2014, 3:07:58 PM4/11/14

to

Linux attached it via smbios (not ACPI) from what I could tell. That
should work under FreeBSD as well, but I think it means you want to look
at the smbios identify code in the ipmi(4) driver to debug this. The
dmidecode info for this particular BMC was posted earlier in the thread
already.

--
John Baldwin

Lanny Baron

unread,

Apr 11, 2014, 4:28:50 PM4/11/14

to

Go into bios of the Server Board. Ensure you have valid
IP/Netmask/gateway for BMC.

On another box, run #ipmitool -H ip.add.re.ss sel list
where ip.add.... is the IP of that 'broken s1200rp'

ou should get a reply and some data.

Regards,
+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=
Lanny Baron
Servaris Corporation
High Performance Servers and RAID Systems

http://www.servaris.com/

Toll Free: 1.877.963.1900
+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=

Y

On 14-04-11 03:12 PM, Sean Bruno wrote:
> On Fri, 2014-04-11 at 22:42 +0400, Vladimir Laskov wrote:
>>
>>
>> links
>> https://bitbucket.org/weec/docs/downloads/dmesg_verbose_boot.log
>> https://bitbucket.org/weec/docs/downloads/intel_s1200rp.dsdt
>>
>>
> Wanted to xpost this over to freebsd-acpi too. Since it looks to me
> that the IPMI driver isn't getting invoked, I assume that its because of
> a variance in ACPI parsing of the relevant IPMI section.
>
> sean
>
>
>>
>> On Fri, Apr 11, 2014 at 8:08 PM, Sean Bruno <sbr...@ignoranthack.me>

>> sean