Date: Sat, 4 Nov 2006 11:35:23 -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: ULE-scheduler helped (Re: new em-driver still broken) Message-ID: <200611041135.23651@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. Ok. First I tried to cvs the sys/dev/em back to 6.1 -- the new kernel had the same problems... Then I tried to change the 'PCI latency timer' in the BIOS -- from the minimum of 32 to the maximum of 360. Same problems. Then, finally, I decided to give the ULE-scheduler a try -- and things seem to work just fine (with polling enabled on the interface)... The dump has completed -- in 7 hours or so... Could this (failure of the BSD44 scheduler) be due to my using slightly different CPUs (Opteron 244 in the first slot and 246 in the second)? I thought, BIOS/motherboard take care to "downgrade" the second one to match -- according to the dmesg.boot, both processors are identified as: CPU: AMD Opteron(tm) Processor 244 (1800.01-MHz K8-class CPU) But if the scheduler looks at some CPU-local register, it may, in some cases, still think, it is running on 246? To summarize, unless someone else continues to see em-related problems, the current driver is fine, I guess... -mi
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200611041135.23651>