WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

RE: [Xen-devel] domains not shutting down properly -theproblemisbackagai

To: "Keir Fraser" <keir.fraser@xxxxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-devel] domains not shutting down properly -theproblemisbackagain
From: "James Harper" <james.harper@xxxxxxxxxxxxxxxx>
Date: Sat, 3 Jan 2009 11:57:36 +1100
Cc:
Delivery-date: Fri, 02 Jan 2009 16:58:06 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <C583E3EB.20ADF%keir.fraser@xxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <AEC6C66638C05B468B556EA548C1A77D01550177@trantor> <C583E3EB.20ADF%keir.fraser@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AclsEUiDJwnrGfQLQ6G5Bsw4GM+wzgAAL2RgAAIdJkkAHEzXYAAA9a8QAAD1UUAACaHcAAABmirxAAEexXAAAH2McAAAGpUAAAH94BAAAdTsvgABrLdgAASGj2IAE4Rj0A==
Thread-topic: [Xen-devel] domains not shutting down properly -theproblemisbackagain
> On 02/01/2009 13:27, "James Harper" <james.harper@xxxxxxxxxxxxxxxx>
wrote:
> 
> > I added some debugging to the send_guest_global_virq code path too,
but
> > as soon as the DomU I created for testing shut down, my Dom0 became
> > unresponsive so I suspect I have botched my debug statements. It's
> > nearly 12:30am here and the server is at work so I'm done for the
day.
> >
> > The most frustrating thing is that I just know it's going to be some
> > stupid little configuration thing on my server causing all of
this!!!
> 
> Perhaps multiprocessor dom0, plus a bug in the dom0 kernel which means
> that
> the VCPU which Xen notifies for the virq is not the one which dom0
kernel
> is
> expecting to receive the notification to? What do you use as dom0
kernel?
> 

My dom0 kernel is http://xenbits.xensource.com/linux-2.6.18-xen.hg

The crash I had last night was just:

"
void send_guest_global_virq(struct domain *d, int virq)
{
    unsigned long flags;
    int port;
    struct vcpu *v;
    struct evtchn *chn;

    ASSERT(virq_is_global(virq));

if (virq == VIRQ_DOM_EXC)
  printk("send_guest_global_virq\n");
"

adding the last two lines above. There should be no reason for that to
cause a crash that I can see, but as soon as I take those lines away it
all works. I have printk's in the function that calls
send_guest_global_virq and they work just fine.

Is my version of gcc a problem "gcc (Debian 4.3.2-1) 4.3.2"?

When things like adding (seemingly) benign print statements start
causing crashes (or making crashes go away :), I start to get suspicious
that there is something a whole lot different going on...

James

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>