On 12/19/2013 05:34 AM, Peter Zijlstra wrote:
On Thu, Dec 19, 2013 at 12:53:56AM -0500, Sasha Levin wrote:
Hi all,
I think that my bloated kernel managed to create way too many entries in the
dependency table. If that sounds right, I can send a patch to increase those.
Attached /proc/lock_stat as requested as well.
/proc/lockdep_stats not lock_stat :-)
Do you still happen to have that?
Is the BUG message intentional ("Please attach the output of /proc/lock_stat to the
bug report")?
Here's /proc/lockdep_stats:
lock-classes: 2397 [max: 8191]
direct dependencies: 16384 [max: 16384]
indirect dependencies: 60481
all direct dependencies: 308079
dependency chains: 21162 [max: 32768]
dependency chain hlocks: 67298 [max: 163840]
in-hardirq chains: 51
in-softirq chains: 430
in-process chains: 19782
stack-trace entries: 235133 [max: 262144]
combined max dependencies: 443376596
hardirq-safe locks: 59
hardirq-unsafe locks: 1285
softirq-safe locks: 156
softirq-unsafe locks: 1136
irq-safe locks: 168
irq-unsafe locks: 1285
hardirq-read-safe locks: 4
hardirq-read-unsafe locks: 357
softirq-read-safe locks: 7
softirq-read-unsafe locks: 337
irq-read-safe locks: 8
irq-read-unsafe locks: 357
uncategorized locks: 281
unused locks: 0
max locking depth: 12
max bfs queue depth: 663
chain lookup misses: 21432
chain lookup hits: 490237032
cyclic checks: 20219
find-mask forwards checks: 12353
find-mask backwards checks: 128734
hardirq on events: 372837372
hardirq off events: 372837362
redundant hardirq ons: 3467
redundant hardirq offs: 361517382
softirq on events: 3688513
softirq off events: 3688541
redundant softirq ons: 0
redundant softirq offs: 0
debug_locks: 0
Thanks,
Sasha
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
