Date: Fri, 23 Oct 2009 15:52:26 -0500 From: Jaime Bozza <jbozza@mindsites.com> To: Scott Ullrich <sullrich@gmail.com> Cc: "freebsd-stable@freebsd.org" <freebsd-stable@freebsd.org>, "jacob@whotookspaz.org" <jacob@whotookspaz.org> Subject: RE: Possible scheduler (SCHED_ULE) bug? Message-ID: <CF092998EA82AE4D83AF9C9ECA9A8BDE02EB411A8E@ATLAS.msg.local> In-Reply-To: <d5992baf0910231149qa4e89fdx2e1cde9b2a529cd3@mail.gmail.com> References: <CF092998EA82AE4D83AF9C9ECA9A8BDE02EB411A85@ATLAS.msg.local> <d5992baf0910231149qa4e89fdx2e1cde9b2a529cd3@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> Try adding this or changing these items in lighttpd.conf: > > ## FreeBSD! > server.event-handler = "freebsd-kqueue" > server.network-backend = "writev" Scott, Lighttpd was already using freebsd-kqueue, but I added the writev network-backend and the problem went away. With this additional information I was able to track down kern/138999, which seems to be the exact issue I'm having. The additional information I have (over the PR) is that: 1) Files over 64K cause the problem, not just larger files 2) switching over to SCHED_4BSD eliminates the problem - system no longer locks. 3) 7.2 amd64 doesn't have the problem - Tested a similar configuration and was not able to duplicate on amd64 at all. I'm CC'ing the original submitter of the PR to give him an update to see if he had any additional luck. Jaime
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CF092998EA82AE4D83AF9C9ECA9A8BDE02EB411A8E>