John Baldwin wrote:
On Sunday 15 June 2008 07:23:19 am Stef Walter wrote:
I've been trying to track down a deadlock on some newish production
servers running FreeBSD 6.3-RELEASE-p2. The deadlock occurs on a
specific (although mundane) hardware configuration, and each of several
servers
On Monday 23 June 2008 03:16:40 pm James Gritton wrote:
John Baldwin wrote:
On Thursday 19 June 2008 11:57:51 am James Gritton wrote:
John Baldwin wrote:
On Sunday 15 June 2008 07:23:19 am Stef Walter wrote:
I've been trying to track down a deadlock on some
On Thursday 19 June 2008 11:57:51 am James Gritton wrote:
John Baldwin wrote:
On Sunday 15 June 2008 07:23:19 am Stef Walter wrote:
I've been trying to track down a deadlock on some newish production
servers running FreeBSD 6.3-RELEASE-p2. The deadlock occurs on a
specific (although
John Baldwin wrote:
On Thursday 19 June 2008 11:57:51 am James Gritton wrote:
John Baldwin wrote:
On Sunday 15 June 2008 07:23:19 am Stef Walter wrote:
I've been trying to track down a deadlock on some newish production
servers running FreeBSD 6.3-RELEASE-p2. The deadlock
John Baldwin wrote:
On Sunday 15 June 2008 07:23:19 am Stef Walter wrote:
I've been trying to track down a deadlock on some newish production
servers running FreeBSD 6.3-RELEASE-p2. The deadlock occurs on a
specific (although mundane) hardware configuration, and each of several
servers
On Sunday 15 June 2008 07:23:19 am Stef Walter wrote:
I've been trying to track down a deadlock on some newish production
servers running FreeBSD 6.3-RELEASE-p2. The deadlock occurs on a
specific (although mundane) hardware configuration, and each of several
servers running this hardware
John Baldwin wrote:
Try this change:
jhb 2007-10-27 22:07:40 UTC
snip
We use it at work on 6.x. W/o this fix, round-robin stops working on 4BSD
when softclock() (swi4: clock) blocks on a lock like Giant.
Awesome. Thanks. That looks like it'll do the trick. I'll deploy it and
