From owner-freebsd-current@FreeBSD.ORG Wed Jan 21 21:10:22 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 459AF16A4CE for ; Wed, 21 Jan 2004 21:10:22 -0800 (PST) Received: from electra.cse.Buffalo.EDU (electra.cse.Buffalo.EDU [128.205.32.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id AD46343D1D for ; Wed, 21 Jan 2004 21:10:20 -0800 (PST) (envelope-from kensmith@cse.Buffalo.EDU) Received: from electra.cse.Buffalo.EDU (kensmith@localhost [127.0.0.1]) i0M5AKTr012075; Thu, 22 Jan 2004 00:10:20 -0500 (EST) Received: (from kensmith@localhost) by electra.cse.Buffalo.EDU (8.12.10/8.12.9/Submit) id i0M5AH5v012073; Thu, 22 Jan 2004 00:10:17 -0500 (EST) Date: Thu, 22 Jan 2004 00:10:17 -0500 From: Ken Smith To: Kris Kennaway Message-ID: <20040122051017.GA11853@electra.cse.Buffalo.EDU> References: <20040121182730.GB40652@xor.obsecurity.org> <20040121183959.GA25589@electra.cse.Buffalo.EDU> <20040121184307.GA41138@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040121184307.GA41138@xor.obsecurity.org> User-Agent: Mutt/1.4.1i cc: "Robin P. Blanchard" cc: Ken Smith cc: current@freebsd.org Subject: Re: Strange behaviour X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Jan 2004 05:10:22 -0000 On Wed, Jan 21, 2004 at 10:43:07AM -0800, Kris Kennaway wrote: > OK, sounds like it might be something to do with vnode locking. > Turning on DEBUG_VFS_LOCKS might help to find it. I turned that on but it doesn't seem to have given any more clues. The machine is (recently...) attached to a serial console, no extra messages. At the time I did it the only net traffic would have been my login session (watching with top) so odds are it's just the disk I/O causing it. Amongst other things I've got: # Debugging for use in -current options DDB #Enable the kernel debugger options INVARIANTS #Enable calls of extra sanity checking options INVARIANT_SUPPORT #Extra sanity checks of internal structures, required by INVARIANTS options WITNESS #Enable checks to detect deadlocks and cycles #options WITNESS_SKIPSPIN #Don't run witness on spinlocks for speed options DEBUG_VFS_LOCKS Otherwise it's a more or less GENERIC config file. As an earlier attempt I did try turning off acpi with this in /boot/loader.conf: hint.acpi.0.disabled="1" The machine is up and running right now with several wedged find processes: perseus 13 % ps alxww | grep find 0 1425 1 69 -4 0 1316 836 getblk D p0- 0:13.09 find / -name foo -print 0 1426 1 115 -4 0 1316 836 ufs D p0- 0:11.74 find / -name foo -print 0 1427 1 105 -4 0 1316 836 ufs D p0- 0:11.77 find / -name foo -print 0 1428 1 112 -4 0 1316 836 getblk D p0- 0:11.54 find / -name foo -print 0 1429 1 89 -4 0 1316 836 getblk D p0- 0:11.22 find / -name foo -print perseus 14 % Given the DDB config info above is there anything I can do to give you more information? -- Ken Smith - From there to here, from here to | kensmith@cse.buffalo.edu there, funny things are everywhere. | - Theodore Geisel |