From owner-freebsd-current@FreeBSD.ORG Fri Oct 21 21:31:03 2011 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 2637C106566C; Fri, 21 Oct 2011 21:31:03 +0000 (UTC) (envelope-from lacombar@gmail.com) Received: from mail-wy0-f182.google.com (mail-wy0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id 8697A8FC0A; Fri, 21 Oct 2011 21:31:02 +0000 (UTC) Received: by wyi40 with SMTP id 40so5745331wyi.13 for ; Fri, 21 Oct 2011 14:31:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=3oj9YvQTz/LbHm3BUYuDM0hGzgc/8dvuW4eM5GvLWNA=; b=C4b5x2DIwdJS7U8JDZjqbJSuqDAOEJLj5iNJ+EbmFqFqjuP+6v+k9AAlyxAx2ygoTm jqND3soorZj2y01ShPQrCyt1cZP+pIEYKqwfjmieIaHkw3XCH5NTL7mhYVUuUb32NsU9 3V9PmQ2wXAexNArbxFtT5TOV2OD+I66cQHJdE= MIME-Version: 1.0 Received: by 10.227.59.12 with SMTP id j12mr6143537wbh.86.1319232661457; Fri, 21 Oct 2011 14:31:01 -0700 (PDT) Received: by 10.180.105.162 with HTTP; Fri, 21 Oct 2011 14:31:01 -0700 (PDT) In-Reply-To: <201110211619.45623.jhb@freebsd.org> References: <201110211619.45623.jhb@freebsd.org> Date: Fri, 21 Oct 2011 17:31:01 -0400 Message-ID: From: Arnaud Lacombe To: John Baldwin Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-current@freebsd.org Subject: Re: ipmi(4)/isa woes 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: Fri, 21 Oct 2011 21:31:03 -0000 Hi, On Fri, Oct 21, 2011 at 4:19 PM, John Baldwin wrote: > On Tuesday, October 11, 2011 6:53:11 pm Arnaud Lacombe wrote: >> Hi, >> >> On Tue, Oct 11, 2011 at 6:34 PM, Arnaud Lacombe wro= te: >> > Hi folks, >> > >> > I've got a machine where ipmi(4) seem to be unable to fully attach. >> > 10-current kernel complains the following way: >> > >> > ipmi0: at iomem 0-0x1 on isa0 >> > ipmi0: KCS mode found at mem 0x0 alignment 0x1 on isa >> > ipmi0: couldn't configure I/O resource >> > device_attach: ipmi0 attach returned 6 > > Resource 0 is not right and will not work. =A0In this case your BIOS has = a buggy > SMBIOS / DMI table entry for IPMI. > >> Actually, I can bypass this issue by enabling acpi(4): >> >> ipmi0: port 0xca2,0xca3 on acpi0 >> ipmi0: KCS mode found at io 0xca2 on acpi >> ipmi1: on isa0 >> device_attach: ipmi1 attach returned 16 >> pmtimer0 on isa0 >> ipmi1: on isa0 >> device_attach: ipmi1 attach returned 16 > > You can ignore the ipmi1 messages. > >> However, the driver fails right after with: >> >> ipmi0: Timed out waiting for GET_DEVICE_ID > > Are you sure you have working IPMI? =A0The timeouts and the busted DMI ta= ble > is consistent with a machine where IPMI is available via an optional > daughterboard, but the daughterboard isn't installed. > Well, I'm not sure exactly what's the hardware layout looks like[0], but when ipmi0 is "attached" on isa0, I can access the IPMI controller, get the various information, set/reset the watchdog. ipmitool(1) works like a charm. However, at some point, the KCS is unable to reach the IPMI controller. Typical error is: ipmi0: KCS: Reply address mismatch ipmi0: KCS error: 01 ipmi0: KCS: Reply address mismatch ipmi0: KCS error: 01 ipmi0: Failed to set watchdog over an undetermined period of time. Sometimes it stops before the watchdog triggers, sometimes it [falsely] triggers the watchdog. - Arnaud [0]: I'll have a look to the physical machine and let you know.