From owner-freebsd-current@FreeBSD.ORG  Fri May 23 13:06:55 2003
Return-Path: <owner-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 099AD37B401; Fri, 23 May 2003 13:06:55 -0700 (PDT)
Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 1002C43F85; Fri, 23 May 2003 13:06:54 -0700 (PDT)
	(envelope-from phk@phk.freebsd.dk)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
	by critter.freebsd.dk (8.12.9/8.12.9) with ESMTP id h4NK6pLp099396;
	Fri, 23 May 2003 22:06:51 +0200 (CEST)
	(envelope-from phk@phk.freebsd.dk)
To: "Daniel C. Sobral" <dcs@tcoip.com.br>
From: "Poul-Henning Kamp" <phk@phk.freebsd.dk>
In-Reply-To: Your message of "Fri, 23 May 2003 16:15:36 -0300."
             <3ECE7358.4060608@tcoip.com.br> 
Date: Fri, 23 May 2003 22:06:51 +0200
Message-ID: <99395.1053720411@critter.freebsd.dk>
cc: CURRENT <freebsd-current@freebsd.org>
cc: Robert Watson <rwatson@freebsd.org>
Subject: Re: /dev/null panic still alive 
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 23 May 2003 20:06:55 -0000

In message <3ECE7358.4060608@tcoip.com.br>, "Daniel C. Sobral" writes:
>Poul-Henning Kamp wrote:
>> In message <3ECE647B.1030705@tcoip.com.br>, "Daniel C. Sobral" writes:
>> 
>> 
>>>And well. Funny. Something in my daily (or so it seems) caused the 
>>>panic. After which the lockmgr panic attacked. :-( Anyway, core dump for 
>>>the /dev/null:
>> 
>> 
>> This is an attempt to fiddle an EA on a VCHR vnode backed by UFS/FFS.
>> 
>> I currently have no idea how to fix this without doing things to the
>> buffer cache which are not kosher at this time or at all.
>
>/me shrugs
>
>It's just that having a computer with mac enabled panic each time daily 
>is run is kinda bad.

Somewhere, probably under /compat/linux/dev you have some device nodes
on a UFS filesystem.  You shouldn't need those (I think ?) and they
are likely the cause of this.

Kirk's on vacation and I havn't heard back from rwatson what he think
we should do.

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.