From owner-freebsd-security@FreeBSD.ORG  Fri Apr 28 11:29:56 2006
Return-Path: <owner-freebsd-security@FreeBSD.ORG>
X-Original-To: freebsd-security@FreeBSD.org
Delivered-To: freebsd-security@FreeBSD.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id E5B8216A403
	for <freebsd-security@FreeBSD.org>;
	Fri, 28 Apr 2006 11:29:56 +0000 (UTC)
	(envelope-from rwatson@FreeBSD.org)
Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42])
	by mx1.FreeBSD.org (Postfix) with ESMTP id A493543D45
	for <freebsd-security@FreeBSD.org>;
	Fri, 28 Apr 2006 11:29:56 +0000 (GMT)
	(envelope-from rwatson@FreeBSD.org)
Received: from fledge.watson.org (fledge.watson.org [209.31.154.41])
	by cyrus.watson.org (Postfix) with ESMTP id 4871A46C2F
	for <freebsd-security@FreeBSD.org>;
	Fri, 28 Apr 2006 07:29:56 -0400 (EDT)
Date: Fri, 28 Apr 2006 12:29:56 +0100 (BST)
From: Robert Watson <rwatson@FreeBSD.org>
X-X-Sender: robert@fledge.watson.org
To: freebsd-security@FreeBSD.org
Message-ID: <20060428122811.P40418@fledge.watson.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: 
Subject: Looking for tor users experiencing crashes
X-BeenThere: freebsd-security@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "Security issues \[members-only posting\]"
	<freebsd-security.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-security>, 
	<mailto:freebsd-security-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-security>
List-Post: <mailto:freebsd-security@freebsd.org>
List-Help: <mailto:freebsd-security-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-security>, 
	<mailto:freebsd-security-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Apr 2006 11:29:57 -0000


I've had an informal, third or fourth hand report of kernel instability when 
running Tor under load on unidentified versions of FreeBSD.  Obviously, this 
is a bit vague as bug reports go, but I'm interested in seeing if anyone has 
had real experience with this happening, and might be interested in helping to 
track it down.  If there are kernel crashes, I'm specifically looking for 
information on what version of FreeBSD is being used, a panic message / trap 
message, DDB stack trace, etc.  I'm assuming it's likely a networking related 
bug, which I'm happy to work on fixing.  If it's not network-related, I can 
certainly try to track someone down who could work on it.

Thanks,

Robert N M Watson