From owner-freebsd-stable@FreeBSD.ORG Mon Aug 20 21:06:03 2007 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4CE6B16A417 for ; Mon, 20 Aug 2007 21:06:03 +0000 (UTC) (envelope-from clay@milos.co.za) Received: from bart.milos.co.za (bart.milos.co.za [196.38.18.66]) by mx1.freebsd.org (Postfix) with ESMTP id F3B8013C45A for ; Mon, 20 Aug 2007 21:06:01 +0000 (UTC) (envelope-from clay@milos.co.za) Received: (qmail 67762 invoked by uid 89); 20 Aug 2007 21:08:14 -0000 Received: by simscan 1.2.0 ppid: 67757, pid: 67759, t: 0.6886s scanners: attach: 1.2.0 clamav: 0.88.7/m:43/d:3604 Received: from unknown (HELO claylaptop) (clay@milos.za.net@84.203.53.189) by bart.milos.co.za with ESMTPA; 20 Aug 2007 21:08:14 -0000 Message-ID: <006c01c7e36d$e67f95d0$0701a8c0@claylaptop> From: "Clayton Milos" To: References: <2306ABA6-49A6-412E-81CD-CBABAE885EB2@charter.net> <46C9D817.1070704@optim.com.ru> Date: Mon, 20 Aug 2007 22:05:53 +0100 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="UTF-8"; reply-type=response Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.3138 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138 Subject: Re: Marvel Yukon using the sk driver 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: Mon, 20 Aug 2007 21:06:03 -0000 > Hi, what I can tell. > I had a terrible problem with this card (PCI-E version) exactly one week > ago. Both drivers msk from the system and myk from the vendor show similar > behavior. > On high loads, like 2-3 users from Samba domain pulling their profiles at > the same time, the card just chokes. No ping, and > "buffer overflow message". > I mean I had to bring the interface down and up again. Absolutely > disgusting. > No tweak helps. > > I mean, we tested it over the weekend and it was fine, till folks come > there on Monday and start massively using the server. > > We downgraded the hardware and put good old 3Com509 PCI or whatever works > with xl driver. > > > Robert Slawson said the following on 20.08.2007 10:13: >> Greetings, >> >> I have a marvel yukon pci gigabit ethernet card. For some reason, after a >> period of time it will not transmit unless I make it transmit by pinging >> via the console. It is very annoying as I cannot ssh into the machine >> until I "wake up" the card by telling it to ping something. >> >> I am using 6.2 stable and just yesterday rebuilt the kernel and world >> hoping this would fix the problem. But nothing seems to help. >> >> I think the card needs to use the msk driver , which is installed, but >> the card keeps using the sk driver. Is there a way to have freebsd re >> identify the card correctly and use the proper driver? >> >> Thanks in advance, >> Bob >From my experience it always pays to use good hardware. I use 3com/Broadcom or Intel NIC's. Nothing else. Ever! They get much better throughput with less CPU overhead. And the real advantage is they have good suport in UNIX systems. I know Jack Vogel did his best and sorted out the issues with mine and many other people's Intel gigabit (em based) cards when there were issues. My em card is flying along happily now like it should be. The last server I bought had dual onboard Broadcom NIC's and I've had not issues throwing 500Mbit/s through them. Haven't had a chance to really push them to the limits yet. I know I'm not really helping you directly here but my advice would be to throw an Intel gigabit desktop adapter in there and your problems will disappear. They're only $20-$30 nowadays and it's going to take your headache away. -Clay