Date: Sat, 08 Feb 2003 00:34:03 +0100 From: Dag-Erling Smorgrav <des@ofug.org> To: Mark Nipper <nipsy@tamu.edu> Cc: stable@freebsd.org Subject: Re: OpenSSH_3.5p1 FreeBSD-20030201 crash Message-ID: <xzpfzqz7jis.fsf@flood.ping.uio.no> In-Reply-To: <20030207211147.GB62439@ops.tamu.edu> (Mark Nipper's message of "Fri, 7 Feb 2003 15:11:47 -0600") References: <20030207054918.GA28559@ops.tamu.edu> <xzpel6knnrn.fsf@flood.ping.uio.no> <20030207145905.GA44046@ops.tamu.edu> <xzpbs1onlv7.fsf@flood.ping.uio.no> <20030207161343.GB44046@ops.tamu.edu> <xzplm0s6jyq.fsf@flood.ping.uio.no> <20030207211147.GB62439@ops.tamu.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
Mark Nipper <nipsy@tamu.edu> writes: > On Fri, Feb 07, 2003 at 07:09:49PM +0100, Dag-Erling Smorgrav wrote: > > In any case, the message indicates data corruption in the TCP > > connection which has gone undetected by the NIC and the network stack. > > It's a very unlikely occurrence, but not impossible. > Does this imply hardware failure of some kind? Not necessarily, it could simply be noise on the cable. DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?xzpfzqz7jis.fsf>