Date: Wed, 29 Feb 2012 21:08:36 +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: <20120229.200836.168.1@DOMY-PC> In-Reply-To: <201202291127.00209.jhb@freebsd.org> References: <20120217.074355.853.1@DOMY-PC> <201202271123.59244.jhb@freebsd.org> <20120228.200906.958.1@DOMY-PC> <201202291127.00209.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: = Wed, 29 Feb 2012 11:26:59 -0500=0D=0ASubject: 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=0APatch fails at 9.0 RELEASE: = (Is this for 9 STABLE?)=0D=0A----=0D=0AHmm... Looks like a unified diff = to me...=0D=0AThe text leading up to this = was:=0D=0A--------------------------=0D=0A|Index: = boot/i386/boot2/boot2.c=0D=0A|=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=0D=0A|--- = boot/i386/boot2/boot2.c (revision 232297)=0D=0A|+++ = boot/i386/boot2/boot2.c (working = copy)=0D=0A--------------------------=0D=0APatching file = /sys/boot/i386/boot2/boot2.c using Plan A...=0D=0AHunk #1 failed at = 225.=0D=0AHunk #2 failed at 242.=0D=0AHunk #3 failed at 265.=0D=0A3 out = of 3 hunks failed--saving rejects to = /sys/boot/i386/boot2/boot2.c.rej=0D=0AHmm... Ignoring the trailing = garbage.=0D=0Adone=0D=0A----=0D=0A=0D=0A=0D=0AI'll give you a hint (which = I've mentioned at start)=0D=0A=0D=0AIn 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=0AThat is ...=0D=0AI've created vnode image. Then, = ... when I 'dd' it to HDD's slice, it boots.=0D=0ABUT when I 'dd' it to = USB's slice it hangs.=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?20120229.200836.168.1>