From: Ross Philipson <ross.philipson@gmail.com>
To: Ian Campbell <ian.campbell@citrix.com>,
Paul Durrant <Paul.Durrant@citrix.com>
Cc: Andrew Cooper <Andrew.Cooper3@citrix.com>,
Ian Jackson <Ian.Jackson@citrix.com>,
Jan Beulich <JBeulich@suse.com>,
xen-devel <xen-devel@lists.xen.org>
Subject: Re: ACPI shutdown unreliable with win7?
Date: Fri, 29 May 2015 11:34:46 -0400 [thread overview]
Message-ID: <55688716.7040304@gmail.com> (raw)
In-Reply-To: <1432912292.15036.64.camel@citrix.com>
On 05/29/2015 11:11 AM, Ian Campbell wrote:
> On Fri, 2015-05-29 at 16:06 +0100, Paul Durrant wrote:
>>> FWIW We appear to wait 200s, if we were seeing failures due to windows
>>> update then I'd be inclined to extend that, but I think right now that
>>> would be premature, unless WU happens with no status on the screen.
>>>
>>
>> No, you'd see something. Perhaps our ACPI lid/power switch code is just buggy then?
>
> It seems to work reliably for the WinXP tests, FWIW...
>
> Ian.
>
One thing I find confusing is that the firmware code does not even have
a power button device (PNP0C0C) or the fixed feature power button that
is enabled in the FADT (flag == PWR_BUTTON bit 4). So I don't see how
the shutdown is purely an ACPI function. Is there something else to the
story? Is it relying on PV tools to do it?
Ross
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
>
--
Ross Philipson
next prev parent reply other threads:[~2015-05-29 15:34 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-22 8:54 ACPI shutdown unreliable with win7? Ian Campbell
2015-05-22 8:59 ` Andrew Cooper
2015-05-22 9:08 ` Ian Campbell
2015-05-29 12:54 ` Ian Campbell
2015-05-29 13:04 ` Jan Beulich
2015-05-29 13:13 ` Ian Campbell
2015-05-29 14:25 ` Paul Durrant
2015-05-29 14:35 ` Ian Campbell
2015-05-29 15:06 ` Paul Durrant
2015-05-29 15:11 ` Ian Campbell
2015-05-29 15:34 ` Ross Philipson [this message]
2015-05-29 16:00 ` Paul Durrant
2015-05-29 16:11 ` Ross Philipson
2015-05-29 16:14 ` Ross Philipson
2015-05-29 15:34 ` Paul Durrant
2015-05-29 15:56 ` Jan Beulich
2015-05-29 15:51 ` Paul Durrant
2015-05-29 14:35 ` Jan Beulich
2015-05-29 13:14 ` Andrew Cooper
2015-05-29 13:19 ` Ian Campbell
2015-05-29 13:28 ` Jan Beulich
2015-05-29 14:00 ` Ian Campbell
2015-05-29 14:31 ` Andrew Cooper
2015-05-29 14:38 ` Ian Campbell
2015-05-29 14:40 ` Jan Beulich
2015-05-29 14:49 ` Ian Campbell
2015-05-29 18:55 ` Don Slutz
2015-05-22 9:01 ` Jan Beulich
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=55688716.7040304@gmail.com \
--to=ross.philipson@gmail.com \
--cc=Andrew.Cooper3@citrix.com \
--cc=Ian.Jackson@citrix.com \
--cc=JBeulich@suse.com \
--cc=Paul.Durrant@citrix.com \
--cc=ian.campbell@citrix.com \
--cc=xen-devel@lists.xen.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.