From owner-freebsd-hackers@FreeBSD.ORG Sat Aug 2 08:56:49 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8646A37B401 for ; Sat, 2 Aug 2003 08:56:49 -0700 (PDT) Received: from natto.numachi.com (natto.numachi.com [198.175.254.216]) by mx1.FreeBSD.org (Postfix) with SMTP id 5194543FAF for ; Sat, 2 Aug 2003 08:56:47 -0700 (PDT) (envelope-from reichert@numachi.com) Received: (qmail 8866 invoked by uid 1001); 2 Aug 2003 15:56:45 -0000 Date: Sat, 2 Aug 2003 11:56:45 -0400 From: Brian Reichert To: freebsd-hackers@freebsd.org Message-ID: <20030802155645.GE969@numachi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4i Subject: network crash dumps X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Aug 2003 15:56:49 -0000 I'm messing with a utility for performing network crash dumps: and have currently applied his instructions (with some mods) to FreeBSD 4.7-RELEASE. I have two questions: - To test the functionability, I need to invoke a panic. I've attempted to call 'panic' with a DDB-enabled kernel, but his client code doesn't seem to get triggered. Recent feedback from the author: I seem to remember calling "panic" from ddb actually does something strange. Try "call boot(1)" or "call boot" instead. Does anyone have a grasp on an alternate way of panicing a 4.7-R kernel? - If I can get this to fly, does anyone know in advance if his client code will apply to FBSD 5.x? It wouldn't take me long to find out hte hard way, but I figured I'd ask. Thanks for any advice... -- Brian 'you Bastard' Reichert 37 Crystal Ave. #303 Daytime number: (603) 434-6842 Derry NH 03038-1713 USA BSD admin/developer at large