From mboxrd@z Thu Jan 1 00:00:00 1970 From: George Dunlap Subject: Re: HVM hangs system on AMD A10-6800K + Hudson-D4 Date: Tue, 20 Aug 2013 10:02:18 +0100 Message-ID: <5213309A.80309@eu.citrix.com> References: <2D8CB7EA-68A3-41F1-ACA0-B0ED728511A0@gmail.com> <5213445402000078000ECFF0@nat28.tlf.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <5213445402000078000ECFF0@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: Jan Beulich Cc: Darren Shepherd , Andrew Cooper , "xen-devel@lists.xen.org" , Sherry Hurwitz List-Id: xen-devel@lists.xenproject.org On 08/20/2013 09:26 AM, Jan Beulich wrote: >>>> On 20.08.13 at 03:42, Darren Shepherd wrote: >> Okay, so I compiled, ran and tested everything between RELEASE-4.3.0 (bad) >> with master (good). Unfortunately I came to the conclusion it's not a patch >> but instead it's the debug flag. So if I build RELEASE-4.3.0 it fails my test >> case because because Config.mk has "debug ?= n". If I then just rebuild >> xen.gz with "make debug=y" it works. > > Pretty unusual - normally we'd expect more problems with debug=y > (because of extra checking done), not less. Unfortunately the kind of bug that changes when you add debugging is usually pretty difficult to track down: race conditions, clobbered variables... nearly impossible without a serial console. > >> I'll keep fooling around and see if I can narrow this down any further. So >> my simple test fails with debug off, but I don't know if debug on just makes >> it less likely to happen. I'm going to run more extensive tests later. I'll >> also try to get a serial port setup on the box. > > I'm afraid that's the only viable route. > > Jan >