From owner-freebsd-current@FreeBSD.ORG Fri Oct 22 09:29:49 2010 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 703C31065718 for ; Fri, 22 Oct 2010 09:29:49 +0000 (UTC) (envelope-from avg@freebsd.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id B94148FC19 for ; Fri, 22 Oct 2010 09:29:48 +0000 (UTC) Received: from porto.topspin.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id MAA10980; Fri, 22 Oct 2010 12:29:40 +0300 (EEST) (envelope-from avg@freebsd.org) Received: from localhost.topspin.kiev.ua ([127.0.0.1]) by porto.topspin.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1P9DwS-000CX4-5q; Fri, 22 Oct 2010 12:29:40 +0300 Message-ID: <4CC15983.80003@freebsd.org> Date: Fri, 22 Oct 2010 12:29:39 +0300 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: volker@vwsoft.com References: <4CBCCAB8.4090500@vwsoft.com> <4CBD24FA.8040302@icyb.net.ua> <4CC1510C.2020000@freebsd.org> <4CC154C5.3020500@vwsoft.com> In-Reply-To: <4CC154C5.3020500@vwsoft.com> X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: FreeBSD current Subject: Re: c 213323 breaks Sony Vaio P11Z w/o acpi X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Oct 2010 09:29:49 -0000 on 22/10/2010 12:09 volker@vwsoft.com said the following: > On 10/22/10 10:53, Andriy Gapon wrote: >> >> [ping] > > Sorry, Andriy! > > I haven't found the time to hack yesterday. The Intel website doesn't provide > the 20091221 tarball anymore (but a more recent one) and I need to lay my hands > on the script and the code tarball to get it working. As a result, I hope I can > provide a more recent script that should work out of the box. > > Please stay tuned (I guess I'll find the time to get it working over the > upcoming weekend). Volker, thanks a lot! Perhaps, meanwhile you can provide a verbose boot dmesg? The problem that you get is quite unexpected. Essentially, that division by zero that you get is a form of an assert and I am planning to put a real KASSERT there. Neither cpu_logical nor cpu_cores should be zero after that loop because they both should be incremented when the iterator is equal to boot CPU ID. -- Andriy Gapon