From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: resume from S3 sleep not working in Dom0 - Xen4.2.1 Date: Fri, 8 Feb 2013 16:22:58 -0500 Message-ID: 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" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <5114CF55.5000303@citrix.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Tomasz Wroblewski Cc: Milan opath , "xen-devel@lists.xen.org" , Ben Guthro , Jan Beulich , Konrad Rzeszutek Wilk List-Id: xen-devel@lists.xenproject.org On Fri, Feb 8, 2013 at 5:11 AM, Tomasz Wroblewski wrote: > >> Hm, that is suspect. There should not be any cpuidle_register? Perhaps >> you are .. ah yes, you are hitting a bug that should be in the stable >> tree fix. >> >> Here is the git commit b88a634a903d9670aa5f2f785aa890628ce0dece and >> 6f8c2e7933679f54b6478945dc72e59ef9a3d5e0 >> >> > > 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. > 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?