From owner-freebsd-current@FreeBSD.ORG Fri Mar 24 07:18:16 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D34B416A400 for ; Fri, 24 Mar 2006 07:18:16 +0000 (UTC) (envelope-from Joerg.Pulz@frm2.tum.de) Received: from mailhost.frm2.tum.de (mailhost.frm2.tum.de [129.187.179.12]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2EDCB43D45 for ; Fri, 24 Mar 2006 07:18:13 +0000 (GMT) (envelope-from Joerg.Pulz@frm2.tum.de) Received: from localhost (mailhost.frm2.tum.de [129.187.179.12]) by mailhost.frm2.tum.de (8.13.4/8.13.4) with ESMTP id k2O7I3DW023281 for ; Fri, 24 Mar 2006 08:18:03 +0100 (CET) (envelope-from jpulz@frm2.tum.de) Received: from hades.admin.frm2 (hades.admin.frm2 [172.25.1.10]) by mailhost.frm2.tum.de (8.13.4/8.13.4) with ESMTP id k2O7Hxld023277 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Fri, 24 Mar 2006 08:17:59 +0100 (CET) (envelope-from jpulz@frm2.tum.de) Received: from hades.admin.frm2 (localhost [127.0.0.1]) by hades.admin.frm2 (8.13.4/8.13.4) with ESMTP id k2O7Hx4p033408 for ; Fri, 24 Mar 2006 08:17:59 +0100 (CET) (envelope-from jpulz@frm2.tum.de) Received: (from jpulz@localhost) by hades.admin.frm2 (8.13.4/8.13.4/Submit) id k2O7HxTd033407; Fri, 24 Mar 2006 08:17:59 +0100 (CET) (envelope-from jpulz) Date: Fri, 24 Mar 2006 08:17:57 +0100 (CET) From: Joerg Pulz To: freebsd-current@freebsd.org Message-ID: <20060324075852.I54268@hades.admin.frm2> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: at mailhost.frm2.tum.de Subject: MFC of ichwd(4) and ipmi 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, 24 Mar 2006 07:18:16 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, are there any plans to MFC the latest ichwd(4) to RELENG_6? I use it on several RELENG_6 systems since it was commit'ed the CURRENT without problems, and i like it really much. The same question belongs to the new ipmi(currently no manpage) stuff. It's really hot and works for me on several systems without problems. It would be really nice to see this in RELENG_6. There is another question which came to my mind when i started using ichwd and ipmi. I see currently no way to tell watchdogd(8) to talk to the ichwd watchdog or the ipmi watchdog. There is only one /dev/fido. I have some systems where ichwd attaches a watchdog first and later ipmi attaches a second watchdog. But when i start watchdogd(8) it talks to the ichwd watchdog every time (debug.bootverbose is set to "1" to get this information). Who makes the decision to use ichwd and not ipmi. Is this because ipmi forces the device to be /dev/ipmi, but the code looks like the watchdog is attached using the normal watchdog attach routines and therefore this part of ipmi should end as /dev/fido. Thats a little bit confusing. Here are some dmesg lines in the order they are shown when booting the system. ichwd0: on isa0 ... ipmi0: at iomem 0xf77a0-0xf77be,0x3feee000-0x3feee61a on isa0 ipmi0: SMBIOS Version: 2.34 ipmi0: KCS mode found at io 0xca2 alignment 0x1 on isa ipmi0: IPMI device rev. 3, firmware rev. 4.81, version 1.5 ipmi0: Number of channels 1 ipmi0: Attached watchdog Any clarification would be appreciated. regards Joerg - -- The beginning is the most important part of the work. -Plato -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.1 (FreeBSD) iD8DBQFEI50nSPOsGF+KA+MRApUbAKCZjuh78zwRBtuYoxMB5Qh6ytFbwwCfUsOd 2AMJZiDr/fgea+dnuFse57I= =EQjA -----END PGP SIGNATURE-----