From owner-freebsd-current@FreeBSD.ORG Wed May 31 07:31:56 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 B94A016A420 for ; Wed, 31 May 2006 07:31:56 +0000 (UTC) (envelope-from yar@comp.chem.msu.su) Received: from comp.chem.msu.su (comp.chem.msu.su [158.250.32.97]) by mx1.FreeBSD.org (Postfix) with ESMTP id 32FB343D53 for ; Wed, 31 May 2006 07:31:54 +0000 (GMT) (envelope-from yar@comp.chem.msu.su) Received: from comp.chem.msu.su (localhost [127.0.0.1]) by comp.chem.msu.su (8.13.4/8.13.3) with ESMTP id k4V7Vj1l031171; Wed, 31 May 2006 11:31:45 +0400 (MSD) (envelope-from yar@comp.chem.msu.su) Received: (from yar@localhost) by comp.chem.msu.su (8.13.4/8.13.3/Submit) id k4V7VjER031170; Wed, 31 May 2006 11:31:45 +0400 (MSD) (envelope-from yar) Date: Wed, 31 May 2006 11:31:45 +0400 From: Yar Tikhiy To: Nate Lawson Message-ID: <20060531073145.GA30802@comp.chem.msu.su> References: <20060528142039.GA80613@comp.chem.msu.su> <447B551F.8000904@root.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <447B551F.8000904@root.org> User-Agent: Mutt/1.5.9i 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: Wed, 31 May 2006 07:31:57 -0000 On Mon, May 29, 2006 at 01:10:07PM -0700, Nate Lawson wrote: > 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. Thank you for your reply! As I reported in <20060529085723.GA98288@comp.chem.msu.su>, this way of disabling apic didn't work in my case for some reason although I had triple checked the line in device.hints. The only mention of apic in the output from sysctl -a was there irrespective of the setting in device.hints: "hw.apic.enable_extint: 0". Perhaps my system has no apic at all? Nevertheless, removing "device apic" from the kernel changed things in a way, but C3 still was unusable and the system would go to C2 after detecting too many short sleeps by cpu0, which was described in the said message, too. -- Yar