Date: Sat, 10 Apr 2010 07:52:47 -0400 From: Justin Hibbits <jrh29@alumni.cwru.edu> To: Nathan Whitehorn <nwhitehorn@freebsd.org> Cc: FreeBSD PowerPC ML <freebsd-ppc@freebsd.org> Subject: Re: ppc64 snapshot Message-ID: <k2vfd9cd3451004100452s576305b3kf175bad9dbd08bee@mail.gmail.com> In-Reply-To: <4BBFF786.50704@freebsd.org> References: <g2kfd9cd3451004041522pec1d3740l7e3551284b619b5@mail.gmail.com> <4BBB6DC0.3030808@freebsd.org> <j2zfd9cd3451004081857o4f39ac5dr8bcd16873c874c30@mail.gmail.com> <y2qfd9cd3451004091754u5a1d4af0p54dacd41bbd65a93@mail.gmail.com> <4BBFD278.30804@freebsd.org> <q2mfd9cd3451004091950p284aee19ube4575bb02892f04@mail.gmail.com> <4BBFF786.50704@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Apr 9, 2010 at 11:59 PM, Nathan Whitehorn <nwhitehorn@freebsd.org>wrote: > On 04/09/10 21:50, Justin Hibbits wrote: > > On Fri, Apr 9, 2010 at 9:20 PM, Nathan Whitehorn <nwhitehorn@freebsd.org>wrote: > >> On 04/09/10 19:54, Justin Hibbits wrote: >> >> On Thu, Apr 8, 2010 at 9:57 PM, Justin Hibbits <jrh29@alumni.cwru.edu>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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?k2vfd9cd3451004100452s576305b3kf175bad9dbd08bee>