Date: Fri, 23 Oct 2009 17:42:06 -0400 From: Jacob Myers <jacob@whotookspaz.org> To: Jaime Bozza <jbozza@mindsites.com> Cc: "freebsd-stable@freebsd.org" <freebsd-stable@freebsd.org>, Scott Ullrich <sullrich@gmail.com> Subject: Re: Possible scheduler (SCHED_ULE) bug? Message-ID: <4AE2232E.10406@whotookspaz.org> In-Reply-To: <CF092998EA82AE4D83AF9C9ECA9A8BDE02EB411A8E@ATLAS.msg.local> References: <CF092998EA82AE4D83AF9C9ECA9A8BDE02EB411A85@ATLAS.msg.local> <d5992baf0910231149qa4e89fdx2e1cde9b2a529cd3@mail.gmail.com> <CF092998EA82AE4D83AF9C9ECA9A8BDE02EB411A8E@ATLAS.msg.local>
next in thread | previous in thread | raw e-mail | index | archive | help
Jaime Bozza wrote: [snip] > The additional information I have (over the PR) is that: > 1) Files over 64K cause the problem, not just larger files I thought it was over 1 MB or so. But maybe I'm wrong. ISTR that I couldn't trigger it with some images of around 70K. > 2) switching over to SCHED_4BSD eliminates the problem - system no longer locks. I will have to test this. This is indeed interesting... > 3) 7.2 amd64 doesn't have the problem - Tested a similar configuration and was not able to duplicate on amd64 at all. I can replicate this problem on FreeBSD 7.2/amd64 reliably. -- Jacob Myers <Jacob@whotookspaz.org> | Website: http://whotookspaz.org Network Admin, Wilcox Technologies | Public key: 186A424A Using FreeBSD since 2007 | Public shell: http://bit.ly/42iGCR Answer a fool according to his folly, lest he be wise in his own conceit -- Proverbs, 26:5
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4AE2232E.10406>