Subject: changes to config / ncr5380 driver?
To: None <port-pc532@netbsd.org>
From: Jon Buller <jonb@paclink.com>
List: port-pc532
Date: 01/03/2000 14:44:43
Does anyone know what has happened to the ncr driver in the last
couple of weeks? I built a (couple of) kernel(s) that panic when
probing the scsi system, and just figured out a work around. Is
this a proper fix, or the creation of a bug/anti-bug pair?
OK, the problem is that when this appears in the boot sequence:
Jan 3 07:19:17 bullbox /netbsd: ncr0 at mainbus0 addr 0xffd00000, irq 4
Jan 3 07:19:17 bullbox /netbsd: scsibus0 at ncr0: 8 targets, 8 luns per target
it is followed by (from memory):
Jan 3 07:19:17 bullbox /netbsd: ncr1 at mainbus0 addr 0xffd00000, irq 4
panic: interrupt already allocated
instead of:
Jan 3 07:19:17 bullbox /netbsd: zero=fff8802b, bio=4010, net=34010, tty=76a90,
clock=76a94, imp=76a90, softclock=fff9c02b, softnet=34000
Jan 3 07:19:17 bullbox /netbsd: scsibus0: waiting 2 seconds for devices to settle...
Jan 3 07:19:17 bullbox /netbsd: sd0 at scsibus0 targ 0 lun 0: <SEAGATE, ST15230W SUN4.2G, 0738> SCSI2 0/direct fixed
Jan 3 07:19:17 bullbox /netbsd: sd0: 4095 MB, 3992 cyl, 19 head, 110 sec, 512 bytes/sect x 8386733 sectors
The fix I have is to apply the following diff:
Index: std.pc532
===================================================================
RCS file: /cvsroot/syssrc/sys/arch/pc532/conf/std.pc532,v
retrieving revision 1.11
diff -u -r1.11 std.pc532
--- std.pc532 1999/11/15 19:00:29 1.11
+++ std.pc532 2000/01/03 22:37:15
@@ -11,7 +11,7 @@
mainbus0 at root
clock0 at mainbus0 # system timer
rtc0 at mainbus0 # realtime clock
-ncr* at mainbus0 # ncr SCSI driver
+ncr0 at mainbus0 # ncr SCSI driver
scsibus0 at ncr? # ncr SCSI bus
#aic* at mainbus0 # aic SCSI driver
#scsibus1 at aic? # aic SCSI bus
Is that reasonable / proper? Any suggestions to correct it if it's not?
Jon