From owner-freebsd-ppc@FreeBSD.ORG Sat Apr 10 11:52:49 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 677801065672; Sat, 10 Apr 2010 11:52:49 +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 AF0338FC18; Sat, 10 Apr 2010 11:52:48 +0000 (UTC) Received: by bwz8 with SMTP id 8so1619793bwz.3 for ; Sat, 10 Apr 2010 04:52:47 -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=lEr1puPCOKkLtwo4S2yuie2AjyrbnZ/Vbm2zmfhZYkY=; b=HrA8ZiTIC5X6MNPcgatilEYX8Jl9IfVulnGo50Z0S7/WFwEANkdjwa43/xlhzF1CdF 0YixDEtEwi3VOJ1hmtokssp0wNMTqU1bFDg2cvUYepLp8id4wURHqtDAL9cudEIwRfkF CLt9O98/wAXoo4Bu3XT3V/NbGMfqTWmdlhEFw= 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=emQDU7HO/O00oBYMav5o4kr+Jbqjn3sUpnex/WXKPtNHO6W12VSdOrdhw6pwi7t0IG 0WGhZpg8b+V0tWIvJDIkDgHti0sSyl08LUoSxDd64ashwPfy8Ai8t0Gen0lbOcaPcIZe yHqwB9RM1+/W/DYKP7Ov1e0ve5hXgRQH+WEL8= MIME-Version: 1.0 Sender: chmeeedalf@gmail.com Received: by 10.204.135.133 with HTTP; Sat, 10 Apr 2010 04:52:47 -0700 (PDT) In-Reply-To: <4BBFF786.50704@freebsd.org> References: <4BBB6DC0.3030808@freebsd.org> <4BBFD278.30804@freebsd.org> <4BBFF786.50704@freebsd.org> Date: Sat, 10 Apr 2010 07:52:47 -0400 X-Google-Sender-Auth: 207c34e6e3eaea36 Received: by 10.204.1.136 with SMTP id 8mr1548465bkf.92.1270900367142; Sat, 10 Apr 2010 04:52:47 -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: Sat, 10 Apr 2010 11:52:49 -0000 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