xfs
[Top] [All Lists]

Re: xfs oops (CVS-2004-05-15_05:00_UTC)

To: Krzysztof Rusocki <kszysiu@xxxxxxxxxxxxxxxxxxxx>
Subject: Re: xfs oops (CVS-2004-05-15_05:00_UTC)
From: Nathan Scott <nathans@xxxxxxx>
Date: Mon, 21 Jun 2004 17:29:06 +1000
Cc: linux-xfs@xxxxxxxxxxx
In-reply-to: <20040621025905.GA1323@xxxxxxxxxxxxxxxxxxxx>
References: <20040529155852.GA30391@xxxxxxxxxxxxxxxxxxxx> <20040604130816.GA12556@xxxxxxxxxxxxxxxxxxxx> <20040621010330.GA1295@xxxxxxxxxxxxxxxxxxxx> <20040621021505.GA1173@frodo> <20040621025905.GA1323@xxxxxxxxxxxxxxxxxxxx>
Sender: linux-xfs-bounce@xxxxxxxxxxx
User-agent: Mutt/1.5.3i
On Mon, Jun 21, 2004 at 04:59:06AM +0200, Krzysztof Rusocki wrote:
> > 
> > Could you try the 2.6.7 code from XFS CVS for me?  (with
> > SLAB_DEBUG _enabled_).  I think this may be fixed by the
> > XFS buffer undelay fix recently, but I couldn't reproduce
> > this problem initially so I'm not 100% sure (and I would
> > really like to know :) -- thanks).
> > 
> 
> It is done but... Oops is still there - it occurs in shorter
> period of time than on 2.6.6. run-parts /etc/cron.daily
> gives here more than fifty percent chance of hitting this.
> 
> One time I also caught that before init managed to run gettys...
> 
> However - slab corruption messages did not show up (I have kdb
> enabled here, so maybe that is the reason).

Hmmm - no, I can't think what else it might be.  Since it
sounds like you can easily reproduce it, could you start
from the last working kernel version for you and do binary
chops thru the changes (bk is meant to be good at helping
with this) till you find which change caused it?  The most
likely area is xfs_buf.c|h, so I'd concentrate on changes
to those two files.

thanks!

-- 
Nathan


<Prev in Thread] Current Thread [Next in Thread>