From owner-freebsd-current@FreeBSD.ORG Mon Sep 17 15:14:02 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0CB611065670 for ; Mon, 17 Sep 2012 15:14:02 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from bigwig.baldwin.cx (bigknife-pt.tunnel.tserv9.chi1.ipv6.he.net [IPv6:2001:470:1f10:75::2]) by mx1.freebsd.org (Postfix) with ESMTP id D6DBB8FC0C for ; Mon, 17 Sep 2012 15:14:01 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 3ABB9B922; Mon, 17 Sep 2012 11:14:01 -0400 (EDT) From: John Baldwin To: freebsd-current@freebsd.org Date: Mon, 17 Sep 2012 08:27:34 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p17; KDE/4.5.5; amd64; ; ) References: <20120914212716.GB7612@michelle.cdnetworks.com> <20120917104110.GX3324-v2@home.opsec.eu> <20120917104631.GY3324@home.opsec.eu> In-Reply-To: <20120917104631.GY3324@home.opsec.eu> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201209170827.34159.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Mon, 17 Sep 2012 11:14:01 -0400 (EDT) Cc: Kurt Jaeger Subject: Re: Call for bge(4) testers X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Sep 2012 15:14:02 -0000 On Monday, September 17, 2012 6:46:31 am Kurt Jaeger wrote: > Hi! > > > > box. I'm especially interested in whether there is any ASF/IPMI > > > regression on BCM570x/571x. > > > > Any ipmi-specific tests I should make ? > > This comes with kldload ipmi: > > ipmi0: port 0xca2-0xca3 on acpi0 > ipmi0: KCS mode found at io 0xca2 on acpi > ipmi0: KCS error: ff > ipmi0: IPMI device rev. 1, firmware rev. 1.10, version 2.0 > ipmi0: Number of channels 1 > ipmi0: Attached watchdog > ipmi1: on isa0 > device_attach: ipmi1 attach returned 16 > ppc0: cannot reserve I/O port range That shows you have a working BMC (just ignore the ipmi1 warning). I think to test you will want to use ipmitool from a remote machine to access the BMC over the network. (Some BMC's have web UI's as well that support remote KVM, etc. That would be a better test than just using ipmitool.) -- John Baldwin