Subject: It crashed again (after trying new kernel)! =(
To: port-sun3 <port-sun3@NetBSD.ORG>
From: Mauricio Tavares <raub@kushana.aero.ufl.edu>
List: port-sun3
Date: 01/21/1996 13:19:10
	It seems that I am still having some problems rebuilding the
kernel in my 3/50 (4MB RAM, 1GB HD with 64MB swap).  It compiles fine, but
as soon as I try to boot it in multiuser mode -- `b sd()` as opposite to
`b sd() -s` -- it crashes rather nastily:

[...]
dump on sd0b
Automatic boot in progress:  starting file system checks.
/dev/rsd0a: file system is clean; not checking
/dev/rsd0d: file system is clean; not checking
/dev/rsd0e: file system is clean; not checking
/dev/rsd0f: file system is clean; not checking
/dev/rsd0g: file system is clean; not checking
setting tty flags
starting network
add host keshya: gateway localhost
add net default: gateway 128.227.42.1
starting rpc daemons: portmap.
===== < The problem shows its ugly head > ==========
starting system logger, time daemon  syslogd: unknown facility name: "Amerr" 
.
checking for core dump...
savecore: R9//: not found
`: not foundt found
savecore: //: not found
savecore: cannot open Nq_dumpdev_dumplo_time_dumpsize_version_panicstr_dumpmagsa
vecorecdfN:vzreboot: no such file
anic:: not found
savecore: V/: not found
savecore: /: permission denied
savecore: 1: Syntax error:  word unexpected (expecting ")")
checking quotas: done.
building databases...
=== < Would the following message mean my new HD has a problem ? > ===
bad block 1106085656, ino 7492
dev_mkdb: 1: Syntax error:  word unexpected (expecting ")")
clearing /tmp
si0: 1812439040 extra bytes from 0:0
ncr5380_command: short transfer: wanted 10 got 6.
si(0:0:0)-28,0,c3,47,16,70,0,fc,30,0-
Stopped at      _Debugger+0x6:  unlk    a6
db>

I really do not know what may be wrong here.  

	o If the HD has a problem, for instance, how can I look for it and
	  why didn't newfs find it for me?  After all, all my partitions did
	  seem to be ok when the boot program did the file system checks. 

	o If the new kernel has a problem, why did it wait until the the
	  time daemon to give trouble?  As I still have my CDC 94161-155
	  with netbsd installed, I can try putting the new kernel there to
	  see what will happen. 

	o Could it be that I have only 4MB of RAM even though I have 64MB
	  of swap?  If that is the case, I am searching for an expansion 
	  board for my beast.

I do not know whether it may be relevant, but these are the sizes of the 
old and new kernels:

-rwxr-xr-x   1 root  wheel  776110 Jan 17 09:22 netbsd*
-rwxr-xr-x   1 root  wheel  760965 Jan 20 13:26 netbsd.new*

and here is my kernel config file:

#	$NetBSD: GENERIC,v 1.24.2.1 1995/11/18 07:15:57 gwr Exp $

#
# GENERIC Sun3 (3/50, 3/60, 3/110, 3/160, 3/260)
# Supports root on: ie0, le0, sd*, ...
#
# NOTEs:
# o	The "?" you may find as arguments in some commands mean something
#	like: use the default address

include "std.sun3"

# Machines to be supported by this kernel
options		GENERIC
# options 	FPU_EMULATE		# My 3/50 has the 68881 FPU
# options 	HAVECACHE		# Sun3/260 VAC

# Needs to be set per system.  i.e change these as you see fit
# maxusers	4
maxusers	8

# Standard system options
options		SWAPPAGER, VNODEPAGER, DEVPAGER	# paging
options		KTRACE				# system call tracing support
#makeoptions	DEBUG="-g"			# symbols for kgdb + nm
options 	DDB

# Filesystem options
options 	NFSSERVER			# nfs server support
options 	NFSCLIENT			# nfs client support
options 	FFS				# ufs file system
#
options		CD9660		# ISO 9660 + Rock Ridge file system
options 	FDESC		# /dev/fd/*
options		FIFO		# FIFOs; RECOMMENDED
options		KERNFS		# /kern
options		NULLFS		# loopback file system
options 	PROCFS		# /proc
options 	UNION		# union file system

# Networking options
options		INET				# IP prototol stack support
# XXX - Work-around for root on slow SunOS/Sun3 servers (sigh...)
options 	NFS_BOOT_RWSIZE=1024

# Compatability options
options 	COMPAT_SUNOS	# can run SunOS 4.1.1 executables
options 	COMPAT_09	# NetBSD 0.9,
options 	COMPAT_10	# NetBSD 1.0,
options 	COMPAT_43	# and 4.3BSD
options 	TCP_COMPAT_42	# TCP bug compatibility with 4.2BSD

# Sun3-specific debugging options
#options 	CONTEXT_DEBUG
#options 	PMAP_DEBUG
#options 	VMFAULT_TRACE
#options 	SYSCALL_DEBUG
#options 	EXEC_DEBUG
options 	DIAGNOSTIC
options 	SCSIDEBUG

config		netbsd swap generic

#
# Network devices
#

# Intel Ethernet (onboard, or VME)
# ie0 at obio0 addr ? level ?
# ie1 at vmes0 addr 0xffe88000 level 3 vect 0x75

# Lance Ethernet (only onboard)
# The 3/50 only has this ethernet 
le0 at obio0 addr ? level ?

#
# Disk and tape devices
#

# Sun3 "si" SCSI controller (NCR 5380)
ncr_si0 at obio0 addr ? level ?
ncr_si0 at vmes0 addr 0xff200000 level 2 vect 0x40
ncr_si1 at vmes0 addr 0xff204000 level 2 vect 0x41

# Xylogics 7053 controllers
# xdc0 at vmel0 addr 0xffffee80 level 2 vect 0x44
# xdc1 at vmel0 addr 0xffffee90 level 2 vect 0x45
# xd* at xdc? drive ?

# Xylogics 450/451 controllers
# xyc0 at vmes0 addr 0xffffee40 level 2 vect 0x48
# xyc1 at vmes0 addr 0xffffee48 level 2 vect 0x49
# xy* at xyc? drive ?

# Xylogics 472 tape controllers?

#
# Frame buffer devices
#

# The default cgfour address depends on the machine:
# 3/60: obio 0xFF200000 .. 0xFF9fffff
# 3/110: different? (not tested)
# cgfour0 at obmem0 addr ?

# 3/60 P4 accelerated 8-bit color frame buffer
# cgsix0 at obmem0 addr ?

# 3/60 P4 24-bit color frame buffer
# cgeight0 at obmem0 addr ?

# The default bwtwo address depends on the machine:
# 3/50: obio   0x100000
# else: obio 0xff000000
bwtwo0 at obmem0 addr ?
# 3/60 P4 color frame buffer overlay plane, or P4 monochrome frame buffer
#bwtwo1 at obmem0 addr 0xff300000
# 3/60 plug-in color frame buffer overlay plane
#bwtwo1 at obmem0 addr 0xff400000

# Sun-3 color board, or CG5 8-bit VME frame buffer.
# cgtwo0 at vmes0 addr 0xff400000 level 4 vect 0xA8

# Support for the CG9 24-bit VME frame buffer.
# cgnine0 at vmel0 addr 0x08000000

#
# SCSI infrastructure
#
scsibus* at scsi?

# Sun compatible scsi device mappings
sd0 at scsibus? target 0 lun 0
sd1 at scsibus? target 0 lun 1
sd2 at scsibus? target 1 lun 0
sd3 at scsibus? target 1 lun 1
sd* at scsibus? target ? lun ?

st0 at scsibus? target 4 lun 0
st1 at scsibus? target 5 lun 0
st* at scsibus? target ? lun ?

cd0 at scsibus? target 6 lun 0
cd* at scsibus? target ? lun ?

#ch* at scsibus? target ? lun ?


# RAM-disk drivers
rd0 at mainbus?
rd1 at mainbus?

# Misc.
pseudo-device	loop	1		# network loopback
pseudo-device	bpfilter 8		# packet filter
pseudo-device	sl	2		# CSLIP
pseudo-device	ppp	2		# PPP
pseudo-device	tun	2		# network tunneling over tty

pseudo-device	pty	64		# pseudo-terminals
#pseudo-device	vnd	4		# paging to files

Also, I set si_options in /sys/arch/sun3/dev/ncr_si.c to 3.

-- 

 ===========================+=============================================
| Mauricio Tavares          | "We will attack...                          |
| raub@kushana.aero.ufl.edu |  ...under the cover of daylight!" Rimmer    |
 ===========================+=============================================