Hi,
somehow this thread ended without any conclusion. Today I noticed
that
BUG: MAX_LOCK_DEPTH too low!
still shows up when starting kvm on 2.6.31-rc8
So is increasing MAX_LOCK_DEPTH to say 96 good way to go?
If yes, shouldn't we set this for upstream kernel?
thanks
nik
On Sun, May 24, 2009
Andrea Arcangeli wrote:
On Sun, May 17, 2009 at 11:27:42PM +0300, Avi Kivity wrote:
Andrea, looks like the mother of all locks below.
eheh yes that really is the mother of all locks ;).
So the thing is, like BUG says MAX_LOCK_DEPTH is too low, to fix you
should rebuild after
On Sun, May 17, 2009 at 11:27:42PM +0300, Avi Kivity wrote:
Andrea, looks like the mother of all locks below.
eheh yes that really is the mother of all locks ;).
So the thing is, like BUG says MAX_LOCK_DEPTH is too low, to fix you
should rebuild after increasing it in include/linux/sched.h to
Hi,
sometimes trying to start kvm on 2.6.30-rc5 (with kvm module v85, userspace
v85) fails with:
kvm_create_vm: Interrupted system call
Could not create KVM context
and following backtrace appears in dmesg:
[ 309.546138] BUG: MAX_LOCK_DEPTH too low!
[ 309.549964] turning off the locking
