From owner-freebsd-current@FreeBSD.ORG  Thu Jan 29 14:11:34 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id E5E0916A4CE; Thu, 29 Jan 2004 14:11:34 -0800 (PST)
Received: from gw.catspoiler.org (217-ip-163.nccn.net [209.79.217.163])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 65E7743D73; Thu, 29 Jan 2004 14:11:16 -0800 (PST)
	(envelope-from truckman@FreeBSD.org)
Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2])
	by gw.catspoiler.org (8.12.9p2/8.12.9) with ESMTP id i0TMAm7E088048;
	Thu, 29 Jan 2004 14:10:52 -0800 (PST)
	(envelope-from truckman@FreeBSD.org)
Message-Id: <200401292210.i0TMAm7E088048@gw.catspoiler.org>
Date: Thu, 29 Jan 2004 14:10:48 -0800 (PST)
From: Don Lewis <truckman@FreeBSD.org>
To: emoe@cox.net
In-Reply-To: <IJEJIDFLPIJEPPAPEIHCOEDCCEAA.emoe@cox.net>
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
cc: freebsd-current@FreeBSD.org
cc: jhb@FreeBSD.org
Subject: Re: 5.2-RELEASE panic in turnstile_wait
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: Thu, 29 Jan 2004 22:11:35 -0000

On 29 Jan, Erik Moe wrote:
> How long has this been an issue?  Was this a problem in 5.1-RELEASE as well,
> because I had a few mysterious panics in 5.1 where it look like there was
> memory corruption.

I'm not familiar with the history of the code in question, but I think
the problem has been there quite a while.  I saw the first report of the
problem last November, and it took quite some time to trace it to the
vchan code.