From owner-freebsd-amd64@FreeBSD.ORG Tue Feb 7 14:16:06 2006 Return-Path: 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 C7B0D16A420 for ; Tue, 7 Feb 2006 14:16:06 +0000 (GMT) (envelope-from garyj@jennejohn.org) Received: from mail08a.verio.de (mail08a.verio.de [213.198.55.73]) by mx1.FreeBSD.org (Postfix) with SMTP id CE9D043D49 for ; Tue, 7 Feb 2006 14:16:04 +0000 (GMT) (envelope-from garyj@jennejohn.org) Received: from mx19.stngva01.us.mxservers.net (204.202.242.102) by mail08a.verio.de (RS ver 1.0.95vs) with SMTP id 0-0198921750; Tue, 7 Feb 2006 15:16:03 +0100 (CET) Received: from www.jennejohn.org [213.198.5.174] (EHLO peedub.jennejohn.org) by mx19.stngva01.us.mxservers.net (mxl_mta-1.3.8-10p4) with ESMTP id 79ba8e34.6132.375.mx19.stngva01.us.mxservers.net; Tue, 07 Feb 2006 09:15:51 -0500 (EST) Received: from jennejohn.org (localhost [127.0.0.1]) by peedub.jennejohn.org (8.13.4/8.11.6) with ESMTP id k17EF03v001858; Tue, 7 Feb 2006 15:15:00 +0100 (CET) (envelope-from garyj@jennejohn.org) Message-Id: <200602071415.k17EF03v001858@peedub.jennejohn.org> X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.0.4 To: Robert Watson In-Reply-To: Message from Robert Watson of "Tue, 07 Feb 2006 13:26:24 GMT." <20060207132335.W37594@fledge.watson.org> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Date: Tue, 07 Feb 2006 15:15:00 +0100 From: Gary Jennejohn Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by peedub.jennejohn.org id k17EF03v001858 X-Spam: [F=0.0100000000; heur=0.500(-19800); stat=0.010; spamtraq-heur=0.500(2006020620)] X-MAIL-FROM: X-SOURCE-IP: [213.198.5.174] X-Loop-Detect: 1 X-DistLoop-Detect: 1 Cc: Giorgos Keramidas , freebsd-current@FreeBSD.org, Olivier Houchard , 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Feb 2006 14:16:06 -0000 Robert Watson writes: > Does the instability occur if kern.pts.enable=3D0, or only when=20 > kern.pts.enable=3D1? If 0, if you back out the user space changes but = leave=20 > tty_pts.c compiled into the kernel, do the instability issues persist? = How=20 > about with the kernel code compiled out, but the user space code in pla= ce? >=20 > Basically, it would be good to know if what you're seeing is a property= of th > e=20 > pts code being in the kernel at all, or a property of it actually in us= e.=20 > The former might be indicate that a memory layout change or devfs behav= ioral=20 > change has triggered an existing bug previously masked, whereas the lat= ter=20 > more likely signals a bug in the pts code or a bug in devfs generated b= y=20 > virtue of the deletion of device nodes. That some of the panics happen= very=20 > early (perhaps before a pts device is actually allocated) is suggestive= ... I was running 32-bit so I rebooted to 64-bit. kern.pts.enable was 0=A0so I set it to 1 and started X. This automaticall= y starts an mrxvt with 3 virtual terminals. Everything was OK and ``tty'' showed /dev/pts/{0,1,2}, as expected. I didn't try booting with an entry in loader.conf to set kern.pts.enable to 1. I'm now back running 32-bit with kern.pts.enable set to 1 in X with a whole slew of mrxvt's running and I see no problems here either. The only difference is that ``w'' doesn't show any of the /dev/pts entries although I have 7 active. --- Gary Jennejohn / garyjATjennejohnDOTorg gjATfreebsdDOTorg garyjATdenxDOTd= e