From owner-freebsd-current  Tue May 29  8:55: 9 2001
Delivered-To: freebsd-current@freebsd.org
Received: from green.bikeshed.org (localhost [127.0.0.1])
	by hub.freebsd.org (Postfix) with ESMTP
	id D3DB337B422; Tue, 29 May 2001 08:54:58 -0700 (PDT)
	(envelope-from green@green.bikeshed.org)
Received: from localhost (green@localhost)
	by green.bikeshed.org (8.11.2/8.11.1) with ESMTP id f4TFssf97663;
	Tue, 29 May 2001 11:54:54 -0400 (EDT)
	(envelope-from green@green.bikeshed.org)
Message-Id: <200105291554.f4TFssf97663@green.bikeshed.org>
X-Mailer: exmh version 2.3.1 01/18/2001 with nmh-1.0.4
To: Brian Somers <brian@Awfulhak.org>
Cc: Warner Losh <imp@harmony.village.org>,
	Michael Reifenberger <root@nihil.plaut.de>,
	Doug Barton <DougB@DougBarton.net>, cvs-committers@FreeBSD.org,
	freebsd-current@FreeBSD.org
Subject: Re: cvs commit: src UPDATING 
In-Reply-To: Message from Brian Somers <brian@Awfulhak.org> 
   of "Tue, 29 May 2001 16:04:14 BST." <200105291504.f4TF4EH02212@hak.lan.Awfulhak.org> 
From: "Brian F. Feldman" <green@FreeBSD.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Tue, 29 May 2001 11:54:53 -0400
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-current.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-current>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-current>
X-Loop: FreeBSD.ORG

Brian Somers <brian@Awfulhak.org> wrote:
> > In message <Pine.BSF.4.31.0105290848330.514-100000@nihil> Michael Reifenberger writes:
> > : Have you tried to start aviplay ( coming from ports/graphics/avifile ) or using
> > : whine?
> > 
> > Nope.
> 
> vmware does the job too, and I believe star-office.

I've noticed it, and after backing out locally the commits recently made to 
"lock" LDT access, things work (at least, as well as they used to).  I 
didn't do this hastily;  I spent hours looking at what could possibly be 
wrong with the new locking added, and couldn't find anything :(  I know that 
sched_lock is being held too long, which means (I think) that either somehow 
the code is sleeping with it held or just not releasing it at all.


-- 
 Brian Fundakowski Feldman           \  FreeBSD: The Power to Serve!  /
 green@FreeBSD.org                    `------------------------------'



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message