From owner-freebsd-current@FreeBSD.ORG Wed Oct 26 18:25:27 2005 Return-Path: X-Original-To: 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 8150A16A41F for ; Wed, 26 Oct 2005 18:25:27 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from mv.twc.weather.com (mv.twc.weather.com [65.212.71.225]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1D93543D48 for ; Wed, 26 Oct 2005 18:25:27 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from [10.50.41.234] (Not Verified[10.50.41.234]) by mv.twc.weather.com with NetIQ MailMarshal (v6, 0, 3, 8) id ; Wed, 26 Oct 2005 14:42:11 -0400 From: John Baldwin To: freebsd-current@freebsd.org Date: Wed, 26 Oct 2005 13:59:19 -0400 User-Agent: KMail/1.8.2 References: <20051025230925.GA4354@sandvine.com> In-Reply-To: <20051025230925.GA4354@sandvine.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200510261359.20789.jhb@freebsd.org> Cc: Ed Maste Subject: Re: panic: trying to sleep while sleeping is prohibited (from ttyinfo) 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: Wed, 26 Oct 2005 18:25:27 -0000 On Tuesday 25 October 2005 07:09 pm, Ed Maste wrote: > I just got this panic from my 7.0-CURRENT laptop (Thinkpad T20), > cvsup'd as of Oct 11. I was editing a file in vi at the time. > > -ed > > root@laptop# uname -a > FreeBSD laptop 7.0-CURRENT FreeBSD 7.0-CURRENT #3: Tue Oct 11 18:03:58 EDT > 2005 > emaste_bsd-build.phaedrus.sandvine.com:/d2/emaste/head/obj/d2/emaste/head/s >r c/sys/GENERIC i386 Bah, this is my bug. Looks like you hit Ctrl-T in non-X11. Try the patch at www.freebsd.org/~jhb/patches/ttyinfo.patch It reverts my changes to use the proctree sx lock in ttyinfo and expands use of the proc lock to address my earlier concerns that prompted me to use the proctree lock. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org