From owner-freebsd-amd64@FreeBSD.ORG Mon Mar 27 19:59:38 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D9C5416A400 for ; Mon, 27 Mar 2006 19:59:38 +0000 (UTC) (envelope-from ghelmer@palisadesys.com) Received: from magellan.palisadesys.com (magellan.palisadesys.com [192.188.162.211]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1801843D5A for ; Mon, 27 Mar 2006 19:59:35 +0000 (GMT) (envelope-from ghelmer@palisadesys.com) Received: from [172.16.1.108] (cetus.palisadesys.com [192.188.162.7]) (authenticated bits=0) by magellan.palisadesys.com (8.13.4/8.13.4) with ESMTP id k2RJxT2C015336 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 27 Mar 2006 13:59:29 -0600 (CST) (envelope-from ghelmer@palisadesys.com) Message-ID: <44284421.7040205@palisadesys.com> Date: Mon, 27 Mar 2006 13:59:29 -0600 From: Guy Helmer User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: freebsd-amd64@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Palisade-MailScanner-Information: Please contact the ISP for more information X-Palisade-MailScanner: Found to be clean X-Palisade-MailScanner-From: ghelmer@palisadesys.com Subject: FreeBSD 6.x SMP amd64 hang on dual Xeon after "shutdown -r" X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Mar 2006 19:59:38 -0000 On systems without PS/2 keyboard controllers, after issuing a "shutdown -r", the system winds down to this point: Shutting down ACPI Stray irq9 Rebooting...... cpu_reset: stopping other CPUs and it no longer responds to the keyboard - only reset or power cycling will bring it out of this state. Does the Opteron or EMT64-enabled Xeon not reboot on a triple fault like i386 CPUs do? (A triple fault is what umapping all the virtual memory causes, doesn't it?) Any ideas? Guy -- Guy Helmer, Ph.D. Principal System Architect Palisade Systems, Inc.