From owner-freebsd-net@FreeBSD.ORG Mon Dec 29 08:42:03 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 128D216A4CE for ; Mon, 29 Dec 2003 08:42:03 -0800 (PST) Received: from gateway.yorkelec.com (s142-179-221-95.ab.hsia.telus.net [142.179.221.95]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7B3E143D1F for ; Mon, 29 Dec 2003 08:41:59 -0800 (PST) (envelope-from timp@crossthread.com) Received: from crossthread.com (pkqyna@yorkpc101.yorkelec.com [192.168.15.101] (may be forged)) by gateway.yorkelec.com (8.12.9/8.12.9) with ESMTP id hBTGdP0Y053172 for ; Mon, 29 Dec 2003 09:39:26 -0700 (MST) Message-ID: <3FF05943.8040205@crossthread.com> Date: Mon, 29 Dec 2003 09:41:39 -0700 From: Tim Pushor User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6b) Gecko/20031205 Thunderbird/0.4 X-Accept-Language: en-us, en MIME-Version: 1.0 To: net@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.33 (www . roaringpenguin . com / mimedefang) Subject: 3rd nic's a charm? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Dec 2003 16:42:03 -0000 Hi all, happy holidays! I have an old box that I am using as my home firewall/NAT box for my residential cable ISP. It was running at or about 4.0. I was using 2 xl interfaces (3com 3c509b's) and was very stable. I have recently added another network at home, and wanted to add another interface to the box, so I added another 509b and the box became unstable. It would work, then hang, then work etc. The thing just rebooted itself a few minutes ago. I installed 5.1-RELEASE on it for a couple of reasons, but was curious to see if I tickled a bug in the stack or driver by adding the 3rd nic. The box doesn't exhibit the exact same problems now, but still stops responding to network traffic once in a while. (i.e its still unstable, but the symptoms are different). I am pretty sure the card I put in is OK - it came from a working system. The box is of an older vintage - Its a P133 with an Intel VX chipset on a gigabyte motherboard. After a while last night, dmesg reported weird things, like just one garbled line. The relevant bits from a working dmesg: xl0: <3Com 3c905B-TX Fast Etherlink XL> port 0x6100-0x617f mem 0xe4002000-0xe400207f irq 11 at device 8.0 on pci0 xl0: Ethernet address: 00:10:5a:12:89:1e miibus0: on xl0 xlphy0: <3Com internal media interface> on miibus0 xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto xl1: <3Com 3c905B-TX Fast Etherlink XL> port 0x6200-0x627f mem 0xe4000000-0xe400007f irq 10 at device 9.0 on pci0 xl1: Ethernet address: 00:50:04:67:7e:63 miibus1: on xl1 xlphy1: <3Com internal media interface> on miibus1 xlphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto xl2: <3Com 3c905B-TX Fast Etherlink XL> port 0x6300-0x637f mem 0xe4001000-0xe400107f irq 9 at device 10.0 on pci0 xl2: Ethernet address: 00:10:5a:07:21:43 miibus2: on xl2 xlphy2: <3Com internal media interface> on miibus2 xlphy2: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto Any ideas? Thanks! Tim