Date: Fri, 10 Mar 2000 05:50:37 -0500 (EST) From: Mike Squires <mikes@sir-alan.chem.indiana.edu> To: dayton+freebsd-stable@overx.com Cc: freebsd-stable@freebsd.org Subject: Re: samba 2.0.6 crashing -stable Message-ID: <200003101050.FAA76368@sir-alan.chem.indiana.edu> In-Reply-To: <86put34v4f.fsf@polo.overx.com> from Soren Dayton at "Mar 9, 2000 04:49:20 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
> Is this the stuff about setting all the socket options and shared > memory size? Yes > When you say it appears to be related to your hardware, what leads you > to suspect this? I'm also using an intel pro 10/100 NIC, so I'm Other systems on the same switch (not running FreeBSD) do not have problems. 3.4-STABLE is better than 3.3-RELEASE for me here; I've been copying files of up to a few GB, no system crashes (one file was corrupted in transfer). netstat -i says 6171527 in, 15 errors; 5862394 out, 2 errors; 347782 collisions. This is 100Mbit half duplex. (If you're running 100Mbit full duplex on the network, you may want to force full duplex connections; my Pro100B was not negotiating with the 3Com 3000 switch correctly and had to be forced to full duplex). ifconfig fxp0: fxp0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 inet 129.79.137.215 netmask 0xffffff00 broadcast 129.79.137.255 atalk 43136.253 range 43136-43139 phase 2 broadcast 0.255 ipx 814f8800.a0c96c576b ether 00:a0:c9:6c:57:6b media: 100baseTX <full-duplex> status: active supported media: autoselect 100baseTX <full-duplex> 100baseTX 10baseT/UTP <full-duplex> 10baseT/UTP Mike Squires 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?200003101050.FAA76368>