From owner-freebsd-current@FreeBSD.ORG Thu Aug 12 12:37:29 2004 Return-Path: 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 1F99B16A4CF for ; Thu, 12 Aug 2004 12:37:29 +0000 (GMT) Received: from mail0.ewetel.de (mail0.ewetel.de [212.6.122.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 58A5E43D45 for ; Thu, 12 Aug 2004 12:37:28 +0000 (GMT) (envelope-from uwe@laverenz.de) Received: from ensign.laverenz.de (dialin-80-228-12-060.ewetel.net [80.228.12.60]) by mail0.ewetel.de (8.12.1/8.12.9) with ESMTP id i7CCbPt4026776 for ; Thu, 12 Aug 2004 14:37:26 +0200 (MEST) Received: from localhost (localhost.laverenz.de [127.0.0.1]) by ensign.laverenz.de (Postfix) with ESMTP id E57D876F42B for ; Thu, 12 Aug 2004 14:37:24 +0200 (CEST) Received: from ensign.laverenz.de ([127.0.0.1]) by localhost (ensign.laverenz.de [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 71559-01-4 for ; Thu, 12 Aug 2004 14:37:17 +0200 (CEST) Received: by ensign.laverenz.de (Postfix, from userid 2000) id 1C1D776F42C; Thu, 12 Aug 2004 14:35:03 +0200 (CEST) Date: Thu, 12 Aug 2004 14:35:02 +0200 From: Uwe Laverenz To: current@freebsd.org Message-ID: <20040812123502.GA71807@ensign.laverenz.de> Mail-Followup-To: current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Organization: private site Sender: uwe@laverenz.de User-Agent: Mutt/1.5.6i X-Virus-Scanned: by amavisd-new at laverenz.de X-CheckCompat: OK Subject: VIA C3M-266 vs. Current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Aug 2004 12:37:29 -0000 Hi, I just wanted to report a quite annoying (for me ;) problem with -CURRENT: I've been running a small server with 5.2.1p9 on a VIA C3M-266 board for several months. This is a micro-ATX board with VIA's CLE-266 chipset for PIII-comaptible CPUs. I experienced problems with rpc.lockd and decided to switch to -CURRENT. I first bootet with a new kernel and the old 5.2.1 userland: no problem. I continued with the upgrade and did the necessary installworld and mergemaster stuff. After the complete upgrade, the machine does not boot correctly anymore, it crashes in or shortly after the bootloader. I don't get any useful error messages. This problem must be related to the VIA motherboard, because the system starts fine with other boards (Asus A7V600, Asus P5A). Is this a known problem? thank you, Uwe