From owner-freebsd-current@FreeBSD.ORG Sat Jun 5 14:44:46 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 2FDBF16A4CF for ; Sat, 5 Jun 2004 14:44:46 -0700 (PDT) Received: from mtaw4.prodigy.net (mtaw4.prodigy.net [64.164.98.52]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1B6FE43D2D for ; Sat, 5 Jun 2004 14:44:46 -0700 (PDT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (13419bcbca590f942f36c93171a9c14e@adsl-67-115-73-128.dsl.lsan03.pacbell.net [67.115.73.128]) by mtaw4.prodigy.net (8.12.10/8.12.10) with ESMTP id i55LiifY008992; Sat, 5 Jun 2004 14:44:45 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 4DBC5516F6; Sat, 5 Jun 2004 14:44:44 -0700 (PDT) Date: Sat, 5 Jun 2004 14:44:44 -0700 From: Kris Kennaway To: some one Message-ID: <20040605214444.GB65326@xor.obsecurity.org> References: <20040605112233.34851.qmail@web25201.mail.ukl.yahoo.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="i0/AhcQY5QxfSsSZ" Content-Disposition: inline In-Reply-To: <20040605112233.34851.qmail@web25201.mail.ukl.yahoo.com> User-Agent: Mutt/1.4.2.1i cc: freebsd-current@freebsd.org Subject: Re: 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 21:44:46 -0000 --i0/AhcQY5QxfSsSZ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Jun 05, 2004 at 01:22:33PM +0200, some one wrote: > Hi all! >=20 > 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. I had this problem with SCHED_ULE on sparc64. Reverting to SCHED_4BSD fixed it. Can you confirm that this works for you too? Kris --i0/AhcQY5QxfSsSZ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFAwj7MWry0BWjoQKURAncWAKCa3gejyOe260I4rd7pMfzwXysYKQCg9xq9 TxDn6iLoA+U66w5WRbmv/bI= =WQQ6 -----END PGP SIGNATURE----- --i0/AhcQY5QxfSsSZ--