From owner-freebsd-stable@FreeBSD.ORG Wed Jun 28 21:06:24 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BD76F16A738 for ; Wed, 28 Jun 2006 21:06:23 +0000 (UTC) (envelope-from freebsd-listen@fabiankeil.de) Received: from smtprelay01.ispgateway.de (smtprelay01.ispgateway.de [80.67.18.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id CF50844C8C for ; Wed, 28 Jun 2006 20:48:27 +0000 (GMT) (envelope-from freebsd-listen@fabiankeil.de) Received: (qmail 24538 invoked from network); 28 Jun 2006 20:48:25 -0000 Received: from unknown (HELO localhost) (775067@[217.50.134.146]) (envelope-sender ) by smtprelay01.ispgateway.de (qmail-ldap-1.03) with SMTP for ; 28 Jun 2006 20:48:25 -0000 Date: Wed, 28 Jun 2006 22:48:12 +0200 From: Fabian Keil To: Robert Watson Message-ID: <20060628224812.38b09d82@localhost> In-Reply-To: <20060628101729.J50845@fledge.watson.org> References: <20060627175853.765a590e@localhost> <20060628101729.J50845@fledge.watson.org> X-Mailer: Sylpheed-Claws 2.2.3 (GTK+ 2.8.19; i386-portbld-freebsd6.1) X-PGP-KEY-URL: http://www.fabiankeil.de/gpg-keys/freebsd-listen-2006-08-19.asc User-Agent: 321 test Mime-Version: 1.0 Content-Type: multipart/signed; boundary=Sig_rgQAbWi_742OYf7F4GTdY6W; protocol="application/pgp-signature"; micalg=PGP-SHA1 Cc: Peter Thoenen , freebsd-stable@freebsd.org Subject: Re: FreeBSD 6.1 Tor issues (Once More, with Feeling) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Jun 2006 21:06:25 -0000 --Sig_rgQAbWi_742OYf7F4GTdY6W Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Robert Watson wrote: > On Tue, 27 Jun 2006, Fabian Keil wrote: >=20 > > There was a "request" for Tor related problem reports a while ago, > > I couldn't find the message again, but I believe it was posted here. >=20 > I'm very interested in tracking down this problem, but have had a lot > of trouble getting reliable reports of problems -- i.e., ones where I > could get any debugging information. I had a similar conversation on > these lines yeterday with Roger (Tor author) here at the WEIS > conference. If this is easily reproduceable, I would like you to do > the following: >=20 > - Compile in options DDB, options KDB, options BREAK_TO_DEBUGGER, > options WITNESS, options WITNESS_SKIPSPIN, options INVARIANTS, options > INVARIANT_SUPPORT. >=20 > - Make sure to have a kernel with debugging symbols for the kernel. >=20 > - Turn on core dumps. Done. I expect to get a chance to test the settings in the next 24 hours. =20 > The above debugging options will have a significant performance > impact, and may or may not affect the probability of the race or > deadlock being exercised. The first question is: >=20 > - Are there any warnings on the console from WITNESS or other > debugging options? If so, please copy/paste them into an e-mail for > me. So far the logs show nothing unusual, but I noticed that the ssh connection gets unresponsive from time to time. I did a few pings with "interesting" results: [fk@tor ~]$ ping 10.0.0.1 | grep 'time=3D[^0]' 64 bytes from 10.0.0.1: icmp_seq=3D25 ttl=3D64 time=3D1.104 ms 64 bytes from 10.0.0.1: icmp_seq=3D61 ttl=3D64 time=3D2.983 ms 64 bytes from 10.0.0.1: icmp_seq=3D167 ttl=3D64 time=3D1.112 ms 64 bytes from 10.0.0.1: icmp_seq=3D189 ttl=3D64 time=3D1.653 ms 64 bytes from 10.0.0.1: icmp_seq=3D222 ttl=3D64 time=3D1.748 ms 64 bytes from 10.0.0.1: icmp_seq=3D291 ttl=3D64 time=3D1.058 ms 64 bytes from 10.0.0.1: icmp_seq=3D334 ttl=3D64 time=3D1.020 ms 64 bytes from 10.0.0.1: icmp_seq=3D337 ttl=3D64 time=3D1.967 ms 64 bytes from 10.0.0.1: icmp_seq=3D562 ttl=3D64 time=3D1.027 ms 64 bytes from 10.0.0.1: icmp_seq=3D586 ttl=3D64 time=3D1.230 ms ^C[fk@tor ~]$ ping tor.fabiankeil.de | grep 'time=3D[^0]' 64 bytes from 81.169.155.246: icmp_seq=3D70 ttl=3D64 time=3D1.920 ms 64 bytes from 81.169.155.246: icmp_seq=3D79 ttl=3D64 time=3D1.587 ms 64 bytes from 81.169.155.246: icmp_seq=3D402 ttl=3D64 time=3D1.062 ms ^C[fk@tor ~]$ ping localhost | grep 'time=3D[^0]' 64 bytes from 127.0.0.1: icmp_seq=3D142 ttl=3D64 time=3D1.142 ms 64 bytes from 127.0.0.1: icmp_seq=3D497 ttl=3D64 time=3D1.227 ms 64 bytes from 127.0.0.1: icmp_seq=3D627 ttl=3D64 time=3D1.181 ms 10.0.0.1 is on lo1, 81.169.155.246 is on fxp0, both are filtered with pf. lo0 is skipped. The pings were run locally while tor was running, the usual ping response times are below 0.2 ms. I get even more obscene ping times if I ping from home, but my net connection isn't the best. I'd appreciate if someone with a reliable net connection could confirm the weirdness. Thanks for your time, Robert, I hope to have real information by tomorrow. Fabian --=20 http://www.fabiankeil.de/ --Sig_rgQAbWi_742OYf7F4GTdY6W Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEousWjV8GA4rMKUQRAi5iAJ9R8apw+r726wihMtTCtXvukCx9IgCfaNRZ upyIw2IRItOUcoY8QH7PcLs= =fHla -----END PGP SIGNATURE----- --Sig_rgQAbWi_742OYf7F4GTdY6W--