From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S268873AbUHUHMW (ORCPT ); Sat, 21 Aug 2004 03:12:22 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S268874AbUHUHMW (ORCPT ); Sat, 21 Aug 2004 03:12:22 -0400 Received: from willy.net1.nerim.net ([62.212.114.60]:15624 "EHLO willy.net1.nerim.net") by vger.kernel.org with ESMTP id S268873AbUHUHMV (ORCPT ); Sat, 21 Aug 2004 03:12:21 -0400 Date: Sat, 21 Aug 2004 08:54:13 +0200 From: Willy Tarreau To: Chris Johns Cc: linux-kernel@vger.kernel.org, kaos@oss.sgi.com Subject: Re: Dumping kernel log (dmesg) and backtraces after a panic Message-ID: <20040821065413.GF1456@alpha.home.local> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Aug 20, 2004 at 09:21:05PM -0500, Chris Johns wrote: > To put it simply, is there either an alternative to KDB that works with > RH EL3 and provides what I need (bt and dmesg, or just dmesg), or is > there a version of KDB that would work with EL3 already? I don't know if there's a specific KDB version, but you might give a try to kmsgdump, it's not so intrusive and might apply on RHEL kernel. It will allow you to dump the dmesg log buffer onto a floppy disk or a parallel printer upon panic or on demand. Cheers, Willy