From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S964874AbWDDDzU (ORCPT ); Mon, 3 Apr 2006 23:55:20 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751470AbWDDDzT (ORCPT ); Mon, 3 Apr 2006 23:55:19 -0400 Received: from mx2.suse.de ([195.135.220.15]:14532 "EHLO mx2.suse.de") by vger.kernel.org with ESMTP id S1751467AbWDDDzS (ORCPT ); Mon, 3 Apr 2006 23:55:18 -0400 From: Andi Kleen To: linux-kernel@vger.kernel.org, discuss@x86-64.org Subject: [ANNOUNCE] firescope for i386/x86-64 released Date: Tue, 4 Apr 2006 05:55:12 +0200 User-Agent: KMail/1.9.1 Cc: benh@kernel.crashing.org MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200604040555.12989.ak@suse.de> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org [This has been on ftp for some time but I didn't get around to announce it] I ported Ben Herrenschmidt's firescope tool to i386/x86-64 and did some changes. It allows to read memory from a target over firewire. All you need is a fitting firewire cable and two machines with firewire port and ohci1394 firewire controllers. There's no xmon on x86-64, so it's primarily to read the dmesg log buffer (but it can read arbitary memory). It's very useful to get kernel logs out of machines without serial port like laptops. ftp://ftp.suse.com/pub/people/ak/firescope/firescope-0.1.tar.gz See the manpage in the package for more details. Limitations: - raw1394 needs to be loaded on the host - Host needs to run ohci1394 first. This means it currently cannot be used to capture very early oopses. - Host needs to be same bitsize as target. You can use a 32bit binary (firescope32 as generated by the Makefile), but you need 2.6.17rc1 for the compat support - The tty output inserts too many newlines. - Under high load auto update mode sometimes gets confused (it is hard to do this without any locking) -Andi