From owner-freebsd-hackers  Mon Jun 19 16:22:57 1995
Return-Path: hackers-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id QAA18362
          for hackers-outgoing; Mon, 19 Jun 1995 16:22:57 -0700
Received: from silvia.HIP.Berkeley.EDU (silvia.HIP.Berkeley.EDU [136.152.64.181])
          by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id QAA18348
          for <freebsd-hackers@freebsd.org>; Mon, 19 Jun 1995 16:22:55 -0700
Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.6.11/8.6.9) id QAA00724; Mon, 19 Jun 1995 16:22:36 -0700
Date: Mon, 19 Jun 1995 16:22:36 -0700
Message-Id: <199506192322.QAA00724@silvia.HIP.Berkeley.EDU>
To: esser@zpr.uni-koeln.de
CC: mdomsch@dellgate.us.dell.com, freebsd-hackers@freebsd.org
In-reply-to: <199506060928.AA04221@FileServ2.MI.Uni-Koeln.DE> (esser@zpr.uni-koeln.de)
Subject: Re: NCR810 problem?
From: asami@cs.berkeley.edu (Satoshi Asami)
Sender: hackers-owner@freebsd.org
Precedence: bulk

 * > assertion "cp == np->header.cp" failed: file "../../pci/ncr.c", line 5235
 * > assertion "cp" failed: file "../../pci/ncr.c", line 5236
 * > ncr0 targ0?: ERROR (80:100) (e-ab-2) (8/13) @ (10d4:e000000).
 * >              reg: da 10 0 13 47 8 0 1f 0 e 80 ab 80 0 3 0.
 * > ncr0: restart (fatal error).
 * > ncr0: reset by timeout.

Just FYI (as I "seconded" the movement to bash the ncr code :).  This
problem seems to have disappeared recently.  I was away for a week, so
I'm not exactly sure if it's before or after the release.

At least, my 53c825-based no-name card with an Atlas 2.1G survived
half a dozen reboots (including one cold boot) without a hint of this
error since last weekend.

Satoshi