From owner-freebsd-smp@FreeBSD.ORG Mon Dec 15 12:43:43 2003 Return-Path: Delivered-To: freebsd-smp@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1E2B616A4CE for ; Mon, 15 Dec 2003 12:43:43 -0800 (PST) Received: from mail6.speakeasy.net (mail6.speakeasy.net [216.254.0.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id 086C743D55 for ; Mon, 15 Dec 2003 12:43:34 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: (qmail 20328 invoked from network); 15 Dec 2003 20:43:33 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 15 Dec 2003 20:43:33 -0000 Received: from laptop.baldwin.cx (gw1.twc.weather.com [216.133.140.1]) by server.baldwin.cx (8.12.10/8.12.10) with ESMTP id hBFKhUM0008042; Mon, 15 Dec 2003 15:43:30 -0500 (EST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.5.4 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Mon, 15 Dec 2003 15:43:32 -0500 (EST) From: John Baldwin To: Mikulas Patocka X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) cc: freebsd-hackers@freebsd.org cc: freebsd-smp@freebsd.org Subject: RE: Hyperthreading crashes X-BeenThere: freebsd-smp@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: FreeBSD SMP implementation group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Dec 2003 20:43:43 -0000 On 13-Dec-2003 Mikulas Patocka wrote: > Hi > > I use FreeBSD-4.9-RC1 on a machine with hyperthreading (it seems that > hyperthreading support was ripped out of final 4.9 release --- why?) It wasn't ripped out. It is now enabled by default. Check /usr/src/UPDATING and the release notes. > I get random SIGBUSes when compiling (once I got SIGSEGV too). When I > compile only with make -j 1, I get no errors. Is it known problem with > FreeBSD? Or does it mean that the machine is bad? > > How can I find what's the reason for particular SIGBUS signal --- what did > the program wrong? In reply to your later post: I'm not sure why you are getting alignment traps, except perhaps that the PSL_AC flag is somehow flipped on on the second processor. Make sure you enable HT in your BIOS if you haven't already. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/