Date: Sun, 12 Mar 1995 22:27:40 +0200 From: Heikki Suonsivu <hsu@cs.hut.fi> To: Peter Dufault <dufault@hda.com> Cc: freebsd-bugs@freefall.cdrom.com Subject: Re: kern/238: failed assertion in ncr.c --> no more scsi disk access Message-ID: <199503122027.WAA23884@shadows.cs.hut.fi> In-Reply-To: Peter Dufault's message of 12 Mar 1995 15:00:41 %2B0200
index | next in thread | raw e-mail
> >Synopsis: failed assertion in ncr.c --> no more scsi disk access
...
> The hardware: ASUS PCI/I-486SP3G
> Intel 486 DX 4 100
> 32MB Ram 70ns in two sims
> WD8003EP AT-BUS
> Adaptec AHA1542CF with disabled Floppy and disabled BIOS
> ELSA Winner100pro PCI 2MB
> QUANTUM Empire 2100S Target 0 on ncr bus
> "QUANTUM EMPIRE_2100S 1200"
> WANG DAT 3400 Target 3 on ncr bus
> "WangDAT Model 3400DX 1.10"
Cheap taiwanese PCI-VLB combo board (junk)
AMD 486 DX 3 100
32MB ram
SMC Ultra (If I remember correctly)
Cheap PCI NCR controller
> If you try to access /dev/rst0.0 with dd bs=128k if=/dev/rst0.0
> you get on the first access:
> Mar 10 09:00:28 boheme kernel: st0: bad request, must be between 0 and 0
> (I think this message doesn't do any harm. It also starts the first
> access on the adaptec and does no harm there.)
...
> If you try a second time you get the following:
> st0: ncr.c assertion "cp = np->header.cp" line 5171 failed
> st0: ncr.c assertion "cp" line 5172 failed
> .
> .
> ncr0: restart
We also got this with WangDAT 3400DX. The drive works fine on a BT or
Adaptek, but not on a PCI NCR controller. I don't have much more info on
this, I was too busy at the time and moved the driver to another machine.
-
Heikki Suonsivu, T{ysikuu 10 C 83/02210 Espoo/FINLAND,
hsu@cs.hut.fi home +358-0-8031121 work -4513377 fax -4555276 riippu SN
help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199503122027.WAA23884>