Date: Tue, 17 Sep 1996 18:37:45 -0700 (PDT) From: asami@freebsd.org (Satoshi Asami) To: current@freebsd.org Subject: RAM parity error Message-ID: <199609180137.SAA09571@silvia.HIP.Berkeley.EDU>
next in thread | raw e-mail | index | archive | help
Is there any reason why the above would happen when it is NOT the hardware that's broken? I've seen it on a couple of P6 boxes around here, with or without ccd, when I try to push a lot of stuff through the SCSI system (like parallel iozone's on multiple non-ccd filesystems). I'd send you the dmesg output if it's not all disks. I believe this machine has the Intel Natoma chipset with 32MB of parity RAM (9 chips, the middle one is bigger than others, is this the "logic parity" thing?).... Satoshi ------- >> gdb -k kernel.1 vmcore.1 GDB is free software and you are welcome to distribute copies of it under certain conditions; type "show copying" to see the conditions. There is absolutely no warranty for GDB; type "show warranty" for details. GDB 4.13 (i386-unknown-freebsd), Copyright 1994 Free Software Foundation, Inc...(no debugging symbols found)... IdlePTD 201000 current pcb at 1e81f0 panic: RAM parity error, likely hardware failure. #0 0xf0113197 in boot () (kgdb) bt #0 0xf0113197 in boot () #1 0xf0113456 in panic () #2 0xf01c5b05 in isa_nmi () #3 0xf01bf2ee in trap () #4 0xf01b4b61 in calltrap () #5 0xf0194652 in scsi_scsi_cmd () #6 0xf0198269 in sdstart () #7 0xf019810e in sd_strategy () #8 0xf0195368 in scsi_strategy () #9 0xf0197c3c in sdstrategy () #10 0xf013927a in spec_strategy () #11 0xf01a4caa in ufs_strategy () #12 0xf012ed33 in cluster_read () #13 0xf019e5d1 in ffs_read () #14 0xf0135a86 in vn_read () #15 0xf011a16f in read () #16 0xf01bfca9 in syscall () #17 0xf01b4bb5 in Xsyscall () #18 0x1095 in ?? ()
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199609180137.SAA09571>