From owner-freebsd-current@FreeBSD.ORG Mon May 29 20:11:52 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0A1A816A429 for ; Mon, 29 May 2006 20:11:52 +0000 (UTC) (envelope-from nate@root.org) Received: from ylpvm15.prodigy.net (ylpvm15-ext.prodigy.net [207.115.57.46]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9B71A43D48 for ; Mon, 29 May 2006 20:11:51 +0000 (GMT) (envelope-from nate@root.org) Received: from pimout7-ext.prodigy.net (pimout7-int.prodigy.net [207.115.4.147]) by ylpvm15.prodigy.net (8.12.10 outbound/8.12.10) with ESMTP id k4TKBtEs014262 for ; Mon, 29 May 2006 16:11:58 -0400 X-ORBL: [71.139.38.236] Received: from [10.0.5.50] (ppp-71-139-38-236.dsl.snfc21.pacbell.net [71.139.38.236]) by pimout7-ext.prodigy.net (8.13.6 out.dk/8.13.6) with ESMTP id k4TKBfRi154600; Mon, 29 May 2006 16:11:45 -0400 Message-ID: <447B551F.8000904@root.org> Date: Mon, 29 May 2006 13:10:07 -0700 From: Nate Lawson User-Agent: Thunderbird 1.5.0.2 (Windows/20060308) MIME-Version: 1.0 To: Yar Tikhiy References: <20060528142039.GA80613@comp.chem.msu.su> In-Reply-To: <20060528142039.GA80613@comp.chem.msu.su> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: Freeze due to performance_cx_lowest=LOW 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: Mon, 29 May 2006 20:11:52 -0000 Yar Tikhiy wrote: > Hi, > > A while ago I installed CURRENT on my new home PC and noticed that > the system would hang hard at the boot time soon after setting > cx_lowest to C3 according to the LOW setting in /etc/defaults/rc.conf. > The last message on the console was each time: Mounting NFS file > systems:. Setting performance_cx_lowest to HIGH made the problem > go away. > > Now I've just tried again to return performance_cx_lowest to its > modern default setting in a fresh CURRENT and found that the bug > is still there. Is it due to my ACPI HW being broken? I'll be > glad to show relevant debug output from my ACPI if told how to get > it. Thanks. > disable apic (hint.apic.0.disabled="1"). I isolated this a little while ago to the change to enable LAPIC timer. However, there is currently no easy way to disable the LAPIC timer with APIC enabled so you have to disable APIC. jhb@ and I have been discussing how to do this better but no easy answers apparently. -- Nate