From: Keith Owens <kaos@sgi.com>
To: Sidik Isani <lksi@cfht.hawaii.edu>
Cc: linux-xfs@sgi.com
Subject: Re: kernel OOPS in xlog_do_log_recovery (2.4.19) 
In-reply-to: Your message of "Wed, 18 Sep 2002 16:23:59 -1000."
             <20020918162359.A30809@cfht.hawaii.edu> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 19 Sep 2002 12:42:07 +1000
Message-ID: <3697.1032403327@kao2.melbourne.sgi.com>
Sender: linux-xfs-bounce@oss.sgi.com
Errors-to: linux-xfs-bounce@oss.sgi.com
Precedence: bulk

On Wed, 18 Sep 2002 16:23:59 -1000, 
Sidik Isani <lksi@cfht.hawaii.edu> wrote:
>  As a follow-up to my previous posting: I just tried the current
>  linux-2.4-xfs from CVS, and the same thing happens (mount crashes
>  and I drop into kdb.)  Something is strange about the formatting
>  of the backtrace in kdb ... some lines are definitely scrolling
>  off the top of my console before the "more>" prompt appears.  This
>  time the function at the top of my screen is "scrup", but I think
>  there are stack levels above which rolled off the screen (is there
>  a screen height setting in kdb?)

set LINES 15

The default LINES is 24 which matches the screen, but only if all lines
are <= 80 characters.  kdb does not track long lines so it does not
detect wraparound.  You are much better off using kdb over a serial
console and capturing the output on a second machine - no problems with
lost lines then.