From owner-freebsd-hackers@FreeBSD.ORG Fri Mar 2 18:46:36 2012 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C4AE21065674; Fri, 2 Mar 2012 18:46:36 +0000 (UTC) (envelope-from rank1seeker@gmail.com) Received: from mail-ee0-f54.google.com (mail-ee0-f54.google.com [74.125.83.54]) by mx1.freebsd.org (Postfix) with ESMTP id B89F18FC0A; Fri, 2 Mar 2012 18:46:35 +0000 (UTC) Received: by eekd17 with SMTP id d17so752116eek.13 for ; Fri, 02 Mar 2012 10:46:34 -0800 (PST) Received-SPF: pass (google.com: domain of rank1seeker@gmail.com designates 10.14.37.69 as permitted sender) client-ip=10.14.37.69; Authentication-Results: mr.google.com; spf=pass (google.com: domain of rank1seeker@gmail.com designates 10.14.37.69 as permitted sender) smtp.mail=rank1seeker@gmail.com; dkim=pass header.i=rank1seeker@gmail.com Received: from mr.google.com ([10.14.37.69]) by 10.14.37.69 with SMTP id x45mr6562088eea.43.1330713994872 (num_hops = 1); Fri, 02 Mar 2012 10:46:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:from:to:subject:date:content-type :content-transfer-encoding:in-reply-to:references:x-mailer; bh=c2E8YqhfEjD1eBpGEzXVRn0GGC1ti7oFS9qusfpY/1w=; b=eKbmlx5NFLf3XT8CF5BaOVr3NHFqjhJQvdooobG+7/qskGKIqJixMR7WEgFv6mmdEw ocrrLXIHQ4x2RoRbo1whonInImlQtIgTujLcX3xtnFU/i50vp6PdeQOz+wAJPkLKwSuq LoKZnzbF5D+C/LeX/mmOwTH4d29Yg+v1zcvJ4e1olftlKuEPN6DByk8oGdjBupPw4b/p zmaEyBA5Rh+zH/oI8bDZp2HwGM+jk4CU5CIUkCaDyVzA7mljkG9AfOcutQ7v/zNfR5nS vdjRHGo1he6ZSE+TTS06wlOrKvwbS1b4wnMQElone5dLousDe8diDazK1SCB1xG0OguX TTpw== Received: by 10.14.37.69 with SMTP id x45mr5057747eea.43.1330713994558; Fri, 02 Mar 2012 10:46:34 -0800 (PST) Received: from DOMYPC ([82.193.208.173]) by mx.google.com with ESMTPS id u11sm23354971eeb.1.2012.03.02.10.45.57 (version=SSLv3 cipher=OTHER); Fri, 02 Mar 2012 10:46:33 -0800 (PST) Message-ID: <20120302.184637.320.4@DOMY-PC> From: rank1seeker@gmail.com To: hackers@freebsd.org, "John Baldwin" , "Roman Divacky" , "Andriy Gapon" Date: Fri, 02 Mar 2012 19:46:37 +0100 Content-Type: text/plain; charset="Windows-1250" Content-Transfer-Encoding: quoted-printable In-Reply-To: <201203021224.24735.jhb@freebsd.org> References: <20120302.151703.536.2@DOMY-PC> <201203021224.24735.jhb@freebsd.org> X-Mailer: POP Peeper (3.8.1.0) Cc: Subject: Re: BUG: 9.0 stage 2 boot (/boot/boot) 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: Fri, 02 Mar 2012 18:46:36 -0000 ----- Original Message -----=0D=0AFrom: John Baldwin = =0D=0ATo: rank1seeker@gmail.com=0D=0ACc: = hackers@freebsd.org, "Roman Divacky" , "Andriy = Gapon" =0D=0ADate: Fri, 2 Mar 2012 12:24:24 = -0500=0D=0ASubject: Re: BUG: 9.0 stage 2 boot (/boot/boot)=0D=0A=0D=0A> = On Friday, March 02, 2012 10:17:03 am rank1seeker@gmail.com wrote:=0D=0A> = > ----- Original Message -----=0D=0A> > From: John Baldwin = =0D=0A> > To: rank1seeker@gmail.com=0D=0A> > Cc: = hackers@freebsd.org, "Roman Divacky" , Andriy Gapon = =0D=0A> > Date: Thu, 1 Mar 2012 16:14:43 -0500=0D=0A> > = Subject: Re: BUG: 9.0 stage 2 boot (/boot/boot)=0D=0A> > =0D=0A> > = =0D=0A> > > > However, avg@ might have found the actual cause of the bug. = And Roman did=0D=0A> > > > indeed break this earlier. Try the updated = boot2_test.patch again.=0D=0A> > > =0D=0A> > > You should still try = this.=0D=0A> > > =0D=0A> > > -- =0D=0A> > > John Baldwin=0D=0A> > > = =0D=0A> > =0D=0A> > =0D=0A> > Using patch: MD5 (boot2_test.patch) =3D = 72412f9b47b114302268561f12c1b46b=0D=0A> > =0D=0A> > = http://www.starforce.biz/stage2boot_1.jpg=0D=0A> > =0D=0A> > This is the = worst patch as even RE-typing doesn't work.=0D=0A> > That is, it is = completely unable to boot.=0D=0A> > =0D=0A> > Throw me another = patch!=0D=0A> =0D=0A> Ah, was using sizeof() on the wrong thing, and I = have a fix for the garbage=0D=0A> you saw for kname as well. Patch is = updated at the normal URL.=0D=0A> =0D=0A> > > Please don't treat John = this way. He has put in a lot of time for=0D=0A> > > you, and many = others, and is one of THE experts.=0D=0A> > > =0D=0A> > > Chris=0D=0A> > = =0D=0A> > =0D=0A> > He didn't got a bad treatment, nor any side is = angry.=0D=0A> > Relax! ;)=0D=0A> =0D=0A> Actually, you've been rather = rude for the entire thread, I am just doing my=0D=0A> best to ignore it = in the interest of getting the bug fixed.=0D=0A> =0D=0A> -- =0D=0A> John = Baldwin=0D=0A> =0D=0A=0D=0AI'm sorry if you think so, especially part = where I am rude through the entire thread. That I can hardly = believe.=0D=0AI am also actively testing and am persistant in solving = issue.=0D=0AOr is problem in my perception?=0D=0A=0D=0AAnyway, yours = latest patch has a same md5 hash as a previous one and also built binary = /boot/boot had same md5 hash.=0D=0ASo I've simply skipped installing boot = code.=0D=0A=0D=0A=0D=0ADomagoj Smol=E8i=E6