From owner-freebsd-stable Mon Oct 1 14:51:47 2001 Delivered-To: freebsd-stable@freebsd.org Received: from pc1-cove4-0-cust214.bir.cable.ntl.com (pc1-cove4-0-cust214.bir.cable.ntl.com [213.105.93.214]) by hub.freebsd.org (Postfix) with ESMTP id AF04337B406 for ; Mon, 1 Oct 2001 14:51:42 -0700 (PDT) Received: from ntlworld.com (alpha.private [192.168.0.2]) (authenticated) by pc1-cove4-0-cust214.bir.cable.ntl.com (8.11.6/8.11.6) with ESMTP id f91LpJ465771 (using TLSv1/SSLv3 with cipher RC4-MD5 (128 bits) verified NO); Mon, 1 Oct 2001 22:51:21 +0100 (BST) (envelope-from ianjhart@ntlworld.com) Message-ID: <3BB8E557.2752CB2F@ntlworld.com> Date: Mon, 01 Oct 2001 22:51:19 +0100 From: ian j hart X-Mailer: Mozilla 4.78 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Keith Mitchell Cc: Matt Dillon , freebsd-stable@FreeBSD.ORG, kmitch@guru.org Subject: Re: fs corruption (ATA / 4.4-REL) References: <20011001195142.87F0025@weenix.guru.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Keith Mitchell wrote: > > > It's worth updating to the latest -stable kernel. At least one other > > person has reported filesystem corruption due to kstack underflows which > > went away when I bumped UPAGES from 2 to 3. I don't think the stack > > fixes for the IDE drivers have been MFCd to -stable yet so heavy IDE use > > could be hitting up against the kstack problem. > > After reading more, it doesn't look like my MB is likely the problem. I have > been doing massive builds in ports when the problem hits. The install seems > to go ok without corruption. I'm in the process of building a RELENG_4 > image to try (I'm going to build a whole CD just to make sure). It's > probably going to be a day or two before my new CD is ready for me to try. With a UDMA33 drive I only got errors under heavy load (like massive builds). But if you don't see any error messages I guess UDMA is not the problem. Did you check + measure the cables like I suggested? A re-read of your original post reveals it's a k6 450. Touch the CPU heatsink. If you burn your finger that's the problem :) Seriously tho' there were problems with one of the k6 chips, but it's so long ago I can't remember clearly whether it's the 450. What's the core voltage printed on the chip, and what's the M/B core voltage set to. There should also be a revision number. While you do that I'll see if I can find the info. If I'm correct there were two versions with different core voltages - one of which was suspect. Anyone remember this? What brand is the mobo, maybe someone else has one. > > Is there any way from an installed 4.4.0 system to tell if I'm running > into this kstack problem definatively? > > -- > Keith Mitchell > Email: kmitch@guru.org PGP key available upon request > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- ian j hart To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message