Re: Panic when booting MARVELL_NAS

[Nick Hudson <skrll%netbsd.org@localhost>]

On 02/07/16 22:15, Michael Blatt wrote:
> Hi all
>
> On a Zyxel NSA320S NAS - using the generic MARVELL_NAS config plus
> pseudo-device drvctl
> mvsocrtc* at mvsoc? offset ? irq ?
>
> The stock u-boot (Marvell's u-boot 1.1.4 fork, v3.26 - probably the same as the Sheevaplug's) causes NetBSD to panic with
>
> Marvell>> bootm 0x800000
>
> ## Booting image at 00800000 ...
>     Image Name:   NetBSD/ 7.99.25
>     Created:      2016-01-16  10:30:58 UTC
>     Image Type:   ARM NetBSD Kernel Image (uncompressed)
>     Data Size:    4452228 Bytes =  4.2 MB
>     Load Address: 00008000
>     Entry Point:  00008000
>     Verifying Checksum ... OK
> OK
> ## Transferring control to NetBSD stage-2 loader (at address 00008000) ...
> software interrupt
> pc : [<f0000004>]   lr : [<c000c9fc>]
> sp : c04476c8  ip : e24dd048 fp : c04476ec
> r10: c0465698  r9 : c0447774 r8 : 000186a0
> r7 : 00000000  r6 : c0393f70 r5 : c0465698  r4 : c0447c30
> r3 : 00600380  r2 : 0000001c r1 : 006003e0  r0 : e51fd344
> Flags: nZCv  IRQs off  FIQs off  Mode SVC_32
> Resetting CPU …
>
> I tested using a more recent u-boot based off 2015.10 from https://github.com/mibodhi/u-boot-kirkwood and that works flawlessly with the same kernel - except that u-boot cannot enable the 2nd SATA port with enough voltage for my 3.5’’ HDD. I’m investigating the u-boot issue, but in parallel I would try to understand the NetBSD panic.

That doesn't look like NetBSD to me. I just looked at a random u-boot 
tree I have and that seems to agree.

> Any pointers? I’m not sure where to begin.
>
> Cheers
> Michael

Nick