Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 10 Mar 2013 21:44:30 +0100
From:      Pawel Jakub Dawidek <pjd@FreeBSD.org>
To:        John Baldwin <jhb@freebsd.org>
Cc:        davide@FreeBSD.org, Dimitry Andric <dim@freebsd.org>, freebsd-current@freebsd.org, "Hartmann, O." <ohartman@zedat.fu-berlin.de>
Subject:   Re: r247839: broken pipe - for top, sudo and ports
Message-ID:  <20130310204430.GB9784@garage.freebsd.pl>
In-Reply-To: <201303060804.57238.jhb@freebsd.org>
References:  <5135B7E1.3050002@zedat.fu-berlin.de> <5135BBD9.9090009@FreeBSD.org> <51364914.2010104@zedat.fu-berlin.de> <201303060804.57238.jhb@freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help

--Bn2rw/3z4jIqBvZU
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Wed, Mar 06, 2013 at 08:04:57AM -0500, John Baldwin wrote:
> On Tuesday, March 05, 2013 2:35:48 pm Hartmann, O. wrote:
> > On recent FreeBSD 10.0-CURRENT/amd64 (CLANG buildworld, serveral systems
> > (3) the same symptoms)), many services drop a sporadic
> >=20
> > broken pipe
> >=20
> > 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
> >=20
> > *** [do-extract] Signal 13
> >=20
> > 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.
> >=20
> > Since dbus fails to start and even the nVidia driver (which is a kernel
> > module, it canot be built and therefore ... ).
> >=20
> > Dimitry, I put you into CC, just in case. It seems that the last commits
> > (not only the new DRM2 mess) broke something.
> >=20
> > I hope that others using FreeBSD 10.0CURRENT with CLANG can confirm thi=
s.\
>=20
> Have you tried backing up to just before all of pjd@'s file descriptor and
> capsicum commits?  It broke some other stuff initially related to fd pass=
ing,
> so I don't think it is beyond imagination that it broke something with UN=
IX
> domain sockets in general.

Is there a consensus already if this is result of my changes or davide's
r247804?

I just upgraded my laptop to today's HEAD and I don't see any weird
behaviour yet. If someone can provide a way to reproduce the problem,
I'd be happy to investigate.

--=20
Pawel Jakub Dawidek                       http://www.wheelsystems.com
FreeBSD committer                         http://www.FreeBSD.org
Am I Evil? Yes, I Am!                     http://tupytaj.pl

--Bn2rw/3z4jIqBvZU
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (FreeBSD)

iEYEARECAAYFAlE88K4ACgkQForvXbEpPzQlQACgovYkKt+YDykpeTJ3bEh6epaY
JBcAoO3EP0EoQ25Uh6DggAec/uQFS7ak
=cj7/
-----END PGP SIGNATURE-----

--Bn2rw/3z4jIqBvZU--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20130310204430.GB9784>