Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Fri, 21 Mar 2003 04:03:55 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Fri, 21 Mar 2003 04:03:55 -0500 Received: from angband.namesys.com ([212.16.7.85]:59786 "HELO angband.namesys.com") by vger.kernel.org with SMTP id ; Fri, 21 Mar 2003 04:03:53 -0500 Date: Fri, 21 Mar 2003 12:14:55 +0300 From: Oleg Drokin To: Dave Jones , Linux Kernel Subject: Re: reiserfs oops [2.5.65] Message-ID: <20030321121454.A17440@namesys.com> References: <20030319141048.GA19361@suse.de> <20030320112559.A12732@namesys.com> <20030320132409.GA19042@suse.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030320132409.GA19042@suse.de> User-Agent: Mutt/1.3.22.1i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1167 Lines: 32 Hello! On Thu, Mar 20, 2003 at 01:24:09PM +0000, Dave Jones wrote: > > Hm, very interesting. Thank you. > > I've seen this once too, but on kernel patched with lots of unrelated and > > possibly memory corrupting stuff. > > I will look at it more closely. > > BTW, it oopsed not in find. Is your box SMP? > Same box committed seppuku overnight, this time in a different way. Hm, am I missing something? So it died in the morning yesterday, but before that it died again? Or were those two different nights? ;) > There's lots of "slab error in cache_alloc_debugcheck_after()" > warnings. cache reiser_inode_cache memory after object was overwritten This second oops and first BUG you quoted indicate that internal slab structures (I think second oops happened in the middle of list_del) were corrupted, not the guarded data itself. At least I think so. Can I take a look at your .config? Thank you. Bye, Oleg - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/