From owner-freebsd-bugs@FreeBSD.ORG Thu Aug 28 15:25:40 2008 Return-Path: Delivered-To: freebsd-bugs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B482C106566B for ; Thu, 28 Aug 2008 15:25:40 +0000 (UTC) (envelope-from jchambers@ucla.edu) Received: from out-76.smtp.ucla.edu (out-76.smtp.ucla.edu [169.232.46.169]) by mx1.freebsd.org (Postfix) with ESMTP id 9E5B28FC1F for ; Thu, 28 Aug 2008 15:25:40 +0000 (UTC) (envelope-from jchambers@ucla.edu) Received: from mail.ucla.edu (mail.ucla.edu [169.232.48.151]) by smtp-15.smtp.ucla.edu (8.14.3/8.14.3) with ESMTP id m7SFPBcT028859; Thu, 28 Aug 2008 08:25:11 -0700 Received: from b4dc0ded.local ([149.142.36.207]) (authenticated bits=0) by mail.ucla.edu (8.13.8/8.13.8) with ESMTP id m7SFPAHO003368 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 28 Aug 2008 08:25:10 -0700 Message-ID: <48B6C356.1050700@ucla.edu> Date: Thu, 28 Aug 2008 08:25:10 -0700 From: Jason Chambers Organization: UCLA User-Agent: Thunderbird 2.0.0.16 (Macintosh/20080707) MIME-Version: 1.0 To: gavin@FreeBSD.org References: <200808281514.m7SFENIf001746@freefall.freebsd.org> In-Reply-To: <200808281514.m7SFENIf001746@freefall.freebsd.org> X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Probable-Spam: no X-Scanned-By: smtp.ucla.edu on 169.232.46.242 Cc: freebsd-bugs@FreeBSD.org Subject: Re: kern/126902: Kernel panic during install boot X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Aug 2008 15:25:40 -0000 There was an install of linux on the drives originally which was setup in a LVM I believe. It looked like FreeBSD detected this with GEOM_LABEL messages for each partition then crashed immediately after. The mailing list link I included is for the most part an exact replica of what happened. I had the problem with both i386 and amd64 ports and did not write down the messages. I may have another system to try this on and will update the PR then if it is still open. --Jason