Re: [Xen-devel] Xen BUG at mm-locks.h:118 in 4.2.1 - mm locking order violation - Dom0 reboot

[Sylvain Munaut <s.munaut@xxxxxxxxxxxxxxxxxxxx>]

Hi,


> In the meantime, perhaps you could try the attached (untested) patch.
> If my guess is right, it ought to stop the crashes but you might find
> the VM's performance suffers.

The patch seems to have fixed this issue.

I did however encounter a :

(XEN) p2m_pod_demand_populate: Dom1 out of PoD memory! (tot=392185
ents=131072 dom0)
(XEN) domain_crash called from p2m-pod.c:1077
(XEN) Domain 1 reported crashed by domain 0 on cpu#1:

The domU then rebooted and it doesn't seem to happen again, but since
it's related to PoD, it might be related to that same issue ...


Cheers,

    Sylvain

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel