From: Jeremy Fitzhardinge <jeremy@goop.org>
To: "Nakajima, Jun" <jun.nakajima@intel.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
M A Young <m.a.young@durham.ac.uk>
Subject: Re: Tracebacks from dom0 pvops changeset 2342
Date: Mon, 09 Feb 2009 17:16:48 -0800 [thread overview]
Message-ID: <4990D580.3020801@goop.org> (raw)
In-Reply-To: <0B53E02A2965CE4F9ADB38B34501A3A16D8517B1@orsmsx505.amr.corp.intel.com>
Nakajima, Jun wrote:
> BTW, I tried 2350 (latest), and I'm seeing repeated complaints from mod_l1_entry().
> (XEN) mm.c:1650:d0 Bad L1 flags 400000
>
Is this 32 or 64 bit? I fixed similar symptoms in 32-bit with
"x86/paravirt: return full 64-bit result" I think.
> By adding printk, I got the same info: mfn=ff7fffffff, gl1mfn=72c96 from every complaint; mfn looks bogus.
>
Sure does.
> Looks like it's the mod_l1_entry() called by do_update_va_mapping(), and the guest stack shows (by vcpu_show_execution_state() that I added) it's going back to xen_mc_flush(). As long as I ignore the MEM_LOG message, it boots up to the login prompt.
>
Odd. What's the backtrace beyond that?
> One thing that puzzles me is that MC_DEBUG is 1 in multicalls.c, but I don't see any complaints from dom0. Is the following MC_DEBUG working? Or I may be looking at a wrong stack.
>
Yes, I've noticed that sometimes multicalls seem not to report
detectable errors. I haven't looked into see what's really going on.
J
next prev parent reply other threads:[~2009-02-10 1:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-08 22:40 Tracebacks from dom0 pvops changeset 2342 M A Young
2009-02-09 1:39 ` Jeremy Fitzhardinge
2009-02-09 8:39 ` M A Young
2009-02-09 18:24 ` Jeremy Fitzhardinge
2009-02-09 18:57 ` M A Young
2009-02-09 19:37 ` Jeremy Fitzhardinge
2009-02-09 21:49 ` M A Young
2009-02-09 22:49 ` Jeremy Fitzhardinge
2009-02-10 0:45 ` Nakajima, Jun
2009-02-10 1:16 ` Jeremy Fitzhardinge [this message]
2009-02-12 5:55 ` Nakajima, Jun
2009-02-20 22:34 ` 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=4990D580.3020801@goop.org \
--to=jeremy@goop.org \
--cc=jun.nakajima@intel.com \
--cc=m.a.young@durham.ac.uk \
--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 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.