From owner-freebsd-sparc64@FreeBSD.ORG Mon Jun 9 18:19:08 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 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 722A024E for ; Mon, 9 Jun 2014 18:19:08 +0000 (UTC) Received: from hydra.pix.net (hydra.pix.net [IPv6:2001:470:e254::4]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3D87522C6 for ; Mon, 9 Jun 2014 18:19:08 +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.8/8.14.8) with ESMTP id s59IIxjs040945 for ; Mon, 9 Jun 2014 14:19:06 -0400 (EDT) (envelope-from cross+freebsd@distal.com) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.98.1 at mail.pix.net Received: from zalamar.mm-corp.net ([65.207.51.191]) (authenticated bits=0) by mail.distal.com (8.14.8/8.14.8) with ESMTP id s59IHbA9000978 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for ; Mon, 9 Jun 2014 14:17:38 -0400 (EDT) (envelope-from cross+freebsd@distal.com) Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\)) Subject: Re: FreeBSD 10-STABLE/sparc64 panic From: Chris Ross In-Reply-To: Date: Mon, 9 Jun 2014 14:13:06 -0400 Content-Transfer-Encoding: quoted-printable Message-Id: References: <20140518083413.GK24043@gradx.cs.jhu.edu> <751F7778-95CE-40FC-857F-222FB37737C0@distal.com> <20140518235853.GM24043@gradx.cs.jhu.edu> <20140519145222.GN24043@gradx.cs.jhu.edu> <20140519193529.GO24043@gradx.cs.jhu.edu> <20140519205047.GP24043@gradx.cs.jhu.edu> To: freebsd-sparc64@freebsd.org X-Mailer: Apple Mail (2.1827) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (mail.distal.com [206.138.151.250]); Mon, 09 Jun 2014 14:17:38 -0400 (EDT) X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Jun 2014 18:19:08 -0000 On May 20, 2014, at 10:45, Chris Ross wrote: > For anyone else following along, and for my own records. Following > my successes with r262743 and r262783, I moved well forward to > r263980. Despite the first boot working successfully, I rebooted it > again this morning, after it had been running for quite a few hours, > and the panic occurred 6 times [=85] Back a few weeks ago, after my failures with r263980, I compiled and booted r263101, which booted on the first attempt 6 times across a span of 3-4 days. I called that =93stable=94, and moved on to r263307 next=85 I ended up getting out of the pattern of testing things, but I know I = ran r263307 for weeks, and rebooted it anytime I remembered to, and never saw it exhibit the failure. This morning, I moved forward to r263508, which looks to be a very large batch of MFC=92s to things in the kernel. This one fails, = although once it did bring up DHCP _before_ failing. But, most of the time if fails = in the same place, after configuring the bge0 interface. All the failures are = still the same backtrace: spin lock 0xc0c61cb0 (smp rendezvous) held by 0xfffff8000552b240 (tid = 100342) too long timeout stopping cpus panic: spin lock held too long cpuid =3D 1 KDB: stack backtrace: #0 0xc051fcb0 at _mtx_lock_spin_failed+0x50 #1 0xc051fd78 at _mtx_lock_spin_cookie+0xb8 #2 0xc088771c at tick_get_timecount_mp+0xdc #3 0xc0541ebc at binuptime+0x3c #4 0xc085138c at timercb+0x6c #5 0xc0887a80 at tick_intr+0x220 reboot in 15 seconds - press a key on the console to abort Again, it failed many times running before eventually lucking into = getting all the way to multiuser. More information for the records. I=92ll likely try to drop back just = before r263508 (r263478) since r263508 was so seemingly large, in case I=92ve found the =93problem point=94. One can hope. - Chris