From owner-freebsd-sparc64@FreeBSD.ORG  Thu May 19 17:25:49 2011
Return-Path: <owner-freebsd-sparc64@FreeBSD.ORG>
Delivered-To: freebsd-sparc64@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 7F80A1065675
	for <freebsd-sparc64@freebsd.org>; Thu, 19 May 2011 17:25:49 +0000 (UTC)
	(envelope-from marcel@xcllnt.net)
Received: from mail.xcllnt.net (mail.xcllnt.net [70.36.220.4])
	by mx1.freebsd.org (Postfix) with ESMTP id 334F98FC21
	for <freebsd-sparc64@freebsd.org>; Thu, 19 May 2011 17:25:48 +0000 (UTC)
Received: from sa-nc-common3-61.static.jnpr.net (natint3.juniper.net
	[66.129.224.36]) (authenticated bits=0)
	by mail.xcllnt.net (8.14.4/8.14.4) with ESMTP id p4JHAR85003361
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Thu, 19 May 2011 10:10:36 -0700 (PDT)
	(envelope-from marcel@xcllnt.net)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Marcel Moolenaar <marcel@xcllnt.net>
In-Reply-To: <20110519162553.GA88158@mech-cluster241.men.bris.ac.uk>
Date: Thu, 19 May 2011 10:10:22 -0700
Content-Transfer-Encoding: 7bit
Message-Id: <2147A9F8-B80F-4A33-9D7F-ACE8DFFF3747@xcllnt.net>
References: <20110519162553.GA88158@mech-cluster241.men.bris.ac.uk>
To: Anton Shterenlikht <mexas@bristol.ac.uk>
X-Mailer: Apple Mail (2.1084)
Cc: freebsd-sparc64@freebsd.org
Subject: Re: panic on r219425
X-BeenThere: freebsd-sparc64@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Porting FreeBSD to the Sparc <freebsd-sparc64.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-sparc64>, 
	<mailto:freebsd-sparc64-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-sparc64>
List-Post: <mailto:freebsd-sparc64@freebsd.org>
List-Help: <mailto:freebsd-sparc64-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-sparc64>,
	<mailto:freebsd-sparc64-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 19 May 2011 17:25:49 -0000


On May 19, 2011, at 9:25 AM, Anton Shterenlikht wrote:

> I found my blade 1500 silver r219425 in debugger
> today after Uptime: 69d2h22m8s
> 
> db> bt
> Tracing pid 10 tid 100002 td 0xfffff80002059980
> uart_intr() at uart_intr+0x1b4
> intr_event_handle() at intr_event_handle+0x64
> intr_execute_handlers() at intr_execute_handlers+0x8
> intr_fast() at intr_fast+0x68
> -- interrupt level=0xc pil=0 %o7=0xc0268610 --
> sched_idletd() at sched_idletd+0x8c
> fork_exit() at fork_exit+0x9c
> fork_trampoline() at fork_trampoline+0x8
> db> show thread
> Thread 100002 at 0xfffff80002059980:
> proc (pid 10): 0xfffff80002053a70
> name: idle
> stack: 0xe2e12000-0xe2e19fff
> flags: 0x50024  pflags: 0x200000
> state: RUNNING (CPU 0)
> priority: 255
> container lock: sched lock (0xc05e5bc0)
> db>

Normally when you go from the uart interrupt handler to the
debugger, you have a break condition on the serial line or
someone (accidentally) typed the debugger character sequence.
Look at the message buffer to see if this is the case. If
yes, then you can just continue...

FYI,

-- 
Marcel Moolenaar
marcel@xcllnt.net