From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Atom2 <ariel.atom2@web2web.at>
Cc: xen-devel <xen-devel@lists.xenproject.org>,
Ian Campbell <ian.campbell@citrix.com>,
Jan Beulich <JBeulich@suse.com>
Subject: Re: Powerdown problem on XEN | ACPI S5
Date: Wed, 14 Aug 2013 21:38:33 +0100 [thread overview]
Message-ID: <520BEAC9.107@citrix.com> (raw)
In-Reply-To: <520BE76A.9010905@web2web.at>
On 14/08/13 21:24, Atom2 wrote:
> Am 14.08.13 22:18, schrieb Andrew Cooper:
> [...]
>>
>> Ok thanks.
>>
>> Do you mind confirming whether S5 works with "iommu=off" on the Xen
>> command line?
>>
>> ~Andrew
>>
> Yes, that works: The system powers off after issuing
> shutdown -h now
> from the dom0.
So it is certainly an iommu interaction issue, which was sadly suspected
given that we have seen similar problems in the past.
Curiously, there are two IOMMUs on the system. I am not familiar enough
with Cougar Point chipsets to know how they are layed out. Perhaps the
ACPI tables might have more information.
ACPI interaction with Xen is tricky at the best of times. Xen as no AML
interpreter, so relies on Linux in dom0 to most of the ACPI legwork.
My best guess at the moment is that something in the ACPI code for S5 is
turning off enough of the PCH that Xen can no longer talk to the one of
the IOMMUs.
~Andrew
next prev parent reply other threads:[~2013-08-14 20:38 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-14 8:48 Powerdown problem on XEN | ACPI S5 Atom2
2013-08-14 10:30 ` Jan Beulich
2013-08-14 13:52 ` Atom2
2013-08-14 14:00 ` Andrew Cooper
2013-08-14 17:00 ` Atom2
2013-08-14 17:30 ` Andrew Cooper
2013-08-14 18:40 ` Atom2
2013-08-14 19:10 ` Atom2
2013-08-14 19:18 ` Andrew Cooper
2013-08-14 19:39 ` Atom2
2013-08-14 20:18 ` Andrew Cooper
2013-08-14 20:24 ` Atom2
2013-08-14 20:30 ` Atom2
2013-08-14 20:34 ` Ben Guthro
2013-08-14 20:37 ` Konrad Rzeszutek Wilk
2013-08-14 21:56 ` Atom2
2013-08-15 1:58 ` Ben Guthro
2013-08-15 19:28 ` Atom2
2013-08-15 20:26 ` Konrad Rzeszutek Wilk
2013-08-15 21:39 ` Atom2
2013-08-16 12:24 ` Konrad Rzeszutek Wilk
2013-12-11 21:52 ` Konrad Rzeszutek Wilk
2013-08-15 13:40 ` Konrad Rzeszutek Wilk
2013-08-14 20:38 ` Andrew Cooper [this message]
2013-08-14 20:54 ` Atom2
2013-08-14 21:11 ` Andrew Cooper
2013-08-15 8:12 ` Jan Beulich
2013-08-15 8:16 ` Atom2
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=520BEAC9.107@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=JBeulich@suse.com \
--cc=ariel.atom2@web2web.at \
--cc=ian.campbell@citrix.com \
--cc=xen-devel@lists.xenproject.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;
as well as URLs for NNTP newsgroup(s).