From owner-freebsd-stable@FreeBSD.ORG Thu Jul 15 18:45:53 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 818841065678 for ; Thu, 15 Jul 2010 18:45:53 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 51BEE8FC1C for ; Thu, 15 Jul 2010 18:45:53 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id DFD1846B09; Thu, 15 Jul 2010 14:45:52 -0400 (EDT) Received: from jhbbsd.localnet (smtp.hudson-trading.com [209.249.190.9]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id D66A28A04E; Thu, 15 Jul 2010 14:45:51 -0400 (EDT) From: John Baldwin To: freebsd-stable@freebsd.org Date: Thu, 15 Jul 2010 13:33:39 -0400 User-Agent: KMail/1.13.5 (FreeBSD/7.3-CBSD-20100217; KDE/4.4.5; amd64; ; ) References: In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201007151333.39738.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (bigwig.baldwin.cx); Thu, 15 Jul 2010 14:45:51 -0400 (EDT) X-Virus-Scanned: clamav-milter 0.95.1 at bigwig.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.6 required=4.2 tests=AWL,BAYES_00 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on bigwig.baldwin.cx Cc: Masoom Shaikh Subject: Re: FreeBSD RELEASE-8.0-p3 panic X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Jul 2010 18:45:53 -0000 On Thursday, July 15, 2010 1:13:05 pm Masoom Shaikh wrote: > Howdy, > > here is the image of my FreeBSD panic > http://images.cjb.net/d64f4.jpg > > the error says RAM parity error(not visible in pic). but I have > following reasons to believed it could be wrong > > 1. I have 1GB of RAM, with two chips of 512MB each. It panics even if > I boot with only 512MB of total RAM. i.e. one chip removed. It panics > for both chips individually. > 2. I tried replacing my both 512MB chips with two 512MB chips from my > friends laptop, it still panics with exact same error. RAM parity > error, it is very unlikely that his chips have this problem. He runs > Ubuntu on those chips and Windows7 with no issues whatsoever. > 3. Windows7 operates on this(my) laptop just fine. > > sometimes it take 3-4 attempts to boot it, since it panics the moment > KDM tries to load. But once running it runs few hours if I do not > subject it to load. Even moderate load like browsing some multimedia > content websites, e.g. youtube or some site with lots of flash based > ads or even some javascript heavy page like GMail etc... It appears > the moment I start subjecting the machine to load, mem usage increases > and it hits the part of RAM which might possibly have parity error. > > have a look at the pic, the frame pointer is always remains same > 0xffffffff803f1ef1. I have already asked, and again ask, is there a > way to ask FreeBSD to "ignore" some part of RAM ? how do I zero in on > the exact point of failure ? I am aware, just too many variables are > here, some wild guesses ? > > I am very sorry for my feeble OS debugging skills if any, but FreeBSD > has nothing to do with my day job, it is just a hobby for me. I > sincerely want it to work. There is a tunable you can set in the loader (vm.blacklist) to a list of physical addresses of pages that should be ignored. -- John Baldwin