> Oh I am sorry - I gave you incorrect information. We are not seeing the > crash on our xenified 2.6.32 kernel. We just started seeing it in our newer > 3.2 pvops kernel. Sorry for the confusion. >
I would suggest you try the v3.9 kernel to see if the problem shows up. There were fixes in arch/x86/xen/setup.c and arch/x86/xen/p2m.c that might cause this. (XEN) mm.c:901:d0 Error getting mfn 800 (pfn 5555555555555555) from L1 entry 0000000000800403 for l1e_owner=0, pg_owner=0 (XEN) mm.c:4976:d0 ptwr_emulate: could not get_page_from_l1e() And earlier: [ 0.000000] init_memory_mapping: 0000000000000000-0000000036ffe000 is a bit odd. It is trying to map only up to 36ffe000. Thought it also reminds me of an clipped MTRR issue that Stefan Bader found - take a look in the xen-devel archives and see.I think the fix was a one line change in the Linxu code but I can't recall the details What you need to figure out is why the M2P (so DIRECTMAP from Xen) is giving dom0 the 14060 MFN value for some PTE. > Thanks > > -- > Ross Philipson > ------------------------------------------------------------------------------ Get 100% visibility into Java/.NET code with AppDynamics Lite It's a free troubleshooting tool designed for production Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://p.sf.net/sfu/appdyn_d2d_ap2 _______________________________________________ tboot-devel mailing list tboot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tboot-devel
