From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: Xen4.2 S3 regression? Date: Wed, 26 Sep 2012 08:43:36 -0400 Message-ID: <20120926124335.GG7356@phenom.dumpdata.com> References: <20120924140411.GH31618@phenom.dumpdata.com> <20120925140611.GB16478@phenom.dumpdata.com> <5061E800020000780009DBBA@nat28.tlf.novell.com> <5062C81D020000780009DE2E@nat28.tlf.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline 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: Javier Marcet Cc: Keir Fraser , john.baboval@citrix.com, Konrad Rzeszutek Wilk , xen-devel , Ben Guthro , Jan Beulich , Thomas Goetz List-Id: xen-devel@lists.xenproject.org On Wed, Sep 26, 2012 at 09:59:07AM +0200, Javier Marcet wrote: > On Wed, Sep 26, 2012 at 9:17 AM, Jan Beulich wrote: > > >> Adding the additional call in xen/arch/x86/acpi/cpu_idle.c causes an > >> instant reboot on resume. > > > > That addition can hardly be responsible for a reboot. Did you > > Just like I could perform a full cycle without issues, the instant > reboot might as well be another way the race ends. > > > have "noreboot" (or "reboot=no") in place on the Xen command > > line? "sync_console"? > > Neither of them. I have used the sync_console parameter to check > whether it changed anything but I removed it afterwards. > > > And then again, for the other failure case, iirc it was the kernel > > that died, not the hypervisor, so the problem there isn't directly > > related to the problems here I would guess. > > All I know is that I'm using that same kernel without hypervisor, with > lots of suspend/resume and not a single issue. > > With the two kernel patches from Konrad added I can also suspend and > resume fine under the hypervisor but there is always a cpu which > receives an irq while offline. And that error you get - can you reproduce it without going to suspend/resume? Meaning if you offline/online a VCPU in the guest by manipulating the /sys/../cpuX/online attribute? And actually - we should move that discussion to a completlty different thread as it has nothing to do with the hypervisor. That is a PV kernel issue.