From owner-freebsd-hardware@FreeBSD.ORG Fri Feb 11 04:25:14 2005 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EB74F16A4CE for ; Fri, 11 Feb 2005 04:25:14 +0000 (GMT) Received: from aramaki.bong.com.au (aramaki.bong.com.au [203.91.232.99]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6CEB143D39 for ; Fri, 11 Feb 2005 04:25:11 +0000 (GMT) (envelope-from dean@bong.com.au) Received: from staff-gw.penrithcity.nsw.gov.au ([203.91.245.99] helo=[172.16.15.15]) by aramaki.bong.com.au with asmtp (Exim 4.34) id 1CzSS2-0001Os-Ng; Fri, 11 Feb 2005 15:30:45 +1100 Message-ID: <420C339F.3070200@bong.com.au> Date: Fri, 11 Feb 2005 15:25:03 +1100 From: Dean Hamstead User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Martin Minkus References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Spam-Score: -2.8 X-Spam-Report: Spam detection software, running on the system "aramaki.bong.com.au", hasmessagelabel similar future email. If you have any questions, see staff@bong.com.au for details. Content preview: [...] Content analysis details: (-2.8 points, 5.0 required) pts rule name description -------------------------------------------------- -2.8 ALL_TRUSTED Did not pass through any untrusted hosts X-Spam-Scanned-By: aramaki.bong.com.au X-Scan-Signature: bd7b6e61b9c8e509d2ad47a490618f2c cc: hardware@freebsd.org Subject: Re: 5.3-Stable network issue X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Feb 2005 04:25:15 -0000 i cant offer a proper patch, but i can suggest dropping in a different network card - as in other than realtek which may solve your immediate problem. i certainly would *never* use a realtek card where ever humanly possible. intel and 3com are usually the goers. the 3c905b is possibly one of the most renouned as a work horse. i have one in my home fileserver and the performance difference verses its onboard realtek is quite astounding. (1-2000k/s to 5-6000k/s) ive also had great success with dlink and netgear cards. the dlink the dfe530tc (rev a) which is via rhine based and the netgear fa310tx which is uses the tulip driver Dean Martin Minkus wrote: > I seem to have been having a rather strange networking issue in FreeBSD > 5.3-Stable (it started happening immediately after 5.2.1 and has persisted > since.. I keep ³hoping² that next time I cvsup it will be fixed, but no). > > I downgraded back to 5.2.1-p13 and it is perfectly fine once again. > > > *** Some background information: > > My FreeBSD box is my home NAT router, server, firewall, etc. It does DHCP, > MX for some of my domains, secondary DNS (I got primary elsewhere), apache > for some webhosting, blah blah blah. Nothing really special. It is a Dual > PIII-500, 512mb ram, and a couple ATA hdd¹s. Had 3 realtek network > interfaces, but down to 2 now. > > *** The problem: > > Networking simply "stops" or "locks up". Why, I don't know. I believe > initially it happened for all 3 network cards... I thought tcp/ip processing > or something in the kernel got locked. It happens every 30 minutes to an > hour, and lasts about 60 seconds to 120 seconds. Unfortunately, 60 seconds > to 120 seconds is long enough to kill messenger (my gf does not like), > online gaming, etc etc. > > Lately, I had taken one of the realtek cards out (it was for a several km > long wireless link) and moved the server to my gf's place (where I am now > 100% of the time). So now that I have the server locally and rely on it for > my internet connection, this has become a real PAIN. > > I've noticed that I can remain ssh'd into diablo, do whatever I want while > this "lock" issue occurs. So the lan interface rl0 is fine. The internet > interface, rl1 (which goes to the cable modem) locks up. (btw, its not the > cable modem as I am using my gf's now, and it did this at my place on my > cable modem too, which is a different brand. Nortel at my place, motorola at > my gfs). > > *** Attempts: > > I've attempted switching out network cards, and places 3 other realtek cards > in. Different brands, all with different revisions (D instead of B, etc, > etc). > > No matter what I try, nothing fixes it. The machine seems perfectly > repsonsive, and I am still ssh'd in and can do whatever I want on it... But > the network card going to the cable modem has stopped responding?! > > This never happened during 5.0-Current all throughout 5.2.1-STABLE, but > anywhere beyond 5.2.1 it craps itself. > > > *** Dmesg output: > > Copyright (c) 1992-2004 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > The Regents of the University of California. All rights reserved. > FreeBSD 5.2.1-RELEASE-p13 #2: Thu Feb 10 18:39:33 CST 2005 > diskiller@diablo.diskiller.net:/junk/obj/junk/src/sys/DIABLO > Preloaded elf kernel "/boot/kernel/kernel" at 0xc076c000. > MPTable: > Timecounter "i8254" frequency 1193182 Hz quality 0 > CPU: Pentium III/Pentium III Xeon/Celeron (504.72-MHz 686-class CPU) > Origin = "GenuineIntel" Id = 0x673 Stepping = 3 > > Features=0x387fbff CMOV,PAT,PSE36,PN,MMX,FXSR,SSE> > real memory = 536870912 (512 MB) > avail memory = 516034560 (492 MB) > FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs > cpu0 (BSP): APIC ID: 0 > cpu1 (AP): APIC ID: 1 > ioapic0: Assuming intbase of 0 > ioapic0 irqs 0-23 on motherboard > Pentium Pro MTRR support enabled > npx0: [FAST] > npx0: on motherboard > npx0: INT 16 interface > pcibios: BIOS version 2.10 > Using $PIR table, 7 entries at 0xc00fdcf0 > pcib0: at pcibus 0 on > motherboard > pci0: on pcib0 > pci_cfgintr: 0:10 INTA BIOS irq 10 > pci_cfgintr: 0:12 INTA BIOS irq 11 > agp0: mem 0xd0000000-0xd3ffffff > at device 0.0 on pci0 > pcib1: at device 1.0 on pci0 > pci1: on pcib1 > isab0: at device 7.0 on pci0 > isa0: on isab0 > atapci0: port 0xf000-0xf00f at device 7.1 on > pci0 > ata0: at 0x1f0 irq 14 on atapci0 > ata0: [MPSAFE] > ata1: at 0x170 irq 15 on atapci0 > ata1: [MPSAFE] > uhci0: port 0xe000-0xe01f at > device 7.2 on pci0 > pci_cfgintr: 0:7 INTD routed to irq 11 > usb0: on uhci0 > usb0: USB revision 1.0 > uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > uhub0: 2 ports with 2 removable, self powered > piix0: port 0x5000-0x500f at device 7.3 on pci0 > Timecounter "PIIX" frequency 3579545 Hz quality 0 > pci0: at device 8.0 (no driver attached) > rl0: port 0xe400-0xe4ff mem > 0xd7000000-0xd70000ff irq 10 at device 10.0 on pci0 > rl0: Ethernet address: 00:00:21:f2:a5:47 > miibus0: on rl0 > rlphy0: on miibus0 > rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > rl1: port 0xe800-0xe8ff mem > 0xd7001000-0xd70010ff irq 11 at device 12.0 on pci0 > rl1: Ethernet address: 00:40:f4:90:1c:4b > miibus1: on rl1 > rlphy1: on miibus1 > rlphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > orm0: