Date: Wed, 13 May 2009 10:15:27 -0400 From: John Baldwin <jhb@freebsd.org> To: pluknet <pluknet@gmail.com> Cc: freebsd-stable@freebsd.org Subject: Re: lock up in 6.2 (procs massively stuck in Giant) Message-ID: <200905131015.27431.jhb@freebsd.org> In-Reply-To: <a31046fc0905122340n55785cben89c81736ec790e4c@mail.gmail.com> References: <a31046fc0904292336w17aca317hefd32dad5bc28007@mail.gmail.com> <a31046fc0905122245k4ac946c0lcbd29d4557cafab8@mail.gmail.com> <a31046fc0905122340n55785cben89c81736ec790e4c@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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 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. -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200905131015.27431.jhb>