From owner-freebsd-hackers Fri Feb 21 5: 3:15 2003 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 31C0037B401 for ; Fri, 21 Feb 2003 05:03:14 -0800 (PST) Received: from smtp1.sentex.ca (smtp1.sentex.ca [199.212.134.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3DECF43FBD for ; Fri, 21 Feb 2003 05:03:13 -0800 (PST) (envelope-from mike@sentex.net) Received: from house (cage.simianscience.com [64.7.134.1]) by smtp1.sentex.ca (8.12.6/8.12.6) with SMTP id h1LD3Dnm095536 for ; Fri, 21 Feb 2003 08:03:14 -0500 (EST) (envelope-from mike@sentex.net) From: Mike Tancsa To: freebsd-hackers@freebsd.org Subject: Re: debugging a repeating panic Date: Fri, 21 Feb 2003 08:05:17 -0500 Message-ID: References: <5.2.0.9.0.20030219101029.041d18d8@marble.sentex.ca> <5.2.0.9.0.20030217135903.064d7378@marble.sentex.ca> <5.2.0.9.0.20030217091242.05b184b0@marble.sentex.ca> <5.2.0.9.0.20030217091242.05b184b0@marble.sentex.ca> <5.2.0.9.0.20030217135903.064d7378@marble.sentex.ca> <5.2.0.9.0.20030219101029.041d18d8@marble.sentex.ca> <5.2.0.9.0.20030219143729.05f5e308@marble.sentex.ca> In-Reply-To: X-Mailer: Forte Agent 1.8/32.548 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, 20 Feb 2003 09:45:19 +0100, in sentex.lists.freebsd.hackers you wrote: >Mike Tancsa writes: >> It only happens when periodic runs, but it on occasion skips a day. >> Eg. yesterday it did not do it. It only started happening post >> Jan28th. I can brutalize the server with repeated buildworlds (-j2 >> through 8) and it is always successful. Its only on periodic that it >> dies and find is always the process running. Its only with SMP as well >> on this 'oldish' machine > >Hmm, it would be great to know what process was running when it >crashed. Unfortunately, I don't know how to do that post-KSE... Is there anything I can add to the kernel to provide more info to track this down ? If its not a solveable issue, I will have to wipe the machine try 5.x or spend money on different hardware :-( All the box does is run spamassassin on mail that passes through it. ---Mike Mike Tancsa (mike@sentex.net)=09 http://www.sentex.net/mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message