From owner-freebsd-current  Tue Jan  6 14:32:10 1998
Return-Path: <owner-freebsd-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id OAA01435
          for current-outgoing; Tue, 6 Jan 1998 14:32:10 -0800 (PST)
          (envelope-from owner-freebsd-current)
Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA01377
          for <freebsd-current@FreeBSD.ORG>; Tue, 6 Jan 1998 14:31:54 -0800 (PST)
          (envelope-from grog@lemis.com)
Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137])
	by allegro.lemis.com (8.8.7/8.8.5) with ESMTP id JAA24995;
	Wed, 7 Jan 1998 09:01:23 +1030 (CST)
Received: (from grog@localhost)
          by freebie.lemis.com (8.8.8/8.8.7) id JAA20661;
          Wed, 7 Jan 1998 09:01:17 +1030 (CST)
          (envelope-from grog)
Message-ID: <19980107090116.47086@lemis.com>
Date: Wed, 7 Jan 1998 09:01:16 +1030
From: Greg Lehey <grog@lemis.com>
To: dk+@ua.net
Cc: Satoshi Asami <asami@cs.berkeley.edu>, freebsd-current@FreeBSD.ORG,
        dk@farm.org
Subject: Re: RAM parity error
References: <199801060852.AAA04597@dog.farm.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.84e
In-Reply-To: <199801060852.AAA04597@dog.farm.org>; from Dmitry Kohmanyuk on Tue, Jan 06, 1998 at 12:52:04AM -0800
Organisation: LEMIS, PO Box 460, Echunga SA 5153, Australia
Phone: +61-8-8388-8286
Fax: +61-8-8388-8725
Mobile: +61-41-739-7062
WWW-Home-Page: http://www.lemis.com/~grog
Sender: owner-freebsd-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

On Tue, Jan 06, 1998 at 12:52:04AM -0800, Dmitry Kohmanyuk wrote:
> In article <199712310100.RAA03280@vader.cs.berkeley.edu> you wrote:
>> I have been seeing a "RAM parity error" in one of our machines lately.
>> I have swapped machines and it still happens on the machine in the
>> same position.  The only things that are common in the old and new
>> machines are the external SCSI disk array.  It has happened on 3 PCs.
>
>> Is it possible that data on a non-system filesystem would cause such
>> an error?  I always thought the parity error panic is caused by the
>> chipset asserting a signal line dedicated for the NMI....
>
>> Here's one of the dumps:
>
> [...]
>> #14 0xf0151f62 in spec_strategy ()
>> #15 0xf0151689 in spec_vnoperate ()
>> #16 0xf01aee01 in ufs_vnoperatespec ()
>> #17 0xf0114606 in ccdstart ()
>> #18 0xf0114560 in ccdstrategy ()
>> #19 0xf0151f62 in spec_strategy ()
> [...]
>
> note the ccd drives...

It's a pity you truncated this.  What does the whole trace look like?

Greg