[<prev] [next>] [day] [month] [year] [list]
Message-ID: <6278d2220808221354s7b978e28q718a0654cb4b34eb@mail.gmail.com>
Date: Fri, 22 Aug 2008 21:54:03 +0100
From: "Daniel J Blueman" <daniel.blueman@...il.com>
To: "Linux Kernel" <linux-kernel@...r.kernel.org>
Subject: [2.6.27-rc4] MAX_LOCK_DEPTH too low...
When running some kvm testing on 2.6.27-rc4 with various kernel debug
options enabled, I hit the MAX_LOCK_DEPTH limit of 48:
[ 30.670253] uhci_hcd 0000:00:1d.2: FGR not stopped yet!
[ 30.701773] uhci_hcd 0000:00:1d.1: FGR not stopped yet!
[ 30.733533] uhci_hcd 0000:00:1d.0: FGR not stopped yet!
[ 30.765379] uhci_hcd 0000:00:1a.2: FGR not stopped yet!
[ 30.797253] uhci_hcd 0000:00:1a.0: FGR not stopped yet!
[ 115.469934] uhci_hcd 0000:00:1d.0: FGR not stopped yet!
[ 184.507012] Hangcheck: hangcheck value past margin!
[ 245.448004] BUG: MAX_LOCK_DEPTH too low!
[ 245.448004] turning off the locking correctness validator.
[ 260.937296] kvm: emulating exchange as write
[ 364.507049] Hangcheck: hangcheck value past margin!
[ 544.454998] Hangcheck: hangcheck value past margin!
[ 724.507006] Hangcheck: hangcheck value past margin!
Maybe the result of a particular path abusing a lock (ie a bug) even?
Daniel
--
Daniel J Blueman
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists