7.0 issues fixed? upgrade timing?
pyunyh at gmail.com
Wed May 14 00:17:43 UTC 2008
On Tue, May 13, 2008 at 12:22:10PM -0400, Ben Kaduk wrote:
> 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
> 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 at periphrasis.mit.edu:/usr/obj/usr/src/sys/PERIPHRASIS amd64
> Any thoughts would be appreciated.
There had been large changes to enhance re(4) stablility and many
users reported positive results. But it still seems to have issues
for certain models. See kern/123202, kern/123563.
If you encounter issues on latest re(4), please try patch in
kern/123563 and let me know how it goes.
> -Ben Kaduk
> ------------------ random message from this thread, for some context
> * From: Jeremy Chadwick <koitsu at xxxxxxxxxxx>
> * 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 <torfinn.ingolfsen at xxxxxxxxxxxx> 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"'
> -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/share/javavm/export -I../../../src/share/javavm/include
> -I../../../src/solaris/hpi/include -I../../../src/share/native/common
> -I../../../src/solaris/native/java/lang/management -c -o
> Disconnecting: Bad packet length 3601161525.
> The machine is running:
> tingo at 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 at xxxxxxxxxxxx:/usr/obj/usr/src/sys/GENERIC
> and has been up for about 14 days:
> tingo at 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
> Is this machine using pf(4) at all?
More information about the freebsd-stable