From owner-freebsd-current@FreeBSD.ORG  Fri Aug 27 01:13:42 2004
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 8F4D916A4CE
	for <freebsd-current@freebsd.org>;
	Fri, 27 Aug 2004 01:13:42 +0000 (GMT)
Received: from linda.pathlink.com (linda.pathlink.com [129.250.170.197])
	by mx1.FreeBSD.org (Postfix) with ESMTP id EAA9243D54
	for <freebsd-current@freebsd.org>;
	Fri, 27 Aug 2004 01:13:41 +0000 (GMT)
	(envelope-from kachun@pathlink.com)
Received: from kachun.pathlink.com (dvl-1.pathlink.com [129.250.170.211])
	by linda.pathlink.com (8.12.8p1/8.12.8) with ESMTP id i7R1DfoG029584
	for <freebsd-current@freebsd.org>;
	Thu, 26 Aug 2004 18:13:41 -0700 (PDT)
	(envelope-from kachun@pathlink.com)
Message-Id: <5.0.2.1.2.20040826181101.00b933a0@dvl.pathlink.com>
X-Sender: kachun@dvl.pathlink.com
X-Mailer: QUALCOMM Windows Eudora Version 5.0.2
Date: Thu, 26 Aug 2004 18:13:40 -0700
To: freebsd-current@freebsd.org
From: Kachun Lee <kachun@pathlink.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Subject: Re: 5.3-BETA1 panic with getnewbuf: locked buf
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, 27 Aug 2004 01:13:42 -0000

 >The server (E7501 single XEON 4G RAM) that I upgraded from 4.10 to 
5.3-BETA few days >ago panic'ed twice on 'getnewbuf: locked buf'. I 
included the backtrace and dmesg below. I >searched the lists and found 
several similar instances mentioned. Anything I can help to >find the 
problem. Thanks in advance for any help.

I forget to mention that I already rebuilt its kernel with 1.75 kern_lock.c 
(from current).

Regards
Kachun