Date: Tue, 05 Mar 2013 20:35:48 +0100 From: "Hartmann, O." <ohartman@zedat.fu-berlin.de> To: FreeBSD Current <freebsd-current@freebsd.org> Cc: Dimitry Andric <dim@FreeBSD.org> Subject: r247839: broken pipe - for top, sudo and ports Message-ID: <51364914.2010104@zedat.fu-berlin.de> In-Reply-To: <5135BBD9.9090009@FreeBSD.org> References: <5135B7E1.3050002@zedat.fu-berlin.de> <5135BBD9.9090009@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?51364914.2010104>