From owner-freebsd-current Fri Jan 24 4:32:51 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 2DA9A37B401 for ; Fri, 24 Jan 2003 04:32:50 -0800 (PST) Received: from mail1.luukku.com (ultra45.almamedia.fi [193.209.83.53]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0543443E4A for ; Fri, 24 Jan 2003 04:32:49 -0800 (PST) (envelope-from atte.peltomaki@iki.fi) Received: by mail1.luukku.com (Postfix, from userid 60001) id 7FE391BA3A4; Fri, 24 Jan 2003 14:32:42 +0200 (EET) Received: from kameli.org (ip213-185-39-29.laajakaista.mtv3.fi [213.185.39.29]) by mail1.luukku.com (Postfix) with SMTP id 38F861BA3A4; Fri, 24 Jan 2003 14:32:42 +0200 (EET) Received: by kameli.org (sSMTP sendmail emulation); Fri, 24 Jan 2003 14:34:27 +0200 Date: Fri, 24 Jan 2003 14:34:27 +0200 From: "Atte Peltomaki" To: Terry Lambert Cc: freebsd-current@freebsd.org Subject: Re: Performance problems with 5.0-RELEASE Message-ID: <20030124123427.GA2649@naama> References: <20030123162644.GA560@naama> <3E309E58.C0745816@mindspring.com> <20030124040705.GA7945@dan.emsphone.com> <3E30C597.8FB82EC9@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <3E30C597.8FB82EC9@mindspring.com> User-Agent: Mutt/1.4i 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 > > > If you lean on the keyboard, or if you set up the network adapters > > > as "entropy" sources, does the problem fix itself? > > > > If you're thinking it's /dev/random blocking on him, 5.0's output never > > blocks. Its output is a PRNG periodically seeded from random data, > > including interrupt timings and LAN traffic by default. > > Mostly, I was thinking that the other suggestions (WITNESS, > INVARIANTS, malloc flags) didn't really have any chance of > being the cause of the lock-ups, and without some message on > the console, it's unlikely that it was a driver tiemout, either. No messages on console. > If it's long enough to pause the console noticibly, the next > thing to try is breaking to the debugger -- which might require > an NMI card -- to see what code it's stuck in during the pause. It's noticeable - if you type under heavy load in console, you experience similar to ssh lag - you can't see what you type, but it appears a second later to the screen. I've spoken about this issue on IRC for a few times, and ran into a guy who said he was experiencing similar problems on 5.0-REL. Just to let you know. I've tried adding HR< to malloc.conf and removing ALL unneccessary options from the kernel, no help. Atte Peltomäki http://kameli.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message