Received: by oss.sgi.com id ; Tue, 10 Oct 2000 15:37:15 -0700 Received: from pneumatic-tube.sgi.com ([204.94.214.22]:32071 "EHLO pneumatic-tube.sgi.com") by oss.sgi.com with ESMTP id ; Tue, 10 Oct 2000 15:36:57 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id PAA07986 for ; Tue, 10 Oct 2000 15:43:25 -0700 (PDT) mail_from (cattelan@thebarn.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/craymail-smart-nospam1.1) with ESMTP id RAA7166952; Tue, 10 Oct 2000 17:34:50 -0500 (CDT) Received: from gibble.americas.sgi.com (gibble.americas.sgi.com [128.162.195.80]) by daisy-e185.americas.sgi.com (980427.SGI.8.8.8/SGI-server-1.6mw-e) with ESMTP id RAA84749; Tue, 10 Oct 2000 17:34:50 -0500 (CDT) Received: from thebarn.com (localhost [127.0.0.1]) by gibble.americas.sgi.com (8.10.1/8.10.1) with ESMTP id e9AMYnQ11575; Tue, 10 Oct 2000 17:34:49 -0500 Message-ID: <39E39988.3A61C4A0@thebarn.com> Date: Tue, 10 Oct 2000 17:34:48 -0500 From: Russell Cattelan X-Mailer: Mozilla 4.73 [en] (X11; U; Linux 2.4.0-whipme5 i686) X-Accept-Language: en MIME-Version: 1.0 To: Keith Owens CC: cattelan@cthulhu.engr.sgi.com, linux-xfs@oss.sgi.com Subject: Re: ADD 804398 - XFS hits BUG call in pagebuf_read_full_page References: <1674.971216931@kao2.melbourne.sgi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;linux-xfs-outgoing Keith Owens wrote: > On Tue, 10 Oct 2000 12:25:10 -0700 (PDT), > pv@fddi-odin.corp.sgi.com (cattelan@thebarn.com) wrote: > >that is what "I don't have all the kbd output... I;ll add to it as > >I capture more traces" means > > > >I didn't capture all that > >kdb crashed and I was forced to reboot. > > How did kdb crash? it wasn't that kdb it self crashed, rather I entered a bad address into the xinode command with cause a null reference which cause kdb to do a re enter. After that any info I was going after was lost. kdb it self did keep running sorry about the confusion.