From nobody@FreeBSD.org  Thu Nov 11 16:43:09 2004
Return-Path: <nobody@FreeBSD.org>
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 44EF016A509
	for <freebsd-gnats-submit@FreeBSD.org>; Thu, 11 Nov 2004 16:43:09 +0000 (GMT)
Received: from www.freebsd.org (www.freebsd.org [216.136.204.117])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 32A2443D41
	for <freebsd-gnats-submit@FreeBSD.org>; Thu, 11 Nov 2004 16:43:09 +0000 (GMT)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (localhost [127.0.0.1])
	by www.freebsd.org (8.12.11/8.12.11) with ESMTP id iABGh9gD046081
	for <freebsd-gnats-submit@FreeBSD.org>; Thu, 11 Nov 2004 16:43:09 GMT
	(envelope-from nobody@www.freebsd.org)
Received: (from nobody@localhost)
	by www.freebsd.org (8.12.11/8.12.11/Submit) id iABGh9lJ046080;
	Thu, 11 Nov 2004 16:43:09 GMT
	(envelope-from nobody)
Message-Id: <200411111643.iABGh9lJ046080@www.freebsd.org>
Date: Thu, 11 Nov 2004 16:43:09 GMT
From: Arne Wrner <arne_woerner@yahoo.com>
To: freebsd-gnats-submit@FreeBSD.org
Subject: acpi / power-on by timer support
X-Send-Pr-Version: www-2.3

>Number:         73823
>Category:       kern
>Synopsis:       [request] acpi / power-on by timer support
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-acpi
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          change-request
>Submitter-Id:   current-users
>Arrival-Date:   Thu Nov 11 16:50:19 GMT 2004
>Closed-Date:    
>Last-Modified:  Sun Dec  5 15:00:36 UTC 2010
>Originator:     Arne Wrner
>Release:        R5.3
>Organization:
>Environment:
FreeBSD neo.riddick.homeunix.org. 5.3-RELEASE FreeBSD 5.3-RELEASE #7: Wed Nov 10 13:37:28 UTC 2004     aw@neo.riddick.homeunix.org.:/usr/src/sys/i386/compile/RIDDICK  i386
>Description:
I believe, that the R5.3 acpi driver is unable to turn power on after a
certain amount of time passed by (just like 5.2-CURRENT-20040408). SuSE
Linux was able to do so at least one year ago.

I would prefer an acpi driver, that is able to order the power on procedure
at the time specified in the BIOS... I am ready and able to test certain
patches.
>How-To-Repeat:
neo# sysctl dev.acpi
dev.acpi.0.%desc: AMIINT VIA_K7
dev.acpi.0.%driver: acpi
dev.acpi.0.%parent: nexus0

neo# sysctl hw.acpi
hw.acpi.supported_sleep_state: S1 S4 S5
hw.acpi.power_button_state: S5
hw.acpi.sleep_button_state: S1
hw.acpi.lid_switch_state: NONE
hw.acpi.standby_state: S1
hw.acpi.suspend_state: S3
hw.acpi.sleep_delay: 1
hw.acpi.s4bios: 0
hw.acpi.verbose: 0
hw.acpi.reset_video: 1
hw.acpi.cpu.throttle_max: 16
hw.acpi.cpu.throttle_state: 8
hw.acpi.cpu.cx_supported: C1/0
hw.acpi.cpu.cx_lowest: C1
hw.acpi.cpu.cx_usage: 100.00%

neo# acpidump -d| head
/*
 * Intel ACPI Component Architecture
 * AML Disassembler version 20040527
 *
 * Disassembly of /tmp/acpidump.7VapkZ, Thu Nov 11 16:36:27 2004
 */
