From owner-freebsd-current@FreeBSD.ORG Sun Aug 21 18:45:44 2011 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4F2BA1065672 for ; Sun, 21 Aug 2011 18:45:44 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 99DAD8FC17 for ; Sun, 21 Aug 2011 18:45:43 +0000 (UTC) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id VAA23110; Sun, 21 Aug 2011 21:45:40 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1QvD1f-00015l-VE; Sun, 21 Aug 2011 21:45:39 +0300 Message-ID: <4E515252.4060706@FreeBSD.org> Date: Sun, 21 Aug 2011 21:45:38 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:6.0) Gecko/20110819 Thunderbird/6.0 MIME-Version: 1.0 To: Derrick Edwards References: <1313705220.8034.2.camel@datdude> <4E4E717B.9090407@FreeBSD.org> <1313948879.2448.3.camel@datdude> In-Reply-To: <1313948879.2448.3.camel@datdude> X-Enigmail-Version: undefined Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: "freebsd-current@freebsd.org" Subject: Re: PANICS on 9.0-BETA1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Aug 2011 18:45:44 -0000 on 21/08/2011 20:47 Derrick Edwards said the following: > On Fri, 2011-08-19 at 17:21 +0300, Andriy Gapon wrote: >> on 19/08/2011 01:07 Derrick Edwards said the following: >>> Fatal trap 12: page fault while in kernel mode >>> cpuid = 0; apic id = 00 >>> fault virtual address = 0xffffbe00a45b6798 >> >> This address looks suspiciously like a result of bit flips. >> >>> fault code = supervisor write data, page not present >>> instruction pointer = 0x20:0xffffffff814f444c >>> stack pointer = 0x28:0xffffff82267fbe90 >>> frame pointer = 0x28:0xffffff82267fbea0 >>> code segment = base 0x0, limit 0xfffff, type 0x1b >>> = DPL 0, pres 1, long 1, def32 0, gran 1 >>> processor eflags = interrupt enabled, resume, IOPL = 0 >>> current process = 5889 (csup) >>> trap number = 12 >>> panic: page fault >>> cpuid = 0 >>> Uptime: 10h9m0s >>> Dumping 1823 out of 7912 >> >> Do you always get the same stack trace? Or are they always different? >> I would double-check the hardware first. >> > Andriy, > Thanks for the reply. The stack trace are different. Attached is the > latest one. Machine is about 3 months old. Any recommendations on what > hardware to start looking at. Panic occurs with X and without X being > used. Start with the memory - try memtest86/memtest86+. But actually any bit could be under suspicion - CPU, PSU, etc. -- Andriy Gapon