From owner-freebsd-hackers@FreeBSD.ORG Mon Jan 10 22:22:53 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 28CB0106564A; Mon, 10 Jan 2011 22:22:53 +0000 (UTC) (envelope-from tom@tomjudge.com) Received: from eu1sys200aog106.obsmtp.com (eu1sys200aog106.obsmtp.com [207.126.144.121]) by mx1.freebsd.org (Postfix) with SMTP id 14D7A8FC17; Mon, 10 Jan 2011 22:22:51 +0000 (UTC) Received: from source ([63.174.175.251]) by eu1sys200aob106.postini.com ([207.126.147.11]) with SMTP ID DSNKTSuGu6agfTQP6aCd38gN6e0hexWjfodn@postini.com; Mon, 10 Jan 2011 22:22:52 UTC Received: from [172.17.10.53] (unknown [172.17.10.53]) by bbbx3.usdmm.com (Postfix) with ESMTP id 88AB6FD054; Mon, 10 Jan 2011 22:02:58 +0000 (UTC) Message-ID: <4D2B820C.3050205@tomjudge.com> Date: Mon, 10 Jan 2011 16:02:52 -0600 From: Tom Judge User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.13) Gecko/20101208 Lightning/1.0b2 Thunderbird/3.1.7 MIME-Version: 1.0 To: Luigi Rizzo References: <4D295820.20807@tomjudge.com> <20110109183316.GA92631@onelab2.iet.unipi.it> <4D2A0514.7040305@tomjudge.com> <20110109224401.GA95358@onelab2.iet.unipi.it> In-Reply-To: <20110109224401.GA95358@onelab2.iet.unipi.it> X-Enigmail-Version: 1.1.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org, luigi@freebsd.org Subject: Re: sys/boot/boot0/boot0.S - r186598 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Jan 2011 22:22:53 -0000 On 01/09/2011 04:44 PM, Luigi Rizzo wrote: > On Sun, Jan 09, 2011 at 12:57:24PM -0600, Tom Judge wrote: >> On 09/01/2011 12:33, Luigi Rizzo wrote: >>> On Sun, Jan 09, 2011 at 12:39:28AM -0600, Tom Judge wrote: >>>> Hi, >>>> >>>> Today I ran into an issue where setting the default slice with boot0cfg >>>> -s is broken. >>> a few questions inline: >>> >> Output inline, full script log attached. >> >> If you need more info let me know. > > can you take a dump of the boot sector at various stages > indicated below: > Paths to the files inline. >> > > DUMP #1: ORIGINAL BOOT SECTOR http://www.tomjudge.com/tmp/boot0/file1 > > > > DUMP #2: AFTER THE BOOT SECTOR UPDATE http://www.tomjudge.com/tmp/boot0/file2 > > > > > DUMP #3: AFTER A REBOOT WITH NO KEYPRESS http://www.tomjudge.com/tmp/boot0/file3 > > > > DUMP #4: AFTER THE SUCCESSFUL BOOT IN SLICE 2 http://www.tomjudge.com/tmp/boot0/file4 > > At least from this we can tell how #4 differs from #2/#3 > Maybe we can update the update code so that it only writes an updated active flag if the active flag has changed? This would resolv the wear issue that caused this to change behavior. Tom -- TJU13-ARIN