Hi!
I see these messages from the xen-kernel:
(XEN) /usr/src/xen-unstable.hg/xen/include/asm/mm.h:186:d0 Error pfn 100:
rd=ffff8300df05c100, od=0000000000000000, caf=00000000, taf=0000000000000000
(XEN) mm.c:636:d0 Error getting mfn 100 (pfn 5555555555555555) from L1 entry
8000000000100125 for dom32753
(XEN) /usr/src/xen-unstable.hg/xen/include/asm/mm.h:186:d0 Error pfn 100:
rd=ffff8300df05c100, od=0000000000000000, caf=00000000, taf=0000000000000000
(XEN) mm.c:636:d0 Error getting mfn 100 (pfn 5555555555555555) from L1 entry
8000000000100125 for dom32753
Xen does not crash, Dom0 continues to run.
System configuration:
x86_64 debug xen-kernel, x86_64 linux-2.6.18 dom0 kernel built from xen tree,
OpenSuSE 10.2 distribution as Dom0.
Steps to reproduce:
Launch yast, select "Network devices" and "Network card".
yast now reads config entries. If you are on a serial console where screen
refreshes are slow enough, you should see that xen prints something.
Exit yast without changing anything. Back on command line run "xm dmesg".
There you can see the above xen messages.
This is repeatable. Doing this multiple times without reboot, you can always
see the same message even with the same numbers.
Question:
Can anyone else on this list reproduce this?
Christoph
--
AMD Saxony, Dresden Germany
Operating System Research Center
Legal Information:
AMD Saxony Limited Liability Company & Co. KG
Sitz (Geschäftsanschrift):
Wilschdorfer Landstr. 101, 01109 Dresden, Deutschland
Registergericht Dresden: HRA 4896
vertretungsberechtigter Komplementär:
AMD Saxony LLC (Sitz Wilmington, Delaware, USA)
Geschäftsführer der AMD Saxony LLC:
Dr. Hans-R. Deppe, Thomas McCoy
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
Home