Jon Buller <jonb@paclink.com> writes:

> 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

So why does it think there is more than one ncr device? I wouldn't
have called your work-around a bug-antibug pair, but then I wouldn't
call it a fix either! Still, since we will never have more than one ncr device,
it seems a good case for being pragmatic.

Ian