From owner-freebsd-current@FreeBSD.ORG Sun May 28 21:26:31 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 03A6116B14A for ; Sun, 28 May 2006 21:14:17 +0000 (UTC) (envelope-from boris@brooknet.com.au) Received: from jay.exetel.com.au (jay.exetel.com.au [220.233.0.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2BE5E43D53 for ; Sun, 28 May 2006 21:14:14 +0000 (GMT) (envelope-from boris@brooknet.com.au) Received: (qmail 18378 invoked by uid 507); 29 May 2006 07:14:12 +1000 Received: from 180.205.233.220.exetel.com.au (HELO ?192.168.0.7?) (220.233.205.180) by jay.exetel.com.au with SMTP; 29 May 2006 07:14:12 +1000 In-Reply-To: <20060528142039.GA80613@comp.chem.msu.su> References: <20060528142039.GA80613@comp.chem.msu.su> Mime-Version: 1.0 (Apple Message framework v750) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <28788BCA-187D-4BD6-B82A-6C4F5B1E0D5C@brooknet.com.au> Content-Transfer-Encoding: 7bit From: Sam Lawrance Date: Mon, 29 May 2006 07:14:11 +1000 To: Yar Tikhiy X-Mailer: Apple Mail (2.750) Cc: njl@freebsd.org, 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: Sun, 28 May 2006 21:26:34 -0000 On 29/05/2006, at 12:20 AM, 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. I noticed the same behaviour, but I haven't looked into it yet.