From owner-freebsd-sparc64@FreeBSD.ORG Fri May 20 10:42:41 2011 Return-Path: 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 B5ECF106566C for ; Fri, 20 May 2011 10:42:41 +0000 (UTC) (envelope-from marius@alchemy.franken.de) Received: from alchemy.franken.de (alchemy.franken.de [194.94.249.214]) by mx1.freebsd.org (Postfix) with ESMTP id 4DDE28FC0A for ; Fri, 20 May 2011 10:42:40 +0000 (UTC) Received: from alchemy.franken.de (localhost [127.0.0.1]) by alchemy.franken.de (8.14.4/8.14.4/ALCHEMY.FRANKEN.DE) with ESMTP id p4KAgOhT040565; Fri, 20 May 2011 12:42:24 +0200 (CEST) (envelope-from marius@alchemy.franken.de) Received: (from marius@localhost) by alchemy.franken.de (8.14.4/8.14.4/Submit) id p4KAgOVe040564; Fri, 20 May 2011 12:42:24 +0200 (CEST) (envelope-from marius) Date: Fri, 20 May 2011 12:42:24 +0200 From: Marius Strobl To: Anton Shterenlikht Message-ID: <20110520104224.GA40529@alchemy.franken.de> References: <20110519162553.GA88158@mech-cluster241.men.bris.ac.uk> <2147A9F8-B80F-4A33-9D7F-ACE8DFFF3747@xcllnt.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2147A9F8-B80F-4A33-9D7F-ACE8DFFF3747@xcllnt.net> User-Agent: Mutt/1.4.2.3i 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 May 2011 10:42:41 -0000 On Thu, May 19, 2011 at 10:10:22AM -0700, Marcel Moolenaar wrote: > > 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 Which also can result from replugging the cable ... Marius