From owner-freebsd-current Tue Jan 11 3:17: 3 2000 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 113E8153BD for ; Tue, 11 Jan 2000 03:17:02 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) id DAA09813; Tue, 11 Jan 2000 03:40:17 -0800 (PST) Date: Tue, 11 Jan 2000 03:40:16 -0800 From: Alfred Perlstein To: Christian Carstensen Cc: current@FreeBSD.ORG Subject: Re: reported system freezes... Message-ID: <20000111034016.L9397@fw.wintelcom.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from cc@devcon.net on Tue, Jan 11, 2000 at 01:56:44AM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Christian Carstensen [000111 02:03] wrote: > > so, ok, > > i've tried several checkout dates for sys and tested the compiled kernels. > as i cannot reproduce this freeze thing, this is quite vague, but kernels > up to 04 Jan 2000 worked fine, those from 05 Jan 2000 up to now don't. > > maybe, this is useful information. not without your configuration... are you running vinum or softupdates? Kirk just fixed softupdates and I committed a patch to vinum just last night. If you're using vinum don't forget to update your modules, a kernel function was changed that causes it to panic unless your kernel and modules are exactly in sync. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message