DefinitionBlock ("DSDT.aml", "DSDT", 1, "VIA", "VIA_K7", 4096)
{
    Name (APIC, 0x00)
    Method (\_PIC, 1, NotSerialized)
[...]
>Fix:
      ?
>Release-Note:
>Audit-Trail:
Responsible-Changed-From-To: freebsd-bugs->freebsd-acpi 
Responsible-Changed-By: arved 
Responsible-Changed-When: Tue May 10 13:49:03 GMT 2005 
Responsible-Changed-Why:  
Over to ACPI mailinglist 

http://www.freebsd.org/cgi/query-pr.cgi?pr=73823 
State-Changed-From-To: open->suspended 
State-Changed-By: linimon 
State-Changed-When: Mon Jan 28 09:07:27 UTC 2008 
State-Changed-Why:  
Mark suspended awaiting patches. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=73823 
State-Changed-From-To: suspended->closed 
State-Changed-By: arundel 
State-Changed-When: Sun Sep 5 19:54:13 UTC 2010 
State-Changed-Why:  
The FreeBSD 5.x branch went EoL long ago. 
If this issue is still present in a supported branch, please submit a new PR. 

Thanks. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=73823 
State-Changed-From-To: closed->open 
State-Changed-By: arundel 
State-Changed-When: Sun Sep 5 20:52:21 UTC 2010 
State-Changed-Why:  
It seems that this issue is still present in more recent branches. That's why it 
should remain open. 
Thanks to Bruce Cran for pointing this out to me. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=73823 

From: Andriy Gapon <avg@icyb.net.ua>
To: bug-followup@FreeBSD.org, arne_woerner@yahoo.com
Cc: Bruce Cran <brucec@FreeBSD.org>
Subject: Re: kern/73823: [request] acpi / power-on by timer support
Date: Mon, 06 Sep 2010 09:33:41 +0300

 Can someone (Bruce?) explain to me in greater detail what this PR is about?
 I thought that the functionality of turning power on at certain time completely
 belonged to BIOS.  How is acpi(4) driver expected to help?
 
 -- 
 Andriy Gapon

From: Andriy Gapon <avg@icyb.net.ua>
To: AW <arne_woerner@yahoo.com>
Cc: bug-followup@FreeBSD.org, Bruce Cran <brucec@FreeBSD.org>
Subject: Re: kern/73823: [request] acpi / power-on by timer support
Date: Mon, 06 Sep 2010 10:14:45 +0300

 on 06/09/2010 09:54 AW said the following:
 >> Can someone (Bruce?) explain to me in greater detail what this PR is about?
 >>
 > I believed that the box can boot at the specified time if Linux powers it down...
 > and that it cant, if FreeBSD does it...
 > 
 >> I thought that the functionality of turning power on at certain time completely
 >> belonged to BIOS.  How is acpi(4) driver expected to help?
 >>
 > i dont know... maybe the power down procedure offers some flag
 > (like "power down, but honor the BIOS settings about wake-up time" and
 > "power down and ignore BIOS settings about wake-up time")?
 > That LAN wake-up packet worked fine (WOL?) if FreeBSD powered the box down...
 > 
 > Maybe i used a different/buggy BIOS when I found the problem?
 > Maybe Linux couldnt do it, too...?
 > 
 > I dont use that box (mainboard: ECS K7VVM+ or so)/FreeBSD anymore,
 > but it should be easy for u to test it on contemporary hardware...
 
 Well, I am not aware of any OS assistance or control over this.
 If hardware and BIOS support this feature and it is properly configured, then
 power-on happens entirely in hardware and for OS it looks just like a normal boot.
 
 BTW, an interesting page:
 http://www.mythtv.org/wiki/ACPI_Wakeup
 It mentions that BIOS would disable wake up if hardware clock is modified later.
 We do that.
 
 -- 
 Andriy Gapon

From: Andriy Gapon <avg@icyb.net.ua>
To: Kostik Belousov <kostikbel@gmail.com>
Cc: freebsd-acpi@freebsd.org, bug-followup@freebsd.org
Subject: Re: kern/73823: [request] acpi / power-on by timer support
Date: Mon, 06 Sep 2010 13:36:21 +0300

 on 06/09/2010 12:45 Kostik Belousov said the following:
 > I think this is RTC wakeup event support. See, for instance,
 > 4.7.2.4 Real Time Clock Alarm in ACPI 4.0 spec.
 
 Well, possible.  But, unfortunately, bug originator was vague enough.
 I am not sure what he mean by "power-on", I assumed going from S5 to S1, but
 maybe he meant wakeup e.g. from S3.
 
 -- 
 Andriy Gapon

From: Andriy Gapon <avg@freebsd.org>
To: bug-followup@freebsd.org
Cc:  
Subject: Re: kern/73823: [request] acpi / power-on by timer support
Date: Sun, 05 Dec 2010 16:56:02 +0200

 I guess this PR is about ACPI interface to the time-of-day clock that is
 provided on some systems.
 Perhaps we could implement this too (along with a userland utility for
 configuration).
 
 -- 
 Andriy Gapon
>Unformatted:
