From owner-freebsd-questions@FreeBSD.ORG Wed Oct 15 11:49:51 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9B2881065687 for ; Wed, 15 Oct 2008 11:49:51 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from QMTA07.emeryville.ca.mail.comcast.net (qmta07.emeryville.ca.mail.comcast.net [76.96.30.64]) by mx1.freebsd.org (Postfix) with ESMTP id 5BBC08FC19 for ; Wed, 15 Oct 2008 11:49:50 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from OMTA08.emeryville.ca.mail.comcast.net ([76.96.30.12]) by QMTA07.emeryville.ca.mail.comcast.net with comcast id SyA11a0060FhH24A7zpqNU; Wed, 15 Oct 2008 11:49:50 +0000 Received: from koitsu.dyndns.org ([69.181.141.110]) by OMTA08.emeryville.ca.mail.comcast.net with comcast id Szpp1a00B2P6wsM8UzppX7; Wed, 15 Oct 2008 11:49:50 +0000 X-Authority-Analysis: v=1.0 c=1 a=N8TDiX_OOuEA:10 a=TiS0_Z0ZvfoA:10 a=QycZ5dHgAAAA:8 a=vOf0ggQMuSXUGlx4LksA:9 a=q5gB_7RqAMST_KdbYhYK6k2G__cA:4 a=EoioJ0NPDVgA:10 a=LY0hPdMaydYA:10 Received: by icarus.home.lan (Postfix, from userid 1000) id 53345C9419; Wed, 15 Oct 2008 04:49:49 -0700 (PDT) Date: Wed, 15 Oct 2008 04:49:49 -0700 From: Jeremy Chadwick To: Wojciech Puchar Message-ID: <20081015114949.GA76694@icarus.home.lan> References: <1224054780.4011.20.camel@debian> <20081015072630.GA70901@icarus.home.lan> <1224069478.4247.7.camel@debian> <20081015113101.GA76278@icarus.home.lan> <20081015133954.Y9605@wojtek.tensor.gdynia.pl> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20081015133954.Y9605@wojtek.tensor.gdynia.pl> User-Agent: Mutt/1.5.18 (2008-05-17) Cc: PYUN Yong-Hyeon , Aniruddha , freebsd-questions@freebsd.org Subject: Re: Under heavy load internet gets killed, only a reboot can bring it back up X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Oct 2008 11:49:51 -0000 On Wed, Oct 15, 2008 at 01:40:45PM +0200, Wojciech Puchar wrote: >> >> One thing worth trying would be to disable MSI/MSI-X. You can disable >> these by adding the following to your /boot/loader.conf : >> >> hw.pci.enable_msix="0" >> hw.pci.enable_msi="0" > > what's wrong in MSI interrupts? Nothing -- but there are known compatibility problems with MSI/MSI-X on some boards. I remember reading about this with regards to em(4) not too long ago. It's worth ruling out, especially since his problem is reproducible (if disabling MSI doesn't fix the problem, he can simply remove those two loader.conf variables and we've ruled out one possibility). >>> mskc0: Uncorrectable PCI Express error >>> mskc0: Uncorrectable PCI Express error >> >> Those errors at the end of your dmesg don't look good; could be the sign >> of a NIC or motherboard that's going bad, or possibly a very strange >> driver problem. > > or just connectors should be cleaner or card isn't fitted well - contact > problems. I'm under the impression his NIC is on-board, not a physical PCI-E card. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB |