From owner-freebsd-hackers@FreeBSD.ORG Thu Dec 14 21:07:37 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7343916A50A for ; Thu, 14 Dec 2006 21:07:37 +0000 (UTC) (envelope-from tyler@bleepsoft.com) Received: from zeus.lunarpages.com (zeus.lunarpages.com [216.193.211.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id A9F8143CA1 for ; Thu, 14 Dec 2006 21:04:54 +0000 (GMT) (envelope-from tyler@bleepsoft.com) Received: from cpe-24-26-238-91.satx.res.rr.com ([24.26.238.91] helo=[192.168.250.101]) by zeus.lunarpages.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.52) id 1Guxnq-00036f-23; Thu, 14 Dec 2006 13:07:42 -0800 In-Reply-To: <20061214190510.GA26590@neutrino.bsdhome.com> References: <20061214190510.GA26590@neutrino.bsdhome.com> Mime-Version: 1.0 (Apple Message framework v752.3) Message-Id: <552E24DE-C1D1-41B1-83D2-157F0A3E0449@bleepsoft.com> From: "R. Tyler Ballance" Date: Thu, 14 Dec 2006 15:06:29 -0600 To: Brian Dean X-Mailer: Apple Mail (2.752.3) X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - zeus.lunarpages.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [47 12] X-AntiAbuse: Sender Address Domain - bleepsoft.com X-Source: X-Source-Args: X-Source-Dir: Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-hackers@freebsd.org Subject: Re: Kernel hang on 6.x X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Dec 2006 21:07:37 -0000 On Dec 14, 2006, at 1:05 PM, Brian Dean wrote: > Hi, > > We're experiencing a kernel hang on a 6.x quad processor Sun amd64 > based system. We are able to reproduce it fairly reliably, but the > environment to do so is not easily replicatable so I cannot provide a > simple test case. However, I have been able to build a debug kernel > and when the system "hangs", I can break to the debugger prompt. But > once there, I'm not sure what to do to isolate where the system is > hung up. I have confirmed that the hang occurs in both SMP and > uniprocessor mode. Here are some system details: I think you'll need to ship this machine to my house for further um....erm, diagnostics, yes, that's it ;) On a more serious topic, can you paste the output from: ddb> show pcpu ddb>allpcpu ddb>traceall ddb>show alllocks ddb>show lockedvnods Just curious as to whether those would show more info, because you're right, that trace is about as informative as new printer paper :) Cheers R. Tyler Ballance: Lead Mac Developer at bleep. software contact: tyler@bleepsoft.com | jabber: tyler@jabber.geekisp.com