From owner-freebsd-sparc64@FreeBSD.ORG  Fri Jan  4 23:46:36 2013
Return-Path: <owner-freebsd-sparc64@FreeBSD.ORG>
Delivered-To: freebsd-sparc64@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by hub.freebsd.org (Postfix) with ESMTP id 7740AB27
 for <freebsd-sparc64@freebsd.org>; Fri,  4 Jan 2013 23:46:36 +0000 (UTC)
 (envelope-from marius@alchemy.franken.de)
Received: from alchemy.franken.de (alchemy.franken.de [194.94.249.214])
 by mx1.freebsd.org (Postfix) with ESMTP id 0356FEE6
 for <freebsd-sparc64@freebsd.org>; Fri,  4 Jan 2013 23:46:35 +0000 (UTC)
Received: from alchemy.franken.de (localhost [127.0.0.1])
 by alchemy.franken.de (8.14.5/8.14.5/ALCHEMY.FRANKEN.DE) with ESMTP id
 r04NkHvI038493; Sat, 5 Jan 2013 00:46:17 +0100 (CET)
 (envelope-from marius@alchemy.franken.de)
Received: (from marius@localhost)
 by alchemy.franken.de (8.14.5/8.14.5/Submit) id r04NkGVi038492;
 Sat, 5 Jan 2013 00:46:16 +0100 (CET) (envelope-from marius)
Date: Sat, 5 Jan 2013 00:46:16 +0100
From: Marius Strobl <marius@alchemy.franken.de>
To: Chris Ross <cross+freebsd@distal.com>
Subject: Re: Changes to kern.geom.debugflags?
Message-ID: <20130104234616.GA37999@alchemy.franken.de>
References: <7AA0B5D0-D49C-4D5A-8FA0-AA57C091C040@distal.com>
 <6A0C1005-F328-4C4C-BB83-CA463BD85127@distal.com>
 <20121225232507.GA47735@alchemy.franken.de>
 <8D01A854-97D9-4F1F-906A-7AB59BF8850B@distal.com>
 <A947C892-5379-4F70-BFA0-0A7AB94DF0C6@distal.com>
 <6FC4189B-85FA-466F-AA00-C660E9C16367@distal.com>
 <20121230032403.GA29164@pix.net>
 <56B28B8A-2284-421D-A666-A21F995C7640@distal.com>
 <EEB60849-3192-46E2-8626-EC6824182515@distal.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <EEB60849-3192-46E2-8626-EC6824182515@distal.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: "freebsd-sparc64@freebsd.org" <freebsd-sparc64@freebsd.org>,
 Kurt Lidl <lidl@pix.net>
X-BeenThere: freebsd-sparc64@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Porting FreeBSD to the Sparc <freebsd-sparc64.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-sparc64>, 
 <mailto:freebsd-sparc64-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-sparc64>
List-Post: <mailto:freebsd-sparc64@freebsd.org>
List-Help: <mailto:freebsd-sparc64-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-sparc64>,
 <mailto:freebsd-sparc64-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Jan 2013 23:46:36 -0000

On Thu, Jan 03, 2013 at 11:27:44PM -0500, Chris Ross wrote:
> 
> On Dec 31, 2012, at 21:05 , Chris Ross <cross+freebsd@distal.com> wrote:
> >  Okay.  Well, I tried building stable/9 at revision 243673, which didn't work, and
> > then 243242, which also failed in the same way.  So, it may be something earlier
> > than the suggested (if I'm reading your email correctly, and 243243 is where the
> > rev you mentioned was integrated to stable/9.)
> > 
> >  Thanks much for the pointers!  I'll try to take a look at some of the underlying
> > changes, and see if anything looks more relevant.
> 
>   So, now that we're past the holiday madness, and I haven't heard anything back
> on this is there some other group or list I should ask the questions of ZFS internals
> to figure out why the sparc64 MD boot loader code is seeing a dn_datablkszsec
> of 0, and what it should be set to?
> 
>   Thanks.  I'm happy to compose another message to include people who might
> be able to help.  I'm out of my "comfort zone" in ZFS.
> 

The most straightforward way is to identify the commit that broke
it via a binary search and email the corresponding commit.

Marius