Re: HP 715/100 installation.

Michael Shalayeff <[email protected]> Mon, 18 Oct 2004 13:08:53 -0400 (EDT)
Newsgroups gmane.os.openbsd.hppa
Message-ID <[email protected]>
Making, drinking tea and reading an opus magnum from Stuart William Mackie:
> I'm having problems net-booting the HP 715/100 platform for install.

first of all it's a snapshot built from some stuff i was hacking on
and a bit before being in calgary and trying to tame new hppa64 that
had been donated by one of the users.

so you should understand that it might be a bit broken unintentionally (:

> OK so far, but:
> 
> [ no symbol table formats found ]
> Copyright (c) 1982, 1986, 1989, 1991, 1993
>          The Regents of the University of California.  All rights reserved.
> Copyright (c) 1995-2004 OpenBSD. All rights reserved. 
> http://www.OpenBSD.org
> 
> OpenBSD 3.6-current (RAMDISK) #149: Wed Sep 29 01:51:51 MDT 2004
>      [email protected]:/usr/src/sys/arch/hppa/compile/RAMDISK
> HP 9000/715/100 (Mirage Sr.) PA-RISC 1.1c
> real mem = 67108864 (524288 reserved for PROM, 7471104 used by OpenBSD)
> avail mem = 50782208
> using 1630 buffers containing 6676480 bytes of memory
> mainbus0 (root) [flex fff80000]
> pdc0 at mainbus0
> power0 at mainbus0: not available
> mem0 at mainbus0 offset ffbf000: viper rev 0, size 64MB
> cpu0 at mainbus0 offset ffbe000 irq 31: PCXL L1-A 100MHz, FPU PCXL 
> (CMOS-26B) re
> v 1
> cpu0: 128K(32b/l) Icache, 128K(32b/l) wr-back coherent Dcache, 120 
> coherent TLB,
>   8 BTLB
> panic: trap: uvm_fault(0x689890, c0125000, 0, 2): 14
> Stopped at      0x20842c:       break   0,5
> RUN AT LEAST 'trace' AND 'ps' AND INCLUDE OUTPUT WHEN REPORTING THIS 
> PANIC!
> DO NOT EVEN BOTHER REPORTING THIS WITHOUT INCLUDING THAT INFORMATION!
> ddb>trace
> (null)(22f62c,402d10,5,8) at 0x20842c
> (null)(2696d0,689890,c0125000,0) at 0xfc5b4
> (null)(1000,3,6ee8c8,2) at 0xfc58c
> (null)(0,0,0,c0001) at 0x2123a4
> -- trap #15
[skipped]

> Is this a hardware failure?

probably no.
although it's hard to see what's happenning w/ the ramdisks
as those are stripped of symbol table. if you try install
3.5 and then just try to boot generic /bsd from the snapshot
do you get the same problem?

cu

-- 
    paranoic mickey       (my employers have changed but, the name has remained)