Date: Thu, 01 Mar 2012 21:58:02 +0100 From: rank1seeker@gmail.com To: hackers@freebsd.org, "John Baldwin" <jhb@freebsd.org>, "Roman Divacky" <rdivacky@freebsd.org> Subject: Re: BUG: 9.0 stage 2 boot (/boot/boot) Message-ID: <20120301.205802.182.3@DOMY-PC> In-Reply-To: <201203011543.25446.jhb@freebsd.org> References: <20120217.074355.853.1@DOMY-PC> <201202291605.08267.jhb@freebsd.org> <20120301.200235.040.1@DOMY-PC> <201203011543.25446.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
----- Original Message -----=0D=0AFrom: John Baldwin = <jhb@freebsd.org>=0D=0ATo: rank1seeker@gmail.com=0D=0ACc: = hackers@freebsd.org, "Roman Divacky" <rdivacky@freebsd.org>=0D=0ADate: = Thu, 1 Mar 2012 15:43:25 -0500=0D=0ASubject: Re: BUG: 9.0 stage 2 boot = (/boot/boot)=0D=0A=0D=0A> On Thursday, March 01, 2012 3:02:35 pm = rank1seeker@gmail.com wrote:=0D=0A> > ----- Original Message -----=0D=0A> = > From: John Baldwin <jhb@freebsd.org>=0D=0A> > To: = rank1seeker@gmail.com=0D=0A> > Cc: hackers@freebsd.org, "Roman Divacky" = <rdivacky@freebsd.org>=0D=0A> > Date: Wed, 29 Feb 2012 16:05:08 = -0500=0D=0A> > Subject: Re: BUG: 9.0 stage 2 boot (/boot/boot)=0D=0A> > = =0D=0A> > > On Wednesday, February 29, 2012 3:08:36 pm = rank1seeker@gmail.com wrote:=0D=0A> > > > ----- Original Message = -----=0D=0A> > > > From: John Baldwin <jhb@freebsd.org>=0D=0A> > > > To: = rank1seeker@gmail.com=0D=0A> > > > Cc: hackers@freebsd.org, "Roman = Divacky" <rdivacky@freebsd.org>=0D=0A> > > > Date: Wed, 29 Feb 2012 = 11:26:59 -0500=0D=0A> > > > Subject: Re: BUG: 9.0 stage 2 boot = (/boot/boot)=0D=0A> > > > =0D=0A> > > > > On Tuesday, February 28, 2012 = 3:09:06 pm rank1seeker@gmail.com wrote:=0D=0A> > > > > > ----- Original = Message -----=0D=0A> > > > > > From: John Baldwin = <jhb@freebsd.org>=0D=0A> > > > > > To: rank1seeker@gmail.com=0D=0A> > > > = > > Cc: hackers@freebsd.org, "Roman Divacky" = <rdivacky@freebsd.org>=0D=0A> > > > > > Date: Mon, 27 Feb 2012 11:23:59 = -0500=0D=0A> > > > > > Subject: Re: BUG: 9.0 stage 2 boot = (/boot/boot)=0D=0A> > > > > > =0D=0A> > > > > > > On Saturday, February = 25, 2012 9:41:48 am rank1seeker@gmail.com wrote:=0D=0A> > > > > > > > > = Do you only see the "No " message? Do you see the '/boot.config: = /loader'=0D=0A> > > > > > > > > message? (Do you have RBX_QUIET enabled = perhaps? (-q)) Do you get the actual=0D=0A> > > > > > > > > boot2 prompt = at all?=0D=0A> > > > > > > > =0D=0A> > > > > > > > I don't have RBX_QUIET = enabled nor any other flags=0D=0A> > > > > > > > =0D=0A> > > > > > > > = Let the pic tell a story:=0D=0A> > > > > > > > = http://www.starforce.biz/stage2boot.jpg=0D=0A>; > > > > > > =0D=0A> > > > = > > > Ahh, this is helpful. You do see the '/boot.config: /loader' = message.=0D=0A> > > > > > =0D=0A> > > > > > I've already explained that, = numerous times (RE-typing ...)=0D=0A> > > > > =0D=0A> > > > > It was not = as obvious before, and you are seeing a failure that no one else=0D=0A> > = > > > has reported, so you need to be patient.=0D=0A> > > > > =0D=0A> > > = > > > > > Patch eliminates possible error, of manual = "intervention"=0D=0A> > > > > > > > That is, a perfectly valid patch = being classified as invalid.=0D=0A> > > > > > > =0D=0A> > > > > > > I = have no idea what you mean here. However, it seems you don't have junk = in=0D=0A> > > > > > > your 'opts' variable anyway.=0D=0A> > > > > > = =0D=0A> > > > > > What I meant was that I won't manually(edit file) apply = patch, but via 'patch' tool/bin.=0D=0A> > > > > =0D=0A> > > > > = Ok.=0D=0A> > > > > =0D=0A> > > > > > > Hmm, you could try adding some = more debugging to boot2.c to see exactly what=0D=0A> > > > > > > is = failing. For example, does the first call to 'parse()' fail and = clear=0D=0A> > > > > > > autoboot?=0D=0A> > > > > > =0D=0A> > > > > > I = don't do nor understand c code.=0D=0A> > > > > =0D=0A> > > > > Ok. That = will take a bit longer to fix, but that is ok. I've attached a = new=0D=0A> > > > > patch with some debugging output. It shouldn't fix = the problem yet, but I want=0D=0A> > > > > to see if any of the new = messages are output, and when they are output.=0D=0A> > > > > =0D=0A> > > = > > > How could it silently loose documented functionality?=0D=0A> > > > = > =0D=0A> > > > > Several changes were made to boot2 to make it smaller = so it could be compiled with=0D=0A> > > > > clang, and it seems that at = least one of those changes must have had a bug.=0D=0A> > > > > =0D=0A> > = > > > -- =0D=0A> > > > > John Baldwin=0D=0A> > > > >=0D=0A> > > > =0D=0A> = > > > =0D=0A> > > > Patch fails at 9.0 RELEASE: (Is this for 9 = STABLE?)=0D=0A> > > =0D=0A> > > Nope, patch was made against a 9.0 = tree:=0D=0A> > > =0D=0A> > > % svn info .=0D=0A> > > Path: .=0D=0A> > > = URL: svn+ssh://svn.freebsd.org/base/releng/9.0/sys=0D=0A> > > Repository = Root: svn+ssh://svn.freebsd.org/base=0D=0A> > > Repository UUID: = ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f=0D=0A> > > Revision: 232297=0D=0A> > = > Node Kind: directory=0D=0A> > > Schedule: normal=0D=0A> > > Last = Changed Author: kensmith=0D=0A> > > Last Changed Rev: 229283=0D=0A> > > = Last Changed Date: 2012-01-02 09:45:30 -0500 (Mon, 02 Jan 2012)=0D=0A> > = > =0D=0A> > > % svn stat boot/i386/boot2=0D=0A> > > M = boot/i386/boot2/boot2.c=0D=0A> > > =0D=0A> > > % svn diff boot/i386/boot2 = | md5=0D=0A> > > 888f90f32bd20d1bf7e2d3277d9b697b=0D=0A> > > =0D=0A> > > = And the file I sent to you before:=0D=0A> > > =0D=0A> > > % md5 = ~/work/patches/boot2_test.patch =0D=0A> > > MD5 = (/home/jhb/work/patches/boot2_test.patch) =3D = 888f90f32bd20d1bf7e2d3277d9b697b=0D=0A> > > =0D=0A> > > > I'll give you a = hint (which I've mentioned at start)=0D=0A> > > > =0D=0A> > > > In order = to expose bug, 2 conditions have to be met:=0D=0A> > > > 1) = boot.config in use=0D=0A> > > > 2) daX device (i.e; USB stick)=0D=0A> = > > > =0D=0A> > > > That is ...=0D=0A> > > > I've created vnode image. = Then, ... when I 'dd' it to HDD's slice, it boots.=0D=0A> > > > BUT when = I 'dd' it to USB's slice it hangs.=0D=0A> > > =0D=0A> > > USB booting = uses a different chunk of BIOS code, and it may be doing different=0D=0A> = > > things which result in uninitialized memory having different values = (e.g. the=0D=0A> > > cmd[] array).=0D=0A> > > =0D=0A> > > -- =0D=0A> > > = John Baldwin=0D=0A> > > =0D=0A> > =0D=0A> > Using new:=0D=0A> > MD5 = (boot2_test.patch) =3D 01cc3a9dda1f1ecbd5125092ebccc476=0D=0A> =0D=0A> = Hmmm, it seems you have autoboot =3D=3D 0, but kname set (but you didn't = get the=0D=0A> printf where autoboot is set to 0, and you didn't get the = printf where kname=0D=0A> is set to a non-NULL value). I'll update the = patch again (same URL), but if=0D=0A> you don't get any new messages, = then I suspect you aren't actually using the=0D=0A> new = boot2.=0D=0A=0D=0A> You do realize you have to use gpart to install the = new boot code=0D=0A> on the USB stick after you have built it, = yes?=0D=0A=0D=0AYou are kidding me, right?=0D=0AIf I haven't used gpart = to install PATCHED AND BUILT boot2, THEN on picture taken and given here, = as url, WOULDN'T be very custom output!=0D=0ANo RELEASE boot2 would = output what is displayed = on:=0D=0A=0D=0Ahttp://www.starforce.biz/stage2boot.jpg=0D=0A=0D=0ACUSTOM = output is an ultimate proof of patched version in use.=0D=0AOr do you = think otherwise ... ?=0D=0A=0D=0A=0D=0A=0D=0ADomagoj Smol=E8i=E6
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120301.205802.182.3>