From owner-freebsd-acpi@FreeBSD.ORG Wed Aug 12 07:01:20 2009 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A4B20106564A for ; Wed, 12 Aug 2009 07:01:20 +0000 (UTC) (envelope-from tim.matthews7@gmail.com) Received: from mail-yx0-f181.google.com (mail-yx0-f181.google.com [209.85.210.181]) by mx1.freebsd.org (Postfix) with ESMTP id 59E708FC4E for ; Wed, 12 Aug 2009 07:01:20 +0000 (UTC) Received: by yxe11 with SMTP id 11so5753176yxe.3 for ; Wed, 12 Aug 2009 00:01:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=QRdPSi3sbDisj53vyeDdkhJfm86ikUg5Nj+Vt74g4bo=; b=waRnoCwaI0NhCWWz18UcLgqU0R3l5E5gsL35f0meSdcm6cLAKnvEiKkyAjPzKB1D2l fz7nsGdRZiOyTCSLzsth7gfLgMAjsNeMo1qdj8pdnhFGGbkvXARFHke8E0WV5Ck03pCf ELrZcA2e6etOcCyCKaTSK/4OIjI9SkitLLAIQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=rYzej3byou1lQwxK7s2Jp7jLNjSFbO4a9W1plvhmTsetV9ZZsLDzT6jKFBhv/HOXOA FfDqgygVjxeg8qKvQ27xnuXt2XvRDlhE4jcupy/Zmt9kK453hfTJRYsPdtvFKFKtAZXB pJe7iIMhwvMUUxIgTiPBkeHVhMD541wKnG0Yg= MIME-Version: 1.0 Received: by 10.231.38.140 with SMTP id b12mr2019811ibe.29.1250060479344; Wed, 12 Aug 2009 00:01:19 -0700 (PDT) In-Reply-To: References: <3f1d93450908090448p3553bfb7te177a3b247bf6cc@mail.gmail.com> <3f1d93450908092109p63b10f8bnd92d15fbbc943d4f@mail.gmail.com> <3f1d93450908102038g2f972d45yc3ae5cb0ae9de785@mail.gmail.com> Date: Wed, 12 Aug 2009 19:01:19 +1200 Message-ID: <3f1d93450908120001q5970e3baoc9d6ea0c4eeda2a5@mail.gmail.com> From: Tim Matthews To: "b. f." , freebsd-acpi@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Re: laptop doesn't power off X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Aug 2009 07:01:20 -0000 On Tue, Aug 11, 2009 at 9:57 PM, b. f. wrote: > On 8/11/09, Tim Matthews wrote: > > > I have tried different combinations of a lot of things and powering off > not > > working, everything else working fine with no sign of acpi errors in > logs. > > acpiconf -s 1 (or any other number) operation not supported. I am now > very > > sure that my bios is up to date. Is there any thing that can be done to > make > > freebsd's acpi behave like linux's acpi? > > > > Looking at http://www.lesswatts.org/projects/acpi/ , it appears that > both Linux and FreeBSD use ACPICA. So we could check to see if Linux > has made any changes to their imported sources, and how they handle > the power-down. From what you have told us, it appears that your > machine is failing at some stage in calling three functions: > > AcpiEnterSleepStatePrep(ACPI_STATE_S5); > ACPI_DISABLE_IRQS(); > AcpiEnterSleepState(ACPI_STATE_S5); > > We could specifically compare the handling of these three functions in > FreeBSD and Linux, if you know that your computer works under Linux. > If you want to enable debugging as I mentioned in a previous message > (the one where you compile kernel and modules with ACPI_DEBUG, which > can give us a lot more information than even hw.acpi.verbose=1), we > can learn more about exactly where the problem occurs. > > There are a couple of other things you can try: if you think that a > certain piece of hardware is connected with the problem (again, we > would know more if debugging was enabled), you can try: > > 1) physically removing the hardware; > 2) going into the BIOS setup and disabling the hardware, if possible; or > 3) disabling the ACPI subsystem that handles that hardware via > /boot/loader.conf > > Also, have you tried FreeBSD 8 to see if that works for you? I have just tried upgrading to current and powering off still didn't work. I am not sure if I could get you any log files as my wifi, X and probably other things no longer work. > > > In the meantime, you can safely power down your machine by running > 'shutdown -h now', and then manually cutting power. A bit of a > nuisance, but not the end of the world. > > > b. >