From owner-freebsd-net@FreeBSD.ORG Thu May 4 14:00:12 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5E6A316A406; Thu, 4 May 2006 14:00:12 +0000 (UTC) (envelope-from robertw@ssginnovations.com) Received: from ssg1.ssginnovations.com (ssg1.ssginnovations.com [205.145.130.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id BDB8243D55; Thu, 4 May 2006 14:00:11 +0000 (GMT) (envelope-from robertw@ssginnovations.com) Received: from server1.ssgi.local (unknown [205.145.129.164]) by ssg1.ssginnovations.com (Mail Daemon) with ESMTP id E3D0D40F0; Thu, 4 May 2006 10:00:10 -0400 (EDT) X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Thu, 4 May 2006 10:00:08 -0400 Message-ID: <85D4F2C294E8434CA0AF7757415326860950E7@server1.ssgi.local> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: IPMI and bge (again) Thread-Index: AcZvLnJmoV0itcyLQ8i40QitFqtL4wADuOgAABEquzA= From: "Robert Wojciechowski" To: "Doug Ambrisko" Cc: freebsd-net@freebsd.org, oleg@freebsd.org Subject: RE: IPMI and bge (again) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 May 2006 14:00:12 -0000 > > Could you try: > > http://www.ambrisko.com/doug/bge_ipmi_2.patch > > > > Try this version. If this has trouble we can try to add some debug > > stuff to it. > > >=20 > Doug, >=20 > Thanks for the response. I applied the patch from home and rebooted one > of our servers at work and it isn't coming back up. I only saw a few > pings go through on the IPMI IP address for a bit, then nothing at all. > It froze up hard. >=20 > If you want to throw debugging code in there I can do anything you need > to trace this down! >=20 Just to follow up, I got in this morning and it was indeed locked up right after setting the hostname... the same place it locked up before. -- Robert