Date: Tue, 16 Aug 2011 20:15:51 -0700 From: Julian Elischer <julian@freebsd.org> To: =?ISO-8859-1?Q?Ask_Bj=F8rn_Hansen?= <ask@develooper.com> Cc: net@freebsd.org, embedded@freebsd.org Subject: Re: system locks up with vr driver on alix board Message-ID: <4E4B3267.8050707@freebsd.org> In-Reply-To: <9255C71C-BB78-417E-A900-85140FC2050C@develooper.com> References: <D8B41107-90ED-4357-A7DA-4FF987C70567@develooper.com> <4E4AB3BE.4090603@sentex.net> <9255C71C-BB78-417E-A900-85140FC2050C@develooper.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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..) >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4E4B3267.8050707>