I'm trying to run NetBSD/sun3x on a -3/80.  I have two disks on it, sd0
at targ 0 lun 0 and sd1 at targ 1 lun 0; I'm running with root on sd0a
swap on sd0b.  sd1 is partitioned with one partition covering the
entire disk.  I had booted single-user.

Here's a ten-finger copy of the crash.  I didn't bother copying all the
arguments in the stack trace.  The kernel is straight off
ftp.netbsd.org as of a day or two ago.  (I'd give its md5 checksum, but
there seem to be other problems - I can't get it off that machine.  I
get the right number of bytes but the checksum is wrong; the -3/80's
(serial) console spewed "le0: memory error" at me about 20 times while
I was trying to do the transfer, which may be related.  Another attempt
gave me maybe 10 "le0: memory error" messages and then panicked.)

Is this simply the known flakiness of the sun3x esp when used with
multiple targets?  (I intend to move everything to the disk that's
currently sd1....)

# fsck /dev/rsd1c
** /dev/rsd1c
** File system is clean; not checking
# fsck -f /dev/rsd1c
esp0: illegal command: 0x1 (state 4, phase 7, prevphase 3)
sd1(esp0:1:0): esp0: timed out [ecb 0xf854a8ec (flags 0x7, dleft 20, stat 2)], <
state 1, nexus 0xf854a8ec, phase(c 101, p 101), resid 0, msg(q 0,o 0) >
sd1(esp0:1:0): esp0: timed out [ecb 0xf854a8ec (flags 0x47, dleft 20, stat 2)], 
<state 1, nexus 0xf854a8ec, phase(c 101, p 101), resid 0, msg(q 0,o 0) > AGAIN
panic: esp0: nexus in reset state
Stopped at ....
db> trace
_Debugger(...) + 6
_panic(...) + 40
_ncr53c9x_intr(...) + c6
_isr_autovec(...) + 60
__isr_autovec(?)
_softclock(...) + 4
_hardclock(...) + 180
_clock_intr(...) + 16
__isr_clock(?)
_mi_switch(...) + 4
_tsleep(...) + 132
_scheduler(...) + 66
_main(...) + 500

					der Mouse

			       mouse@rodents.montreal.qc.ca
		     7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B