Date: Wed, 13 May 2009 19:41:22 +0400 From: pluknet <pluknet@gmail.com> To: John Baldwin <jhb@freebsd.org> Cc: freebsd-stable@freebsd.org Subject: Re: lock up in 6.2 (procs massively stuck in Giant) Message-ID: <a31046fc0905130841p6c762d95h40ec989bd0355c9d@mail.gmail.com> In-Reply-To: <200905131015.27431.jhb@freebsd.org> References: <a31046fc0904292336w17aca317hefd32dad5bc28007@mail.gmail.com> <a31046fc0905122245k4ac946c0lcbd29d4557cafab8@mail.gmail.com> <a31046fc0905122340n55785cben89c81736ec790e4c@mail.gmail.com> <200905131015.27431.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
2009/5/13 John Baldwin <jhb@freebsd.org>: > On Wednesday 13 May 2009 2:40:33 am pluknet wrote: >> 2009/5/13 pluknet <pluknet@gmail.com>: >> > 2009/5/13 John Baldwin <jhb@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 ar= e >> >>> possibly a bit different conditions. >> >>> clock proc here is on swi4, I hope it's a non-important difference. >> >>> >> >>> =A0 =A018 =A0 =A0 0 =A0 =A0 0 =A0 =A0 0 =A0LL =A0 =A0 *Giant =A0 =A0= 0xd0a6b140 [swi4: clock sio] >> >>> db> bt 18 >> >> >> >> Ok, this is a known issue in 6.x. =A0It is fixed in 6.4. >> >> >> >> Looking at the face of kern_timeout.c I suspect that was fixed in r18101= 2. > > 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. --=20 wbr, pluknet
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?a31046fc0905130841p6c762d95h40ec989bd0355c9d>