From owner-freebsd-current@FreeBSD.ORG  Mon Jul 19 05:25:36 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from green.homeunix.org (freefall.freebsd.org [216.136.204.21])
	by hub.freebsd.org (Postfix) with ESMTP
	id 6B6FA16A4CE; Mon, 19 Jul 2004 05:25:36 +0000 (GMT)
Received: from green.homeunix.org (green@localhost [127.0.0.1])
	by green.homeunix.org (8.12.11/8.12.11) with ESMTP id i6J5PZ31001137;
	Mon, 19 Jul 2004 01:25:35 -0400 (EDT)
	(envelope-from green@green.homeunix.org)
Received: (from green@localhost)
	by green.homeunix.org (8.12.11/8.12.11/Submit) id i6J5PZ9R001136;
	Mon, 19 Jul 2004 01:25:35 -0400 (EDT)
	(envelope-from green)
Date: Mon, 19 Jul 2004 01:25:34 -0400
From: Brian Fundakowski Feldman <green@FreeBSD.org>
To: current@FreeBSD.org
Message-ID: <20040719052534.GA1038@green.homeunix.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.6i
Subject: lockups with src/tools/regression/gaithrstress
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Jul 2004 05:25:36 -0000

Running with or without kern.smp.disabled, with a very up-to-date kernel,
I can easily lock up the system by running gaithrstress -t 50 a few times
at once.  There is nothing special that has changed in the last few weeks,
though I have extensive changes to kqueue and VM which I consider entirely
stable at this point.  Anything causing a problem like this seems like it's
due to changes within the last few weeks.

The only clue I have comes from a previous panic() (which promptly just
locked up going into "KDB: enter: panic"), "kse/thread mismatch" as
generated by choosethread().  The connect() system call was trying to
do an mi_switch() inside a mtx_lock() at the time.

-- 
Brian Fundakowski Feldman                           \'[ FreeBSD ]''''''''''\
  <> green@FreeBSD.org                               \  The Power to Serve! \
 Opinions expressed are my own.                       \,,,,,,,,,,,,,,,,,,,,,,\