From owner-freebsd-stable@FreeBSD.ORG Fri Jun 2 08:02:50 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org 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 A0D4116A6D2 for ; Fri, 2 Jun 2006 08:02:50 +0000 (UTC) (envelope-from rink@rink.nu) Received: from mx0.rink.nu (thunderstone.rink.nu [80.112.228.34]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2AE0143D45 for ; Fri, 2 Jun 2006 08:02:49 +0000 (GMT) (envelope-from rink@rink.nu) Received: from localhost (localhost [127.0.0.1]) by mx0.rink.nu (Postfix) with ESMTP id B1B4C170B1; Fri, 2 Jun 2006 10:02:51 +0200 (CEST) X-Virus-Scanned: amavisd-new at rink.nu Received: from mx0.rink.nu ([127.0.0.1]) by localhost (thunderstone.rink.nu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9rghcX7Lhqk7; Fri, 2 Jun 2006 08:02:46 +0000 (UTC) Received: by mx0.rink.nu (Postfix, from userid 1678) id D2253170B0; Fri, 2 Jun 2006 10:02:46 +0200 (CEST) Date: Fri, 2 Jun 2006 10:02:46 +0200 From: Rink Springer To: Jack Vogel Message-ID: <20060602080246.GC3769@rink.nu> References: <2a41acea0606011530wf7bca5du23711fbfbfbc81@mail.gmail.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="MfFXiAuoTsnnDAfZ" Content-Disposition: inline In-Reply-To: <2a41acea0606011530wf7bca5du23711fbfbfbc81@mail.gmail.com> User-Agent: Mutt/1.5.11 Cc: freebsd-stable@freebsd.org Subject: Re: long timeout on boot X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Jun 2006 08:02:50 -0000 --MfFXiAuoTsnnDAfZ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi, > Both on my own machine, and on systems in our test group's lab, we > notice these long (like 2min maybe?) delays near the end of boot. It > seems to be ATA/SATA related. It has just announced the one disk > it discovered, then shows the CPUs launched, and then it just sits > printing nothing for, like I said, maybe a minute or two. Finally it will > complete boot and all seems to be fine. >=20 > I am guessing its in a detection loop maybe? Any ideas?? Oh, > this is 6.1 RELEASE on i386, although I'm pretty sure x86_64 > will show the same behavior. I also have this problem, it only showed up on 6-STABLE and 6.1-RELEASE (not 6.0-RELEASE AFAICT). Strangely enough, it does not happen on all my machines, my Dual Opteron has no problems but both my Dual P3 and Dual Athlon MP suffer from this. Another Dual MP I have access to shows this long timeout as well. I have tried to track this down; the problem seems to be that once initialization is completed, quite a few runs are needed to find the process to be scheduled; the offending function seems to be scheduler() in vm/vm_glue.c. I was unable to determine why this is exactly, but I'd love to help in tracking this down. Regards, --=20 Rink P.W. Springer - http://rink.nu "Richter: Tribute? You steal men's souls, and make them your slaves! Dracula: Perhaps the same could be said of all religions." - Castlevania: Symphony of the Night --MfFXiAuoTsnnDAfZ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEf/Cmb3O60uztv/8RAgN1AKC75EEHS7e4a7oNdR+0Cawe0yWeoQCfRK9+ zKpDeYAVtI9GQgAb4yeoL3Y= =WOGU -----END PGP SIGNATURE----- --MfFXiAuoTsnnDAfZ--