[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

To: "Sylvain Munaut" <s.munaut@xxxxxxxxxxxxxxxxxxxx>
From: "Jan Beulich" <JBeulich@xxxxxxxx>
Date: Mon, 18 Feb 2013 11:05:06 +0000
Cc: xen-devel@xxxxxxxxxxxxx
Delivery-date: Mon, 18 Feb 2013 11:05:34 +0000
List-id: Xen developer discussion <xen-devel.lists.xen.org>

>>> On 18.02.13 at 11:47, Sylvain Munaut <s.munaut@xxxxxxxxxxxxxxxxxxxx> wrote:
> It is very reproducible and it's on a test machine I can reboot any
> time, so if you need more debug info, I can collect it.
> I don't have any different hw to test on unfortunately.

Minimally you will want to let us know at what changeset you
cloned your tree.

Jan


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

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

Prev by Date: Re: [Xen-devel] [PATCH] xend: disallow multiple destroy() call
Next by Date: Re: [Xen-devel] Xen BUG at mm-locks.h:118 in 4.2.1 - mm locking order violation - Dom0 reboot
Previous by thread: [Xen-devel] Xen BUG at mm-locks.h:118 in 4.2.1 - mm locking order violation - Dom0 reboot
Next by thread: Re: [Xen-devel] Xen BUG at mm-locks.h:118 in 4.2.1 - mm locking order violation - Dom0 reboot
Index(es):
- Date
- Thread

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.