From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tomasz Wroblewski Subject: Re: resume from S3 sleep not working in Dom0 - Xen4.2.1 Date: Mon, 11 Feb 2013 09:42:47 +0100 Message-ID: <5118AF07.90704@citrix.com> References: <510F91CA02000078000BB6AA@nat28.tlf.novell.com> <510F885B.2040603@citrix.com> <20130205183236.GB5652@konrad-lan.dumpdata.com> <5114CF55.5000303@citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Konrad Rzeszutek Wilk Cc: Milan opath , "xen-devel@lists.xen.org" , Ben Guthro , Jan Beulich , Konrad Rzeszutek Wilk List-Id: xen-devel@lists.xenproject.org >> Thanks Konrad. I've tried your patches, and whilst I have not seen this >> crash in cpuidle_register anymore, the others are still present (in >> build_schedule_domains for example). >> >> > That looks familiar too. I think it got fixed in the upstream kernel > and it was a generic bug - but I can't recall which commit it was. > > Aha, all right. >> I've stumbled on a bit of interesting info - using dom0_vcpus_pin on xen >> commandline stops both the xen scheduler and dom0 kernel crashing and all >> works fine - made dozens of succesfull s3 attempts. Was wondering if you >> guys had any thoughts on this? Is the dom0 kernel even supposed to cope >> during s3 in non dom0 vcpu pin case? >> >> > No that is something new. Is this only an issue on Intel boxes but not AMD? > I think it was primarily reproducible on sandybridge intels whilst being hard/impossible to repro on Ivy Bridge - and sorry - don't have an AMD box to make a test. It might just go away with newer kernel though, I think we're in the process of updating to 3.8 (previous tests were on 3.2) so will be worth trying on that.