From owner-acpi-jp@jp.freebsd.org  Sat Feb 24 13:18:19 2001
Received: (from daemon@localhost)
	by castle.jp.freebsd.org (8.9.3+3.2W/8.7.3) id NAA68996;
	Sat, 24 Feb 2001 13:18:19 +0900 (JST)
	(envelope-from owner-acpi-jp@jp.FreeBSD.org)
Received: from mass.dis.org (3Cust138.tnt32.atl2.da.uu.net [63.38.70.138])
	by castle.jp.freebsd.org (8.9.3+3.2W/8.7.3) with ESMTP id NAA68989
	for <acpi-jp@jp.freebsd.org>; Sat, 24 Feb 2001 13:18:16 +0900 (JST)
	(envelope-from msmith@mass.dis.org)
Received: from mass.dis.org (localhost [127.0.0.1])
	by mass.dis.org (8.11.1/8.11.1) with ESMTP id f1O4Jul01433
	for <acpi-jp@jp.freebsd.org>; Fri, 23 Feb 2001 20:19:59 -0800 (PST)
	(envelope-from msmith@mass.dis.org)
Message-Id: <200102240419.f1O4Jul01433@mass.dis.org>
X-Mailer: exmh version 2.1.1 10/15/1999
To: acpi-jp@jp.freebsd.org
In-reply-to: Your message of "Fri, 23 Feb 2001 15:56:07 EST."
             <14998.52839.389426.155188@grasshopper.cs.duke.edu> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Fri, 23 Feb 2001 20:19:56 -0800
From: Mike Smith <msmith@freebsd.org>
Reply-To: acpi-jp@jp.freebsd.org
Precedence: list
X-Distribute: distribute version 2.1 (Alpha) patchlevel 24e+000315
X-Sequence: acpi-jp 1078
Subject: [acpi-jp 1078] Re: status of ACPI based power-mgmnt in -current? 
Errors-To: owner-acpi-jp@jp.freebsd.org
Sender: owner-acpi-jp@jp.freebsd.org
X-Originator: msmith@freebsd.org

> I've been playing with FreeBSD-current's ACPI features on a Dell
> PowerEdge-4400.  I cannot seem to make the machine power-off, nor can
> I suspend it.   Can somebody help?
> 
> I've attempted to power the machine off via:
> # acpiconf -e
> # halt -p
> 
> I then see this on the serial console:
> 
>   Waiting (max 60 seconds) for system process `bufdaemon' to stop...stopped
>   Waiting (max 60 seconds) for system process `syncer' to stop...stopped
> 
>   syncing disks... 
>   done
>   Uptime: 8m2s
>   Power system off using ACPI...
> 
> 
> However, the machine is still up and running (power LED on, all 8
> disks spinning, etc).

Looks like your system is hanging when the ACPI code asks it to go to S5, 
even though it claims to support doing that.  The output of 'acpidump' 
might be a good place to start.

> If I attempt to press the power button, I see
> one "stray irq 9" on console.

This is the ACPI notification interrupt, but we've already unregistered 
all the interrupt handlers including that one.

> I've also tried this using an Asus P2BLS.  I don't see the stray IRQs,
> but it does not seem to shutdown either.  Is this a known bug?

No, it should (and on at least some systems) does work.  I have a new 
code update from the ACPI CA folks to integrate, but I've been on the 
road for the last week, and will be for another week, so testing it has 
been difficult.

> I've left acpidump output for the PowerEdge at
> http://www.cs.duke.edu/~gallatin/PE4400_acpi_dump and boot messages at
> http://www.cs.duke.edu/~gallatin/PE4400_bootmsg

Hrrm.  Pretty lame stuff, unfortunately. 8(

> Also, how would I go about suspending the machine?  Is this possible?

Ideally, yes.

> If I do acpiconf -s 1, the machine locks up (or at least acpiconf is
> unkillable, and I'm in single user mode).:
>
>   # ./acpiconf -e -s 1

The system *should* go to sleep at this point.  It looks like there are 
issues with your system's ability to enter sleep states. 8(

-- 
... every activity meets with opposition, everyone who acts has his
rivals and unfortunately opponents also.  But not because people want
to be opponents, rather because the tasks and relationships force
people to take different points of view.  [Dr. Fritz Todt]
           V I C T O R Y   N O T   V E N G E A N C E


