From owner-freebsd-current@FreeBSD.ORG Thu Jan 24 13:12:24 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D310E16A418 for ; Thu, 24 Jan 2008 13:12:24 +0000 (UTC) (envelope-from swhetzel@gmail.com) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.153]) by mx1.freebsd.org (Postfix) with ESMTP id 5FB4813C45D for ; Thu, 24 Jan 2008 13:12:23 +0000 (UTC) (envelope-from swhetzel@gmail.com) Received: by fg-out-1718.google.com with SMTP id 16so249495fgg.35 for ; Thu, 24 Jan 2008 05:12:22 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=pqpGIfJ97k76+dCvY4TTEAadw8k8fziuBiAGUboKPx8=; b=qSVKW+SVvyca4jUSfTTjgXl3gY7r3yhP22RPMOAT1VpOunQ1rg4PPEFTAkR9MNEKIQEwTHCt3nBbbXt4yLNLY6D0Uke4sPjDV9zorhuU1+t1ivo2TBXA+qWGpPEuqlGkyoFUy9hRGk1XjN8omr5OnKy0YGuNi7TwRwmGp68iaZE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=HqEFz1BDtyFzgu4WKqRUtymeYoo5eJEw2VJH497w4hITQp8Ds8KlFDLYgCuRMpCdWHqkA/5YCpkAf7napLFfBoE49Kylga4HjUBn7JFRMJnA5m7326lDv95ZOJ3JA+A31V7dT5/IllmhJJcezOIVz39+ZZScMFbPEviXTiBED9M= Received: by 10.86.51.2 with SMTP id y2mr580405fgy.56.1201180342812; Thu, 24 Jan 2008 05:12:22 -0800 (PST) Received: by 10.86.99.17 with HTTP; Thu, 24 Jan 2008 05:12:22 -0800 (PST) Message-ID: <790a9fff0801240512m1a43fee6s12fcb164f4be1f7c@mail.gmail.com> Date: Thu, 24 Jan 2008 07:12:22 -0600 From: "Scot Hetzel" To: "Yar Tikhiy" In-Reply-To: <20080124122808.GA15600@freefall.freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <790a9fff0801150552l542a4238ofc12efe5fdb45fc2@mail.gmail.com> <20080115143924.GB57756@deviant.kiev.zoral.com.ua> <20080124122808.GA15600@freefall.freebsd.org> Cc: Kostik Belousov , Attilio Rao , freebsd-current@freebsd.org Subject: Re: panic: System call lstat returning with 1 locks held X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 24 Jan 2008 13:12:24 -0000 On Jan 24, 2008 6:28 AM, Yar Tikhiy wrote: > On Tue, Jan 15, 2008 at 04:39:24PM +0200, Kostik Belousov wrote: > > > > I think this could be related to the recent vn_lock()/VOP_LOCK() KPI changes. > > Please, add DEBUG_VFS_LOCKS to the kernel config, and do the > > show lockedvnods > > from the ddb prompt when the panic occurs. The witness does not track > > the lockmgr locks. > > I think I'm seeing the same panic on UFS. It's rather nasty: I > cannot rebuild CURRENT natively due to it so I have to build it > under 6-STABLE. My favourite way to trigger the panic reliably is > running `make install' in a simple port directory, e.g., portmaster, > but my system also panics during daily scripts run and, as already > said, if trying to build world. > Try backing the -CURRENT sources to "Jan 08 23:45 UTC 2008", and then rebuild/install the kernel. This is the point before the vn_lock/VOP_LOCK changes. Reboot your system and perform your steps that caused the lstat panic (this kernel shouldn't give the lstat panic). Create a backup of this kernel: cd /boot cp -rp kernel kernel_good Then try building/installing a kernel from the -CURRENT sources that have been updated to "Jan 08 23:49 UTC 2008". Reboot and try the same steps again, this kernel should give the lstat panic. After it panics, just reboot, break into the boot loader, then do: unload boot kernel_good Then either copy kernel_good to kernel or add the following to /boot/loader.conf: kernel="kernel_good" Scot