Booting -CURRENT on VIOS

Nathan Whitehorn nwhitehorn at freebsd.org
Sun Sep 4 10:01:59 UTC 2016


OK, so it looks like the fixed address at which loader wants to run is 
unavailable. Can you do these two commands as well:
printenv real-base
printenv load-base

Then I'll try to think of a workaround.
-Nathan

On 09/04/16 02:03, Kevin Bowling wrote:
> Sure,
>
> 0 > dev /memory  ok
> 0 > .properties
> name                    memory
> device_type             memory
> reg                     00000000 00000000  00000000 08000000
> available               00000000 00004000 00000000 001fc000 00000000 
> 0021d058 00000000 00010000
>                         00000000 00242bfc 00000000 009bd404 00000000 
> 02261000 00000000 05d9f000
> #address-cells          00000001
> #size-cells             00000000
> ibm,phandle             fffffffa
> ibm,associativity       00000004 00000000 00000000 00000000 00000000
>
>  ok
>
>
> On Sun, Sep 4, 2016 at 2:01 AM, Nathan Whitehorn 
> <nwhitehorn at freebsd.org <mailto:nwhitehorn at freebsd.org>> wrote:
>
>     It could be something with the system memory map. Can you sent the
>     output of:
>     dev /memory at 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 at 30000002/disk at 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 at freebsd.org <mailto:freebsd-ppc at freebsd.org>
>         mailing list
>         https://lists.freebsd.org/mailman/listinfo/freebsd-ppc
>         <https://lists.freebsd.org/mailman/listinfo/freebsd-ppc>
>         To unsubscribe, send any mail to
>         "freebsd-ppc-unsubscribe at freebsd.org
>         <mailto:freebsd-ppc-unsubscribe at freebsd.org>"
>
>
>



More information about the freebsd-ppc mailing list