From owner-freebsd-current@FreeBSD.ORG Tue Oct 18 20:01:31 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A521216A41F for ; Tue, 18 Oct 2005 20:01:31 +0000 (GMT) (envelope-from dan@mail.neosystem.cz) Received: from gem.neosystem.cz (gem.neosystem.cz [81.95.103.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8C3AD43D45 for ; Tue, 18 Oct 2005 20:01:30 +0000 (GMT) (envelope-from dan@mail.neosystem.cz) Received: from localhost (localhost [127.0.0.1]) by gem.neosystem.cz (Postfix) with ESMTP id E416538AF8E for ; Tue, 18 Oct 2005 22:01:33 +0200 (CEST) Received: from gem.neosystem.cz ([127.0.0.1]) by localhost (gem [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 31488-09 for ; Tue, 18 Oct 2005 22:01:32 +0200 (CEST) Received: from phobos.sky.net (ip-85-160-47-156.eurotel.cz [85.160.47.156]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by gem.neosystem.cz (Postfix) with ESMTP id CF13B38AF8D for ; Tue, 18 Oct 2005 22:01:30 +0200 (CEST) Date: Tue, 18 Oct 2005 21:59:50 +0200 From: Dan Bilik To: freebsd-current@freebsd.org Message-Id: <20051018215950.7defb35e.dan@mail.neosystem.cz> In-Reply-To: <20051017114655.636eff01.dan@mail.neosystem.cz> References: <20051017114655.636eff01.dan@mail.neosystem.cz> Organization: neosystem.cz X-Mailer: Sylpheed version 2.0.1 (GTK+ 2.6.8; i686-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at neosystem.cz Subject: Re: Possible fxp(4) problem in -CURRENT 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: Tue, 18 Oct 2005 20:01:31 -0000 On Mon, 17 Oct 2005 11:46:55 +0200 Dan Bilik wrote: > Situation: > Single-purpose machines only serving http requests for static content, > ... > Problem: > After some time of serving requests the ethernet interface in the > machine stops communicating on the wire. It does not respond to any > packets (ping, http, nfs, ssh) and vmstat(8) shows stopped interrupt > ... Some fresh additional info: Today one of the problem machines got stuck again. I was able to log on through second functional interface and watch it more closely. Sending packets from the box worked (its arp requests were appearing on other boxes in the subnet) but it could not receive any packet. And another thing... It seems that running tcpdump (ie. entering and leaving promiscuous mode) on the interface resolved the problem and made the machine to appear back on the network. It's running with no problem from that moment. Any ideas what's going on here? Does it make sense to anyone? Dan