From: David F Barrera <dfbp@us.ibm.com>
To: xen-devel@lists.xensource.com
Subject: (XEN) (file=memory.c, line=42) Only I/O-capable domains may allocate multi-page extents.
Date: Wed, 11 Jan 2006 12:56:38 -0600 [thread overview]
Message-ID: <43C554E6.4000203@us.ibm.com> (raw)
We have seen a series of messages when running xm-test lately on a SLES
9 SP2 32-bit box with 4GB of RAM, PAE enabled Xen build. I don't know
whether this defect of just an informational message.
(XEN) (file=memory.c, line=42) Only I/O-capable domains may allocate
multi-page extents.
(XEN) (file=memory.c, line=42) Only I/O-capable domains may allocate
multi-page extents.
(XEN) (file=memory.c, line=42) Only I/O-capable domains may allocate
multi-page extents.
(XEN) (file=memory.c, line=42) Only I/O-capable domains may allocate
multi-page extents.
(XEN) (file=memory.c, line=42) Only I/O-capable domains may allocate
multi-page extents.
(XEN) (file=memory.c, line=42) Only I/O-capable domains may allocate
multi-page extents.
(XEN) (file=memory.c, line=42) Only I/O-capable domains may allocate
multi-page extents.
(XEN) (file=memory.c, line=42) Only I/O-capable domains may allocate
multi-page extents.
(XEN) (file=memory.c, line=42) Only I/O-capable domains may allocate
multi-page extents.
(XEN) (file=/tmp/xen-unstable.hg/xen/include/asm/mm.h, line=203) Error
pfn 101a63: rd=ff387500, od=00000000, caf=00000000, taf=00000000
(XEN) DOM0: (file=mm.c, line=352) Could not get page ref for pfn 101a63
(XEN) DOM0: (file=mm.c, line=2173) Could not get page for mach->phys update
--
Regards,
David F Barrera
Linux Technology Center
Systems and Technology Group, IBM
"The wisest men follow their own direction. "
Euripides
next reply other threads:[~2006-01-11 18:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-11 18:56 David F Barrera [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-01-13 19:29 (XEN) (file=memory.c, line=42) Only I/O-capable domains may allocate multi-page,extents David F Barrera
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=43C554E6.4000203@us.ibm.com \
--to=dfbp@us.ibm.com \
--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.