Date: Wed, 1 Nov 2006 09:23:52 -0500 From: Mikhail Teterin <mi+mx@aldan.algebra.com> To: "Jack Vogel" <jfvogel@gmail.com> Cc: stable@freebsd.org, re@freebsd.org Subject: Re: new em-driver still broken Message-ID: <200611010923.52414.mi%2Bmx@aldan.algebra.com> In-Reply-To: <2a41acea0610311643y7360cbc4ie4a2a16b66e4b1e@mail.gmail.com> References: <200610282112.k9SLC0cC024602@corbulon.video-collage.com> <200610311937.32326.Mikhail.Teterin@murex.com> <2a41acea0610311643y7360cbc4ie4a2a16b66e4b1e@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
в╕второк 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200611010923.52414.mi%2Bmx>