From owner-freebsd-stable@FreeBSD.ORG Fri Nov 28 20:23:37 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 0F29D1065670 for ; Fri, 28 Nov 2008 20:23:37 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from dhcp-172-19-247-186.corp.google.com (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id D53808FC0C; Fri, 28 Nov 2008 20:23:36 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <49305348.3060801@FreeBSD.org> Date: Fri, 28 Nov 2008 12:23:36 -0800 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.18 (Macintosh/20081105) MIME-Version: 1.0 To: Richard Tector References: <492D6663.60704@thekeelecentre.com> In-Reply-To: <492D6663.60704@thekeelecentre.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: Random hangs with 7.1-PRE 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, 28 Nov 2008 20:23:37 -0000 Richard Tector wrote: > I'm not discounting hardware here, but I'm having problems with a > previously stable amd64 system (dmesg attached) now running: > FreeBSD 7.1-PRERELEASE #1: Wed Nov 26 00:10:41 GMT 2008 > and previously running a RELENG_7 from around Oct 15th which also > exhibited the problem. > > The system appears to hang with SSH terminals eventually timing out, and > no other services being available. The odd thing is, when I go to the > console, I can switch between terminals with Alt-F2, etc, but can not > type anything. Pressing the power button a couple of times gives an acpi > not ready message, so it doesn't appear the system has completely hung. > > The system is in a cool room and under little load running basic > services: samba, postgres, dhcp, etc. Never seen problems with the > machine previously. > > Does anyone have any thoughts or suggestions on narrowing down the cause? See the developers handbook chapter on kernel debugging for full instructions on how to gather the necessary information to proceed. Kris