Date: Sun, 22 Apr 2007 10:53:54 -0700 From: "Jack Vogel" <jfvogel@gmail.com> To: "John-Mark Gurney" <gurney_j@resnet.uoregon.edu>, current@freebsd.org Subject: Re: MSI issues w/ Athlon64 X2 3800+ and nForce 430? Message-ID: <2a41acea0704221053r5630b054ked29d9238f248851@mail.gmail.com> In-Reply-To: <20070422064444.GK73385@funkthat.com> References: <20070422064444.GK73385@funkthat.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 4/21/07, John-Mark Gurney <gurney_j@resnet.uoregon.edu> 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. Jack
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2a41acea0704221053r5630b054ked29d9238f248851>