Date: Tue, 15 Jun 2010 11:04:24 +0530 From: Masoom Shaikh <masoom.shaikh@gmail.com> To: freebsd-stable@freebsd.org Subject: disable RAM parity error Message-ID: <AANLkTiksJ53X3eJcuZK8gjTpX7x3Nk1Fo-dITYDgYLa4@mail.gmail.com> In-Reply-To: <AANLkTinr7O6O95Kp_bQmlAULxkpR6Wus890VmhPqej6x@mail.gmail.com> References: <AANLkTinr7O6O95Kp_bQmlAULxkpR6Wus890VmhPqej6x@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello List, In continuation to my earlier mail, I am now convinced(nearly) that the freezes faced by me are "RAM parity error" indeed. http://www.mail-archive.com/freebsd-hackers@freebsd.org/msg70730.html when using internet via wpi0, FreeBSD freezes are very prone to occur compared to when I am using bfe0. But they do occur, due to some reason it feels stable when connected via bfe0. Over course of time I have accumulated some core.txt.<n> files, which I have uploaded to pastebin and their links are below. My question is why only FreeBSD minds about RAM parity error check, while latest offering from Redmond does not ? is there a way to IGNORE RAM parity check ? is it possible to get hold of offending address from these core files ? while I observe "stack pointer" and "frame pointer" have repeated values in core files, I cannot conclude anything from this observation. Anybody here care ? core.txt.1 ------ http://pastebin.com/HDji1Xvs core.txt.2 ------ http://pastebin.com/yXg1iXAN core.txt.3 ------ http://pastebin.com/xEfcgtQf core.txt.4 ------ http://pastebin.com/zVQspP4g core.txt.5 ------ http://pastebin.com/7RjL2san core.txt.6 ------ http://pastebin.com/q4yjVefB Masoom Shaikh
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTiksJ53X3eJcuZK8gjTpX7x3Nk1Fo-dITYDgYLa4>