From owner-freebsd-stable@FreeBSD.ORG Wed May 13 15:41:24 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 11135106564A; Wed, 13 May 2009 15:41:24 +0000 (UTC) (envelope-from pluknet@gmail.com) Received: from mail-bw0-f213.google.com (mail-bw0-f213.google.com [209.85.218.213]) by mx1.freebsd.org (Postfix) with ESMTP id 606CB8FC24; Wed, 13 May 2009 15:41:23 +0000 (UTC) (envelope-from pluknet@gmail.com) Received: by bwz9 with SMTP id 9so726231bwz.43 for ; Wed, 13 May 2009 08:41:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=4NyppntDqUj0MUYQNMgaF7wagRZLU+K1stmvcBiaDtE=; b=OvToCQJELnicyrts9ZBZ6Y6jacI+RAxp+uWicToVlDv6EVCsJkEP4MwkPxO6dqGHTB zpLyjX0dzk1/s7sozzlRXw0nwYfkJ4a7RHM2aQ847bWS1rxb0+f0BlZoTAlOzaivYfOk rBVtwuk338/9S2OzuE4bc2iHE9Jaots4xP2Zo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=lz08NFRCTah+vq3uz/9B8lRlL9hV2hUI8pxT5bHN7qcZ+QEUFD0/OoTyVqy94JCpRM 4MhZcVjDdy0/+WFX/3aInO2ZzxGSl1oft7HBxTzSRzXvLsxHEZ4nAUphCCCxniBJkiJp Cg2jW0WKhdbOkvCHS2bB58VRvn8Y1kklpHr6w= MIME-Version: 1.0 Received: by 10.103.240.15 with SMTP id s15mr766218mur.102.1242229282185; Wed, 13 May 2009 08:41:22 -0700 (PDT) In-Reply-To: <200905131015.27431.jhb@freebsd.org> References: <200905131015.27431.jhb@freebsd.org> Date: Wed, 13 May 2009 19:41:22 +0400 Message-ID: From: pluknet To: John Baldwin Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable 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 15:41:24 -0000 2009/5/13 John Baldwin : > 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 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