From owner-freebsd-current@FreeBSD.ORG Mon Jun 18 17:44:34 2007 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B92CD16A421 for ; Mon, 18 Jun 2007 17:44:34 +0000 (UTC) (envelope-from maxim@macomnet.ru) Received: from mp2.macomnet.net (mp2.macomnet.net [195.128.64.6]) by mx1.freebsd.org (Postfix) with ESMTP id 3B6A413C484 for ; Mon, 18 Jun 2007 17:44:33 +0000 (UTC) (envelope-from maxim@macomnet.ru) Received: from localhost (localhost.int.ru [127.0.0.1] (may be forged)) by mp2.macomnet.net (8.13.7/8.13.8) with ESMTP id l5IHiWLf039325; Mon, 18 Jun 2007 21:44:32 +0400 (MSD) (envelope-from maxim@macomnet.ru) Date: Mon, 18 Jun 2007 21:44:32 +0400 (MSD) From: Maxim Konovalov To: Kris Kennaway In-Reply-To: <20070618173852.GA74395@rot13.obsecurity.org> Message-ID: <20070618214409.R73282@mp2.macomnet.net> References: <20070617213948.GA50404@rot13.obsecurity.org> <1182171046.1253.10.camel@localhost> <20070618133144.GQ2268@deviant.kiev.zoral.com.ua> <20070618213139.O73282@mp2.macomnet.net> <20070618173852.GA74395@rot13.obsecurity.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: Kostik Belousov , Tom Evans , current@freebsd.org Subject: Re: Userland problems from kern.pts.enable=1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Jun 2007 17:44:34 -0000 On Mon, 18 Jun 2007, 13:38-0400, Kris Kennaway wrote: > On Mon, Jun 18, 2007 at 09:33:24PM +0400, Maxim Konovalov wrote: > > [...] > > > Mentioned patches are at > > > http://people.freebsd.org/~kib/misc/destroy_dev_sched.10.patch > > > > > Btw, I tried the patch recently when discovered script(1) just stuck > > at exit. The patch didn't help. Turning off pts did. > > Are you sure it was this revision? It was believed to be fixed in an > older version. If you are still seeing it, can you please try to > obtain backtraces, lockedvnodes, etc? > I'll try the latest and report results back. -- Maxim Konovalov