From owner-freebsd-stable Tue Feb 12 21:20:23 2002 Delivered-To: freebsd-stable@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 0AB0737B404; Tue, 12 Feb 2002 21:20:19 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id g1D5JkS96746; Tue, 12 Feb 2002 21:19:46 -0800 (PST) (envelope-from dillon) Date: Tue, 12 Feb 2002 21:19:46 -0800 (PST) From: Matthew Dillon Message-Id: <200202130519.g1D5JkS96746@apollo.backplane.com> To: Bjoern Fischer Cc: freebsd-stable@FreeBSD.ORG, freebsd-bugs@FreeBSD.ORG Subject: Re: Panic in vnlru in 4.5-RELEASE References: <20020212182716.A63685@blazingdot.com> <200202130433.g1D4XXb96360@apollo.backplane.com> <20020213045554.GA3581@frolic.no-support.loc> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG :Hi Matt, : :> Try updating to the latest -stable kernel and tell us if the panic still :> occurs. There was A softupdates bug that caused precisely this problem. :> It was fixed a while ago but the fix just missed the -RELEASE. : :That was MFC 1.104 or 1.103, right? This is not in RELENG_4_5 yet, is it? : :-Björn It takes a great deal of time and testing to commit to -current and MFC to -stable so I usually leave it up to others to decide what to put in RELENG_4_5. Since it is a separate branch it requires a commit rather then a simple cvs tag adjustment (to be safe. Changing branch tags on a regular basis is a great way to screw up a CVS tree). So the answer is: It probably isn't in RELENG_4_5 but you can probably petition security@freebsd.org to get it in. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message