From: xming <xmingske@gmail.com>
To: "Jeremy Fitzhardinge" <jeremy@goop.org>
Cc: linux-kernel@vger.kernel.org, Xen-devel <xen-devel@lists.xensource.com>
Subject: Re: Cannot boot xen DomU > 2.6.23.1
Date: Fri, 18 Jan 2008 17:56:09 +0100 [thread overview]
Message-ID: <519a8b110801180856o7757889as47106fd3eabcc0de@mail.gmail.com> (raw)
In-Reply-To: <4790D187.8050000@goop.org>
On Jan 18, 2008 5:19 PM, Jeremy Fitzhardinge <jeremy@goop.org> 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
next prev parent reply other threads:[~2008-01-18 16:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-17 16:13 xming
2008-01-17 17:15 ` Jeremy Fitzhardinge
2008-01-17 19:13 ` xming
2008-01-18 7:32 ` Jeremy Fitzhardinge
2008-01-18 12:38 ` xming
2008-01-18 16:19 ` Jeremy Fitzhardinge
2008-01-18 16:56 ` xming [this message]
2008-01-18 17:26 ` Jeremy Fitzhardinge
2008-01-20 13:08 ` xming
2008-01-20 18:37 ` Jeremy Fitzhardinge
2008-01-20 19:29 ` xming
2008-01-20 23:52 ` Jeremy Fitzhardinge
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=519a8b110801180856o7757889as47106fd3eabcc0de@mail.gmail.com \
--to=xmingske@gmail.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=xen-devel@lists.xensource.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®