From owner-freebsd-current Tue Aug 20 17:53:22 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA21480 for current-outgoing; Tue, 20 Aug 1996 17:53:22 -0700 (PDT) Received: from paloalto.access.hp.com (daemon@paloalto.access.hp.com [15.254.56.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id RAA21475 for ; Tue, 20 Aug 1996 17:53:20 -0700 (PDT) Received: from srmail.sr.hp.com by paloalto.access.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA232188784; Tue, 20 Aug 1996 17:53:04 -0700 Received: from hpnmhjw.sr.hp.com by srmail.sr.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA234968782; Tue, 20 Aug 1996 17:53:03 -0700 Received: from mina.sr.hp.com by hpnmhjw.sr.hp.com with SMTP (1.37.109.16/15.5+ECS 3.3) id AA227868782; Tue, 20 Aug 1996 17:53:02 -0700 Message-Id: <199608210053.AA227868782@hpnmhjw.sr.hp.com> To: current@freefall.freebsd.org Subject: Re: ktrace/kdump under 2.2-960801-snap? In-Reply-To: Your message of "Tue, 20 Aug 1996 14:33:45 PDT." Date: Tue, 20 Aug 1996 17:53:01 -0700 From: Darryl Okahata Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I wrote: > Does ktrace/kdump work under the 960801-snap? Ktrace seems to work > fine, but kdump dies with a "kdump: bogus length 0xf000ef6f" error. A little investigation shows that the ktrace.out file is being somehow *randomly* corrupted (i.e., it doesn't always occur, and, when it does, it's at different places, but usually with the same bad data). Interestingly enough, if the corruption occurs, it appears to occur on a 4K boundary. Here's an hex dump of a corrupted ktrace.out (all numbers are in hex): 0001fe0 00 00 00 00 00 00 00 00 0c 00 00 00 02 00 00 00 0001ff0 5b 1c 00 00 63 76 73 75 70 00 00 00 00 00 00 00 0002000 6f ef 00 f0 6f ef 00 f0 c3 e2 00 f0 6f ef 00 f0 0002010 6f ef 00 f0 54 ff 00 f0 4c e1 00 f0 6f ef 00 f0 0002020 a5 fe 00 f0 87 e9 00 f0 6f ef 00 f0 6f ef 00 f0 0002030 6f ef 00 f0 6f ef 00 f0 57 ef 00 f0 6f ef 00 f0 Here, the corruption occurs starting at 0x2000 (and it usually begins with "0xf000ef6f" -- anyone recognize this number?). With other ktrace runs, I've seen the corruption occur at file offsets 0x0 and 0x8000. Also, I've re-run ktrace a couple of other times, without any corruption whatsoever. -- Darryl Okahata Internet: darrylo@sr.hp.com DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Hewlett-Packard, or of the little green men that have been following him all day.