From owner-freebsd-stable@FreeBSD.ORG Fri Nov 5 15:22:55 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 3D6461065672 for ; Fri, 5 Nov 2010 15:22:55 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 855C38FC19 for ; Fri, 5 Nov 2010 15:22:54 +0000 (UTC) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id RAA15756; Fri, 05 Nov 2010 17:22:15 +0200 (EET) (envelope-from avg@icyb.net.ua) Message-ID: <4CD42127.5070902@icyb.net.ua> Date: Fri, 05 Nov 2010 17:22:15 +0200 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.11) Gecko/20101021 Lightning/1.0b2 Thunderbird/3.1.5 MIME-Version: 1.0 To: Dan Allen References: <68E248E0-8619-4859-BFFE-1B5F5ABBC51F@airwired.net> <4CD11FE9.8050105@freebsd.org> <5224E1F5-4567-45A8-A12C-868F7B45BC21@airwired.net> In-Reply-To: <5224E1F5-4567-45A8-A12C-868F7B45BC21@airwired.net> X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Sergey Kandaurov , FreeBSD-STABLE Mailing List 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: Fri, 05 Nov 2010 15:22:55 -0000 on 05/11/2010 16:53 Dan Allen said the following: > > On 3 Nov 2010, at 2:40 AM, Andriy Gapon wrote: > >> This problem seems to happen only on SMP systems that for some reason run as UP. >> E.g. because ACPI and/or APIC are disabled. >> Or some other BIOS configuration. >> But I am not sure what exactly is the case here. > > Okay, I have been researching my UP/SMP problem. > > In the past, before recent "Intel topology" changes, on my Toshiba Satellite U205 machine if I used a kernel with ACPI support, only 1 logical CPU showed up in FreeBSD 8.1-STABLE. When I booted into Windows XP on the same machine, with the same BIOS settings, I would see 2 logical CPUs. If I built a FreeBSD kernel WITHOUT ACPI support and left the BIOS settings as they were above, I then would see 2 logical CPUs. > > Now with these recent FreeBSD changes I cannot get the machine to EVER recognize a 2nd logical processor, but if I boot into Windows XP I still see two CPUs, so we still have a bug in this new Intel topology code. Technically speaking this has nothing to do with topology code. Topology code decides how detected (logical) CPUs are layed out, whether there are multiple sockets, or cores, or both, or etc. Different code is responsible for discovering those multiple processors in the first place. And that code can not work without proper assistance from BIOS. > This laptop has an Intel Core Duo T2400 @ 1.83 GHz chip. (The BIOS is set to provide multiple logical CPUs in all cases and Andriy, I am using your patched kernel.) > > Is there anything else I can do to help you understand this system config? > > What next? Let's look at the following: 0. your kernel config 1. verbose dmesg 2. acpidump -dt output 3. x86info -a (sysutils/x86info) -- Andriy Gapon