From owner-freebsd-stable@FreeBSD.ORG Thu Feb 10 11:53:51 2005 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 3D6B016A4CF for ; Thu, 10 Feb 2005 11:53:51 +0000 (GMT) Received: from mail.gmx.net (mail.gmx.de [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id BEDD943D31 for ; Thu, 10 Feb 2005 11:53:49 +0000 (GMT) (envelope-from emanuel.strobl@gmx.net) Received: (qmail invoked by alias); 10 Feb 2005 11:53:48 -0000 Received: from flb.schmalzbauer.de (EHLO cale.flintsbach.schmalzbauer.de) (62.245.232.135) by mail.gmx.net (mp005) with SMTP; 10 Feb 2005 12:53:48 +0100 X-Authenticated: #301138 From: Emanuel Strobl To: freebsd-stable@freebsd.org Date: Thu, 10 Feb 2005 12:53:48 +0100 User-Agent: KMail/1.7.2 References: In-Reply-To: X-Birthday: 10/06/72 X-CelPhone: +49 173 9967781 X-Tel: +49 89 18947781 X-Country: Germany X-Address: Munich, 80686 X-OS: FreeBSD MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart2107250.0NrrVKbHPP"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200502101253.58985@harrymail> X-Y-GMX-Trusted: 0 cc: Martin Minkus cc: stable@freebsd.org Subject: Re: 5.3-Stable network issue 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: Thu, 10 Feb 2005 11:53:51 -0000 --nextPart2107250.0NrrVKbHPP Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Am Donnerstag, 10. Februar 2005 11:00 schrieb Martin Minkus: > 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 =B3hoping=B2 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=B9s. 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. Just a wils guess: Try setteing 'debug.mpsafet=3D0' in /boot/loader.conf I had similar problems with pf and RELENG_5=20 No soultion though :( =2DHarry > > 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 f= or > 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... B= ut > 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 =3D "GenuineIntel" Id =3D 0x673 Stepping =3D 3 > > Features=3D0x387fbff, CMOV,PAT,PSE36,PN,MMX,FXSR,SSE> > real memory =3D 536870912 (512 MB) > avail memory =3D 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-0xd3ffff= ff > 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: