From owner-freebsd-bugs Sat Mar 11 11:05:42 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA14358 for bugs-outgoing; Sat, 11 Mar 1995 10:40:01 -0800 Received: (from gnats@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA14351; Sat, 11 Mar 1995 10:40:01 -0800 Date: Sat, 11 Mar 1995 10:40:01 -0800 Message-Id: <199503111840.KAA14351@freefall.cdrom.com> From: oli@devsoft.com Reply-To: oli@devsoft.com To: freebsd-bugs Subject: kern/238: failed assertion in ncr.c --> no more scsi disk access In-Reply-To: Your message of Sat, 11 Mar 1995 19:40:12 -0000 <95Mar11.194021met.7430@devsoft.devsoft.com> Sender: bugs-owner@FreeBSD.ORG Precedence: bulk >Number: 238 >Category: kern >Synopsis: failed assertion in ncr.c --> no more scsi disk access >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs (FreeBSD bugs mailing list) >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sat Mar 11 10:40:00 1995 >Originator: Oliver Adler & >Organization: no current org >Release: FreeBSD 2.0-RELEASE i386 also in current snapshot >Environment: 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" >Description: 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 . . sd0: unit attention sd0: oops not qeued This sequence repeats 2-times. There is no more recovery of the scsi subsytem. No more access to the harddisk. I had to reset. Because there is no more disk access I have no exact copy of all kernel messages. But I suppose I got the most important messages. >How-To-Repeat: see description above >Fix: My only work-around was to put the DAT tape to the scsi Bus of the adaptec. Then there is no problem in accessing the DAT after the message st0: bad request, must be between 0 and 0 I took care of the proper termination in both setups. I also tried the DAT in SCSI1 and SCSI2 mode. Sorry that I can't help more. Thank you and the whole FreeBSD team for providing us with the very BEST unix available. Oliver >Audit-Trail: >Unformatted: