From owner-freebsd-stable@FreeBSD.ORG Mon Aug 20 19:01:35 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 4BEB516A4EE for ; Mon, 20 Aug 2007 19:01:34 +0000 (UTC) (envelope-from nik@mail.optim-mol.cemu.ru) Received: from mail.optim-mol.cemu.ru (mail.optim-mol.cemu.ru [83.102.188.27]) by mx1.freebsd.org (Postfix) with ESMTP id 8C0FE13C48A for ; Mon, 20 Aug 2007 19:01:34 +0000 (UTC) (envelope-from nik@mail.optim-mol.cemu.ru) Received: from user-105na47.cable.mindspring.com ([64.91.168.135] helo=[192.168.2.254]) by mail.optim-mol.cemu.ru with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67 (FreeBSD)) (envelope-from ) id 1INBeI-000NwC-8T; Mon, 20 Aug 2007 22:06:49 +0400 Message-ID: <46C9D817.1070704@optim.com.ru> Date: Mon, 20 Aug 2007 13:06:15 -0500 From: Nikolay Mirin Organization: =?UTF-8?B?0J7Qn9Ci0JjQnA==?= User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 To: Robert Slawson , freebsd-stable@freebsd.org References: <2306ABA6-49A6-412E-81CD-CBABAE885EB2@charter.net> In-Reply-To: <2306ABA6-49A6-412E-81CD-CBABAE885EB2@charter.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Sender: nik@mail.optim-mol.cemu.ru X-SA-Exim-Connect-IP: 64.91.168.135 X-SA-Exim-Mail-From: nik@mail.optim-mol.cemu.ru X-SA-Exim-Scanned: No (on mail.optim-mol.cemu.ru); SAEximRunCond expanded to false Cc: 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 19:01:35 -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 > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"