From owner-freebsd-bugs@FreeBSD.ORG Thu Sep 4 15:34:38 2008 Return-Path: Delivered-To: freebsd-bugs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 244C7106564A for ; Thu, 4 Sep 2008 15:34:38 +0000 (UTC) (envelope-from ed@hoeg.nl) Received: from palm.hoeg.nl (mx0.hoeg.nl [IPv6:2001:610:652::211]) by mx1.freebsd.org (Postfix) with ESMTP id D8E6C8FC16 for ; Thu, 4 Sep 2008 15:34:37 +0000 (UTC) (envelope-from ed@hoeg.nl) Received: by palm.hoeg.nl (Postfix, from userid 1000) id 15ECD1CC40; Thu, 4 Sep 2008 17:34:36 +0200 (CEST) Date: Thu, 4 Sep 2008 17:34:36 +0200 From: Ed Schouten To: ben wilber Message-ID: <20080904153436.GU99951@hoeg.nl> References: <200809031003.m83A3xAg069149@freefall.freebsd.org> <20080903112406.GO99951@hoeg.nl> <20080903144844.GP99951@hoeg.nl> <20080903202922.GA2753@exodus.desync.com> <20080904044829.GT99951@hoeg.nl> <20080904094250.GA2825@exodus.desync.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="+lRMm5cUbRiRpMBy" Content-Disposition: inline In-Reply-To: <20080904094250.GA2825@exodus.desync.com> User-Agent: Mutt/1.5.18 (2008-05-17) Cc: freebsd-bugs@FreeBSD.org Subject: Re: kern/127054: [panic] perl causes panic X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Sep 2008 15:34:38 -0000 --+lRMm5cUbRiRpMBy Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hello Ben, * ben wilber wrote: > On Thu, Sep 04, 2008 at 06:48:29AM +0200, Ed Schouten wrote: > > > #11 0xffffffff80524e3f in ptsdev_close (fp=3D0xffffff00057c5808, td= =3DVariable "td" is not available. > > > ) =20 > > > at /usr/src/sys/kern/tty_pts.c:436 >=20 > Sorry, I lost my dump again trying to make DDB scripts work. This is > yet another new one. It seems we're dealing with a very obscure case here: > $4 =3D {t_mtx =3D 0xffffff000587c008, t_mtxobj =3D {lock_object =3D { > lo_name =3D 0xffffffff808952c6 "tty lock", lo_flags =3D 16908288, l= o_data =3D 0,=20 > lo_witness =3D 0x0}, mtx_lock =3D 6}, t_list =3D {tqe_next =3D 0x0,= tqe_prev =3D 0xffffff000530d028},=20 > t_flags =3D 1543831584, t_revokecnt =3D 1, t_inq =3D {ti_list =3D {tqh_= first =3D 0x0,=20 t_flags shouldn't be this high. Converted to hexadecimal, its value is 0x5c050020. The only valid flags here are TF_GONE|TF_EXCLUDE|TF_ZOMBIE. > > t_softc =3D 0xffffff001a30d100, t_dev =3D 0x0} t_dev is 0, which means we're tearing down the TTY. Have you got COMPAT_43TTY enabled in your kernel configuration file? If so, can you reproduce the panic if COMPAT_43TTY is disabled? I think I already see where the problem is. And yes, the bug is quite awful. --=20 Ed Schouten WWW: http://80386.nl/ --+lRMm5cUbRiRpMBy Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEARECAAYFAkjAAAwACgkQ52SDGA2eCwWUGgCcC9Vxa2Kj/GTGmAl4dEIz+P/+ +/gAnj0UTEMTCk3+AOc6AZKM8MacoRyQ =3aHQ -----END PGP SIGNATURE----- --+lRMm5cUbRiRpMBy--