From owner-freebsd-stable@FreeBSD.ORG Wed May 13 14:27:34 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5030F106564A for ; Wed, 13 May 2009 14:27:34 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 215BC8FC12 for ; Wed, 13 May 2009 14:27:34 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id CA85B46B5C; Wed, 13 May 2009 10:27:33 -0400 (EDT) Received: from jhbbsd.hudson-trading.com (unknown [209.249.190.8]) by bigwig.baldwin.cx (Postfix) with ESMTPA id C77818A026; Wed, 13 May 2009 10:27:32 -0400 (EDT) From: John Baldwin To: pluknet Date: Wed, 13 May 2009 10:15:27 -0400 User-Agent: KMail/1.9.7 References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200905131015.27431.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (bigwig.baldwin.cx); Wed, 13 May 2009 10:27:32 -0400 (EDT) X-Virus-Scanned: clamav-milter 0.95 at bigwig.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.5 required=4.2 tests=AWL,BAYES_00,RDNS_NONE autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on bigwig.baldwin.cx Cc: freebsd-stable@freebsd.org Subject: Re: lock up in 6.2 (procs massively stuck in Giant) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 May 2009 14:27:34 -0000 On Wednesday 13 May 2009 2:40:33 am pluknet wrote: > 2009/5/13 pluknet : > > 2009/5/13 John Baldwin : > >> 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