From owner-freebsd-current@FreeBSD.ORG Mon Aug 30 06:00:46 2004 Return-Path: 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 0435916A4D0; Mon, 30 Aug 2004 06:00:46 +0000 (GMT) Received: from smtp3.server.rpi.edu (smtp3.server.rpi.edu [128.113.2.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id 893B543D46; Mon, 30 Aug 2004 06:00:28 +0000 (GMT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.netel.rpi.edu [128.113.24.47]) by smtp3.server.rpi.edu (8.13.0/8.13.0) with ESMTP id i7U60QUm009317; Mon, 30 Aug 2004 02:00:27 -0400 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <20040829174521.H69068@carver.gumbysoft.com> References: <200408271337.i7RDbXgu052801@pooker.samsco.org> <20040829174521.H69068@carver.gumbysoft.com> Date: Mon, 30 Aug 2004 02:00:25 -0400 To: Doug White From: Garance A Drosihn Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Scanned-By: CanIt (www . canit . ca) cc: re@freebsd.org cc: current@freebsd.org Subject: Re: 5.3-RELEASE TODO - make/kqueue X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Aug 2004 06:00:46 -0000 At 5:45 PM -0700 8/29/04, Doug White wrote: >On Sat, 28 Aug 2004, Garance A Drosihn wrote: > >> I do still get the "*** Signal 6"s, even though I am now running > > with v1.76 of src/sys/kern/kern_lock.c. ... > >If you're sure you've updated, and have tried rebuilding make >to eliminate a corrupted binary, then you might have hardware >problems. This seems much too repeatable to be hardware. The more times I repeat my testing, the more consistent the problem seems. (but I'll spare you the details until I narrow it down even more...). I am sure I have rebuilt make several times, because I am switching between "make WITH_KQUEUE" and make without kqueue, and I do complete recompiles each time I switch. These signal-6's are not coming up in "normal operation" for me. It is only when I have been stress-testing changes to the make command. >Are you using gvinum? No. I am not that adventurous when it comes to filesystems. I use plain UFS2. I even turn off background FSCK-ing because I'm not sure I trust it yet... Please note that I did not mean to make a big deal about these signal 6's. I have to go out-of-my-way to trigger the problem, but now that I know what to do I can trigger it at will. Given that I can repeat it I do intend to keep poking away at it, but I do not consider this a serious issue. So unless a lot of other people start reporting something similar, I do not expect anyone else to spend any of their own time trying to pin it down. It's the kind of annoying little anomaly that will drive me nuts unless I pin it down, but in the greater scheme of things it is probably irrelevant. I do appreciate the suggestions because they give me more ideas of things I want to try when I have the time. But I don't expect anyone to worry about this. Certainly I am not worried about it. The main thing I wished to say was just "Great progress has been made wrt using KQUEUE for make", given how well it has stood up to my repeated hammering of it. -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu