From owner-freebsd-ppc@freebsd.org Sun Sep 4 09:01:59 2016 Return-Path: Delivered-To: freebsd-ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A7264BCF14A for ; Sun, 4 Sep 2016 09:01:59 +0000 (UTC) (envelope-from nwhitehorn@freebsd.org) Received: from c.mail.sonic.net (c.mail.sonic.net [64.142.111.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 966FB2E0 for ; Sun, 4 Sep 2016 09:01:59 +0000 (UTC) (envelope-from nwhitehorn@freebsd.org) Received: from zeppelin.tachypleus.net ([88.131.223.94]) (authenticated bits=0) by c.mail.sonic.net (8.15.1/8.15.1) with ESMTPSA id u8491nI1010981 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Sun, 4 Sep 2016 02:01:52 -0700 Subject: Re: Booting -CURRENT on VIOS To: freebsd-ppc@freebsd.org, kevin.bowling@kev009.com References: From: Nathan Whitehorn Message-ID: Date: Sun, 4 Sep 2016 02:01:52 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Sonic-CAuth: UmFuZG9tSVaocZY/dogE8xlM+ZQ7M/fepco46a1DDF23rgkx+d9k4CpnrFxkYueO8NuGW2rC3Cc55dbYzHlt3ptgLZnRVPmCRnMJL/oa2lM= X-Sonic-ID: C;jkwkN35y5hGqkqDx2xNB0g== M;KGRsOH5y5hGqkqDx2xNB0g== X-Spam-Flag: No X-Sonic-Spam-Details: 0.0/5.0 by cerberusd X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Sep 2016 09:01:59 -0000 It could be something with the system memory map. Can you sent the output of: dev /memory@0 .properties That will help see what the memory layout looks like. -Nathan On 09/03/16 22:39, Kevin Bowling wrote: > I'm trying to run -CURRENT on VIOS (on POWER6). After a lot of digging I > found how to get the full path to the boot device I want (using firmware's > ioinfo tool), and the location of the loader from > release/powerpc/mkisoimages.sh. Ubuntu 16.04 is able to boot by selecting > the CD from the SMS menu so that's something I will dig into more later. > > The first major hurdle I've pasted below, when trying to run the loader. > It seems to fail quite early so I'm not sure where to start looking or how > to debug. Any advice? > > 0 > boot /vdevice/v-scsi@30000002/disk@8200000000000000:,\ppc\chrp\loader > CLAIM failed > Call History > ------------ > throw - c3b044 > $call-method - c48d18 > (poplocals) - c3c9e8 > (init-program) - c85738 > boot - c8647c > evaluate - c4c6ec > determine-of-footprint - c19100 > invalid pointer - 45 > invalid pointer - 45 > quit - c4cdcc > quit - c4cbc0 > > My Fix Pt Regs: > 00 0000000000000000 0000000000000000 00000000deadbeef 0000000000c6f61c > 04 0000000000c16fc0 0000000000a48ef0 0000000000019100 0000000000c05010 > 08 0000000008000000 0000000000000000 ffffffffffffffff 0000000000000000 > 0c 8000000012f7a914 0000000000c19100 0000000000c1a000 0000000001cc8bb8 > 10 0000000000e77c55 0000000000e77b65 0000000000c6f614 0000000000c6f6c4 > 14 0000000000000087 0000000000000000 0000000000000006 fffffffffffffffb > 18 0000000000c14fe8 0000000000c3a000 0000000000c16fc0 0000000000c19000 > 1c 0000000000c22000 0000000000c42100 0000000000c13fd8 0000000000c12fe0 > Special Regs: > %IV: 00000900 %CR: 24808004 %XER: 20000001 %DSISR: 00000000 > %SRR0: 0000000000c6f61c %SRR1: 800000000000b002 > %LR: 0000000000c48944 %CTR: 0000000000000005 > %DAR: 0000000000000000 > ok > _______________________________________________ > freebsd-ppc@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ppc > To unsubscribe, send any mail to "freebsd-ppc-unsubscribe@freebsd.org" >