Re: Trying to boot on D350

On Monday 09 July 2007 09:47, Wojciech Gałązka wrote:
> Hello,
> Here is my experience with NetBSD 3.88.20, GENERIC kernel with DEBUG and
> DIAGNOSTICS options enabled
>
> The machine is D350 2 x 7200 CPUs, 1.5 GB RAM

The support for this processor type is just not there at the moment. I did 
make some progress on the code for this, but got side-tracked.

> The machine boots and works nicely under HP-UX 11.11
>
> The netbooting of NetBSD kernels gives the following output on the serial
> console
>
> Booting...
> Network Station Address 080009-af2b6e
> Boot IO Dependent Code (IODC) revision 2
> HARD Booted.
>
> >> NetBSD/hp700 LIF/FFS/LFS Boot, Revision 1.3
> >> (n4@small, Sun Jun 24 23:04:08 CEST 2007)
> >> Enter "reset" to reset system.
>
> Boot: [[[lf0a:]netbsd][-a][-c][-d][-s][-v][-q]] :- boot netbsd -v
> 10240088+110592+471040 [311888+277865]=0xb1e388
> Start @ 0x200000 [1=0xc8e000-0xd1e388]...
> PDC_CACHE_SETCS: 0, 0, 0, 0 (-2)
> SPID bits: 0x0, error = -2
> btlb info: minsz=128, maxsz=16384
> btlb fixed: i=0, d=0, c=16
> btlb varbl: i=0, d=0, c=0
> pdc_hwtlb.min_size 0x1000
> pdc_hwtlb.max_size 0x80000000
> HP9000/831/D200-2/D400-2 (UltraLight Proc 2-way T'100), PA7200
>   [ BTLB slot 0: r-x--- 0x00200000 @ 0x0:0x00200000 len 0x00200000 ]
>   [ BTLB slot 1: r-x--- 0x00400000 @ 0x0:0x00400000 len 0x00400000 ]
>   [ BTLB slot 2: r-x--- 0x00800000 @ 0x0:0x00800000 len 0x00400000 ]
>   [ BTLB slot 3: rw---- 0x00c00000 @ 0x0:0x00c00000 len 0x00400000 ]
>   [ BTLB slot 4: rw---- 0x01000000 @ 0x0:0x01000000 len 0x01000000 ]
>   [ BTLB slot 5: rw---- 0x02000000 @ 0x0:0x02000000 len 0x02000000 ]
>   [ BTLB slot 6: rw---- 0x04000000 @ 0x0:0x04000000 len 0x02000000 ]
>   [ BTLB slot 7: rw---- 0x06000000 @ 0x0:0x06000000 len 0x00800000 ]
>
> [ ... Lots of pdc_kenter stuff deleted ...]
>
> pdc_coproc: 0xc0, 0xc0
> Loaded initial symtab at 0xc8e000, strtab at 0xcda61c, # entries 19474
>
>
> It seems that after leaving hppa_init (/hp700/hp700/machdep.c) processing
> goes back to locore.S and goes nowhere or idles helplessly

I got as far as determining that pdc calls were problematic after going 
virtual on the J200 that I had access to. I worked around this and hit other 
problems.

> Moreover I'm not sure if this is ok for PDC_CACHE calls to fail

yeah, don't worry about that.

> BTW OpenBSD 4.1 fails to boot on this machine generating similar messages

I guess linux works.

Nick
--
Nick Hudson                                             <[email protected]>
Portmaster, NetBSD/hp700              <http://www.NetBSD.org/Ports/hp700/>