From owner-freebsd-arch@FreeBSD.ORG Sun May 4 22:59:26 2014 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id F0771B5A; Sun, 4 May 2014 22:59:26 +0000 (UTC) Received: from wonkity.com (wonkity.com [67.158.26.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "wonkity.com", Issuer "wonkity.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 8234B1AE4; Sun, 4 May 2014 22:59:26 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.8/8.14.8) with ESMTP id s44MxMgI009250 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sun, 4 May 2014 16:59:22 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.8/8.14.8/Submit) with ESMTP id s44MxLbp009247; Sun, 4 May 2014 16:59:22 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Sun, 4 May 2014 16:59:21 -0600 (MDT) From: Warren Block To: Rui Paulo Subject: Re: proposal: set default lid state to S3, performance/economy Cx states to Cmax In-Reply-To: Message-ID: References: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (wonkity.com [127.0.0.1]); Sun, 04 May 2014 16:59:22 -0600 (MDT) Cc: Kevin Oberman , Adrian Chadd , "freebsd-acpi@freebsd.org" , "freebsd-arch@freebsd.org" X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 May 2014 22:59:27 -0000 On Sun, 4 May 2014, Rui Paulo wrote: > On May 4, 2014, at 1:27, Adrian Chadd wrote: > >> * Flipping the default lid state to S3. I think ACPI suspend/resume >> seems to work well enough these days and I've not met anyone lately >> who expects the default from their laptop to be "stay awake with the >> lid shut." > > The sysctl is really just a hack. We should have a much better mechanism for integrating our ACPI with the X11 desktop environments. GNOME/KDE/Mate don't understand our sysctl and get confused easily. > > You can turn it on by default, but I'm sure ACPI suspend/resume is not working well enough like you say. How many laptops have you tested? For completeness, how many desktops? Suspend works for me. It's the resume part, on Dell and Acer systems at least, that does not work at all. > There are bunch of ports kernel modules that will crash your system if you suspend. VirtualBox is one of them. > >> * Save chip bugs that we should add workarounds for, we should be OK >> to enter lower sleep states when idling. Flipping this may expose some >> further crazy driver, platform or timer bugs, but they again likely >> should be fixed. > > They are still not fixed. Some of these problems are not in FreeBSD though and I don't expect us to be able to work around them. We should try to identify systems where C3 has surprising effects and blacklist them. If there were an easy-to-run test, many would be happy to report results.