From owner-freebsd-current@FreeBSD.ORG  Fri Apr  2 09:25:03 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 E723916A4CE
	for <freebsd-current@freebsd.org>;
	Fri,  2 Apr 2004 09:25:03 -0800 (PST)
Received: from demos.bsdclusters.com (demos.bsdclusters.com [69.55.225.36])
	by mx1.FreeBSD.org (Postfix) with ESMTP id B72B943D2D
	for <freebsd-current@freebsd.org>;
	Fri,  2 Apr 2004 09:25:03 -0800 (PST)
	(envelope-from kmacy@fsmware.com)
Received: from demos.bsdclusters.com (demos [69.55.225.36])
	i32HOt5V081360;	Fri, 2 Apr 2004 09:24:55 -0800 (PST)
	(envelope-from kmacy@fsmware.com)
Received: from localhost (kmacy@localhost)i32HOtuA081357;
	Fri, 2 Apr 2004 09:24:55 -0800 (PST)
X-Authentication-Warning: demos.bsdclusters.com: kmacy owned process doing -bs
Date: Fri, 2 Apr 2004 09:24:55 -0800 (PST)
From: Kip Macy <kmacy@fsmware.com>
X-X-Sender: kmacy@demos.bsdclusters.com
To: Artem Koutchine <matrix@itlegion.ru>
In-Reply-To: <00da01c418aa$8247b160$0c00a8c0@artem>
Message-ID: <20040402092303.L64402@demos.bsdclusters.com>
References: <00da01c418aa$8247b160$0c00a8c0@artem>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: freebsd-current@freebsd.org
Subject: Re: 5.2-current  does not allow login and panics with modifiedmemory
 after free
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: Fri, 02 Apr 2004 17:25:04 -0000

> Is this all a twe driver problem or general 5.2-CURRENT instability?
> Any ideas what happened in two cases and how to avoid it or/and
> solve the problems?

Could be either - with the latest snapshot I get the same panic on boot
consistently (but inside of CAM) on my laptop.

			-Kip