From owner-freebsd-stable@FreeBSD.ORG Sat Jul 19 06:29:51 2008 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 D30961065675 for ; Sat, 19 Jul 2008 06:29:51 +0000 (UTC) (envelope-from peter@wemm.org) Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.168]) by mx1.freebsd.org (Postfix) with ESMTP id A04778FC12 for ; Sat, 19 Jul 2008 06:29:51 +0000 (UTC) (envelope-from peter@wemm.org) Received: by wf-out-1314.google.com with SMTP id 24so347670wfg.7 for ; Fri, 18 Jul 2008 23:29:51 -0700 (PDT) Received: by 10.142.231.7 with SMTP id d7mr350124wfh.207.1216448991392; Fri, 18 Jul 2008 23:29:51 -0700 (PDT) Received: by 10.142.76.14 with HTTP; Fri, 18 Jul 2008 23:29:51 -0700 (PDT) Message-ID: Date: Fri, 18 Jul 2008 23:29:51 -0700 From: "Peter Wemm" To: "Jo Rhett" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20080711164939.GA10238@lava.net> Cc: FreeBSD Stable , Clifton Royston Subject: Re: how to get more logging from GEOM? 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: Sat, 19 Jul 2008 06:29:51 -0000 On Wed, Jul 16, 2008 at 2:42 PM, Jo Rhett wrote: >> On Fri, Jul 11, 2008 at 12:59:33AM -0700, Jo Rhett wrote: >>> >>> Every time it is rebuilding ad0. Every single boot in the last two >>> weeks. > > On Jul 11, 2008, at 9:49 AM, Clifton Royston wrote: >> >> That just means that it halted without a proper shutdown. If it >> crashes, the mirror isn't stopped properly, so it's marked dirty, so it >> must rebuild it. It is the precise analogy of finding all the file >> systems dirty on boot and fscking them, following a crash. > > > Thanks for the clarification. Dang, I hoped I was on to something. This is really off on a tangent, but I thought I'd mention it on the off-chance that it fit your problem. Recently there have been grumblings about heat problems with certain nvidia chipsets on consumer boards. Apparently, there is some process issue, if you believe trade rags like theinquirer.net etc. Apparently there is some issue with heat damage over time. Consumer motherboards with passive cooled (no fan) heat pipes etc seem to be particularly vulnerable. I use the word "apparently" because it is far from a verified fact. However, I've got two motherboards, one running freebsd, one running windows, with nvidia chipsets. Both used to be fine with onboard IDE activity. Both now use raid controllers so the IDE interfaces have been idle for a good year or so. Something came up and I had to use the IDE interfaces for a lot of data transfer. Suddenly, both machines are flakey. The windows machine blue screens under load. My freebsd box just "turns off" (motherboard appears to power off, but the power supply is on still). The same happens when I use a linux boot disk, so I know its not FreeBSD's fault. The common factor seems to be that the motherboards are now about a year and a half old. They both have the same nvidia south bridge that theinquirer.net was trashing. Both used to work fine, now have problems with IDE. and now I recalled the article and started wondering... Do you, by any wildly remote chance, have an nvidia based motherboard? I believe the fault I'm seeing is the system asserting a fatal error by doing a HT ECC flood to halt everything. -- Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com; KI6FJV "All of this is for nothing if we don't go to the stars" - JMS/B5 "If Java had true garbage collection, most programs would delete themselves upon execution." -- Robert Sewell