From: Tony Vroon <tony@linx.net>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Michal Hocko <mhocko@suse.cz>,
Matthew Garrett <mjg59@srcf.ucam.org>,
linux-kernel@vger.kernel.org,
Jesse Barnes <jbarnes@virtuousgeek.org>,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
pm list <linux-pm@lists.linux-foundation.org>
Subject: Re: commit 9630bdd9 changes behavior of the poweroff - bug?
Date: Thu, 08 Apr 2010 23:37:43 +0100 [thread overview]
Message-ID: <1270766263.5923.3.camel@localhost> (raw)
In-Reply-To: <201004082243.18393.rjw@sisk.pl>
[-- Attachment #1: Type: text/plain, Size: 510 bytes --]
Rafael,
I have the exact same "lid close = powering back on" regression on a
Fujitsu-Siemens Lifebook S6420. Totally missed this thread before, but
I'm glad that I'm not alone with this one.
Happy to test any patches you may come up with; will an acpidump do for
you or do you need additional data?
Regards,
--
Tony Vroon
UNIX systems administrator
London Internet Exchange Ltd, Trinity Court, Trinity Street,
Peterborough, PE1 1DA
Registered in England number 3137929
E-Mail: tony@linx.net
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2010-04-08 22: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
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:37 ` Tony Vroon [this message]
2010-04-08 22:54 ` Rafael J. Wysocki
2010-04-08 22:54 ` Rafael J. Wysocki
2010-04-09 20:42 ` 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-12 23:01 ` Rafael J. Wysocki
2010-04-13 8:27 ` Michal Hocko
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-19 11:59 ` Michal Hocko
2010-04-19 11:59 ` Michal Hocko
2010-04-19 15:19 ` Rafael J. Wysocki
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 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 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-27 6:51 ` Michal Hocko
2010-04-26 18:51 ` Rafael J. Wysocki
2010-04-26 15:05 ` Michal Hocko
2010-04-25 2:35 ` Rafael J. Wysocki
2010-04-16 18:00 ` Rafael J. Wysocki
2010-04-13 20:53 ` Rafael J. Wysocki
2010-04-12 23:01 ` Rafael J. Wysocki
2010-04-10 19:36 ` Rafael J. Wysocki
2010-04-09 21:20 ` Tony Vroon
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=1270766263.5923.3.camel@localhost \
--to=tony@linx.net \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=mhocko@suse.cz \
--cc=mjg59@srcf.ucam.org \
--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 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.