From owner-freebsd-amd64@FreeBSD.ORG Wed Apr 13 07:44:39 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B1E2B16A4CE for ; Wed, 13 Apr 2005 07:44:39 +0000 (GMT) Received: from anduin.net (anduin.net [212.12.46.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6343A43D41 for ; Wed, 13 Apr 2005 07:44:39 +0000 (GMT) (envelope-from ltning@anduin.net) Received: from [213.225.74.166] (helo=[10.0.16.10]) by anduin.net with esmtpa (Exim 4.50 (FreeBSD)) id 1DLcYA-0000kP-5I for amd64@freebsd.org; Wed, 13 Apr 2005 09:44:38 +0200 User-Agent: Microsoft-Entourage/11.1.0.040913 Date: Wed, 13 Apr 2005 09:44:35 +0200 From: Eirik =?ISO-8859-1?B?2A==?=verby To: Message-ID: In-Reply-To: Mime-version: 1.0 Content-type: text/plain; charset="ISO-8859-1" Content-transfer-encoding: quoted-printable Subject: Re: Mysterious hangs X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Apr 2005 07:44:39 -0000 Sorry, this was meant for the amd64 list. Got another report for this list. Confused the addresses. On 13-04-05 07:28, "Eirik =D8verby" wrote: > Hi, >=20 > For some time I've been seeing infrequent and seemingly random hangs on m= y > dual opteron system. Motherboard is Tyan K8S Pro. Until now I thought it = was a > "hard" hang, but I've got serial console hooked up and BREAK_TO_DEBUGGER,= DDB > and KDB in the kernel, and when sending a break through telnet I get: >=20 > telnet> send brk=20 > KDB: enter: Line break on console >=20 > And nothing more. Which means the box is sort of alive, but fails to pres= ent > even the kernel debugger. The machine is currently on 5.4 as of yesterday= . > It's been hanging before (with anything from days to weeks between), unde= r > various variations of 5.x, but I haven't had the serial console before no= w. >=20 > Has any one seen this before? Any ideas what I could look at? I suspected > hardware, but it seems that isn't the case as most HW errors I've seen wo= uld > cause a total freeze. >=20 > Here's to hoping. >=20 > Thanks, > /Eirik