From mboxrd@z Thu Jan 1 00:00:00 1970 From: Priit Laes Subject: Lock warning traceback Date: Tue, 29 Sep 2009 08:56:24 +0300 Message-ID: <1254203784.2432.4.camel@chi> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: QUOTED-PRINTABLE To: kvm@vger.kernel.org Return-path: Received: from ns.store20.com ([212.7.7.16]:40825 "EHLO store20.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750826AbZI2GEo convert rfc822-to-8bit (ORCPT ); Tue, 29 Sep 2009 02:04:44 -0400 Received: from chi (r22fw2.campusnet.ee [193.40.10.180]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: plaes) by store20.com (Postfix) with ESMTPSA id 7840F1A0071 for ; Tue, 29 Sep 2009 08:56:26 +0300 (EEST) Sender: kvm-owner@vger.kernel.org List-ID: Hi! I've been getting some locking-related warning when I fire up a KVM machine. This has been popping up since a 2.6.30 kernel: [snip] [119206.978058] BUG: MAX_LOCK_DEPTH too low! [119206.978062] turning off the locking correctness validator. [119206.978067] Pid: 9510, comm: kvm Not tainted 2.6.31 #44 [119206.978071] Call Trace: [119206.978080] [] __lock_acquire+0x94c/0x974 [119206.978086] [] lock_acquire+0xcc/0xe9 [119206.978092] [] ? mm_take_all_locks+0xd9/0x110 [119206.978099] [] ? mutex_lock_nested+0x23b/0x24a [119206.978104] [] ? mm_take_all_locks+0x3a/0x110 [119206.978109] [] _spin_lock_nest_lock+0x2c/0x3b [119206.978114] [] ? mm_take_all_locks+0xd9/0x110 [119206.978119] [] mm_take_all_locks+0xd9/0x110 [119206.978125] [] do_mmu_notifier_register +0xa8/0x16a [119206.978130] [] mmu_notifier_register+0xe/0x10 [119206.978136] [] kvm_dev_ioctl+0x136/0x2ed [119206.978142] [] vfs_ioctl+0x1d/0x82 [119206.978147] [] do_vfs_ioctl+0x45b/0x4a1 [119206.978153] [] ? __up_read+0x9a/0xa2 [119206.978158] [] ? up_read+0x26/0x2a [119206.978163] [] sys_ioctl+0x42/0x65 [119206.978169] [] system_call_fastpath+0x16/0x1b [119216.471426] kvm: emulating exchange as write [/snip] Although, this does not seem to be critical as my guest op-system seems to be working fine... P=C3=A4ikest, Priit :)