From owner-freebsd-hackers@FreeBSD.ORG Thu Dec 1 13:20:16 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 990AC16A41F for ; Thu, 1 Dec 2005 13:20:16 +0000 (GMT) (envelope-from jf@trispen.com) Received: from brolloks.trispen.com (brolloks.trispen.com [196.22.177.34]) by mx1.FreeBSD.org (Postfix) with ESMTP id CF37443D6E for ; Thu, 1 Dec 2005 13:20:10 +0000 (GMT) (envelope-from jf@trispen.com) Received: from localhost (unknown [127.0.0.1]) by brolloks.trispen.com (Postfix) with ESMTP id 416ED283 for ; Thu, 1 Dec 2005 15:20:05 +0200 (SAST) Received: from brolloks.trispen.com ([127.0.0.1]) by localhost (brolloks.trispen.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 96953-04 for ; Thu, 1 Dec 2005 15:20:03 +0200 (SAST) Received: from jf64x2.trispen.com (tpnnat.trispen.com [196.22.177.50]) by brolloks.trispen.com (Postfix) with ESMTP id 5D0732F for ; Thu, 1 Dec 2005 15:20:03 +0200 (SAST) References: Message-ID: To: freebsd-hackers@freebsd.org From: "Jacques Fourie" Organization: Trispen Technologies Content-Type: text/plain; format=flowed; delsp=yes; charset=iso-8859-15 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Date: Thu, 01 Dec 2005 15:20:02 +0200 In-Reply-To: User-Agent: Opera M2/8.50 (Win32, build 7700) X-Virus-Scanned: amavisd-new at trispen.com Subject: 4.11 SMP issues on Intel SE7501CW2 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Dec 2005 13:20:16 -0000 Hi, With reference to the following thread : http://groups.google.com/group/mailing.freebsd.smp/browse_thread/thread/bd45afab721e1a85/f66c8476272952af?lnk=st&q=%2Bfreebsd+%2B%22failed!%22+%2Bpanic&rnum=80#f66c8476272952af I am seeing the same issue on an Intel SE7501CW2 dual Xeon machine. 6.0 as well as -current exhibits the same behaviour. Various postings to the above thread suggests that this may be due to the APIC ID that the BIOS claims is assigned to the CPU not being the actual APIC ID assigned to the CPU. Does anyone have any new information on this issue? If the subsequent panic succeeded in rebooting the machine this would not be a big issue for me but unfortunately the machine hangs after pressing 'y' to the "panic [y/n]" prompt. Is there a way in which to initiate a hard reset in software? regards, jacques