Date: Fri, 11 Apr 2014 16:28:50 -0400 From: Lanny Baron <lbaron@servaris.com> To: freebsd-hackers@freebsd.org Subject: Re: IPMI is broken on Intel S1200RP Board Message-ID: <53485082.5050208@servaris.com> In-Reply-To: <1397243561.1434.74.camel@powernoodle.corp.yahoo.com> References: <CAEtGZqu0mScwxjSebJHCy=a68X4DN0y2%2BF02ssaymYFtXsAZVw@mail.gmail.com> <1397156847.1088.11.camel@powernoodle.corp.yahoo.com> <CAEtGZqvnhyck03yKCaP6bBh0su61_c=4M5TaTdQaMk%2B=3yLu-w@mail.gmail.com> <CAEtGZqvnA6RUitpAuHUVg4sRVpG%2BWEmaKRYVZ03t8di6L7ZKDw@mail.gmail.com> <1397232539.1434.6.camel@powernoodle.corp.yahoo.com> <CAEtGZqvXciJ9yMyQwpNzGwQdmTvXPLNzg_MR8CjZskNnDp6iFw@mail.gmail.com> <1397243561.1434.74.camel@powernoodle.corp.yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <sbruno@ignoranthack.me> >> wrote: >> On Fri, 2014-04-11 at 07:47 +0400, venom wrote: >> > 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 >> > >> >> >> >> 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 >> >> >> >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?53485082.5050208>