On Mon, Jan 23, 2006 at 11:27:07PM +0100, Hauke Fath wrote:
> At 8:29 Uhr -0800 18.1.2006, Chuck Silvers wrote:
> >On Tue, Jan 17, 2006 at 08:29:56PM +0100, Hauke Fath wrote:
> >> Folklore has it that there are SCSI devices that work with one but not the
> >> other, or vice versa (or none, like a Sun branded Seagate 420 MB disk I
> >> have around).
> >
> >what does that seagate disk do with the sbc driver with flags 7?
> 
> I'd have to check. With one driver, the machine drowns in parity errors
> while going multi-user, and with the other it gets little further. The
> flags should be settable with gdb, no?

the ncrscsi driver ignores all parity errors, so it must be the sbc driver
that has problems with that.  try editing dev/ic/ncr5380sbc.c and
commenting out the checks for SCI_CSR_PERR being set.  if that makes
your drive work then I'll add a way to disable the check selectively.



> >> > the MI driver is 50% faster and uses 1/3 less CPU time than the MD driver.
> >>
> >> Is it? Which machine, which disk, which benchmark? You are aware that a
> >> busy NetBSD/mac68k loses time so badly that any benchmark data is to be
> >> taken with a spoon of salt?  ;)
> >
> >it's a Mac IIci.  the disk is:
> >sd0 at scsibus0 target 0 lun 0: <FUJITSU, M2616S, 1003> disk fixed
> >sd0: 100 MB, 1544 cyl, 4 head, 33 sec, 512 bytes/sect x 205086 sectors
> 
> Hm, fairly slow disk. I have a few old disks here, mostly Quantums, a
> Conner and the odd IBM. It may take some time until I can come up with
> data, though - still struggling with getting netbsd-2 stable.

ok, thanks.

-Chuck