From: "Justin P. Mattock" <justinmattock@gmail.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: BUG: MAX_LOCK_DEPTH too low!
Date: Mon, 17 Nov 2008 07:24:37 -0800 [thread overview]
Message-ID: <1226935477.3336.5.camel@LiNuX> (raw)
When running kvm I get an error
about vmalloc not having enough memory
(adding vmalloc=256m resolves the issue);
then during the session I'm seeing:
[ 201.020491] BUG: MAX_LOCK_DEPTH too low!
[ 201.020498] turning off the locking correctness validator.
other than seeing this in dmesg,
kvm run's really good.
regards;
--
Justin P. Mattock <justinmattock@gmail.com>
next reply other threads:[~2008-11-17 15:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-17 15:24 Justin P. Mattock [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-12-17 8:14 BUG: MAX_LOCK_DEPTH too low! Kirill A. Shutemov
2012-12-17 8:14 ` Kirill A. Shutemov
2012-12-17 8:17 ` Gleb Natapov
2012-12-17 8:17 ` Gleb Natapov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1226935477.3336.5.camel@LiNuX \
--to=justinmattock@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.