From owner-freebsd-current@FreeBSD.ORG Sat Jun 5 04:22:55 2004 Return-Path: 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 F0F7716A4CE for ; Sat, 5 Jun 2004 04:22:55 -0700 (PDT) Received: from web25201.mail.ukl.yahoo.com (web25201.mail.ukl.yahoo.com [217.12.10.61]) by mx1.FreeBSD.org (Postfix) with SMTP id 2EF7043D1F for ; Sat, 5 Jun 2004 04:22:55 -0700 (PDT) (envelope-from devnullaccount@yahoo.se) Message-ID: <20040605112233.34851.qmail@web25201.mail.ukl.yahoo.com> Received: from [213.100.201.151] by web25201.mail.ukl.yahoo.com via HTTP; Sat, 05 Jun 2004 13:22:33 CEST Date: Sat, 5 Jun 2004 13:22:33 +0200 (CEST) From: =?iso-8859-1?q?some=20one?= To: freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailman-Approved-At: Sat, 05 Jun 2004 04:40:05 -0700 Subject: Network going nuts on -CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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: Sat, 05 Jun 2004 11:22:56 -0000 Hi all! I have a Dell laptop running -CURRENT (built from CVS May 18th, generic kernel except SMP disabled) which most of the time works like a charm. But every now and then when I boot it, the network get horrible delays which makes it unusable. For example, a ping to the local network will give results like 100,93,83,73,63,53,43,33,23,13,100,93 and continue to cycle in the same way. Seems like some read interval gets screwed. I get the same results from both the built-in xl0 and from a pc-card wi0 interface, so it's not a network card hardware issue. When I get to this stage, I cannot get it fixed no matter what I try (rebooting it gets me nowhere). What I found out is that if I reboot kernel.old (5.2.1-RELEASE, GENERIC) and then reboot again and revert to to my current kernel all is well again. Until X number of reboots later, when it appears from nowhere again. I'm completely lost as to what to do to fix it, so any help would be appreciated. I can provide more information from the system, but I don't know how long it'll take 'til next time the error appears, so it's hard to reproducce. TIA, Chris Höstrusk och grå moln - köp en resa till solen på Yahoo! Resor på adressen http://se.docs.yahoo.com/travel/index.html