From 35e440b8530a92377c580dbd8ba3a4a01b3fef2c Mon Sep 17 00:00:00 2001 From: Eitan Adler Date: Sat, 23 Feb 2013 14:50:24 +0000 Subject: [PATCH] Update the lock-order-reversal question PR: docs/174226 Submitted by: Bas Smeelen Reviewed by: Erich Dollansky Reviewed by: avg Reviewed by: bjk Discussed with: wblock Approved by: ??? (mentor) --- en_US.ISO8859-1/books/faq/book.xml | 16 +++++++++++++--- 1 file changed, 13 insertions(+), 3 deletions(-) diff --git a/en_US.ISO8859-1/books/faq/book.xml b/en_US.ISO8859-1/books/faq/book.xml index eaab6c11a8..e52f33370a 100644 --- a/en_US.ISO8859-1/books/faq/book.xml +++ b/en_US.ISO8859-1/books/faq/book.xml @@ -2493,9 +2493,19 @@ kern.timecounter.hardware: TSC -> i8254 - An answer for this question can be found in the &os; - Glossary, see LOR. + The &os; kernel uses a number of resource locks to + arbitrate contention for certain resources. A run-time + lock diagnostic system found in &os.current; kernels + (but removed for releases), called &man.witness.4;, + detects the potential for deadlocks due to locking errors. + (It is possible to get false positives, as &man.witness.4; + is slightly conservative.) A true positive report + indicates that "if you were unlucky, a deadlock would have + happened here">. + + Problematic LORs tend to get fixed + quickly, so check &a.current.url; before posting to the + mailing lists.