From owner-freebsd-current@FreeBSD.ORG Tue May 3 14:42:55 2011 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 1E6781065674 for ; Tue, 3 May 2011 14:42:55 +0000 (UTC) (envelope-from bsam@ipt.ru) Received: from services.ipt.ru (services.ipt.ru [194.62.233.110]) by mx1.freebsd.org (Postfix) with ESMTP id C90478FC1A for ; Tue, 3 May 2011 14:42:54 +0000 (UTC) Received: from bb.ipt.ru ([194.62.233.89]) by services.ipt.ru with esmtps (TLSv1:AES128-SHA:128) (Exim 4.54 (FreeBSD)) id 1QHGoP-000ITB-3n for freebsd-current@FreeBSD.org; Tue, 03 May 2011 18:42:53 +0400 From: Boris Samorodov To: freebsd-current@FreeBSD.org Date: Tue, 03 May 2011 18:42:52 +0400 Message-ID: <00959411@bb.ipt.ru> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Subject: a process waits forever 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: Tue, 03 May 2011 14:42:55 -0000 Hi, I've got a problem which I harly can explain. Latest CURRENT built with gcc and clang suffers. Both hosts with CURRENT I have an access to has this problem. The most clean way to reproduce the error (for me) is to reload (sometimes once or twice, sometimes more, but not more than a dozen) current and latest builds at my local tinderbox. Firefox (I use FF4) reloads the page (it's seen since time counter is updated) shows "X" with red foreground instead of a reload sign at the very end of an URL window. The next symptom is using gsasl within emacs (gnus). Sometimes communication between gnus and an imap server stops. The only way to resume operations is to do "killall gsasl". BTW, a gsasl process is at a "select" state. Sometimes gnus displays something like "garbage received, enter RET to continue". I never managed to reproduce the bug by a script (i.e. fetching the problem URL 100 times succeeds). And I'm not sure how to diagnose the case further. Any suggestions? Thanks! -- WBR, Boris Samorodov (bsam) Research Engineer, http://www.ipt.ru Telephone & Internet SP FreeBSD Committer, http://www.FreeBSD.org The Power To Serve