From owner-freebsd-stable@FreeBSD.ORG Fri Apr 2 05:22:27 2004 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 A457216A4CE for ; Fri, 2 Apr 2004 05:22:27 -0800 (PST) Received: from maze.meitech.com (maze.meitech.com [69.33.133.24]) by mx1.FreeBSD.org (Postfix) with ESMTP id 36DE943D31 for ; Fri, 2 Apr 2004 05:22:27 -0800 (PST) (envelope-from tjg@meitech.com) Received: from ripley.meitech.com (ripley.meitech.com [192.168.100.12]) by maze.meitech.com (8.12.11/8.12.10) with ESMTP id i32DMU07019659 for ; Fri, 2 Apr 2004 13:22:31 GMT (envelope-from tjg@meitech.com) Received: by RIPLEY with Internet Mail Service (5.5.2653.19) id ; Fri, 2 Apr 2004 08:25:30 -0500 Message-ID: <86ECB35C998DCC49AD435A099AFACCD1A7AA44@RIPLEY> From: "Gustafson, Tim" To: "'freebsd-stable@freebsd.org'" Date: Fri, 2 Apr 2004 08:25:21 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on maze.meitech.com Subject: FreeBSD 4.9 / Supermicro 7043P-8R / Crashes After 2-5 Minutes Of Uptime 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: Fri, 02 Apr 2004 13:22:27 -0000 Hello I have a brand spanking new Supermicro 7043P-8R server with dual Intel 3.2gHZ Xeon processors and 4GB of Kingston memory. I installed FreeBSD 4.9 on the box and it gives me the following message on the screen about 2-5 minutes after it finished booting: boot() called on CPU#0 I get this message no matter whether I leave the console alone or if I log in and try to work on the machine. I read a thread about a problem very similar to this from November of 2003, but the thread seems to have just died without any resolution. Is this a known issue with Supermicro Motherboards? Does anyone have any suggestions as to a potential patch or other fix? I'm going to start doing the hardware swapping thing in a bit and see if that fixes anything, but I'd really like to hear back from anyone who has any experience with this issue. Thanks a million! Tim Tim Gustafson MEI Technology Consulting, Inc tjg@meitech.com (516) 379-0001 Office (516) 480-1870 Mobile/Emergencies http://www.meitech.com/