From owner-freebsd-current@FreeBSD.ORG Thu Mar 4 14:03:40 2004 Return-Path: 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 81B7316A4CE for ; Thu, 4 Mar 2004 14:03:40 -0800 (PST) Received: from root.org (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id 4CFC943D1F for ; Thu, 4 Mar 2004 14:03:40 -0800 (PST) (envelope-from nate@root.org) Received: (qmail 25639 invoked by uid 1000); 4 Mar 2004 22:03:41 -0000 Date: Thu, 4 Mar 2004 14:03:41 -0800 (PST) From: Nate Lawson To: acpi-jp@jp.FreeBSD.org In-Reply-To: Message-ID: <20040304135734.D25611@root.org> References: <20040301234415.53B3E5D07@ptavv.es.net> <20040301160136.N8753@root.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=iso-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE cc: current@freebsd.org Subject: Re: [acpi-jp 3096] Re: Update on ACPI with FreeBSD CURRENT on ThinkPad T30 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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: Thu, 04 Mar 2004 22:03:40 -0000 On Wed, 3 Mar 2004, Dag-Erling [iso-8859-1] Sm=F8rgrav wrote: > Nate Lawson writes: > > Try using the sysctls from the new acpi_video module to turn off the > > backlight, perhaps by turning the brightness way down. If it works, pu= t > > it in /etc/rc.{suspend,resume}. > > /etc/rc.{suspend,resume} are useless since they (apparently) only run > when you suspend manually using acpiconf(8) or apm(8). apmd has always called the rc scripts, no matter how the suspend request was generated. It's only acpi that calls them directly from acpiconf. The reason is simple. apm requires a convoluted model that ties kernel behavior to userland. A suspend request goes out from the kernel, hits apmd, and then is blocked or approved and then goes back to the kernel before the actual suspend is initiated. With -current, a conscious decision was made that no critical services should depend on userland. This applies to acpi in the following ways. Power profile changes based on AC adapter events go out to a usermode script, which can decide to tweak power-saving settings based on the event. If it's not present, the worst that happens is that the system persists in performance/economy mode. On the other hand, hitting a critical high temp starts a shutdown process entirely from kernel mode. Since this has the potential to cause system damage, userland can't be in the critical path for this. What if the system is hitting the high temp due to a fork bomb and the fan died? -Nate