From owner-freebsd-stable@FreeBSD.ORG Thu Dec 18 06:44:15 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EBFE416A4CE for ; Thu, 18 Dec 2003 06:44:15 -0800 (PST) Received: from unix18.sihope.com (unix18.sihope.com [207.195.195.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0C16043D45 for ; Thu, 18 Dec 2003 06:44:14 -0800 (PST) (envelope-from adam@whee.org) Received: from adammxp (pc6.sihope.com [207.195.195.65]) by unix18.sihope.com (8.12.10/8.12.10) with SMTP id hBIEiCCl007264 for ; Thu, 18 Dec 2003 08:44:13 -0600 (CST) (envelope-from adam@whee.org) Message-ID: <005401c3c575$674d4ab0$41c3c3cf@office.sihope.com> From: "Adam Maloney" To: Date: Thu, 18 Dec 2003 08:44:11 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Subject: SMP forcing crash/reboot in 4.9-STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Dec 2003 14:44:16 -0000 We have a 4-way P3/500 Xeon system running FreeBSD. We had been running 4.8-STABLE for a number of months with SMP enabled and no issues. Around 25-November we moved to 4.9-STABLE. The system ran without SMP enabled until Tuesday, when we enabled SMP and APIC_IO, rebuilt the kernel, and rebooted. Then about every 30 minutes the system would reboot. We moved back to single-processor (using the source updated on 25-Nov) and it has worked since. So we synced source last night and tried enabling SMP again this morning. We are still seeing the same problem. We have switched back to a non-SMP kernel (from last night's sync) and are running fine. Has anyone else seen this? Any ideas where to look? There is nothing in messages or dmesg about the crash, and I haven't been able to catch it at the console to see if there's a message there.