From owner-freebsd-current@FreeBSD.ORG Wed Feb 13 16:41: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 A2D0D16A420 for ; Wed, 13 Feb 2008 16:41:24 +0000 (UTC) (envelope-from stas@ht-systems.ru) Received: from smtp.ht-systems.ru (mr0.ht-systems.ru [78.110.50.55]) by mx1.freebsd.org (Postfix) with ESMTP id 624E413C459 for ; Wed, 13 Feb 2008 16:41:23 +0000 (UTC) (envelope-from stas@ht-systems.ru) Received: from [78.110.49.49] (helo=quasar.ht-systems.ru) by smtp.ht-systems.ru with esmtpa (Exim 4.62) (envelope-from ) id 1JPK6T-0002q2-B2 for freebsd-current@FreeBSD.org; Wed, 13 Feb 2008 19:04:57 +0300 Received: by quasar.ht-systems.ru (Postfix, from userid 1024) id 370127D1002; Wed, 13 Feb 2008 19:04:56 +0300 (MSK) Date: Wed, 13 Feb 2008 19:04:56 +0300 From: Stanislav Sedov To: freebsd-current@FreeBSD.org Message-ID: <20080213160456.GA13484@dracon.ht-systems.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Organization: The FreeBSD Project X-Voice: +7 916 849 20 23 X-XMPP: ssedov@jabber.ru X-Yahoo: stanislav_sedov X-PGP-Fingerprint: F21E D6CC 5626 9609 6CE2 A385 2BF5 5993 EB26 9581 X-University: MEPhI X-Mailer: carrier-pigeon X-Operating-System: FreeBSD quasar.ht-systems.ru 7.0-BETA2 FreeBSD 7.0-BETA2 Cc: Subject: dump(8) hangup on RC2 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: Wed, 13 Feb 2008 16:41:24 -0000 Hi! I recently installed the RC2 snapshot and discovered an interesting problem: dump utility frequently hangs up independently from what and where it dumps. Several other people also reported the same problem. When the hangup occurs, the main dump process freezes in the state sbwait, awaiting some input from child proceesses, wheere the last ones hangs in 'pause' state. It looks like some signal problem, though I'm not sure. Does anyone have any suggestion what it can be or how to debug that? It seems that at least BETA2 isn't affected by this problem. I tried to use ktrace to find something, but can't see anything wrong in its output. Thanks! -- Stanislav Sedov ST4096-RIPE