From owner-freebsd-hackers@FreeBSD.ORG Mon Oct 21 13:30:39 2013 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id A2BF7451; Mon, 21 Oct 2013 13:30:39 +0000 (UTC) (envelope-from rank1seeker@gmail.com) Received: from mail-ee0-x22e.google.com (mail-ee0-x22e.google.com [IPv6:2a00:1450:4013:c00::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 199DB2855; Mon, 21 Oct 2013 13:30:38 +0000 (UTC) Received: by mail-ee0-f46.google.com with SMTP id c13so3594588eek.5 for ; Mon, 21 Oct 2013 06:30:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:from:to:cc:subject:date:in-reply-to:references; bh=iG+TvQuRVihfm/O6YXLr+oCFjKxvJiG9W9PnnnnueqI=; b=hNqY7yX/HzNcmU/UdXk9kyGd0s8w9w0lHkxQO7CgMPQh3jHAG5ZB3cboJGqb8yOUlc s6f6jsLHME8hEjGWj9SckL8YuQ6HOwKLOMk/VG3AdHP7r90Mv7L2EYFHhLqNa7hG5Prn DodRti0NrtSYmw12n8CQ1PnfOIzwPSnR/acMALhi7Y4zIGaJzeUcwYB5gfKbKLWQ95Dp oQwWY9XADU3DgxmaPp/ahtNPxXZvx8WfxegcXWYolqqMre1kC9xi7sUbROP9e9lVttWT z6Cml0SDRUbZV8NJ7/4qZDZ13yBNz+1AYKqt7z0KPHPy8uvid5tKvkMQF9k+Pr8rqf3+ oAvA== X-Received: by 10.15.81.137 with SMTP id x9mr1953361eey.77.1382362237463; Mon, 21 Oct 2013 06:30:37 -0700 (PDT) Received: from DOMYPC ([82.193.208.225]) by mx.google.com with ESMTPSA id b42sm43828623eem.9.2013.10.21.06.30.35 for (version=TLSv1 cipher=RC4-SHA bits=128/128); Mon, 21 Oct 2013 06:30:36 -0700 (PDT) Message-ID: <20131021.133036.045.1@DOMY-PC> From: rank1seeker@gmail.com To: "John Baldwin" Subject: Re: UFS related panic (daily <-> find) Date: Mon, 21 Oct 2013 15:30:36 +0200 In-Reply-To: References: <20130719.174511.786.3@DOMY-PC> <201310071212.05281.jhb@freebsd.org> <20131016.104912.479.1@DOMY-PC> <201310161650.52354.jhb@freebsd.org> X-Mailer: POP Peeper (3.8.1.0) Cc: Adam Vande More , hackers@freebsd.org X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Oct 2013 13:30:39 -0000 > > Same drill as before, see what instruction this is. Actually, this looks > > to > > be in the same location as your last panic, so a NULL pointer is 0x1 > > instead > > of 0x0 again. In my experience, this would still indicate failing RAM to > > me, > > memtest86+ notwithstanding (memtest86+ is single threaded AFAIK, so it may > > not stress the hardware quite the same, e.g. if the error is heat related, > > etc.). > > > memtest* cannot conclusively diagnose a dimm as good. Usually the only > practical solution is to swap modules with known good ones. > 0xc082c552 : cmp %ecx,0x24(%eax) PREVIOUS we talked about 0xc083bd42 : cmp %ecx,0x24(%eax) CURRENT ONE Lattest (few days ago): -- #7 0xc06d5f11 in cache_lookup_times (dvp=0xc921b470, vpp=0xe7c24ae8, cnp=0xe7c24afc, tsp=0x0, ticksp=0x0) at /usr/src/sys/kern/vfs_cache.c:548 548 numchecks++; (kgdb) p ncp $1 = (struct namecache *) 0x1 (kgdb) p *ncp Cannot access memory at address 0x1 -- Now, after all this I recompiled kernel and world and there was no crash. How can it be, when it is far more stresing dan daily's 'find'?! Why does exactly daily's 'find' AND not every time, but each 10th or 20th time triggers this? I see addresses 0xc08* and 0xc06* appearing each time, so as I have four DDR1 (400) modules, each of 256 MB = 1GB, can those addresses aid me in targeting failing module? If I can't use memtest86+-4.20, to determine failing module, then what is a use of it at all? Test RAM speed perhaps? I might try to pull out module 2 and 4 (dual channel) and wait for a month to see if find will crash machine. Then another month ... Well you get a point. There must be other solution. Thanks for your help. Domagoj