linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Michal Hocko <mhocko@suse.cz>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
	linux-kernel@vger.kernel.org,
	Jesse Barnes <jbarnes@virtuousgeek.org>
Subject: Re: commit 9630bdd9 changes behavior of the poweroff - bug?
Date: Thu, 1 Apr 2010 14:45:35 +0100	[thread overview]
Message-ID: <20100401134535.GA6527@srcf.ucam.org> (raw)
In-Reply-To: <20100401133923.GA4104@tiehlicka.suse.cz>

On Thu, Apr 01, 2010 at 03:39:23PM +0200, Michal Hocko wrote:
> Hi Rafael, Matthew,
> my laptop changed behavior during poweroff recently (after upgrading
> from .33 to .34-rc1). The system seems to be powered off (status display
> is off) at first glance but when I close the lid then I can hear a noise
> which sounds like HDD parking and when I open lid again it starts
> booting without poweroff button (same like when I suspend to RAM).

Hm. At a guess, we're somehow managing to leave the lid GPE enabled at 
poweroff. Can you send the output of the acpidump command?

-- 
Matthew Garrett | mjg59@srcf.ucam.org

  reply	other threads:[~2010-04-01 13:45 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-01 13:39 commit 9630bdd9 changes behavior of the poweroff - bug? Michal Hocko
2010-04-01 13:45 ` Matthew Garrett [this message]
2010-04-01 13:53   ` Michal Hocko
2010-04-02 19:31     ` Rafael J. Wysocki
2010-04-07  7:34       ` Michal Hocko
2010-04-07 19:49         ` Rafael J. Wysocki
2010-04-08  9:49           ` Michal Hocko
2010-04-08 20:43             ` Rafael J. Wysocki
2010-04-08 22:37               ` Tony Vroon
2010-04-08 22:54                 ` Rafael J. Wysocki
2010-04-09 20:42               ` Rafael J. Wysocki
2010-04-09 21:20                 ` Tony Vroon
2010-04-10 19:36                   ` Rafael J. Wysocki
2010-04-12 23:01                     ` Rafael J. Wysocki
2010-04-13  8:27                       ` Michal Hocko
2010-04-13 20:53                         ` Rafael J. Wysocki
2010-04-14  7:58                           ` Michal Hocko
2010-04-16 18:00                             ` Rafael J. Wysocki
2010-04-19 11:59                               ` Michal Hocko
2010-04-19 15:19                                 ` Rafael J. Wysocki
2010-04-25  2:35                                   ` Rafael J. Wysocki
2010-04-25  3:15                                     ` Rafael J. Wysocki
2010-04-26 15:05                                     ` Michal Hocko
2010-04-26 16:22                                       ` Len Brown
2010-04-27  7:04                                         ` Michal Hocko
2010-04-29 14:38                                         ` Tony Vroon
2010-04-26 18:51                                       ` Rafael J. Wysocki
2010-04-27  6:51                                         ` Michal Hocko
2010-04-27 22:06                                           ` Rafael J. Wysocki
2010-04-28 21:18                                             ` Rafael J. Wysocki

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20100401134535.GA6527@srcf.ucam.org \
    --to=mjg59@srcf.ucam.org \
    --cc=jbarnes@virtuousgeek.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhocko@suse.cz \
    --cc=rjw@sisk.pl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).