From owner-freebsd-stable@FreeBSD.ORG Fri Sep 12 09:25:45 2003 Return-Path: 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 B14B816A4BF for ; Fri, 12 Sep 2003 09:25:45 -0700 (PDT) Received: from sourcream.tacosalad.org (216.93.178.246 [216.93.178.246]) by mx1.FreeBSD.org (Postfix) with ESMTP id E855043FF5 for ; Fri, 12 Sep 2003 09:25:44 -0700 (PDT) (envelope-from info@PerryResearch.com) Message-ID: <1063383965.3f61f39d6a97d@www.tacosalad.org> Date: Fri, 12 Sep 2003 12:26:05 -0400 From: Info Account To: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: Lotus Notes Release 5.0.8 June 18, 2001 X-Originating-IP: 67.121.51.142 Subject: recent stability problems with fxp driver X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Sep 2003 16:25:45 -0000 I've spent the past four days or so updating machines here to 4.8/9-stable via cvsup, and have done a complete make buildworld/kernel on each machine (some SMP, some single processor). It seems something is broken with the latest fxp driver, on each machine (different mobos and hardware configs) heavy network traffic with fxp NICs causes timeouts and random kernel panics. First machine to experience the problem was a single proc PIII-650 with 512M and Adaptec 2940UW, one fxp, doing a backup via scp, after 10 megs or so starting giving fxp0 timeout errors and dropping the connection (host was not pingable and dropped all arp entries). The only way to restart the scp was to ifconfig fxp0 back up with the same IP and netmask. Second machine is a dual proc PIII-650 with 512M, MegaRAID, one fxp - after a minute or so of scp'ing the machine completely locked, had to be hard reset. Second attempt caused a panic that seized entire machine with instant reboot. Few more machines, same problems, all with varying SCSI subsystems and with one fxp NIC. After replacing each machine's fxp with crappy tulip and/or $12 kmart linksys NIC, I've had no problems at all. --------------------------------- Perry Research, Inc. 5450 Bruce B. Downs Blvd #313 Wesley Chapel, FL 33543 p: 813-864-7659 f: 813-862-2015 http://www.PerryResearch.com