From: Ted Kaczmarek <tedkaz@optonline.net>
To: xen-devel@lists.xensource.com
Subject: Confused, xm dmesg output showing header from my source tree
Date: Fri, 14 Oct 2005 10:54:35 -0400 [thread overview]
Message-ID: <1129301675.12282.203.camel@pluto.linsolutions.com> (raw)
changeset: 7353:29db5bded574
tag: tip
user: kaf24@firebug.cl.cam.ac.uk
date: Wed Oct 12 11:15:02 2005 +0100
summary: Fix 64-bit compile warnings in firmware.
UP Dell Precision 330, Centos 4.1 dom0.
Should XEN even be accessing anything from the source it was built from?
Also had all the domU's toast right after this, they where running for
almost 2 days.
(XEN) DOM24: (file=mm.c, line=462) Non-privileged attempt to map I/O
space 00000000
(XEN) (file=grant_table.c, line=1016) Bad flags (0) or dom (0). (NB.
expected dom 0)
(XEN) (file=grant_table.c, line=791) gnttab_transfer: Transferee has no
reservation headroom (51072,51200) or provided a bad grant ref
(00000000) or is dying (1)
(XEN) file=/usr/src/redhat/SOURCES/xen-unstable.hg/xen/include/asm/mm.h,
line=203) Error pfn 0: rd=ffbec080, od=ff195080, caf=80000002,
taf=f0000002
(XEN) DOM24: (file=mm.c, line=350) Could not get page ref for pfn 0
(XEN) DOM24: (file=mm.c, line=2220) Could not get page for mach->phys
update
I will archive this changset so if anything additional of value can be
provided let me know.
Regards,
Ted
reply other threads:[~2005-10-14 14:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1129301675.12282.203.camel@pluto.linsolutions.com \
--to=tedkaz@optonline.net \
--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.