Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 07 Mar 1995 12:20:24 -0800
From:      David Greenman <davidg@Root.COM>
To:        "Paul F. Werkowski" <pw@snoopy.MV.COM>
Cc:        hackers@FreeBSD.org
Subject:   Re: SYSV{SHM|MSG} kills network?? 
Message-ID:  <199503072020.MAA01516@corbin.Root.COM>
In-Reply-To: Your message of "Tue, 07 Mar 95 14:41:13 EST." <199503071941.OAA01546@snoopy.mv.com> 

next in thread | previous in thread | raw e-mail | index | archive | help
>I was running a stock 2.0 kernel connected to ethernet by DE435 PCI
>NIC. Kernel was also built with SYSVSHM. This system got along just
>fine on our small LAN. A few weeks ago I added options SYSVMSG and
>SYSVSEM and rebuilt the kernel. The new system then had network
>problems which caused repeated NFS hangs, etc. Ping from the FreeBSD
>box to any other system resulted in OK performance for about 45
>seconds followed by 45 seconds of lost packets, followed by 45 seconds
>of ok response, followed by 45 seconds of lost packets, etc.. From
>TCPDUMP it appeared that nothing was received for about 50% of the
>time. Rebuilding the kernel without SYSVMSG and SYSVSEM returned the
>network to OK performance.
>
>So, is this fixed in -current or can anyone confirm this behavior?

   Yes, it's fixed in -current. It was caused by a bad assumption about
allocated memory being physically contiguous at startup.

-DG



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199503072020.MAA01516>