From owner-freebsd-stable@FreeBSD.ORG Sun Dec 8 19:38:44 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C22E2C87 for ; Sun, 8 Dec 2013 19:38:44 +0000 (UTC) Received: from mail-we0-x232.google.com (mail-we0-x232.google.com [IPv6:2a00:1450:400c:c03::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 4E525194E for ; Sun, 8 Dec 2013 19:38:44 +0000 (UTC) Received: by mail-we0-f178.google.com with SMTP id u57so2562889wes.23 for ; Sun, 08 Dec 2013 11:38:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=rG2YMo0lDJ1BOQ/kPzrfhRhJ6kpwE9A6XrFtCxakYAI=; b=L0M1/Vrgg6dD1WOfUJrTeQFCE4utbtmDSQlYTRSZO5IEYIuB+BdlVPmJJ2vLWRLj7l SHvDb9O9hSWi7RQDM+YplWKyqDnxx1HQG/kvihrZIimdqf1xSVUUNLjNoXKkNAJWuYFk zzSqbqY4kmxFuBiLTZGElGPI4O2LpeImitS0Evd8vTWauGeRnuyjslltkFocA6QY33c4 ljzl8JKWrji/33Nk6ma3hKkECjAMolJRefZIibmM3YKK3U/Mjhx3+hXrtujRKNVUjKSz dv64HR+R3ATwvwuLLgnRJThML9h/emZTy2ElU1AAZN7RmHnmWdLa8KE24dgFmScHhw0A zuIA== MIME-Version: 1.0 X-Received: by 10.194.170.133 with SMTP id am5mr11794030wjc.42.1386531522750; Sun, 08 Dec 2013 11:38:42 -0800 (PST) Received: by 10.217.89.138 with HTTP; Sun, 8 Dec 2013 11:38:42 -0800 (PST) In-Reply-To: <20131207183044.GA19655@x2.osted.lan> References: <20131206201329.GK59496@kib.kiev.ua> <20131207183044.GA19655@x2.osted.lan> Date: Sun, 8 Dec 2013 21:38:42 +0200 Message-ID: Subject: Re: stable/10 r258317 - UFS lock problem From: =?ISO-8859-1?Q?=D6zkan_KIRIK?= To: Peter Holm Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: Konstantin Belousov , freebsd-stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Dec 2013 19:38:44 -0000 Hi, You're right Peter. Now i am compiling with DDB option. But http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kernel= debug-deadlocks.html page, dont tell about the "DDB" option. Thank you, On Sat, Dec 7, 2013 at 8:30 PM, Peter Holm wrote: > On Sat, Dec 07, 2013 at 08:24:32AM +0200, =D6zkan KIRIK wrote: > > Hi, > > > > I'm trying to compile a debug kernel with these options : > > > > makeoptions DEBUG=3D-g > > options INVARIANTS > > options INVARIANT_SUPPORT > > options WITNESS > > options DEBUG_LOCKS > > options DEBUG_VFS_LOCKS > > options DIAGNOSTIC > > > > While compiling; compilations fails due to this error : > > /usr/src/sys/kern/subr_vmem.c:1357:1: error: unused function 'vmem_dump= ' > > [-Werror, -Wunused-function] > > > > Did you forget "options DDB" ? > > - Peter > > > > > I'll comment out this function and recompiled kernel. > > Now, while booting, kernel panics. Error line is below; KDB stack > > backtrace is attached as PNG screenshot. > > > > "panic: mtx_lock_spin: recursed on non-recursive mutex cnput_mtx @ > > /usr/src/sys/kern/kern_cons.c:500" > > > > I think, i hit an other bug. > > > > Best wishes, > > > > Ozkan KIRIK > > ePati Information Technologies > > http://www.epati.com.tr/ > > > > > > On Fri, Dec 6, 2013 at 10:13 PM, Konstantin Belousov < > kostikbel@gmail.com>wrote: > > > > > On Fri, Dec 06, 2013 at 08:10:55PM +0200, ?zkan KIRIK wrote: > > > > Hi, > > > > > > > > I am using FreeBSD 10.0-BETA3 r258317 GENERIC kernel. > > > > > > > > I run "portsnap fetch extract". > > > > While extracting files, extracting operation hangs, and i cant kill > > > process. > > > > > > > > Output of : "ps ax | grep D+" ( uninterruptable process list ) > > > > % ps ax | grep D+ > > > > 28933 0 D+ 0:00.01 tar -xz --numeric-owner -f > > > > > > > > /var/db/portsnap/files/77d41f10d2832f8450e4e02a4db5c0a6131c97d15076ed0c76= e761c9ce58338d.gz > > > > -C /usr/ports/emulators/qemu/ (bsdtar) > > > > 29051 1 S+ 0:00.00 grep D+ > > > > % > > > > > > > > > > > > Because of D flag, process cannot be interrupted even by SIGKILL. > > > > I cannot remove usr/ports folder while this process on D+ state. > > > > If I run rm -r /usr/ports, rm process is flagged as D+ also. > > > > > > > > I tested this situation on both vmware workstation and different re= al > > > > hardware installations. ( Sun Fire X4150, HP DL380G4, Sun X3 > servers. ) > > > > > > > > Problem is repeatable. If you install FreeBSD on ZFS root, problem > > > doesn't > > > > occur. > > > > > > > > > > > > # mount > > > > /dev/da0p2 on / (ufs, local, journaled soft-updates) > > > > devfs on /dev (devfs, local, multilabel) > > > > > > See > > > > > > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kern= eldebug-deadlocks.html > > > > > _______________________________________________ >