Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 20 Jun 2005 15:36:13 -0400
From:      Suleiman Souhlal <ssouhlal@FreeBSD.org>
To:        Maksim Yevmenkin <maksim.yevmenkin@savvis.net>
Cc:        freebsd-current@FreeBSD.org
Subject:   Re: ufs LOR
Message-ID:  <FB67401C-3AE6-4DA8-AB6D-E70293AB6920@FreeBSD.org>
In-Reply-To: <42B6FFE4.4030807@savvis.net>
References:  <42B6FFE4.4030807@savvis.net>

next in thread | previous in thread | raw e-mail | index | archive | help
Hi,

On Jun 20, 2005, at 1:41 PM, Maksim Yevmenkin wrote:

> Hello,
>
> after upgrading to recent -current
>
> beetle% uname -a
> FreeBSD beetle.digisle.com 6.0-CURRENT FreeBSD 6.0-CURRENT #3: Fri  
> Jun 17 10:57:03 PDT 2005 max@beetle.digisle.com:/usr/obj/usr/src/ 
> sys/GENERIC i386
>
> i'm getting the following LOR (see below). the easiest way to  
> reproduce it (for me) is to run 'make buildworld/buildkernel'. my / 
> var/log/messages flooded with the same traces while make is running.
>
> would person who is responsible for this please fix it or please  
> back it out.

This has been reported many times last week, and I even posted a  
patch: http://people.freebsd.org/~ssouhlal/testing/ 
knlist_locking-20050618.diff. I'm just waiting for approval from jmg@  
(and then re@) to commit it.

--
Suleiman Souhlal     | ssouhlal@vt.edu
The FreeBSD Project  | ssouhlal@FreeBSD.org




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?FB67401C-3AE6-4DA8-AB6D-E70293AB6920>