From owner-freebsd-alpha Sat Oct 2 10:58:15 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 2BFFA14FD7 for ; Sat, 2 Oct 1999 10:58:01 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.8.7/8.8.7) with ESMTP id KAA20108; Sat, 2 Oct 1999 10:57:05 -0700 Date: Sat, 2 Oct 1999 10:56:54 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Don Cc: Chuck Robey , alpha@FreeBSD.ORG Subject: Re: Problem with NCR driver In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I would make a CAMDEBUG kernel to print out the commands being sent and/or otherwise hack it so the CDB *and* the dma length is printed out. I'm wondering whether this is related to the problems that seem to have surfaced in the last day or so in -current. Unfortunately, this is not one of the cards the Gerard's driver supports so you can't do a crosscheck to eliminate the sim driver. On Sat, 2 Oct 1999, Don wrote: > > Seeing as the NCR controller is used pretty widely on the Alpha, and many > > of us haven't any problems with it at all, you maybe should give much more > > information, like the model of the controller, the kind of cable (describe > > thoroughly, what's terminating, how many connectors, drives, etc) and how > > the relevant portions of your dmesg and config file. > > > > I'll bet it's something to do with cabling or terminations. Too many of > > us think they're pretty solid controllers. > Well given that these controllers perform flawlessly with the snapshot > kernels and the fact that they performed flawlessly when these systems > were running NetBSD I can honestly say that I dont think the cabling or > the termination is the issue. For clarity the cabling is the default > cabling that comes with the AS200's and the termination is handled by the > drive which is the only one on the chain. > > The relevant dmesg output is: > ncr0: irq 11 at device 6.0 on pci0 > ncr0: interrupting at ISA irq 11 > da0 at ncr0 bus 0 target 6 lun 0 > da0: Fixed Direct Access SCSI-2 device > da0: 10.000MB/s transfers (10.000MHz, offset 8), Tagged Queueing Enabled > da0: 3090MB (6328861 512 byte sectors: 255H 63S/T 393C) > > The error was: > (da0:ncr0:0:6:0): extraneous data discarded. > (da0:ncr0:0:6:0): COMMAND FAILED (9 0) @0xfffffe000057a000. > (da0:ncr0:0:6:0): extraneous data discarded. > (da0:ncr0:0:6:0): COMMAND FAILED (9 0) @0xfffffe000057a000. > (da0:ncr0:0:6:0): extraneous data discarded. > (da0:ncr0:0:6:0): COMMAND FAILED (9 0) @0xfffffe000057a000. > (da0:ncr0:0:6:0): extraneous data discarded. > (da0:ncr0:0:6:0): COMMAND FAILED (9 0) @0xfffffe000057a000. > (da0:ncr0:0:6:0): extraneous data discarded. > (da0:ncr0:0:6:0): COMMAND FAILED (9 0) @0xfffffe000057a000. > > ... > could not fsck /dev/da0a > ... > > syncing disks... done > > Actually I am not sure whether this is da issue or an ncr issue although I > said ncr due to the problems I had a few weeks ago with having to cold > boot the system after making SCSI changes. > > -Don > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-alpha" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message