From owner-freebsd-amd64@FreeBSD.ORG  Tue Feb  7 14:44:13 2006
Return-Path: <owner-freebsd-amd64@FreeBSD.ORG>
X-Original-To: freebsd-amd64@FreeBSD.org
Delivered-To: freebsd-amd64@FreeBSD.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id B242F16A420;
	Tue,  7 Feb 2006 14:44:13 +0000 (GMT)
	(envelope-from sgk@troutmask.apl.washington.edu)
Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu
	[128.208.78.105])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 6691E43D49;
	Tue,  7 Feb 2006 14:44:13 +0000 (GMT)
	(envelope-from sgk@troutmask.apl.washington.edu)
Received: from troutmask.apl.washington.edu (localhost [127.0.0.1])
	by troutmask.apl.washington.edu (8.13.4/8.13.4) with ESMTP id
	k17Ei9Wp048655; Tue, 7 Feb 2006 06:44:09 -0800 (PST)
	(envelope-from sgk@troutmask.apl.washington.edu)
Received: (from sgk@localhost)
	by troutmask.apl.washington.edu (8.13.4/8.13.1/Submit) id
	k17Ei9om048654; Tue, 7 Feb 2006 06:44:09 -0800 (PST)
	(envelope-from sgk)
Date: Tue, 7 Feb 2006 06:44:09 -0800
From: Steve Kargl <sgk@troutmask.apl.washington.edu>
To: Robert Watson <rwatson@FreeBSD.org>
Message-ID: <20060207144409.GA48597@troutmask.apl.washington.edu>
References: <20060201235556.GA708@troutmask.apl.washington.edu>
	<20060207104411.GA1067@flame.pc>
	<20060207132335.W37594@fledge.watson.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20060207132335.W37594@fledge.watson.org>
User-Agent: Mutt/1.4.2.1i
Cc: Giorgos Keramidas <keramida@ceid.upatras.gr>, freebsd-current@FreeBSD.org,
	Olivier Houchard <cognet@FreeBSD.org>, freebsd-amd64@FreeBSD.org
Subject: Re: HEADSUP: New pts code triggers panics on amd64 systems.
X-BeenThere: freebsd-amd64@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Porting FreeBSD to the AMD64 platform <freebsd-amd64.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-amd64>,
	<mailto:freebsd-amd64-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-amd64>
List-Post: <mailto:freebsd-amd64@freebsd.org>
List-Help: <mailto:freebsd-amd64-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-amd64>,
	<mailto:freebsd-amd64-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Feb 2006 14:44:13 -0000

On Tue, Feb 07, 2006 at 01:26:24PM +0000, Robert Watson wrote:
> 
> Does the instability occur if kern.pts.enable=0, or only when 
> kern.pts.enable=1?  If 0, if you back out the user space changes but leave 
> tty_pts.c compiled into the kernel, do the instability issues persist?  How 
> about with the kernel code compiled out, but the user space code in place?
> 

I opened a critial PR about this problem.  There is
a backtrace from a kernel panic that shows that there
is either a latent bug in devfs uncovered by pts code
or the pts code is stomping on memory.  I still have the
vmcore.0 file and I may have the matching kernel.

-- 
Steve