From owner-acpi-jp@jp.freebsd.org  Sat Feb 24 05:56:47 2001
Received: (from daemon@localhost)
	by castle.jp.freebsd.org (8.9.3+3.2W/8.7.3) id FAA37529;
	Sat, 24 Feb 2001 05:56:47 +0900 (JST)
	(envelope-from owner-acpi-jp@jp.FreeBSD.org)
Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1])
	by castle.jp.freebsd.org (8.9.3+3.2W/8.7.3) with ESMTP id FAA37524
	for <acpi-jp@jp.freebsd.org>; Sat, 24 Feb 2001 05:56:45 +0900 (JST)
	(envelope-from gallatin@cs.duke.edu)
Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30])
	by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id PAA24692
	for <acpi-jp@jp.freebsd.org>; Fri, 23 Feb 2001 15:56:37 -0500 (EST)
Received: (from gallatin@localhost)
	by grasshopper.cs.duke.edu (8.11.2/8.9.1) id f1NKu7a87027;
	Fri, 23 Feb 2001 15:56:07 -0500 (EST)
	(envelope-from gallatin@cs.duke.edu)
From: Andrew Gallatin <gallatin@cs.duke.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <14998.52839.389426.155188@grasshopper.cs.duke.edu>
Date: Fri, 23 Feb 2001 15:56:07 -0500 (EST)
To: acpi-jp@jp.freebsd.org
X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid
Reply-To: acpi-jp@jp.freebsd.org
Precedence: list
X-Distribute: distribute version 2.1 (Alpha) patchlevel 24e+000315
X-Sequence: acpi-jp 1074
Subject: [acpi-jp 1074] 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: gallatin@cs.duke.edu


Hi,

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).  If I attempt to press the power button, I see
one "stray irq 9" on console.

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?

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

Also, how would I go about suspending the machine?  Is this possible?
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
  ^C
  ^Z
  ^Tload: 0.00  cmd: acpiconf 39 [acpislp] 0.00u 0.00s 0% 60k
  esc b (send break)
                    Stopped at      siointr1+0xb1:  jmp     siointr1+0x1b7
  db> ps
  pid   proc     addr    uid  ppid  pgrp  flag stat wmesg   wchan   cmd
   39 cbfeb980 ce20e000    0     6    39 004002  3                  acpiconf
    6 cbfebba0 ce20b000    0     1     6 004002  3    wait cbfebba0 sh
    5 cbfebdc0 cce9f000    0     0     0 000204  3  syncer c0369978 syncer
    4 cbfebfe0 cce9d000    0     0     0 100204  3  psleep c03515ac bufdaemon
    3 cbfec200 cce9b000    0     0     0 000204  3  psleep c035d2e0 vmdaemon
    2 cbfec420 cce99000    0     0     0 100204  3  psleep c03327d8 pagedaemon
   27 cbfec640 cca26000    0     0     0 000204  6                  irq8: rtc
   26 cbfec860 cca24000    0     0     0 000204  6                  irq0: clk
   25 cbfeca80 cca22000    0     0     0 000204  6                  irq7: ppc0
   24 cbfecca0 cca20000    0     0     0 000204  6                  irq3: sio1
   23 cbfecec0 cca1e000    0     0     0 000204  6                  irq4: sio0
   22 cbfed0e0 cca1c000    0     0     0 000204  6                  swi0: tty:sio
   21 cbfed300 cca1a000    0     0     0 000204  6                  irq6: fdc0
   20 cbfed520 cca12000    0     0     0 000204  6                  irq11: ohci0++
   19 cbfed740 cca0f000    0     0     0 000204  6                  irq14: fxp0
   18 cbfed960 cca0d000    0     0     0 000204  6                  irq9: acpi0
   17 cbfedb80 cca04000    0     0     0 000204  6                  swi3: cambio
   16 cbfedda0 cca02000    0     0     0 000204  6                  swi2: camnet
   15 cbfedfc0 cca00000    0     0     0 000204  6                  swi5: task queue
   14 cbfee1e0 cc9fe000    0     0     0 000204  3  rndslp c0341000 random
   13 cbfee400 cc9fc000    0     0     0 000204  6                  swi4: vm
   12 cbfee620 cc9fa000    0     0     0 00020c  6                  swi6: tty:sio+
   11 cbfee840 cc9f8000    0     0     0 000204  6                  swi1: net
   10 cbfeea60 cbff5000    0     0     0 00020c  2                  idle
    1 cbfeec80 cbff3000    0     0     1 004200  3    wait cbfeec80 init
    0 c0368f00 c03fa000    0     0     0 000200  3   sched c0368f00 swapper

<...>
At this point, I can call panic in ddb and reboot the machine..

Thank you for your help,

Drew

------------------------------------------------------------------------------
Andrew Gallatin, Sr Systems Programmer	http://www.cs.duke.edu/~gallatin
Duke University				Email: gallatin@cs.duke.edu
Department of Computer Science		Phone: (919) 660-6590







