From owner-freebsd-current@FreeBSD.ORG Thu Jul 29 23:59:54 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 659C316A4CF for ; Thu, 29 Jul 2004 23:59:54 +0000 (GMT) Received: from mail.parodius.com (mail.parodius.com [64.62.145.229]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4642D43D64 for ; Thu, 29 Jul 2004 23:59:54 +0000 (GMT) (envelope-from jdc@pentarou.parodius.com) Received: from pentarou.parodius.com (jdc@localhost [127.0.0.1]) by mail.parodius.com (8.12.11/8.12.11) with ESMTP id i6TNxnlt002280 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 29 Jul 2004 16:59:49 -0700 (PDT) (envelope-from jdc@pentarou.parodius.com) Received: (from jdc@localhost) by pentarou.parodius.com (8.12.11/8.12.11/Submit) id i6TNxna2002279 for freebsd-current@freebsd.org; Thu, 29 Jul 2004 16:59:49 -0700 (PDT) (envelope-from jdc) Date: Thu, 29 Jul 2004 16:59:49 -0700 From: Jeremy Chadwick To: freebsd-current@freebsd.org Message-ID: <20040729235949.GA2185@parodius.com> Mail-Followup-To: freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.6i Subject: Latest CVS: disklabel broken? 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, 29 Jul 2004 23:59:54 -0000 Greetings. I've managed to confirm a "problem" (note quotes) with disklabel on the latest cvs. After upgrading the machine (buildworld/buildkernel/installkernel, reboot in single user, installworld) and doing `disklabel -B ad0s1', the transition between boot0 and boot1 causes an exception error, panics, and then reboots. I've got two completely different -CURRENT systems which both do this with the latest cvs. Is this related to the gcc 3.4 import? Am I doing something wrong with disklabel? I'm in somewhat of a major fix with this issue, as I now have a pseudo- production server that's dead (yes yes, I know, don't run -CURRENT on servers... someone backport SATA support to -STABLE then :P), and a home workstation that's constantly rebooting as well. To clarify what's happening: F1 FreeBSD F5 Drive 1 Default: F1 Can anyone else confirm this? Thanks. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. |