From owner-freebsd-sparc64@FreeBSD.ORG Thu Oct 2 13:37:34 2014 Return-Path: Delivered-To: freebsd-sparc64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 277F290B for ; Thu, 2 Oct 2014 13:37:34 +0000 (UTC) Received: from hydra.pix.net (hydra.pix.net [IPv6:2001:470:e254::4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E72E830E for ; Thu, 2 Oct 2014 13:37:33 +0000 (UTC) Received: from mail.distal.com (mail.distal.com [IPv6:2001:470:e24c:200::ae25]) (authenticated bits=0) by hydra.pix.net (8.14.9/8.14.9) with ESMTP id s92DbOHI019358; Thu, 2 Oct 2014 09:37:32 -0400 (EDT) (envelope-from cross+freebsd@distal.com) Received: from magrathea.distal.com (magrathea.distal.com [206.138.151.12]) (authenticated bits=0) by mail.distal.com (8.14.8/8.14.8) with ESMTP id s92Da2m9001073 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 2 Oct 2014 09:36:03 -0400 (EDT) (envelope-from cross+freebsd@distal.com) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Subject: Re: FreeBSD 10-STABLE/sparc64 panic From: Chris Ross In-Reply-To: <0686B43F-94CC-48BA-81B6-5FBEAF9713EC@distal.com> Date: Thu, 2 Oct 2014 09:36:09 -0400 Content-Transfer-Encoding: quoted-printable Message-Id: <32B71E26-EA09-4143-9E6F-CF4E033E9106@distal.com> References: <323A3936-DE55-459A-B8AA-CFF463922F22@distal.com> <7DD7D2DC-A265-40D6-9995-16ABAF79C1FB@distal.com> <456226AE-0712-4510-AEF5-2053F36F2181@distal.com> <20140929042249.GK43300@funkthat.com> <0686B43F-94CC-48BA-81B6-5FBEAF9713EC@distal.com> To: John-Mark Gurney X-Mailer: Apple Mail (2.1878.6) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (mail.distal.com [206.138.151.250]); Thu, 02 Oct 2014 09:36:04 -0400 (EDT) Cc: freebsd-sparc64@freebsd.org X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Oct 2014 13:37:34 -0000 On Oct 1, 2014, at 22:53 , Chris Ross wrote: > On Sep 29, 2014, at 00:22 , John-Mark Gurney wrote: >> If you could get a core dump (call doadump) that'd be good, but = dumping >> the stack of the tid that held the spinlock too long would be a good >> start.. >=20 > I fear I'm going to need some help doing this. I'm not sure what I = need to > do to get into ddb. (And, after that, I'm not sure how to dump the = stack of > the tld that held the spinlock) Okay. I rebuilt GENERIC after adding options DDB, and found the = following: spin lock 0xc0ccbdb0 (smp rendezvous) held by 0xfffff8000559f6d0 (tid = 100351) too long timeout stopping cpus panic: spin lock held too long [...] db> thread 100351 [ thread pid 299 tid 100351 ] sched_switch+0x3e0: call cpu_switch db> thread =20 [ thread pid 299 tid 100351 ] sched_switch+0x3e0: call cpu_switch db> bt Tracing pid 299 tid 100351 td 0xfffff8000559f6d0 mi_switch() at mi_switch+0x19c critical_exit() at critical_exit+0x9c spinlock_exit() at spinlock_exit+0x8 turnstile_chain_unlock() at turnstile_chain_unlock+0x6c __mtx_unlock_sleep() at __mtx_unlock_sleep+0x9c bge_init() at bge_init+0x5c ether_ioctl() at ether_ioctl+0x70 M_PLIMIT() at M_PLIMIT+0x8 db> dump Cannot dump: no dump device specified. db>=20 Apparently, I don't have a dump device set, so I'll to fix that next = and get a core dump. I'm not sure, however, if what I provided above was the = stack of the tid as was requested. At least, it's not 100% consistent. Since I = had a DDB kernel running, while trying to get the system back up to multiuser, = I did get many more panic's to experiment with, and doing the same "thread NNN", "bt" on many passes I sometimes got different results. Perhaps I'm doing something wrong? Or worse, it may not be 100% consistent. :-/ A pointer to what I need to do within ddb would be appreciated, if I'm doing anything wrong (or suboptimmally), or any other instructions. I'll = try to get a dump device specified. Thanks. - Chris