From owner-freebsd-stable@FreeBSD.ORG Wed Jul 16 21:41:36 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 CDBA81065670 for ; Wed, 16 Jul 2008 21:41:36 +0000 (UTC) (envelope-from hostmaster@netconsonance.com) Received: from mail.netconsonance.com (mail.netconsonance.com [198.207.204.4]) by mx1.freebsd.org (Postfix) with ESMTP id B3F098FC2B for ; Wed, 16 Jul 2008 21:41:36 +0000 (UTC) (envelope-from hostmaster@netconsonance.com) Received: from [10.66.240.106] (public-wireless.sv.svcolo.com [64.13.135.30]) (authenticated bits=0) by mail.netconsonance.com (8.14.1/8.14.1) with ESMTP id m6GLfY1n032867; Wed, 16 Jul 2008 14:41:34 -0700 (PDT) (envelope-from hostmaster@netconsonance.com) X-Virus-Scanned: amavisd-new at netconsonance.com X-Spam-Flag: NO X-Spam-Score: -1.876 X-Spam-Level: X-Spam-Status: No, score=-1.876 tagged_above=-999 required=3.5 tests=[ALL_TRUSTED=-1.44, AWL=-0.436] Message-Id: <6AA8BC91-AF84-4CC7-B6BE-4CA84D82EC1E@netconsonance.com> From: Jo Rhett To: Roland Smith In-Reply-To: <20080711155831.GA72963@slackbox.xs4all.nl> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v928.1) Date: Wed, 16 Jul 2008 14:41:28 -0700 References: <20080711155831.GA72963@slackbox.xs4all.nl> X-Mailer: Apple Mail (2.928.1) Cc: FreeBSD Stable 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: Wed, 16 Jul 2008 21:41:36 -0000 On Jul 11, 2008, at 8:58 AM, Roland Smith wrote: >> After about 2 weeks of watching it carefully I've learned almost >> nothing. It's not a disk failure (AFAIK) it's not cpu overheat (now >> running healthd without complaints) it's not based on any given >> network traffic... however it does appear to accompany heavy cpu/ >> disk >> activity. It usually dies when indexing my websites at night (but >> not >> always) and it sometimes dies when compiling programs. Just heavy >> disk isn't enough to do the job, as backups proceed without >> problems. Heavy cpu by itself isn't enough to do it either. But if >> I start compiling things and keep going a while, it will eventually >> hang. > >> Is there anything else I should be looking at? > > Power supply or motherboard would be my first guess. If the system went offline, I agree. But it's clearly a kernel deadlock, since the system remains pingable, answers TCP connections, etc etcc.... but doesn't respond. No TCP negotiation, no response on the console, etc. It's higher level activity which isn't working... -- Jo Rhett Net Consonance : consonant endings by net philanthropy, open source and other randomness