Date: Tue, 17 Sep 1996 21:01:15 -0700 (PDT) From: asami@FreeBSD.org (Satoshi Asami) To: dg@root.com Cc: current@FreeBSD.org, haertel@ichips.intel.com, erich@uruk.org Subject: Re: RAM parity error Message-ID: <199609180401.VAA09813@silvia.HIP.Berkeley.EDU> In-Reply-To: <199609180316.UAA11084@root.com> (message from David Greenman on Tue, 17 Sep 1996 20:16:07 -0700)
next in thread | previous in thread | raw e-mail | index | archive | help
* I'll bet that the real traceback has a "#4.5" that is ahc_scsi_cmd(). gdb * often doesn't decode the traceback correctly since it doesn't deal with * trapframes correctly. I'm seeing *exactly* the same behavior on wcarchive (B0 * Orion, Stepping 1 of the P6). During heavy disk I/O, I occasionally see "RAM * parity errors" during the outsl instruction. That's very interesting to hear. This machine is running 2.2-current (about 1 day old), btw. Intel Natoma, step unknown. By the way, I just remembered that it once crashed during a newfs (over a 35-disk ccd) too. A single disk iozone won't crash it, so I guess having the load of multiple disk I/O's is the problem. Satoshi
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199609180401.VAA09813>