From owner-freebsd-stable@FreeBSD.ORG Wed Nov 1 14:24:00 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 780DE16A415; Wed, 1 Nov 2006 14:24:00 +0000 (UTC) (envelope-from mi+mx@aldan.algebra.com) Received: from corbulon.video-collage.com (static-151-204-231-237.bos.east.verizon.net [151.204.231.237]) by mx1.FreeBSD.org (Postfix) with ESMTP id 83CB443D4C; Wed, 1 Nov 2006 14:23:59 +0000 (GMT) (envelope-from mi+mx@aldan.algebra.com) Received: from mteterin.us.murex.com (mx-broadway [38.98.68.18]) by corbulon.video-collage.com (8.13.8/8.13.8) with ESMTP id kA1ENwVo027375 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 1 Nov 2006 09:23:58 -0500 (EST) (envelope-from mi+mx@aldan.algebra.com) From: Mikhail Teterin Organization: Virtual Estates, Inc. To: "Jack Vogel" Date: Wed, 1 Nov 2006 09:23:52 -0500 User-Agent: KMail/1.9.5 References: <200610282112.k9SLC0cC024602@corbulon.video-collage.com> <200610311937.32326.Mikhail.Teterin@murex.com> <2a41acea0610311643y7360cbc4ie4a2a16b66e4b1e@mail.gmail.com> In-Reply-To: <2a41acea0610311643y7360cbc4ie4a2a16b66e4b1e@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-u" Content-Transfer-Encoding: 8bit Content-Disposition: inline Message-Id: <200611010923.52414.mi+mx@aldan.algebra.com> X-Virus-Scanned: ClamAV 0.88.4/2136/Tue Oct 31 22:06:48 2006 on corbulon.video-collage.com X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.43 Cc: 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 14:24:00 -0000 в╕второк 31 жовтень 2006 19:43, Jack Vogel написав: > This is fairly bizarre :) I think I can say pretty safely that this is NOT > an em driver issue, its a scheduler problem of some sort. Am I the only one having problems with em driver? In its latest 6.x-incarnation? Or is the "enabled DEVICE_POLLING, but don't enable polling" supposed to work? I seem to remember BDE saying, that the driver can cause problem even in the "slow-interrupt" mode on SMP machines -- just less often (as in my case)... -mi