FreeBSD 10-STABLE/sparc64 panic

[Nathaniel W Filardo]

On Mon, May 19, 2014 at 03:12:15PM -0400, Chris Ross wrote:
> 
> On May 19, 2014, at 10:52, Nathaniel W Filardo <nwf at 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 (r263478)
> > -- also exhibits this problem.  I believe 04e37d68 also problematic, just in
> > case anyone else is out there looking, but I may have flubbed testing that
> > one.  Will report back soon.
> 
>   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 = 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;
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 181 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-sparc64/attachments/20140519/a4c7e030/attachment.sig>