From owner-freebsd-hackers@FreeBSD.ORG Fri Apr 11 03:47:16 2014 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5561C7F7; Fri, 11 Apr 2014 03:47:16 +0000 (UTC) Received: from mail-qg0-x234.google.com (mail-qg0-x234.google.com [IPv6:2607:f8b0:400d:c04::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 035CB1ACD; Fri, 11 Apr 2014 03:47:15 +0000 (UTC) Received: by mail-qg0-f52.google.com with SMTP id q107so4811123qgd.25 for ; Thu, 10 Apr 2014 20:47:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=5K7GhHDbmeHYlS6LkqTty80KLE1GXBJhMqNNx8JZBr0=; b=ZAloUb+yDoXN5nUeR65lnBXvI9XV/u8683V3oTPEr7KcqsRosPMFaeF6dQZ8oNLkVk 4tCVD7nWDyYB7lRoW7gW8A/8VewgUoAoT9zLfYuirvhvn5PNjijnK3eyTIDCHPEa0h29 B3aamrh/+rKxUMEIi7oyxHqTcWIMQ1kcpp1ICdwaLm2vVUmmYdtsqxcGHYK2lyR9W7wT qNlJhtI9YUSPLeINEXDZXvXcvceugoE9i4HJszPruRJL3QGgFPEi4Yfa7QXFnUpk7nPt /FSJ4YnOEoHTVc8GNK2Vvdnbc2txPRJhrjnq6aV2Lf6OE1jDMq4XFrnCWlg7yGpASGTT joXA== MIME-Version: 1.0 X-Received: by 10.140.30.225 with SMTP id d88mr23940957qgd.62.1397188035149; Thu, 10 Apr 2014 20:47:15 -0700 (PDT) Received: by 10.140.92.56 with HTTP; Thu, 10 Apr 2014 20:47:15 -0700 (PDT) In-Reply-To: References: <1397156847.1088.11.camel@powernoodle.corp.yahoo.com> Date: Fri, 11 Apr 2014 07:47:15 +0400 Message-ID: Subject: Re: IPMI is broken on Intel S1200RP Board From: venom To: sbruno@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: freebsd-hackers@freebsd.org X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Apr 2014 03:47:16 -0000 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 On Fri, Apr 11, 2014 at 7:43 AM, venom wrote: > dmesg output is attached > procedure "kldload ipmi" is at end of file > > > On Thu, Apr 10, 2014 at 11:07 PM, Sean Bruno wrote: > >> On Wed, 2014-04-09 at 12:56 +0400, venom wrote: >> > 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 root@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 ? >> > >> > -- >> >> >> 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 >> > >