From owner-freebsd-questions@FreeBSD.ORG Thu Nov 12 18:28:12 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F0287106566B for ; Thu, 12 Nov 2009 18:28:11 +0000 (UTC) (envelope-from anti_spam256@yahoo.ca) Received: from web65508.mail.ac4.yahoo.com (web65508.mail.ac4.yahoo.com [76.13.9.52]) by mx1.freebsd.org (Postfix) with SMTP id 8A3BE8FC19 for ; Thu, 12 Nov 2009 18:28:11 +0000 (UTC) Received: (qmail 51721 invoked by uid 60001); 12 Nov 2009 18:28:10 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.ca; s=s1024; t=1258050490; bh=a/wrYd+6eaa+SUn++DXTwggJ/F3f96uneG0/tNYM+D4=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type; b=VAg1stZWJOonE03oejD2FOxR19N9XIwd0INegyUEk+y4lL27ZjuwLGPKx75ODIOcjiqWOG0LXoNhvS7Gc2lX0BCL0WaqKASvrt377mJD0Xvyx1jtnZV5jYYNWUKSZczJAv8d5cotyNmDkcEkqfNjnzUX1VsAYxZR8yBBF9bPpp4= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.ca; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type; b=JEN4tL7WpkH5qx5tV8rkZdgUTXKET8NgnR2lZJ+sOcTo/l3W8bNLmvtkyDeooDIyVItywVv9DL51UVPeh7fBc5RpGL+AToeFqYAbqXwkdV+BZHr5tj/WdU8OvDpwYw55nDWLgypOywQBFwLXJdTGNqxY4i+ESZYv2G75Sxr544I=; Message-ID: <784120.47330.qm@web65508.mail.ac4.yahoo.com> X-YMail-OSG: Yu_gfQ4VM1mtD0X.d_VAYEn.hdCnpMO6V2dSJg5k8udwz9uSDTdvWUcaFOsrevVuQspEl1DGKLxNO6SVw.FN9aO01XBYC0yLSIaeXUIM4Dy1jNf5DH1Oc6fj35ClW_q0eBFqho7_zT2t_NbhsNNvqJrmoNqeOh1B9nBfACkTwL3GLDLg_DiTOJvA1YS60It85GVTJyaJQtir8ITbZbUlPcOWdtVnvTnjVdNkoKpgggOxy61jBDYojgJUfWRHqqzvKuasI86c6QjiolGp3VGgFedr8iMRbfBCOYdm7LjtVg_Sgo0lk37k8HOrKPQa_Q8pAhpOn5V6biqHDzf9kW2EcnP9GYji_ZBtHCWKe6jactuELl8xHJVgSecnagbCdYn2Ww0kcSKr5xgw9tqAC2RyLSnDZxrLeVHk9A79SqDvJiGitHf1VHMpEhIQkWRpKUu6ewWi1b562.KSPEaffGG_piFCjUTZ5pLF3jt32tUk42GzW5v0BpUgTaSrbPzzW3jgOqryp0FdlcLVSUx2yKSs.zAfwmAQL9RgyCF8MfdJEcw6NfBWBxTeZ.cnrTczvGm7GiDtrWSEXw-- Received: from [208.99.137.71] by web65508.mail.ac4.yahoo.com via HTTP; Thu, 12 Nov 2009 10:28:10 PST X-Mailer: YahooMailClassic/8.1.6 YahooMailWebService/0.7.361.4 Date: Thu, 12 Nov 2009 10:28:10 -0800 (PST) From: James Phillips To: freebsd-questions@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: APM X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Nov 2009 18:28:12 -0000 Hello, On Tuesday, I was all happy that I got APM working on my pre-2000 Compaq Deskpro following these instructions: http://forums.freebsd.org/showthread.php?t=4619 On Wednesday, after configuring the router to wake the server whenever DHCP leases are touched (quick&dirty hack), I was disappointed to learn that "suspend" mode saves only ~1watt over the "inherent" use of the HLT instruction by the kernel. I was expecting a savings of ~6 watts due to the disk spinning down. Approx power consumption (+- 1W): 51 Watts (busy; disk + CPU IIRC; not retested with DVD activity) 35 Watts idle 34 Watts suspend 3 Watts off (Measured using Kill-A-Watt model P4400) Part of the problem may be that I am not using the "on board" IDE controllers: I am using a Promise (Ultra100TX2) PDC20268 I realize the memory can't be shutdown without Hibernation support, but the disks can be spun down manually (using atacontrol): http://forums.freebsd.org/showthread.php?t=1012 However, when I try to do that, I find that the disk wakes within 2 seconds of spinning down. I noticed that the spindowns are logged. Could the log being written be causing the drive to spin up again? apm(4) says that apm gets around that problem by logging the suspend event AFTER waking up. I suppose it would be tricky to concurrently log to spin down of several disks that way. For example: Say disk with /var/log spins down at 00:00:05, but the rarely-used /srv drive spins down at 00:00:07. Should the logging drive defer recording BOTH spin-down messages, or spin-up, then spin-down again at about 00:15:20? Not that important for a 1W savings, but apm says my BIOS supports the following capabilities: global standby state // Supported sleep modes global suspend state resume timer from standby // Resume timer allows sleep to last resume timer from suspend // specific period of time? RI resume from standby // Wake on interrupts, i assume RI resume from suspend Would it be possible to coordinate the cron dameon with the suspend timer? Ie: wake 15 sec- 5min before next cron job? Not worth it without hibernate support though. apm(4) does not mention suspend timers at all. acpi(4) mentions "timer" as a sub-device and feature that can be disabled. Regards, James Phillips __________________________________________________________________ Connect with friends from any web browser - no download required. Try the new Yahoo! Canada Messenger for the Web BETA at http://ca.messenger.yahoo.com/webmessengerpromo.php