From: George Dunlap <george.dunlap@eu.citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Darren Shepherd <darren.s.shepherd@gmail.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
Sherry Hurwitz <sherry.hurwitz@amd.com>
Subject: Re: HVM hangs system on AMD A10-6800K + Hudson-D4
Date: Tue, 20 Aug 2013 10:02:18 +0100 [thread overview]
Message-ID: <5213309A.80309@eu.citrix.com> (raw)
In-Reply-To: <5213445402000078000ECFF0@nat28.tlf.novell.com>
On 08/20/2013 09:26 AM, Jan Beulich wrote:
>>>> On 20.08.13 at 03:42, Darren Shepherd <darren.s.shepherd@gmail.com> 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
>
prev parent reply other threads:[~2013-08-20 9:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-14 5:51 HVM hangs system on AMD A10-6800K + Hudson-D4 Darren Shepherd
2013-08-14 9:47 ` Andrew Cooper
2013-08-14 10:21 ` Jan Beulich
2013-08-14 18:22 ` Hurwitz, Sherry
2013-08-18 2:14 ` Darren Shepherd
2013-08-19 10:31 ` George Dunlap
2013-08-20 1:42 ` Darren Shepherd
2013-08-20 8:26 ` Jan Beulich
2013-08-20 9:02 ` George Dunlap [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5213309A.80309@eu.citrix.com \
--to=george.dunlap@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=darren.s.shepherd@gmail.com \
--cc=sherry.hurwitz@amd.com \
--cc=xen-devel@lists.xen.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.