Date: Mon, 19 May 2014 15:35:29 -0400 From: Nathaniel W Filardo <nwf@cs.jhu.edu> To: Chris Ross <cross+freebsd@distal.com> Cc: freebsd-sparc64@freebsd.org Subject: Re: FreeBSD 10-STABLE/sparc64 panic Message-ID: <20140519193529.GO24043@gradx.cs.jhu.edu> In-Reply-To: <A092DFEB-D5CF-473E-88BD-81B005C26C57@distal.com> 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> <A092DFEB-D5CF-473E-88BD-81B005C26C57@distal.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--QRo3kt64Wi40AlcO Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, May 19, 2014 at 03:12:15PM -0400, Chris Ross wrote: >=20 > On May 19, 2014, at 10:52, Nathaniel W Filardo <nwf@cs.jhu.edu> wrote: > > I am having trouble bisecting, and it's slow going, but I should report= that > > a clean build of dbd9b17 (r262853), which is well before 03fdc293 (r263= 478) > > -- also exhibits this problem. I believe 04e37d68 also problematic, ju= st in > > case anyone else is out there looking, but I may have flubbed testing t= hat > > one. Will report back soon. >=20 > I went back a little further, and had two successful boots with a kernel > from r262743. That was a big multi-MFC so I started there. I am surprised by your success with r262743. I just got 04e37d68 to crash on me; that corresponds to the much earlier r262349. It booted fine at least twice but then crashed in the usual place. The backtrace is a little different this time and seems not to include any noise from bge, but it's still right around the time when networking is coming up: Setting hostname: hydra.priv.oc.ietfng.org. tap0: Ethernet address: 00:bd:00:00:57:00 tap1: Ethernet address: 00:bd:00:00:58:01 spin lock 0xc0c5f420 (smp rendezvous) held by 0xfffff80005f90920 (tid 100328) too long timeout stopping cpus panic: spin lock held too long cpuid =3D 1 KDB: stack backtrace: #0 0xc05204b0 at _mtx_lock_spin_failed+0x50 #1 0xc0520578 at _mtx_lock_spin_cookie+0xb8 #2 0xc088849c at tick_get_timecount_mp+0xdc #3 0xc054275c at binuptime+0x3c #4 0xc08521ec at timercb+0x6c #5 0xc0888800 at tick_intr+0x220 Uptime: 23s I'm currently going way back to 44aad33d (r261716) and will see what happens. Cheers, --nwf; --QRo3kt64Wi40AlcO Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAlN6XQEACgkQTeQabvr9Tc8qBgCfcjiqpa++JfouiM1u5F131s+H 8YQAn3McYzPqBLB3vI+erPXQn29O4o/v =cR4l -----END PGP SIGNATURE----- --QRo3kt64Wi40AlcO--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20140519193529.GO24043>