Date: Wed, 13 May 2009 10:40:33 +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: <a31046fc0905122340n55785cben89c81736ec790e4c@mail.gmail.com> In-Reply-To: <a31046fc0905122245k4ac946c0lcbd29d4557cafab8@mail.gmail.com> References: <a31046fc0904292336w17aca317hefd32dad5bc28007@mail.gmail.com> <200905121014.55450.jhb@freebsd.org> <a31046fc0905121359q156d6355ja6a86bf3db193ba2@mail.gmail.com> <200905122046.43048.jhb@freebsd.org> <a31046fc0905122245k4ac946c0lcbd29d4557cafab8@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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 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. Thanks again for the tips. -- wbr, pluknet
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?a31046fc0905122340n55785cben89c81736ec790e4c>