From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Cooper Subject: Re: Xen-4.3 and -unstable regression from changeset "numa-sched: leave node-affinity alone if not in 'auto' mode" Date: Fri, 29 Nov 2013 11:04:27 +0000 Message-ID: <529874BB.7070803@citrix.com> References: <529737AD.7070708@citrix.com> <5297B2DE.1020806@citrix.com> <1385722276.25763.12.camel@kazak.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1385722276.25763.12.camel@kazak.uk.xensource.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: Ian Campbell Cc: George Dunlap , Dario Faggioli , Jan Beulich , Xen-devel List List-Id: xen-devel@lists.xenproject.org On 29/11/13 10:51, Ian Campbell wrote: > On Thu, 2013-11-28 at 21:17 +0000, Andrew Cooper wrote: >> the XenServer patch queue on > Are you positive that the bug is in the underlying Xen tree and not some > interaction with a patch in your queue? > > A boot time issue ought to be reasonably easy to test with a bare tree. > > Ian. > I am not sure of anything at the moment, although I have found one instance of a crash with none of the XenServer patch queue whatsoever. At the moment, I have narrowed the problem down to a handful of instructions writing 0s into a well-formed region of the stack. Clearly, this is not correct, and every tweak of the debugging causes the problem to jump around. ~Andrew