From owner-freebsd-stable@FreeBSD.ORG Wed May 19 10:44:35 2010 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 72F2B106564A for ; Wed, 19 May 2010 10:44:35 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta07.westchester.pa.mail.comcast.net (qmta07.westchester.pa.mail.comcast.net [76.96.62.64]) by mx1.freebsd.org (Postfix) with ESMTP id 23B8C8FC0A for ; Wed, 19 May 2010 10:44:34 +0000 (UTC) Received: from omta02.westchester.pa.mail.comcast.net ([76.96.62.19]) by qmta07.westchester.pa.mail.comcast.net with comcast id KNcv1e0050QuhwU57Nkbh2; Wed, 19 May 2010 10:44:35 +0000 Received: from koitsu.dyndns.org ([98.248.46.159]) by omta02.westchester.pa.mail.comcast.net with comcast id KNkZ1e00K3S48mS3NNkauK; Wed, 19 May 2010 10:44:35 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 345289B419; Wed, 19 May 2010 03:44:32 -0700 (PDT) Date: Wed, 19 May 2010 03:44:32 -0700 From: Jeremy Chadwick To: Mark Stapper Message-ID: <20100519104432.GA75634@icarus.home.lan> References: <4BF3BEA9.3010900@mapper.nl> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4BF3BEA9.3010900@mapper.nl> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: stable@freebsd.org Subject: Re: network probs rxcsum 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, 19 May 2010 10:44:35 -0000 On Wed, May 19, 2010 at 12:34:17PM +0200, Mark Stapper wrote: > I have two machines running FreeBSD amd64 8.0-Stable with custom kernels. > My newer box has had troubles with ssh from day one. > I hoped a kernel upgrade would help, but it didn't. > When I'd ssh into the box ssh would exit with errors: > Bad packet length xxxxxx > Disconnecting: Packet corrupt. > > after issueing: "ifconfig em0 -rxcons" everything was stable again. > First I figured it'd be a driver issue. However, I use the same NIC in > my other box! > What could be causing this problem? I think you mean "-rxcsum", not "-rxcons". Could you please provide output from the following commands? Jack Vogel will probably respond later about this, but said output would help him. - uname -a - dmesg | grep em0 - pciconf -lvc Thanks. -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB |