Date: Fri, 24 Jan 2003 14:34:27 +0200 From: "Atte Peltomaki" <atte.peltomaki@iki.fi> To: Terry Lambert <tlambert2@mindspring.com> Cc: freebsd-current@freebsd.org Subject: Re: Performance problems with 5.0-RELEASE Message-ID: <20030124123427.GA2649@naama> In-Reply-To: <3E30C597.8FB82EC9@mindspring.com> References: <20030123162644.GA560@naama> <3E309E58.C0745816@mindspring.com> <20030124040705.GA7945@dan.emsphone.com> <3E30C597.8FB82EC9@mindspring.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> > > 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030124123427.GA2649>