From owner-freebsd-stable@FreeBSD.ORG Tue May 13 16:50:09 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B0A361065673 for ; Tue, 13 May 2008 16:50:09 +0000 (UTC) (envelope-from minimarmot@gmail.com) Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.30]) by mx1.freebsd.org (Postfix) with ESMTP id 6EDD98FC1C for ; Tue, 13 May 2008 16:50:09 +0000 (UTC) (envelope-from minimarmot@gmail.com) Received: by yw-out-2324.google.com with SMTP id 9so1581545ywe.13 for ; Tue, 13 May 2008 09:50:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; bh=foThX6HJ7uKUbj3+Rbu7fdWeW4SuMk/ioDB7yZRefrs=; b=rtWE7GPvFiM8WcCqSX/Sjbbk69jbX2gRnO5i+CF11gbBdFaf6da3MikOLB/Xzep6KToyZx9FtHpIXpenYlkVAlerlbbmMuxqpSQ14gW/57dkuthNJ7n8pbWmSIXm8adyY2FtxxYFelZ3hHCjmhdSjKQjHD/nuzFu82apUx5McEI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=WJNkbvEepePx4iIK9wNka95ydK6LOqMLS/QoeS6M3gaho1dkLH29y+EPuJoiXkAhWMwabji4BHoVKe/P91RDizPhCWO9NObWnIds/hn/7k6aOe4Lw4Fcz+MDK18MR4hsclWjEHGmXd6lzfMYMB5xEEHcZrJZusjfmtnUiBG+qE8= Received: by 10.150.206.21 with SMTP id d21mr3430447ybg.227.1210695730867; Tue, 13 May 2008 09:22:10 -0700 (PDT) Received: by 10.151.60.8 with HTTP; Tue, 13 May 2008 09:22:10 -0700 (PDT) Message-ID: <47d0403c0805130922x62fc479cs47b8a03f41598e00@mail.gmail.com> Date: Tue, 13 May 2008 12:22:10 -0400 From: "Ben Kaduk" To: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: Re: 7.0 issues fixed? upgrade timing? 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: Tue, 13 May 2008 16:50:09 -0000 Hi all, I only just now subscribed, so my apologies if this has been covered and my cursory search missed it. I am seeing a similar issue to the one described in the email below (pasted from a web listing of this list). That is, my ssh connection will occasionally be dropped with the message Disconnecting: Bad packet length 3190815048. (the number is not always the same). I can reliably reproduce this with `cat < /dev/urandom | od -c` from a FreeBSD-current box (a few weeks old, actually, since the build was broken when I last tried to update) as well as from a mac running OS X 10.4 . The system that is killing my connections is: FreeBSD periphrasis.mit.edu 7.0-STABLE FreeBSD 7.0-STABLE #3: Tue Mar 25 14:53:51 EDT 2008 kaduk@periphrasis.mit.edu:/usr/obj/usr/src/sys/PERIPHRASIS amd64 Any thoughts would be appreciated. -Ben Kaduk ------------------ random message from this thread, for some context ------------- * From: Jeremy Chadwick * Date: Mon, 12 May 2008 05:32:07 -0700 On Mon, May 12, 2008 at 01:44:22PM +0200, Torfinn Ingolfsen wrote: On Mon, 12 May 2008 11:37:53 +0200 Torfinn Ingolfsen wrote: FWIW, I had major troubles with re(4) around 7.0-release, and a while later (I had to use patches). After upgrading to 7-stable on 2008-04-12, re(4) is working for me without patches. (sigh).. it seems that I spoke to soon. Murphy just showed up. I still get ssh disconnects (see below) on connections _to_ the machine when transferring largish amounts of data (like when upgrading a port). Here is one example (portupgrading the jdk port): /usr/bin/gcc -fno-strict-aliasing -fPIC -W -Wall -Wno-unused -Wno-parentheses -pipe -Damd64 -DARCH='"amd64"' -DRELEASE='"1.6.0_03-p4"' -DFULL_VERSION='"1.6.0_03-p4-root_12_may_2008_13_25-b00"' -D_GNU_SOURCE -D_REENTRANT -D_THREAD_SAFE -D_ALLBSD_SOURCE -D_LP64=1 -I. -I/usr/ports/java/jdk16/work/control/build/bsd-amd64/tmp/java/java.lang.management/management/CClassHeaders -I../../../src/solaris/javavm/export -I../../../src/share/javavm/export -I../../../src/share/javavm/include -I../../../src/solaris/javavm/include -I../../../src/share/native/sun/management -I../../../src/solaris/hpi/include -I../../../src/share/native/common -I../../../src/solaris/native/common -I../../../src/share/native/java/lang/management -I../../../src/solaris/native/java/lang/management -c -o /usr/ports/java/jdk16/work/control/build/bsd-amd64/tmp/java/java.lang.management/management/obj64/ClassLoadingImpl.o ../../../src/share/native/sun/management/ClassLoadingImpl.c Disconnecting: Bad packet length 3601161525. The machine is running: tingo@kg-vm$ uname -a FreeBSD kg-vm.kg4.no 7.0-STABLE FreeBSD 7.0-STABLE #10: Sat Apr 12 21:42:55 CEST 2008 root@xxxxxxxxxxxx:/usr/obj/usr/src/sys/GENERIC amd64 and has been up for about 14 days: tingo@kg-vm$ uptime 1:36PM up 14 days, 17:42, 7 users, load averages: 2.15, 1.85, 1.34 I see that if_re.c for RELENG_7 has been updated on April 22nd, so I'll upgrade the machine to latest -stable and see if that works better. Is this machine using pf(4) at all?