From owner-p4-projects@FreeBSD.ORG Sun Feb 28 10:52:58 2010 Return-Path: Delivered-To: p4-projects@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 32767) id DDDC61065672; Sun, 28 Feb 2010 10:52:57 +0000 (UTC) Delivered-To: perforce@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A1AC8106566B for ; Sun, 28 Feb 2010 10:52:57 +0000 (UTC) (envelope-from rene@FreeBSD.org) Received: from repoman.freebsd.org (repoman.freebsd.org [IPv6:2001:4f8:fff6::29]) by mx1.freebsd.org (Postfix) with ESMTP id 581768FC08 for ; Sun, 28 Feb 2010 10:52:57 +0000 (UTC) Received: from repoman.freebsd.org (localhost [127.0.0.1]) by repoman.freebsd.org (8.14.3/8.14.3) with ESMTP id o1SAqvuK026152 for ; Sun, 28 Feb 2010 10:52:57 GMT (envelope-from rene@FreeBSD.org) Received: (from perforce@localhost) by repoman.freebsd.org (8.14.3/8.14.3/Submit) id o1SAqvI6026150 for perforce@freebsd.org; Sun, 28 Feb 2010 10:52:57 GMT (envelope-from rene@FreeBSD.org) Date: Sun, 28 Feb 2010 10:52:57 GMT Message-Id: <201002281052.o1SAqvI6026150@repoman.freebsd.org> X-Authentication-Warning: repoman.freebsd.org: perforce set sender to rene@FreeBSD.org using -f From: Rene Ladan To: Perforce Change Reviews Precedence: bulk Cc: Subject: PERFORCE change 175196 for review X-BeenThere: p4-projects@freebsd.org X-Mailman-Version: 2.1.5 List-Id: p4 projects tree changes List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Feb 2010 10:52:58 -0000 http://p4web.freebsd.org/chv.cgi?CH=175196 Change 175196 by rene@rene_self on 2010/02/28 10:52:29 IFC Affected files ... .. //depot/projects/docproj_nl/en_US.ISO8859-1/articles/contributors/Makefile#3 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/articles/contributors/article.sgml#3 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/articles/contributors/contrib.additional.sgml#50 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/articles/contributors/contrib.committers.sgml#38 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/articles/contributors/contrib.develalumni.sgml#7 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/articles/contributors/contrib.develinmemoriam.sgml#1 branch .. //depot/projects/docproj_nl/en_US.ISO8859-1/articles/contributors/contrib.ent#3 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/articles/portbuild/article.sgml#21 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/articles/version-guide/article.sgml#3 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/developers-handbook/x86/chapter.sgml#4 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/security/chapter.sgml#13 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/porters-handbook/book.sgml#73 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/captions/2009/asiabsdcon/losh-mips.sbv#1 branch .. //depot/projects/docproj_nl/en_US.ISO8859-1/captions/2009/asiabsdcon/rao-kernellocking-2.sbv#2 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/captions/2009/dcbsdcon/dixon-bsdisstilldying.sbv#2 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/share/sgml/authors.ent#31 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/mirrors/chapter.sgml#43 integrate .. //depot/projects/docproj_nl/share/sgml/mirrors.xml#11 integrate .. //depot/projects/docproj_nl/www/en/art.sgml#2 integrate .. //depot/projects/docproj_nl/www/en/cgi/search.cgi#2 integrate .. //depot/projects/docproj_nl/www/en/donations/donors.sgml#26 integrate .. //depot/projects/docproj_nl/www/en/donations/wantlist.sgml#16 integrate .. //depot/projects/docproj_nl/www/en/releases/7.3R/Makefile#1 branch .. //depot/projects/docproj_nl/www/en/releases/7.3R/docbook.css#1 branch .. //depot/projects/docproj_nl/www/en/releases/7.3R/schedule.sgml#1 branch .. //depot/projects/docproj_nl/www/en/releases/Makefile#5 integrate .. //depot/projects/docproj_nl/www/en/releng/index.sgml#32 integrate .. //depot/projects/docproj_nl/www/en/where.sgml#7 integrate .. //depot/projects/docproj_nl/www/share/sgml/commercial.consult.xml#18 integrate .. //depot/projects/docproj_nl/www/share/sgml/commercial.isp.xml#16 integrate .. //depot/projects/docproj_nl/www/share/sgml/events.xml#26 integrate .. //depot/projects/docproj_nl/www/share/sgml/news.xml#68 integrate .. //depot/projects/docproj_nl/www/share/sgml/notices.xml#6 integrate .. //depot/projects/docproj_nl/www/share/sgml/release.ent#21 integrate Differences ... ==== //depot/projects/docproj_nl/en_US.ISO8859-1/articles/contributors/Makefile#3 (text+ko) ==== @@ -1,5 +1,5 @@ # -# $FreeBSD: doc/en_US.ISO8859-1/articles/contributors/Makefile,v 1.11 2008/08/16 22:21:38 pgj Exp $ +# $FreeBSD: doc/en_US.ISO8859-1/articles/contributors/Makefile,v 1.12 2010/02/20 18:38:46 linimon Exp $ # # Article: Contributors to FreeBSD @@ -18,6 +18,7 @@ SRCS+= contrib.committers.sgml SRCS+= contrib.corealumni.sgml SRCS+= contrib.develalumni.sgml +SRCS+= contrib.develinmemoriam.sgml URL_RELPREFIX?= ../../../.. DOC_PREFIX?= ${.CURDIR}/../../.. ==== //depot/projects/docproj_nl/en_US.ISO8859-1/articles/contributors/article.sgml#3 (text+ko) ==== @@ -10,7 +10,7 @@ Contributors to FreeBSD - $FreeBSD: doc/en_US.ISO8859-1/articles/contributors/article.sgml,v 1.449 2008/08/16 22:21:38 pgj Exp $ + $FreeBSD: doc/en_US.ISO8859-1/articles/contributors/article.sgml,v 1.451 2010/02/20 19:10:50 linimon Exp $ &tm-attrib.freebsd; @@ -28,6 +28,13 @@ Donors Gallery + + As of 2010, the following section is several years out-of-date. + Donations from the past several years appear + here. + + + The FreeBSD Project is indebted to the following donors and would like to publicly thank them here! @@ -356,6 +363,20 @@ &contrib.develalumni; + + Development Team: In Memoriam + + development team + During the many years that the FreeBSD Project has been in + existence, sadly, some of our developers have passed away. + Here are some remembrances. + + In rough reverse chronological order of their + passing: + + &contrib.develinmemoriam; + + Derived Software Contributors ==== //depot/projects/docproj_nl/en_US.ISO8859-1/articles/contributors/contrib.additional.sgml#50 (text+ko) ==== @@ -1,4 +1,4 @@ - + + + @@ -220,12 +220,6 @@ - &a.cg; (1999 - - 2005) - - - - &a.sada; (1998 - 2005) @@ -326,12 +320,6 @@ - &a.alane; (2002 - - 2003) - - - - &a.amurai; (1995 - 2003) @@ -638,10 +626,6 @@ - &a.itojun; (1997 - 2001) - - - &a.chuckr; (1996 - 2000) ==== //depot/projects/docproj_nl/en_US.ISO8859-1/articles/contributors/contrib.ent#3 (text+ko) ==== @@ -1,7 +1,8 @@ - + + ==== //depot/projects/docproj_nl/en_US.ISO8859-1/articles/portbuild/article.sgml#21 (text+ko) ==== @@ -11,7 +11,7 @@ The &os; Ports Management Team - $FreeBSD: doc/en_US.ISO8859-1/articles/portbuild/article.sgml,v 1.51 2010/01/26 03:24:58 linimon Exp $ + $FreeBSD: doc/en_US.ISO8859-1/articles/portbuild/article.sgml,v 1.54 2010/02/19 16:12:58 linimon Exp $ 2003 @@ -204,6 +204,19 @@ (8-exp branch) + + + dopackages.9 - Perform + a 9.X build + + + + + dopackages.9-exp - Perform + a 9.X build with experimental patches + (9-exp branch) + + These are wrappers around dopackages, @@ -1005,7 +1018,8 @@ Experimental patches builds are run from time to time to new features or bugfixes to the ports infrastructure (i.e. bsd.port.mk), or to test large sweeping - upgrades. The current experimental patches branch is + upgrades. At any given time there may be several simultaneous + experimental patches branches, such as 8-exp on the amd64 architecture. @@ -1971,6 +1985,10 @@ + mkdir lockfiles + + + ln ../make.conf ./make.conf @@ -1979,8 +1997,12 @@ - (Apparently no longer needed?) Create - pnohang.arch. + Create + pnohang.arch. + (The easiest way may be to do the following on a client, and + then copy it back): + cc pnohang.c -o pnohang-arch + @@ -2030,9 +2052,23 @@ - In the /var/portbuild/errorlogs/ - directory, create one more link for the webserver: -ln -s ../arch/archive/buildlogs arch-buildlogs + As with the procedure for creating a new branch: + in the /var/portbuild/errorlogs/ + directory, create links for the webserver: +ln -s ../arch/branch/builds/latest/bak/errors arch-branch-full +ln -s ../arch/branch/builds/latest/bak/logs arch-branch-full-logs +ln -s ../arch/branch/builds/latest/errors arch-branch-latest +ln -s ../arch/branch/builds/latest/logs arch-branch-latest-logs +ln -s ../arch/branch/builds/latest/bak/packages arch-branch-packages-full +ln -s ../arch/branch/builds/latest/packages arch-branch-packages-latest + + + + + In that + directory, create two more links for the webserver: +ln -s ../arch/archive/buildlogs arch-buildlogs +ln -s ../arch/archive/errorlogs arch-errorlogs ==== //depot/projects/docproj_nl/en_US.ISO8859-1/articles/version-guide/article.sgml#3 (text+ko) ==== @@ -21,7 +21,7 @@ - $FreeBSD: doc/en_US.ISO8859-1/articles/version-guide/article.sgml,v 1.13 2008/06/20 20:46:25 gabor Exp $ + $FreeBSD: doc/en_US.ISO8859-1/articles/version-guide/article.sgml,v 1.15 2010/02/19 21:33:18 jhb Exp $ &tm-attrib.freebsd; @@ -258,13 +258,9 @@ more bugs by doing so is much less. Also, by focusing on a time deadline rather than a - feature set, it should be finally be possible for users, developers + feature set, it should finally be possible for users, developers of external applications, and the &os; developers themselves to be able to better plan for the future. - - These considerations, rather than any kind of keeping up with - the major release number of any other OS, comprise the main motivation for - the scheduling changes going forward. ==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/developers-handbook/x86/chapter.sgml#4 (text+ko) ==== @@ -15,7 +15,7 @@ author to assign us the copyright. For now, it is valuable content so it should stay. - $FreeBSD: doc/en_US.ISO8859-1/books/developers-handbook/x86/chapter.sgml,v 1.17 2009/07/13 07:37:11 blackend Exp $ + $FreeBSD: doc/en_US.ISO8859-1/books/developers-handbook/x86/chapter.sgml,v 1.18 2010/02/17 18:20:32 jhb Exp $ --> @@ -249,7 +249,7 @@ linked, you need to brand the executable: -&prompt.user; brandelf -f Linux filename +&prompt.user; brandelf -t Linux filename ==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/security/chapter.sgml#13 (text+ko) ==== @@ -1,7 +1,7 @@ @@ -330,7 +330,7 @@ You can do this by editing your /etc/ssh/sshd_config file, and making sure that PermitRootLogin is set to - NO. Consider every access method — + no. Consider every access method — services such as FTP often fall through the cracks. Direct root logins should only be allowed via the system console. ==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/porters-handbook/book.sgml#73 (text+ko) ==== @@ -1,7 +1,7 @@ sigpause(3). + 800503 + February 25, 2010 + 8.0-STABLE after addition of SIOCGIFDESCR + and SIOCSIFDESCR ioctls to network interfaces. These + ioctl can be used to manipulate interface description, + as inspired by OpenBSD. + + 900000 August 22, 2009 9.0-CURRENT. ==== //depot/projects/docproj_nl/en_US.ISO8859-1/captions/2009/asiabsdcon/rao-kernellocking-2.sbv#2 (text+ko) ==== @@ -1,8 +1,8 @@ 0:00:00.530,0:00:01.590 -So, basically, +So basically, 0:00:04.590,0:00:10.029 -we are going to look mainly in this second part +we are going to look, mainly in this second part, at how to 0:00:10.029,0:00:11.519 @@ -15,32 +15,32 @@ that categorize in the kernel. 0:00:17.910,0:00:24.410 -Here there are described two kinds of problems -you can get with locks, that are pretty much common +Here, there are described two kinds of problems +you can get with locks, that are pretty much common. 0:00:24.410,0:00:27.859 -The first one is called Lock Order Reversal +The first one is called Lock Order Reversal (LOR). 0:00:27.859,0:00:30.140 -when you have for example a thread A +When you have for example a thread A, 0:00:30.140,0:00:32.340 which owns 0:00:32.340,0:00:35.870 -a lock code, for example, L1 +a lock code, for example L1 0:00:35.870,0:00:37.920 and another thread B 0:00:37.920,0:00:40.070 -which owns another lock, L2 +which owns the lock, L2 0:00:40.070,0:00:43.150 -Then thread A tries to +Then thread A tries to.. 0:00:43.150,0:00:44.730 -Right, it's wrong. +Right.. it's wrong. 0:00:44.730,0:00:46.220 The slide is wrong. @@ -96,7 +96,7 @@ locks should maintain 0:01:32.910,0:01:34.319 -an ordering regard of each other. +an ordering in regard of each other. 0:01:34.319,0:01:38.859 That's not very simple when @@ -110,25 +110,26 @@ 0:01:44.850,0:01:49.180 is going to count because you can -never mix two different kinds of locks +never mix two different kinds of locks. 0:01:49.180,0:01:50.680 -for example +For example 0:01:50.680,0:01:51.610 -a spin lock +a spinlock 0:01:51.610,0:01:53.770 -and a mutex. +and a mutex 0:01:53.770,0:01:59.120 -You can mix in this way. +can be mixed in this way. 0:01:59.120,0:02:01.720 - +You can have the mutex first and the spinlock later, +while the opposite is not actually true. 0:02:01.720,0:02:07.060 -So, you will see that this kind +So, you will see that these kind of deadlocks are possible 0:02:07.060,0:02:09.290 @@ -141,26 +142,26 @@ or such. 0:02:14.569,0:02:16.090 -Um... + 0:02:16.090,0:02:17.409 -Also +Also, 0:02:17.409,0:02:19.949 -Even if it's not very well documented, +even if it's not very well documented, 0:02:19.949,0:02:22.880 -for example, spin locks, +for example spinlocks 0:02:22.880,0:02:26.599 -in previous deep, as a way to +in FreeBSD, have a way to identify such kind of deadlocks. 0:02:26.599,0:02:27.619 -And it's pretty much implemented... +And it's pretty much implemented. 0:02:27.619,0:02:29.709 -a very much in it would + 0:02:29.709,0:02:32.449 It's a feature enabled in the code. @@ -178,7 +179,7 @@ an exaggerated result, 0:02:41.379,0:02:47.870 -it means that they are probable +it means that they are probably under a deadlock and the system panics. 0:02:47.870,0:02:52.489 @@ -224,7 +225,7 @@ sleeping on this wait channel 0:03:30.569,0:03:34.589 -and nobody is going to wake up them again. +and nobody is going to wake them up again. 0:03:34.589,0:03:37.629 This is usually called missed wakeup @@ -240,10 +241,10 @@ 0:03:46.719,0:03:52.109 it's very difficult to differentiate -between missed wakeup and, +between missed wakeup and 0:03:52.109,0:03:53.480 -for example, +for example 0:03:53.480,0:03:56.189 forever sleep @@ -256,7 +257,7 @@ 0:04:01.859,0:04:07.109 So these kind of deadlocks are -very difficult to be discovered +very very difficult to be discovered 0:04:07.109,0:04:11.669 and will require some bit of @@ -278,7 +279,7 @@ and some things integrated into the debugger. 0:04:22.240,0:04:22.979 -Um, + 0:04:22.979,0:04:25.520 In FreeBSD, @@ -292,7 +293,7 @@ 0:04:32.080,0:04:36.539 The first one (and the most important) -is called witness. +is called WITNESS. 0:04:36.539,0:04:39.169 It was introduced @@ -301,7 +302,7 @@ in the context of SMPng 0:04:42.080,0:04:44.979 -and has been written in the recent past, +and has been rewritten in the recent past, 0:04:44.979,0:04:47.919 mainly by a contribution of @@ -313,7 +314,7 @@ They contributed back then 0:04:52.270,0:04:54.989 -to the writing of witness. +to the writing of WITNESS. 0:04:54.989,0:04:57.389 This subsystem is very important @@ -322,7 +323,7 @@ because it tracks down exactly every order 0:05:02.730,0:05:03.949 -of the locks +of the locks. 0:05:03.949,0:05:07.810 So that, if there is an ordering violation like a LOR, @@ -356,7 +357,7 @@ we can identify 0:05:36.539,0:05:38.419 -deadlocks possible +deadlocks, possibly 0:05:38.419,0:05:39.500 even @@ -368,7 +369,7 @@ reader's path. 0:05:45.529,0:05:49.609 -We could say that witness is pretty big, +We could say that WITNESS is pretty big, 0:05:49.609,0:05:52.289 so activating it @@ -381,10 +382,10 @@ develop a new feature in the kernel 0:05:59.929,0:06:02.110 -and you are going to test it heavily, +and you are going to test it heavily. 0:06:02.110,0:06:05.479 -in particular if it has +In particular if it has 0:06:05.479,0:06:06.819 some @@ -393,7 +394,7 @@ relation to locking. 0:06:10.509,0:06:13.089 -Uh, + 0:06:13.089,0:06:17.840 We could also tell that with the new code @@ -403,10 +404,10 @@ basically 0:06:19.150,0:06:21.689 -the orad + 0:06:21.689,0:06:25.479 -offered by witness is greatly reduced to about +offered by WITNESS is greatly reduced to about 0:06:25.479,0:06:27.699 the 10th part of @@ -415,7 +416,7 @@ what we had before. 0:06:30.240,0:06:36.150 -Witness is very good at tracking LOR, +WITNESS is very good at tracking LOR, 0:06:36.150,0:06:37.849 but @@ -448,7 +449,7 @@ basically 0:06:58.879,0:07:04.159 -and basically, it's in the 8th release, +it's in the 8th release, we have new features 0:07:04.159,0:07:05.759 @@ -467,18 +468,18 @@ and 0:07:17.549,0:07:23.550 -and shows some graphs of the relations. -Even from the user space, +it shows some graphs of the relations +even from the user space. 0:07:23.550,0:07:28.550 -you don't have to go into the kernel -degubber to look at it's output. +You don't have to go into the kernel +debugger to look at it's output. 0:07:28.550,0:07:35.550 -Well + 0:07:35.620,0:07:37.380 -... + 0:07:37.380,0:07:42.250 Well, I see that sometimes when @@ -507,36 +508,36 @@ is in the kernel. 0:07:59.590,0:08:02.490 -... + 0:08:02.490,0:08:03.389 Usually, 0:08:03.389,0:08:07.939 if you want to find a deadlock -that's happening in the kernel +that's happening in the kernel, 0:08:07.939,0:08:10.909 -your first line of analysis start from the DDB +your first line of analysis starts from the DDB 0:08:10.909,0:08:13.919 instead of a post-mortem analysis, 0:08:13.919,0:08:16.839 -which is even more important, +which is even more important. 0:08:16.839,0:08:22.330 -but using DDB you will get more +But, using DDB you will get more processes and better information. 0:08:22.330,0:08:24.970 -Uh, + 0:08:24.970,0:08:28.499 The most important unit in order to find the deadlock 0:08:28.499,0:08:34.389 -are the LORs reported by witness in order +are the LORs reported by WITNESS in order to see if there is something strange 0:08:34.389,0:08:36.690 @@ -547,10 +548,10 @@ that are running on the system that is deadlocking. 0:08:41.700,0:08:42.900 -... + 0:08:42.900,0:08:47.050 -You can see that you're deadlocking if you see that +You can see that you're deadlocking, if you see that 0:08:47.050,0:08:48.070 on the runqueue @@ -570,21 +571,21 @@ in their own containers. 0:09:02.450,0:09:07.850 -You need to know which are exactly locks +You need to know which are the exact locks that are acquired 0:09:07.850,0:09:11.270 in the system 0:09:11.270,0:09:15.570 -and that's something that witness provides, +and that's something that WITNESS provides 0:09:15.570,0:09:20.720 -and the very important things is +and the very important thing is to know why the threads are stopping. 0:09:20.720,0:09:24.250 -So one on the most important things is +So one of the most important things is retrieving what the threads were doing 0:09:24.250,0:09:26.320 @@ -594,13 +595,13 @@ they were put asleep. 0:09:28.960,0:09:30.070 -... + 0:09:30.070,0:09:33.009 The backtraces of all the threads involved 0:09:33.009,0:09:37.130 -are so printed out in order to identify deadlocks. +are printed out in order to identify deadlocks. 0:09:37.130,0:09:38.589 In the case that @@ -609,13 +610,13 @@ buffered cache and VFS are 0:09:42.830,0:09:45.910 -probably parts of the deadlocking +probably parts of the deadlocking, 0:09:45.910,0:09:50.790 you should also print out 0:09:50.790,0:09:53.420 -the info about vnodes +the information about vnodes 0:09:53.420,0:09:58.250 and what we're interested in is which vnodes are called, @@ -630,10 +631,10 @@ and 0:10:03.530,0:10:10.530 -which way they were called. +in which way they were called. 0:10:11.030,0:10:13.380 -So +So, 0:10:13.380,0:10:15.770 this is an example @@ -648,7 +649,7 @@ in the case of a deadlock. 0:10:20.760,0:10:27.480 -This is an example of a real deadlock +This is an real example of a deadlock 0:10:27.480,0:10:28.900 but you can see @@ -663,10 +664,10 @@ But you can see that all the threads are sleeping. 0:10:38.450,0:10:39.870 -Uh... + 0:10:39.870,0:10:43.580 -And this one is the message +This one is the message 0:10:43.580,0:10:44.790 used by the wait channel @@ -678,7 +679,7 @@ or used by 0:10:48.710,0:10:54.480 -the container like the turnsile or the sleep queue. +the container like the turnstile or the sleepqueue. 0:10:54.480,0:10:59.410 If I recall correctly, it's a forced amount @@ -688,7 +689,7 @@ I'm not really sure 0:11:01.290,0:11:04.190 -because I have to take a look at it. +because I should have looked at it. 0:11:04.190,0:11:08.810 You can see that the revelant command here @@ -698,7 +699,7 @@ that DDB supports. 0:11:11.220,0:11:14.220 -Um, + 0:11:14.220,0:11:17.520 Another important thing @@ -716,43 +717,39 @@ usually 0:11:25.210,0:11:31.600 -is because you can add some data structures corrupted +its because you can add some data structures corrupted 0:11:31.600,0:11:34.320 in the per-CPU datas. 0:11:34.320,0:11:38.830 -That's a very common situation when you get deadlocks, +That's a very common situation where you can get deadlocks, 0:11:38.830,0:11:40.280 -because, for example, +because, for example, 0:11:40.280,0:11:43.149 leaving a corrupted LPD will lead -0:11:43.149,0:11:48.750 -I loved you too much review shellacking double -falls and things like that about that - 0:11:48.750,0:11:55.290 to you having a bigger massive breakage like -double-faults. In general. it's a good idea to -look at all the CPUs involved in the system. +double-faults and things like that. Usually it's always a +good idea to look at all the CPUs involved in the system. 0:11:55.290,0:11:57.310 The command 0:11:57.310,0:12:00.120 -is ""show allpcpu"" +is """"-show allpcpu"". 0:12:00.120,0:12:04.960 -Um, + 0:12:04.960,0:12:06.959 This one 0:12:06.959,0:12:12.009 -this one is a witness specific command -show alllocks +is a WITNESS specific command ""-show alllocks"" and it's going to show all the locks, 0:12:12.009,0:12:13.130 @@ -771,7 +768,7 @@ and the thread is this one, 0:12:21.270,0:12:23.660 -what lock is holding, +what the lock is holding, 0:12:23.660,0:12:24.970 that's the address @@ -783,7 +780,7 @@ It gives you lines and file. 0:12:31.140,0:12:32.770 -... + 0:12:32.770,0:12:34.730 Actually, @@ -792,7 +789,7 @@ that's just possible 0:12:37.620,0:12:40.859 -with witness, because otherwise, +with WITNESS, because otherwise, 0:12:40.859,0:12:44.410 trying to keep the oldest information @@ -806,13 +803,13 @@ the backtrace for any thread. 0:12:59.730,0:13:01.150 -... + 0:13:01.150,0:13:03.390 It's going to show the backtrace 0:13:03.390,0:13:05.700 >>> TRUNCATED FOR MAIL (1000 lines) <<<