All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Michal Hocko <mhocko@suse.cz>
Cc: Matthew Garrett <mjg59@srcf.ucam.org>,
	linux-kernel@vger.kernel.org,
	Jesse Barnes <jbarnes@virtuousgeek.org>
Subject: Re: commit 9630bdd9 changes behavior of the poweroff - bug?
Date: Wed, 7 Apr 2010 21:49:23 +0200	[thread overview]
Message-ID: <201004072149.23791.rjw@sisk.pl> (raw)
In-Reply-To: <20100407073414.GA5174@tiehlicka.suse.cz>

On Wednesday 07 April 2010, Michal Hocko wrote:
> Sorry for late reply, but I was AFK during holiday.
> 
> On Fri 02-04-10 21:31:47, Rafael J. Wysocki wrote:
> > On Thursday 01 April 2010, Michal Hocko wrote:
> > > On Thu 01-04-10 14:45:35, Matthew Garrett wrote:
> > > > 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?
> > > 
> > > Sure, see attached.
> > 
> > Thanks.
> > 
> > Please also send the contents of /proc/acpi/wakeup.
> 
> See attached. I have checked both kernels (with and without reverted
> 9630bdd) and the output looks pretty much same. 2.6.34-rc3, however,
> looks different a bit, so I am attaching it as well.

Well, I fail to see the possible failure scenario, so let's first try a blind
shot.

Please check if this patch helps:
https://patchwork.kernel.org/patch/86238/

Rafael

  reply	other threads:[~2010-04-07 19:46 UTC|newest]

Thread overview: 54+ 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
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 [this message]
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-08 22:54                 ` Rafael J. Wysocki
2010-04-08 22:37               ` Tony Vroon
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-12 23:01                     ` 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-14  7:58                           ` Michal Hocko
2010-04-16 18:00                             ` Rafael J. Wysocki
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-25  3:15                                     ` Rafael J. Wysocki
2010-04-26 15:05                                     ` Michal Hocko
2010-04-26 15:05                                     ` Michal Hocko
2010-04-26 16:22                                       ` Len Brown
2010-04-27  7:04                                         ` Michal Hocko
2010-04-27  7:04                                         ` Michal Hocko
2010-04-29 14:38                                         ` Tony Vroon
2010-04-29 14:38                                           ` Tony Vroon
2010-04-26 16:22                                       ` Len Brown
2010-04-26 18:51                                       ` Rafael J. Wysocki
2010-04-27  6:51                                         ` Michal Hocko
2010-04-27  6:51                                         ` Michal Hocko
2010-04-27 22:06                                           ` Rafael J. Wysocki
2010-04-28 21:18                                             ` Rafael J. Wysocki
2010-04-28 21:18                                             ` Rafael J. Wysocki
2010-04-27 22:06                                           ` Rafael J. Wysocki
2010-04-26 18:51                                       ` Rafael J. Wysocki
2010-04-25  2:35                                   ` Rafael J. Wysocki
2010-04-19 15:19                                 ` Rafael J. Wysocki
2010-04-19 11:59                               ` Michal Hocko
2010-04-13 20:53                         ` Rafael J. Wysocki
2010-04-13  8:27                       ` Michal Hocko
2010-04-10 19:36                   ` Rafael J. Wysocki
2010-04-09 21:20                 ` Tony Vroon
2010-04-09 20:42               ` Rafael J. Wysocki
2010-04-08 20:43             ` 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=201004072149.23791.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=jbarnes@virtuousgeek.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhocko@suse.cz \
    --cc=mjg59@srcf.ucam.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.