From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dietmar Hahn Subject: Re: dump with xen-unstable & linux 3.2.17 Date: Fri, 01 Jun 2012 08:54:31 +0200 Message-ID: <1450428.mTiMjbI6q8@amur> References: <4FC7B32F0200007800087786@nat28.tlf.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4FC7B32F0200007800087786@nat28.tlf.novell.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: xen-devel@lists.xen.org Cc: Juergen Gross , keir@xen.org, Ben Guthro , Jan Beulich , Konrad Rzeszutek Wilk List-Id: xen-devel@lists.xenproject.org Am Donnerstag 31 Mai 2012, 17:06:39 schrieb Jan Beulich: > >>> On 31.05.12 at 17:52, Ben Guthro wrote: > > 1. The changeset mentioned below needed to be reverted, as it was > > removing the CPUS at suspend time. > > I assume you refer to the one line change, not the full c/s? > Juergen would have to tell us whether reverting that would > break something else. Maybe this will take some time as Juergen is away for a week. Dietmar. > > > 2. The linux xen watchdog driver (drivers/watchdog/xen_wdt.c) seems to > > be enabling itsself on resume, even if you tell it not to. > > I worked around this by just turning off watchdogs in my kernel > > config...because I wasn't using them anyhow. > > That was a problem up to 3.3, but was fixed in 3.4 afaict. What > kernel version did you see this with? > > Jan > > > On Fri, May 25, 2012 at 9:20 AM, Ben Guthro wrote: > >> Changed parts: > >> > >> diff --git a/xen/common/schedule.c b/xen/common/schedule.c > >> index 0854f55..95cb2b4 100644 > >> --- a/xen/common/schedule.c > >> +++ b/xen/common/schedule.c > >> @@ -543,7 +543,7 @@ int cpu_disable_scheduler(unsigned int cpu) > >> int ret = 0; > >> > >> c = per_cpu(cpupool, cpu); > >> - if ( (c == NULL) || (system_state == SYS_STATE_suspend) ) > >> + if ( (c == NULL) ) > >> return ret; > >> > >> for_each_domain_in_cpupool ( d, c ) -- Company details: http://ts.fujitsu.com/imprint.html