From owner-freebsd-stable@FreeBSD.ORG Thu Dec 1 13:44:01 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D6BFA16A41F for ; Thu, 1 Dec 2005 13:44:01 +0000 (GMT) (envelope-from massimo@cedoc.mo.it) Received: from insomma.datacode.it (ip-152-166.sn2.eutelia.it [83.211.152.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id E338443D5E for ; Thu, 1 Dec 2005 13:44:00 +0000 (GMT) (envelope-from massimo@cedoc.mo.it) Received: from localhost (localhost.datacode.it [127.0.0.1]) by insomma.datacode.it (Postfix) with SMTP id 530D12C90B for ; Thu, 1 Dec 2005 14:43:58 +0100 (CET) Received: from insomma.datacode.it (localhost.datacode.it [127.0.0.1]) by insomma.datacode.it (Postfix) with ESMTP id 8C49E2C90A for ; Thu, 1 Dec 2005 14:43:57 +0100 (CET) Received: from massimo.datacode.it (massimo.datacode.it [192.168.1.13]) by insomma.datacode.it (Postfix) with ESMTP id 4B4812C906 for ; Thu, 1 Dec 2005 14:43:57 +0100 (CET) From: Massimo Lusetti To: freebsd-stable@freebsd.org In-Reply-To: <20051201112720.GK22816@cell.sick.ru> References: <1133432561.4306.16.camel@massimo.datacode.it> <20051201112720.GK22816@cell.sick.ru> Content-Type: text/plain Organization: CEDOC - Modena Date: Thu, 01 Dec 2005 14:43:57 +0100 Message-Id: <1133444637.4308.2.camel@massimo.datacode.it> Mime-Version: 1.0 X-Mailer: Evolution 2.0.4 (2.0.4-7) Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP Subject: Re: Heavy loaded network machine 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: Thu, 01 Dec 2005 13:44:02 -0000 On Thu, 2005-12-01 at 14:27 +0300, Gleb Smirnoff wrote: > The em(4) driver in STABLE is now in quite good state. We use it on > heavy loaded routers. The interrupt storm in the thread you mention > was probably caused by some bad hardware combination between mainboard > and NIC. Thanks Gleb for the clarification. I'm now willing to ask if there's any evidence of which could be the issue causing that problem, so i can (at least try) avoid that combination. Regards -- Massimo.run();