From: "Robert Wörle" <robert@linuxdevelopment.de>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: linux-acpi@vger.kernel.org
Subject: Re: [git pull request] ACPI patches for 2.6.34-rc6
Date: Wed, 12 May 2010 18:07:26 +0200 [thread overview]
Message-ID: <4BEAD23E.1070401@linuxdevelopment.de> (raw)
In-Reply-To: <20100511172543.GA17868@srcf.ucam.org>
> I've now checked the behaviour of Windows. It turns out that it never
> makes the ACPI enable SMM call on resume. This is consistent with
> http://bugzilla.kernel.org/show_bug.cgi?id=13745 which shows a bug
> being introduced by us making the enable call in the first place.
> Merging my patch and removing the blacklist would re-break these
> machines. Instead, we should just unconditionally set SCI_EN since this
> is the tested configuration. I'll send a followup patch.
>
>
Dear Matthew
Could you tell me how you "check" windows and its behaviour ?
I am stuck on S3 resume problem with some unit and i would love to get
any information ( even from windows, which does S3 fine) to help fix this
next prev parent reply other threads:[~2010-05-12 16:07 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-07 2:22 [git pull request] ACPI patches for 2.6.34-rc6 Len Brown
2010-05-07 2:34 ` Linus Torvalds
2010-05-07 6:12 ` Matthew Garrett
2010-05-07 21:06 ` Linus Torvalds
2010-05-07 21:13 ` Matthew Garrett
2010-05-07 21:21 ` Linus Torvalds
2010-05-07 21:36 ` Matthew Garrett
2010-05-11 17:25 ` Matthew Garrett
2010-05-11 17:42 ` Linus Torvalds
2010-05-11 17:59 ` Matthew Garrett
2010-05-11 18:17 ` Linus Torvalds
2010-05-11 18:22 ` Matthew Garrett
2010-05-12 16:07 ` Robert Wörle [this message]
2010-05-12 16:12 ` Matthew Garrett
2010-05-07 22:39 ` Rafael J. Wysocki
2010-05-07 23:00 ` Linus Torvalds
2010-05-07 23:17 ` Rafael J. Wysocki
2010-05-07 23:21 ` Linus Torvalds
2010-05-08 0:03 ` Rafael J. Wysocki
2010-05-08 0:10 ` Linus Torvalds
2010-05-08 5:19 ` Len Brown
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=4BEAD23E.1070401@linuxdevelopment.de \
--to=robert@linuxdevelopment.de \
--cc=linux-acpi@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox