2009/5/13 John Baldwin <j...@freebsd.org>: > On Wednesday 13 May 2009 2:40:33 am pluknet wrote: >> 2009/5/13 pluknet <pluk...@gmail.com>: >> > 2009/5/13 John Baldwin <j...@freebsd.org>: >> >> On Tuesday 12 May 2009 4:59:19 pm pluknet wrote: >> >>> Hi. >> >>> >> >>> From just another box (not from the first two mentioned earlier) >> >>> with a similar locking issue. If it would make sense, since there are >> >>> possibly a bit different conditions. >> >>> clock proc here is on swi4, I hope it's a non-important difference. >> >>> >> >>> 18 0 0 0 LL *Giant 0xd0a6b140 [swi4: clock sio] >> >>> db> bt 18 >> >> >> >> Ok, this is a known issue in 6.x. It is fixed in 6.4. >> >> >> >> Looking at the face of kern_timeout.c I suspect that was fixed in r181012. > > No, this particular issue is fixed by a change to sched_4bsd.c in r179975. >
Gah.. We constrained to use ule scheduler on 6.x (yes, I know that "it's known to be broken (c)"), since we have had a very bad interactivity on 4bsd on our workload. Ok, that's just another reason to move to 7.x. Thanks. -- wbr, pluknet _______________________________________________ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
