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 Message-ID: <19980107090116.47086@lemis.com> In-Reply-To: <199801060852.AAA04597@dog.farm.org>; from Dmitry Kohmanyuk on Tue, Jan 06, 1998 at 12:52:04AM -0800 References: <199801060852.AAA04597@dog.farm.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19980107090116.47086>