From owner-freebsd-current  Sun Feb 18 18:35:49 2001
Delivered-To: freebsd-current@freebsd.org
Received: from ns.altadena.net (ns.altadena.net [206.126.144.2])
	by hub.freebsd.org (Postfix) with ESMTP id C6A7337B401
	for <current@freebsd.org>; Sun, 18 Feb 2001 18:35:47 -0800 (PST)
Received: (from pete@localhost)
	by ns.altadena.net (8.11.2/8.8.8) id f1J2XpC25216
	for current@freebsd.org; Sun, 18 Feb 2001 18:33:51 -0800 (PST)
	(envelope-from pete)
From: Pete Carah <pete@ns.altadena.net>
Message-Id: <200102190233.f1J2XpC25216@ns.altadena.net>
Subject: Re:  Make kernel fail in modules after upgrade 4.2 -> 5.0
To: current@freebsd.org
Date: Sun, 18 Feb 2001 18:33:51 -0800 (PST)
X-Mailer: ELM [version 2.4ME+ PL68 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=iso8859-1
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

This may relate to a commit about noon (PST) today fixing a different
problem.  I'm just waiting it out :-)

Welcome to "current" where (especially lately) about half the time things 
don't 'make'...  (I'm trying to recompile my kernel after recovering 
from the libc circus, trying to prevent some new panics)

During the fixing stages of the libc problem, vinum caused panics fairly 
regularly for me (very early on or during fsck).

I'm now seeing panics in ufs write after medium heavy activity (make world, 
no -j) on SMP, no reg dump comes out. Complains about table inconsistent 
(don't remember the precise message).  Hopefully my hardware is OK; this 
machine has been stable for several weeks with upgraded RAM.

-- Pete


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