From owner-cvs-src@FreeBSD.ORG Fri Apr 28 18:22:13 2006 Return-Path: X-Original-To: cvs-src@FreeBSD.org Delivered-To: cvs-src@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0464416A404; Fri, 28 Apr 2006 18:22:13 +0000 (UTC) (envelope-from nate@root.org) Received: from ylpvm43.prodigy.net (ylpvm43-ext.prodigy.net [207.115.57.74]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9040543D46; Fri, 28 Apr 2006 18:22:12 +0000 (GMT) (envelope-from nate@root.org) Received: from pimout5-ext.prodigy.net (pimout5-int.prodigy.net [207.115.4.21]) by ylpvm43.prodigy.net (8.12.10 outbound/8.12.10) with ESMTP id k3SIMCne008293; Fri, 28 Apr 2006 14:22:12 -0400 X-ORBL: [67.119.74.222] Received: from [10.0.0.53] (adsl-67-119-74-222.dsl.sntc01.pacbell.net [67.119.74.222]) by pimout5-ext.prodigy.net (8.13.6 out.dk/8.13.6) with ESMTP id k3SIM9dE271124; Fri, 28 Apr 2006 14:22:10 -0400 Message-ID: <44525D16.3070005@root.org> Date: Fri, 28 Apr 2006 11:21:10 -0700 From: Nate Lawson User-Agent: Thunderbird 1.5.0.2 (Windows/20060308) MIME-Version: 1.0 To: Maxim Sobolev References: <200604280317.k3S3Hb3L017882@repoman.freebsd.org> <1146195791.40894.6.camel@shumai.marcuscom.com> <44524F85.5000508@FreeBSD.org> In-Reply-To: <44524F85.5000508@FreeBSD.org> Content-Type: text/plain; charset=KOI8-U; format=flowed Content-Transfer-Encoding: 7bit Cc: cvs-src@FreeBSD.org, src-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/dev/sk if_sk.c if_skreg.h X-BeenThere: cvs-src@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: CVS commit messages for the src tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Apr 2006 18:22:13 -0000 Maxim Sobolev wrote: >> BTW, thanks for your work on the reboot issue. Oh, and are you using > > Don't mention it. The other big and still unresolved issue is getting > SMP working. I have tried to debug it and as long as I can tell second > core for some reason doesn't start at all. I have even attempted to > borrow second CPU kick in magic from xnu (Darwin kernel), but the result > is the same. My current guess is that since it's mobile processor, the > 2nd core may be turned off for power saving purposes and needs some > (ACPI?) hohomagic to power it up. Unfortunately I can't find any > documentation on the processor to check. It is interesting that both > Linux and Windows don't have any problems with getting it working OOB. I don't think there's any special ACPI thing to do. If you have acpi loaded, the MADT (apic table) probe should just work. Are you sure you have the latest -current since cperciva@ fixed the Core Duo limitation we had? -- Nate