Subject: SBC problems in current
To: None <port-sun3@NetBSD.ORG>
From: Scott Ellis <firstname.lastname@example.org>
Date: 06/29/1997 21:57:44
I have a Sun 3/110 which recently had its primary drive
die, so I took the opportunity to install 1.2, and then
move to -current immediately. Under 1.2, the system
seems to work just fine using the GENERIC kernel (si options
are 3 I beleive).
I build a kernel under -current, with si options of
0x2ffff which should disable EVERYTHING (for completeness sake,
I also built ones with 0x10000, 0x20000, and 0x00000, but they
all exhibit the same behaviour). What happens with -current
is that as soon as the kernel gets done initializing,
I get MANY "si_intr suporious from SBC" errors. Depending
on the options in the kernel, these will continue on forever,
or will stop when the system has a pmap error, and drops into
the debugger (or the prom monitor as it were).
Any ideas? I notice there are a few warnings building -current
on the pmap file, but none on the ncr code.
I'm stuck on what to try to aleviate this. Because the system works
fine under 1.2, I don't think it's a hardware issue, however
I did try various termination schemes (active terminator, passive
terminator, only one drive, all my peripherals, etc etc).
Where should I look next?
// Scott Ellis // email@example.com // firstname.lastname@example.org //
// WARNING: This signature warps time and space in its vicinity //