From owner-freebsd-sparc64@FreeBSD.ORG Mon May 19 21:38:01 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 4E1EED1F for ; Mon, 19 May 2014 21:38:01 +0000 (UTC) Received: from blaze.cs.jhu.edu (blaze.cs.jhu.edu [128.220.13.50]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.cs.jhu.edu", Issuer "InCommon Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1E1892AC2 for ; Mon, 19 May 2014 21:38:00 +0000 (UTC) Received: from gradx.cs.jhu.edu (gradx.cs.jhu.edu [128.220.13.52]) by blaze.cs.jhu.edu (8.14.4/8.14.4) with ESMTP id s4JLbu3E017540 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 19 May 2014 17:37:56 -0400 Received: from gradx.cs.jhu.edu (localhost [127.0.0.1]) by gradx.cs.jhu.edu (8.14.8/8.14.5) with ESMTP id s4JLbuu5025544; Mon, 19 May 2014 17:37:56 -0400 Received: (from nwf@localhost) by gradx.cs.jhu.edu (8.14.8/8.14.8/Submit) id s4JLbuvZ025533; Mon, 19 May 2014 17:37:56 -0400 Date: Mon, 19 May 2014 17:37:56 -0400 From: Nathaniel W Filardo To: Chris Ross Subject: Re: FreeBSD 10-STABLE/sparc64 panic Message-ID: <20140519213756.GR24043@gradx.cs.jhu.edu> 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> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="o0y1lerN6xYE2ROn" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Cc: freebsd-sparc64@freebsd.org 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, 19 May 2014 21:38:01 -0000 --o0y1lerN6xYE2ROn Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, May 19, 2014 at 05:19:23PM -0400, Chris Ross wrote: > On May 19, 2014, at 16:50, Nathaniel W Filardo wrote: > > On Mon, May 19, 2014 at 03:35:29PM -0400, Nathaniel W Filardo wrote: > >> I'm currently going way back to 44aad33d (r261716) and will see what > >> happens. > >=20 > > First boot went fine, second boot failed in the same way. Blech. >=20 >=20 > I fear we may be tracking two issues, or otherwise have a problem > in our communications or processes. >=20 > I built and installed r262783, and have booted it three times to > multi-user on the first try. The same was true with two boots of > r262743 earlier. >=20 > You said at some point that the traceback changed. Depending > on specifics of our hardwares, there may be two problems on yours > an only one on mine. I=E2=80=99m grasping, here, but. You=E2=80=99re us= ing a v240, > correct? Mine has two 1.5 Ghz Ultra-Sparc-IIIi=E2=80=99s in it, and 8 GB= of > memory. And just the on-board hardware otherwise, two disk drives. There's apparently some variance in the traceback -- sometimes several interfaces get set up, sometimes they don't, but I think it's all the same issue; it's at least got the same synopsys: smp rendezvous held too long during network configuration. (Or, in that one rare case, later during pf initialization.) Your hardware sounds pretty close to the hardware I'm running here... except I've got 16GB and a mvs SATA card with a few disks hanging off of it. =20 > I suppose I can keep moving forward, but I=E2=80=99m dismayed that we= =E2=80=99re > getting such different results on what we thought was the same test. Indeed; this machine has been useless for days while I have been apparently futilely bisecting. To make sure I wasn't crazy, I went and rebuilt the head of stable/10 and there every boot to multiuser attempted thus far has panic()d. I'm giving up out of frustration, sorry; going to use the current install to build 9-STABLE and jump ship. If that still explodes, I'll try coming up =66rom media for 9-RELEASE and will certainly let people know, because at t= hat point something very strange is going on. Cheers and sorry to abandon the quest, --nwf; --o0y1lerN6xYE2ROn Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAlN6ebQACgkQTeQabvr9Tc8zHwCff0tTEX0rXaAcEoq5L0+pxVKV /VsAmwWGgh2fLh5Wn+qRS8SCgkDRH5To =vCp4 -----END PGP SIGNATURE----- --o0y1lerN6xYE2ROn--