From owner-freebsd-current  Tue Sep 23 11:36:02 1997
Return-Path: <owner-freebsd-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id LAA26208
          for current-outgoing; Tue, 23 Sep 1997 11:36:02 -0700 (PDT)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA26170
          for <freebsd-current@freebsd.org>; Tue, 23 Sep 1997 11:35:57 -0700 (PDT)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id EAA17215; Wed, 24 Sep 1997 04:34:51 +1000
Date: Wed, 24 Sep 1997 04:34:51 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199709231834.EAA17215@godzilla.zeta.org.au>
To: freebsd-current@freebsd.org, j@uriah.heep.sax.de
Subject: Re: Assertion failed in ncr driver
Cc: roberto@keltia.freenix.fr
Sender: owner-freebsd-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

>> 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.

I get these for an IBM DORS-32160 WA6A.  They are apparently a feature
of IBM firmware :-).  They are almost reproducible using lmdd and lm's
`fileblocks' in a loop.  They never seem to cause file system problems.

Bruce