Date: Sun, 12 Sep 2004 10:57:45 -0400 (EDT) From: Robert Watson <rwatson@FreeBSD.ORG> To: Andre Guibert de Bruet <andy@siliconlandmark.com> Cc: current@FreeBSD.ORG Subject: Re: 6-CURRENT Network stack issues w/SMP? (Was: Re: TreeListfailed: Network write failure: ChannelMux.ProtocolError) Message-ID: <Pine.NEB.3.96L.1040912105547.3683C-100000@fledge.watson.org> In-Reply-To: <20040912025037.Y84468@alpha.siliconlandmark.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 12 Sep 2004, Andre Guibert de Bruet wrote: > On Sun, 12 Sep 2004, Kris Kennaway wrote: > > > On Sun, Sep 12, 2004 at 02:42:03AM -0400, Andre Guibert de Bruet wrote: > > > >>> I've also noticed data corruption in the form of failed CRCs (And hence > >>> dropped SSH connections) while transferring large amounts of data via SSH > >>> over gige to a machine on its subnet. These problems started occuring > >>> after the giant-less networking megacommit. Older kernels check out > >>> without any such issues. > > > > Does it go away if you turn off debug.mpsafenet? If not, it's > > probably not related to that commit. > > Setting debug.mpsafenet to 0 allows the SSH transfers to complete. The > MD5 checksums and sizes match. Where do we go from here? I think I'd look at the following next: - Does your network interface driver support checksum offload? If so, what happens if you disable that? - Is the network interface driver marked as INTR_MPSAFE and/or not IFF_NEEDSGIANT. If either, try setting the driver to run with Giant by removing INTR_MPSAFE and adding IFF_NEEDSGIANT. After that I think we want to try and produce a non-SSH reproduction scenario using a very simple test program... Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Principal Research Scientist, McAfee Research
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.NEB.3.96L.1040912105547.3683C-100000>