From owner-freebsd-current@FreeBSD.ORG Tue Mar 5 19:34:48 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 68289D8E; Tue, 5 Mar 2013 19:34:48 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) by mx1.freebsd.org (Postfix) with ESMTP id 0DE36916; Tue, 5 Mar 2013 19:34:47 +0000 (UTC) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost1.zedat.fu-berlin.de (Exim 4.80.1) with esmtp (envelope-from ) id <1UCxdO-0008ws-VV>; Tue, 05 Mar 2013 20:34:47 +0100 Received: from e178002055.adsl.alicedsl.de ([85.178.2.55] helo=munin.geoinf.fu-berlin.de) by inpost2.zedat.fu-berlin.de (Exim 4.80.1) with esmtpsa (envelope-from ) id <1UCxdO-002KCY-Sv>; Tue, 05 Mar 2013 20:34:46 +0100 Message-ID: <51364914.2010104@zedat.fu-berlin.de> Date: Tue, 05 Mar 2013 20:35:48 +0100 From: "Hartmann, O." Organization: FU Berlin User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130216 Thunderbird/17.0.2 MIME-Version: 1.0 To: FreeBSD Current Subject: r247839: broken pipe - for top, sudo and ports References: <5135B7E1.3050002@zedat.fu-berlin.de> <5135BBD9.9090009@FreeBSD.org> In-Reply-To: <5135BBD9.9090009@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Originating-IP: 85.178.2.55 Cc: Dimitry Andric X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 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, 05 Mar 2013 19:34:48 -0000 On recent FreeBSD 10.0-CURRENT/amd64 (CLANG buildworld, serveral systems (3) the same symptoms)), many services drop a sporadic broken pipe This happesn to system's top (I have to type it several times to get finally a top), it happens to "sudo su -", it happens to SSH (drops connection with broken pipe) and as I reported earlier, it seems to affect the entire port system, since I can not build any port, I receive *** [do-extract] Signal 13 This is dramatic for me, because several modules (rtc, linux_adobe ...) can not be recompiled as it is required by the last /usr/src/UPDATING entry 20130304. Since dbus fails to start and even the nVidia driver (which is a kernel module, it canot be built and therefore ... ). Dimitry, I put you into CC, just in case. It seems that the last commits (not only the new DRM2 mess) broke something. I hope that others using FreeBSD 10.0CURRENT with CLANG can confirm this. Regards, Oliver On 03/05/13 10:33, Dimitry Andric wrote: > On 2013-03-05 10:16, Hartmann, O. wrote: >> On FreeBSD 10.0-CURRENT #3 r247829: Tue Mar 5 08:12:19 CET 2013/amd64 I >> run into a mess and can not figure out what happens. >> >> Suddenly, after upgrading, buildworld etc., dbus fails to start so X11 >> is without mouse. >> >> Trying to rebuild the port dbus fails in a SIGNAL 13 while [do-extract]. >> >> This is weird. I can not extract and rebuild ports anymore, every port I >> try to rebuild with portmaster fails with the very same fault: >> >> => SHA256 Checksum OK for dbus-1.4.14.tar.gz. >> *** [do-extract] Signal 13 > > This is SIGPIPE, so maybe your tar is broken? What happens if you > manually extract that tar.gz file?