From owner-freebsd-current@FreeBSD.ORG Thu Jun 30 15:41:13 2005 Return-Path: X-Original-To: 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 BAA9A16A41C for ; Thu, 30 Jun 2005 15:41:13 +0000 (GMT) (envelope-from matt@gsicomp.on.ca) Received: from skippyii.compar.com (webpos.compar.com [216.208.38.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4820743D1D for ; Thu, 30 Jun 2005 15:41:09 +0000 (GMT) (envelope-from matt@gsicomp.on.ca) Received: from hermes (CPE00062566c7bb-CM000039c69a66.cpe.net.cable.rogers.com [70.28.254.189]) by skippyii.compar.com (8.13.1/8.13.1) with ESMTP id j5UFpwX0029070; Thu, 30 Jun 2005 11:52:03 -0400 (EDT) (envelope-from matt@gsicomp.on.ca) Message-ID: <001f01c57d8a$23217040$1200a8c0@gsicomp.on.ca> From: "Matt Emmerton" To: "Roman Kurakin" , References: <42C40B98.5070309@cronyx.ru> Date: Thu, 30 Jun 2005 11:41:01 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="KOI8-R" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1437 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 Cc: Subject: Re: Console freeze 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: Thu, 30 Jun 2005 15:41:13 -0000 > Hi, > > I am getting console freeze with recent current. I've seen the same > a year ago > on current and the proble is still here. One of the console freeze I've > seen while > intensive output from my driver (that is async driver). The other one > I've seen > whille cvs update (for example on alt+f2 cvs update -d . > .z; on alt+f3 > tail -f .z). > > console freeze: > screen contains the last output or blank, currsor IIRC always availabe > and it > moves according to its usual behaviour so terminal is functional but no > output. > > Any ideas? IIRC, there was a discussion here lately about a race condition that is being worked on (fixed?) caused by precisely what you describe -- a cvsup (or other output-intensive process) redirecting to a file in one window, and a tail on said file in another window. How recent is your -current? -- Matt