Subject: sun4/110: kernel panic during netboot
To: None <port-sparc@netbsd.org>
From: Studio Associato Eclipse <eclipse@sirio.iet.unipi.it>
List: port-sparc
Date: 08/19/1999 11:32:31
Hi!
I'm trying to revive the sun4/110 i was gifted by a friend of mine...

My setup is: 
Sun4/110 mod.501/1512 - 20MB ram and no FPU - in a Sun3/60 box
Sun type-3 keyboard and mouse
Sun shoebox (actually containing a cdrom reader and a tape)
P4 3/60 cgfour color framebuffer (actually seems dead)
19'' Sun Hitachi Color monitor mod.365/1006 (seems working, but shows just a
light flashing green grid when the workstation is on).

After some black magic experiments (i hadn't configured rpc.bootparamd before,
and had no manual with me on holidays), i (almost) succeded in netbooting NetBSD
1.4 from my linux box.
Both kernels i have found in the installation directory panic during boot
(according to my nfsd, just after having opened and read two 8KB chunck of init)
in this way (this log is from netbsd.GENERIC.gz):


Selftest Completed.

Sun Workstation, Model Sun-4/100 Series.
Type-3 Keyboard.
ROM Rev 1.8, 20MB memory installed, Serial #10452.
Ethernet address 8:0:20:6:BA:5D.

Testing 20 Megabytes of Memory ... Completed.

Auto-boot in progress...

EEPROM boot device...sd(0,0,0)
scsi: select failed
scsi: select failed
scsi: select failed

Device not found

>b ie()netbsd -s
Boot: ie(0,0,0)netbsd -s
Using IP Address 192.168.1.100 = C0A80164
Booting from tftp server at 192.168.1.1 = C0A80101
Downloaded 56224 bytes from tftp server.

>> NetBSD/sparc Secondary Boot, Revision 1.8
>> (pk@flambard, Sat May  8 21:54:06 MEST 1999)
Using IP Address 192.168.1.100 = C0A80164
boot: client IP address: 192.168.1.100
boot: client name: sun4
root addr=192.168.1.1 path=/export
Booting netbsd @ 0x4000
1818624+129504+177260+[99876+117970]=0x24014a
console is ttya
Copyright (c) 1996, 1997, 1998, 1999
    The NetBSD Foundation, Inc.  All rights reserved.
Copyright (c) 1982, 1986, 1989, 1991, 1993
    The Regents of the University of California.  All rights reserved.

NetBSD 1.4 (GENERIC) #0: Sun May  9 03:00:22 MEST 1999
    pk@flambard:/usr/src/sys/arch/sparc/compile/GENERIC
real mem = 20946944
avail mem = 17416192
using 127 buffers containing 1040384 bytes of memory
bootpath: /obio0/ie0
mainbus0 (root): SUN-4/100 series
cpu0 at mainbus0: MB86900/1A or L64801 @ 14.280 MHz, no FPU
cpu0: no cache
obio0 at mainbus0
ie0 at obio0 addr 0x6000000 level 6 address 08:00:20:06:ba:5d, type onboard
oclock0 at obio0 addr 0x3000000 delay constant 4
eeprom0 at obio0 addr 0x2000000
memreg0 at obio0 addr 0x4000000
zs0 at obio0 addr 0x1000000 level 12 softpri 6
zstty0 at zs0 channel 0 (console)
zstty1 at zs0 channel 1
zs1 at obio0 addr 0x0 level 12 softpri 6
kbd0 at zs1 channel 0
ms0 at zs1 channel 1
sw0 at obio0 addr 0xa000000 level 3 pri 3
sw0: options=1<DMA>
scsibus0 at sw0: 8 targets, 8 luns per target
cd0 at scsibus0 targ 1 lun 0: <SONY, CD-ROM CDU-76S, 1.1c> SCSI2 5/cdrom
removable
st0 at scsibus0 targ 4 lun 0: <WANGTEK, 5525ES SCSI OLVT, 71F2> SCSI1
1/sequential removable
st0: drive empty
vme0 at mainbus0
nfs_boot: trying RARP (and RPC/bootparam)
ie0: TDR detected an open 26 clocks away
ie0: 65 frames 195 bufs
ie0: reserved 56916 bytes
nfs_boot: client_addr=0xc0a80164 (RARP from 0xc0a80101)
ie0: 65 frames 195 bufs
ie0: reserved 56916 bytes
nfs_boot: server_addr=0xc0a80101
nfs_boot: hostname=sun4
root on hiram:/export
WARNING: clock lost 10793 days -- CHECK AND RESET THE DATE!
root file system type: nfs
data fault: pc=0xf018fb30 addr=0xf0218000 ser=8020<WRITE,TIMEOUT>
panic: kernel fault
syncing disks... done
Frame pointer is at 0xf18e3a28
Call traceback:
  pc = 0xf0191e9c  args = (0x4000e6, 0x400fe6, 0x0, 0x0, 0xf18e3b40, 0x9000e6,
0xf18e3a90) fp = 0xf18e3a90
  pc = 0xf004eae8  args = (0x100, 0x0, 0x0, 0x0, 0xf18e3bb4, 0x9000e0,
0xf18e3af8) fp = 0xf18e3af8
  pc = 0xf01a1f14  args = (0xf01a1bc0, 0x100, 0xf0218000, 0xf18e3bc0, 0x2d,
0xf01f9c00, 0xf18e3b60) fp = 0xf18e3b60
  pc = 0xf000857c  args = (0x9, 0x8020, 0xf0218000, 0xf018fb30, 0x40,
0xf18e3c68, 0xf18e3c08) fp = 0xf18e3c08
  pc = 0xf019f7a0  args = (0x1fff, 0x0, 0xf0218000, 0xf0002000, 0x0, 0x0,
0xf18e3cb8) fp = 0xf18e3cb8
  pc = 0xf013d8c0  args = (0xa00001e2, 0x3c6000, 0xf0206800, 0xf019f694,
0xf0207800, 0x0, 0xf18e3d20) fp = 0xf18e3d20
  pc = 0xf0137564  args = (0xf023286c, 0xf02328a0, 0xf01f9c18, 0x1, 0x0, 0x0,
0xf18e3d88) fp = 0xf18e3d88
  pc = 0xf01a1ddc  args = (0xf02328a0, 0x4, 0x7, 0xf18e3e00, 0xf18f4050,
0xf01f9c00, 0xf18e3ea8) fp = 0xf18e3ea8
  pc = 0xf000857c  args = (0xf18e8000, 0x8080, 0x5a004, 0x204c, 0x0, 0xf18e3fb0,
0xf18e3f50) fp = 0xf18e3f50
  pc = 0x0  args = (0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0xeffffd00) fp = 0xeffffd00
rebooting


EEPROM boot device...sd(0,0,0) 

Does anybody know why? Does my sun miss a device the generic kernel is looking
for?
And, BTW, does anybody know why my framebuffer displays almost nothing (just the
flashing grid i said before), even when i set it on the NVRAM as the primary
console (addr.0x1f = 0x12) ? 
PN: the diags find no p4 device and no screen, but the original proms have been
lost (and replaced with version 1.8) and i don't know if this revision is full
compatible w/this board version.

Thank you in advance
Orazio Sottile