From owner-freebsd-questions@FreeBSD.ORG Fri Oct 17 23:02:40 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 280431065687 for ; Fri, 17 Oct 2008 23:02:40 +0000 (UTC) (envelope-from wojtek@wojtek.tensor.gdynia.pl) Received: from wojtek.tensor.gdynia.pl (wojtek.tensor.gdynia.pl [IPv6:2001:4070:101:2::1]) by mx1.freebsd.org (Postfix) with ESMTP id 0BBA28FC16 for ; Fri, 17 Oct 2008 23:02:38 +0000 (UTC) (envelope-from wojtek@wojtek.tensor.gdynia.pl) Received: from wojtek.tensor.gdynia.pl (localhost [IPv6:::1]) by wojtek.tensor.gdynia.pl (8.14.3/8.14.2) with ESMTP id m9HN2Zlc013238; Sat, 18 Oct 2008 01:02:35 +0200 (CEST) (envelope-from wojtek@wojtek.tensor.gdynia.pl) Received: from localhost (wojtek@localhost) by wojtek.tensor.gdynia.pl (8.14.3/8.14.2/Submit) with ESMTP id m9HN2Y6T013235; Sat, 18 Oct 2008 01:02:35 +0200 (CEST) (envelope-from wojtek@wojtek.tensor.gdynia.pl) Date: Sat, 18 Oct 2008 01:02:34 +0200 (CEST) From: Wojciech Puchar To: Aniruddha In-Reply-To: <1224249917.4053.6.camel@debian> Message-ID: <20081018005328.C13134@wojtek.tensor.gdynia.pl> References: <1224054780.4011.20.camel@debian> <20081015072630.GA70901@icarus.home.lan> <1224069478.4247.7.camel@debian> <20081015113101.GA76278@icarus.home.lan> <20081015120911.GI14769@cdnetworks.co.kr> <1224080661.5407.2.camel@debian> <20081015235638.GA22992@cdnetworks.co.kr> <1224249708.4053.0.camel@debian> <1224249917.4053.6.camel@debian> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-questions@freebsd.org Subject: Re: ("SOLVED") 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: Fri, 17 Oct 2008 23:02:40 -0000 > I 'solved' this by buying a new nic. It's an Eminent with a RTL8139D > chipset. you SOLVED it not 'solved'. onboard NICs are usually crap, except high end motherboard. they solder in what's cheapest in the moment. if chips are buggy, they add workaround in windoze drivers. and finally - for average windoze user there is nothing strange that he/she needs to reboot the system many times a day. they don't even know why network stopped working - is it hardware problem, driver problem, system crash. they just reboot. on 3 motherboards i've got with gigabit NIC, 1 are completely unusable (nvidia), one are barely usable after turning off txcsum and rxcsum: re0: port 0xd000-0xd0ff mem 0xf9000000-0xf9000fff irq 17 at device 0.0 on pci4 re0: turning off MSI enable bit. re0: Chip rev. 0x38000000 re0: MAC rev. 0x00000000 the fully working one is: bge0: mem 0xc0100000-0xc010ffff irq 16 at device 0.0 on pci3 miibus0: on bge0 bge0: Ethernet address: 00:14:5e:94:49:19 bge0: [ITHREAD] but the last one is on IBM server. i've just seen re0: turning off MSI enable bit. looks like fix recently added as i upgraded this machine to 7.1 from 6.3 already funny thing - feature that has to be disabled ;)