From owner-freebsd-current@FreeBSD.ORG Thu Apr 26 21:48:00 2007 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D58C816A421; Thu, 26 Apr 2007 21:48:00 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by mx1.freebsd.org (Postfix) with ESMTP id 5A27B13C45E; Thu, 26 Apr 2007 21:48:00 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from localhost.corp.yahoo.com (john@localhost [127.0.0.1]) (authenticated bits=0) by server.baldwin.cx (8.13.8/8.13.8) with ESMTP id l3QLlape078120; Thu, 26 Apr 2007 17:47:57 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-current@freebsd.org Date: Thu, 26 Apr 2007 17:42:20 -0400 User-Agent: KMail/1.9.6 References: <20070422064444.GK73385@funkthat.com> <2a41acea0704221053r5630b054ked29d9238f248851@mail.gmail.com> In-Reply-To: <2a41acea0704221053r5630b054ked29d9238f248851@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200704261742.21007.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [127.0.0.1]); Thu, 26 Apr 2007 17:47:57 -0400 (EDT) X-Virus-Scanned: ClamAV 0.88.3/3165/Thu Apr 26 09:03:24 2007 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: John-Mark Gurney , Jack Vogel , current@freebsd.org Subject: Re: MSI issues w/ Athlon64 X2 3800+ and nForce 430? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Apr 2007 21:48:00 -0000 On Sunday 22 April 2007 01:53:54 pm Jack Vogel wrote: > On 4/21/07, John-Mark Gurney wrote: > > I finally upgraded to -current that supports MSI, and I appear to be > > having issues w/ it. I have two different ethernet cards that exhibit > > issues on this system. An msk PCIe based card, and a PCI em based card... > > > > With MSI the msk card produced regular: > > msk1: watchdog timeout (missed Tx interrupts) -- recovering > > > > But was usable enough to push ~110meg/sec out. When I was watching an > > HD program streamed over http, there were regular hickups ever few > > minutes, which I figured was due to the above messages (though none > > appeared while watching), so I decided to switch back to my em based > > card, and w/ MSI the card is practically useless. I get: > > Apr 21 22:13:09 carbon kernel: em0: watchdog timeout -- resetting > > Apr 21 22:13:09 carbon kernel: em0: link state changed to DOWN > > Apr 21 22:13:12 carbon kernel: em0: link state changed to UP > > Apr 21 22:14:19 carbon kernel: em0: watchdog timeout -- resetting > > Apr 21 22:14:19 carbon kernel: em0: link state changed to DOWN > > > > Which ends up making things a bit difficult to pass usable traffic over > > the interface. > > That NIC is too old to use with MSI, anything not PCI Express is not > going to work reliably, even if at this point you arent stopped from > trying to set it, with changes to the driver forthcoming you will be. FWIW, I actually have used MSI with at least some PCI-X em(4) parts and it worked fine. -- John Baldwin