From owner-freebsd-stable@FreeBSD.ORG Fri May 15 18:10:39 2009 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 4BF601065673; Fri, 15 May 2009 18:10:39 +0000 (UTC) (envelope-from nakal@web.de) Received: from fmmailgate03.web.de (fmmailgate03.web.de [217.72.192.234]) by mx1.freebsd.org (Postfix) with ESMTP id CD40F8FC1E; Fri, 15 May 2009 18:10:38 +0000 (UTC) (envelope-from nakal@web.de) Received: from smtp06.web.de (fmsmtp06.dlan.cinetic.de [172.20.5.172]) by fmmailgate03.web.de (Postfix) with ESMTP id AD872FC8E533; Fri, 15 May 2009 20:10:37 +0200 (CEST) Received: from [217.236.8.179] (helo=zelda.local) by smtp06.web.de with asmtp (TLSv1:AES128-SHA:128) (WEB.DE 4.110 #277) id 1M51rg-0006w4-00; Fri, 15 May 2009 20:10:36 +0200 Date: Fri, 15 May 2009 20:10:34 +0200 From: Martin To: John Baldwin Message-ID: <20090515201034.2b92c525@zelda.local> In-Reply-To: <200905151205.47672.jhb@freebsd.org> References: <1696198956@web.de> <200905151109.21127.jhb@freebsd.org> <20090515173800.071e53c2@zelda.local> <200905151205.47672.jhb@freebsd.org> X-Mailer: Claws Mail 3.7.1 (GTK+ 2.16.1; amd64-portbld-freebsd8.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: nakal@web.de X-Sender: nakal@web.de X-Provags-ID: V01U2FsdGVkX1/+IYzTtYaAHqebxJcNAlWMLAvbstzuFapVuNTK 4JKo30HNFVYDoEnMLq/Jq1XonlCsCZIO8amWY3g08NhugdAdTJ rCl8z1k0E= Cc: freebsd-stable@freebsd.org Subject: Re: kernel trap 12 with interrupts disabled [bge0 on 7.2R] 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: Fri, 15 May 2009 18:10:39 -0000 Am Fri, 15 May 2009 12:05:47 -0400 schrieb John Baldwin : > > (kgdb) x/i 0xffffffff805bbc66 > > 0xffffffff805bbc66 : movzbl (%rdx),%edx > > Hmm, your %rdx is garbage. :( > > rdx 0xef3fdf377db53afa -1207000745686779142 > > That should at least be > > 0xffffff.......... > > Looks like r9 and r14 have the same odd value. Normally I would see > a more obvious breakage such as one of the 'f' nibbles being set to > '0' or 'e', etc. You could try looking for that odd pointer value in > the route structure or as arguments to other functions in the stack > trace to see if you can find a corrupted data structure. Hi John, I've been testing RAM for 2 hours in user space with 3 parallel processes of sysutils/memtest. What can I say? I just got this in second loop of memtest: Loop 2: Stuck Address : ok Random Value : ok Compare XOR : ok Compare SUB : ok Compare MUL : ok Compare DIV : ok Compare OR : ok Compare AND : ok Sequential Increment: ok Solid Bits : ok Block Sequential : ok Checkerboard : testing 59FAILURE: 0xaaaaaaaaaaaaaaaa != 0x400300007007 at offset 0x007dc608. FAILURE: 0x5555555555555555 != 0xf0000070ef00007 at offset 0x007dc609. FAILURE: 0xaaaaaaaaaaaaaaaa != 0x00004003 at offset 0x007dc60a. FAILURE: 0x5555555555555555 != 0x00004002 at offset 0x007dc60b. FAILURE: 0xaaaaaaaaaaaaaaaa != 0xffffffff807cb4e0 at offset 0x007dc60c. FAILURE: 0x5555555555555555 != 0x00000000 at offset 0x007dc60d. FAILURE: 0xaaaaaaaaaaaaaaaa != 0x000002fa at offset 0x007dc60e. FAILURE: 0x5555555555555555 != 0x00000000 at offset 0x007dc60f. Bit Spread : ok Bit Flip : setting 35^C I think this is obvious enough. Thank you for your patience with me. This was a good hint. I would have never thought of a RAM defect. -- Martin