It looks like I sent this to the wrong list. After trying the latest
snapshot kernels (#81) the NCR kernels booted fine and only the SBC
kernels died (guess, what mine use). So I compiled a new kernel with the
NCR driver instead of the SBC driver and now everything works fine. I just
can't use my SyQuest drive anymore.

---------- Forwarded message ----------
Date: Sun, 16 Aug 1998 10:44:28 -0400 (EDT)
From: Skeelo <skeelo@white-dwarf.dyn.ml.org>
To: current-users@netbsd.org
Subject: -current kernels failing to boot

Hi,

I've been seeing my recently built kernels hang when I try to boot them.
Here is a trace.

root on sd4a dumps on sd4b
<debug switch>
Panic switch: PC is 0x36a8.
Stopped at				_Debugger+0x6:	unlk		a6
db> t
_Debugger(ed198,36a8,164db8,3462,0) + 6
_nmihand(0,0,0,2204,0) + 26
_lev7intr(?)
_mi_switch(2204,2200,7403f4,164e78,1047c00) + 12
_tsleep(1046000,11,d39ca,0) + 178
_scsipi_execute_xs(1046000) + 9e
_scsi_scsipi_cmd(1041d40,164e78,6,3450000,200,4,ea60,7403f4,801) + a0
_sdstart(1047e00,1047eb0,7403f4) + 1da
_sdstrategy(7403f4,1000,c,421,1047c00) + c4
_readdisklabel(22,db7de,1047c00,1042f60) + 6c
_sdgetdisklabel(1047e00) + 60
_sdopen(421,0,6000,0) + f4
_sdsize(421,2004,162184,162200,60b00000) + 56
_cpu_dumpconf(0,0) + 4c
_main(11,20fe4,168000,0,1000) + 358
_low9) + 2
db>

It doesn't look md and I've tried the GENERIC kernels from the latest
snapshot with the same results. Does this look familiar to anyone?

My kernel was built on Sat Aug 15 07:17:30 EDT 1998 with freshly sup'd
sources. Everything was fine as of Tue Jun 16 02:46:10 EDT 1998 since the
kernel I built then boots fine.

Thanks.