Date: Fri, 21 Feb 2003 08:05:17 -0500 From: Mike Tancsa <mike@sentex.net> To: freebsd-hackers@freebsd.org Subject: Re: debugging a repeating panic Message-ID: <pr8c5v0l13505ku44p1r9v432lukouab5i@4ax.com> In-Reply-To: <E0uhY.A.w8S.7WJV-@coal.sentex.ca> 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> <E0uhY.A.w8S.7WJV-@coal.sentex.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 20 Feb 2003 09:45:19 +0100, in sentex.lists.freebsd.hackers you wrote: >Mike Tancsa <mike@sentex.net> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?pr8c5v0l13505ku44p1r9v432lukouab5i>