On Sep 8, 2006, at 10:38 AM, Maria Butrico wrote:
I had run my domains and killed them and my console was still
also have as you know multi patch, your 128m patch and the patch I
this morning to xen-ppc.
I saw this on the machine/xen console (we have so many consoles we
(XEN) paddr_to_maddr: Dom:0 paddr: 0xc000000 type: REMOTE
(XEN) WARN at usercopy.c:62
(XEN) [000000000000F530] 000000000044C5EC .paddr_to_maddr+0x118/0x1a0
(XEN) [000000000000F5F0] 000000000044CBC4
(XEN) [000000000000F6F0] 00000000004390D8 .arch_do_dom0_op+0x140/0x4c4
(XEN) [000000000000F810] 0000000000404220 .do_dom0_op+0x193c/0x19b4
(XEN) [000000000000FC00] 000000000043CE28 .hcall_xen+0xcc/0xfc
(XEN) [000000000000FC90] 000000000043CF4C .do_hcall+0x54/0x84
(XEN) [000000000000FD20] 0000000000450348 ex_hcall_continued+0xe4/0xf4
(XEN) [000000000043B948] 800100017C0802A6
(XEN) SP (600000004bffffd8) is not in xen space
This was seen before (by another person that did not post to the
list) and used to be a panic.
I demoted it to a warn, because we are looking for stuff but I don't
think anything will be done with that address.
Basically, any page not belonging to Dom0 can be mapped by Dom0 be
cause she's the boss, these pages are either IO or REMOTE (and IO
However, I do not believe we should ever be performing guest copies
of IO or REMOTE.
0xc000000 is 192M
Hollis, I believe this is an off by one error in the xencomm somewhere.
kpblade4:/ # xm list
/usr/lib/python2.4/xmllib.py:9: DeprecationWarning: The xmllib
obsolete. Use xml.sax instead.
warnings.warn("The xmllib module is obsolete. Use xml.sax
Name ID Mem(MiB) VCPUs State Time(s)
Domain-0 0 192 1 r----- 5714.2
The console xmconsole process was still running. This
means ... ? Never
seen this before btw and I have seen some strange stuff and run xen
Xen-ppc-devel mailing list