From owner-freebsd-stable@FreeBSD.ORG Wed Nov 3 19:45:41 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 13576106564A for ; Wed, 3 Nov 2010 19:45:41 +0000 (UTC) (envelope-from danallen46@airwired.net) Received: from mail.utahbroadband.com (mail.utahbroadband.com [204.14.20.91]) by mx1.freebsd.org (Postfix) with ESMTP id C9F2F8FC1A for ; Wed, 3 Nov 2010 19:45:40 +0000 (UTC) Received: (qmail 27854 invoked by uid 89); 3 Nov 2010 19:45:40 -0000 Received: from unknown (HELO ?192.168.0.18?) (danallen46@airwired.net@66.29.174.6) by mail.utahbroadband.com with ESMTPA; 3 Nov 2010 19:45:40 -0000 Mime-Version: 1.0 (Apple Message framework v1081) Content-Type: text/plain; charset=us-ascii From: Dan Allen In-Reply-To: Date: Wed, 3 Nov 2010 13:45:39 -0600 Content-Transfer-Encoding: quoted-printable Message-Id: <36E416FC-2F45-40C8-A7EC-0E7FA3B603A4@airwired.net> References: <68E248E0-8619-4859-BFFE-1B5F5ABBC51F@airwired.net> To: Sergey Kandaurov , Jeremy Chadwick X-Mailer: Apple Mail (2.1081) Cc: FreeBSD-STABLE Mailing List , Andriy Gapon Subject: Re: Fatal trap 18 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Nov 2010 19:45:41 -0000 On 3 Nov 2010, at 2:18 AM, Sergey Kandaurov wrote: > + if (cpu_logical =3D=3D 0) > + cpu_logical =3D 1; /* XXX max_logical? */ > cpu_cores /=3D cpu_logical; > hyperthreading_cpus =3D cpu_logical; My machine contains an Intel Core Duo, not a Core 2 Duo. However, both = machines have 2 logical CPUs. Perhaps the bug is not handling a Core = Duo properly. I just sync'd with csup's date command as Jeremy suggested. It is = building right now. We'll see if a 2010.10.28.06.00.00 GMT system has = the problem. I doubt it does. I think this Intel logical CPU code = business is probably the culprit. It is hard to believe that I am the only one with a Core Duo machine = finding this problem! More in a bit... Dan