From owner-freebsd-questions@FreeBSD.ORG Sat Aug 18 05:54:03 2012 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8E312106566B for ; Sat, 18 Aug 2012 05:54:03 +0000 (UTC) (envelope-from freebsd@dreamchaser.org) Received: from nightmare.dreamchaser.org (nightmare.dreamchaser.org [12.32.44.142]) by mx1.freebsd.org (Postfix) with ESMTP id 2FCC68FC17 for ; Sat, 18 Aug 2012 05:54:02 +0000 (UTC) Received: from breakaway.dreamchaser.org (breakaway.dreamchaser.org. [12.32.36.73]) by nightmare.dreamchaser.org (8.13.6/8.13.6) with ESMTP id q7I5ruHo004973; Fri, 17 Aug 2012 23:53:56 -0600 (MDT) (envelope-from freebsd@dreamchaser.org) Message-ID: <502F2DF3.6040104@dreamchaser.org> Date: Fri, 17 Aug 2012 23:53:55 -0600 From: Gary Aitken User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:13.0) Gecko/20120609 Thunderbird/13.0 MIME-Version: 1.0 To: Polytropon References: <502EA73B.6000008@dreamchaser.org> <20120818030537.4d5bf55b.freebsd@edvax.de> <502F017A.7030001@dreamchaser.org> <20120818051716.40ccf88c.freebsd@edvax.de> <502F16B7.8050902@dreamchaser.org> <20120818062315.eccc7d1d.freebsd@edvax.de> In-Reply-To: <20120818062315.eccc7d1d.freebsd@edvax.de> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0.2 (nightmare.dreamchaser.org [12.32.36.65]); Fri, 17 Aug 2012 23:53:56 -0600 (MDT) Cc: FreeBSD Mailing List Subject: Re: fsck recoveries, configuration X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd@dreamchaser.org List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 18 Aug 2012 05:54:03 -0000 On 08/17/12 22:23, Polytropon wrote: > Also check the BIOS setup. In most cases, the default configuration > will assign the button press to a "soft power down", raising the > proper signal via ACPI. You can also check dmesg's output: > > acpi_button0: on acpi0 > acpi_button1: on acpi1 > > I don't know where this 2nd button is on my system, it only has > one which - when being pressed - lets the system shut down and > then power off properly. > > You can find even more elaborate data in sysctl's output: > > hw.acpi.power_button_state: S5 > hw.acpi.sleep_button_state: S3 > dev.acpi_button.0.%desc: Power Button > dev.acpi_button.0.%driver: acpi_button > dev.acpi_button.0.%location: handle=\_SB_.PWRB > dev.acpi_button.0.%pnpinfo: _HID=PNP0C0C _UID=0 > dev.acpi_button.0.%parent: acpi0 > dev.acpi_button.1.%desc: Sleep Button > dev.acpi_button.1.%driver: acpi_button > dev.acpi_button.1.%location: handle=\_SB_.SLPB > dev.acpi_button.1.%pnpinfo: _HID=PNP0C0E _UID=0 > dev.acpi_button.1.%parent: acpi0 > dev.acpi_button.1.wake: 1 > > As I said, my system doesn't have that 2nd "sleep" button anywhere, > but addressing the power button is correct, the S3 state explained > as "Commonly referred to as Standby, Sleep, or Suspend to RAM. RAM > remains powered" is then used as a signal to perform the system > shutdown as intended. Hmmm: acpi0: <030811 XSDT1017> on motherboard acpi0: Power Button (fixed) acpi0: reservation of fec00000, 1000 (3) failed acpi0: reservation of fee00000, 1000 (3) failed acpi0: reservation of ffb80000, 80000 (3) failed acpi0: reservation of fec10000, 20 (3) failed acpi0: reservation of fed80000, 1000 (3) failed acpi0: reservation of 0, a0000 (3) failed acpi0: reservation of 100000, c7e00000 (3) failed acpi_timer0: <32-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 cpu0: on acpi0 cpu1: on acpi0 cpu2: on acpi0 cpu3: on acpi0 acpi_ec0: port 0x62,0x66 on acpi0 pcib0: port 0xcf8-0xcff on acpi0 acpi_button0: on acpi0 attimer0: port 0x40-0x43 irq 0 on acpi0 atrtc0: port 0x70-0x71 irq 8 on acpi0 uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 hpet0: iomem 0xfed00000-0xfed003ff on acpi0 atkbdc0: port 0x60,0x64 irq 1 on acpi0 acpi_throttle0: on cpu0 Do all those reservation failed indicate the interrupt is not going to actually be seen? What does (fixed) mean?