From owner-freebsd-current Thu Sep 12 2:43:23 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1F75037B400 for ; Thu, 12 Sep 2002 02:43:20 -0700 (PDT) Received: from gw.catspoiler.org (217-ip-163.nccn.net [209.79.217.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 996F043E3B for ; Thu, 12 Sep 2002 02:43:19 -0700 (PDT) (envelope-from dl-freebsd@catspoiler.org) Received: from mousie.catspoiler.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.12.5/8.12.5) with ESMTP id g8C9hAwr099894; Thu, 12 Sep 2002 02:43:15 -0700 (PDT) (envelope-from dl-freebsd@catspoiler.org) Message-Id: <200209120943.g8C9hAwr099894@gw.catspoiler.org> Date: Thu, 12 Sep 2002 02:43:10 -0700 (PDT) From: Don Lewis Subject: Re: Softupdate panic: softdep_update_inodeblock: update failed To: mb@imp.ch Cc: culverk@yumyumyum.org, current@FreeBSD.ORG In-Reply-To: <20020912020553.A50626-100000@levais.imp.ch> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 12 Sep, Martin Blapp wrote: > > Hi, > >> If I were you I'd start swapping memory modules, because I'm not having > > Already did that. I even used ECC ram. > >> any trouble with -CURRENT and I havn't seen anyone else having trouble. > > Did you try to build a huge project ? If I don't compile anything big > and load the machine it works perfectly. > >> Did you compile your kernel with any wierd optimizations? > > No. > > And this system works perfectly before after I turned on PG_G. > > The instability began after gcc3.2 import. I've haven't had any trouble building and running openoffice since the 3.2 import. I had to add the following kernel options: options DISABLE_PSE options DISABLE_PG_G because I was seeing memory corruption after the system had been in use for a while. If I ran a number of "make buildworld" runs one after another, I'd start seeing compile errors after about five or six buildworld runs. I never saw any kernel panics either with or without these options, ether doing system rebuilds or building openoffice. I last cvsup'ed and rebuilt the system about three days ago. Since then, the only problems I've had are a few warnings about lock order reversals and kernel malloc calls with locks held, and some problems that the DEBUG_VFS_LOCKS option found in the nfs client code. Just a thought ... What type of disks are you using? I'm running SCSI here. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message