Date: Wed, 1 Nov 2006 07:53:55 -0500 From: Mikhail Teterin <mi+kde@aldan.algebra.com> To: "Jack Vogel" <jfvogel@gmail.com> Cc: Joerg Pernfuss <elessar@bsdforen.de>, stable@freebsd.org, re@freebsd.org Subject: Re: new em-driver still broken Message-ID: <200611010753.55556@aldan> In-Reply-To: <2a41acea0610311741w653d5bfdhad49d2f606a7cffe@mail.gmail.com> References: <200610282112.k9SLC0cC024602@corbulon.video-collage.com> <20061101015738.090863a2@loki.starkstrom.lan> <2a41acea0610311741w653d5bfdhad49d2f606a7cffe@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tuesday 31 October 2006 20:41, Jack Vogel wrote: = I still think it looks like some kind of scheduler issue going on = here, so maybe this is something to check. Why would the scheduler affect the "sys" component of the load (which shoots to the sky before the machine drops of the network)? I thought, it only matters for user-space programs (the order in which they run)... Also, if this were a scheduler problem, why would pressing Shift on the keyboard wake everything up? -mi
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200611010753.55556>