From owner-freebsd-stable@FreeBSD.ORG Wed Nov 1 12:53:59 2006 Return-Path: X-Original-To: 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 C09CE16A415; Wed, 1 Nov 2006 12:53:59 +0000 (UTC) (envelope-from mi+kde@aldan.algebra.com) Received: from aldan.algebra.com (aldan.algebra.com [216.254.65.224]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1E3C643D55; Wed, 1 Nov 2006 12:53:58 +0000 (GMT) (envelope-from mi+kde@aldan.algebra.com) Received: from aldan.algebra.com (aldan [127.0.0.1]) by aldan.algebra.com (8.13.8/8.13.7) with ESMTP id kA1CruA0008668 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 1 Nov 2006 07:53:56 -0500 (EST) (envelope-from mi+kde@aldan.algebra.com) Received: from localhost (localhost [[UNIX: localhost]]) by aldan.algebra.com (8.13.8/8.13.7/Submit) id kA1CrtBP008667; Wed, 1 Nov 2006 07:53:55 -0500 (EST) (envelope-from mi+kde@aldan.algebra.com) From: Mikhail Teterin To: "Jack Vogel" Date: Wed, 1 Nov 2006 07:53:55 -0500 User-Agent: KMail/1.9.5 References: <200610282112.k9SLC0cC024602@corbulon.video-collage.com> <20061101015738.090863a2@loki.starkstrom.lan> <2a41acea0610311741w653d5bfdhad49d2f606a7cffe@mail.gmail.com> In-Reply-To: <2a41acea0610311741w653d5bfdhad49d2f606a7cffe@mail.gmail.com> X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7whJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli" Cc: Joerg Pernfuss , stable@freebsd.org, re@freebsd.org Subject: Re: new em-driver still broken 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: Wed, 01 Nov 2006 12:53:59 -0000 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