From owner-freebsd-ppc@FreeBSD.ORG Sat Apr 10 03:59:11 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 B4FBE106564A for ; Sat, 10 Apr 2010 03:59:11 +0000 (UTC) (envelope-from nwhitehorn@freebsd.org) Received: from argol.doit.wisc.edu (argol.doit.wisc.edu [144.92.197.212]) by mx1.freebsd.org (Postfix) with ESMTP id 813518FC0A for ; Sat, 10 Apr 2010 03:59:11 +0000 (UTC) MIME-version: 1.0 Received: from avs-daemon.smtpauth3.wiscmail.wisc.edu by smtpauth3.wiscmail.wisc.edu (Sun Java(tm) System Messaging Server 7u2-7.05 32bit (built Jul 30 2009)) id <0L0N0040I72MU800@smtpauth3.wiscmail.wisc.edu> for freebsd-ppc@freebsd.org; Fri, 09 Apr 2010 22:59:10 -0500 (CDT) Received: from comporellon.tachypleus.net (adsl-99-135-74-201.dsl.mdsnwi.sbcglobal.net [99.135.74.201]) by smtpauth3.wiscmail.wisc.edu (Sun Java(tm) System Messaging Server 7u2-7.05 32bit (built Jul 30 2009)) with ESMTPSA id <0L0N00M4Q72F4V40@smtpauth3.wiscmail.wisc.edu>; Fri, 09 Apr 2010 22:59:04 -0500 (CDT) Date: Fri, 09 Apr 2010 22:59:02 -0500 From: Nathan Whitehorn In-reply-to: To: Justin Hibbits Message-id: <4BBFF786.50704@freebsd.org> X-Spam-Report: AuthenticatedSender=yes, SenderIP=99.135.74.201 X-Spam-PmxInfo: Server=avs-9, Version=5.5.5.374460, Antispam-Engine: 2.7.1.369594, Antispam-Data: 2010.4.10.34814, SenderIP=99.135.74.201 References: <4BBB6DC0.3030808@freebsd.org> <4BBFD278.30804@freebsd.org> User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.1.9) Gecko/20100407 Thunderbird/3.0.4 Content-Type: text/plain; CHARSET=US-ASCII; format=flowed Content-Transfer-Encoding: 7BIT 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: Sat, 10 Apr 2010 03:59:11 -0000 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 >> > 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