From owner-freebsd-hackers@FreeBSD.ORG Sun Dec 7 13:25:20 2014 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 8CBF314A; Sun, 7 Dec 2014 13:25:20 +0000 (UTC) Received: from puchar.net (puchar.net [188.252.31.250]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "puchar.net", Issuer "puchar.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 1B9EF131; Sun, 7 Dec 2014 13:25:19 +0000 (UTC) Received: Received: from 127.0.0.1 (localhost [127.0.0.1]) by puchar.net (8.14.9/8.14.9) with ESMTP id sB7DPFH0068337; Sun, 7 Dec 2014 14:25:15 +0100 (CET) (envelope-from wojtek@puchar.net) Date: Sun, 7 Dec 2014 14:25:11 +0100 (CET) From: Wojciech Puchar X-X-Sender: wojtek@laptop To: Lev Serebryakov Subject: Re: 10.1-STABLE one week old from svn - random hangs In-Reply-To: <54843BB3.2000602@FreeBSD.org> Message-ID: References: <54843BB3.2000602@FreeBSD.org> User-Agent: Alpine 2.11 (BSF 23 2013-08-11) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (puchar.net [10.0.1.1]); Sun, 07 Dec 2014 14:25:15 +0100 (CET) Cc: FreeBSD Hackers X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Dec 2014 13:25:20 -0000 >> >> seems like a deadlock. Anyone know that problem. How to trace it >> down? > Looks like I have same problem sometimes. And you could not run any > new process, you could not login on console, but you could switch > virtual consoles & if "top" is running on one of them, it doesn't hang > itself, right? yes. ping works. all hanged process waits for I/O infinitely. no I/O is going. strange sometimes it does not happen WHILE performing heavy I/O, but after. some kind of deadlock.