From owner-freebsd-questions@FreeBSD.ORG Sun Sep 7 14:49:43 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8E4E11065671 for ; Sun, 7 Sep 2008 14:49:43 +0000 (UTC) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: from be-well.ilk.org (dsl092-078-145.bos1.dsl.speakeasy.net [66.92.78.145]) by mx1.freebsd.org (Postfix) with ESMTP id 506EA8FC18 for ; Sun, 7 Sep 2008 14:49:43 +0000 (UTC) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: from lowell-desk.lan (lowell-desk.lan [172.30.250.6]) by be-well.ilk.org (Postfix) with ESMTP id 086AB2842F; Sun, 7 Sep 2008 10:49:39 -0400 (EDT) Received: by lowell-desk.lan (Postfix, from userid 1147) id BE8B01CCDD; Sun, 7 Sep 2008 10:49:38 -0400 (EDT) To: "j c" References: <29aa29010809060229i6371ca8by11c8b7cd83313e1@mail.gmail.com> From: Lowell Gilbert Date: Sun, 07 Sep 2008 10:49:38 -0400 In-Reply-To: <29aa29010809060229i6371ca8by11c8b7cd83313e1@mail.gmail.com> (j. c.'s message of "Sat\, 6 Sep 2008 02\:29\:22 -0700") Message-ID: <44r67wovst.fsf@lowell-desk.lan> User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.2 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: freebsd-questions@freebsd.org Subject: Re: Compiling Issue X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-questions@freebsd.org List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Sep 2008 14:49:43 -0000 "j c" writes: > I've had an ongoing problem of freezing. It happens randomly, i feel, > but sometimes it seems like it happens more under heavy load (but not > always). I've ran numerous tests: memtest, hard drive tests, cpu load > tests, basically most of the tests on Ultimate Boot CD, and they all > finish successfully. Well, i've been able to reproduce the freezing > during compilation of gnash, or one of its dependencies agg. Does > anyone have any suggestions? When you say it is reproduceable, do you mean that it always fails at the same point? If you have a truly reproduceable case, then you could break to the kernel debugger (the procedure is described in -- if I recall correctly -- the Developers' Handbook) and get information that a developer could use to analyze the situation. If it isn't reliably reproduceable in that sense, it's still likely to be hardware, even if software tests have been passing. Heat-related issues would be a good guess; perhaps you can monitor some motherboard temperature values. Good luck. -- Lowell Gilbert, embedded/networking software engineer, Boston area http://be-well.ilk.org/~lowell/