From owner-freebsd-current Mon Sep 22 22:14:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA17747 for current-outgoing; Mon, 22 Sep 1997 22:14:53 -0700 (PDT) Received: from bunyip.cc.uq.edu.au (daemon@bunyip.cc.uq.edu.au [130.102.2.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA17738 for ; Mon, 22 Sep 1997 22:14:36 -0700 (PDT) Received: (from daemon@localhost) by bunyip.cc.uq.edu.au (8.8.7/8.8.7) id PAA24541 for freebsd-current@freebsd.org; Tue, 23 Sep 1997 15:14:27 +1000 Received: from localhost.dtir.qld.gov.au (localhost.dtir.qld.gov.au [127.0.0.1]) by ogre.dtir.qld.gov.au (8.8.7/8.8.7) with SMTP id PAA18083; Tue, 23 Sep 1997 15:13:29 +1000 (EST) Message-Id: <199709230513.PAA18083@ogre.dtir.qld.gov.au> X-Authentication-Warning: ogre.dtir.qld.gov.au: localhost.dtir.qld.gov.au [127.0.0.1] didn't use HELO protocol To: freebsd-current@freebsd.org cc: syssgm@dtir.qld.gov.au Subject: Re: Assertion failed in ncr driver References: <19970922230618.13112@keltia.freenix.fr> <19970923053330.QX53740@uriah.heep.sax.de> In-Reply-To: <19970923053330.QX53740@uriah.heep.sax.de> from J Wunsch at "Tue, 23 Sep 1997 03:33:30 +0000" Date: Tue, 23 Sep 1997 15:13:29 +1000 From: Stephen McKay Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tuesday, 23rd September 1997, J Wunsch wrote: >As Ollivier Robert wrote: > >> Any idea why I get these ? >> >> assertion "cp" failed: file "../../pci/ncr.c", line 6227 >> sd0: COMMAND FAILED (4 28) @f0765800. >> assertion "cp" failed: file "../../pci/ncr.c", line 6227 >> sd0: COMMAND FAILED (4 28) @f0765c00. > >I'm seeing the same errors occasionally for the IBM DCAS-34330 (not >the `W' in my case, and only a NCR 53c810), also when dump(8)ing. >Wrote this to Stefan in private mail, but it seems he didn't have >enough time to read his mail since. Me too! I occasionally see these errors with my Diamond FirePort 40 (53c875j based) and IBM DCAS-34330W. I have exchanged a bit of mail with Stefan already, but no promising leads developed. I have no way of reliably reproducing the problem, but I do know it has been there a long time because it was happening when I ran 2.2.2 (slightly modified to recognise the 875j). Could the disk be a rogue after all the praise we've heaped on it? Stephen.