From owner-freebsd-net@FreeBSD.ORG Wed Aug 17 03:15:58 2011 Return-Path: Delivered-To: net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 02B3C106564A for ; Wed, 17 Aug 2011 03:15:58 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) by mx1.freebsd.org (Postfix) with ESMTP id C8BA68FC08 for ; Wed, 17 Aug 2011 03:15:57 +0000 (UTC) Received: from julian-mac.elischer.org (home-nat.elischer.org [67.100.89.137]) (authenticated bits=0) by vps1.elischer.org (8.14.4/8.14.4) with ESMTP id p7H3Fj4w066830 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Tue, 16 Aug 2011 20:15:47 -0700 (PDT) (envelope-from julian@freebsd.org) Message-ID: <4E4B3267.8050707@freebsd.org> Date: Tue, 16 Aug 2011 20:15:51 -0700 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10.4; en-US; rv:1.9.2.18) Gecko/20110616 Thunderbird/3.1.11 MIME-Version: 1.0 To: =?ISO-8859-1?Q?Ask_Bj=F8rn_Hansen?= References: <4E4AB3BE.4090603@sentex.net> <9255C71C-BB78-417E-A900-85140FC2050C@develooper.com> In-Reply-To: <9255C71C-BB78-417E-A900-85140FC2050C@develooper.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Cc: net@freebsd.org, embedded@freebsd.org, Mike Tancsa Subject: Re: system locks up with vr driver on alix board X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Aug 2011 03:15:58 -0000 On 8/16/11 5:14 PM, Ask Bjørn Hansen wrote: from your description it doesn't sound like a vr problem. I suggest you hook up teh serial console (I am guessing you already have) and set the config options to allow break-to-debugger or alt-break-to-debugger on it when it happens next, drop into the debugger.. in fact, drop in, and do a ps to see what processes are runnable, 'tr [pid] (or thread id)' to get a stack trace of anything that looks interesting, and then cont and do it again a few times to get a feel for where the processor is hanging out (a straight 'tr' will give you the interrupt of the com port which is not intresting..) >