[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Fw: Re: [Xen-devel] tip.git regression from "vsprintf: unify the format decoding layer for its 3 users"


  • To: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
  • From: Boris Derzhavets <bderzhavets@xxxxxxxxx>
  • Date: Mon, 16 Mar 2009 12:03:55 -0700 (PDT)
  • Cc: Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Mon, 16 Mar 2009 12:04:23 -0700
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=jQGA1ztJIKypVB23GSsdyJLaMbaZ0cDcLxJFRoW7aMfzfueoLKPOvcJJ0ISi+Gq/wPM7idcpds1+J6BUFO6ZzpgYkz7/uk/AbyfvurdHCfdNBZjwu/ZS5HYsq+p03O17BfN1fOQezWMQoX5mZ8iNMlh8sVcvzArlNDjX4mQuKqI=;
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>



--- On Mon, 3/16/09, Jeremy Fitzhardinge <jeremy@xxxxxxxx> wrote:
From: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Subject: Re: Fw: Re: [Xen-devel] tip.git regression from "vsprintf: unify the format decoding layer for its 3 users"
To: bderzhavets@xxxxxxxxx
Cc: "Xen-devel" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Date: Monday, March 16, 2009, 2:51 PM

Boris Derzhavets wrote:
> >>Boris Derzhavets wrote:
> > >Performed:-
> > >
> > >root@ServerIntrepid:/usr/src/linux-2.6-xen# git reset --hard
remotes/origin/xen/dom0/hackery
> > HEAD is now at a38db50 Merge commit 'tip/core/printk' into
xen/dom0/hackery
> > >make clean
> > >make
> >> make modules_install install
> > >mkinitramfs -o /boot/initrd-2.6.29-rc7-tip.img 2.6.29-rc7-tip
> > >
> > >Booted with new kernel under Xen (19355) and get same bug in
place.
> >> Cannot shutdown any PV DomU . Xen Host dies.
> >
> >OK, so we're talking about a new bug now, right?
>
> >When you say "Xen Host dies", do you mean that Xen itself
crashes? Or that >the dom0 kernel crashes? Hangs? Non-responsive?
> *******************************************
> It stops responding at all as 3 days ago.
> Just the same picture :-
>
> PV DomU CentOS 5.2 has been tested with new kernel
> During shutdown mentioned DomU usual sequence of daemon's messages
drops into stack trace with following messages at the end:-
>
> xenbus_dev_shutdown: device/vif/0 timeout closing device
> xenbus_dev_shutdown: device/vbd/51712 timeout closing device
> System halted.
>

OK, so this appears on the domU console? And at the same time, the host
becomes non-responsive? Are there any other symptoms?
******
NO
******

>
> Bellow follows my message to you sent on 3/14/09
> The bug is old.
> I do have null modem cable ( 2 m.) . Setting up serial is quite possible,
> but not right now. Boxes are located in different places.
>

If the host just stops responding, then getting the Xen serial console may be
the best way to diagnose it.

******************************
I'll do that as soon as i can
*******************************

Does it also happen if you remove the vifs from the domU config?

*********************
I can try right now
*********************

Does reverting changes 8c7e11b6b89b3054623bc26bf6bbbda3ffa0ee18,
8b0ddbff9bf6cd8acb881a6296ca5069723f61b1 and
043854ee604d2b49d4def5ac215925296b64b391 help?

**************************************
Please, type an exact git command
i am supposed to run to revert change.
**************************************

J

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

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.