From owner-freebsd-threads@FreeBSD.ORG  Mon Jun 21 00:12:46 2004
Return-Path: <owner-freebsd-threads@FreeBSD.ORG>
Delivered-To: freebsd-threads@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 4EE2916A4CE; Mon, 21 Jun 2004 00:12:46 +0000 (GMT)
Received: from fledge.watson.org (fledge.watson.org [204.156.12.50])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id B898443D5A; Mon, 21 Jun 2004 00:12:41 +0000 (GMT)
	(envelope-from robert@fledge.watson.org)
Received: from fledge.watson.org (localhost [127.0.0.1])
	by fledge.watson.org (8.12.11/8.12.11) with ESMTP id i5L0ANRM018858;
	Sun, 20 Jun 2004 20:10:23 -0400 (EDT)
	(envelope-from robert@fledge.watson.org)
Received: from localhost (robert@localhost)i5L0ANDY018855;
	Sun, 20 Jun 2004 20:10:23 -0400 (EDT)
	(envelope-from robert@fledge.watson.org)
Date: Sun, 20 Jun 2004 20:10:23 -0400 (EDT)
From: Robert Watson <rwatson@FreeBSD.org>
X-Sender: robert@fledge.watson.org
To: threads@FreeBSD.org
Message-ID: <Pine.NEB.3.96L.1040620200617.5500D-100000@fledge.watson.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: current@FreeBSD.org
Subject: calcru: negative time ... followed by freeze
X-BeenThere: freebsd-threads@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Threading on FreeBSD <freebsd-threads.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-threads>,
	<mailto:freebsd-threads-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-threads>
List-Post: <mailto:freebsd-threads@freebsd.org>
List-Help: <mailto:freebsd-threads-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-threads>,
	<mailto:freebsd-threads-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Jun 2004 00:12:46 -0000


I've now seen the following scenario happen several times in the last few
days while doing testing and benchmarking: I run a multi-threaded test,
such as super-smack, that causes a moderately high system load.  I then
hit Ctrl-T or run top, or some other activity that forces calcru() to
execute.  I will not infrequently get an extremely hard hang -- can't get
to DDB using serial break, etc.  I don't remember it happening when using
non-threaded apps, so I'm wondering if there's a poor interaction with
KSE/scheduler/who knows what.

 7:55PM  up 6 mins, 2 users, load averages: 1.37, 0.91, 0.43
USER             TTY      FROM              LOGIN@  IDLE WHAT
root             d0       -                 7:55PM     - w
rwatson          p0       cboss             7:50PM     2 super-smack
select-key
hippy# top
calcru: negative time of 1834075 usec for pid 654 (super-smack)
ca~~

In this case, I ran super-smack with the following parameters:

hippy:/usr/tmp/super-smack> super-smack select-key.smack 15 1000

This generates 15 workers, which should cause mysql to spawn off threads
as well.  I'm running with stock libpthread on this system (slightly old)
but an up-to-date kernel from CVS, GENERIC.

Has anyone else seen this?

Robert N M Watson             FreeBSD Core Team, TrustedBSD Projects
robert@fledge.watson.org      Senior Research Scientist, McAfee Research