From owner-freebsd-current Wed Feb 12 6: 4:46 2003 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 4B1B337B401 for ; Wed, 12 Feb 2003 06:04:44 -0800 (PST) Received: from nebula.wanadoo.fr (ca-sqy-1-243.abo.wanadoo.fr [80.8.54.243]) by mx1.FreeBSD.org (Postfix) with ESMTP id E4E2343F93 for ; Wed, 12 Feb 2003 06:04:40 -0800 (PST) (envelope-from dak@wanadoo.fr) Received: from nebula.wanadoo.fr (localhost.wanadoo.fr [127.0.0.1]) by nebula.wanadoo.fr (8.12.6/8.12.6) with ESMTP id h1CE4VcZ002456 for ; Wed, 12 Feb 2003 15:04:31 +0100 (CET) (envelope-from dak@nebula.wanadoo.fr) Received: (from dak@localhost) by nebula.wanadoo.fr (8.12.6/8.12.6/Submit) id h1CE4V5Z002455 for current@freebsd.org; Wed, 12 Feb 2003 15:04:31 +0100 (CET) Date: Wed, 12 Feb 2003 15:04:31 +0100 From: Aurelien Nephtali To: current@freebsd.org Subject: [SOLVED (NEW SCHEDULER FAULT)] Re: Disk problems (buffers unsynced) Message-ID: <20030212140431.GA711@nebula.wanadoo.fr> References: <20030207064236.GA545@nebula.wanadoo.fr> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="7AUc2qLy4jB3hD7Z" Content-Disposition: inline In-Reply-To: <20030207064236.GA545@nebula.wanadoo.fr> User-Agent: Mutt/1.5.3i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --7AUc2qLy4jB3hD7Z Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi, Those problems are solved if I switch back to the old scheduler (SCHED_4BSD= ). Moreover, with the new scheduler, under high load (CPU ~100%) the system be= came very slow. -- Aurelien On Fri, Feb 07, 2003 at 07:42:36AM +0100, Aurelien Nephtali wrote: > Hi, >=20 > For about two weeks now, each time I halt my computer, all the buffers ar= e not > synced (sometimes they are 1, 2 or 5). > Moreover, when I compile my custom kernel, at the linking stage ("linking > kernel.debug") I got ENOMEM at 0xadress(ad0s1g) (ad0s1g is my /usr slice)= ( > a time I even got a panic with XXX: free mem at bad place or something li= ke > that) >=20 >=20 > Any ideas ? --7AUc2qLy4jB3hD7Z Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE+SlRvDNsbHbt8ok8RAmktAKCd7SXT7MBCPbJOEIhxjlg+56QoAACZAaHh wkrqRabOapPQ8+bGiFABwAA= =ECUO -----END PGP SIGNATURE----- --7AUc2qLy4jB3hD7Z-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message