From owner-freebsd-stable@FreeBSD.ORG Tue Jul 20 16:50:51 2010 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8033A106564A; Tue, 20 Jul 2010 16:50:51 +0000 (UTC) (envelope-from mi+thun@aldan.algebra.com) Received: from mail2.timeinc.net (mail2.timeinc.net [64.236.74.30]) by mx1.freebsd.org (Postfix) with ESMTP id 2B5EB8FC12; Tue, 20 Jul 2010 16:50:51 +0000 (UTC) Received: from mail.timeinc.net (mail.timeinc.net [64.12.55.166]) by mail2.timeinc.net (8.13.8/8.13.8) with ESMTP id o6KGooQE021995 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 20 Jul 2010 12:50:50 -0400 Received: from ws-mteterin.dev.pathfinder.com (ws-mteterin.dev.pathfinder.com [209.251.223.173]) by mail.timeinc.net (8.13.8/8.13.8) with SMTP id o6KGoofY031277; Tue, 20 Jul 2010 12:50:50 -0400 Message-ID: <4C45D3EA.6010208@aldan.algebra.com> Date: Tue, 20 Jul 2010 12:50:50 -0400 From: "Mikhail T." Organization: Virtual Estates, Inc. User-Agent: Mozilla/5.0 (X11; U; Linux i686; uk; rv:1.9.1.10) Gecko/20100512 Lightning/1.0b1 Thunderbird/3.0.5 MIME-Version: 1.0 To: alc@freebsd.org References: <4C4528A8.5040605@aldan.algebra.com> In-Reply-To: Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 8bit X-Mailman-Approved-At: Tue, 20 Jul 2010 17:45:17 +0000 Cc: stable@freebsd.org, Alan Cox Subject: Re: today's 8.1/i386: panic: bad pte 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: Tue, 20 Jul 2010 16:50:51 -0000 20.07.2010 12:47, Alan Cox ΞΑΠΙΣΑΧ(ΜΑ): > Historically, this panic has indicated flakey memory. This panic > occurs because a memory location within a page table has unexpectedly > changed to zero. Ouch... Thanks for the hint (maybe, the panic should say something like that?) In any case, is there a way to identify the the flakey DIMM? I did run memtest on this box and haven't received any errors... Thanks! Yours, -mi