From owner-freebsd-threads@FreeBSD.ORG Thu Feb 23 09:50:11 2006 Return-Path: X-Original-To: freebsd-threads@hub.freebsd.org Delivered-To: freebsd-threads@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 18A2416A420 for ; Thu, 23 Feb 2006 09:50:11 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id D583943D53 for ; Thu, 23 Feb 2006 09:50:07 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k1N9o7wW098224 for ; Thu, 23 Feb 2006 09:50:07 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k1N9o7JY098223; Thu, 23 Feb 2006 09:50:07 GMT (envelope-from gnats) Date: Thu, 23 Feb 2006 09:50:07 GMT Message-Id: <200602230950.k1N9o7JY098223@freefall.freebsd.org> To: freebsd-threads@FreeBSD.org From: Ivan Getta Cc: Subject: Re: threads/93592: Loss of wakeup in pthread_cond_timedwait(), libpthread (KSE), Intel Hyper-Threading Technology (HTT), FreeBSD Production Release 6.0 X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Ivan Getta List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Feb 2006 09:50:11 -0000 The following reply was made to PR threads/93592; it has been noted by GNATS. From: Ivan Getta To: freebsd-gnats-submit@freebsd.org, Cc: Daniel Eischen Subject: Re: threads/93592: Loss of wakeup in pthread_cond_timedwait(), libpthread (KSE), Intel Hyper-Threading Technology (HTT), FreeBSD Production Release 6.0 Date: Thu, 23 Feb 2006 11:42:48 +0200 On Tuesday 21 February 2006 04:43, Daniel Eischen wrote: > Try this patch: > > =A0 http://people.freebsd.org/~deischen/kse/libpthread.diffs.022006 Ok, we had set up this patch and run the test during ~14 hours - it seems like problem is resolved. Thank you for such a fast help!