From owner-freebsd-questions@FreeBSD.ORG Tue Mar 13 22:39:29 2007 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6423B16A405 for ; Tue, 13 Mar 2007 22:39:29 +0000 (UTC) (envelope-from lists@lizardhill.com) Received: from kermit.lizardhill.com (kermit.lizardhill.com [64.69.41.217]) by mx1.freebsd.org (Postfix) with ESMTP id 4A04C13C468 for ; Tue, 13 Mar 2007 22:39:29 +0000 (UTC) (envelope-from lists@lizardhill.com) Received: from ip72-193-85-114.lv.lv.cox.net ([72.193.85.114] helo=mickey) by kermit.lizardhill.com with esmtpa (Exim 4.63) (envelope-from ) id 1HRFeS-00047L-GQ; Tue, 13 Mar 2007 15:39:28 -0700 From: "Don O'Neil" To: , "'FreeBSD Questions'" Date: Tue, 13 Mar 2007 15:39:24 -0700 Message-ID: <002301c765c0$73aa8630$0700020a@mickey> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 thread-index: AcdlwHNu+niGbYC2RkmPY7xcGwAUIw== X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028 Cc: Subject: Exim 4.66 Causing Kernel Panics? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Mar 2007 22:39:29 -0000 Anyone aware of a reason why a fresh build/install of exim 4.66 would cause kernel panics and reboots on my FreeBSD 6.1 machine? My machine, just out of the blue this morning, started rebooting every 3 minutes.... I narrowed it down to exim I think... As long as I never started up exim 4.66 the machine didn't have the problem... But as soon as I started it up, whammo... Panic and reboot. I've since rolled back to 4.63 and the problem seems to be resolved at least for the moment. The strangest thing is that I upgraded to 4.66 several days ago and the problem didn't show up until this morning. I'm not 100% sure the problem is exim but that's the only thing I could narrow it down to. Perhaps there is a new exim bug/exploit that I just didn't get hit with until today? I deleted the message queue just in case it was corrupt. ANY ideas from anyone as to what could be causing this (hardware perhaps?) would be appreciated.