[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Xen-devel] Re: Cannot boot xen DomU > 2.6.23.1
- To: "Jeremy Fitzhardinge" <jeremy@xxxxxxxx>
- From: xming <xmingske@xxxxxxxxx>
- Date: Fri, 18 Jan 2008 17:56:09 +0100
- Cc: Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, linux-kernel@xxxxxxxxxxxxxxx
- Delivery-date: Fri, 18 Jan 2008 10:36:04 -0800
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=Tv3fwR73PlPFMSp9tE90WmDIDfpjXEYVpvgiXZbIS44=; b=bzCB6v7VscXOLXPDnmzC/Oa2n/sQPXmazvlRMf50cst1/HEwP6PA7vqyIS6TlL+FDLBeWrjrQQWJBtULbAVyPE4cu/IZwjsJ1ClXU6uBhSu9hdwJd0waxp4U0l1UOZ+JdTGWkK0J42Jk5RRY1V5cMWvYzFDy4HZCb2k3gaJ6fj4=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=dnpJuw/NrsXdHY1qJVWXKBjj7XqVEOec28BZ5c4oRmnnG30PsUFuPNp4NStKLH6ssiLBtD49/3kgCLEmMVmTOkm3bvvAaVHGx833sJ0cMCeT9/D7ZgAzI8bX4/LKb2AMlCQy5vtGHSfYdZmafWsfDN4eCGB8DDHFMi9GmxQWEtE=
- List-id: Xen developer discussion <xen-devel.lists.xensource.com>
On Jan 18, 2008 5:19 PM, Jeremy Fitzhardinge <jeremy@xxxxxxxx> wrote:
> > First of all this patch solves the lock-ups, it works as advertised :)
>
> OK, good. I guess events are getting lost somewhere with vcpu_info
> placement.
> Would it be possible to map the eip and some top parts of the stack back
> to kernel symbols? Seems to be the same place in both traces, which is
> interesting.
Can you tell me how, or show me some pointers?
> > Scenario 2 (have_vcpu_info_placement = 0)
> > --------------------------------------------------------------
> >
> > test1: no crash
> > test2: no crash, but occationally I still get funny output like this
> >
> > 00AAAAAAAAAAAAAAAAAAAAAAAAAAZZ
> > 00AAAAAAAAAAAAAAAAAAAAAAAAAAZZ00AAAAAAAAAAAAAAAAAAAAAAAAAAZZ
> > 00AAAAAAAAAAAAAAAAAAAAAAAAAAZZ
> > 00AAAAAAAAAAAAAAAAAAAAAAAAAAZZ
> > 0000AAAAAAAAAAAAAAAAAAAAAAAAAAZZ
> > 00AAAAAAAAAAAAAAAAAAAAAAAAAAZZ
> > 00AAAAAAAAAAAAAAAAAAAAAAAAAAZZ
> > 000AAAAAAAAAAAAAAAAAAAAAAAAAAZZ
> > 000AAAAAAAAAAAAAAAAAAAAAAAAAAZZ
> > 00AAAAAAAAAAAAAAAAAAAAAAAAAAZZ
> >
>
> Hm, I guess some of the output is getting dropped. Does this happen
> with 2.6.18-xen?
yes it does
00AAAAAAAAAAAAAAAAAAAAAAAAAAZZ
0000AAAAAAAAAAAAAAAAAAAAAAAAAAZZ
00AAAAAAAAAAAAAAAAAAAAAAAAAAZZ
00AAAAAAAAAAAAAAAAAAAAAAAAAAZZ
00AAAAAAAAAAAAAAAAAAAAAAAAAAZZ00AAAAAAAAAAAAAAAAAAAAAAAAAAZZ
00AAAAAAAAAAAAAAAAAAAAAAAAAAZZ
# uname -a
Linux builder 2.6.18-xen-r8 #3 SMP Thu Dec 20 15:07:20 CET 2007 i686
AMD Athlon(tm) X2 Dual Core Processor BE-2300 AuthenticAMD GNU/Linux
cheers
xming
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel