From owner-freebsd-ppc@FreeBSD.ORG Sun Apr 11 00:19:24 2010 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9AD851065673; Sun, 11 Apr 2010 00:19:24 +0000 (UTC) (envelope-from chmeeedalf@gmail.com) Received: from mail-bw0-f216.google.com (mail-bw0-f216.google.com [209.85.218.216]) by mx1.freebsd.org (Postfix) with ESMTP id E1B338FC08; Sun, 11 Apr 2010 00:19:23 +0000 (UTC) Received: by bwz8 with SMTP id 8so1899002bwz.3 for ; Sat, 10 Apr 2010 17:19:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:received:message-id:subject :from:to:cc:content-type; bh=B4Vs/cUDseLj5QItF/0BiUnAXptgru0p4jV1P0lDtR0=; b=iwb8uK24Rdd8PaNrLsQQz3c9hvZpVoN/v45Ja9Mpue/ClYfMDriOPbSODpf+TIE/8S QGIv4wafDyZ58bJ0HIqf9yzsVfTM6609rZJOyDD1Jb4b/bsSGYS6Nn97q7FylLUQq8X2 BpwLz233i7Dfi6dWGFbDL9G7L3Vgu/kBZL+2U= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; b=PXMIOLig8IHX7CXzX6aMFiNSBmMgb96cQLkSpMZKlXNi2fzPVM7tidsXshQaATIcyh nH1TXzRH82Wc1IgddgJklG/5G546YQNF+iUc0TLvfhx296yRRHV72kDXfi2cLloNXbsI rm9rzQQHD8tHmfqmM3zeS5k8PfS3yAMe0p66c= MIME-Version: 1.0 Sender: chmeeedalf@gmail.com Received: by 10.204.135.133 with HTTP; Sat, 10 Apr 2010 17:19:22 -0700 (PDT) In-Reply-To: <4BC0A1A6.6040700@freebsd.org> References: <4BBFD278.30804@freebsd.org> <4BBFF786.50704@freebsd.org> <4BC075E3.5090500@freebsd.org> <4BC0A1A6.6040700@freebsd.org> Date: Sat, 10 Apr 2010 20:19:22 -0400 X-Google-Sender-Auth: ebb0582183e1c826 Received: by 10.204.132.196 with SMTP id c4mr2269264bkt.5.1270945162680; Sat, 10 Apr 2010 17:19:22 -0700 (PDT) Message-ID: From: Justin Hibbits To: Nathan Whitehorn Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: FreeBSD PowerPC ML Subject: Re: ppc64 snapshot X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Apr 2010 00:19:24 -0000 On Sat, Apr 10, 2010 at 12:04 PM, Nathan Whitehorn wrote: > On 04/10/10 10:53, Justin Hibbits wrote: > > On Sat, Apr 10, 2010 at 8:58 AM, Nathan Whitehorn wrote: > >> On 04/10/10 06:52, Justin Hibbits wrote: >> >> On Fri, Apr 9, 2010 at 11:59 PM, Nathan Whitehorn > > wrote: >> >>> On 04/09/10 21:50, Justin Hibbits wrote: >>> >>> On Fri, Apr 9, 2010 at 9:20 PM, Nathan Whitehorn >> > wrote: >>> >>>> On 04/09/10 19:54, Justin Hibbits wrote: >>>> >>>> On Thu, Apr 8, 2010 at 9:57 PM, Justin Hibbits wrote: >>>> >>>>> On Tue, Apr 6, 2010 at 1:22 PM, Nathan Whitehorn < >>>>> nwhitehorn@freebsd.org> wrote: >>>>> >>>>>> Justin Hibbits wrote: >>>>>> >>>>>>> I just got my hands on a dual-core G5 (Late 2005), and want to >>>>>>> throw >>>>>>> -CURRENT on it. Is there a snapshot available with the recent ppc64 >>>>>>> changes >>>>>>> that I could test out? >>>>>>> >>>>>>> - Justin >>>>>>> _______________________________________________ >>>>>>> freebsd-ppc@freebsd.org mailing list >>>>>>> http://lists.freebsd.org/mailman/listinfo/freebsd-ppc >>>>>>> To unsubscribe, send any mail to " >>>>>>> freebsd-ppc-unsubscribe@freebsd.org" >>>>>>> >>>>>>> >>>>>> I just finished implementing the last missing feature in the 64-bit >>>>>> PowerPC port, and there are no more 64-bit-specific bugs that I know about. >>>>>> Once M. Warner Losh's build system changes are in the tree, I will submit a >>>>>> final patch set for review, and merge it to head, but the port should be >>>>>> completely usable at this point. >>>>>> >>>>>> System Compatibility: >>>>>> - Apple G5 machines >>>>>> >>>>>> Caveats: >>>>>> - Do not run ofwdump on an SMP system, as it can cause hangs (also a >>>>>> 32-bit bug) >>>>>> - Many ports (e.g. X and GTK) need patches not currently in the ports >>>>>> tree to compile, since this is a new platform >>>>>> >>>>>> Instructions: >>>>>> svn co http://svn.freebsd.org/base/projects/ppc64 >>>>>> cd ppc64 >>>>>> make buildworld buildkernel installkernel installworld distribution >>>>>> DESTDIR=/path/to/installation TARGET_ARCH=powerpc64 >>>>>> >>>>>> I would appreciate any feedback or tests, as well as testing on 32-bit >>>>>> Book-E systems to make sure I did not break anything. Many thanks to Andreas >>>>>> Tobler for his tireless testing efforts during development of this port. >>>>>> -Nathan >>>>>> >>>>>> >>>>> I've finally had a chance to test it, but it hangs with the string >>>>> >>>>> Kernel entry at 0x1034e0... >>>>> >>>>> nothing more. I tried booting verbose, but that gave nothing, it >>>>> looks like it may not even be leaving the loader. >>>>> >>>>> - Justin >>>>> >>>> >>>> I just tried a fresh head boot, and I got the same thing loading a ppc32 >>>> kernel. Trying with hw.physmem=512M (the machine has 4GB physical memory) >>>> failed as well, and loading a ppc32 kernel from loader.ppc64 same result. >>>> Any ideas of how to continue debugging this? >>>> >>>> - Justin >>>> >>>> This sounds like an issue with syscons. Can you try setting >>>> hw.syscons.disable=1 from the loader? That should make the kernel fall back >>>> to the Open Firmware text console. >>>> -Nathan >>>> >>> >>> Same result, with both ppc32 and ppc64 kernels. Should I just start >>> riddling the kernel with printf()s to track this down? >>> >>> >>> That is really strange. One of the very first things the kernel does is >>> to print out some lines from KDB. >>> >>> You can try to add an OF_printf() to the line right after OF_bootstrap() >>> in aim/machdep.c. That is the earliest you can use Open Firmware and get >>> output from the kernel. But I suspect it's not even getting there. >>> >>> The entry point looks a little wonky to me -- mine is 100160, and it >>> should always be somewhere around there. Could you check if the printed >>> entry point address corresponds to the first instructions in the text >>> segment with objdump? You can use make buildenv TARGET_ARCH=powerpc64 to get >>> a toolchain and objdump for PPC64 executables. >>> -Nathan >>> >> >> 100160 is the start of the text segment. 1034e0 is the beginning of >> .__start. >> >> - Justin >> >> One other suggestion: try directly loading a PPC32 kernel from Open >> Firmware instead of the loader first. >> -Nathan >> > > Just to rule out my build environment, could you send me (or link me to) a > known-good ppc64 kernel and loader? I'll try booting the kernel directly > tonight. > > - Justin > > > These are from my iMac, so they should work. You should also be aware that > OF can only directly load 32-bit kernels. > -Nathan > Nathan, Good news, your kernel boots on my G5. In fact, it finds almost everything, but panics with: panic: no PIC detected So apparently it's my build environment that's at fault. - Justin