Re: [Xen-devel] Xen4.2 S3 regression?

[Ben Guthro <ben@xxxxxxxxxx>]

I've bisected this issue - and it looks like it is a rather old problem.

The following changeset introduced it in the 4.1 development stream on
Jun 17, 2010

http://xenbits.xen.org/hg/xen-unstable.hg/rev/0695a5cdcb42


Since we (XenClient Enterprise / NxTop) skipped over Xen-4.1 - we
never ran into this until now.


Any thoughts as to a solution?


-Ben



On Fri, Aug 10, 2012 at 3:15 PM, Ben Guthro <ben@xxxxxxxxxx> wrote:
> I'll continue to investigate, as my schedule allows, but haven't found
> any smoking gun just yet.
>
> This happens to be on an Ivybridge system - I have other Sandybridge
> systems that will go to sleep, but never wake up at all, forcing a
> hard power cycle.
>
> I tested these iommu= parameters on one of these machines, to no
> effect. Every time they go into S3, a hard reset is necessary to get
> them to come out of it.
>
>
>
>
> On Fri, Aug 10, 2012 at 2:50 AM, Jan Beulich <JBeulich@xxxxxxxx> wrote:
>>>>> On 09.08.12 at 18:09, Ben Guthro <ben@xxxxxxxxxx> wrote:
>>> iommu=no-intremap
>>> This seems to work around the issue on this platform, performing
>>> multiple suspend/resume cycles, and ahci came back afterwards just
>>> fine.
>>>
>>> What is the downside to flipping this off?
>>
>> Loss of security (against misbehaving/malicious guests). So we
>> certainly want/need to get to the bottom of this (especially if
>> this is not only one kind of system that's affected).
>>
>>> iommu=off
>>> This test behaved similarly to the above, also working around the issue.
>>
>> Of course, this is a superset of the former.
>>
>> This result, however, makes it more likely again to indeed be a
>> Xen side problem, not Dom0 induced corruption.
>>
>> Jan
>>

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel